
Changing System Software Versions
Using TFTP to upgrade or downgrade
MAX Administration Guide
4-3
memory.) To avoid using a PCMCIA flash card, you can upgrade a MAX 6000 unit with one of
the following two recommended builds:
•
eik.m60
(an ultrathin load for E1 environments)
•
tik.m60
(an ultrathin load for T1 environments)
In future releases, these ultrathin builds might not be available, and use of the MAX 6000
unit’s external flash memory will become a requirement. The current release includes a new
feature to prevent a build that is too large from being placed in the unit’s internal flash memory.
If a build is too large, the unit aborts the download and displays the following message:
tftp download aborted due to flash write error
The MAX unit then restarts with its previous TAOS version and configuration intact. In
releases before to TAOS 9.0, the process appeared to complete successfully although TAOS
was corrupted and the configuration unusable.
The
eik.m60
and
tik.m60
builds do not include support for the following features:
•
AppleTalk
•
BRI
•
IPX
•
PHS
•
POTS
•
X.25
For the names of all the software builds and the features they provide, see
/pub/Software-Releases/Max/Upgrade-Filenames.txt
on the Lucent
Technologies FTP server.
Using TFTP to upgrade or downgrade
If possible, use TFTP to change a MAX unit’s version of TAOS. TFTP is a more reliable way
to obtain, store, and then change the version of TAOS than is the alternative. Using TFTP, you
can use a MAX 6000 unit’s external memory to create redundant backup images, as well as to
upgrade the unit’s version of TAOS.
Creating redundant backup images for a MAX 6000 unit
MAX 6000 units now support two redundant copies of TAOS code on the PCMCIA flash
memory card. If the first version of code becomes corrupt, the unit boots up the second
version.
To create the redundant backup image, proceed as follows:
Note:
The order of these two steps is not important, but the unit will be unable to recover
from a failure in the primary code image until both steps have been executed.
1
Create a backup copy of the currently running binary on the PCMCIA flash card by using
the
fBackupImage
debug command:
> fBackupImage