Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5 - Downloading and Installing Software Upgrades [Cisco MGX 8800 Series Switches]

Table Of Contents

Downloading and Installing Software Upgrades

Upgrade Process Overview

Quickstart Procedures for Software Upgrades

Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10

Graceful PXM Boot Upgrades from Release 3.0.10 and Later

Non-Graceful PXM Boot Upgrades

Graceful PXM and Service Module Runtime Software Upgrades

Non-Graceful PXM and Service Module Runtime Software Upgrades

Graceful Service Module Boot Software Upgrades

Non-Graceful Service Module Boot Software Upgrades

Graceful RPM Boot and Runtime Software Upgrades

Graceful RPM Boot Software Upgrades

Graceful RPM Runtime Software Upgrades

Non-Graceful RPM Boot Software Upgrades

Non-Graceful RPM Runtime Software Upgrades

Quickstart Procedures for Software Downgrades

PXM and AXSM Boot Downgrades

Non-Graceful PXM Runtime Software Downgrades

Non-Graceful AXSM Runtime Software Downgrades

Browsing the File System

Locating Software Updates

Copying Software Files to the Switch

Upgrade Procedures for PXM Cards and Service Modules

Upgrading PXM Boot Software from Releases Prior to 3.0.10

Upgrading PXM Boot Software from Release 3.0.10 and Later

Upgrading Boot Software on Service Modules

Loading the Runtime Upgrade Software

Starting the Upgrade Software

Aborting a Runtime Software Upgrade

Committing to a Runtime Software Upgrade

Upgrade Procedures for RPM-PR and RPM-XF Cards

Upgrading RPM Boot Software

Upgrading RPM Runtime Software

Upgrading RPM Runtime Software for 1:N Redundancy

Upgrading RPM Runtime Software for Non-Redundant Cards

Troubleshooting Upgrade Problems

Downloading and Installing Software Upgrades

This appendix describes how to locate, download, and install software updates for the switch. Because software updates are stored in the switch file system, this appendix includes a section on browsing the file system. This appendix includes the following sections:

•Upgrade Process Overview

•Quickstart Procedures for Software Upgrades

•Quickstart Procedures for Software Downgrades

•Browsing the File System

•Locating Software Updates

•Copying Software Files to the Switch

•Upgrade Procedures for PXM Cards and Service Modules

•Upgrade Procedures for RPM-PR and RPM-XF Cards

•Troubleshooting Upgrade Problems

Upgrade Process Overview

This appendix provides a series of quickstart procedures that describe how to perform graceful and non-graceful upgrades to the switch. To perform a graceful upgrade on a switch card, the card must be operating in redundant mode with another switch card of the same type. When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.

Note Graceful upgrades to Release 5.0 are supported from Release 3.0.25 and later. If you are running a release prior to Release 3.0.25, you must upgrade to Release 3.0.25 before you can upgrade to Release 5.0.

When a card to be upgraded is not operating in redundant mode, you must complete a non-graceful upgrade, which disrupts all traffic that passes through the card. For PXM cards, an ungraceful upgrade interrupts all traffic passing through the switch. For all other types of cards, an ungraceful upgrade affects only the traffic that passes through that card.

When you upgrade the software in a switch, you should refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 for the latest information. Each type of switch card runs boot and runtime software. The recommended sequence for upgrading the software on switch cards is as follows:

1. boot software

2. runtime software

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.

Note You do not need to upgrade any software on SRM cards.

Typically, the boot software requires less frequent upgrades. Some upgrades might only require updates to one type of switch card. The Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 should explain which software components require upgrading.

When you upgrade the software on a switch card, proceed as follows:

•Decide whether you are performing a graceful or non-graceful upgrade

•Follow the appropriate quickstart procedure for that type of upgrade

•For additional information on a task within a quickstart procedure, see the appendix section to which the procedure refers

The next section presents the quickstart procedure for switch card software upgrades.

Quickstart Procedures for Software Upgrades

The following sections provide quickstart procedures for the following upgrades:

•Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10

•Graceful PXM Boot Upgrades from Release 3.0.10 and Later

•Non-Graceful PXM Boot Upgrades

•Graceful PXM and Service Module Runtime Software Upgrades

•Non-Graceful PXM and Service Module Runtime Software Upgrades

•Graceful Service Module Boot Software Upgrades

•Non-Graceful Service Module Boot Software Upgrades

•Graceful RPM Boot Software Upgrades

•Graceful RPM Runtime Software Upgrades

•Non-Graceful RPM Boot Software Upgrades

•Non-Graceful RPM Runtime Software Upgrades

Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10

When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.

All releases prior to Release 3.0.10 require entry into shellcon mode to complete a PXM boot upgrade. The PXM boot upgrade takes a little more time and a few more commands for these early releases.

Note This quickstart applies only if you are upgrading from a release prior to release 3.0.10. If you are upgrading from Release 3.0.10 or later, use the quickstart procedure in the "Graceful PXM Boot Upgrades from Release 3.0.10 and Later" section later in this chapter.

When a boot software upgrade is required, the procedure for upgrading redundant PXM cards is as follows:

1. Manually upgrade the boot software on the standby PXM.

2. Switch cards to make the upgraded standby card active.

3. After the standby card becomes the active card, manually upgrade the non-active card.

This process ensures a smooth transition to the new software and preserves all established calls. During the short period when the roles of the active and standby cards are switched, all calls that are not established are lost.

Caution Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade.

To upgrade the boot software, use the following procedure.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

username

password

saveallcnf

If you want to save the configuration before the upgrade, establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges.

This optional step saves the current configuration to the hard disk.

see the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."

Step 3

username

password

Establish a CLI session with the standby PXM card using the CP port on the PXM-UI-S3 or PXM-UI-S3/B back card and a user name with CISCO_GP privileges.

Step 4

sh

sysBackupBoot

<Return> (3.0 and earlier)

Change to the PXM Backup Boot mode.

Note that the software versions 3.0 and earlier require you to press Return during the reboot sequence to enter backup boot mode.

See the "Changing to PXM Backup Boot Mode" section in "PXM Backup Boot Procedures."

Step 5

sysPxmRemove

At the backup boot prompt, enter the sysPxmRemove command: This step prevents the active card from resetting the standby card while you are working with it.
Step 6

sysFlashBootBurn "path/filename"

reboot 2¹

username

password

dspcd
Burn the boot code. Remember to enter quotation marks before and after the boot software filename, and specify the complete path. For example:
sysFlashBootBurn "C:FW/pxm1e_004.000.000.201_bt.fw"
Note Remember to enter quotation marks before and after the boot software filename. The filename you use depends on the release to which you are upgrading. For more information, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00.

Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading PXM Boot Software from Releases Prior to 3.0.10" section later in this appendix.
Step 7

username

password

Establish a CLI session with the active PXM card (which is the non-upgraded card). Use the CP port on the PXM-UI-S3 or PXM-UI-S3/B back card and a user name with CISCO_GP privileges.

Step 8

switchcc

y

Switch the roles of the active and standby cards so you can upgrade the non-upgraded card in standby mode.

Step 9

sh

sysBackupBoot

<Return> (3.0 and earlier)

Change to the PXM Backup Boot mode.

Note that the software versions 3.0 and earlier require you to press Return during the reboot sequence to enter backup boot mode.

See the "Changing to PXM Backup Boot Mode" section in "PXM Backup Boot Procedures.".

Step 10

sysPxmRemove

At the backup boot prompt, enter the sysPxmRemove command. This step prevents the active card from resetting the standby card while you are working with it.
Step 11

sysFlashBootBurn "path/filename"

reboot 21

username

password

dspcd
Burn the boot code. For example,
sysFlashBootBurn "C:FW/pxm1e_004.000.000.201_bt.fw"
Note Remember to enter quotation marks before and after the boot software filename. The filename you use depends on the release to which you are upgrading. For more information, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00.

Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading PXM Boot Software from Releases Prior to 3.0.10" section later in this appendix.

Both active and standby cards should now be upgraded. The card that was active before the upgrade is now operating in standby mode.
¹Beginning with Release 4.0, you must enter reboot 2. For all prior releases, enter reboot.
Graceful PXM Boot Upgrades from Release 3.0.10 and Later

When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.

Beginning with Release 3.0.10, the Cisco MGX software supports the burnboot command for PXM boot software upgrades. If you are upgrading a Release 3.0.10 or later switch, you no longer have to enter shellcon to complete the boot upgrade. The boot upgrade is simpler and quicker in Release 3.0.10 and later.

Note This quickstart applies only if you are upgrading from Release 3.0.10 or a later release. If you are upgrading from a release prior to 3.0.10, use the quickstart procedure in the "Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10" section earlier in this chapter.

When a boot software upgrade is required, the procedure for upgrading redundant PXM card is as follows:

1. Manually upgrade the boot software on the standby PXM.

2. Switch cards to make the upgraded standby card active.

3. After the standby card becomes the active card, manually upgrade the non-active card.

This process ensures a smooth transition to the new software and preserves all established calls. During the short period when the roles of the active and standby cards are switched, all calls that are not established are lost.

Note Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade.

To upgrade the boot software, use the following procedure.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section, which appears later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges or higher.

Step 3

saveallcnf

This optional step saves the current configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standby PXM card by specifying the slot number of the standby card. For example:
M8850_LA.7.PXM.a > burnboot 8 4.0(0.201)
Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading PXM Boot Software from Release 3.0.10 and Later" section, which appears later in this appendix.
Step 5

switchcc

Activate the upgraded card and place the non-upgraded card in standby mode.

Step 6

burnboot <slot> <revision>

dspcd <slot>

Burn the boot software on the non-upgraded, standby PXM card by specifying the slot number of the standby card.

See the "Upgrading PXM Boot Software from Releases Prior to 3.0.10" section, which appears later in this appendix.
Non-Graceful PXM Boot Upgrades

Non-graceful upgrades disrupt all 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 Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using the CP port on the PXM-UI-S3 or PXM-UI-S3/B back card and a user name with CISCO_GP privileges.

Step 3

saveallcnf

This optional step saves the current configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standalone PXM card by specifying the appropriate slot number. For example:
M8850_LA.7.PXM.a > burnboot 7 4.0(0.201)
Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading PXM Boot Software from Release 3.0.10 and Later" section, which appears later in this appendix.
Graceful PXM and Service Module Runtime Software Upgrades

When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections.

This quickstart procedure applies to PXM1E, PXM45 and to all service module cards except the RPM family of cards. The quickstart procedure provides more detail, but the overall procedure is as follows:

1. Load the new software on the standby PXM or service module.

2. Make the standby card active.

3. Load the new software on the formerly active (now standby) card.

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.

Caution Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade. While graceful upgrades can be aborted with the abortrev command, the abortrev command does reset both active and standby cards, so reverting back to an earlier software release is non-graceful.

Note Cisco Systems recommends that you upgrade software on one service module at a time within a switch. Wait until each service module upgrade is complete before starting an upgrade on another service module.

To upgrade the runtime software, use the following procedure.

Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section, which appears later in this appendix.

Step 2

If the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 call for a boot software upgrade, upgrade the boot software for the card you are upgrading.

Note PXM cards should be upgraded first.

For instructions on upgrading service module boot software, see the "Graceful Service Module Boot Software Upgrades" section, which appears later in this appendix.

Step 3

username

password

Establish a CLI session with the active PXM45 card using a user name with SERVICE_GP privileges.

Step 4

saveallcnf

This optional step saves the current switch configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."

Step 5

dspcd

commitrev <slot> <revision>

Verify that all previous upgrades have been committed.

If a previous upgrade is not committed, commit to the new upgrade.

See the "Committing to a Runtime Software Upgrade" section, which appears later in this appendix.

Step 6

loadrev <slot> <revision>

dspcd

Load the new runtime software on the standby PXM or service module.

Step 7

runrev <slot> <revision>

dspcd

dspcd <slot>

Switch over to the standby PXM or service module and load the new runtime software on the new standby (non-upgraded) card.

Step 8

commitrev <slot> <revision>

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 Upgrade" section and the "Committing to a Runtime Software Upgrade" section, both of which appear later in this appendix.

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.

Note Avoid making configuration changes while upgrading PXM software. Configuration changes can be lost when the PXM is reset during the upgrade.

Note Cisco Systems recommends that you upgrade software on one service module at a time within a switch. Wait until each service module upgrade is complete before starting an upgrade on another service module.

Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch"section, which appears later in this appendix.

Step 2

If the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 call for a boot software upgrade, upgrade the boot software as described in the "Graceful PXM Boot Upgrades from Release 3.0.10 and Later" section, which appears earlier in this appendix, or the "Non-Graceful Service Module Boot Software Upgrades" section, which appears later in this appendix.

Step 3

username

password

Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges.

Step 4

saveallcnf

This optional step saves the current configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."

Step 5

dspcd

commitrev <slot> <revision>

Verify that all previous upgrades are committed.

If a previous upgrade is not committed, commit to the new upgrade.

See the "Committing to a Runtime Software Upgrade" section, which appears later in this appendix.

Step 6

loadrev <slot> <revision>

dspcd

Define the new software version to be used.

Step 7

runrev <slot> <revision>

dspcd

Reset the card and run the new software version.

Step 8

commitrev <slot> <revision>

This command prevents an accidental switch back to a previous software revision if someone enters the abortrev command. Enter the commitrev command after the upgraded card reaches the active 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 Upgrade" section and the "Committing to a Runtime Software Upgrade" section, both of which appear later in this appendix.

Graceful Service Module Boot Software Upgrades

When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. This quickstart procedure applies to all service modules except the RPM family of cards and provides an overview and quick reference for those who have already performed graceful boot software 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.

Note Cisco Systems recommends that you upgrade software on one service module at a time within a switch. Wait until each service module upgrade is complete before starting an upgrade on another service module.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section, which appears later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges or higher.

Step 3

saveallcnf

This optional step saves the current configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standby service module by specifying the slot number of the standby card. For example:
M8850_LA.7.PXM.a > burnboot 1 4.0(0.0)
Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading Boot Software on Service Modules" section, which appears later in this appendix.
Step 5

switchredcd <fromSlot> <toSlot>

Activate the upgraded card and place the non-upgraded card in standby mode.

Step 6

burnboot <slot> <revision>

dspcd <slot>

Burn the boot software on the non-upgraded, standby service module by specifying the slot number of the standby card.

See the "Upgrading Boot Software on Service Modules" section, which appears later in this appendix.
Non-Graceful Service Module Boot Software Upgrades

Non-graceful upgrades disrupt all switch traffic and are usually used in lab installations where the use of standalone cards provides no opportunity for a graceful upgrade. This quickstart procedure applies to all service modules except the RPM family of cards and provides an overview and a 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.

Note Cisco Systems recommends that you upgrade software on one service module at a time within a switch. Wait until each service module upgrade is complete before starting an upgrade on another service module.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch.

See the "Copying Software Files to the Switch" section, which appears later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges or higher.

Step 3

saveallcnf

This optional step saves the current configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 9, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standalone service module. For example:
M8850_LA.7.PXM.a > burnboot 1 4.0(0.0)
Caution If the card is removed or reset, or if switch power is interrupted during the boot software upgrade, the upgrade will not complete, the card will not operate, and the card must be returned to Cisco for repair.

See the "Upgrading Boot Software on Service Modules" section, which appears later in this appendix.
Graceful RPM Boot and Runtime Software Upgrades

The RPM cards support graceful boot software upgrades when 1:N redundancy is established in the switch between RPM cards. Boot software is generally upgraded less often than runtime software, so be sure to compare the recommended boot software version with the boot software running on your RPM cards before starting an upgrade. The correct boot software might already be installed.

Note In this document, the general term "RPM" refers to RPM-PR and RPM-XF cards. If a step or procedure is specific to only one of the RPM cards, it will be called out in the text.

The following quickstart procedure describes how to upgrade boot and runtime software in one operation on redundant RPM cards.

Note Redundancy must be established before you use this procedure. If redundancy has not been configured between two RPM cards, upgrade each RPM card using the procedure in the "Non-Graceful RPM Boot Software Upgrades" section later in this chapter. To add redundancy to an RPM card, see the "Establishing Redundancy Between RPM Cards" section in "Preparing RPM Cards for Operation."
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (C:FW).

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

copy

Optional: Copy and rename the runtime file to a generic name for easy updates.

See the "Upgrading RPM Runtime Software" section later in this chapter.

Note If you have already configured the RPM to use a generic name and you perform this step, you can skip Steps 11 through 18.

Step 3

username

password

Establish a CLI session with the active PXM card using a user name at any access level.

Step 4

cc <primarySlot>

Select the slot in which the primary RPM card is installed.

Step 5

enable

password

Enter Enable mode for the router.

Step 6

dir x:

Verify router access to the PXM hard disk and the boot upgrade software.

Step 7

show flash:

Display current contents of bootflash.
Step 8

copy filename bootflash:

dir bootflash:
Copy the upgrade boot software to flash. For example:
copy x:rpm-boot-mz_002.001.060.000 bootflash:
Step 9

config terminal

boot bootldr bootflash:filename

^Z

show bootvar

Configure the BOOTLDR variable to specify the new boot software.

Step 10

copy bootflash:filename x:filename

del bootflash:filename

show flash:

squeeze flash:

Reorganize files in bootflash. The switch always attempts to load the first bootable file in bootflash. If the BOOTLDR variable is not set, the new boot software must be the first file listed in the show flash: display. Copy files you want to save to the x: directory and delete all files that appear before the new boot software. Files are marked with the del command and actually deleted with the squeeze flash: command.

Caution Verify that at least one valid boot or runtime image will not be deleted. If all boot and runtime images are deleted from bootflash, the RPM card must be returned to the factory for repair.

Step 11

show bootvar

Display the current runtime software filename.

Step 12

config terminal

Enter the router global configuration mode.
Step 13

no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system x:rpm-js-mz_122-4.T
Step 14

boot system x:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system x:rpm-js-mz_122-4.T
Step 15

boot config e:auto_config_RPM-PR_slot#

Configure the RPM card to store its configuration on the PXM hard disk.

Note This step only needs to be performed once. If this command is already in the startup configuration file, you do not need to enter it again.

Step 16

^Z

Exit global configuration mode.

Step 17

copy run start

Save the new configuration.

Note If you omit this step, the RPM card will continue to use the previous version of software.

Step 18

show bootvar

Verify the change in the runtime software filename.

Step 19

switchredcd <primarySlot> <secondarySlot>

This step makes the secondary card active and resets the primary RPM card. When the primary card resets, it loads the upgraded boot and runtime software.

Step 20

cc <secondarySlot>

Select the slot in which the secondary RPM card is installed.

Step 21

enable
password
dir x:
show flash:
copy filename bootflash:
dir bootflash:

config terminal
boot bootldr bootflash:filename
^Z
show bootvar

copy bootflash:filename x:filename
del bootflash:filename
show flash:
squeeze flash:

Repeat Steps 5 through 10 to move the upgraded boot software into bootflash.

Step 22

switchredcd <secondarySlot> <primarySlot>

This step makes the upgraded primary card active and resets the secondary RPM card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded boot software.

Note You do not need to upgrade runtime software on a secondary card. When a secondary card goes active, it loads the runtime software and configuration defined for the primary card.

Step 23

—

If there are other primary RPM cards that need upgrading, repeat the part of this procedure that upgrades the primary card, then enter the switchredcd command once to reload the primary card. Finally, enter the switchredcd command a second time to make the upgraded primary card active.
Graceful RPM Boot Software Upgrades

The RPM cards support graceful boot software upgrades when 1:N redundancy is established in the switch between RPM cards. Boot software is generally upgraded less often than runtime software, so be sure to compare the recommended boot software version with the boot software running on your RPM cards before starting an upgrade. The correct boot software might already be installed.

Note In this document, the general term "RPM" refers to RPM-PR and RPM-XF cards. If a step or procedure is specific to only one of the RPM cards, it will be called out in the text.

The following quickstart procedure describes how to upgrade redundant RPM cards.

Note Redundancy must be established before you use this procedure. If redundancy has not been configured between two RPM cards, upgrade each RPM card using the procedure in the "Non-Graceful RPM Boot Software Upgrades" section later in this chapter. To add redundancy to an RPM card, see the "Establishing Redundancy Between RPM Cards" section in "Preparing RPM Cards for Operation."
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (C:FW).

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using a user name at any access level.

Step 3

cc <primarySlot>

Select the slot in which the primary RPM card is installed.

Step 4

enable

password

Enter Enable mode for the router.

Step 5

dir x:

Verify router access to the PXM hard disk and the boot upgrade software.

Step 6

show flash:

Display current contents of bootflash.
Step 7

copy filename bootflash:

dir bootflash:
Copy the upgrade boot software to flash. For example:
copy x:rpm-boot-mz_002.001.060.000 bootflash:
Step 8

config terminal

boot bootldr bootflash:filename

^Z

show bootvar

Configure the BOOTLDR variable to specify the new boot software.

Step 9

copy bootflash:filename x:filename

del bootflash:filename

show flash:

squeeze flash:

Reorganize files in bootflash. The switch always attempts to load the first bootable file in bootflash. If the BOOTLDR variable is not set, the new boot software must be the first file listed in the show flash: display. Copy files you want to save to the x: directory and delete all files that appear before the new boot software. Files are marked with the del command and actually deleted with the squeeze flash: command.

Caution Verify that at least one valid boot or runtime image will not be deleted. If all boot and runtime images are deleted from bootflash, the RPM card must be returned to the factory for repair.

Step 10

switchredcd <primarySlot> <secondarySlot>

This step makes the secondary card active and resets the primary RPM card. When the primary card resets, it loads the upgraded boot software from bootflash.

Step 11

cc <secondarySlot>

Select the slot in which the secondary RPM card is installed.

Step 12

enable
password
dir x:
show flash:
copy filename bootflash:
dir bootflash:

config terminal
boot bootldr bootflash:filename
^Z
show bootvar

copy bootflash:filename x:filename
del bootflash:filename
show flash:
squeeze flash:

Repeat Steps 4 through 9 to move the upgraded boot software into bootflash.

Step 13

switchredcd <secondarySlot> <primarySlot>

This step makes the upgraded primary card active and resets the secondary RPM card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded boot software.

Step 14

—

If there are other primary RPM cards that need upgrading, repeat the part of this procedure that upgrades the primary card, then enter the switchredcd command once to reload the primary card. Finally, enter the switchredcd command a second time to make the upgraded primary card active.
Graceful RPM Runtime Software Upgrades

The RPM cards support graceful upgrades when 1:N redundancy is established in the switch between RPM cards.

Note In this document, the general term "RPM" refers to RPM-PR and RPM-XF cards. If a step or procedure is specific to only one of the RPM cards, it will be called out in the text.

The following quickstart procedure describes how to gracefully upgrade runtime software on redundant RPM cards.

Note Redundancy must be established before you use this procedure. If redundancy has not been configured between two RPM cards, upgrade each RPM card as described in the "Non-Graceful RPM Runtime Software Upgrades" section later in this chapter. To add redundancy to an RPM card, see the "Establishing Redundancy Between RPM Cards" section in "Preparing RPM Cards for Operation."
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (C:FW).

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

copy

Optional: Copy and rename the runtime file to a generic name for easy updates.

See the "Upgrading RPM Runtime Software" section later in this chapter.

Note If you have already configured the RPM to use a generic name, you can skip to Step 12.

Step 3

username

password

Establish a CLI session with the active PXM card using a user name at any access level.

Step 4

cc <primarySlot>

Select the slot in which the primary RPM card is installed.

Step 5

enable

password

Enter Enable mode for the router.

Step 6

show bootvar

Display the current runtime software filename.

Step 7

config terminal

Enter the router global configuration mode.
Step 8

no boot system
Remove the entire boot list. To remove a single file from the boot list, include a filename. For example:
Router(config)# no boot system x:rpm-js-mz_122-4.T
Step 9

boot system x:filename
Add the new router runtime image to the boot list. For example:
Router(config)# boot system x:rpm-js-mz_122-4.T
Step 10

boot config e:auto_config_RPM-PR_slot#

Configure the RPM card to store its configuration on the PXM hard disk.

Note This step only needs to be performed once. If this command is already in the startup configuration file, you do not need to enter it again.

Step 11

^Z

Exit global configuration mode.

Step 12

copy run start

Save the new configuration.

Note If you omit this step, the RPM card will continue to use the previous version of software.

Step 13

show bootvar

Verify the change in the runtime software filename.

Step 14

switchredcd <primarySlot> <secondarySlot>

This step makes the secondary card active and resets the primary RPM card. When the primary card resets, it loads the upgraded boot software from bootflash.

Step 15

switchredcd <secondarySlot> <primarySlot>

This step makes the upgraded primary card active and resets the secondary RPM-PR card. When the secondary card resets, it loads the upgraded boot software from bootflash. Both primary and secondary cards should now be using upgraded runtime software.

Step 16

If there are other primary RPM cards that need upgrading, repeat the part of this procedure that upgrades the primary card, and then enter the switchredcd command once to reload the primary card. Finally, enter the switchredcd command a second time to make the upgraded primary card active.
Non-Graceful RPM Boot Software Upgrades

Use the non-graceful upgrade procedure in this section when you need to upgrade RPM boot software and the RPM is operating in standalone mode. Non-graceful upgrades terminate all connections and disrupt service until the upgrade procedure is complete.

Note In this document, the general term "RPM" refers to RPM-PR and RPM-XF cards. If a step or procedure is specific to only one of the RPM cards, it will be called out in the text.

Note If the RPM is operating in 1:N redundancy mode with another RPM, upgrade the cards as described in the "Graceful RPM Boot Software Upgrades"section earlier in this chapter.

The following quickstart procedure provides an overview and quick reference for those who have already performed RPM upgrades on the switch. For detailed instructions, see the "Upgrade Procedures for RPM-PR and RPM-XF Cards" section which appears later in this appendix.
Command

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (C:FW).

See the "Copying Software Files to the Switch" section later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM card using a user name at any access level.

Step 3

cc <RPM_Slot>

Select the slot in which the RPM card is installed.

Step 4

enable

password

Enter Enable mode for the router.

Step 5

dir x:

Verify router access to the hard disk and the boot upgrade software.

Step 6

show flash:

Display current contents of bootflash.
Step 7

copy filename bootflash:

dir bootflash:
Copy the upgrade boot software to flash. For example:
copy x:rpm-boot-mz_002.001.000.000 bootflash:
Step 8

config terminal

boot bootldr bootflash:filename

^Z

show bootvar

Configure the BOOTLDR variable to specify the new boot software.

Step 9

copy bootflash:filename x:filename

del bootflash:filename

show flash:

squeeze flash:

Reorganize files in bootflash. The switch always attempts to load the first bootable file in bootflash. If the BOOTLDR variable is not set, the new boot software must be the first file listed in the show flash: display. Copy files you want to save to the x: directory and delete all files that appear before the new boot software. Files are marked with the del command and actually deleted with the squeeze flash: command.

Caution Verify that