Downloading and Installing Software Upgrades
Available Languages
Table Of Contents
Downloading and Installing Software Upgrades
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
Non-Graceful PXM Runtime Software Downgrades
Non-Graceful AXSM Runtime Software Downgrades
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
Aborting a Runtime Software Upgrade
Committing to a Runtime Software Upgrade
Upgrade Procedures for RPM-PR and RPM-XF Cards
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:
•
Quickstart Procedures for Software Upgrades
•
•
•
•
•
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.
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.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.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.
2.
Note
Note
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.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00 should explain which software components require upgrading.
When you upgrade the software on a switch card, proceed as follows:
•
•
•
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
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
When a boot software upgrade is required, the procedure for upgrading redundant PXM cards is as follows:
1.
2.
3.
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
To upgrade the boot software, use the following procedure.
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 21
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
Caution
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
Caution
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.
1 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
When a boot software upgrade is required, the procedure for upgrading redundant PXM card is as follows:
1.
2.
3.
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
To upgrade the boot software, use the following procedure.
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
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
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
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.
2.
3.
Note
Caution
Note
To upgrade the runtime software, use the following procedure.
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.1.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00 call for a boot software upgrade, upgrade the boot software for the card you are upgrading.
Note
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
Note
Note
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.1.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.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
Note
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
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
Note
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
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
The following quickstart procedure describes how to upgrade boot and runtime software in one operation on redundant RPM cards.
Note
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
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
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.TStep 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.TStep 15
boot config e:auto_config_RPM-PR_slot#
Configure the RPM card to store its configuration on the PXM hard disk.
Note
Step 16
^Z
Exit global configuration mode.
Step 17
copy run start
Save the new configuration.
Note
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
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
The following quickstart procedure describes how to upgrade redundant RPM cards.
Note
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
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
The following quickstart procedure describes how to gracefully upgrade runtime software on redundant RPM cards.
Note
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
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.TStep 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.TStep 10
boot config e:auto_config_RPM-PR_slot#
Configure the RPM card to store its configuration on the PXM hard disk.
Note
Step 11
^Z
Exit global configuration mode.
Step 12
copy run start
Save the new configuration.
Note
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
Note
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.
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
Step 10
cc <active_PXM_slot>
resetcd <RPM_Slot>
This command sequence restarts the RPM card with the new boot image.
Non-Graceful RPM Runtime Software Upgrades
Use the non-graceful upgrade procedure in this section when you need to upgrade RPM runtime 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
Note
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 "Upgrade Procedures for RPM-PR and RPM-XF Cards," which appears later in this appendix.
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
Copy and rename the runtime file to a generic name for easy updates.
See the "Non-Graceful RPM Runtime Software Upgrades" section later in this chapter.
Note
Step 3
username
password
Establish a CLI session with the active PXM card using a user name at any access level.
Step 4
cc <RPM_Slot>
Select the slot in which the 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.TStep 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.TStep 10
boot config e:auto_config_RPM_slot#
Configure the RPM card to store its configuration on the PXM hard disk.
Note
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_PXM_slot>
resetcd <RPM_Slot>
This command sequence selects the active PXM card and restarts the RPM card with the new runtime image.
Step 14
dspcds
dspcd <RPMR_Slot>
cc <RPM_Slot>
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.
Note
The following sections provide quickstart procedures for the following downgrades:
•
•
PXM 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:
Caution
When upgrading a standalone card, the downgrade is non-graceful, and you should follow the following Graceful PXM Boot Upgrades from Release 3.0.10 and Later procedures.
Non-Graceful PXM Runtime Software Downgrades
To downgrade PXM 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 provides an overview for PXM runtime software downgrades.
Note
Step 1
username
password
Establish a CLI session with the active PXM card using a user name with SERVICE_GP privileges.
Step 2
saveallcnf
y
Save the current switch configuration.
See the "Saving a Configuration"section in Chapter 9, "Switch Operating Procedures."
This step gives you the option to upgrade to the software version from which you are downgrading and use the former configuration.
Step 3
ftp
Copy the boot and runtime files you want to use to the switch. Also copy the saved configuration file from the C:CNF directory to a remote workstation so you have a backup file if something happens to the hard disk.
See the "Copying Software Files to the Switch" section later in this appendix.
Step 4
clrallcnf
y
Clear the current configuration.
See the "Clearing a Switch Configuration" section in Chapter 9, "Switch Operating Procedures."
Step 5
sysVersionSet "version"
reboot 21
Select the runtime firmware version the switch will use on the PXM card and restart the switch with that firmware. For example:
sysVersionSet "002.001.000.000"Note that these commands must be entered at the PXM backup boot prompt: pxmbkup>.
See the "Initializing the Switch" section in Chapter 2, "Configuring General Switch Features.".
Step 6
Reconfigure the PXM cards as described in the "Configuration Quickstart" section in Chapter 2, "Configuring General Switch Features."
1 Beginning with Release 4.0, you must enter reboot 2. For all prior releases, enter reboot.
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 provides an overview of how to downgrade the AXSM software after the PXM45 runtime software has been downgraded.
Step 1
ftp
Copy the boot and runtime files you want to use to the switch.
See "Copying Software Files to the Switch," which appears later in this appendix.
Step 2
Refer to "Configuration Quickstart" "Preparing Service Modules for Communication."
The setrev command in the quickstart procedure clears the card configuration and assigns the downgrade software version to the card.
Browsing the File System
The PXM 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
Locating Software Updates
For information on locating software updates, see the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 and the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00.
Copying Software Files to the Switch
This section describes how to copy software files to a Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8830, or Cisco MGX 8950 switch. The switch cards use boot software and runtime software. Each card uses the boot software to define communications between the card components and to enable cards to start up. The runtime software defines how the card operates after startup. RPM cards function on the runtime software and use the boot software only when they cannot load the runtime software.
Note
Cisco MGX switches provide a File Transfer Protocol (FTP) service to support file transfers to the switch. If you have FTP client software and network connectivity to both the switch and the server where the software files are stored, you can use FTP to transfer files directly from the server to the switch.
Note
Step 1
Step 2
Tip
The procedure you use for transferring the files depends on the FTP client software you are using. When initiating the FTP connection, remember the following:
•
•
•
Step 3
Step 4
Step 5
For more information on browsing the switch file system, see the "Browsing the File System" section earlier in this appendix.
Upgrade Procedures for PXM Cards and Service Modules
The following sections describe procedures that support upgrades to PXM cards and to all service modules except the RPM family of cards. For complete upgrade procedures, see the "Quickstart Procedures for Software Upgrades" section, which appears earlier in this appendix. The procedures in this section detail some of the tasks listed in the quickstart procedures.
Upgrading PXM Boot Software from Releases Prior to 3.0.10
This section describes how to upgrade the PXM boot software on a single PXM card running a release prior to Release 3.0.10. If you are performing a graceful upgrade, use the quickstart procedure described in "Graceful PXM Boot Upgrades from Releases Prior to Release 3.0.10," which appears earlier in this appendix. The following procedure provides detailed information on the upgrade task within the quickstart procedure.
Step 1
Step 2
Step 3
pxm45bkup> sysFlashBootBurn "path/filename"
Caution
Replace filename with the complete path to the boot file on the PXM45 hard drive. For example:
pxm45bkup> sysFlashBootBurn "C:FW/pxm45_004.000.000.201_bt.fw"Step 4
When the boot code burning process is complete, the switch displays a message similar to the following example:
Flash download completed ...value = 0 = 0x0Step 5
pxm45bkup> reboot 2
Note
Be patient and wait for the Login prompt to appear.
Step 6
Step 7
The Boot FW Rev row in the display should show the new revision as shown in the following example:
8850_NY.7.PXM.a > dspcd8850_NY System Rev: 02.01 Mar. 04, 2001 22:47:23 PSTMGX8850 Node Alarm: NONESlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45 UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active Active ActiveSerial Number: SBK050302AF SBK045203PJ SBK044602HJPrim SW Rev: 3.0(0.0) --- ---Sec SW Rev: 3.0(0.0) --- ---Cur SW Rev: 3.0(0.0) --- ---Boot FW Rev: 4.0(0.0) --- ---800-level Rev: A0 A0 A0800-level Part#: 800-06147-08 800-05787-02 800-05052-04CLEI Code: BAA670YCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop:After you confirm the upgrade to the PXM card, the boot software upgrade for that card is complete.
Upgrading PXM Boot Software from Release 3.0.10 and Later
The upgrade procedure for the boot software on a single PXM card is the same for graceful and non-graceful upgrades. The difference between the graceful and non-graceful upgrades is the sequence of commands before and after the upgrade on a single card. For information on the proper sequence, see the "Graceful PXM Boot Upgrades from Release 3.0.10 and Later" section earlier in this appendix.
Note
To upgrade the boot software, use the following procedure.
Step 1
Step 2
Step 3
pop20one.7.PXM.a > burnboot <slot> <revision>
Caution
Replace <slot> with the slot number of a standalone PXM card, or a PXM card operating in standby mode. Replace <revision> with the software revision number to which you are upgrading. For example:
pop20one.7.PXM.a > burnboot 8 3.0(0.0)Step 4
After you confirm the upgrade, the new boot code is burned into the PXM and the card is reset. Be patient, the card reset takes some time. You can enter the dspcds command to display the status of the PXM card. At first, the status may show that the card slot is empty or the card is rebooting. Reenter the command periodically to see the current status of the card. When the card status returns to active or standby, you are ready to continue.
Step 5
M8950_SF.7.PXM.a > dspcd 7M8950_SF System Rev: 02.01 Feb. 04, 2004 19:25:26 GMTMGX8950 (JBP-2) Node Alarm: CRITICALSlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM45B UI Stratum3 PXM HardDiskDriveReserved Card: PXM45 UI Stratum3 PXM HardDiskDriveState: Active Active ActiveSerial Number: SAG053558VP SBK0449017Q SBK042700M6Prim SW Rev: 3.0(0.0) --- ---Sec SW Rev: 3.0(0.0) --- ---Cur SW Rev: 3.0(0.0) --- ---Boot FW Rev: 3.0(0.0) --- ---800-level Rev: A0 A0 A0800-level Part#: 800-09266-04 800-05787-02 800-05052-04CLEI Code: BAA53MZCAB BA7IBCLAAA BA7IADNAAAReset Reason: On Reset From ShellCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:Type <CR> to continue, Q<CR> to stop:After you confirm the upgrade to the PXM card, the boot software upgrade for that card is complete.
Upgrading Boot Software on Service Modules
The upgrade procedure for the boot software on a single service module is the same for graceful and non-graceful upgrades. The difference between the graceful and non-graceful upgrades is the sequence of commands before and after the upgrade on a single card. For information on the proper sequence for graceful upgrades, see the "Graceful Service Module Boot Software Upgrades" section earlier in this appendix.
To upgrade service module boot software, use the following procedure.
Step 1
Step 2
Step 3
pop20one.7.PXM.a > burnboot <slot> <revision>
Caution
Replace <slot> with the slot number of a standalone service module or service module operating in standby mode. Replace <revision> with the software revision number to which you are upgrading. For example:
pop20one.7.PXM.a > burnboot 1 3.0(0.0)Step 4
After you confirm the upgrade, the new boot code is burned into the service module and the card is reset. Be patient, the card reset takes some time. You can enter the dspcds command to display the status of the card. At first, the status may show that the card slot is empty or the card is rebooting. Reenter the command periodically to see the current status of the card. When the card status returns to active or standby, you are ready to continue.
Step 5
8850_NY.7.PXM.a > dspcd 18850_NY System Rev: 02.01 Mar. 04, 2001 22:58:22 PSTMGX8850 Node Alarm: NONESlot Number: 1 Redundant Slot: NONEFront Card Upper Card Lower Card---------- ---------- ----------Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12Reserved Card: AXSM_4OC12 SMFIR_2_OC12 UnReservedState: Active Active ActiveSerial Number: SAK0344001V SBK0406002K SAK032800Q6Prim SW Rev: 3.0(0.0) --- ---Sec SW Rev: 3.0(0.0) --- ---Cur SW Rev: 3.0(0.0) --- ---Boot FW Rev: 3.0(0.0) --- ---800-level Rev:800-level Part#: 800-05774-05 800-05383-01 800-05383-01CLEI Code: 1234567890 BAI9ADTAAA 0Reset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous Information:After you confirm the upgrade to the service module, the boot software upgrade for that card is complete.
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 > dspcd8850_NY System Rev: 02.01 Mar. 04, 2001 22:47:23 PSTMGX8850 Node Alarm: NONESlot Number 7 Redundant Slot: 8Front Card Upper Card Lower Card---------- ---------- ----------Inserted Card: PXM1E UI Stratum3 PXM HardDiskDriveReserved Card: PXM1E UI Stratum3 PXM HardDiskDriveState: Active Active ActiveSerial Number: SBK050302AF SBK045203PJ SBK044602HJPrim SW Rev: 4.0(0.0) --- ---Sec SW Rev: 4.0(0.0) --- ---Cur SW Rev: 4.0(0.0) --- ---Boot FW Rev: 4.0(0.0) --- ---800-level Rev: A0 A0 A0800-level Part#: 800-06147-08 800-05787-02 800-05052-04CLEI Code: BAA670YCAA BA7IBCLAAA BA7IADNAAAReset Reason: On Power upCard Alarm: NONEFailed Reason: NoneMiscellaneous 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 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.
For non-graceful upgrades, the load process defines the software version to which the switch is about to be upgraded. Table A-3 shows how the revision levels change during a non-graceful upgrade.
If you are performing a graceful upgrade, use the quickstart procedure described in the "Graceful PXM and Service Module Runtime Software Upgrades" section earlier in this appendix. The following procedure provides detailed information on the load task within the quickstart procedure.
Step 1
mgx8850a.7.PXM.a > loadrev <slot> <revision>Replace <slot> with the card slot number for the card to be upgraded, and replace <revision> with the software version number for the update. For graceful upgrades, you can specify either the active or the standby card. The switch software will automatically load the upgrade software on the standby card when it is installed. The following example shows how to enter this command:
mgx8850a.7.PXM.a > loadrev 7 4.0(0.0)After you enter the loadrev command, the standby card comes up in the standby-U state.
You can find the software version number in the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.1.00 or the Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.1.00. You can also determine the version number from the runtime software filename as described in the "Determining the Software Version Number from Filenames" section in Chapter 9, "Switch Operating Procedures."
Step 2
Step 3
Note
Starting the Upgrade Software
After you load the runtime upgrade software for a PXM or service module, enter the runrev command to start using the software. The version levels for graceful and non-graceful upgrades change as shown earlier in Table A-2 and Table A-3. The following procedure describes how to start the upgrade software.
Step 1
mgx8850a.7.PXM.a > runrev <slot> <revision>Replace <slot> with the card slot number, and replace <revision> with the software version number specified with the loadrev command. For graceful upgrades, you can specify either the active or the standby card. The switch software will automatically run the upgrade software on the standby card when it is installed. The following example shows how to enter this command:
mgx8850a.7.PXM.a > runrev 7 4.0(0.0)The active card is reset, and the former standby card comes up in the active-U state.
Step 2
Step 3
Step 4
After the runrev command is entered, the switch starts running the new software revision. The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision as described in the "Aborting a Runtime Software Upgrade" section later in this appendix.
Aborting a Runtime Software Upgrade
After upgrading PXM or service module runtime software, you can revert to the previously used version of software as long as you have not used the commitrev command to finalize the upgrade. The commitrev command is described in the next section.
Keep the following in mind when you use the abortrev command to abort the new runtime software during an upgrade:
•
•
•
•
•
Caution
To revert to the previously used runtime software version, use the following procedure.
Step 1
Step 2
Replace slot with the slot number of the active card. To complete the next step, you need to know the secondary software revision shown in the display.
Note
Step 3
mgx8850a.7.PXM.a > abortrev <slot> <revision>Replace <slot> with the card slot number for the active card, and replace <revision> with the software version number for the secondary software revision.
Step 4
Committing to a Runtime Software Upgrade
Committing to an upgrade does the following:
•
•
Once you are sure that an upgrade is stable, you can use the commitrev command commit to that software version. Committing to the current software version prevents other administrators from inadvertently reverting to the previous version. You must also commit to the current software version before you can upgrade to another software version.
To commit to the currently running runtime software version, use the following procedure.
Step 1
Step 2
a.
b.
c.
If all version numbers are identical, the runtime software can be upgraded. There is no need to commit to the current software revision.
Step 3
mgx8850a.7.PXM.a > commitrev <slot> <revision>Replace <slot> with the card slot number for the active card, and replace <revision> with the software version number for the currently used software version. To display the software version number, use the dspcd <slot> command to view the software version in use. You can also view the revision levels with the dsprevs command.
Note
Upgrade Procedures for RPM-PR and RPM-XF Cards
The following sections describe how to upgrade boot and runtime software on RPM-PR and RPM-XF cards.
Note
Upgrading RPM Boot Software
At the factory, a boot file is installed in the bootflash on the RPM card and is used to boot the card. The runtime software is updated more frequently than the boot software. However, the boot software is updated occasionally. When you are updating runtime software, check the release notes that accompany the runtime software to see if a boot software upgrade is required.
The boot software is stored in bootflash memory on the RPM card. To manage the software in bootflash, you access it as if it were a hard disk. For example, in copy and delete file commands, files are identified as bootflash:filename (which is similar to x:filename).
The following example shows a directory of bootflash contents:
Router(boot)#show flash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .D config D4F7352A 40330 18 686 Jan 30 2001 18:18:41 auto_config_slot092 .D config CBF007C1 40660 9 688 Feb 22 2001 15:33:11 slot9.cnf3 .. image F596869A 2973E8 27 2452744 Feb 28 2001 03:16:05 rpm-boot-mz_002.001.000.000
Note
In the example above, the numbers in the left column indicate the order in which the RPM will try to load software. The second column shows that the first two files are marked for deletion (D). The last column lists the names of the files stored in bootflash.
When managing the bootflash, consider the following facts:
•
•
•
•
•
Caution
If you do need to upgrade the boot software, you can copy the new boot file to the PXM disk, and then copy it to the bootflash. The following procedure describes how to upgrade the boot software.
Step 1
Tip
Step 2
Step 3
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the Cisco IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note
Step 4
Router>enablePassword:Router#Step 5
Router#dir x:Directory of x:/0 -rw- 2253552 May 11 2004 15:47:06 +00:00 mpsm_t1e1_030.000.004.016-P2.fw0 -rw- 10655280 Apr 2 2004 08:46:30 +00:00 rpm-js-mz.123-2.T50 -rw- 3350304 Apr 2 2004 08:46:12 +00:00 rpm-boot-mz.123-2.T50 -rw- 1431512 May 11 2004 15:47:00 +00:00 mpsm_t1e1_030.000.004.016-P1_bt.fw0 -rw- 1030532 May 11 2004 15:46:42 +00:00 frsm_vhs_022.000.005.019-A.fw0 -rw- 891552 May 11 2004 15:46:38 +00:00 frsm_8t1e1_022.000.005.019-A.fw0 -rw- 303936 May 11 2004 15:46:30 +00:00 cesm_t3e3_CE8_BT_1.0.02.fw0 -rw- 641312 May 11 2004 15:46:28 +00:00 cesm_t3e3_022.000.005.019-A.fw0 -rw- 743136 May 11 2004 15:46:24 +00:00 cesm_8t1e1_022.000.005.019-A.fw0 -rw- 826392 May 11 2004 15:38:56 +00:00 vxsm_005.000.004.034-A_bt.fw0 -rw- 10528336 May 11 2004 15:38:44 +00:00 vxsm_005.000.004.034-A.fw0 -rw- 7939476 May 11 2004 15:38:06 +00:00 pxm45_005.000.004.034-A_mgx.fw0 -rw- 1160328 May 11 2004 15:37:54 +00:00 pxm45_005.000.004.034-A_bt.fw0 -rw- 468388 May 11 2004 15:46:46 +00:00 frsm_vhs_VHS_BT_1.0.06.fw0 -rw- 1245112 May 11 2004 15:37:42 +00:00 mpsm155_005.000.004.034-P1_bt.fw0 -rw- 4069552 May 11 2004 15:37:36 +00:00 mpsm155_005.000.004.034-P1.fw0 -rw- 737896 May 11 2004 15:37:20 +00:00 frsm12_005.000.004.034-A_bt.fw0 -rw- 2490064 May 11 2004 15:37:14 +00:00 frsm12_005.000.004.034-A.fw0 -rw- 3674368 May 11 2004 15:36:54 +00:00 axsmxg_005.000.004.034-P1.fw0 -rw- 838840 May 11 2004 15:36:46 +00:00 axsmxg_005.000.004.034-A_bt.fw0 -rw- 742168 May 11 2004 15:36:44 +00:00 axsme_005.000.004.034-A_bt.fw0 -rw- 297988 May 11 2004 15:46:40 +00:00 frsm_8t1e1_FR8_BT_1.0.02.fw0 -rw- 264592 May 11 2004 15:46:26 +00:00 cesm_8t1e1_CE8_BT_1.0.02.fw0 -rw- 3111904 May 11 2004 15:36:38 +00:00 axsme_005.000.004.034-A.fw0 -rw- 744600 May 11 2004 15:36:32 +00:00 axsm_005.000.004.034-A_bt.fw0 -rw- 3267520 May 11 2004 15:36:22 +00:00 axsm_005.000.004.034-A.fw0 -rw- 248686 May 11 2004 15:32:56 +00:00 vism_8t1e1_VI8_BT_3.2.00.fw0 -rw- 4135448 May 11 2004 15:32:52 +00:00 vism_8t1e1_003.053.103.007-I.fw0 -rw- 4135000 May 11 2004 15:32:42 +00:00 vism_8t1e1_003.003.103.007-I.fw838616064 bytes total (721004544 bytes free)Step 6
Router#show flash:-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05 rpm-boot-mz_122-4.T30315128 bytes available (2452872 bytes used)Step 7
Router#copy x:rpm-boot-mz_002.001.000.000 bootflash:Destination filename [rpm-boot-mz_002.001.000.000]?CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCC2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tip
Step 8
Step 9
a.
Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.b.
Router(config)#boot bootldr bootflash:rpm-boot-mz_002.001.000.000c.
Router(config)#^ZRouter#copy run startDestination filename [startup-config]?Building configuration...[OK]d.
RPM-XF#show bootvarBOOT variable = bootflash:rpmxf-......CONFIG_FILE variable =BOOTLDR variable = bootflash:rpm-boot-mz_002.001.000.000Configuration register is 0x2Step 10
a.
Router#copy bootflash:filename x:filenameb.
Router#del bootflash:Delete filename []? rpm-js-mzDelete bootflash:rpm-js-mz? [confirm]Router#
Tip
c.
Router(boot)#squeeze flash:All deleted files will be removed. Continue? [confirm]ySqueeze operation may take a while. Continue? [confirm]Squeeze of bootflash completed.
Router#copy x:filename bootflash:filenameYou might want to copy previously saved configuration files back to bootflash, or you might want to copy an older boot image to be used if the newer version becomes corrupt.
e.
Caution
Tip
Step 11
Tip
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command using the following format: boot bootflash:filename.
Upgrading RPM Runtime Software
The runtime software on the RPM-PR and RPM-XF cards can be loaded from the following sources:
•
•
•
Note
Cisco Systems recommends that you configure the RPM card to load from the C:FW directory on the PXM hard disk. Images will load much faster from bootflash, but if you are using multiple RPM cards, it takes longer to complete an upgrade because the runtime software must be copied to each RPM card's bootflash instead of to a single location.
At startup, the RPM card attempts to load the software in the order listed in the startup-config file. The following example shows an excerpt from a startup-config file:
!boot system x:rpm-js-mz_122-4.Tboot system bootflash:rpm-js-mz_122-4.Tboot config c:auto_config_slot09logging rate-limit console 10 except errorsenable password *****!
Tip
In the startup-config file example, the RPM card attempts to load the runtime software from the PXM card (x:rpm-js-mz_122-4.T) first, and if that fails, it attempts to load the image copy stored in bootflash. This configuration takes longer to upgrade, but it assures the card can reboot if someone accidentally removes the file on the PXM hard disk.
To configure the RPM to load upgraded runtime software from the PXM hard disk, you need to do the following:
•
•
•
RPM cards can be configured for 1:N redundancy as well as for non-redundant configurations. The procedures for both types of configuration are in the sections that follow.
Tip
Upgrading RPM Runtime Software for 1:N Redundancy
Redundancy must be established before you use the procedure in this section. If redundancy has not been established, upgrade each RPM card using the procedure in the next section, "Upgrading Without Redundancy".
Note
To upgrade the RPM runtime software for 1:N redundancy, use the following procedure.
Step 1
Step 2
8850_LA.8.PXM.a > copy rpm-js-mz_122-4.T rpm-js-mzStep 3
Step 4
Step 5
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the Cisco IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note
Step 6
Router>enablePassword:Router#Step 7
Router#show bootvarBOOT variable = x:rpm-js-mz_122-4.T,12;CONFIG_FILE variable = c:auto_config_slot09BOOTLDR variable does not existConfiguration register is 0x2In the example above, the startup runtime software file is x:rpm-js-mz_122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 8
Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.Step 9
Router(config)# no boot systemStep 10
Router(config)# boot system x:filenameReplace the filename variable with the name of the new runtime file that was previously transferred to the C:FW directory on the switch. For example:
Router(config)# boot system x:rpm-js-mzIf you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM hard disk:
Router(config)# boot system bootflash:rpm-js-mz_122-4.T
Note
Step 11
Router(config)#^ZRouter#copy run startDestination filename [startup-config]?Building configuration...[OK]Step 12
Step 13
Router#cc 8(session redirected)8850_LA.8.PXM.a > resetcd 9The card in slot number 9, will be reset. Please confirm actionresetcd: Do you want to proceed (Yes/No)? yStep 14
8850_LA.8.PXM.a > switchredcd <fromSlot> <toSlot>Replace <fromSlot> with the slot number of the primary card. Replace <toSlot> with the slot number of the secondary card.
This step makes the secondary card active and resets the primary RPM card. When the primary card resets, it loads the upgraded software.
Step 15
8850_LA.8.PXM.a > switchredcd <fromSlot> <toSlot>Replace <fromSlot> with the slot number of the secondary card. Replace <toSlot> with the slot number of the primary card.
This step makes the primary card active and resets the secondary RPM card. When the reset is complete, the secondary card is ready to run the upgraded software.
Step 16
Step 17
Upgrading RPM Runtime Software for Non-Redundant Cards
To upgrade the RPM-PR or RPM-XF runtime software for nonredundant cards, use the following procedure.
Note
Step 1
Tip
Step 2
8850_LA.8.PXM.a > copy rpm-js-mz_122-4.T rpm-js-mzStep 3
Step 4
Step 5
pop20two.7.PXM.a > cc 9(session redirected)Router>The switch displays the Cisco IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note
Step 6
Router> boot config e:auto_config_slot#Step 7
Router>enablePassword:Router#Step 8
Router#show bootvarBOOT variable = x:rpm-js-mz_122-4.T,12;CONFIG_FILE variable = c:auto_config_slot09BOOTLDR variable does not existConfiguration register is 0x2In the example above, the startup runtime software file is x:rpm-js-mz_122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 9
Router#config terminalEnter configuration commands, one per line. End with CNTL/Z.Step 10
Router(config)# no boot systemStep 11
Router(config)# boot system x:filenameReplace the filename variable with the name of the new runtime file that was previously transferred to the C:FW directory on the switch. For example:
Router(config)# boot system x:rpm-js-mzIf you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM hard disk:
Router(config)# boot system bootflash:rpm-js-mz_122-4.T
Note
Step 12
Router(config)#^ZRouter#copy run startDestination filename [startup-config]?Building configuration...[OK]Step 13
Step 14
Router#cc 8(session redirected)8850_LA.8.PXM.a > resetcd 9The card in slot number 9, will be reset. Please confirm actionresetcd: Do you want to proceed (Yes/No)? y
Troubleshooting Upgrade Problems
Table A-4 lists symptoms of upgrade problems and suggestion on how to correct them.
Tip
Table A-4 Troubleshooting Upgrade Problems
loadrev or runrev command fails
—
The loadrev command is blocked when a previous upgrade has not been completed with the commitrev command. Enter the dsprevs command to locate the cards that are still being upgraded.
For more information on a particular card, enter the dspcd <slot> command and verify that the current, primary, and secondary software revision numbers are identical. If the numbers are not identical, issue the commitrev <slot> command.
Enter the dspcds and verify that the standby card is in standby state. Also look for a -U or -D in the dspcds command display, which indicates that the card is in the process of being upgraded (-U) or downgraded (-D). The loadrev and runrev commands are blocked whenever the standby card is not in standby state or an upgrade or downgrade is in progress.
After restart, the switch stops displaying messages and does not display a prompt.
—
Press Return to display the prompt.
After restart, switch stops at backup boot prompt: pxm1ebkup> or pxm45bkup.
(Use a console port connection to see this. If you missed the startup messages, enter the reboot 21 command.)
The switch displays the following message: Can not open file C:/version.
The version file is probably missing. Create the version file as described in the "Initializing the Switch" section in Chapter 2, "Configuring General Switch Features."
The switch displays the following message: Unable to determine size of C:/FW/filename.
The version recorded in the version file doesn't match software installed in the C:FW directory.
Enter the sysVersionShow command to see which file the PXM is trying to load.
Verify that the correct software is installed on the switch using the commands described in the "Browsing the File System in Backup Boot Mode" section in "PXM Backup Boot Procedures."
If the runtime software is not on the hard disk, copy it to the hard disk as described in the "Transferring Software Files to and from the Switch" section in "PXM Backup Boot Procedures."
If a typo is entered when initializing the switch, re-enter the sysVersionSet command, enter the sysVersionShow command to verify the correct setting, and then reboot the switch with the reboot 21 command.
The switch displays the following message: Please run sysDiskCfgCreate.
The hard disk is formatted, but not ready for operation. Enter the sysDiskCfgCreate command. For more information, see the "Initializing the PXM Hard Disk" section in "PXM Backup Boot Procedures."
Standby PXM continually reboots.
You can view the rebooting process through the console port.
—
The active PXM card cannot bring up the standby card. The following procedure assumes that this card has just been installed in the switch and that you have given the standby card sufficient time to synchronize with the Active card.
Interrupt the boot cycle by pressing Return. Timing is important, so you might have to press Return multiple times. When the pxm1ebkup or pxm45bkup prompt appears, immediately enter the sysPxmRemove command to prevent the Active card from rebooting the standby card while you are working on it.
Enter the sysChangeEnet command and verify that the inet on ethernet (e) and gateway inet (g) values are set to the boot and gateway IP address set with the bootChange command on the active card. Also, verify that the boot device is set to lnPci. The sysChangeEnet command works like the bootChange command, which is described in the "Setting the Boot IP Address" section in Chapter 2, "Configuring General Switch Features."
Enter the sysClrallcnf command to clear any configuration data on the standby card set. This command does not clear the boot IP address set with the sysChangeEnet command.
After restart, the switch stops at shell prompt: pxm1e> or pxm45>.
—
If the Return key is pressed at one of the auto-boot prompts during start up, the switch stops in shell mode. Enter the reboot 21 command to restart the switch and avoid pressing the Return key.
The non-active PXM will not transition out of the active init state.
One or more non-standby PXM cards are in a transitional state.
A non-standby PXM card is a standalone PXM card or the card within a redundant PXM pair that is trying to go active. When a non-standby PXM card is in a transitional state, such as the init state, the PXM cannot transition to the standby state. When all non-standby cards have reached a steady (non-transitional) state, the PXM will transition to a steady state. Steady states are as follows: active ready, failed, mismatch, empty, empty reserved, and standby ready.
Note
1 Beginning with Release 4.0, you must enter reboot 2. For all prior releases, enter reboot.
Feedback