Table of Contents
Advertisement
Hosted system upgrades that include bootloader code
If the new software version requires an upgrade of both the operational code and the
bootloader, then in addition to loading the operational code, you must load both the
host bootloader and Compact Remote bootloader to host flash. Because the host and
the Compact Remote are different types of systems, they cannot share bootloader
code.
For example, the following commands load the required software to host flash from a
TFTP server on the network (10.5.63.145 in this example):
1
Load the new operational code to host flash:
HOST> load tar network 10.5.63.145 stgrel.tar
2
Load the new host bootloader to host flash:
HOST> load boot-cm network 10.5.63.145 stgcmb2.bin
3
Load the Compact Remote bootloader to host flash:
HOST> load file network 10.5.63.145 crtcmb.bin
Then, before resetting the host, you must use the loadslave command to transfer the
Compact Remote bootloader (crtcmb.bin) to all remote shelves. For details about the
loadslave command, see the Stinger Reference.
After the transfer of crtcmb.bin to all remote shelves has completed, resetting the
host completes the rest of the upgrade automatically, as described in "Typical hosted
system upgrade procedure" on page 6-2.
Reset options for hosted systems
From the host, you can reset the host system only, a specific remote shelf, or the
entire hosted system. If you use the reset command with no options, the default
action is to reset all controllers in the hosted system. For example:
HOST> reset
To reset only the master controller (the controller in the host system), use the -m
option:
HOST> reset –m
To reset a specific remote shelf, use the -s option and specify the shelf's ID. For
example, the following command resets shelf 3:
HOST> reset –s 3
Monitoring remote LIMs and connections
Some Stinger administrative commands have been modified to support a
shelf-specific option, to allow you to focus on a particular remote shelf rather than
obtain a large output for all interfaces or connections in the hosted system. Where
appropriate, output of these commands now shows the shelf number, along with slot
and port.
The Stinger® Compact Remote ATM DSLAM Getting Started Guide
Hosted System Management
Monitoring remote LIMs and connections
6-3
Advertisement
Table of Contents
