Allied Telesis Rapier i AT-RP16Fi/SC, Руководство пользователя

Страница: 57 / 123

Operating the switch 57
Software Release 2.6.1
C613-02025-00 REV C
2. Upload the configuration file.
Upload the configuration file from the switch into the TFTP directory of the
TFTP server on the network, using the defaults set above.
UPLOAD FILE= filename.cfg
Monitor the load progress.
SHOW LOAD
When the upload is complete, check that the file is in the TFTP directory on
the network host.
More information
For more information about loading files onto and uploading files from the
switch, including using LDAP to load PKI certificate information, see the
Operation chapter in the Rapier Series Switch Software Reference .
Upgrading Switch Software
When you first start the switch, it automatically loads the software release from
FLASH memory into RAM, where the CPU uses it to run all the router’s
software features. The switch may also load a patch file to improve the main
release. The software release and any patch files are current when the switch is
produced at the factory.
When Allied Telesyn makes a new patch or release available, you may want to
upgrade the software on your switch to use a new patch or release file. You can
download the latest software patches, full software releases, and CLI help files
from the support site at:
http://www.alliedtelesyn.co.nz/support/rapier .
Make sure you download a patch or release file that matches your switch
model. A patch or release file for Rapier Series Switch has 86 as the first two
digits of the filename. Patch files have the file extension
.paz
and release files
have the file extension
.rez
. For example, the Software Release 2.6.1 for the
Rapier Series Switch has the filename
86s-261.rez.
Release and patch files are compressed ASCII files, and consist of a header
followed by a sequence of Motorola S-records containing the actual code for
the release or patch. The header has a standard format, which provides
information about the release or patch to the switch.
Do not change the header in a release or patch file. At best, this will cause the
file load or install to fail, at worst the switch could be put into a state where it
will not boot correctly until field service action is taken.
The current release and patch file are set as the preferred install. The switch
also has a very limited version of the software stored in EPROM. You cannot
delete this version as it is the default, or boot install. When you load a new
software release or patch, you can set it to run once, the next time the switch
reboots. This temporary install allows you to test run a new release or patch
once, before you make it the preferred install. If the temporary install fails the
switch will automatically run the preferred install if there is one, or otherwise
the default install, the next time the switch reboots.