As of software rev 4.4B, certain units can also be upgraded using TFTP.
Currently, only the Max 4000/HP and "revB" Pipeline 50 units (see
question #3) can use this method.
Marco Hyman explained:
> Jacques Vidrine writes: > > Why is this not available for the Pipeline MAX?? > > Good question. The Max and the Pipeline 400s and the older P50 > execute out of flash. I can't erase and put new code into flash > while the system is running on these units. The code loader exists > in the (very small) boot rom which knows nothing about the lan or wan > or tftp, etc. > > The Max-4000 (nee Max-HP) and the new P50s run out of DRAM so we > can download code to flash while the unit is running. The new code > is used at next power cycle.The process to upgrade via TFTP is as follows:
tloadcode hostname filename
> tloadcode tftp-server mhpt1.bin
will load a new Max 4000/HP version into flash from the machine "tftp-server".
The current configuration is also saved to flash before new code is received, as a precaution. Upon the next reset, the new code will be run out of DRAM. If necessary, the saved configuration will be loaded and a second reset performed automatically.
All Ascend units permit saving and restoring configs via TFTP.
To save a config, perform the following steps:
tsave hostname filename
To restore a config, perform the following steps:
trestore hostname filename
(Under previous revisions, the command was "restore".)
Where hostname is your remote TFTP server, and filename
is an existing world-readable config file on the server.
Note that any configurations saved using TFTP will contain all passwords associated with the unit, in clear text. Special care should be taken with these files (to say that TFTP was not designed for security would be a major understatement).