A-41
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide
Release 5.0.10, OL-3845-01 Rev. B0, August 16, 2004
Appendix A Downloading and Installing Software Upgrades
Upgrade Procedures for RPM-PR and RPM-XF Cards
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.
To configure the RPM to load upgraded runtime software from the PXM hard disk, you need to do the
following:
•
Copy the upgraded file to the PXM hard disk
•
Update the boot system variable in the router startup-config file to load the new file.
•
Reset the RPM card so that it loads the new file.
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
To simplify runtime software updates, copy the runtime file in the C:FW directory and rename it to
a generic name such as rpm-js-mz. The production runtime filenames have version numbers
appended to them, but you can change this. This approach allows you to perform future upgrades by
copying the file to the hard disk, renaming a copy of the file to your generic name, and resetting each
card. The approach eliminates the need to reconfigure Cisco IOS commands on each card to
recognize the new filename.
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
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.
