User Manual

ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates
Page 5-4
 2005, ADC Telecommunications, Inc.
On the upgraded RAN CPU, verify PAs are functioning and power levels are as expected.
Refer to the above "Preliminary Steps" section for details.
5 FAILED UPGRADES
In the case of a failed upgrade, it will be desirable to attempt to return the target CPU to its
previous revision by uninstalling the most recent software upgrade. This action will be
accomplished with the use of a downgrade script that is installed as part of the upgrade. The
name of the downgrade script will contain the name of the version being downgraded to; for
example, hr-3.0.0-downgrade would be used to revert a CPU that has been upgraded to
version 3.1.0 back to 3.0.0.
Note that it is difficult to guarantee that a CPU reverted to its previous revision will work
exactly as the CPU did prior to the upgrade. There are simply too many variables to guarantee
this. The regression test cycle here at ADC will include a series of steps to validate that the
uninstall/downgrade process works, but it is extremely difficult to guarantee that all possible
failure paths will be exercised.
It is important that, upon completion of a downgrade, the verification steps described in the
previous section are taken to ensure that the CPU is left in an operational state.
6 FPGA UPDATES
Certain software releases will contain updates to the FPGA images that the ADC modules load
on startup. These FPGA image updates need to be programmed into an EEPROM on the
module(s) in question. The ADC software processes, upon detection of an out of date FPGA
image, will notify the maintainer via an ADC trap. The maintainer is responsible for
programming the EEPROM at the earliest convienence (See Reference #80-83 in Section 4).
Depending on the module(s) being updated with new FPGA images, this action could take as
long as 20-30 minutes to complete
Caution: While FGPAs are being downloaded, service will be interrupted.
7 BACKUP/RESTORE
There are several files on a hubmaster CPU being upgraded that should be backed up in case
something goes wrong with the upgrade and need to be restored. This set of files includes the
MIBmap files where MIB data is stored, as well as several system configuration files.
The upgrade executable will automatically run the backup script to take care of backing up all
key files. These files will be bundled into a file that will be stored on the CPU being upgraded,
in the /var directory. This file will be given a name that associates it with version of the
upgrade being performed, for example: backup-pre-2.1.0.tar.gz.