User Manual

ADCP-75-192 • Issue 1 • December 2005 • Section 5: Software Updates
Page 5-1
2005, ADC Telecommunications, Inc.
SECTION 5: SOFTWARE UPDATES
Content Page
1 SOFTWARE RELEASE DELIVERABLE ....................................................... 5-1
2 RELEASE NOTES .................................................................... 5-1
3 UPGRADING EXISTING SYSTEM.......................................................... 5-2
3.1 Preliminary Steps ............................................................. 5-2
3.2 Upgrade Steps ............................................................... 5-2
4 VERIFICATION ..................................................................... 5-3
5 FAILED UPGRADES .................................................................. 5-4
6 FPGA UPDATES .................................................................... 5-5
7 BACKUP/RESTORE .................................................................. 5-5
7.1 Backup .................................................................... 5-5
7.2 Restore .................................................................... 5-5
7.3 Adding/Removing SNMP Traps..................................................... 5-6
8 UPDATING SPARE CPUS............................................................... 5-6
9 MIB EXTRACTION ................................................................... 5-7
1 SOFTWARE RELEASE DELIVERABLE
The ADC software upgrade process is based on packaging utilities built into the Linux-based
operating system used by ADC. The software upgrade is a set of interdependent packages
delivered in a self-extracting executable named so as to reflect the revision of the contained
software; for example: hr-3.2.0-upgrade would be used to upgrade a target Hub or RAN CPU
to version 3.1.0. When invoked, the upgrade executable will automatically take the appropriate
actions to upgrade the target CPU.
2 RELEASE NOTES
The release notes delivered with each software release distribution will contain specific details
about the changes being made in that software release. The release notes will itemize each
change made, including a description of the problem/issue being addressed, a description of
how the problem/issue was resolved, and the impact of the change on the NMS.
Included in the release notes are details of any upgrades to the FPGA images, including
revision number information contained in the latest release build. To ensure the latest
documentation matches the current packaged images, the release notes will be the only place
where this information is captured in external/customer documentation.
Also included are the steps needed to complete the upgrade.