Non-Graceful Pxm And Service Module Runtime Software Upgrades - Cisco MGX 8850 (PXM1E/PXM45) Configuration Manual

Appendix A Downloading and Installing Software Upgrades
Command
Step 6
loadrev <slot> <revision>
dspcd
Step 7
runrev <slot> <revision>
dspcd
dspcd <slot>
Step 8
commitrev <slot> <revision>

Non-Graceful PXM and Service Module Runtime Software Upgrades

Non-graceful upgrades disrupt switch traffic and are usually used in lab installations where the use of
standalone cards provides no opportunity for a graceful upgrade. The quickstart procedure provides an
overview and quick reference for those who have already performed ungraceful upgrades on the switch.
Note If you plan to upgrade PXM cards and service modules, upgrade the PXM cards first. Wait until the PXM
cards are operating in active and standby modes with the correct software before upgrading service
modules. The software version used by the PXM cards should be equal to or later than the version used
on the service modules. When service module boot software is to be upgraded, it should be upgraded
before upgrading the runtime software.
Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost
Note
when the PXM is reset during the upgrade.
Cisco Systems recommends that you upgrade software on one service module at a time within a switch.
Note
Wait until each service module upgrade is complete before starting an upgrade on another service
module.
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Purpose
Load the new runtime software on the standby PXM or service
module.
Switch over to the standby PXM or service module and load the
new runtime software on the new standby (non-upgraded) card.
This command prevents an accidental switch back to a previous
software revision if someone enters the abortrev command.
Enter the commitrev command after the former active PXM45
comes up in the standby-U state. Cisco Systems recommends that
you avoid configuration changes until after you have run the
commitrev or abortrev commands.
See the "Aborting a Runtime Software
"Committing to a Runtime Software
which appear later in this appendix.
Quickstart Procedures for Software Upgrades
Upgrade" section and the
Upgrade" section, both of
A-9