Table of Contents
Advertisement
Hosted System Management
Upgrading hosted system software
To ensure that the system reestablishes all remote shelves and connections after its
NVRAM has been initialized, follow these steps:
1
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
2
Back up the system configuration that contains connection data for RLIMs. For
example:
HOST> save -a network 10.5.63.145 hostcr-config-0930
3
Initialize NVRAM on the host.
HOST> nvram -f
4
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 RLIMs are created dynamically when the
corresponding remote-shelf-config profile is written.
5
Restore the system configuration containing RLIM connection data. For example:
HOST> load config network 10.5.63.145 hostcr-config-0930
Typical hosted system upgrade procedure
Software upgrades usually do not include new bootloader code. For an upgrade that
introduces new operational code only, you can allow most of the upgrade procedure
to occur automatically between the host and remote shelves.
Following is the general procedure for loading new operational software to host flash
from a TFTP server on the network (10.5.63.145 in this example):
1
Load the new operational software to host flash:
HOST> load tar network 10.5.63.145 stgrel.tar
2
Reset the host.
HOST> reset
After you reset the host system, it communicates the version and size of its
operational code to the remote shelves. When a remote COP detects a difference
from its operational code, it downloads the new code from the host automatically.
During the download, the remote shelf COP displays a spinning clock at the console,
and a NOTICE log message is displayed on the host. All CLI downloads also are
blocked during the control channel loading from the host.
You do not need to reset each remote shelf separately. The system resets the remote
COPs automatically when you allow the hosted system to upgrade its remote shelves
automatically.
Note
Before you reset the host, you can choose to manually load operational code
to each remote shelf via the loadslave command, to slightly reduce service outage
when upgrading. For details about loadslave command usage and options, see the
Stinger Reference.
6-2
The Stinger® Compact Remote ATM DSLAM Getting Started Guide
Advertisement
Table of Contents
Need help?
Do you have a question about the Stinger Compact Remote and is the answer not in the manual?