
4-2
MAX Administration Guide
Changing System Software Versions
Preparing to change system software
Preparing to change system software
As you prepare to change the system software on a MAX unit, you must verify that Field
Service and Operations are enabled on the unit. When upgrading, try to stay with the same
build. But you can use an alternative build to avoid having to add memory. You can use the
memory provided by a MAX 6000 unit’s external PCMCIA card as you change system
software. No additional memory is required on a MAX 3000 or MAX 800 units.
Enabling Field Service and Operations parameters
The Field Service parameter, in the Security profile, enables or disables permission to perform
Lucent-specific field service operations, such as changing the operating system software on a
MAX unit. The Field Service parameter is not applicable if the Operations parameter, also in
the Security profile, is set to
No
. Before you begin the process of changing the unit’s version of
TAOS, make sure that both parameters are set to Yes in the administrating Security profile. For
example, the following Full Access security profile of a MAX 800 unit is correctly configured
to support a change of operating system software:
00-300 Security
00-303 Full Access
>Name=Full Access
Passwd=*SECURE*
Operations=Yes
Edit Security=Yes
Edit System=Yes
Field Service=Yes
Staying with the same software build
When a particular build of the system software is updated, it retains the same filename. If
possible, you should always stay with the same build when you upgrade or downgrade. If you
install a different build, your unit can lose its configuration. If this happens, you might need to
manually restore your configuration. There can be no automated way to restore configuration
data from a backup when changing builds since, if the file formats between the builds are
incompatible, no suitable backup exists. For example, your MAX unit might have a T1
interface. If you are attempting to transfer a build that is appropriate for an E1 interface, the
unit can display the following message:
This load appears not to support your network interface.
Download aborted. Use
tloadcode -f
to force.
If this happens, verify that you have selected the correct build. If the build is intended for
another type of unit, that you forcing the download is not recommended.
Alternative builds for a MAX 6000 unit
With two exceptions, the builds you can use to upgrade to TAOS 9.0 require additional flash
memory, which is available to the MAX 6000 unit only, by way of an external PCMCIA flash
card. (The builds for MAX 3000 and MAX 800 units do not require any additional flash