Introduction
is recommended if you need to go back to the version of software that is currently being executed by the ELS10-26.
3.Tell TFTP to transfer (“put”) the first file, (dnld_hdr).
4.Wait one minute, or until the ELS10-26 sends the SNMP Trap described in the swdis branch of SMC’s private MIB. (The Trap will be sent when the ELS10-26 is ready for the second file, which will be somewhat shorter than three minutes.)
5.Tell TFTP to transfer the second file, (dnld_software). This transfer should take approximately one minute.
The initial one minute waiting may be omitted and this second transfer may be initiated immediately following the first transfer; however, that causes the second transfer to take approximately two minutes, and creates a slightly heavier network load during the file transfer.
Note: If the above TFTP sequence is abnormally terminated, there is no cause for alarm, since the ELS10-26 maintains a back-up set of software, and the ELS10-26 will not use the incomplete new software.
Older versions of software may be distributed to an ELS10-26, provided that the older software is at least Version 2.3. To distribute the older software to an ELS10-26, the above TFTP procedure should be altered, with the following step being performed before the older software is distributed.
If the bulk retrieval of all of the parameters of the ELS10-26 had been performed while the ELS10-26 was executing that older software, that retrieved file should be used to do a bulk set of all parameters (as described below). Otherwise, when the older software is distributed and the ELS10-26 reboots, the older software will not understand the format of the ELS10-26’s parameters.2
