Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3 - 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 PXM45 Boot Upgrades

Non-Graceful PXM45 Boot Upgrades

Graceful PXM45, AXSM, and FRSM-12 Runtime Software Upgrades

Non-Graceful PXM45, AXSM, and FRSM-12 Runtime Software Upgrades

Graceful AXSM or FRSM-12 Boot Upgrades

Non-Graceful AXSM Boot Upgrades

Graceful RPM-PR Boot Software Upgrades

Graceful RPM-PR Runtime Software Upgrades

Non-Graceful RPM-PR Boot Software Upgrades

Non-Graceful RPM-PR Runtime Software Upgrades

Installing SCT Files

Quickstart Procedures for Software Downgrades

PXM45 and AXSM Boot Downgrades

Non-Graceful PXM45 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 PXM45, AXSM, and FRSM-12 Cards

Upgrading PXM45 Boot Software

Loading the Runtime Upgrade Software

Starting the Upgrade Software

Upgrading Boot Software on an AXSM or FRSM-12 Card

Aborting a Runtime Software Upgrade

Committing to a Runtime Software Upgrade

Upgrade Procedures for RPM-PR Cards

Upgrading RPM-PR Boot Software

Upgrading RPM-PR Runtime Software

Upgrading RPM-PR Runtime Software for 1:N Redundancy

Upgrading RPM-PR Runtime Software for Non-Redundant Cards

Upgrading SCT Files

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 PXM45, AXSM, and FRSM-12 Cards

•Upgrade Procedures for RPM-PR Cards

•Upgrading SCT Files

•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 3.0 are supported from Releases 2.0.16 and 2.1.15.

When a card to be upgraded is not operating in redundant mode, you must do a non-graceful upgrade, which disrupts all traffic that passes through the card. For PXM45 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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 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. PXM45 boot software

2. PXM45 runtime software

3. AXSM and FRSM-12 boot software

4. AXSM and FRSM-12 runtime software

5. RPM-PR boot software

6. RPM-PR runtime software

Note If you plan to upgrade PXM45 cards and AXSM or FRSM-12 cards, upgrade the PXM45 cards first. Wait until the PXM45 cards are operating in active and standby modes with the correct software before upgrading AXSM or FRSM-12 cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, AXSM-E. AXSM-32-E, or FRSM-12 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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 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 PXM45 Boot Upgrades

•Non-Graceful PXM45 Boot Upgrades

•Graceful PXM45, AXSM, and FRSM-12 Runtime Software Upgrades

•Non-Graceful PXM45, AXSM, and FRSM-12 Runtime Software Upgrades

•Graceful AXSM or FRSM-12 Boot Upgrades

•Non-Graceful AXSM Boot Upgrades

•Graceful RPM-PR Boot Software Upgrades

•Graceful RPM-PR Runtime Software Upgrades

•Non-Graceful RPM-PR Boot Software Upgrades

•Non-Graceful RPM-PR Runtime Software Upgrades

•Installing SCT Files

Graceful PXM45 Boot Upgrades

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

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

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

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 PXM45 software. Configuration changes can be lost when the PXM45 is reset during the upgrade.

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

username

password

Establish a CLI session with the standby PXM45 card using the CP port on the UI-S3 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 7, "Switch Operating Procedures."

Step 4

sh

sysBackupBoot

<Return> (2.0.11 and earlier)

Change to the PXM45 backup boot mode.

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

See the "Changing to PXM45 Backup Boot Mode" section in "PXM45 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 "Filename"

reboot

username

password

dspcd
Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example:
sysFlashBootBurn "C:FW/pxm45_003.000.000.000_bt.fw"
See the "Upgrading PXM45 Boot Software" section, which appears later in this appendix.
Step 7

username

password

Establish a CLI session with the active PXM45 card (which is the non-upgraded card) using the CP port on the UI-S3 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> (2.0.11 and earlier)

Change to the PXM45 backup boot mode.

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

See the "Changing to PXM45 Backup Boot Mode" section in "PXM45 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 "Filename"

reboot

username

password

dspcd
Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example:
sysFlashBootBurn "C:FW/pxm45_003.000.000.000_bt.fw"
See the "Upgrading PXM45 Boot Software" section, which appears 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.
Non-Graceful PXM45 Boot Upgrades

Ungraceful 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 is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the switch.

Note Avoid making configuration changes while upgrading PXM45 software. Configuration changes can be lost when the PXM45 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, which appears later in this appendix.

Step 2

username

password

Establish a CLI session with the active PXM45 card using the CP port on the UI-S3 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 7, "Switch Operating Procedures."

Step 4

sh

sysBackupBoot

<Return> (2.0.11 and earlier)

Change to the PXM45 Backup Boot mode.

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

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

Step 5

sysPxmRemove

If there are two PXM45 cards installed in the switch, enter the sysPxmRemove command to prevent the active card from resetting the standby card while you are working with it.
Step 6

sysFlashBootBurn "Filename"

reboot

username

password

dspcd
Burn the boot code. Remember to enter quotation marks before and after the boot software filename. For example:
sysFlashBootBurn "C:FW/pxm45_003.000.000.000_bt.fw"
See the "Upgrading PXM45 Boot Software" section, which appears later in this appendix.
Graceful PXM45, AXSM, and FRSM-12 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 PXM45, AXSM, and FRSM-12 cards. Use the procedure to perform the following tasks:

1. Loads the new software on the standby PXM45, AXSM, or FRSM-12 card.

2. Makes the standby card active.

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

Note If you plan to upgrade PXM45 cards and AXSM or FRSM-12 cards, upgrade the PXM45 cards first. Wait until the PXM45 cards are operating in active and standby modes with the correct software before upgrading AXSM or FRSM-12 cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, AXSM-E, AXSM-32-E, and FRSM-12 cards. When AXSM or FRSM-12 boot software is to be upgraded, it should be upgraded before upgrading the runtime software.

Caution Avoid making configuration changes while upgrading PXM45 software. Configuration changes can be lost when the PXM45 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 AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card.

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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 call for a boot software upgrade, upgrade the boot software for the card you are upgrading.

PXM45 cards should be upgraded first. See the "Graceful PXM45 Boot Upgrades" section, which appears earlier in this appendix.

For instructions on upgrading AXSM or FRSM-12 boot software, see the "Graceful AXSM or FRSM-12 Boot 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 configuration to the hard disk.

See the "Saving a Configuration" section in Chapter 7, "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 PXM45.

Step 7

runrev <slot> <revision>

dspcd

dspcd <slot>

Switch over to the standby PXM45 card and load the new runtime software on the new standby (non-upgraded) PXM45.

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 PXM45, AXSM, and FRSM-12 Runtime Software Upgrades

Ungraceful 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 is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the switch.

Note If you plan to upgrade PXM45 cards and AXSM or FRSM-12 cards, upgrade the PXM45 cards first. Wait until the PXM45 cards are operating in active and standby modes with the correct software before upgrading AXSM or FRSM-12 cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, AXSM-E, AXSM-32-E, or FRSM-12 cards. When AXSM or FRSM-12 boot software is to be upgraded, it should be upgraded before upgrading the runtime software.

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

Note Cisco Systems recommends that you upgrade software on one AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card.

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 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3 call for a boot software upgrade, upgrade the boot software as described in the "Non-Graceful PXM45 Boot Upgrades" section, which appears earlier in this appendix, or the "Non-Graceful AXSM Boot 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 configuration to the hard disk.

see the "Saving a Configuration" section in Chapter 7, "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 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.

Graceful AXSM or FRSM-12 Boot Upgrades

When performed properly, graceful upgrades have minimal impact on connections in progress and do not interrupt any established connections. The quickstart procedure is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the switch.

Note If you plan to upgrade PXM45 cards and AXSM or FRSM-12 cards, upgrade the PXM45 cards first. Wait until the PXM45/B cards are operating in active and standby modes with the correct software before upgrading AXSM or FRSM-12 cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, AXSM-E, AXSM-32-E, and FRSM-12 cards.

Note Cisco Systems recommends that you upgrade software on one AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card.
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 PXM45 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 7, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standby AXSM card by specifying the slot number of the standby card. For example:
M8850_LA.7.PXM.a > burnboot 1 3.0(0.0)
See the "Upgrading Boot Software on an AXSM or FRSM-12 Card" 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 AXSM card by specifying the slot number of the standby card.

See the "Upgrading Boot Software on an AXSM or FRSM-12 Card" section, which appears later in this appendix.
Non-Graceful AXSM Boot Upgrades

Ungraceful 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 is provided as an overview and as a quick reference for those who have already performed ungraceful upgrades on the switch.

Note If you plan to upgrade PXM45 cards and AXSM cards, upgrade the PXM45 cards first. Wait until the PXM45 cards are operating in active and standby modes with the correct software before upgrading AXSM cards. The software version used by the PXM45/B cards should be equal to or later than the version used on the AXSM, AXSM/B, and AXSM-E cards.

Note Cisco Systems recommends that you upgrade software on one AXSM or FRSM-12 card at a time within a switch. Wait until each AXSM or FRSM-12 card upgrade is complete before starting an upgrade on another AXSM or FRSM-12 card.
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 PXM45 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 7, "Switch Operating Procedures."
Step 4

burnboot <slot> <revision>

dspcd <slot>
Burn the boot software on the standby AXSM or FRSM-12 card by specifying the slot number of the standby card. For example:
M8850_LA.7.PXM.a > burnboot 1 3.0(0.0)
See the "Upgrading Boot Software on an AXSM or FRSM-12 Card" section, which appears later in this appendix.
Graceful RPM-PR Boot Software Upgrades

The RPM-PR card supports graceful boot software upgrades when 1:n redundancy is established in the switch between RPM-PR 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 RPMs before starting an upgrade. The correct boot software might already be installed.

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

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

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (E:RPM).

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

Step 2

username

password

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

Step 3

cc <primarySlot>

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

Step 4

enable

password

Enter Enable mode for the router.

Step 5

dir e:

Verify router access to the PXM45 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 e: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 c: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 c: 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-PR 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-PR 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-PR card is installed.

Step 12

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

config terminal
boot bootldr bootflash:filename
^Z
show bootvar

copy bootflash:filename c: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-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 boot software.

Step 14

—

If there are other primary RPM-PR 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-PR Runtime Software Upgrades

The RPM-PR card supports graceful upgrades when 1:n redundancy is established in the switch between RPM-PR cards.

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

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

Purpose

Step 1

ftp

Copy the boot and runtime files you want to use to the switch (E:RPM).

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

Step 2

copy

This step is optional. Copy and rename the runtime file to a generic name for easy updates.

See the "Non-Graceful RPM-PR Runtime Software Upgrades" section, which appears later in this chapter.

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

Step 3

username

password

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

Step 4

cc <primarySlot>

Select the slot in which the primary RPM-PR 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 c:rpm-js-mz_122-4.T
Step 9

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

boot config e:auto_config_RPM-PR_slot#

Configure the RPM-PR card to store its configuration on the PXM45 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-PR card will continue to use the previous version of software.

Step 13

show bootvar

Verify the change in the runtime software filename.

Step 14

softswitch <primarySlot> <secondarySlot>

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

Step 15

softswitch <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-PR cards that need upgrading, repeat the part of this procedure that upgrades the primary card, then enter the softswitch command once to reload the primary card. Finally, enter the softswitch command a second time to make the upgraded primary card active.
Non-Graceful RPM-PR Boot Software Upgrades

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

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

The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed RPM-PR upgrades on the switch. For detailed instructions, see the "Upgrade Procedures for RPM-PR 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 (E:RPM).

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

Step 2

username

password

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

Step 3

cc <RPM_Slot>

Select the slot in which the RPM-PR card is installed.

Step 4

enable

password

Enter Enable mode for the router.

Step 5

dir e:

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 e: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 c: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 c: 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 and the card is reset, the RPM-PR card must be returned to the factory for repair.

Step 10

cc <active_PXM_slot>

resetcd <RPM_Slot>

This command sequence restarts the RPM-PR card with the new boot image.
Non-Graceful RPM-PR Runtime Software Upgrades

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

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

The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed RPM-PR upgrades on the switch. For detailed instructions, see the "Upgrade Procedures for RPM-PR 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 (E:RPM).

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

Step 2

copy

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

See the "Non-Graceful RPM-PR Runtime Software Upgrades" section, which appears later in this chapter.

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

Step 3

username

password

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

Step 4

cc <RPM-PR_Slot>

Select the slot in which the RPM-PR 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 c:rpm-js-mz_122-4.T
Step 9

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

boot config e:auto_config_RPM-PR_slot#

Configure the RPM-PR card to store its configuration on the PXM45 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

copy run start

Exit global configuration mode and save the new configuration.

Step 12

show bootvar

Verify the change in the runtime software filename.

Step 13

cc <active_PXM45_slot>

resetcd <RPM-PR_Slot>

This command sequence selects the active PXM45 card and restarts the RPM-PR card with the new runtime image.

Step 14

dspcds

dspcd <RPM-PR_Slot>

cc <RPM-PR_Slot>

Verify router reboot is complete.
Installing SCT Files

Use the procedure in this section when you need to manually install or upgrade SCT files.

If you are using CWM to install or upgrade SCT files in your network, refer to the Cisco WAN Manager User's Guide, Release 11

Note The following quickstart procedure is provided as an overview and as a quick reference for those who have already performed SCT upgrades on the switch. For detailed instructions, see the "Upgrading SCT Files" section, which appears later in this appendix.

Command

Purpose

Step 1

ftp

Copy the new SCT files you want to use to the appropriate C:SCT\<card_type> directory. For example, copy new AXSM or FRSM-12 SCT files to the C:SCT\AXSM or C:SCT\FRSM directory.

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 PXM45 card using a user name at any access level.

Step 3

addsct <oprtions>

Select the slot in which the RPM-PR card is installed.

Step 4

switchcc

or

reboot

If you are upgrading the SCTs on redundant cards, switch the roles of the active and standby cards. You need to upgrade the SCTs on the non-upgraded card while it is in standby mode.

If you are upgrading the SCTs on non-redundant cards, reboot the card to activate the new SCTs.

Step 5

dspscts

Verify router reboot is complete.

Quickstart Procedures for Software Downgrades

Cisco Systems, Inc., recommends that you avoid software downgrades, which replace a current software release with another that has a lower version number. However, there are some situations in which you might want to downgrade the software. For example, if you have been testing pre-release software in a lab, the software version number can be higher than a later official software release. Any time the software version number to which you are changing is lower than the current software version, the change is a downgrade, regardless of when the software versions are released.

The following sections provide quickstart procedures for the following downgrades:

•PXM45 and AXSM Boot Downgrades

•Non-Graceful PXM45 Runtime Software Downgrades

•Non-Graceful AXSM Runtime Software Downgrades

PXM45 and AXSM Boot Downgrades

When redundant cards are used and the downgrade software is compatible with the existing runtime software, boot software downgrades can be graceful. To perform a graceful downgrade of boot software, follow the instructions for the appropriate graceful software upgrade:

•Graceful PXM45 Boot Upgrades

•Graceful AXSM or FRSM-12 Boot Upgrades

Caution Cisco Systems, Inc., does not guarantee that any software downgrade is graceful, so assume that the downgrade is non-graceful and time the downgrade accordingly. The advantage to following the graceful upgrade procedures listed above is that you might be able to delay traffic interruption until the runtime software is downgraded.

When upgrading a standalone card, the downgrade is non-graceful, and you should follow one of the following software upgrade procedures:

•Non-Graceful PXM45 Boot Upgrades

•Non-Graceful AXSM Boot Upgrades

Non-Graceful PXM45 Runtime Software Downgrades

To downgrade PXM45 runtime software, you must clear the entire switch configuration.All traffic is disrupted until the switch downgrade is complete and the configuration has been re-entered. The following quickstart procedure is provided as an overview for PXM45 runtime software downgrades.

Note The switch does not support a configuration restore to a downgraded software version. When you downgrade the PXM45 runtime software, you must re-enter the configuration.

Non-Graceful AXSM Runtime Software Downgrades

AXSM runtime software downgrades are always non-graceful when the PXM45 runtime software is also downgraded (because the PXM45 downgrade requires a clearing of the configuration). The quickstart procedure is provided as an overview of how to downgrade the AXSM software after the PXM45 runtime software has been downgraded.

Browsing the File System

The PXM45 hard disk stores log files, configuration files, and boot and runtime software. The switch operating system supports a set of UNIX-like commands that you can use to locate log files or manage software updates. Table A-1 lists commands that you can use to browse the file system.

Note File and directory names in the switch file system are case sensitive. Also, some of the commands listed in Table A-1 are not available at all administrator access levels.

Table A-1 File System Commands at Switch Prompt

Command

Description

cd

Change directories. Access level required: ANYUSER or above.

copy

Copies a file from one location to another.

Syntax: copy <source file name> <destination file name>

Access level required: GROUP1 or above.

del

Deletes a file.

Syntax: del <file name>

Access level required: GROUP1 or above.

ll

List directory contents using long format, which includes the name, size, modification date, and modification time for each file. This command also displays the total disk space and free disk space.

Syntax: ll

Access level required: ANYUSER or above.

ls

List directory contents using the short format, which displays filenames, total disk space, and free disk space.

Syntax: ls

Access level required: ANYUSER or above.

pwd

Display the present working directory.

Syntax: pwd

Access level required: ANYUSER or above.

rename

Renames a file.

Syntax: rename <old file name> <new file name>

Access level required: GROUP1 or above.

whoami

Lists the login name for the current session.

Syntax: whoami

Access level required: ANYUSER or above.

Locating Software Updates

For information on locating software updates, refer to the Release Notes for Cisco MGX 8850 and MGX 8830 Software Version 3 (PXM45/B and PXM1E) or the Release Notes for Cisco MGX 8950 Software Version 3.

Copying Software Files to the Switch

This section describes how to copy software files to an MGX 8850 or MGX 8950 switch. The switch cards use boot software and runtime software. Each PXM45, AXSM, and FRSM-12 card uses the boot software to define communications between the card components and to enable cards to start up. The runtime sof