Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco MGX 8800 Series Switches

Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(11)T6 for PXM45-based Switches, Release 5.1.20

Downloads

Table Of Contents

Release Notes for Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.3(11)T6 for PXM45-based Switches, Release 5.1.20

Contents

Overview

About this Release

New Features

Features Introduced in Cisco IOS Release 12.3(11)T6

Features Introduced in Cisco IOS Release 12.3(11)T3

Features Introduced in Cisco IOS Release 12.3(7)T3

Features Introduced in Cisco IOS Release 12.3(2)T6

Features Introduced in Cisco IOS Release 12.3(2)T5

Features Introduced in Cisco IOS Release 12.3(2)T4

Link Fragmentation Interleaving

Increased Maximum Number of Policy Maps

Multicast VPN Feature

Compressed Real-Time Protocol

WRED Drop Counters Feature

Traffic Matrix Statistics Feature

Segmentation and Reassembly-based Traffic Management and QoS Feature

Feature Introduced in Cisco IOS Release 12.3(2)T2

Transmission Control Protocol Decompression Support

2-Port Packet Over SONET and 2-Port Gigabit Ethernet Service Module Back Cards

Dual Multiprotocol Label Switching Partition for RPM-XF

Features Introduced Earlier than Cisco IOS Release 12.3(2)T2

Cisco MGX 8950 Switch Support for RPM-XF

Border Gateway Protocol Load-Balancing Feature

IP Accounting Counter Storage Feature

Applying Multiple Actions—police Command

QoS Suboptimal Link Use Feature

RPM-XF Redundancy Support

Features Not Supported in Cisco IOS Release 12.3(11)T5

Network Management Features

SNMP MIB

RPM-XF Limitations and Restrictions

Notes and Cautions

RPM-XF auto_config File Management

Card Management

RPM-XF Bootflash Precautions

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

Open Caveats—Release 12.3(11)T6

Open Caveats—Release 12.3(11)T3

Open Caveats—Release 12.3(7)T3

Resolved Caveats—Release 12.3(11)T6

Resolved Caveats—Release 12.3(11)T3

Resolved Caveats—Release 12.3(7)T3

Resolved Caveats—Release 12.3(2)T6

Resolved Caveats—Release 12.3(2)T5

Resolved Caveats—Release 12.3(2)T4

Resolved Caveats—Release 12.3(2)T2

Compatibility Notes

RPM-XF Boot File and Firmware File Names and Sizes

RPM-XF Compatibility Matrix

MGX RPM-XF Hardware

Cisco IOS Release Compatibility Information

Using XModem to Download Flash to RPM-XF Cards

Historical Information for Cisco IOS Release 12.2.x Baseline

Resolved Caveats—Release 12.2(15)T5

Resolved Caveats—Release 12.2.15T

Resolved Caveats—Before Release 12.2.15T

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-XF) Cisco IOS Release 12.3(11)T6 for PXM45-based Switches, Release 5.1.20

Part Number OL-7278-01 Rev. B0, July 13, 2005

Contents

Overview

These release notes contain the following sections:

•"About this Release" section

•"New Features" section

•"RPM-XF Redundancy Support" section

•"Features Not Supported in Cisco IOS Release 12.3(11)T5" section

•"SNMP MIB" section

•"RPM-XF Limitations and Restrictions" section

•"Notes and Cautions" section

•"Open Caveats—Release 12.3(11)T6" section

•"Open Caveats—Release 12.3(11)T3" section

•"Open Caveats—Release 12.3(7)T3" section

•"Resolved Caveats—Release 12.3(11)T6" section

•"Resolved Caveats—Release 12.3(11)T3" section

•"Resolved Caveats—Release 12.3(7)T3" section

•"Resolved Caveats—Release 12.3(2)T6" section

•"Resolved Caveats—Release 12.3(2)T5" section

•"Resolved Caveats—Release 12.3(2)T4" section

•"Resolved Caveats—Release 12.3(2)T2" section

•"Compatibility Notes" section

•"MGX RPM-XF Hardware" section

•"Cisco IOS Release Compatibility Information" section

•"Using XModem to Download Flash to RPM-XF Cards" section

•"Historical Information for Cisco IOS Release 12.2.x Baseline" 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-XF Cisco IOS Release 12.3(11)T6 for PXM-based Switches, Release 5.1.20. These notes also contain Cisco support information. For more information on the RPM-XF, refer to the Cisco MX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 5.

New Features

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

Features Introduced in Cisco IOS Release 12.3(11)T6

No new features were introduced in Cisco IOS Release 12.3(11)T6.

Features Introduced in Cisco IOS Release 12.3(11)T3

Features added to the RPM-XF in Cisco IOS Release 12.3(11)T3 include:

•Copper small-form factor pluggable (SFP)

•RPM-XF software—Queueing elements, statistics, FTP elements, compressed Real-Time Protocol (cRTP) elements, MIBs

•Dynamic bandwidth

For more information, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 5.

Features Introduced in Cisco IOS Release 12.3(7)T3

Features introduced in Cisco IOS Release 12.3(7)T3 include:

•MGX-XF-UI/B notched back card—A redesign of the user interface back card for the RPM-XF. The notch was added to allow clearance for installation of the RCON APS connector on the Cisco MGX 8850B and MGX 8880 chassis.

•Preferred routes on RPM-XF—Cisco IOS software Release 12.3(7)T3 contains enhanced support for preferred routes on the RPM-XF. Currently the AXSM and other service modules provide the facility to associate an already-defined preferred route on the PXM to an soft permanent virtual connection (SPVC) mastered on that service module. The commands described below are updated to support Preferred Route association through a command-line interface (CLI) or Simple Network Management Protocol (SNMP) for SPVC, Hybrid, and extended permanent virtual connection (XPVC) configured with an RPM-XF as the master end.

Syntax Description

Router(config-if-swconn)#[no] prefrte <Route ID>

Route ID—An identifier for the configured preferred route that is associated with this connection. Preferred routes are maintained in a separate database on the PXM and referenced by the ID. The range is 0 through 65535. Setting the ID to 0 means no preferred route is configured. The default value for preferred route ID is zero (no preferred route attached).

Router(config-if-swconn)#[no] directrte

Setting the Directed Route flag to Yes sets the connection to be routed only on the specified preferred route. The default value for a directed route is No.

Router(config-if-swconn)# prefrte ?

<1 - 65535> Preferred Route ID value

Router(config-if-swconn)# directrte ?

<cr>

Note If you use the directrte command to specify a directed route for a connection with its preferred route ID set to zero, an error message appears. Both the prefrte and directrte commands must be run on the master end of the connection. If you try to use these commands on the slave end of the connection, an error message appears.

Examples

To configure a preferred route ID value of 10 for the connection: 

Router(config-if-swconn)# prefrte 10

To configure a preferred route ID value of 5 and set the connection on directed route: 

Router(config-if-swconn)# prefrte 5

Router(config-if-swconn)# directrte

To change the directed route flag for the connection to No: 

Router(config-if-swconn)# no directrte

To set the preferred route id to zero and set the directed route to No: 

Router(config-if-swconn)# no prefrte

Features Introduced in Cisco IOS Release 12.3(2)T6

The following new features were introduced in Cisco IOS Release 12.3(2)T6:

•Enhanced Interior Gateway Routing Protocol (eiGRP) between customer edge (CE) to provider edge (PE).

•Basic Point-to-Point Protocol (PPP) over ATM feature evaluation on various port speeds from 768 Kbps up to DS3 with a maximum of T1 bandwidth per flow.

•PPP over ATM with cRTP on various port speeds from 768 Kbps up to DS3 with a maximum of T1 bandwidth per flow.

•PPP over ATM with cRTP and QoS enabled on the links.

•Scaling up to 200 cRTP enabled pppoATM links with QoS.

Features Introduced in Cisco IOS Release 12.3(2)T5

No new features were introduced in Cisco IOS Release 12.3(2)T5.

Features Introduced in Cisco IOS Release 12.3(2)T4

Link Fragmentation Interleaving

Cisco IOS Release 12.3(2)T4 adds support for Link Fragmentation Interleaving (LFI). For more information on the CLI commands introduced or modified to support this feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

For Cisco IOS software configuration information, go to:

http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtlfifra.htm

Increased Maximum Number of Policy Maps

Policy maps, class maps, and service policy maps define traffic policies, and attach them to interfaces. In earlier releases, you could create 256 separate policy maps and up to 256 class maps per policy map. In Cisco IOS Release 12.3(2)T4, the maximum number of policy maps is increased to 2048. Each policy map supports up to 32 class maps per policy map. For more information on the CLI commands that have been introduced or modified to support this feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Multicast VPN Feature

The frame-based Multicast VPN (MVPN) feature enables the RPM-XF 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

Compressed Real-Time Protocol

The Cisco IOS Release 12.3(2)T4 of the RPM-XF adds the ability to configure the 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

WRED Drop Counters Feature

The WRED Drop Counters feature adds class-based packet counters to existing RPM-XF functionality. The counters can be Differentiated Services Code Point (DSCP) based or precedence based. For more information on the CLI commands introduced or modified to support the weighted random early detection (WRED) Drop Counters feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Traffic Matrix Statistics Feature

The Traffic Matrix Statistics (TMS) feature allows an administrator to gather the number of packets and bytes that travel across the backbone from internal and external sources. These packets and bytes are called traffic matrix statistics. Use the statistics collected to determine how much traffic the backbone handles. The statistics are always collected on the incoming interface. For more information on CLI commands introduced or modified to support TMS on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Segmentation and Reassembly-based Traffic Management and QoS Feature

Traffic management, weighted random early detection WRED, and cell-based weighted fair queuing algorithm processing is accomplished using the Segmentation and Reassembly (SAR) engine.

Feature Introduced in Cisco IOS Release 12.3(2)T2

Transmission Control Protocol Decompression Support

Cisco IOS Release 12.3(2)T2 adds support for Transmission Control Protocol (TCP) decompression as an adjunct to supporting the cRTP header feature on the RPM-XF.

2-Port Packet Over SONET and 2-Port Gigabit Ethernet Service Module Back Cards

Cisco IOS Release 12.3(2)T2 adds support for two service module back cards that provide either two Gigabit Ethernet or two Packet over SONET (POS) ports. For more information on the fit and function of the back cards and CLI commands which support the back cards on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.

Dual Multiprotocol Label Switching Partition for RPM-XF

Cisco IOS Release 12.3(2)T2 adds support for dual Multiprotocol Label Switching (MPLS) partitions on the RPM-XF. This is related to 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

Features Introduced Earlier than Cisco IOS Release 12.3(2)T2

Cisco MGX 8950 Switch Support for RPM-XF

In Cisco MGX Release 3.0.10 and later, the Cisco MGX 8950 switch supports the MGX RPM-XF card set. The MGX RPM-XF card set can occupy any of the available service module slots in the Cisco MGX 8950 switch, which are slots 1 through 6 and slots 11 through 16.

Border Gateway Protocol Load-Balancing Feature

To load-balance by external Border Gateway Protocol (eBGP) and internal Border Gateway Protocol (iBGP) on multiple paths to a destination, traffic is directed on multiple available paths between autonomous systems (AS) by gateway routers.

The following CLI commands are used to implement this feature.

Command
Description

maximum-path <nums>

Configure maximum number of eiBGP parallel routes.

For example: 

bgpbox-zenith-CE1(config)#router bgp 4

bgpbox-zenith-CE1(config-rout)#maximum-paths 3

bgpbox-zenith-CE1(config-rout)#end

show ip bgp

•This command is enhanced to show the multipaths.

•Each multipath is marked as multipath.

•The bestpath is marked as multipath and bestpath.

•The output describes the type of multipath that is enabled.

For example: 

bgpbox-zenith-CE1#sh ip bgp 141.22.0.0

BGP routing table entry for 141.22.0.0/16, version 18

Paths: (2 available, best #1)

Multipath: eBGP

Advertised to non peer-group peers:

7.0.76.9

100 5

7.0.76.2 from 7.0.76.2 (100.0.0.2)

Origin IGP, localpref 100, valid, external, multipath, 
best

100 5

7.0.76.9 from 7.0.76.9 (100.0.0.9)

Origin IGP, localpref 100, valid, external, multipath

Limitations of eiBGP Load-Balancing

The limitations of eiBGP are as follows:

•If multiple alternate paths for a peering point exist, only one of the paths is used for a given prefix.

•Only per-flow load-balancing is supported. Per-packet load-balancing is not supported.

•eiBGP load-balancing is supported only in MPLS and VPN networks.

•Load-balancing proportional to link bandwidth (see dmz-linkbw command) is not supported. The load-balancing is performed on the available links with equal costs.

•The maximum number of paths that can be used for load-balancing is 6. This is the current Cisco IOS software limitation.

•Load-balancing does not work if RDs are the same as RRs. If RRs are used, RDs must be different.

•Having CEs in different VPNs using the same RDs does not work.

IP Accounting Counter Storage Feature

The Cisco MGX RPM-XF only stores packet/byte counters based on precedence and DSCP values on a per-interface level at input.

The following CLIs are added or enhanced for this release to implement this feature:

Command
Description

ip accounting ? 

pop20-slot6(config-if)#ip accounting ?

precedence         Count packets by IP precedence on 
this interface

dscp               Count packets by DSCP on this 
interface

ip accounting precedence ? 

pop20-slot6(config-if)#ip accounting precedence ?

input   received packets and bytes

ip accounting dscp ? 

pop20-slot6(config-if)#ip accounting dscp ?

input   received packets and bytes

show int [interface] precedence 

pop20-slot5# show int [interface] precedence

show int [interface] dscp 

pop20-slot5# show int [interface] dscp

clear counters 

pop20-slot5# clear counters

Limitations

The limitations are as follows:

•Counters are maintained only at the input per interface.

•There is no count of dropped or transmitted packets based on DSCP/PREC packets per interface.

Applying Multiple Actions—police Command

The MGX RPM-XF police command is similar to the Cisco IOS RPM command. Therefore, you can apply multiple exceed and conform actions on the police command.

The police CLI command is enhanced. Before this release, the police command had no menus and all parameters were listed on one line, as shown in the following example: 

domino80p01-z001#sh policy test1z

.............

police 128000 8000 8000 conform-action transmit exceed-action drop

This allowed only one value for the conform-action and exceed-action fields.

The new police command functions as shown in the following example: 

ipfrtx90r14-01(config-pmap-c)#police 128000 8000 8000

ipfrtx9(config-pmap-c-police)#conform-action transmit

ipfrtx9(config-pmap-c-police)#exceed-action set-dscp 28

ipfrtx9(config-pmap-c-police)#exceed-action set-mpls 2

Note that you can configure multiple conform-action and exceed-action parameters.

QoS Suboptimal Link Use Feature

RPM-XF uses Versatile Traffic Management System (VTMS) as a scheduling algorithm. VTMS schedules queues based on the current link use in real time. The previous version of the VTMS algorithm was efficient and mapped well in an ASIC or network processor; however, it did not fully use the link.

Cisco IOS Release 12.3(2)T2 adds support through the CLI to allow you to specify the oversubscription factor on a queue. The factor is in the range of 1 through 31 and can be denoted as 2n. An oversubscription factor of n = 2 on any queue means to subscribe that queue by a factor of 4 (2n where n is 2; so 2 raised to power 2 = 4).

The syntax for the bandwidth and priority commands is: 

[no] bandwidth {<kbps> | percent <percentage> | remaining percent <percentage>} 
[maximize-utilization [<max-shift>]] 

[no] priority {<kbps> | percent <percentage>} [maximize-utilization

RPM-XF Redundancy Support

RPM-XF 1:N redundancy is used to switch configuration and traffic from one RPM-XF module to another RPM-XF module. Route processing continues with minimal traffic loss even if an RPM-XF fails and there is no operator or direct access to swap the failed card or fix the problem. Redundancy that ensures Layer 2 state restoration is supported. Layer 3 state is restored through convergence.

Note When you reset a chassis with RPM-XFs configured for 1:N redundancy, we recommend that you bring up the primary slots in active state.

Benefits of 1:N redundancy include the following:

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

•Software upgrades are easier and can be performed with less downtime.

•LAN interface redundancy supported with MAC addresses of primary RPM-XF copied to standby RPM-XF.

•1:N redundancy support for Gigabit Ethernet interface back cards during front card switchover.

•Y cable redundancy support for POS back cards during front card switchover. With Y cable, 1:N redundancy is restricted to N = 1.

The following are general guidelines for redundancy on the RPM-XF:

•The Addred command is not allowed between RPM-PR and RPM-XF.

•To configure redundancy, the primary RPM-XF should be in active state and secondary RPM-XF card must be in active/standby state.

•Removing the active RPM-XF back card does not cause a switchover to the standby RPM-XF.

•Before adding redundancy, you must ensure that E:RPM/auto_config_slot# is created. This may require that you log in to the primary card through the command line and manually add boot config e:auto_config_slot# followed by a write mem command.

•Executing the switchcc command back-to-back using the switchredcd command can cause problems. We recommend allowing at least 5 seconds between switchredcd and a switchcc.

•Cisco IOS software on a standby card should be the same or later release than the active RPM-XF card release.

•If the card is in a redundancy group, do not boot the card from an image on a TFTP server. Boot the card from image in bootflash or PXM disk only.

•Do not configure the standby RPM-XF.

Features Not Supported in Cisco IOS Release 12.3(11)T5

The following features are not supported in Cisco IOS Release 12.3(11)T5:

•LSC redundancy

•Modem connectivity on auxiliary port

•MPLS TE tunnels on ATM interfaces

•Online insertion and removal (OIR) of back cards without interfaces in shutdown mode

•Per-packet load-balancing

•ROM monitor (ROMmon) Xmodem functionality does not support the speed option

•RPM-PR to RPM-XF upgrade

•Virtual circuit (VC) merge

Network Management Features

Network management features are detailed in the Release Notes for Cisco WAN Manager 15.1.00 at:

http://cisco.com/univercd/cc/td/doc/product/wanbu/svplus/151/rnotes/index.htm

SNMP MIB

SNMP MGX Release 5.1.00 MIB files are provided in Cisco IOS Release 12.3(11)T5. These files may be compiled with most standards-based MIB compilers. The tar file for MIB contains the file that contains the MIB release notes. This contains only MGX MIBs.

Cisco IOS MIBs are not part of the SNMP MGX Release 5.1.00 MIB bundle; they are part of Cisco IOS Release 12.3(2)T6.

RPM-XF Limitations and Restrictions

The following RPM-XF limitations and restrictions apply to this release:

•Before you add redundancy, you must create E: RPM/auto_config_slot#. This may require a login through the CLI and manually adding the boot config command followed by a write mem command.

•Permanent Virtual Paths (PVPs) cannot operate at a rate greater than 599,039 kbps.

•PXF buffer depletion may occur if packets of the same size (especially packets greater than 640 bytes) are sent to a congested interface.

•High speed VC Sustainable Cell Rate (SCR) greater than or equal to 599,039 kbps does not receive full-configured rate for single flow (unique source and destination IP address). This happens because for high speed VCs, Parallel Express Forwarding (PXF) creates two queues and these queues cannot be shared for the same stream. Sharing two queues for the same stream causes out-of-sequence packets.

•The PXF queue selection algorithm may cause traffic to drop for multiple streams traveling to the same destination using multiple paths. When the PXF receives a packet, it selects the output queue based on source and destination IP address. These addresses hash into one of the queues for the selected destination. So, if multiple paths for the same destination exist, multiple streams may possibly hash to one queue, causing some queues to overflow, while others might be underused.

•Variable bit rate non-real time (VBR-nrt) and variable bit rate-real time (VBR-rt) are treated with the same priority system-wide.

•RPM-XF PVP only supports unspecified bit rate (UBR).

•PVP in RPM-XF is not Operation, Administration, and Maintenance (OAM) managed.

•If out-of-sync SPVC or SPVP exist on the RPM-XF, the shrinking of the Private Network-to-Network (PNNI) partition is not permitted.

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

•Because RPM-XF only supports UBR, VBR-rt, and VBR-nrt on the PXM, the dsppnportrsrc command for RPM-XF port shows 0 available resources for CBR, ABR, and signaling service types. Also, the cnfpnportcac command for CBR and ABR is rejected.

•If RPM-XF is configured as an eLSR, RPM-XF does not support incoming VC-merge label switch controlled virtual circuits (LVCs). There is a problem logged against LSC module that it cannot support both VC-merge/non-VC-merge supporting Virtual Switch Interface (VSI) slaves at the same time. So for now, if RPM-XF eLSR is part of a cell-based MPLS network (with RPM-PRs or AXSMs in the same node), disable the VC-merge feature on LSC. (Note that VC-merge is enabled on LSC by default).

•RPM-XF eLSR only supports up to two MPLS subinterfaces. If you attempt to configure over the limit, an error message appears.

•Although RPM-XF VSI slave supports the connections statistics get command, only packet and byte counts are available. Therefore, use the show xtag cross-connect traffic int xtagatm command connection statistic to show how on the LSC module, packet counts from RPM-XF eLSR exist.

•OIR of MGX-1GE and MGX-1OC-12POS-IR back cards are supported only with interfaces in shutdown state.

•The MGX-1GE back card does not have the capability to provide line loopback.

•The Flow Control option is not configurable with the MGX-1GE back card.

•The MGX-1GE back card does not support SFP security.

•Line loopback and internal loopback cannot be set at the same time for the MGX-1OC-12POS-IR back card using AMCC Mux.

•The pos ais-shut command is not supported on MGX-1OC-12POS-IR back card.

•The traffic rate per flow is at half the interface speed for POS Gigabit Ethernet interfaces in this release.

•When traffic is traveling on Gigabit Ethernet interfaces, do not toggle autonegotiation. This may result in permanent disruption of traffic.

•For UBR, two queues always exist which results in half the flow rate for each flow because the hashing algorithm hashes the two into one queue.

The performance limits supported in Release 5.1.20 include the following:

•2K ATM SPVC connection endpoints

•2K Interface Description Blocks (IDBs)

•4K LVCs

•100 Virtual Path Connections (VPCs)

•256 policy map

•100 open shortest path first (OSPF) neighbors

•6 Cisco IOS-based cards in the Cisco MGX chassis

•500 VPN routing/forwarding instances (VRFs)

•500 BGP CE peers

•100 Routing Information Protocol (RIP) CE sessions

•500 Static CEs

•100,000 VPN Routes per PE

•250K non-VPN Routes per RPM-XF

•50 Xtag interfaces per RPM-XF

•300 OAM-enabled connections

For more RPM-XF performance details, contact your sales representative.

Notes and Cautions

Before you use this release, review the following notes and cautions:

•Attempting to initiate RPM-XF switchover when write mem is in progress on the active RPM-XF card may lead to the card coming up with a partial configuration. When an addred command is executed, an automatic write mem is triggered on the primary RPM-XF. If the primary card fails when the write mem is in progress, this is when you may see the card come up with a partial configuration. The duration of write mem depends on the configuration size and can take up to 4 minutes to complete.

•When you execute a dspcds command, a new stable boot-hold state appears on the PXM45. This state indicates that the RPM-XF is running only a boot image. This state is reached when the config register is set to 0x1 or when the bootldr cannot find the run-time image, but finds the boot image. Enter the cc command to access the RPM-XF from the PXM45.

•A valid boot image need not be the first file in the bootflash. The RPM-XF loads from any valid boot image from the bootflash:. The run-time image can be the first file in the bootflash flash and RPM-XF comes up with that image.

•Trying to change peak cell rate (PCR) value of a VP tunnel or changing the maximum transmission unit (MTU) of switch interface with more than 4000 VCs may overuse the CPU.

•If a large number of VCs (PVCs, LVCs or both) exist on the RPM-XF card and are executing disruptive operations on the main switch interface (int switch1), this may cause flapping of the protocols that run on these VCs. Examples of disruptive operations are clear int switch1 and modification of PVP parameters. These operations cause deactivation and reactivation of all VCs under the main switch interface. Depending on the number of VCs, the time required to complete such operations may exceed a certain protocol timeout limit. Examples of protocols that may be affected are OSPF and Tag Distribution Protocol (TDP)/Label Distribution Protocol (LDP).

•The RPM-XF VSI slave tends to put out informational warning/traceback messages caused by misconfigurations and connection admission control (CAC) failures (onto console/IOS log file). These messages are for information and debugging purposes. When these messages are observed, confirm that connection status is still intact and traffic is still passing successfully.

•Due to PXF SCR granularity, the configured SCR on the Cisco IOS pvc CLI may not be the same as the SCR programmed in the PXF. PXF bandwidth chunk size is 18 kbps. All PXF VC SCRs are programmed as multiples of 18 kbps. For instance, if the PVCs were configured with 50 kbps as PCR, 54 kbps are programmed in PXF. The show atm pvc commands shows 50 kbps, and the VSI slave accounts 50 kbps during CAC. However, 54 kbps is being used. As a result, when bandwidth use reaches the maximum value, both the VSI slave and the PNNI continue to allow connection provisioning, because the VSI slave and the PNNI available bandwidth show more than the PXF has remaining.

•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.

•For eLSR to LSC connectivity, use the default control VC of 32. If a PNNI partition exists with VCI 32 as part of its partition range, when an MPLS partition is added, there are two options to handle the situation:

–Add the MPLS controller and define its partition with available range. On eLSR, define the control VC from any VCI value within the range defined in the partition. The same VC should be defined on the LSC on the Xtag interface.

–Reconfigure the PNNI partition to spare the control VC usage on the RPM-XF and AXSM, AXSM/B or AXSM-E APS Management Information.

•Each time you change the RPM-XF configuration, enter the write mem command on the RPM-XF to save the configuration. If you do not do this, the changed configuration is lost on an RPM-XF card reboot or RPM-XF switchover, in the case of redundancy.

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)T5, 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 dspcd, dsprevs, 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.

RPM-XF Bootflash Precautions

The RPM-XF bootflash is used to store boot image, configuration, and run-time files. Erasing the boot image from the flash prevents the card from booting.

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

To avoid unnecessary failures that require card servicing, remember the following:

•Never erase the boot file from the RPM flash.

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

•Use care when "squeezing" the flash to clean it up.

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

If the bootflash is corrupt, use the tftpdnld command described in the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide or the xmodem procedure described in the "Using XModem to Download Flash to RPM-XF Cards" section to download a new boot image.

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

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

Open Caveats—Release 12.3(11)T6

Table 1 lists caveats in Cisco IOS Release 12.3(11)T6 for MGX Release 5.1.20.

Table 1 Cisco IOS Release 12.3(11)T6 for MGX Release 5.1.20—Open Caveats 

Caveat Number
Symptom
Conditions
Workaround

CSCef05018

Disconnecting and reconnecting a Gigabit Ethernet cable on an RPM-XF may cause the TCP/IP connection to be lost on the VISM.

This symptom is observed on an RPM-XF that runs Cisco IOS Release 12.2(11)YP and Release 12.3T.

None

CSCeg23771

All compressed UDP packets from a RPM_PR CE are dropped by PE RPM_XF.

Configure basic frame-based MPLS and send UDP traffic from CE to PE. This condition was observed on an RPM-XF that runs Cisco IOS Release 12.3(11)T.

Unknown

CSCeh56264

The PXM resets abnormally in the network due to TBB Length Error.

Under normal conditions. No special trigger found. This condition was observed on an RPM-XF that runs Cisco IOS Release 12.3(2)XZ.

None. The microcode module reloaded abnormally which resulted in a short duration of outage as the hardware forwarding is disabled.


Open Caveats—Release 12.3(11)T3

Table 2 lists caveats in Cisco IOS Release 12.3(11)T3 for MGX Release 5.1.00.

Table 2 Cisco IOS Release 12.3(11)T3 for MGX Release 5.1.00—Open Caveats 

Caveat Number
Symptom
Conditions
Workaround

CSCee75243

RPM-XF may reload abnormally during a rapid adding and removing of the service policy map.

While adding or removing service policy maps, the RPM-XF router reloaded abnormally with following error/traceback:

%GENERAL-3-EREVENT: Policy map is in use. Traceback = 400BAD74 400BB498 400BB6A0

Unknown

CSCef05018

Disconnecting and reconnecting a Gigabit Ethernet cable on an RPM-XF may cause the TCP/IP connection to be lost on the VISM.

This symptom is observed on an RPM-XF that runs Cisco IOS Release 12.2(11)YP but could also occur in Release 12.3.

None

CSCeg23771

All compressed UDP packets from RPM_PR CE are dropped by PE RPM_XF.

Configure basic frame-based MPLS and send UDP traffic from CE to PE.

Unknown

CSCeg24938

Continuously executes clear ip mroute * and causes RPM-XF to get reset.

While RPM-XF is configured as XF low speed, clear ip mroute * command was executed repeatedly which eventually caused the router to get reloaded abnormally.

Unknown

CSCeg27043

Peripheral Interface Manager (PIM) neighbors continue to flap after you have reloaded microcode.

This symptom is observed on a Cisco MGX 8850 series RPM-XF that runs Cisco IOS Release 12.3.

None

CSCeg40721

SAR tail drops seen on multicast PEs.

This problem was seen on a Cisco MGX8850 switch with RPM-XF cards running Cisco IOS Release 12.3(11)T images. Tail drops were observed on the SAR while sending bursty traffic to multiple multicast destinations.

Under investigation

CSCeg64074

The switch connection goes through the following states with the maximum PCR value: inSync, unknown, OnlyOnRPm

Create a switch connection between any two RPM_XF cards with service type VBR-nrt with a maximum PCR value.

None

CSCsa45189

Header compression is not working on an RPM-XF card that is configured for SAR-based CBWFQ.

This problem is seen when header compression is configured with a PPP configuration on a virtual template. This configuration is used because the PVC size is more than 768kbps and MLPPP does not support CoS for PVCs of this size.

Use a smaller PVC with MLPPP and cRTP.


Open Caveats—Release 12.3(7)T3

Table 3 lists caveats in Cisco IOS Release 12.3(7)T3 for MGX 5.0.10.

Table 3 Cisco IOS Release 12.3(7)T3 for MGX Release 5.0.10—Open Caveats 

Caveat Number
Symptom
Conditions
Workaround

CSCea84387

A user session may pause indefinitely, causing a Cisco router to become unresponsive.

This symptom is observed when multiple simultaneous users enter modular QoS CLI (MQC) commands on the same router through separate virtual type terminal (vty) sessions.

Allow only one user at a time to enter MQC commands.

CSCec16481

A Cisco device running Cisco IOS and enabled for the OSPF protocol is vulnerable to a Denial of Service (DoS) attack from a malformed OSPF packet. The OSPF protocol is not enabled by default.

The vulnerability is only present in Cisco IOS release trains based on 12.0S, 12.2, and 12.3. Releases based on 12.0, 12.1 mainlines, and all Cisco IOS images before 12.0 are not affected. Refer to the Security Advisory for a list of affected release trains.

Further details and the workarounds to mitigate the effects are explained in the Security Advisory which is available at:

http://www.cisco.com/warp/public/707/cisco-sa-20040818-ospf.shtml

CSCed05924

PXF reloaded abnormally due to software exception %PXF-2-FAULT:T0 SW Exception:CPU[t0r3c1] 0x00000180 at 0x0DE1 LR 0x084B.

MVPN traffic was being passed. No other activity was present on the card at that time.

Unknown

CSCed34575

An MPLS packet is transmitted without fragmentation even if the MPLS packet exceeds the outgoing interface MTU.

Occurs when the MPLS packet is greater than the outgoing interface MTU.

None

CSCed39641

SAR rx drops all packets because there is no buffer.

RPM-XF is configured as a PE in a frame-based or cell-based MPLS or VPN network. Executing the sh pxf cpu buff leaked 0-5 or clear interface sw1 command while the system is under load may cause a SAR rx failure.

None

CSCed48954

Traffic tail drops on the output of a Gigabit Ethernet interface even when the traffic rate is well below the interface limit.

Occurs after multiple Gigabit Ethernet interface flaps.

Reload the PXF using the microcode reload pxf command.

CSCed86771

Removing or inserting an RPM-XF while running call rate made the card reload/failed.

Occurs while running 360K Busy Hour Call Attempts (BHCA) with 120-second CHT. Upon removing an RPM-XF card and putting it back into the rack, this RPM-XF card rebooted and entered failed state.

None

CSCee36771

A PPPoA interface constantly flaps when passing data with SAR-based CBWFQ enabled.

Observed under the following conditions:

•SAR-based CBWFQ is enabled on a PPPoA interface.

•The class default is assigned a small bandwidth (less than 10 percent).

•All classes on the VC are congested.

Assign 10 percent bandwidth to the class-default of the policy map attached to the interface.

CSCee53246

The standby (secondary) RPM does not release the config_file boot variable after the primary redundant RPM card takes over after the card switch over command was executed.

This intermittent symptom was observed after a switchover from secondary RPM card to primary RPM card. The secondary (redundant) card is in standby state, but the show bootvar command still shows that the config_file variable is not null.

Unknown


Resolved Caveats—Release 12.3(11)T6

Table 4 lists resolved caveats in Cisco IOS Release 12.3(11)T6 for MGX Release 5.1.20.

Table 4 Cisco IOS Release 12.3(11)T6 for MGX Release 5.1.20—Resolved Caveats 

Caveat Number
Description

CSCdz67845

The other counts field in the show ip mroute CLI command output is not accurate.

CSCed43120

Traffic rate distribution between classes during congestion is not according to the specified class bandwidth.

CSCee25068

RPM-XF card with SAR-based QOS failed with Data Path Check Failed logged.

CSCeg20467

show pxf cpu cef verify fails for 0.0.0.0/0 if the default route is not configured on the RPM-XF.

CSCeg23176

An RPM-XF is reset by the PXM because of an SCM poll timeout. A PCI information file is generated in the bootflash memory just before the RPM-XF resets.

CSCeg24938

An RPM-XF resets when you enter the clear ip mroute * command repeatedly.

CSCeg27043

PIM neighbors continue to flap after you have reloaded microcode.

CSCeg40721

Tail drops were seen on SAR CoS queues in XF low speed PEs.

CSCeg48606

A PXF stall error occurs, followed by a PXF crash.

CSCeg58427

It is difficult to detect any PXF programming errors in multicast FIB.

CSCeg61656

Bandwidth change on the bundle is not reflected on the RPM-XF switch sub i/f.

CSCeg64074

Switch connection creation with SCR at OC24 rate(1197656 kbps) fails.

CSCeg67839

The router stops responding when the CLI sh pxf cpu cef command is used in certain circumstances.

CSCeg69006

An alignment trace is seen in the RPM-XF log of the form %ALIGN-3-TRACE: Traceback = 4009E4C8 400AB6AC 404DB994 404DE5DC 404DEAA4 404DEE5C 404FDC4C 400AC160.

CSCeg69019

When cwaChanDirectRoute is queried through SNMP, it returns a large int value instead of 1 or 2.

CSCeg80790

The commands show policy-map int Switch1.x and show pxf cpu police <policymap-name> can show different values for confirm burst (Bc) and there could be some drops on the policy map.

CSCeg84573

Traffic, including cell-based MPLS traffic, may be affected (that is, traffic may be dropped, or its behavior may be modified) after you have modified a QoS policy map that is already attached to an interface by way of adding a new class or deleting an existing class.

Additionally, when a cell-based interface is affected by this symptom, traffic on other switch subinterfaces may also be affected even though the same policy map is not applied to these subinterfaces.

CSCeg89665

After you enter switchredcd on RPM-XF cards, the Gigabit Ethernet port on the RPM-XF back card does not forward or receive any traffic.

CSCeh05199

The sh rpm iphc connection command does not show all details for a flow on an IPHC-enabled interface.

CSCeh05517

It is difficult to detect PXF programming errors in multicast FIB's output interface list.

CSCeh05540

Packet statistics that are displayed under an L2 policy map are incorrect. The counters that show incorrect information are the Conformed packets/bytes and Exceeded packets/bytes counters.

CSCeh08537

The sh rpm iphc hash-cids command gives the hash-index but not the connection identifier (CID) for an IPHC flow.

CSCeh10391

An OamLpbkFail alarm is not cleared after a VISM card is reset.

CSCeh11228

Some data MDT may have the register flag stuck after card reload.

CSCeh12908

Unable to view the compressor side context on IPHC-enabled interfaces on an RPM-XF.

CSCeh13435

You cannot view the decompressor side context on IPHC enabled interfaces on an RPM-XF.

CSCeh14591

The following error message appeared %SYS-3-MEMLITE: Free lite called for non lite chunk by 0x400B93C4.

CSCeh15563

SAR CoSQ channel sometimes becomes stuck in close_pending state.

CSCeh15949

An extended access list does not function when it is applied to an interface even though the access list is configured correctly.

CSCeh22616

The output queue of a Fast Ethernet back card of a Cisco MGX RPM-XF may be stuck at 40/40.

CSCeh23404

The VC becomes inactive. ATM periodic process fails to delete the VC and reports tracebacks.

CSCeh27803

An MLP bundle is incompletely set up on an RPM-XF, and therefore the MLP traffic is lost.

CSCeh30818

A traceback is generated when multicast traffic is flowing. This symptom is observed when a PIM is enabled on multiple interfaces and when the counters are cleared.

CSCeh35987

The policy map counter displays incorrectly after you modify a CoSQ channel parameter.

CSCeh44900

Tracebacks are seen while modifying the Access list.

CSCeh46004

A SAR ucode reload is not recorded.

CSCeh46547

Alignment errors logged with fast-switched IP packets sent over a Multilink interface.

CSCeh49205

Ping fails after enabling ip cef accounting.

CSCeh53494

Input policy map change causes the system to warn that the associated input service policy is being removed due to incompatible command usage.

CSCeh54816

L2 policing is incorrect. It shows a greater number of cells than used by the cRTP packet for certain packet sizes.

CSCeh61337

The commands ip icmp rate-limit unreachable and ip icmp rate-limit unreachable DF are always set at 500 ms.

CSCeh61775

It is difficult to detect any rewrite string errors in multicast FIB.

CSCeh67651

The policy map output counters are incorrect. They do not show the total number of packets, such as transmitted + dropped < input count. This problem manifests when there is congestion and is only seen for non-llq classes (excluding class-default).

CSCin90062

VSICMERR136 logged in an RPM-XF VSI slave for connections in CmtPend state.

CSCsa45270

The show policy interface multilink <no:> command shows discrepancy in total transmitted+ random drop + tail drop and the number shown to be received on the remote end.

CSCsa71055

Pings from a PE router to the Ethernet interface of a CE router fail.

CSCsa86250

The CPU use of a Cisco MGX series RPM-XF increases to 99 percent when a Gigabit Ethernet (GE) interface of a peer RPM-XF is shut down.


Resolved Caveats—Release 12.3(11)T3

Table 5 lists resolved caveats in Cisco IOS Release 12.3(11)T3 for MGX Release 5.1.00.

<

Table 5 Cisco IOS Release 12.3(11)T3—Resolved Caveats 

Caveat Number
Description

CSCee63435

The RPM-XF VSI slave does not reply with extended VSI negative acknowledgement (NAK) error codes 51-54.

CSCee65241

In the show policy-map interface command, all police counters should be read as Layer 2 counters.

CSCef91218

An RPM-XF corrupts the DSCP values of traffic passing through.

CSCef36941

Apart from real time traffic streams, the RPM-XF card compresses the UDP traffic also on the Multilink interface configured for IP Header compression and connected to Customer router. The compressed UDP traffic received by the CE creates some problems thus making the CE unstable.

CSCef92881

Output of traceroute incorrectly shows the next hop entry for an interface on RPM-XF as 0.0.0.0 instead of showing the IP address of the interface.

CSCef95597

RPM-XF router reloads abnormally when the ATM encapsulation for a PVC is changed.

CSCeg10138

The 64-bit counters in the output of a show policy-map command may not provide correct information.

CSCeg16660

Load balancing of traffic works inconsistently if the traffic flow reaching the particular PE was already load balanced at a previous hop by another PE.

CSCeg16953

DBF tracebacks on RPM-XF by RPM-XF VSIS process.

CSCeg17058

There is not enough information to verify the exact cause of memory-related ECC errors for a PXF ASIC present on an RPM-XF.

CSCeg17274

When you enter a timeout value shorter than 8 seconds on an compression-enabled interface, the value is not configured. Instead, a timeout value of 8 seconds is configured.

CSCeg18940

Connection level parameter mismatch between RPM-XF and Cisco WAN Manager (CWM) Db.

CSCeg20768

The OSPF cost calculation is not triggered when the DBF update is received.

CSCeg24025

IPCP between MWR and RPM-XF does not come up after throttling Q2 on an MPSM.

CSCeg25053

There is no notification message in the log buffer or on the console related to the Switch Connection Synchronization applicable to Auto Resync or Manual Resync.

CSCeg27046

Important system and CPU register values are not stored into the Crashinfo file if the router reloaded abnormally.

CSCeg28876

no ip route-cache appears under the MLPPP interface in the configuration even though route-cache is enabled by default. In addition, no ip route-cache cef occasionally appears.

CSCeg31236

Spurious memory access is seen along with the traceback.

CSCeg34852

VCCI drops on RPM-XF after resetting the MPSM card.

CSCeg36182

The RPM-XF card does not come up after reload and some tracebacks are observed.

CSCeg47178

The clear counters command takes a long time to zero out the average offered/drop rate counters.

CSCeg65037

swfpga cam overwrites, which results in a dangling connection.

CSCeg65362

The show policy interface <intf> input command shows more packets are received than the show interface <intf> precedence command.

CSCin81995

The SAR engine on a RPM-XF shows buffer exhaustion, causing data drops.

CSCin84419

Multicast traffic is punted to the RP, the CPU utilization is high, and the output of the show pxf cpu mroute vrf [vrf-name] command shows that the "No_FS" flag is set for a (S,G) entry and does not clear.

CSCin84421