Specifications

A-40
Cisco MGX 8800/8900 Series Software Configuration Guide
Release 5.1, Part Number OL-6482-01, Rev. A0, January 25, 2005
Appendix A Downloading and Installing Software Upgrades
Upgrade Procedures for RPM-PR and RPM-XF Cards
Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you
can enter rommon mode and load the bootable image. To get into rommon mode, establish a console
connection to the RPM card, reset the RPM card using the resetcd <slot> command from the active
PXM card, then quickly enter the CTRL-[, Break sequence at the RPM console. The command to
send a Break depends on the computer platform and software you are using. It may take a couple of
attempts to successfully get into rommon mode. When you are in rommon mode, the RPM card
displays the rommon 1 > prompt.
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:
• The C:FW directory on the PXM hard disk
• Bootflash
• A TFTP server on a LAN to which an RPM back card is connected.
Note In this document, the general term “RPM” refers for both the RPM-PR and RPM-XF cards. If a step or
procedure is specific to only one of the RPM cards, it will be called out in the text.
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.T
boot system bootflash:rpm-js-mz_122-4.T
boot config c:auto_config_slot09
logging rate-limit console 10 except errors
enable password *****
!
Tip The c: reference in the previous example refers to the E:RPM directory on the PXM hard disk. When
configuring the RPM to store configuration files on E:RPM, enter commands that reference the e:
drive. When displaying the configuration, the e: drive is always displayed as c:.
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.