Specifications

10-21
Cisco MGX 8800/8900 Series Software Configuration Guide
Release 5.1, Part Number OL-6482-01, Rev. A0, January 25, 2005
Chapter 10 Switch Maintenance Procedures
Replacing Cards
Upgrading Standalone Configurations
When upgrading a standalone service module to MPSM-8-T1E1, you must upgrade both the software
and the hardware. The software configuration and feature licenses remain intact during the upgrade, but
all active connections are terminated.
Tip To avoid service interruption for standalone service modules, configure card redundancy and use the
procedure in the “Replacing a Primary Card in a Redundancy Group” section that follows this section.
Step 1 If you have not done so already, upgrade the PXM software to a version that supports the MPSM software
you will be using. For more information, refer to the Release Notes for Cisco MGX 8850
(PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00.
Step 2 If you have not done so already, copy the MPSM runtime software to the switch as described in the
“Copying Software Files to the Switch” section in Appendix A, “Downloading and Installing Software
Upgrades.”
MPSM runtime files are named using the following format: mpsm_t1e1_030.000.000.000.fw. The
numerals in the file name indicate the software version as described in “Determining the Software
Version Number from Filenames” in Chapter 9, “Switch Operating Procedures.”
Step 3 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 4 Use the loadrev command to prepare the standalone service module slot for the MPSM software. The
command format is:
M8850_SF.7.PXM.a > loadrev <slotNo> <mpsm-rev> mpsm
Replace the slotNo variable with the slot number for the legacy service module, and replace the
mpsm-rev variable with the version number of the MPSM software. For information on determining the
software version number using the filename, see “Determining the Software Version Number from
Filenames” in Chapter 9, “Switch Operating Procedures.”
The mpsm parameter is required to enable loading of MPSM software for a slot that is configured for
another type of card. The following example shows how this command is used:
M8850_SF.7.PXM.a > loadrev 13 30.0(0.85)A mpsm
one or more card(s) in the logical slot may be reset.
loadrev: Do you want to proceed (Yes/No)? y
Step 5 Use the runrev command to configure the standalone service module slot to run the MPSM software.
The command format is:
M8850_SF.7.PXM.a > runrev <slotNo> <mpsm-rev> mpsm
Replace the slotNo variable with the slot number for the legacy service module, and replace the
mpsm-rev variable with the version number of the MPSM software. The version number is the same
number used with the loadrev command.
Again, the mpsm parameter is required to enable the operation of MPSM software for a slot that is
configured for another type of card. The following example shows how this command is used:
M8850_SF.7.PXM.a > runrev 13 30.0(0.85)A mpsm
one or more card(s) in the logical slot may be reset.
runrev: Do you want to proceed (Yes/No)? y
After you enter the runrev command, the standalone service module will reset and the card state, which
you can view with the dspcds command, will change to mismatch.
Step 6 Remove the standalone service module from the slot you have prepared for the MPSM.