Specifications

A-24
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide
Release 3, Part Number 78-14788-01 Rev. C0, January 2004
Appendix A Downloading and Installing Software Upgrades
Upgrade Procedures for PXM45, AXSM, and FRSM-12 Cards
Loading the Runtime Upgrade Software
This section describes how to load the runtime upgrade software in preparation for running it. Production
switches should have redundant cards installed, so that upgrades can occur without interrupting traffic.
For graceful upgrades, the upgrade software is loaded on the standby card first, and then the control is
switched to upgraded card so that the other card can be upgraded. The best way to assess the upgrade
status of a card is to enter the dspcd <slot> command. For example:
8850_NY.7.PXM.a > dspcd
8850_NY System Rev: 02.01 Mar. 04, 2001 22:47:23 PST
MGX8850 Node Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SBK050302AF SBK045203PJ SBK044602HJ
Prim SW Rev: 2.1(0) --- ---
Sec SW Rev: 2.1(0) --- ---
Cur SW Rev: 2.1(0) --- ---
Boot FW Rev: 3.0(0.0) --- ---
800-level Rev: A0 A0 A0
800-level Part#: 800-06147-08 800-05787-02 800-05052-04
CLEI Code: BAA670YCAA BA7IBCLAAA BA7IADNAAA
Reset Reason: On Power up
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
The primary (Prim SW Rev), secondary (Sec SW Rev), and current (Cur SW Rev) software revision
labels indicate the status of an upgrade. In this example, these numbers match because the runtime
software upgrade has not started. (Note that the boot software has been upgraded as indicated by the Boot
FW Rev label.)
The primary software revision indicates which revision a card will run if it becomes active, and the
secondary revision indicates an alternate revision that the card will use if the abortrev command is
entered. (For more information on aborting an upgrade, see the “Aborting a Runtime Software
Upgrade”section, which appears later in this appendix.) The current software revision represents the
software the active card is using.
The normal sequence of commands for a runtime software upgrade is loadrev, runrev, and commitrev.
Table A-2 shows how the software revision levels change during a graceful runtime software upgrade
Table A-2 Software Versions Reported During Graceful Upgrades
Software
Revision
Before Upgrade After loadrev After runrev After commitrev
Slot 7 Slot 8 Slot 7 Slot 8 Slot 7 Slot 8 Slot 7 Slot 8
Active Standby Active Standby Standby Active Active Standby
Primary 2.1(0) 2.1(0)) 2.1(0) 2.1(0) 3.0(0.0) 3.0(0.0) 3.0(0.0) 3.0(0.0)
Secondary 2.1(0) 2.1(0) 3.0(0.0) 3.0(0.0) 2.1(0) 2.1(0) 3.0(0.0) 3.0(0.0)
Current 2.1(0) 2.1(0) 2.1(0) 3.0(0.0) 3.0(0.0) 3.0(0.0) 3.0(0.0) 3.0(0.0)