Cisco MGX 8800 Series Switches

Table Of Contents

Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(11)T7 for MGX Releases 1.3.12 and 5.2.00

Contents

Overview

About This Release

New Features in MGX Release 1.3.12 or Earlier

Features Introduced in Cisco IOS Release 12.3(11)T7 for MGX Release 1.3.12

Features Introduced in Cisco IOS Release 12.3(11)T6 for MGX Release 1.3.12

Features Introduced in Cisco IOS Release 12.3(11)T3 for MGX 1.3.12

Features Introduced in Cisco MGX 8800 Release 1.2.21

Previously Released Features

Automatic Cell Bus Clocking

VISM-PR to RPM-PR Connectivity

Configuring the Cell Bus Clock Rate

LDP on RPM-PR Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1

Multi-LVC on RPM-PR Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1

Bypass Feature for RPM-PR in Cisco IOS Release 12.2(4)T

Features Not Supported in This Release

RPM-PR Redundancy Support

SNMP MIB

Notes and Cautions

Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT

UPC Connection Parameters

Booting the RPM-PR

RPM-PR Bootflash Precautions

Solving the RPM-PR Bandwidth Issue When Adding a 12th VISM Card

Limitations and Restrictions

CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards

RPM/B and RPM-PR Front Card Resets on the Back Card Removal

RPM/B and RPM-PR Back Ethernet Card Support

MGX-RPM-128M/B Ethernet Back Card Support

RPM/B and RPM-PR Limitations and Restrictions for MGX Release 1.3.12

Open Caveats

Open Caveats in Release 12.3(11)T7 for MGX 1.3.12

Open Caveats in Release 12.3(11)T6 for MGX 1.3.12

Open Caveats in Release 12.3(11)T3 for MGX 1.3.12

Open Caveats in Release 12.3(7)T3 for MGX 1.3.10

Resolved Caveats

Resolved Caveat in Release 12.3.(11)T7 for MGX 1.3.12

Resolved Caveats in Release 12.3(11)T6 for MGX 1.3.12

Resolved Caveats in Release 12.3(11)T3 for MGX 1.3.12

Resolved Caveats in Release 12.3(7)T3 for MGX 1.3.10

Resolved Caveats in Release 12.3(2)T6 for MGX 1.3.00

Resolved Caveats in Release 12.3(2)T5 for MGX 1.3.00

Compatibility Notes

RPM-PR Boot File and Firmware File Names and Sizes

RPM-PR Compatibility Matrix

MGX RPM/B and RPM-PR Hardware

Previous Cisco IOS Release Compatibility Information

About Cisco IOS Release 12.2(15)T5

About Cisco IOS Release 12.2(11)T1

About Cisco IOS Release 12.2(8)T4

About Cisco IOS Release 12.2(8)T1

About Cisco IOS Release 12.2(4)T3

About Cisco IOS Release 12.2(4)T1

About Cisco IOS Release 12.2(4)T

About Cisco IOS Releases 12.2(2)T2 and 12.2(2)T3

About Cisco IOS Release 12.1(5.3)T_XT

Caveats Fixed with Cisco IOS Release 12.1(5.3)T_XT

Special Installation and Upgrade Requirements

Upgrading from an MGX-RPM-128M/B Card to an RPM-PR Card

Upgrading RPM-PR Cards in MGX PXM1 Switches

Upgrading RPM-PR Boot Software

Upgrading RPM-PR Run-Time Software

Upgrading Boot Software and Run-Time Software for Non-Redundant Cards

Upgrading RPM-PR Boot Software and Run-Time Software for 1:N Redundancy

Using XModem to Download Flash to RPM-PR Cards

New Features in MGX Release 5.2.00 or Earlier

Features Introduced in Cisco IOS Release 12.3(11)T7 for MGX Release 5.2.00

Features Introduced in Cisco IOS Release 12.3(11)T6 for MGX Release 5.1.20

Features Introduced in Cisco IOS Release 12.3(11)T4 for MGX Release 5

1FECP Back Card Support

OIR Commands

Features Introduced in Cisco MGX 8800 Release 4.0.10

Previously Released Features

RPM-PR Image Directory Change From E:RPM to C:/FW

Automatic Cell Bus Clocking

dspcd Command—New Fields

Switching from Active to Standby—switchredcd Command with RPM-PR Cards

VISM-PR to RPM-PR Connectivity

Configuring the Cell Bus Clock Rate

Enabling LDP on RPM-PR in Cisco MGX 8850 and MGX 8950 Switches

Multi-LVC on RPM-PR in Cisco MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T1

MPLS over ATM using VC Merge in Cisco MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T

Bypass Feature for RPM-PR in Cisco IOS Release 12.2(4)T

Features Not Supported in This Release

RPM-PR Redundancy Support

SNMP MIB

Notes and Cautions

UPC Connection Parameters

Booting the RPM-PR

RPM-PR Bootflash Precautions

CLI Modifications in MGX Release 5.1.00

Limitations and Restrictions

CWM Recognition of RPM-PR Back Card

RPM-PR Front Card Resets on the Back Card Removal

RPM-PR Back Ethernet Card Support

RPM-PR Limitations and Restrictions for PXM45 and PXM1E

Open Caveats

Open Caveats in Release 12.3(11)T7 for MGX Release 5.2.00

Open Caveats in Release 12.3(11)T6 for MGX Release 5.1.20

Open Caveats in Release 12.3(11)T3 for MGX Release 5.1.00

Open Caveats in Release 12.3(7)T3 for MGX Release 5.0.10

Resolved Caveats

Resolved Caveat in Release 12.3(11)T7 for MGX Release 5.2.00

Resolved Caveats in Release 12.3(11)T6 for MGX Release 5.1.20

Resolved Caveats in Release 12.3(11)T3 for MGX Release 5.1.00

Resolved Caveats in Release 12.3(7)T3 for MGX Release 5.0.10

Resolved Caveats in Release 12.3(2)T6 for MGX Release 5.0.00

Resolved Caveats in Release 12.3(2)T5 for MGX 5.0.00

Compatibility Notes

RPM-PR Boot File and Firmware File Names and Sizes

RPM-PR Compatibility Matrix

MGX RPM-PR Hardware

Previous Cisco IOS Release Compatibility Information

About Cisco IOS Release 12.2(11)T1

About Cisco IOS Release 12.2(8)T4

About Cisco IOS Release 12.2(8)T1

About Cisco IOS Release 12.2(4)T3

About the Cisco IOS Release 12.2(4)T1

About the Cisco IOS Release 12.2(4)T

Special Installation and Upgrade Requirements

Upgrading RPM-PR Cards in MGX 8000 Releases 2.1 and 3 (PXM45 and PXM1E) Switches

Upgrading RPM-PR Boot Software

Upgrading RPM-PR Run-Time Software

Upgrading Boot Software and Run-Time Software for Non-Redundant Cards

Upgrading RPM-PR Cards in MGX 8000 Series Release 4 (PXM45 and PXM1E) Switches

Using XModem to Download Flash to RPM-PR Cards

Related Documentation

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(11)T7 for MGX Releases 1.3.12 and 5.2.00

---

These notes are Part Number OL-8162-01 Rev. A0, September 30, 2005.

Contents

Overview

These release notes contain the following sections:

•"About This Release" section

•"New Features in MGX Release 1.3.12 or Earlier" section

•"Previously Released Features" section

•"Features Not Supported in This Release" section

•"RPM-PR Redundancy Support" section

•"SNMP MIB" section

•"Notes and Cautions" section

•"Limitations and Restrictions" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Compatibility Notes" section

•"MGX RPM/B and RPM-PR Hardware" section

•"Previous Cisco IOS Release Compatibility Information" section

•"Special Installation and Upgrade Requirements" section

•"New Features in MGX Release 5.2.00 or Earlier" section

•"Previously Released Features" section

•"Features Not Supported in This Release" section

•"RPM-PR Redundancy Support" section

•"SNMP MIB" section

•"Notes and Cautions" section

•"Limitations and Restrictions" section

•"Open Caveats" section

•"Resolved Caveats" section

•"Compatibility Notes" section

•"MGX RPM-PR Hardware" section

•"Previous Cisco IOS Release Compatibility Information" section

•"Special Installation and Upgrade Requirements" section

•"Related Documentation" section

•"Obtaining Documentation" section

•"Documentation Feedback" section

•"Cisco Product Security Overview" section

•"Obtaining Technical Assistance" section

•"Obtaining Additional Publications and Information" section

About This Release

These maintenance release notes describe the system requirements, new features, and limitations that apply to the Cisco Media Gateway Switch (MGX) Route Processor Module-PR Cisco IOS Release 12.3(11)T7 for MGX Releases 1.3.12 and 5.2.00.

These notes also contain Cisco support information. For more information on the RPM-PR with MGX Release 5.2, refer to the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 5.2.

For MGX Release 1.3.12, the user documentation (command reference, overview, and installation and configuration guides) were not updated. Use the Release 1.1.3 and 1.2.10 documents in addition to this release note.

For product documentation about Cisco MGX 8850 switches, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/12/index.htm

For product documentation about Cisco MGX 8250 switches, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/12/index.htm

For product documentation about Cisco MGX 8230 switches, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/12/index.htm

For product documentation about VISM Version 3.0(0), go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/

For product documentation about RPM-PR Release 2.1 and these release notes, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/12/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/12/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/12/rpm/index.htm

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

New Features in MGX Release 1.3.12 or Earlier

This section lists new features introduced by release for Cisco IOS Release 12.3(11)T7 for MGX 1.3.12 or earlier releases.

Features Introduced in Cisco IOS Release 12.3(11)T7 for MGX Release 1.3.12

No new features are introduced with this release.

Features Introduced in Cisco IOS Release 12.3(11)T6 for MGX Release 1.3.12

No new features are introduced with this release.

Features Introduced in Cisco IOS Release 12.3(11)T3 for MGX 1.3.12

No new features are introduced with this release.

Features Introduced in Cisco MGX 8800 Release 1.2.21

The RPM-PR in Cisco MGX 8800 Release 1.2.21 supports all new and existing features introduced in the Release 1.2.x baseline. The following four new features were introduced for RPM-PR implementations using Cisco IOS Release 12.2(15)T5:

1. Multiprotocol Label Switching (MPLS) CoS Transparency—This feature allows the service provider to set the MPLS experimental field instead of overwriting the value in the customer's IP precedence field. The IP header remains available for customer use; the IP packet's CoS is not changed as the packet travels through the MPLS network.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdtmode.htm

2. cRTP with MQC—Modular Quality of Service (QoS) Command-Line Interface (CLI). An RPM-PR in Cisco MGX 8800 Release 1.2.21 supports using the MQC to configure the compressed Real-Time Protocol (cRTP) header. The CLI commands introduced to support this feature include:

–ip rtp header-compression—Enables RTP header compression for a particular interface.

–no ip rtp header-compression—Disables RTP header compression for a particular interface.

–clear ip rtp header-compression <interface>—Resets all statistics for the interface to 0.

–show ip rtp header-compression <interface> [detail]—Shows all statistics for an interface.

–show policy-map int sw1.x—Shows the number of packets which are compressed because of a match in policy map.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthdrcmp.htm

3. Label Switch Controller (LSC) Redundancy

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px1e/rel4/scg/rpm.htm

4. MVPN—The frame-based Multicast Virtual Private Network (MVPN) feature enables the RPM-PR in Cisco MGX 8800 Release 1.2.21 to pass frame-based multicast traffic to VPNs across the ATM core.

For configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mvpn.htm

Previously Released Features

This section lists previously released features for Cisco IOS Release 12.3(11)T7 for MGX Release 1.3.12 or earlier releases.

Automatic Cell Bus Clocking

To implement automatic cell bus clocking, an -autoClkMode option was added to the xcnfcbclk command. The default is disabled for backward compatibility. To enable this feature, enter the xcnfcbclk -autoClkMode enable command. The PXM scans the entire shelf to verify if two RPMs reside on the same cell bus, and then changes that cell bus to run at a 42 MHz clock rate. The clock rate for the remaining cell buses is not changed. The active PXM updates the disk DB and sends the update to the standby PXM.

When you enable this feature, you cannot manually configure the cell bus clock rate for any of the cell buses. When you disable this feature using the xcnfcbclk -autoClkMode disable command, the PXM does not change the clock rate for any of the cell buses, but still updates the disk DB and sends the update to the standby PXM.

---

Note The command to enable or disable the feature is on a per shelf basis.

---

---

Note The clock is automatically changed to 21 MHz if one of the two RPM-PRs residing on the same cell bus is removed from the shelf.

---

---

Note After disabling the automatic cell bus clocking, you can manually configure the cell bus clock.

---

The output from the dspcbclk command changes to reflect this new feature. A column indicates whether the feature is enabled or disabled on the cell buses. When the feature is enabled and an RPM-PR card is inserted, the PXM checks whether the card that resides next to it on the same cell bus is also an RPM-PR card. If both cards are RPM-PR cards and neither of them is in failed, reserved, unknown, self-test-fail, or no-card state, the cell bus clock rate is automatically set to 42 MHz.

Conversely, when the feature is enabled, and an RPM-PR card with a cell bus clock rate of 42 MHz is removed or fails, the PXM sets the cell bus to 21 MHz, as shown in the following example:

mgx574.1.7.PXM.a > dspcbclk

     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         21           1, 2       disable

       CB2         21           3, 4       disable

       CB3         21           5, 6       disable

       CB4         21        17 - 22       disable

       CB5         21          9, 10       disable

       CB6         21         11, 12       disable

       CB7         21         13, 14       disable

       CB8         21        25 - 30       disable

mgx574.1.7.PXM.a > cnfcbclk 1 42

WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 
effected by this command.

mgx574.1.7.PXM.a > cnfcbclk 5 42

WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 

effected by this command.

mgx574.1.7.PXM.a > dspcbclk

     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         42           1, 2       disable

       CB2         21           3, 4       disable

       CB3         21           5, 6       disable

       CB4         21        17 - 22       disable

       CB5         42          9, 10       disable

       CB6         21         11, 12       disable

       CB7         21         13, 14       disable

       CB8         21        25 - 30       disable

mgx574.1.7.PXM.a > xcnfcbclk

Not enough arguments (?)

xcnfcbclk "-cb <cellBus> -rate <clockRate> -autoClkMode <autoClkEnable>"

    -cb <cellBus>, where cellBus is a string CB1..CB8

    -rate <clockRate>, where clockRate is 21 or 42 (MHz)

    -autoClkMode <autoClkEnable>, where autoClkEnable is enable or disable

mgx574.1.7.PXM.a > xcnfcbclk -autoClkMode enable

mgx574.1.7.PXM.a > dspcbclk

     CellBus    Rate (MHz)     Slot     AutoClkMode

    --------------------------------------------------

       CB1         42           1, 2       enable 

       CB2         21           3, 4       enable 

       CB3         21           5, 6       enable 

       CB4         21        17 - 22       enable 

       CB5         21          9, 10       enable 

       CB6         42         11, 12       enable 

       CB7         21         13, 14       enable 

       CB8         21        25 - 30       enable

VISM-PR to RPM-PR Connectivity

VISM Release 3.0 introduces VISM-PR front cards for Cisco MGX Release 1.2.21 and Cisco IOS Release 12.2(15)T.

The new VISM-PR-8E1 and VISM-PR-8T1 cards work in Cisco MGX 8230, MGX 8250, and MGX 8850 PXM1-based switches, in combination with the PXM1 Processor Module card. The VISM-PR card supports 144 channels when used with the G.723.1 codec, whereas the VISM card supports 64 channels with the G.723.1 codec.

Setting connections between a VISM-PR card and an RPM-PR card in your Cisco MGX 8230, MGX 8250, or MGX 8850 PXM1-based switch chassis requires that you use the new VBR (NRT) 3 connection type. For more information, refer to the Cisco VISM Installation and Configuration Guide.

Configuring the Cell Bus Clock Rate

As of Cisco MGX Release 1.2.10 and Cisco IOS Release 12.2(8)T4), when two RPM-PR cards are on the same cell bus occupying adjacent slots (for example, slots 1 and 2 or slots 3 and 4), set the cell bus clock (CBC) rate to 42 MHz. Correspondingly, if only one RPM-PR exists on the cell bus, set the clock to the default value of 21 MHz.

If one of the adjacent RPM-PRs goes to failed or empty state, the CBC for that cell bus must be reconfigured for traffic shaping to work correctly on the active RPM-PR. On Cisco MGX 1 switches with Release 1.2.10, you must use the cnfcbclk command to change the CBC from 42 MHz to 21 MHz. Use the dspcbclk command from the PXM1 to confirm the CBC rate.

The following output displays the use of the cnfcbclk and dspcbclk commands used to change the clock on cell bus 1 (for slots 1 and 2) from 21 MHz to 42 MHz and confirm the change:

PXM> dspcbclk

     CellBus    Rate (MHz)    Slot

    -------------------------------

       CB1         21        1, 2

       CB2         21        3, 4

       CB3         21        5, 6

       CB4         21        17 - 22

       CB5         21        9, 10

       CB6         21        11, 12

       CB7         21        13, 14

       CB8         21        25 - 30

PXM> cnfcbclk CB1 42

WARNING: Certain Service Modules will not operate at the clock rate you specified.

         Please check the Service Modules in the slots where the Cell Bus clock rate is 
effected by this command

mgx3.1.7.PXM.a > dspcbclk

     CellBus    Rate (MHz)    Slot

    -------------------------------

       CB1         42        1, 2

       CB2         21        3, 4

       CB3         21        5, 6

       CB4         21        17 - 22

       CB5         21        9, 10

       CB6         21        11, 12

       CB7         21        13, 14

       CB8         21        25 - 30

The RPM-PR makes use of idle cells for traffic shaping and scheduling. If two RPM-PRs exist in adjacent slots on the same cell bus and one of the RPM-PRs is put into a failed state by the PXM while that card is alive, then the failed RPM-PR must stop sending idle cells to avoid having an impact on traffic shaping on the adjacent functional RPM-PRs. The rpm-auto-cbclk-change command implements the RPM-PR support for this feature. This command instructs the RPM-PR to stop sending idle cells if the RPM-PR is put into a failed state by the PXM and thus prevents an impact on traffic shaping on an adjacent functional RPM-PR.

This command may be used if traffic shaping is not required.

The following output displays an example of the rpm-auto-cbclk-change command:

RPM-11#config terminal

  Enter configuration commands, one per line. End with CNTL/Z.

  RPM-11(config)#int sw1

  RPM-11(config-if)#rpm-auto-cbclk-change

  RPM-11(config-if)#end

  RPM-11#write mem

  Building configuration...

  [OK]

  RPM-11#show run int sw1

Building configuration...

Current configuration:142 bytes

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 rpm-auto-cbclk-change

 switch autoSynch off

end

! rpm_tag_id Apr 04 2002 02:49:04

If traffic shaping is not a requirement, enter the no rpm-cbclk-change command, either manually or during card configuration. The following output displays an example of the no rpm-auto-cbclk-change command:

RPM-11#config terminal

  Enter configuration commands, one per line. End with CNTL/Z.

  RPM-11(config)#int sw1

  RPM-11(config-if)#no rpm-auto-cbclk-change

  RPM-11(config-if)#end

  RPM-11#write mem

  Building configuration...

  [OK]

  RPM-11#show run int sw1

Building configuration...

Current configuration:145 bytes

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 no rpm-auto-cbclk-change

 switch autoSynch off

end

! rpm_tag_id Apr 04 2002 02:49:57

---

Note The CBC feature is enabled by default on the RPM-PR.

---

LDP on RPM-PR Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1

The MPLS label distribution protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services.

1. LDP provides a standard methodology for hop-by-hop or dynamic label distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols.

2. The resulting labeled paths, called label switch paths (LSPs), forward label traffic across an MPLS backbone to particular destinations.

These capabilities enable service providers to implement Cisco MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.

From an historical and functional standpoint, LDP is a superset of the Cisco pre-standard Tag Distribution Protocol (TDP), which also supports MPLS forwarding along normally routed paths. For those features that LDP and TDP share in common, the pattern of protocol exchanges between network routing platforms is identical. The differences between LDP and TDP for those features supported by both protocols are embedded in their implementation details, such as the encoding of protocol messages.

This software release of LDP provides the means for transitioning an existing network from a TDP operating environment to an LDP operating environment. Thus, you can run LDP and TDP simultaneously on any given router platform. The routing protocol that you select can be configured on both:

•A per-interface basis for directly-connected neighbors and

•A per-session basis for non-directly-connected (targeted) neighbors

In addition, a label switch path (LSP) across an MPLS network can be supported by LDP on some hops and by TDP on other hops.

MPLS LDP offers the following features:

•IETF Standards-based label distribution protocol

•Multivendor interoperability

•TDP to LDP migration and interoperability

Multi-LVC on RPM-PR Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1

This feature enables support for initiation of multiple LSPs per destination on the RPM-PR. Different label switched paths are established for different classes of service (CoS). This feature enables interface level queueing rather than per-vc level on the RPM-PR based on MPLS CoS policy. With Multilabel switched controlled virtual circuits (Multi-LVC) support, customers can deploy IP VPN services with CoS Service Level Agreements (SLAs).

Bypass Feature for RPM-PR in Cisco IOS Release 12.2(4)T

---

Note Information about the bypass feature and its Cisco IOS commands was not available at publish time; therefore, it is included in the these release notes.

---

RPM-PR cards have a maximum storage of 128 KB for the nonvolatile RAM (NVRAM). This size limitation creates a problem for customers with large configurations who find it impossible to store the complete configuration in the NVRAM, even with compression enabled.

To allow customers to store large configuration files, a bypass feature was added. With the bypass feature enabled, users execute the enhanced write memory command to bypass NVRAM and save the configuration in the following location:

For MGX Release 1, the file auto_config_slot## is located in the C:/RPM directory on the PXM1.

Where ## represents the zero-padded slot number in which the RPM-PR card is seated in the MGX chassis.

To enable the bypass feature, enter the rpmnvbypass command from the Cisco IOS run-time image (not in the Cisco IOS boot image).

To disable the bypass feature, enter the no rpmnvbypass command.

To verify the bypass feature is either enabled or disabled, enter the show running-configuration command. If the bypass feature is enabled, rpmnvbypass appears in the window. If it does not appear, the feature is not enabled.

---

Note Because the bypass feature bypasses NVRAM, it is not necessary to compress the configuration file using the service compress-config command.

---

Table 1 lists the cautions that are important to successfully use the bypass feature.

Table 1 Boot Cautions 

Caution	Description
When using the bypass feature, you can load the run-time Cisco IOS image from the PXM hard drive or from the bootflash.	You can load the Cisco IOS image in one of three ways: 3. From the PXM hard drive. 4. From the bootflash. 5. From the network (for example, through TFTP) from the RPM-PR back card (Ethernet or Fast Ethernet). When the bypass feature is enabled, the boot config statement (c:auto_config_slot##) is automatically generated. The NVRAM configuration is cleared upon executing a write memory command. To load from the network, the RPM-PR must have an IP address for its back card. This information is part of the NVRAM configuration, which was just cleared by enabling the bypass feature. Hence, it is not possible to load the Cisco IOS image from the network upon a reload of the RPM-PR after you execute the rpmnvbypass and write memory commands.
Do not execute the no boot config command. Doing so may prevent the bypass feature from working properly.	When you enable the bypass feature, the following boot config statement is automatically generated, and the NVRAM configuration is cleared: c:auto_config_slot## Any writes are subsequently directed to the boot config file. This is essential, as a write memory command expects the boot config statement to be present. If the boot config statement is not present, and you enter the write memory command, this writes the configuration into the NVRAM, which is not desirable when the objective is to save a complete configuration that is large and requires more space.
If the command write memory is issued with the bypass feature enabled, and is consequently followed by an RPM-PR card reset, previous versions of the boot image trigger the RPM-PR card to enter boot mode (unable to load run-time Cisco IOS software).	For safety purposes, the location of the system image is stored in a special area called the ROM monitor (ROMmon) area in the NVRAM. The ROMmon is always intact. The Release 12.2(4)T boot image accesses and reads ROMmon to load the Cisco IOS image. Boot images earlier than Release 12.2(4)T do not read the ROMmon area. Generally, Cisco IOS boot and run-time images are the same versions. However, if you change the boot image to one earlier than Release 12.2(4)T on a reload, the boot image sees that the NVRAM configuration is empty [which is normal when the bypass feature is enabled]. But because boot images earlier than Release 12.2(4)T cannot access the ROMmon area, the boot image cannot read the location of the Cisco IOS image. Because it cannot see the Cisco IOS image, it loads itself.

Example 1 through Example 5 illustrate how to enable and disable the bypass feature, and how to validate each of these actions from the configuration display.

Example 1 Running Configuration—No Bypass Feature Enabled

rpm_slot02#show running-config

Building configuration...

Current configuration : 470 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname rpm_slot02

!

boot system c:rpm-js-mz.<new_rel>

enable password cisco

!

ip subnet-zero

!

!

!

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 switch autoSynch off

!

ip classless

no ip http server

ip pim bidir-enable

!

!

snmp-server community public RO

snmp-server community private RW

!

!

line con 0

line aux 0

line vty 0 4

 no login

!

end

Example 2 Enabling the Bypass Feature—rpmnvbypass

rpm_slot02#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

rpm_slot02(config)#rpmnvbypass

The "boot config" statement has been (re)added to your

running configuration. Do not remove it else risk not

using the nvbypass feature

rpm_slot02(config)#end

rpm_slot02#

Example 3 Running Configuration with Bypass Feature Enabled—rpmnvbypass at End of Output

rpm_slot02#show running-config

Building configuration...

Current configuration: 515 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname rpm_slot02

!

boot system c:rpm-js-mz.<new_rel>

boot config c:auto_config_slot02    <==== Line added as per output above

enable password cisco

!

ip subnet-zero

!

!

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 switch autoSynch off

!

ip classless

no ip http server

ip pim bidir-enable

!

!

snmp-server community public RO

snmp-server community private RW

!

!

line con 0

line aux 0

line vty 0 4

 no login

!

rpmnvbypass

end

Example 4 Disabling Bypass Feature—no rpmnvbypass

rpm_slot02#configure terminal

Enter configuration commands, one per line. End with CNTL/Z.

rpm_slot02(config)#no rpmnvbypass

rpm_slot02(config)#end

rpm_slot02#

Example 5 Running the Configuration After Disabling the Bypass Feature

rpm_slot02#show running-config

Building configuration...

Current configuration: 503 bytes

!

version 12.2

service timestamps debug uptime

service timestamps log uptime

no service password-encryption

!

hostname rpm_slot02

!

boot system c:rpm-js-mz.<new_rel>

boot config c:auto_config_slot02

enable password cisco

!

ip subnet-zero

!

!

!

!

interface Switch1

 no ip address

 no atm ilmi-keepalive

 switch autoSynch off

!

ip classless

no ip http server

ip pim bidir-enable

!

!

snmp-server community public RO

snmp-server community private RW

!

!

line con 0

line aux 0

line vty 0 4

 no login

!

end

rpm_slot02#

Features Not Supported in This Release

The following features are not supported on the RPM-PR:

•MPLS inter AS

•MPLS TE

RPM-PR Redundancy Support

Use RPM 1:N redundancy to switch configuration and traffic from one RPM-PR card to another. The main benefits are:

•Route processing continues even if an RPM-PR fails and there is no operator or direct access to swap the failed card or fix the problem.

•An RPM-PR card with hardware problems can be fixed while the redundant standby card takes over its functionality.

•Software upgrades are easy and are performed with less downtime.

SNMP MIB

SNMP MIB files for RPM-PR are provided with MGX Release 1.3.12. These files can be compiled with most standards-based MIB compilers. The tar file contains the MGX MIB files and the MIB release notes.

Cisco IOS MIBs are not part of the MGX Release 1.3.12 SNMP MIB bundle; they are part of Cisco IOS Release 12.3(11)T7.

---

Note As of this release, the old_mib_Format is discontinued.

---

Notes and Cautions

Before using this release, review the following notes and cautions.

Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT

Use the following procedure when upgrading from your current RPM Cisco IOS Release12.1(5.3)T_XT run-time image and MGX version for MGX Releases 1.2.02 and 1.2.10:

---

Step 1 Upgrade the RPM-PR/IOS boot and run-time images first. Follow the RPM/IOS image upgrade procedure as specified in the "Upgrading RPM-PR Cards in MGX PXM1 Switches" section.

Step 2 Upgrade the MGX software by entering the following commands:

install <image-name>

newrev <image-name>

commit <image-name>

---

For more information on the MGX upgrade procedures, refer to the Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1), Software Version 1.2.10.

UPC Connection Parameters

In Release 1.1.40 and later, the default peak cell rate (PCR) is 50 cps, and the default for policing is enabled. These settings are insufficient for running RPM-PR Intermediate System-to-Intermediate System (IS-IS) protocol over the connection, and with such settings, the IS-IS protocol fails.

---

Note You must increase the PCR value depending upon the number of interfaces configured for IS-IS on the RPM-PR.

---

Depending upon your connection type, you can use the following CLI commands to modify the PCR parameter:

•cnfupccbr

•cnfupcvbr

•cnfupcabr

•cnfupcubr

Booting the RPM-PR

See Chapter 5, "Configuring the MGX RPM" in the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1, (DOC-7812278=) for complete details on configuring an RPM-PR. (See the "Obtaining Documentation" section for information on ordering a printed copy of this guide, or to locate it online.)

When the RPM-PR boots, the boot image must be the first file in the bootflash. If the bootflash does not have a valid boot image as a first file, the card may not be able to boot. You can reboot the RPM-PR from the PXM by entering the resetcd <card_number> command from the switch CLI, where card_number is the slot number of the RPM-PR that is being rebooted.

---

Note Omitting the card number resets the entire system.

---

Also, you can reboot the RPM-PR from the RPM-PR using the console port and then entering the reload command.

Each time you turn on power to the RPM-PR by inserting the RPM-PR into the Cisco MGX 8850 switch, the RPM-PR goes through the following boot sequence:

1. The RPM-PR runs diagnostics on the CPU, memory and interfaces.

2. The system boot software (which is the boot image) executes and searches for a valid Cisco IOS image (which is the RPM-PR run-time software). If the configuration register:

–Is 0x01 (default setting)—The RPM-PR comes up and stays in boot mode.

–Is 0x2—The RPM-PR looks for the run-time image either in bootflash or on the PXM1 C:/RPM drive.

The source of the Cisco IOS image is determined by the configuration register setting. To verify this setting, you can either enter the show version or the show bootvar command. See the "Viewing the Hardware Configuration" section of the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 (DOC-7812278=).

3. The search for run-time image is determined by one of the following boot system commands that you enter:

–Enter the boot system c:<runtime_image_name> command to search for a run-time image in the C:/RPM directory on the PXM1 hard disk.

–Enter the boot system bootflash:<runtime_image_name> to search for a run-time image in the bootflash.

–If the boot system bootflash:<runtime_image_name> is not entered, it loads the first available Cisco IOS image from C:/RPM, if an image is present.

4. After three attempts, if the run-time software is not found, the RPM-PR reverts to boot mode.

5. If a valid Cisco IOS image is found, the RPM-PR searches for a valid configuration. The configuration can reside in NVRAM or as a configuration file either on the PXM hard disk C:/RPM drive or in bootflash.

To load from a specific configuration file, enter either the boot config bootflash:<config_file> command or the boot config c:<config_file> command.

6. For normal RPM-PR operation, a valid Cisco IOS image must be present on the PXM-1 C:/RPM drive or in bootflash, and a configuration file must be present in NVRAM, or in the bootflash or on the PXM hard disk.

The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-PR Card" in the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 (DOC-7812278=). For more information, refer to Appendix C, "IOS and Configuration Basics" of the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1 (DOC-7812510=).

RPM-PR Bootflash Precautions

The RPM-PR bootflash is used to store the boot image, configuration, and run-time files. The flash memory stores and accesses data sequentially, and the RPM-PR boot image must be the first file stored to successfully boot the card. If you erase the boot image or move it from the first position on the flash, the card will not boot.

The RPM-PR boot image, which is shipped loaded on the flash, works for all RPM-PR Cisco IOS images. Therefore, there is no reason to ever delete or move the factory-installed boot image.

---

Caution Erasing or moving the boot image can cause RPM-PR boot failure. When this happens, the RPM-PR card must be returned to Cisco and reflashed.

---

To avoid this unnecessary failure, requiring card servicing, remember the following:

•Never erase the boot file from the RPM-PR flash.

•Never change the position of the boot file on the RPM-PR flash.

•Use care when using squeeze flash: command to clean it up the flash.

If the boot file remains intact in the first position on the flash, the RPM-PR successfully boots.

Solving the RPM-PR Bandwidth Issue When Adding a 12th VISM Card

If you add more than 11 VISM cards to an MGX chassis with RPM-PR cards, you must enable the expanded memory option on the PXM45/B using the cnfndparms command (option 4). This expanded memory option does not have an impact on chassis performance, and allows more connections.

Limitations and Restrictions

This section lists the limitations and restrictions for Cisco IOS Release 12.3(11)T7 for MGX Release 1.3.12 and earlier releases.

CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards

Cisco WAN Manager (CWM) does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. There is no functionality difference.

RPM/B and RPM-PR Front Card Resets on the Back Card Removal

When you remove or insert an Ethernet back card, the RPM-PR front card may reset on Cisco MGX 8250 and MGX 8850 switches with PXM1 controller cards. To avoid this reset problem, execute a shut command before removing the back card.

RPM/B and RPM-PR Back Ethernet Card Support

For Ethernet connectivity with the RPM-PR, you must have the model /B 4-port Ethernet back card (part number: MGX-RJ45-4E/B).

MGX-RPM-128M/B Ethernet Back Card Support

You can use the model /B 4-port Ethernet back card with the MGX-RPM-128M/B module only in combination with Cisco IOS Release 12.2(2)T2 or later. The model /B back card does not work on the MGX-RPM-128M/B with earlier versions of Cisco IOS (part number: MGX-RJ45-4E/B).

You can use earlier back cards with any Cisco IOS release.

4-port Ethernet Back Card Used with MGX-RPM-128M/B	Required Cisco IOS Release
Model /B back card	12.2(2)T2
Earlier back card models	Minimum Cisco IOS release for MGX-RPM-128M/B on MGX 8250 is Release .0(7)T

RPM/B and RPM-PR Limitations and Restrictions for MGX Release 1.3.12

The following RPM/B and RPM-PR limitations and restrictions apply to this release:

•The MGX-RPM-128M/B is a NPE-150-based router card capable of sustaining 150,000 pps. The RPM-PR is an NPE-400-based router capable of sustaining over 350,000 pps. The RPM-PR only operates with Cisco IOS Release 12.1(5.3)T_XT or later. In the following section, RPM refers to both the MGX-RPM-128M/B and the RPM-PR, (unless specifically stated). Some software versions and limitations are not applicable to the RPM-PR because it does not support any releases earlier than Cisco IOS Release 12.1(5.3)T_XT.

•With MGX-RPM-128M/B versions earlier than 12.0.7T1, some limitations in Inter-Process Communication when the MGX-RPM-128M/B is at high loads can cause the PXM to declare that the MGX-RPM-128M/B has failed. To avoid this with MGX-RPM-128M/B, software releases earlier than 12.0.7T1, throughput is limited to 62,000 pps, and we recommend that MPLS configurations are limited to 100 interfaces. With RPM software releases from 12.0.7T1, those limitations are removed. In a separate limitation, the number of directly-connected open shortest path first (OSPF) networks supported by an RPM is currently limited to 27. This means that any or all of the subinterfaces supported by the RPM can run OSPF, but the number of distinct OSPF networks supported is limited to 27. (A workaround is available; see below.) The limit of 27 is because of the overhead of supporting separate link-state databases for separate networks.

•In an application in which the RPM is a PE router in an MPLS Virtual Private Network service, the solution is to use a distance-vector routing protocol between the customer routers and the RPM. A distance-vector routing protocol provides the information for this application: reachability information, and not link-state information. The distance-vector routing protocols supported by the RPM are Border Gateway Protocol (BGP), RIP v1 and RIP v2, and static routing. With RPM software from Release 12.0.7T1 and later, distance-vector routing protocols can be used with as many different networks as subinterfaces.

•If the RPM is acting as a PE router in an MPLS VPN service, and even if OSPF is running in a customer network, it is not necessary to run OSPF between the customer router and the RPM. If the customer edge devices run Cisco IOS, they can redistribute OSPF routing information into RIP using Cisco IOS commands, redistribute RIP in the OSPF configuration, and redistribute OSPF in the RIP configuration. Similar configurations are possible for BGP. (For more information, see the "Configuring IP Routing Protocol-Independent Features" chapter in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1). Redistribution is not unique to Cisco CPEs, and other vendor equipment also supports redistribution.

•Each time two RPM cards on adjacent slots are driven by the same CBC, use the cnfcbclk command to set the clock rate to 42 MHz for traffic shaping. This configuration is lost if the node rebuilds due to resetsys or a power cycle. After a rebuild using the cnfcbclk command, you must manually reconfigure the CBC rate.

•On a Cisco MGX 8850 switch, when the chassis is loaded with six or more RPM-PR cards, and if each card is configured to download the Cisco IOS run-time image from the PXM-1 hard disk, occasionally, upon entering a resetsys command or after a power cycle, some of the RPM-PR cards may go into the failed state. To reset failed RPM-PR cards, enter the resetcd <slot #> command for each failed card.

•One RPM-PR can only function as either an edge Label Switch Router (eLSR) or as an LSC, but not as both.

•Supports a total of (OC-12 minus T3) Mbps intrashelf traffic for cell bus-based modules.

•To configure redundancy, the primary and secondary RPM-PR cards need to be in the active state and the secondary card should not have any configuration.

•Removing a back card does not cause an RPM-PR switchover.

•After establishing redundancy between two RPM-PR cards with the addred command, you must enter the copy run start command on the primary RPM-PR card to save the configuration change.

•If a secondary RPM-PR card is redundant to primary cards x and y, you cannot delete redundancy for only card x.

•If you must enter the switchredcd and switchcc commands, we recommend that you wait at least 5 seconds after issuing the switchredcd command, and then enter the switchcc command.

•Cisco IOS software images on primary and secondary RPM-PR cards do not have to be compatible, but the Cisco IOS software on a secondary card should be at the same level as the primary card or higher.

•Each time the RPM-PR configuration is changed and you want to store that configuration, you must enter the copy run start command on the RPM-PR. If you do not, the changed configuration is lost on RPM-PR card reboot or RPM-PR switchover in case of redundancy.

•Even though an RPM-PR can have 1999 subinterfaces, you must plan the use of subinterfaces to prevent the crossing of a safe limit of 1985. This is because each subinterface takes one interface descriptor block (IDB) and the number of IDBs available in the card is 2000. Further, a user might need some IDBs for the RPM-PR back card and its ports.

•For RPM/B and RPM-PR PVC dax connections, the slave end must be deleted before the master endpoint.

Open Caveats

This section contains the lists of open caveats in Cisco IOS Releases 12.3.x.

Open Caveats in Release 12.3(11)T7 for MGX 1.3.12

No open bugs are listed for this release.

Open Caveats in Release 12.3(11)T6 for MGX 1.3.12

Table 2 lists open caveats in Cisco IOS Release 12.3(11)T6 for MGX Release 1.3.12 as of June 20, 2005.

Table 2 Open Caveats in Cisco IOS Release 12.3(11)T6 for MGX Release 1.3.12 

Caveat Number	Symptom	Conditions	Workaround
CSCef79260	A Cisco RPM-PR card stops responding at atmdx_rx_interrupt.	Observed in a configuration in which two LSCs are configured for hot redundancy with a large MPLS VPN configuration on a PE router, and LDP flapping was performed for a long time. Observed on an RPM router running Cisco IOS Release 12.2(15)T4e.	Unknown

Open Caveats in Release 12.3(11)T3 for MGX 1.3.12

Table 3 lists open caveats in Cisco IOS Release 12.3(11)T3 for MGX Release 1.3.12 as of January 2005.

Table 3 Open Caveats in Cisco IOS Release 12.3(11)T3 for MGX 1.3.12 

Caveat Number	Symptom	Condition	Workaround
CSCec68542	In a large-scale network and under a stressful condition, segmentation and reassembly (SAR) may not reassemble properly for large packets, causing the protocol to fail.	Observed on an RPM-PR that runs Cisco IOS Release 12.2(15)T4B that functions as a Label Edge Router (LER), and that is configured with two LSCs under the following conditions: •With a script running, disable and re-enable the multi-virtual-circuit (Multi-VC) mode on the RPM-PR. •1000 soft permanent virtual circuits (SPVCs) that have VPN routing/forwarding (VRF) enabled exist. •500 external Border Gateway Protocol (eBGP) sessions exist. •80-Mbps input traffic and 6-Mbps output IP traffic is in place.	To clear the issue, enter the clear int switch1 command. L3 protocols come up.
CSCee21093	On a Cisco MGX 8850 switch with a PXM1 controller card platform, TFTP of the config file by the CWM NMS application from the RPM-PR card takes a long time to complete.	The CWM application attempts to sync up with the Cisco MGX 8850 switch. This process invokes an SNMP get route command to collect information from the switch cards. The RPM-PR config file cannot be collected as the SNMP get routine gets timed out. As the timeout happens in this condition, CWM cannot sync up with the RPM-PR configuration.	Remove the running configuration of the RPM-PR card by executing the clrsmcnf command from the PXM1 controller card. Reload the original configuration (which must be sav