
Caution: Periodically the procedure for uploading new software to Ascend units changes
significantly. Carefully read the new software loading procedures explained in this section
before upgrading your system.
Definitions and terms
This document uses the following terms:
Guidelines for upgrading system software
Caution: Before upgrading, consider the following very important guidelines:
fsave command immediately after executing the tload command. Failure to do so might cause your Ascend unit to lose its configuration.
Guidelines for downgrading system software
The MAX expects a specific organization of the parameters in a configuration file. When you upgrade a MAX, you can restore a configuration that was saved on an older release. The MAX enters default values for parameters if the MAX supports a parameter that is not included in the configuration file.
The MAX restarts and loads the older version of system software.
After entering you must be able to telnet to the MAX.
Or, press Ctrl-D to invoke the DO menu and select D=Diagnostics.Esc [ Esc =
> prompt, use the TRestore command to restore the configuration as in the following example:
This restores the configuration named>trestore tftp-server router1.cfg
router1.cfg from the TFTP home directory of the server named tftp-server. This file must exist and be readable.
> prompt, enter Exit to return to the VT100 interface.
Before you begin
Make sure you perform all the tasks explained in Table C-2 before upgrading your software.
Upgrading system software with a standard load
To upgrade system software with a standard load you can use either the serial port or TFTP. TFTP is the recommended method because it preserves your Ascend unit's configuration. If you want to use the serial port to upgrade, see "Using the serial port to upgrade to a standard or a thin load" on page C-11.
Using TFTP to upgrade to a standard load
To upgrade to a standard load using TFTP, you only have to enter a few commands. But you must enter them in the correct sequence, or you could lose the Ascend unit's configuration.
Esc [ Esc = > prompt, use the Tsave command to save your configuration as in the following example:
> tsave tftp-server router1.cfgrouter1.cfg in the TFTP home directory of the server named tftp-server. This file must already exist and be writable. Normally, TFTP upgrades save the configuration. Tsave is a precaution.
Caution: The file you save with the Tsave command contains all the passwords in clear
text. You should move this file from the TFTP directory to a secure location after the
upgrade procedure is complete.
tloadcode hostname
filenamet.m40 into flash from the machine tftp-server.:
tloadcode tftp-server t.m40
Caution: You must use the Fsave command immediately after executing the Tload
command. Failure to do so can cause your Ascend unit to lose its configuration.
fsave
nvramclearAfter the Ascend unit clears NVRAM memory, it automatically resets.
Upgrading system software with a fat or thin load
Upgrading to a fat or thin load is not difficult, but you must be careful to follow the correct sequence of tasks.
Caution: If you are upgrading from software version 4.6C or earlier, see "Upgrading system
software from versions earlier than 4.6C to version 5.0A or above" on page C-11 for important
information before upgrading.
Caution: If possible, you should stay with the same build when upgrading. Loading a
different build can cause your Ascend unit to lose all or part of its configuration. If this
happens, you must restore your configuration from a backup.
For example, if you are upgrading a MAX 4000 to 5.0Ai13 fat load (such as
tbim.m40), obtain a thin load of the same build (such as 5.0A tbim.m40). Note: Newer Pipeline 50 or 75 units do not have fat or thin loads, you only need to load a single software binary. Refer to
/pub/Software-Releases/Pipeline/Upgrade-Filenames.txt on the
Ascend FTP site to determine if you have a new Pipeline 50 or 75 unit.
Esc [ Esc = > prompt, use the Tsave command to save your configuration, as in the following example:
> tsave tftp-server router1.cfgThis saves the configuration of your unit to the file named
router1.cfg in the TFTP home directory of the server named tftp-server. This file must already exist and be writable. Normally, TFTP upgrades save the configuration. Tsave is a precaution.
Caution: The file you save with the Tsave command contains all the passwords in clear
text. You should move this file from the TFTP directory to a secure location after the
upgrade procedure is complete.
> prompt, enter:
> tloadcode hostname filename
Caution: If you are upgrading from a standard load to a fat load, make sure you load a
thin load first.
For example, the command:
> tloadcode tftp-server t.m40loads
t.m40 into flash from the machine named tftp-server.
Caution: You must use the Fsave command immediately after executing the Tload
command. Failure to do so may cause your Ascend unit to lose its configuration.
fsave
nvramclearAfter the Ascend unit clears NVRAM memory, it automatically resets.
UART initialized
thin load: inflate ...........................................................
starting system...
UART initializedThis completes the upgrade if you have no errors. If the upgrade is not successful, refer to "Recovering from a failed fat load upgrade" next.
fat load: inflate ............................................................
starting system...
UART initializedImmediately after this message appears, the serial console speed is switched to 57600 bps, and the Ascend unit initiates an Xmodem serial download. To recover from this error and load the fat system, you must first load a thin system that is fat-load aware. Proceed as follows:
fat load: bad CRC!!
forcing serial download at 57600 bps
please download a "thin" system...
> tload 192.168.1.82 tbam.m40The "fat load part n:" messages notify you when the first and second halves of the download begin.
saving config to flash
........................................
loading code from 192.168.1.82:69
file tbam.m40..
fat load part 1:
........................................................................
fat load part 2:
..................................................
Upgrading system software with an extended load
Your first upgrade to an extended load requires a preliminary procedure. You must first upgrade to a restricted load. A restricted load only contains essential system software and is not meant to be run in a working environment. It does not have full functionality and is to be used only to upload to an extended load.
Warning: You cannot upgrade to extended loads using an IP over X.25 connection because
restricted loads do not have X.25 support.
Caution: If you are upgrading from software version 4.6C or earlier, see "Upgrading system
software from versions earlier than 4.6C to version 5.0A or above" on page C-11 for important
information before upgrading.
Extended loads are denoted by an "f" preceding the build filename.
For example, if you are upgrading a MAX 4000 to an extended load (such as
ftbam.m40), obtain a MAX 4000 restricted load (such as rtbam.m40).
Esc [ Esc = > prompt, use the Tsave command to save your configuration, as in the following example:
> tsave tftp-server router1.cfgThis saves the configuration of your unit to the file named
router1.cfg in the TFTP home directory of the server named tftp-server. This file must already exist and be writable. Normally, TFTP upgrades save the configuration. Tsave is a precaution.
Caution: The file you save with the Tsave command contains all the passwords in
clear text. You should move this file from the TFTP directory to a secure location after the
upgrade procedure is complete.
> prompt, enter:
tloadcode hostname filenamewhere hostname is the name or IP address of your TFTP server, and filename is the name of the system software on the server (relative to the TFTP home directory).
Caution: If you want to upgrade your system for the first time to a software version 6.0.0 or
later, you must first upgrade your system to a restricted load. Failure to do so can cause your
Ascend unit to lose its configuration.
For example, the command:
loads the restricted loadtloadcode tftp-server rtbam.m40
rtbam.m40 into flash from the machine named tftp-server.
Caution: You must use the Fsave command immediately after executing the Tload
command. Failure to do so can cause your Ascend unit to lose its configuration.
fsave
nvramclearAfter the Ascend unit clears NVRAM memory, it automatically resets.
If you have loaded a restricted load, your system boots up in restricted mode. Restricted mode only allows you to load software. You cannot change or save profiles. While in restricted mode, the Edit menu displays the following banner:
* * RESTRICTED MODE * * * If your system boots up in restricted mode, perform the following steps:
> prompt, enter:
tloadcode hostname filenamewhere hostname is the name or IP address of your TFTP server, and filename is the name of the extended load of system software on the server (relative to the TFTP home directory).
For example, the command:
tloadcode tftp-server ftbam.m40loads the extended load
ftbam.m40 into flash from the machine named tftp-server.
nvramclearAfter the Ascend unit clears NVRAM memory, it automatically resets.
Upgrading system software from versions earlier than 4.6C to version 5.0A or above
If you are upgrading from software version 4.6C or earlier to version 5.0A or later, perform the upgrade in the following order:
Caution: Failure to follow this procedure might cause your Ascend unit to lose or corrupt its
configuration, and could render the unit unusable.
Using the serial port to upgrade to a standard or a thin load
Caution: Uploading system software via the serial console overwrites all existing profiles.
Save your current profiles settings to your hard disk before you begin upgrading system
software. After the upgrade, restore your profiles from the backup file you created. Since the
backup file is readable text, you can reenter the settings through the Ascend unit's user
interface. To avoid having existing profiles overwritten, use TFTP to upgrade your unit.
Caution: You cannot upload a fat load or an extended load using the serial port; it must be
done using TFTP.
Caution: If you use a Windows-based terminal emulator such as Windows Terminal or
HyperTerminal, disable any screen savers or other programs or applications that could
interrupt the file transfer. Failure to do so might cause the software upload to halt, and can
render the Ascend unit unusable.
You can cancel the backup process at any time by pressing Ctrl-C.
To save the Pipeline configuration (except passwords) to disk:
The following message appears:
Ready to download - type any key to start....
Rows of configuration information appear on the screen as the configuration file is downloaded to your hard disk. When the file has been saved, your communications program displays a message indicating the download is complete.
START= and other lines begin with END=. A pair of these START/STOP lines and the block of data between them constitute a profile. If a parameter in a profile is set to its default value, it does not appear. In fact, you can have profiles with all parameters at their defaults, in which case the corresponding START/STOP blocks are empty. Make sure that there are no extra lines of text or characters either before START= or after END=. If there are, delete them. They could cause problems when you try to upload the file to the Ascend unit.
Esc [ Esc -(Press the Escape key, the Left Bracket key, the Escape key, and the Minus key, in that order, in rapid succession.) The following string of Xmodem control characters appears:CKCKCKCK
If the upload fails during the transfer, try downloading another copy of the binary image from the Ascend FTP server and re-loading the code to the Ascend unit. If you still have problems, contact Ascend technical support for assistance.
To restore the configuration, you must have administrative privileges that include Field Service (such as the Full Access profile, for example). You use the Restore Cfg command to restore a full configuration that you saved by using the Save Cfg command, or to upload more specific configuration information obtained from Ascend (for example, a single filter stored in a special configuration file).
Esc [ Esc = > prompt, enter the Fclear command:
>fclear
> prompt, enter the NVRAMClear command:
>This causes the system to reset. When it comes back up, proceed with restoring your configuration.nvramclear
quit to exit the Diagnostic interface.
The following message appears:
Waiting for upload data...
When the restore has been completed, the following message appears:
Restore complete - type any key to return to menu
After upgrading you may have to re-enter all the passwords on your system. If you edit your saved configuration file, however, and enter passwords in the appropriate fields (by replacing the word *SECURE* in each instance), these passwords will be restored. But note that if you do choose to edit your configuration file, you must save it as text only or you will not be able to load it into your unit.
If you restored a complete configuration, the passwords used in your Security profiles have been wiped out. To reset them:
Changing to system software that does not support V.90
If the software version on the MAX supports Rockwell V.90 code, the default value for the Ethernet > Mod Config > TServ Options > MDM Modulation parameter is V.90. If you downgrade to a software version on the MAX that does not support Rockwell V.90 code, you must set the MDM Modulation parameter to either K56 or V.34. In general, if you downgrade to older software versions and need to restore a configuration, you must originally have saved the configuration from a MAX running the older version of code.
System messages
Table C-3 explains the messages that can appear during your upgrade.
Copyright © 1998, Ascend Communications, Inc. All rights reserved.