Table of Contents
Advertisement
Hosted Operation of Cascaded Stinger MRT units
Hosted MRT system management
Normally, you do not need to clear the system's NVRAM for an upgrade.
However, if the upgrade requires this step, you must follow the instructions in
"Required steps before initializing NVRAM in the host" on page B-12.
A typical upgrade is described in "Automatic upgrade procedure" on page B-12.
A manual upgrade, in which you explicitly load new software to each remote
shelf, is described in "Manual upgrade via loadslave (optional procedure)" on
page B-13.
Note
This section describes general procedure and requirements.
Required steps before initializing NVRAM in the host
Before you initialize nonvolatile random-access memory in the host, you must
save basic configuration settings to the default.cfg file in the system's flash
memory, to enable the system to restore a minimal configuration. For
background information about default.cfg, see the Stinger Administration Guide.
Caution
!
information in default.cfg to allow the master controller to restore the hosted
system framework and recognize the remote shelves. Otherwise, when you load
the saved configuration file after clearing NVRAM, the host will drop connection
profiles with nailed groups that do not yet exist in the system.
To ensure that the system reestablishes all remote shelves and connections after
its NVRAM has been initialized, follow these steps:
1
2
3
4
5
Automatic upgrade procedure
A typical software upgrade modifies only the system's operational code. For this
type of upgrade, following is the general procedure for upgrading a host Stinger
and up to 5 remote shelves from a TFTP server on the network:
B-12
Always check the specific upgrade instructions for a new software version.
For a hosted system, it's very important to save enough profile
On the host, create a default.cfg file with minimal required profiles. For
example:
HOST> save flash 1/default.cfg -p remote-shelf-config system
ip-interface ip-route user
Back up the system configuration that contains connection data for remote
LIMs. For example:
HOST> save -a network 10.5.63.145 hostmrt-config-0930
Initialize NVRAM on the host.
HOST> nvram -f
After the host has reinitialized and reset, wait until it has recreated its
remote-shelf-config and slot-static-config profiles.
The slot-static-config profiles for remote LIMs are created dynamically
when the corresponding remote-shelf-config profile is written.
Restore the system configuration containing remote LIM connection data.
For example:
HOST> load config network 10.5.63.145 hostmrt-config-0930
Stinger® MRT Getting Started Guide
Advertisement
Table of Contents
