User Manual

ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates
Page 6-6
 2005, ADC Telecommunications, Inc.
3.6.2 Restore:
Again, note that a restore only needs to be performed if problems with the upgrade have been
encountered and the CPU is going to be downgraded.
Telnet to the target CPU, using operator/operate as the username/password.
Run the restore script:
sudo backup-hubmaster -r operator@<target-IP>:/var <backupname>.tar
Reboot by entering: sudo reboot
Note that the restore script is simply the backup script invoked with a "-r" switch. The "-r"
switch is identical to the switch "--restore".
4 UPDATING SPARE CPU’S
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:
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 CPU’s 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 CPU’s 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 Digivance
CXD software release is of a new major revision, spare CPU’s in stock need to be
upgraded at the same time as all of the other CPU’s in the fielded system.