Allied Telesis AT-S97 - Manual (Page 161)

AT-S85 and AT-S97 Management Software Command Line Interface User’s Guide
161
General Description
This command downloads new versions of the AT-S85 and AT-S97 boot
loaders and management software to the management and media
converter modules in a chassis from a TFTP server. Allied Telesis may
post new versions of these files on our web site so our customers can
update their equipment with the latest files.
You can also use this command to download a master configuration file
that you edited at your management workstation to the management
module.
If you are updating the management software on the modules, the
software should be downloaded in the following order:
1. AT-S85 boot loader for the media converter modules.
2. AT-S97 boot loader for the management module.
3. AT-S85 management software for the media converter modules.
4. AT-S97 management software for the management module.
Description of Syntax 1
This command downloads a new version of a boot loader to a
management or media converter module from a TFTP server. The boot
loader is part of the operating system of a module.
The modules use different boot loaders. The AT-MCF2000M Management
Module uses the AT-S97 boot loader and the media converter modules the
AT-S85 boot loader. The boot loader files are identified by their “.BIN”
filename extension and the “S85” and “S97” in the filenames.
A boot loader must be stored on a module in an area of memory referred
to as BOOTBLOCK. This section of memory is separate from the file
system and cannot be displayed with the FILE SHOW command. When
you enter the FILE DOWNLOAD command, you must specify
BOOTBLOCK as the destination. If you specify a filename as the
destination, the command will store the file in the file system of the
module. This is an inappropriate destination for a boot loader. (If you do
inadvertently download a boot loader file into the file system of a module,
you can delete it with the FILE DELETE command. For instructions, refer
to “FILE DELETE” on page 156.)
After a module has received a new boot loader, it tests the file prior to
writing it to BOOTBLOCK area of flash memory to determine whether the
file is appropriate for its module type. If the file type is correct, it writes the
file to the BOOTAPP section. If it is not, it discards the file. This protects
the module from installing the wrong boot loader.