Guest

Cisco WAN Switching Modules

Field Notice: *Expired* FN - 14947 - Save RPM-PR Configuration When Used in 1:N Redundancy


Revised October 26, 2006

September 21, 2001

NOTICE:

THIS FIELD NOTICE HAS BEEN ARCHIVED AND IS NO LONGER MAINTAINED OR UPDATED BY CISCO.

THIS FIELD NOTICE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE, WARRANTY OR SUPPORT. USE OF THE INFORMATION ON THIS FIELD NOTICE OR MATERIALS LINKED FROM THIS FIELD NOTICE IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS FIELD NOTICE AT ANY TIME.


Products Affected

Product

MGX-RPM-PR-256

MGX-RPM-PR-512

Problem Description

Users should save the RPM-PR (Route Processor Module-PRemium) configuration to the PXM (Processor Switch Module) hard drive when used in the 1:N redundancy application. Failure to do so will result in the standby RPM-PR being unable to load the correct configuration.

Background

In the 1:N redundancy scheme, the standby RPM-PR must download the configuration of the protected RPM-PR off the PXM hard drive. This scheme requires that each RPM-PR that is part of a 1:N redundancy group have its configuration stored on the PXM hard drive. Each time the configuration of a protected RPM-PR is changed, either by adding or deleting connections or changing values, the changed configuration must be saved on the PXM hard drive.

For this Field Notice, it should be noted that the term "PXM" refers to any PXM1 model or any PXM45 model, as well as any future models or types of PXMs.

Problem Symptoms

Failure to constantly update the configuration file may result in the standby RPM-PR downloading an older configuration file and possibly losing network services or user connectivity.

Workaround/Solution

Save the configuration of each RPM-PR that is protected by a standby RPM-PR in a 1:N redundancy group.

After every addred (add redundancy), cc (change card) to the primary RPM and execute write mem (write memory) or copy running startup on the primary RPM. This will automatically create an auto_config_slot file (configuration file) on the PXM hard disk. Also, after any modification on the configuration files, the user must execute the write mem or copy running startup command on the active RPM, so that after any switchover, the new RPM will not have improper configurations.

The command sequence to use is:

  1. cc slot_number (where slot number is the primary RPM-PR slot)

  2. write mem OR copy running startup

The above two commands should be executed after each change in the configuration of any RPM-PR, whether it is a new connection added, enabling or disabling an ethernet port, or enabling or disabling partitions or MPLS functionalities, configuring IP address parameters.

For More Information

If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods:

Receive Email Notification For New Field Notices

Product Alert Tool - Set up a profile to receive email updates about reliability, safety, network security, and end-of-sale issues for the Cisco products you specify.