Manualshelf

User Manual

ManualsBrandsADC Telecommunications ManualsElectronicsDigivance® CXD 1900 MHz ADB Band
101102103104105106107108109110
ADCP-75-192 • Issue D • October 2005 • Section 6: Software Updates
Page 6-3
2005, ADC Telecommunications, Inc.
3.3 Verification
It is important to be sure that the upgrade was successful before continuing on with upgrading
other CPUs in the network. Some of this verification is done automatically by the upgrade
executable, but there are certain steps that need to be done manually as well.
Actions that are automatically taken by the upgrade executable to verify success include the
following:
• Built in package management checks to be sure that files are being written and
removed as expected.
• Checks to be sure that upon completion of the upgrade, certain processes are running
(or no longer running, as the case may be) as expected.
• Test scripts being run to ensure that processes are running as expected.
If the autonomous actions taken by the upgrade executable discover that the upgrade was not
successful, the upgrade executable will report this information in the log file located at
/var/log/opencell-upgrade. Otherwise, a successful status message will be reported to that log.
Manual steps must also be taken to ensure that the upgrade process completed successfully.
Note that some of the manual validation steps below may also be performed by the automatic
validation described above.
The process list should be examined to be sure that the appropriate processes are running. This
can be done by telnetting into the target CPU (see "Upgrade Steps" section above) and
entering:
ps ax | grep "/usr/bin/”. The list that is returned will indicate all processes that were run from
the system binary directory. This list should include the following, at a minimum:
/usr/bin/pathtrace /usr/bin/rgc
/usr/bin/nodepaths /usr/bin/equipment
/usr/bin/netnode /usr/bin/stf
/usr/bin/hlpwatch /usr/bin/i2cbusscan
/usr/bin/pcibusscan /usr/bin/i2cbusmaster (6 instances)
/usr/bin/fgc /usr/bin/gps
/usr/bin/niprs (4 instances) /usr/bin/hcp
Where hcp represents the listing of all HCPs that correspond to the modules being controlled
by the target CPU. These are specific to the target CPU being upgraded and include HDC,
BIM, FSC, HUC, MUC, RUC, RDC, SIF, and RSC. There should be one instance of each
HCP per module managed by the target CPU.