#

# Upgrading System Software

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.

This appendix explains how to upgrade your system software. It covers the following topics

Definitions and terms
Guidelines for upgrading system software
Guidelines for downgrading system software
Before you begin
Upgrading system software with a standard load
Upgrading system software with a fat or thin load
Upgrading system software with an extended load
Upgrading system software from versions earlier than 4.6C to version 5.0A or above
Using the serial port to upgrade to a standard or a thin load
Changing to system software that does not support V.90
System messages

:

## Definitions and terms

This appendix uses the following terms:

Build | The name of the software binary. For example, `ti.m40` is the MAX 4000 T1 IP-only software build. For the names of all the software builds and the features they provide see `/pub/Software-Releases/Max/Upgrade-Filenames.txt` on the Ascend FTP server. If possible, you should stay with the same build when upgrading. Loading a different build can cause your Ascend unit to lose its all or part of its configuration. If this happens, you must restore your configuration from a backup.
Standard load | Software versions 4.6Ci18 or earlier and all 4.6Cp releases. You can load these versions of software through the serial port or by using TFTP. TFTP is the recommended upgrade method for standard loads.
Fat load | 4.6Ci19 to 5.0Aix and all 5.0Ap releases with a file size greater than 960 KB (for MAX units) or 448K (for Pipeline units). Before upgrading to a fat load for the first time, you must upgrade to a thin load. You must use TFTP to upgrade to fat loads.
Thin load | 4.6Ci19 to 5.0Aix and all 5.0Ap releases with a file size less than 960 KB (for MAX units) or 448 KB (for Pipeline units). TFTP is the recommended upgrade method for thin loads.
Restricted load | 6.0.0 or later MAX release denoted by an "r" preceding the build name. For example, rti.m40 is the restricted load for the MAX 4000 T1 IP-only software build. Before upgrading to an extended load for the first time, you must upgrade to a restricted load. Note that after you have upgraded your system to version 6.0.0 or above, you do not need to use a restricted load to upgrade. 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. Restricted loads do allow you to access the unit via Telnet. TFTP is the recommended upgrade method for restricted loads. Pipeline releases do not have restricted loads.
Extended load | 6.0.0 or later MAX release denoted by an "f" preceding the build name. You must use TFTP to upgrade to extended loads. For example, `fti.m40` is the extended load for the MAX 4000 T1 IP-only software build. MAX 6000 and Pipeline releases do not have extended loads.

## Guidelines for upgrading system software

Caution: Before upgrading, consider the following very important guidelines:

- Use TFTP to upgrade if possible. TFTP is more reliable and saves the Ascend unit configuration when you upgrade.

- You cannot load a fat load or an extended load through the serial port. You must use TFTP.

- If you are using TFTP to upgrade your software, use the `fsave` command immediately after executing the `tload` command. Failure to do so might cause your Ascend unit to lose its configuration.

- If possible, you should always stay with the same build of software when you upgrade. If you load a different version, your Ascend unit may lose its configuration. If this happens, you must restore your configuration from a backup.

- If you are upgrading to a software version 5.0A or 5.0Aix fat load for the first time, you must be on a load that supports the fat load format. All versions of software 5.0A or above support fat loads. You should perform the upgrade in two steps:

  - Upgrade to a thin load of the same build

  - Upgrade to the fat load

- If you are upgrading to a software version 6.0.0 or above, you must be on a load that supports the extended load format. All versions of software 6.0.0 or above support extended loads. You should perform the upgrade in two steps:

  - Upgrade to a restricted load of the same build

  - Upgrade to the extended load

- The MAX 6000 does not have extended or restricted loads.

- After you have upgraded your system to version 6.0.0 or above, you do not need to use a restricted load to upgrade.

- You can upgrade to a thin load or a restricted load from any version of software.

- If you are upgrading from software version 4.6C or earlier to software version 5.0A or later, see Upgrading system software from versions earlier than 4.6C to version 5.0A or above for important information before you start.

Table 6-1 explains where to find the information you need to upgrade your unit.

Table 6-1. Ascend system software versions

#### Version you are upgrading to

#### Use the instructions in...

Standard load
(4.6Ci18 or earlier and all 4.6Cp releases)

Upgrading system software with a standard load.

Fat or thin load
(4.6Ci19 to 5.0Aix and all 5.0Ap releases)

Upgrading system software with a fat or thin load.

Extended load
(6.0.0 or later)

Upgrading system software with an extended load.

## 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.

When you downgrade to older versions of software, the configuration might not upload completely, because older software does not support the parameters that might be in configuration files from newer releases.

You must upload a configuration that was saved from the same version of software to make sure that the MAX receives a complete configuration. If you upload a configuration from a newer version of software, you should check all parameter values to verify they are configured accurately.

If you are downgrading system software, make sure that you have a configuration saved from a MAX running with the older software and that you have console access to the MAX. Then, proceed as follows:

1. Use TFTP to load the system software.

2. Enter FCLEAR which clears the MAX unit's flash memory.

3. Enter NVRAMCLEAR which clears the MAX unit's main configuration and resets the MAX.

   The MAX restarts and loads the older version of system software.

4. When the MAX is up, manually enter basic information being sure to include at least IP address, subnet mask, and default gateway to the Ethernet interface.

   After entering you must be able to telnet to the MAX.

5. From the MAX unit's VT100 interface, access the diagnostics monitor by typing the following characters in rapid succession:

       Esc [ Esc =

   Or, press Ctrl-D to invoke the DO menu and select D=Diagnostics.

6. At the `>` prompt, use the TRestore command to restore the configuration as in the following example:

       > trestore tftp-server router1.cfg

   This restores the configuration named `router1.cfg` from the TFTP home directory of the server named `tftp-server`. This file must exist and be readable.

7. At the `>` prompt, enter Exit to return to the VT100 interface.

## Before you begin

Make sure you perform all the tasks explained in Table 6-2 before upgrading your software.

Table 6-2. Before upgrading

#### Task

#### Description

If necessary, activate a Security Profile that allows for field upgrade.

If you are not sure how, see the section about Security Profiles in your documentation.

Record all of the passwords you want to retain, and save your Ascend unit's current configuration to your computer's hard disk.

For security reasons, passwords are not written to configuration files created through the serial console. A configuration file created using the Tsave command, however, does contain the system passwords. You can restore the Tsave configuration file using the serial console. If you chose to save your configuration using the serial console, you will have to restore your passwords manually. Restoring passwords is explained in Using the serial port to upgrade to a standard or a thin load.

Obtain the correct file, either by downloading it from the FTP server or by requesting it from Ascend technical support.

To ensure that you load the correct software binary, you should check the load currently installed on your unit. To do so:

1. Tab over to the 00-100 Sys Options window.

2. Press Enter to open the Sys Options menu.

3. Using the Down-Arrow key (or Ctrl- N), scroll down until you see a line similar to the following:

       Load: tb.m40

4. When upgrading, obtain the file with same name from the Ascend FTP site.

If your unit does not display the current load or you are unsure about which load to use, contact technical support.

If you are upgrading to a fat load or an extended load for the first time, you must also obtain a thin load or a restricted load of the same build, if possible.

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`).

If you are upgrading to a MAX 6.0.0 extended load, obtain a 6.0.0 restricted load. Restricted loads are designated with an "r" in the load name. (For example `rtbam.m40` is a restricted load). Note that after you have upgraded your system to version 6.0.0 or above, you do not need to use a restricted load to upgrade.

Newer Pipeline 50 or 75 units do not have fat loads and no Pipeline units have extended or restricted loads. Refer to `/pub/Software-Releases/Pipeline/Upgrade-Filenames.txt` to determine if you have a new Pipeline 50 or 75 unit.

If you are using TFTP, make sure you load the correct binaries into the TFTP home directory on the TFTP server.

You must use TFTP to upgrade to a fat load or an extended load.

If you are using the serial port, make sure you have a reliable terminal emulation program, such as Procomm Plus.

If you use the serial port, you can only upgrade to a standard or a thin load. Upgrading through the serial port is not recommended.

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.

## 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.

### 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.

To upgrade to a standard load via TFTP:

1. Obtain the software version you want to upgrade to and place it in the TFTP server home directory.

2. From the Ascend unit's VT100 interface, access the diagnostics monitor by typing the following characters in rapid succession:

   `Esc [ Esc =`

   Or, press Ctrl-D to invoke the DO menu and select D=Diagnostics.

3. At the `>` prompt, use the Tsave command to save your configuration as in the following example:

   `>``tsave tftp-server router1.cfg`

   This 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.

1. Enter the following command:

tloadcode hostname `filename`

where 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).

For example, the command:

    tloadcode tftp-server t.m40

loads `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 can cause your Ascend unit to lose its configuration.

1. Enter the following command to save your configuration to flash memory:

    fsave

2. Enter the following command:

    nvramclear

After the Ascend unit clears NVRAM memory, it automatically resets.

This completes the upgrade.

## 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 for important information before upgrading.

To upgrade your system:

1. Obtain the software version binary you want to upgrade to and place it in the TFTP server home directory. If you are upgrading to a fat load for the first time, also obtain a thin load of the same build and place it in the same directory. (See page Definitions and terms for an explanation of fat and thin loads.)

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.

1. From the Ascend unit's VT100 interface, access the diagnostics monitor by typing the following characters in rapid succession:

`Esc [ Esc =`

Or, press Ctrl-D to invoke the DO menu and select D=Diagnostics.

2. At the `>` prompt, use the Tsave command to save your configuration, as in the following example:

       > tsave tftp-server router1.cfg

   This 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.

1. At the `>` prompt, enter:

`> tloadcode` hostname filename

where 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 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.m40

loads `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.

1. Enter the following command to save your configuration to flash memory:

    fsave

2. Enter the following command:

    nvramclear

After the Ascend unit clears NVRAM memory, it automatically resets.

3. If you are upgrading to a thin load, you are done. If you are upgrading to a fat load, repeat the procedure, this time uploading the fat load binary.

After a successful upgrade, one of the following messages appears.

- If the load is thin:

      UART initialized
      thin load: inflate ...........................................................
      starting system...

- If the load is fat:

      UART initialized
      fat load: inflate ............................................................
      starting system...

This completes the upgrade if you have no errors. If the upgrade is not successful, refer to "Recovering from a failed fat load upgrade" next.

### Recovering from a failed fat load upgrade

If a fat load has a CRC (cyclic redundancy check) error, the following message appears:

    UART initialized
    fat load: bad CRC!!
    forcing serial download at 57600 bps
    please download a "thin" system...

Immediately 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:

1. Activate your Xmodem software.

2. After you have finished loading the fat-aware thin load, reboot the unit.

3. Use the Tload command to download the fat load.

   When you download a fat load, messages similar to the following appear on the diagnostics monitor screen:

       > tload 192.168.1.82 tbam.m40
       saving config to flash
       ........................................
       loading code from 192.168.1.82:69
       file tbam.m40..
       fat load part 1:
       ........................................................................
       fat load part 2:
       ..................................................

   The "fat load part n:" messages notify you when the first and second halves of the download begin.

## 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.

After you have upgraded your system to version 6.0.0 or above, you do not need to use a restricted load to upgrade. Note that the MAX 6000 and Pipeline units do not have extended loads.

units

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 for important information before upgrading.

To upgrade your system:

1. Obtain the software-version binary you want to upgrade to and place it in the TFTP server home directory.

Extended loads are denoted by an "f" preceding the build filename.

2. If this is the first time you have upgraded to an extended load, obtain a restricted load of the same build and place it in the directory.

   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`).

3. From the Ascend unit's VT100 interface, access the diagnostics monitor by typing the following characters in rapid succession:

   `Esc [ Esc =`

   Or, press Ctrl-D to invoke the DO menu, and select D=Diagnostics.

4. At the `>` prompt, use the `Tsave` command to save your configuration, as in the following example:

       > tsave tftp-server router1.cfg

   This 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.

1. At the `>` prompt, enter:

    tloadcode hostname filename

where 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:

    tloadcode tftp-server rtbam.m40

loads the restricted load `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.

1. Enter the following command to save your configuration to flash memory:

    fsave

2. Enter the following command:

    nvramclear

After the Ascend unit clears NVRAM memory, it automatically resets.

If you have downloaded the extended load, the upgrade is complete.

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:

1. At the `>` prompt, enter:

tloadcode hostname filename

where 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.m40

loads the extended load `ftbam.m40` into flash from the machine named `tftp-server`.

2. Enter the following command:

    nvramclear

After the Ascend unit clears NVRAM memory, it automatically resets.

Your system will then boot up with the new version of software running.

## 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:

1. Load version 4.6Ci18, following the procedure in Upgrading system software with a standard load.

2. Load version 5.0A, following the procedure in Upgrading system software with a fat or thin load.

3. Load version 5.0Aix or 6.0.0, following the procedure in Upgrading system software with a fat or thin load (for software versions 5.0Aix) or Upgrading system software with an extended load (for software version 6.0.0).

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.

Upgrading through the serial port consists of the following general steps:

- Saving your configuration

- Uploading the software

- Restoring the configuration

#### Before you begin

Before upgrading your system through the serial port, make sure you have the following equipment and software:

- An IBM compatible PC or Macintosh with a serial port capable of connecting to the Ascend unit's Console port.

- A straight-through serial cable.

- Data communications software for your PC or Mac with XModem CRC/1K support (for example, Procomm Plus, HyperTerminal for PCs or ZTerm for the Mac).

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.

#### Saving your configuration

Before you start, verify that your terminal emulation program has a disk capture feature. Disk capture allows your emulator to capture to disk the ASCII characters it receives at its serial port. You should also verify that the data rate of your terminal emulation program is set to the same rate as the Term Rate parameter in the System Profile (Sys Config menu).

You can cancel the backup process at any time by pressing Ctrl-C.

To save the Pipeline configuration (except passwords) to disk:

1. Open the Sys Diag menu.

2. Select Save Config, and press Enter.

   The following message appears:

   `Ready to download - type any key to start....`

3. Turn on the Capture feature of your communications program, and supply a filename for the saved profiles. (Consult the documentation for your communications program if you have any questions about how to turn on the Capture feature.)

4. Press any key to start saving your configured profiles.

   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.

5. Turn off the Capture feature of your communications program.

6. Print a copy of your configured profiles for later reference.

You should examine the saved configuration file. Notice that some of the lines begin with `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.

#### Uploading the software

To upload the software:

1. Type the following four-key sequence in rapid succession (press each key in the sequence shown, one after the other, as quickly as possible):

`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 you do not see these characters, you probably did not press the four-key sequence quickly enough. Try again. Most people use both hands and keep one finger on the escape key.

2. Use the Xmodem file-transfer protocol to send the system file to the Ascend unit.

   Your communications program normally takes anywhere from 5 to 15 minutes to send the file to your Ascend unit. The time displayed on the screen does not represent real time. Do not worry if your communication program displays several "bad batch" messages. This is normal.

After the upload, the Ascend unit resets. Upon completion of the self-test, the Ascend unit's initial menu appears in the Edit window with all parameters set to default values. This completes the upgrade.

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.

#### Restoring the configuration

Under certain circumstances, the serial-port method might not completely restore your configuration. You should therefore verify that your configuration was properly restored every time you use this method. If you have many profiles and passwords, you should consider using TFTP to upgrade your software. (See Using TFTP to upgrade to a standard load.)

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).

To load configuration information through the serial port

1. From the Ascend unit's VT100 interface, access the diagnostics monitor by typing the following characters in rapid succession:

`Esc [ Esc =`

Or, press Ctrl-D to invoke the DO menu, and select D=Diagnostics.

2. At the `>` prompt, enter the Fclear command:

       > fclear

3. At the `>` prompt, enter the NVRAMClear command:

       > nvramclear

   This causes the system to reset. When it comes back up, proceed with restoring your configuration.

4. Enter `quit` to exit the Diagnostic interface.

5. Open the Sys Diag menu.

6. Select Restore Cfg, and press Enter.

   The following message appears:

       Waiting for upload data...

7. Use the Send ASCII File feature of the communications software to send the configuration file to the unit. (If you have any questions about how to send an ASCII file, consult the documentation for your communications program.)

   When the restore has been completed, the following message appears:

       Restore complete - type any key to return to menu

8. Press any key to return to the configuration menus.

9. Reset the Ascend unit, by selecting System > Sys Diag > Sys Reset and confirming the reset.

#### Restoring passwords

For security reasons, passwords are not written to configuration files created through the serial console. A configuration file created using the Tsave command, however, does contain the system passwords. You can restore the Tsave configuration file using the serial console.

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:

1. Press Ctrl-D to invoke the DO menu, select Password, and choose the Full Access profile.

2. When you are prompted to enter the password, press Enter (the null password).

   After you have restored your privileges by entering the null password, you should immediately open the Connection profiles, Security profiles, and Ethernet profile (Mod Config menu), and reset the passwords to their previous values.

## 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 paramater 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 6-3 explains the messages that can appear during your upgrade.

Table 6-3. System software messages

#### Message

#### Explanation

    UART initialized

    fat load: bad CRC!!

    forcing serial download at 57600 bps

    please download a "thin" system...

The fat load has a CRC (cyclic redundancy check) error. Immediately after this message appears, the serial console speed is switched to 57600 bps, and the Ascend unit initiates an Xmodem serial download. Load a thin load that understand the fat load format, as explained in Upgrading system software with a fat or thin load.

    File tbam.m40

    incompatible fat load
    format--discarding downloaded data

You attempted to upgrade to a fat load from a version of system software that does not understand the fat load format. You must first load a thin load that is fat load aware, as explained in Upgrading system software with a fat or thin load.

    This load has no platform identifier.
    Proceed with caution.

This message can occur if you are running software version 5.0Ai11 or later and you load an earlier incremental or patch release onto your system. The message indicates that Tloadcode cannot determine which platform the code is intended for. If you are using the correct software version, you can ignore this message.

    This load appears not to support your
    network interface.

    Download aborted.  Use \Qtloadcode -f'
    to force.

Indicates you are attempting to load a version of code intended for a different network interface (for example, loading MAX 4000 T1 software onto a MAX 4000 E1 unit).

    This load appears to be for another
    platform.

    Download aborted.  Use \Qtloadcode -f'
    to force.

Indicates you are attempting to load a version of code onto a platform for which it is not intended (for example, loading MAX 4000 software onto a MAX 2000). This is not recommended

    UART initialized

    fat load: inflate
    ......................................
    ......................

    starting system...

Indicates you have successfully loaded a fat load.

    UART initialized

    extended load:

    inflate essential
    .+.+................................

    invalid CRC!!

    entering restricted mode

    starting system...

Indicates the extended load has failed and that your system is being brought up in restricted mode. You must reload the software as explained in Upgrading system software with an extended load.

    UART initialized

    extended load:

    inflate essential
    .+.+..................................
    .

    invalid length!!

    entering restricted mode

    starting system...

Indicates the extended load has failed and that your system is being brought up in restricted mode. You must reload the software as explained in Upgrading system software with an extended load.

    UART initialized

    extended load:

    inflate essential .+.+...............

    inflate expendable..............|....

    starting system...

Indicates you have successfully loaded an extended load.

    UART initialized

    thin load: inflate
    ......................................
    .....................

    starting system...

Indicates you have successfully loaded a thin load.

Copyright © 1998, Ascend Communications, Inc. All rights reserved.