MAX Series Upgrade Instructions (Short Version)

MAX Series Upgrade Instructions (Concise Version)

Table of Contents

Abstract

Steps

Abstract

ftp://ftp.ascend.com/pub/Software-Releases/Max/Release-7.0.X/7.0.0/doc/.

Steps

Use of a TFTP (Trivial File Transfer Protocol) server is the recommended method to upgrade the MAX since TFTP is required in most cases (for extended or fat loads). Upgrading via TFTP is faster, more reliable, and allows the MAX unit to retain its configurations.

Obtain the correct MAX software binary build from ftp://ftp.ascend.com/pub/Software-Releases/Max. If you are not sure which file to download, consult the Upgrade-Filenames.txt file located in that directory.

If you are upgrading from a 4.6B or a 4.6C release to 6.0.0 or higher, you must first upgrade to a 5.0 release. Once you are on a 5.0 release, you can proceed directly to 6.0.0 or higher.

If you are upgrading from a 5.0A release to a 6.0.0 release or higher, some builds require an "r" load and an "f" load. If your build has an "r" in its file name, look for the corresponding "f" load and vice-versa. For example, if your MAX unit uses a tik.m40 build on 5.0Ap51, it will require two loads to upgrade to 6.0.0 or higher--rtik.m40 and ftik.m40. If you happen to find your required build without the "r" or "f" in the filename, then only that one file is required.
f Extended (full) Load - Complete version of code for production environments.
r Restricted Load - Bare minimum code, only used for migration from a 5.0 revision to 6.0.0 or higher. Failure to use this load will result in potential configuration loss. When in Restricted mode, T1/PRI lines (switched or nailed PPP/frame relay) and modems will be operational. All other protocols (e.g. IPX, Appletalk, X.25, SNMP, OSPF, AIM, BONDING, DHCP, COMBINET) will not be available.
Once you obtain the two files, you will need to perform the upgrade procedure twice (load the Restricted load, reset the MAX, then load the extended load). All upgrades from 6.0.0 to a higher release thereafter, only require the Extended load without the need for a Restricted load.

Place the file(s) in a known directory on your TFTP server. If you already have a path configured in your TFTP server, place the file in that directory path.

Gain access to the MAX menu screens (either via Telnet or VT100 terminal) and make sure you have proper security priveleges to perform the upgrade (such as "Full Access"). Also make sure your TFTP server can ping the MAX.

Upgrading via TFTP is done from the MAX's "Diagnostics" mode. To enter Diagnostics mode:

If you are NOT on a 5.0A release or higher (e.g. 4.6C), you must hit these four keystrokes one right after the other in rapid succession (from anywhere in the MAX menu screens):
ESC [ ESC =
These four key strokes must be entered within a one second time interval.

If you are on a 5.0A release or higher, hit CTRL D and then D for Diagnostics (from anywhere in the MAX menu screen).

When you reach Diagnostics mode, you should see a ">" prompt (to exit out of Diagnostics mode, type in the command "quit").
Proceed with the upgrade. The key command to use to perform the upgrade is "tloadcode". Here is the syntax:
```
	> tloadcode [ip address of the TFTP server] [file name]
```
Here's an example if you have placed the MAX binary file in a configured path on your TFTP server:
```
	> tloadcode 5.5.5.5 rtik.m40
```
Here's an example if your Windows based TFTP server does not have a path configured, but you have put the file in the c:\temp directory:
```
	> tloadcode 5.5.5.5 c:\temp\rtik.m40
```
Note: If going from a 5.0 release to a 6.0.0 or higher release and your MAX requires using two loads (i.e. Restricted and Extended), first load the Restricted load.
This command loads the binary software image into flash using the TFTP protocol. Although it may operate a bit slower, the MAX is fully functional during the upgrade procedure. The "tloadcode" command first perfoms an implied "fsave" (to save its configurations in its internal Flash memory), then loads the code across the network. During the transfer of the file, a series of dots is printed to indicate progress. Do not interrupt the upload process.

When the upload is complete, you will be back at the ">" prompt. At this point, type in the command...
```
	> fsave
```
...and hit RETURN. Then type in this command...
```
	> nvram
```
...and again hit RETURN.
At this point, the MAX unit will reset. If the new version of code is running, the box will restore its saved configuration from Flash. When this occurs, the MAX unit will automatically reboot a second time. This is necessary because the unit copies its stored configurations from Flash to NVRAM on the first boot, and then must reboot to initialize using the new NVRAM settings.
Important Note: After you load a restricted load and perform the "fsave" and "nvram" commands, the MAX will come back up in "Restricted Mode" (indicated on top of the Main Edit Menu window). Proceed with step 3-5 again to upload the Extended load. However, after the upload is complete, you only need to perform the "nvram" command and not the "fsave" command since "fsave" is not allowed in Restricted mode. Your MAX unit will still maintain its configurations.
ALSO REMEMBER THAT ALL SUBSEQUENT UPGRADES FROM 6.0.0 OR HIGHER DO NOT REQUIRE A RESTRICTED LOAD!