Cisco Cisco MGX 8880 Media Gateway Release Notes

Page of 82
 
46
Release Notes for Cisco MGX Route Processor Module (RPM-XF) for PXM45-based Switches Release 5.4.00
OL-11808-01
  Notes and Cautions
The saveallcnf command (issued on the PXM45/B card) captures configuration data saved by the 
RPM-XF card, as well as AXSM and PXM45 cards, and saves it on the active PXM45/B card’s hard 
disk. Configure the RPM-XF to store its configuration on the PXM45/B hard disk (E:/RPM) by 
entering boot config e:auto_config_slot# in the running configuration of the RPM-XF. To ensure 
that the saved file contains the latest RPM-XF configuration, execute the write mem command on 
each RPM-XF card before you enter the saveallcnf command. This also ensures that the RPM-XF 
files on the active PXM45 hard disk contain the latest configuration to be saved.
RPM-XF auto_config File Management
The RPM-XF auto_config_slot# file stores the configuration for the RPM-XF card. Set the slot# portion 
of the name to the logical slot number that corresponds to the RPM-XF card. This file can be stored in 
bootflash or in the E:RPM directory on the PXM45 hard disk. The configuration is also stored in 
nonvolatile RAM (NVRAM) using the name startup-config.
When the RPM-XF card is inserted or rebooted, it searches for the configuration file in the following 
sequence:
1.
If there is an auto_config file corresponding to its logical slot on the PXM45 hard disk, the RPM-XF 
card uses the configuration stored on the hard disk.
2.
If the boot variable points to configuration stored in the PXM45 hard disk or bootflash, and if the 
file is not found, the card comes up as active-F with the default configuration.
3.
If there is no auto_config file on the hard disk, the NVRAM version is used. 
Note
In case of RPM-XF redundancy, store the configuration in the auto_config_slot# file in the 
E:RPM directory of the PXM45 hard disk. Failure to find the autoconfig file causes a 
user-initiated switchover (switchredcd) to abort and a fatal error is flagged.
Card Management
Before you use Release 12.3(11)T7, review the following card management notes and cautions:
There is a new stable state displayed on the PXM dspcds command—Boot-Hold, which signifies 
that the RPM-XF is running the boot image only. On the RPM-XF, the prompt displays as boot>.
The run-time Cisco IOS image cannot be used as a bootloader to load a different Cisco IOS image. 
Changing the console speed on the terminal server may cause the card to end up in the ROMmon 
state. To avoid this, set the config register to 0x2102.
Another workaround is to enter cont on the ROMmon within 2 minutes of going into ROMmon state. 
This brings the card to its original stable state.
Note
We recommend you always use 9600 baud as the console speed.
The Cisco IOS version of the run-time as well as the boot image is displayed in the dspcddsprevs
and dsprevs -s output. The version is displayed under the heading of Cisco IOS version. Revision 
Control is not available for RPM-XF (like RPM-PR).
Note
The loadrev and setrev commands do not apply for RPM-XF.