Filter
Top Products
ADCP-75-192 • Issue 2 • June 2007
Page 54
© 2007, ADC Telecommunications, Inc.
After completing the desired number of lines, finish by entering two blank lines and then a
Ctrl-D.
To remove a trap-sink, do as above except at the prompt for input (‘>’), enter:
update delete version-trap-sink.domain A address
4.5 Updating Spare CPUs
There are times when it is desirable to update the software on a spare CPU. The general
approach for updating a spare CPU is to install the CPU into an available chassis that is
connected to the network and execute the upgrade steps detailed in the previous section above.
The software upgrade process associated with upgrading a spare CPU is exactly as described in
the “Upgrading Existing System” section above. The only difference between upgrading a spare
CPU and an existing system is that a physical location for upgrading the spare CPU must be
determined.
There are a few ways to make a CPU chassis slot available:
• Each digital chassis in the Hub supports two CPUs - it is possible that one of the installed
Hub digital chassis is only half-populated and contains an available CPU slot. This note is
only applicable to Generation 1 Hubs, since Generation 2 Hub chassis only contain one
CPU.
• Unplug a CPU that resides in the existing fielded system and replace it (temporarily) with
the spare CPU. When finished upgrading the spare CPU, return the original CPU to that
slot in the chassis.
• Dedicate a chassis to be used strictly for this type of update and for verification and test.
This is the recommended option for CPUs not slated for immediate installation.
• There are limitations with this type of update that need to be observed:
• It is important that all Hub/RAN CPUs that reside on the same network are able to
communicate with their Hub Master. Therefore, if the spare CPU is too far outdated, this
may not be possible. In order to avoid a conflict, it is only possible to update a spare CPU
on the fielded system network if the current major version of the spare CPU is the same as
that of the CPUs in the fielded system. For example, if all the CPUs in the fielded system
are currently at revision 2.2.0 and the spare CPU is at 2.0.0, it is possible to update that
CPU with the method described above. However, if the spare CPU in this example is at
1.7.0, it is not possible. This implies that if an ADC software release is of a new major
revision, spare CPUs in stock need to be upgraded at the same time as all of the other
CPUs in the fielded system.