Table Of Contents
Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00
Contents
About These Release Notes
Special Notes
New Features
Features Introduced with 12.3(2)T5
Features Introduced with 12.3(2)T4
Link Fragmentation Interleaving (LFI)
Increase the Maximum Number of Policy Maps to 2048
MPLS VPN Multicast
cRTP
WRED Drop Counters
TMS
SAR based TM/QoS
TCP de-compression
Dual MPLS Partition for RPM-XF (related to LSC redundancy)
Feature Introduced with 12.3(2)T2
2-Port POS (Packet Over SONET) and 2-Port GIG-E (Gigabit Ethernet) Service Module Back Cards
Features Introduced Prior to 12.3(2)T2
MGX 8950 Support for RPM-XF
EiBGP Load Balancing
IP Accounting Counters
Multiple Actions under Police Command
QoS Sub Optimal Link Utilization
RPM-XF Redundancy Support
Features Not Supported in This Release
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
Open Anomalies —Release 12.3(2)T5 for RPM-XF
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 12.2.x IOS Baseline
Resolved Caveats—Release 12.2(15)T5
Resolved Caveats in Release 12.2.15T
Resolved Caveats Prior to Release 12.2.15T
Related Documentation
Obtaining Documentation
Cisco.com
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco TAC Website
Opening a TAC Case
TAC Case Priority Definitions
Obtaining Additional Publications and Information
Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00
These release notes are part OL-4536-01 Rev. B0, August 18, 2004
Contents
Limitations: 6
Limitations: 7
About These Release Notes
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription.
Note that for Release 5.0.00 user documentation (command reference, overview, and installation and configuration guides), use the MGX Release 4 and Cisco IOS documents in addition to this release note.
Product documentation for Release 5 of the MGX 8850 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/index.htm
Product documentation for Release 5 of the MGX 8950 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8950/rel5/index.htm
Special Notes
Please refer to the this Web page for the latest updates on IOS software and firmware issues.
http://www.cisco.com/cgi-bin/Software/Iosplanner/Planner-tool/printsa.pl?get_crypto=&data_from=&hardware_name=&software_name=&release_name=12.3.2T&majorRel=12.3&state=:RL&type=Early%20Deployment&file=12.3.2T.c.html
Note that the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 manual describes some features that are not supported in this release. Refer to the section entitled "Features Not Supported in This Release" section for a list of the affected features.
New Features
The MGX RPM-XF is a next-generation, high performance model of the RPM for the MGX 8850 and MGX 8950 platforms, using PXM45 processor modules. It is a router module based on an RM7000A MIPS processing engine that fits into slots 1-6 and slots 9-16 in the MGX 8850 and slots 1-6 and slots 11-16 in the MGX 8950.
The RPM-XF hardware provides forwarding technology for packet switching capabilities in excess of 2-million pps. The forwarding engine is packet based and is interfaced to the midplane of the system through a combination of switch interface technologies. For more information on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.
Features Introduced with 12.3(2)T5
No new features were introduced with release 12.3(2)T5.
Features Introduced with 12.3(2)T4
Link Fragmentation Interleaving (LFI)
The 12.3(2)T5 release adds support for Link Fragmentation Interleaving (LFI). 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.
IOS configuration information can be found at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121newft/121t/121t5/dtlfifra.htm
Increase the Maximum Number of Policy Maps to 2048
Policy maps along with class maps and service policy maps are used to define a traffic policy and attach them to an interfaces. Prior to this release, you were able to create 256 separate policy maps and a total of 256 class maps per policy map. With this release, the maximum number of policy maps has been 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.
MPLS VPN Multicast
The frame-based Multicast VPN (MVPN) feature enables the RPM-XF to pass frame-based multicast traffic to VPNs across the ATM core.
Configuration information can be found at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122s/122snwft/release/122s14/fs_mvpn.htm
cRTP
The cRTP acronym refers to the Compressed Real-Time Protocol (CRTP) header. This release of the RPM-XF adds the ability to configure this header.
Below are the CLI commands introduced to support this feature:
–
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 match in policy map.
Configuration information can be found at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthdrcmp.htm
WRED Drop Counters
The WRED Drop Counters feature adds Class-Based Packet Counters to existing RPM-XF functionality. The counters can be dscp based or precedence based. For more information on the CLI commands that have been introduced or modified to support the WRED Drop Counters feature on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.
TMS
The TMS (Traffic Matrix Statistics) 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 the CLI commands that have been 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.
SAR based TM/QoS
Traffic Management, Weighted RED, and Cell-Based Weighted Fair Queuing algorithm processing is now accomplished using the Segmentation and Reassembly engine (SAR).
TCP de-compression
The 12.3(2)T2 release adds support for TCP de-compression as an adjunct to supporting the Compressed Real-Time Protocol (CRTP) header feature on the RPM-XF.
Dual MPLS Partition for RPM-XF (related to LSC redundancy)
The 12.3(2)T2 release adds support for dual MPLS partitions on the RPM-XF.
Configuration information can be found at
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px1e/rel4/scg/rpm.htm
Feature Introduced with 12.3(2)T2
2-Port POS (Packet Over SONET) and 2-Port GIG-E (Gigabit Ethernet) Service Module Back Cards
The 12.3(2)T2 release adds support for two new service module back cards that provide either two GIG-E (Gigabit Ethernet) or two POS (Packet Over SONET) ports. For more information on the fit and function of these 2 new service module back cards as well as the CLI commands that have been introduced or modified to support these 2 new service module back cards on the RPM-XF, refer to the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4.
Features Introduced Prior to 12.3(2)T2
MGX 8950 Support for RPM-XF
In Cisco MGX Release 3.0.10 and later, the MGX 8950 supports the MGX RPM-XF card set. The MGX RPM-XF card set can occupy any of the available service module slots in the MGX 8950, which are slots 1-6 and slots 11-16.
EiBGP Load Balancing
To balance load by BGP on multiple paths to 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 has been enhanced to show the multipaths.
Each multipath is marked as 'multipath'.
The bestpath is marked as 'multipath' and 'bestpath'.
The output also has what flavour of multipath 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)
Advertised to non peer-group peers:
7.0.76.2 from 7.0.76.2 (100.0.0.2)
Origin IGP, localpref 100, valid, external, multipath,
best
7.0.76.9 from 7.0.76.9 (100.0.0.9)
Origin IGP, localpref 100, valid, external, multipath
|
Limitations:
•If there are multiple alternate paths for the peering point, only one of the paths is utilized for a given prefix.
•Only per-flow load balancing is supported. Per-packet load balancing is not supported.
•Supported only in MPLS/VPN networks.
•Load balancing proportional to the link's bandwidth [dmz-linkbw] is not supported. The load balancing will be performed on the available links with equal costs.
•The maximum number of paths that can be used for load sharing is 6. This is the current IOS limitation too.
•Load balance will not work if RDs are same with RR. RDs have to be different if RRs are used.
•CEs in different VPNs using same RDs does not work.
IP Accounting Counters
MGX RPM-XF stores the packet/byte counters based on precedence/DSCP values on a per interface level at input ONLY.
The following CLI have been 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:
•Counters are maintained ONLY at input per interface.
•There is no count of dropped/transmitted based onDSCP/PREC packets per interface.
Multiple Actions under Police Command
The MGX RPM-XF police command is now similar to the IOS/RPM command. Therefore, multiple exceed and conform actions can be applied on the police command.
The police CLI command has been enhanced as follows:
Prior to 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 allows only one value for conform-action and exceed-action.
The newly enhanced 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 multiple conform-action and exceed-action parameters can be configured.
QoS Sub Optimal Link Utilization
RPM-XF uses VTMS as a scheduling algorithm. VTMS schedules queues based on the current link utilization 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 utilize the link.
In this release, a fix is made (via a new CLI command) to allow the user to specify the over subscription factor on a queue. The factor is in the range on 1-31 and can be denoted as 2n. An over subscription factor of n = 2 on any queue, essentially means to subscribe that queue by a factor of 4 ( 2n where n (in this example) is 2; so 2 raised to power 2=4).
The new syntax for bandwidth and priority commands are:
[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. Currently we support redundancy that ensures Layer 2 state restoration. Layer 3 state is restored via convergence.
Note When resetting a shelf with RPM-XFs configured for 1:N redundancy, it is recommended that you bring up the primary slots in active state.
The main benefits of 1:N Redundancy are:
•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 done 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 backcards during front card switchover.
•Y cable redundancy support for POS backcards during front card switchover. (With Y cable, 1:N redundancy is restricted to N = 1).
The following are the general guidelines for redundancy on the RPM--XF:
•Addred 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.
•Removal of the Active RPM-XF back card does not cause switchover to the standby RPM-XF.
•User has to make sure that E:RPM/auto_config_slot# is created before adding redundancy. This may require a login to primary card through the command line and manually adding boot config e:auto_config_slot# followed by a write mem.
•Executing switchcc back-to-back with switchredcd can cause problems. We recommend giving a gap of at least 5 seconds between switchredcd and a switchcc.
•IOS software on a standby card should be the same or higher version than the Active RPM-XF card.
•Booting the card from an image on tftp server is not recommended when the card is in redundancy group. The card should be booted from image in bootflash or PXM disk only.
•Configuring the standby RPM-XF is not recommended.
Features Not Supported in This Release
The following features are not supported in this release.
•LSC Redundancy
•MPLS TE tunnels on ATM Interfaces
•VC Merge
•RPM-PR to RPM-XF upgrade
•OIR of backcards without interfaces in shutdown mode
•Per packet load balancing
•Modem connectivity on Auxiliary port
•ROMMON's Xmodem functionality does not support the Speed option.
Network Management Features
Network management features are detailed in the Release Notes for Cisco WAN Manager 15.0.00 at:
http://cisco.com/univercd/cc/td/doc/product/wanbu/svplus/15/rnotes/index.htm
SNMP MIB
SNMP MGX Release 5.0.00 MIB files are provided with the delivery of this release. The MIB files are in standard ASN.1 format and are located in the same directory within the release bundle on CCO. 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 this bundle. They are part of the 12.3(2)T5 CCO release.
RPM-XF Limitations and Restrictions
The RPM-XF limitations and restrictions that apply to this release are as follows:
•E: RPM/auto_config_slot# must be created before adding redundancy. This may require a login through the CLI and manually adding the boot config command followed by a write mem.
•PVPs can not operate at a rate greater than 599039 kbps.
•High speed VC (SCR greater than or equal to 599,039 kbps) would not get full-configured rate for single flow (unique source and destination IP address). This happens because for high speed VCs, the PXF creates two queues and these queues can't be shared for same stream. Sharing two queues for same stream would cause out of sequence packets.
•PXF queue selection algorithm may cause traffic drop for multiple stream going to same destination via multiple paths. When the PXF gets 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 there are multiple paths for the same destination, there is a possibility that multiple streams would hash to one queue, causing some queues to overflow, while others might be under-utilized.
•PXF buffer depletion may occur if packets of the same size (especially packets greater than 640 bytes) are sent to a congested interface.
•Currently VBR-nrt and VBR-rt are treated with same priority system wide.
•RPM-XF PVP only supports UBR.
•PVP in RPM-XF is not OAM managed.
•If out-of-sync SPVC or SPVP exist on RPM-XF, shrinking of PNNI partition would not be permitted.
•A single RPM-XF can only function as either an Edge LSR or as an LSC, but not as both.
•Because RPM-XF only supports UBR, VBR-rt and VBR-nrt, on the PXM, dsppnportrsrc for RPM-XF port will show 0 available resource for CBR, ABR and signaling service types. Also, cnfpnportcac for CBR and ABR will be rejected.
•If RPM-XF is configured as an eLSR, RPM-XF does not support incoming VC-merge LVCs. There is a problem logged against LSC module that it cannot support both VC-merge/non-VC-merge supporting 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 at most two MPLS sub-interfaces. Attempting to configure over the limit will result in an error message.
•Although RPM-XF VSI slave supports connections statistics Get command, only packets and bytes counts are available. Therefore, show xtag cross-connect traffic int xtagatm connection statistic display on LSC are actually packet counts from RPM-XF eLSR.
•OIR of MGX-1GE and MGX-1OC12POS-IR back cards are supported only with interfaces in shutdown state.
•MGX-1GE back card does not have the capability to provide line loopback.
•Flow Control Option is not configurable with MGX-1GE back card.
•MGX-1GE back card does not support SFP security.
•Line loopback and internal loopback cannot be set at the same time for the MGX-1OC12POS-IR back card with AMCC Mux.
•pos ais-shut command is not supported on MGX-1OC12POS-IR back card.
•Traffic rate per flow is at half the interface speed for POS/GigE interfaces in this new release.
•Autonegotiation is not recommended to be toggled on GigE interfaces when traffic is going through. This may result in permanent disruption of traffic.
•For UBR 2 queues always exist which would result in half the Flow rate for each flow because of hashing algorithm hashing into single queue .
The performance limits supported in this release are the following:
•2K ATM SPVC Connection endpoints
•2K IDBs
•4K LVCs
•100 VPCs
•256 Policymap
•100 OSPF neighbors
•6 IOS-based cards in MGX shelf
•500 VRFs: 500
•500 BGP CE Peers
•100 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
The following notes and cautions should be reviewed before using this release.
•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 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, the card may 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.
•There is a new stable "Boot-Hold" state displayed on the PXM45 when dspcds is executed. This state indicates that the RPM-XF is running only boot image. This state is reached when config register is set to 0x1 or when the bootldr cannot find the run-time image, but found the boot image. Enter cc to access the RPM-XF from the PXM45.
•Valid boot image need not be the first file in the boot flash. The RPM-XF will load from any valid boot image from the bootflash:. The run-time image can be the first file in the boot flash and RPM-XF will come up with that image.
•Trying to change PCR value of VP tunnel or changing MTU of switch interface with more than 4K VCs may cause CPU hog.
•If there is a large number of VCs (PVCs or LVCs or both) on RPM-XF card, executing disruptive operations on the main switch interface (int switch1) may cause flapping of protocols that run on these VCs. Examples of disruptive operations are clear int switch1 and modification of PVP parameters. These operations cause deactivation and re-activation of all VCs under the main switch interface. Depending on the number of VCs, the time required to complete such operations may exceed certain protocol timeout limit. Examples of protocols that may be affected are OSPF and TDP/LDP.
•RPM-XF VSI slave tends to output informational warning/trace back messages caused by misconfigurations and CAC failures (onto console/IOS log file). These messages are mostly for information/debugging purpose. 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 IOS pvc CLI may not be the same as the actual scr programmed in the PXF. PXF bandwidth chunk size is 18 kbps; all PXF VC scr will be programmed as multiples of 18 kbps. For instance, if the PVCs were configured with 50 kbps as pcr, 54 kbps would be programmed in PXF. show atm pvc display will show 50 kbps, and VSI Slave will account 50 kbps during CAC. However, 54 kbps is actually being used. So as a result, when bandwidth usage is reaching the maximum value, both VSI Slave and PNNI will continue to allow connection provisioning, because VSI Slave and PNNI available bandwidth shows more than PXF actually has left.
•Saveallcnf (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 prior to the entering saveallcnf command. This also ensures that the RPM-XF files on the active PXM45 hard disk will contain the latest configuration to be saved.
•For ELSR to LSC connectivity, the default control VC used is 32. If 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 control VC from any VCI value within the range defined in partition. The same VC should be defined on LSC on xTag interface.
–Reconfigure PNNI partition to spare the control VC usage both on RPM-XF and AXSM, AXSM/B or AXSM-E APS Management Information.
•Whenever the RPM-XF configuration is changed, enter the write mem command on the RPM-XF to save the configuration. If this is not done, the changed configuration will be 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. The slot# portion of the name should be set 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 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 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, then the NVRAM version is used.
Note In case of RPM-XF redundancy, the configuration should always be stored in auto_config_slot# file in the E:RPM directory of the PXM45 hard disk. Failure to find the auto_config file will lead to aborting of a user-initiated switchover (switchredcd) and a fatal error will be flagged.
Card Management
The following card management notes and cautions should be reviewed before using this release.
•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 will display as boot>
•The run-time IOS image cannot be used as a bootloader to load a different IOS image.
•Change of 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 will bring the card to its original stable state.
Note It is recommended to always use 9600 baud as the console speed.
•The IOS version of the runtime as well as the boot image will be displayed in the dspcd, dsprevs, and dsprevs -s output. The version will be displayed under the heading of IOS version. Revision Control is not available for RPM-XF (like RPM-PR).
Note The commands loadrev and setrev 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 will cause the card to not boot.
The RPM-XF boot image, which comes loaded on the Flash, will work for all RPM-XF IOS images. Therefore, there is no reason to delete or move the factory installed boot image.
In order to avoid any unnecessary failures that would require card servicing, do 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.
As long as the boot file remains intact in the first position on the flash, the RPM-XF will boot successfully.
If the bootflash is corrupted, use the tftpdnld procedure described in the Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide or xmodem procedure described in "Using XModem to Download Flash to RPM-XF Cards" later is this document to download a new boot image.
Open Anomalies —Release 12.3(2)T5 for RPM-XF
Table 1 lists the open caveats in Cisco IOS Release 12.3(2)T5 as of April 14, 2004.
Table 1 Open Anomalies on 12.3(2)T5 for RPM-XF
Caveat Number
|
Description
|
CSCec16481
|
Symptom:
A Cisco device running Internetwork Operating System (IOS) and enabled for the Open Shortest Path First (OSPF) Protocol is vulnerable to a Denial of Service (DoS) attack from a malformed OSPF packet. The OSPF protocol is not enabled by default.
Conditions:
The vulnerability is only present in IOS release trains based on 12.0S, 12.2, and 12.3. Releases based on 12.0, 12.1 mainlines and all IOS images prior to 12.0 are not affected. Refer to the Security Advisory for a complete list of affected release trains.
Workaround:
Further details and the workarounds to mitigate the effects are explained in the Security Advisory which is available at the following URL:
http://www.cisco.com/warp/public/707/cisco-sa-20040818-ospf.shtml.
(This caveat was added August 18, 2004)
|
CSCdy81782
|
no shut on the ppp interface before VA goes down causes pxf to drop
Symptom:
"no shut" on the PPP interface before VA goes down causes PXF to drop certain packets. This results in being unable to have successful ping through routes involving such a PPPoA subinterface from a remote node. Arriving ICMP packets are dropped in PXF.
Conditions:
Under a PPPoA subinterface, if "shut" and "no shut" commands are issued in succession such that "no shut" is completed before the associated virtual-access goes down.
Workaround:
After a "shut", wait until the associated virtual-access changed to go down before issuing "no shut". If symptom occurs, go to the subinterface, perform a "shut", wait for the associated virtual-access to go down and then perform a "no shut".
Further Problem Description:
When node is in this condition, pings originating from the local node and none-ICMP traffic appears to work correctly. Only pings from a remote node would fail.
|
CSCed05924
|
Symptom:
PXF reloaded abnormally due to software exception
%PXF-2-FAULT:T0 SW Exception:CPU[t0r3c1] 0x00000180 at 0x0DE1 LR 0x084B
Conditions:
MVPN traffic was being passed. No other activity on the card at that time.
Workaround:
Unknown.
|
CSCed16744
|
Symptom:
Traffic does not resume after SAR is brought out of hang state.
Conditions:
"sh rpm mxt46 rx chip" command executed several times, via a script, may cause traffic to stop completely
Workaround:
Use "microcode reload sar rx" to bring device to normal state.
|
CSCed34575
|
Symptoms:
MPLS packet will be transmitted without fragmentation even if the MPLS packet exceeds the outgoing interface MTU.
Conditions:
When the MPLS packet is greater than the outgoing interface MTU.
Workaround:
None.
|
CSCed39641
|
Symptoms:
SAR rx drops all packets due to no buffer
Conditions:
RPM-XF configured as PE in frame-based or cell-based MPLS/VPN network. Execute "sh pxf cpu buff leaked 0-5" or "clear interface sw1" command while system is under load, may cause SAR rx failure.
Workaround:
None.
|
CSCed41823
|
Symptom:
Tail drops on PXF queues and protocols go down. Tx SAR stats show no activity as Tx SAE looks hanged and it is not processing any traffic.
Condition:
This condition was reached when "microcode reload sar tx" command was executed multiple times via a script.
Workaround:
Execute "microcode reload sar tx" again.
|
CSCed46603
|
Symptoms:
MIB walk on ifOutDiscards object OID returns an error message. MIB query on ifInDiscards and ifOutDiscards together, returns ifOutDiscards object data.
Conditions:
The following query will always return "noSuchName" when querying an AAL5 layer:
snmpget <IP> <community string> ifOutDiscards.<instance>
Workaround:
Unknown.
|
CSCed48954
|
Symptoms:
Traffic will tail drop on the output of GigabitEthernet interface even when the traffic rate is well below the interface limit.
Condition:
This problem seems to happen after multiple GigabitEthernet interface flaps.
Workaround:
Reload the PXF using "microcode reload pxf" command.
|
CSCed53155
|
Symptom:
After failure recovery, the SAR Segmenter is not programmed correctly.
Condition:
A SAR fatal error occurred which generated a interrupt to the host causing a SAR reset.
Workaround:
Reload/Restart the SAR microcode via one of the following commands:
micro reload sar tx
or
micro reload sar rx
|
CSCed62886
|
Symptom:
TagI counter always shows 0 in the output of "show pxf cpu cef mem" command.
Condition:
This condition can be observed always.
Workaround:
Unknown.
|
CSCed68881
|
Symptom:
"sh controller" output is not part of sar info files. Also the timestamp of last mxt4600 interrupt is incorrect and mxt4600 info file generation stops at max files allowed + 1. The first interrupt is wrongly classified as a continuous interrupt.
Conditions:
When a SAR fatal error occurs and triggers an interrupt to the host.
Workaround:
None.
|
CSCed71495
|
Symptoms:
The exp bit on the topmost label is not changed when set mpls exp topmost is configured on the ingress interface of the P router.
Conditions:
This occurs with the use of the "set mpls exp topmost" command on the ingress interface of the P router in a frame based MPLS network
Workaround:
Use the same command on the PE router egress interface (towards P).
|
CSCed74882
|
Symptoms:
Following Tracebacks were observed when pumping traffic via POS and GigE backcards.
*%SYS-3-CPUHOG:Task is running for (2000)msecs, more than (2000)msecs (0/0),process = Router Init.
-Traceback= 40623AB0 40623B6C 40624054 407CF300 406237E8 40622650 403F1790 403F1774
Conditions:
This error message is logged when we pump more POS and GIGE traffic (around OC3 rates) through 2000 LVCs for 10 min.
Workaround:
None.
|
CSCed75086
|
Symptom:
When issuing the command show pxf cpu rewrite verification x.x.x.x you receive an error message stating that the "Channel ID in the SAR header is non-zero (x) for MVC".
Conditions:
In a cell based mpls VPN network with multi-VC, if the first label (IGP label) value is greater than 0xF.
Workaround:
None.
Ignore this message and verify that the channel ID is correct by executing: "sh pxf cpu cef <prefix used to verify>" and "sh pxf cpu rewrite <rw_index>"
|
CSCed82673
|
Symptom:
An RPM-XF card may reload abnormally when issuing some of the display commands under "show rpm vsis core conn debug-command <WORD> <Argument#1>"
Conditions:
Issuing those command with large numbers of argument values.
Workaround:
None.
|
CSCed86771
|
Symptoms:
Pull/insert RPM-XF while running call rate, made the card to reload/failed.
Conditions:
While running 360K BHCA (Busy Hour Call Attempts) with 120 sec CHT. Upon pulling one of RPM-XF card and putting it back into the rack, this RPM-XF card rebooted and went to failed state.
Workaround:
None.
|
Resolved Caveats—Release 12.3(2)T5
Table 3 lists the resolved caveats in Cisco IOS Release 12.3(2)T5 as of April 14, 2004.
Table 2 Resolved Caveats in Cisco IOS Release 12.3(2)T5
Caveat Number
|
Description
|
CSCed41905
|
DT: Automatic OIR occurred on RPM-XF card and the RPM-XF rebooted.
|
CSCed74712
|
SFP security check fails with 2-port GigE card for new SFP
|
CSCed48941
|
LSNT:PE crash with no memory for XCM temp buffer logged
|
CSCeb74859
|
DE-LSNT:BGP flap when apply/remove output policy map
|
CSCec14218
|
Trace back messages
|
CSCec84591
|
LSNT: Barium Asserted CRC error when clear int sw1
|
CSCec89536
|
LSNT: reassembler multi-bit error cause card crash
|
CSCed00196
|
RPM-XF: <show pxf tfib> doesn't display load balanced routes
|
CSCed21634
|
Need to change exp bit on topmost label on egress interface
|
CSCed30548
|
RPM-XF - input policy map does not match against mpls exp bit
|
CSCed46492
|
Ethernet Port E2/1 on RPM-PR Card Gets Shutdown Upon Resetcd
|
CSCed34585
|
Channel ID is incorrect for certain prefixes if multi-VC is enabled
|
CSCed35834
|
LSNT: Hub router with 2 POS up links crash due to bus error
|
CSCed35859
|
Need to change the way PXF services the IP packets with option
|
CSCed41293
|
LINT:improve PXF CEF and TFIB command output
|
CSCed47631
|
sar resetinfo files don't get written to the bootflash at times
|
CSCed49968
|
OSPF flaps between PE-LSC while congesting input hold queue
|
CSCed50101
|
Need 6s wait before turn on ATM OAM to VXSM while RPMXF GE is up
|
CSCed54591
|
Sar crashinfo does not capture event log but resets the event log
|
CSCed63090
|
RPM-XF: reload occurs when defragmenting ACL XCM memory
|
CSCed69526
|
Process sleep not allowed while interrupts are disabled.
|
Resolved Caveats—Release 12.3(2)T4
Table 3 lists the resolved caveats in Cisco IOS Release 12.3(2)T4 as of February 9, 2004.
Table 3 Resolved Caveats in Cisco IOS Release 12.3(2)T4
Caveat Number
|
Description
|
CSCec13765
|
micro code reload clears the crtp enable flag for ppoA links
|
CSCec09316
|
packet with out of range CID should be dropped
|
CSCec43590
|
RPM-XF IPHC does not decompress 16-bit paks with IP options
|
CSCec40662
|
RPM-XF reloads during <show pxf cpu rewrite tree> command
|
CSCec67863
|
RPM-XF: Memory leak when removing MDT
|
CSCec63848
|
RPM-XF: Some PXF drop counters are not cleared
|
CSCec31168
|
mVPN Tunnel receive counters not implemented
|
CSCec64570
|
Both local CEs cannot ping remote PEs, and hop count is 13
|
CSCeb59710
|
DE-LSNT:protocols flap on ELSR when withdraw LVCs
|
CSCec45704
|
LSNT:binding infor not used by tfib/cef for some PEs prefix
|
CSCec42547
|
LSNT:Incorrect MAC/Encap string in mpls forward table, traffic down
|
CSCeb10018
|
Tracebacks observed on reset card / clear ip bgp
|
CSCec31864
|
RPM-XF sending wrong fields in Interface load info VSI-S message
|
CSCec76217
|
VSICORE: Check null ptr in VprEncIfcCfgGetMore (CSCea64395)
|
CSCec78844
|
VSICORE: Check prev TCB is null before access (CSCdz38917)
|
CSCec39423
|
VSICORE: TCB Leak (CSCea20818) and unicast fixes from CSCdx87287
|
CSCec48318
|
VSICORE: TCB rel err reported incorrectly (CSCdw02481)
|
CSCec29812
|
CEF_scanner triggers high CPU util.
|
CSCea76134
|
e-iBGP load balancing does not work
|
CSCeb61055
|
Incorrect MPLS label built for VRF route
|
CSCea60559
|
lsr mib snmp agent consumes 99% cpu forever
|
CSCea74339
|
SAR-QoS: Data path VC (254/254) is not programmed properly
|
CSCeb80653
|
Generate mxt4600_info file on fatal 4700 SAR errors and reset chip
|
CSCec15993
|
In sar_mxt4400_info file, chip dump overwrites part of the data
|
CSCdx15989
|
Need debug information from sh rpm mxt4400 chip command
|
CSCec61293
|
RPMXF reloads unexpectedly deleting MPLS Switch subinterface
|
CSCeb47748
|
Display vtms info for to-RP link
|
CSCec60947
|
LSNT: AVL memory leak suspected
|
CSCec87123
|
LSNT: carrier transition counter is not working
|
CSCed00573
|
LSNT: No HWIDB_SB_C10K_TT (clear arp caused tracebacks)
|
CSCec53635
|
Channel_id is not updated sometimes after the main switch i/f resets
|
CSCec62846
|
Failure on the data forwarding path was not detected
|
CSCed20528
|
Periodic function keeps on invoking restart PVC after clear int sw1
|
CSCec20821
|
PXF reload is causing a card crash with cell-based MPLS setup
|
CSCeb05796
|
RPMXF: For a range of bandwidth, RPMXF provides lower end of range
|
CSCec85178
|
Reload due to L2 watchdog timer after microcode reload command
|
CSCed28880
|
ATM oam not tracking the gige link status on RPMXF
|
CSCec30428
|
Enhanced VTMS to Handle Possible Hardware Second Timer Update Miss
|
CSCed07480
|
IOS shows SFP MISSING for Hitachi Cable SFP
|
CSCec60594
|
Link can not be up when using 2-port POS with Y-cable redundancy
|
CSCed28404
|
PXF buffer leak occurs for tag switched packets with input policymap
|
CSCdy32261
|
traceback in config switch interface entering an incomplete command
|
CSCdx52061
|
Drop rate counter on output of sh pol int
|
CSCed07712
|
SARCMDTIMEOUT: SAR command timeout, device Reassembly SAR
|
CSCed33563
|
VSI CORE: Mem leak (ec66881) and VSI Core Code Audit fixes
|
CSCed31769
|
Multicast and output logging conflict -- (port CSCec60999)
|
CSCed37755
|
All VCs gets deconfigured in SAR after a microcode reload
|
CSCed15811
|
On data SAR fatal interrupts, SAR CMD TIMEOUTs are seen
|
CSCed17550
|
clearing pxf stat and drop counters cause mem leak
|
CSCec77300
|
RPM-XF returned to rom by bus error at rpm_send_atm_oam_cell
|
CSCed23216
|
LSNT:eiBGP multipath load balancing failed for some IP addresses
|
CSCec76702
|
Per packet load balance is not stable. Packets loss periodically
|
CSCed07231
|
rpmxf ucode error would cause protocol flags if PQ congested
|
CSCed07254
|
rpmxf ucode error would cause toaster stall error
|
CSCec66381
|
RPM-XF: SSI IPC errors during boot up
|
CSCeb84273
|
Need interrupt statistics in 2-port backcard drivers
|
CSCed11101
|
traffic cant recover after POS OIR when vrf configured on POS
|
CSCed35983
|
LSNT: Cannot CC to the RPMXF from PXM
|
CSCed22895
|
rpmc_ipc_vty.c: possible array out of boundary
|
CSCed22568
|
toaster/rpmxf-rp/rpmxf1_rp_cef.c: unmatched raise_interrupt_level()
|
CSCed07063
|
Certain sequence of ftctrace/ttctrace causes IOS crash
|
CSCed23982
|
col4_cicb_extra needs to be populated in right order
|
CSCec53230
|
Command to check consistency between ASIC forwarding & IOS TFIB
|
CSCed23060
|
Incorrect column number passed during a toaster write
|
Resolved Caveats—Release 12.3(2)T2
Table 4 lists the resolved caveats in Cisco IOS Release 12.3(2)T2 as of October 21, 2003.
Table 4 Resolved Caveats in Cisco IOS Release 12.3(2)T2
Caveat Number
|
Description
|
CSCea27838
|
SLT:SYS-3-CPUHOG trace back logged, card hang for a while.
|
CSCeb05118
|
LSNT:RPM-XF crash when delete sw1.1 mpls interface
|
CSCea60343
|
LSNT: connection goes into mismatch
|
CSCdw45040
|
RPM-XF comes up with partial configuration
|
CSCdw76205
|
Error messages when deleting the sw conn under PVC.
|
CSCdw86377
|
Attempting to conf a partition with more lcns than MAX causes TrBack
|
CSCdw86381
|
cnfpnportcac causes traceback if bw used is greater than min bw req
|
CSCdx06018
|
TMC: Multiple VBR flows hash to same toaster Q. Cause taildrops.
|
CSCdx92871
|
iBGP load balancing does not work when two ces are in different vpns
|
CSCdy05346
|
Missing param-groups in Sw Get Cnfg Rsp VSI slave message
|
CSCdy17457
|
sh int shows wrong packet number after shut/no shut the interface
|
CSCdy26882
|
Interface counters show incorrect values after backcard OIR
|
CSCdy42274
|
PXF doesn't recover after a reload at high traffic rates
|
CSCdy73751
|
Certain HW error interrupts may cause the Tx GigE traffic to stop
|
CSCdz23621
|
Z-RED: Standby RPM-XF vsi master endpoint id is not cleared on PXM
|
CSCdz86609
|
Packet drop was observed at switch interface1 when traffic flowing through
|
CSCea15938
|
GTS shapes too aggressively for POS/GigE interfaces
|
Compatibility Notes
RPM-XF Boot File and Firmware File Names and Sizes
The following table displays the RPM-XF boot and firmware file names and sizes for this release.
Table 5 RPM Boot and Firmware File Names and Sizes
| |
File Name
|
File Size (in bytes)
|
Boot File
|
rpmxf-boot-mz.123-2.T5
|
3199320
|
Firmware File
|
rpmxf-p12-mz.123-2.T5
|
8858224
|
RPM-XF Compatibility Matrix
Table 6 RPM -XF Compatible Software Versions
MGX SW version
|
3.0.10
|
4.0.10
|
4.0.12
|
4.0.15
|
5.0.00
|
IOS Version
|
12.2.15T
|
12.2(15)T5
|
12.3(2)T2
|
12.3(2)T5
|
12.3(2)T5
|
CWM
|
11.0.10
|
12.0.00.1
|
12.0.00.2
|
12.0.00.2
|
15.0.00
|
MGX RPM-XF Hardware
Table 7 shows the front card and back card compatibility for the RPM-XF hardware supported in this release. The table lists the card model/ name, part numbers, the minimum version and the minimum revisions of each card supported. Note that there may be more than one 800 level part numbers for the same front cards. The minimum version is identified by the last 2 digits of the 800 level numbers.
Table 7 Hardware Compatibility Matrix
Front Cards
|
Part Number/
Min. Version
|
Rev.
|
Back Cards
|
Part Number/
Min. Version
|
Rev.
|
MGX-RPM-XF-512
|
800-09307-03
|
A0
|
MGX-XF-UI
MGX-1GE
MGX-2GE
MGX-1OC12POS-IR
MGX-2OC12POS-IR
|
800-09492-01
800-18420-03
800-21300-04
800-08359-05
800-20831-04
|
A0
A0
A0
A0
A0
|
Table 8 SFP Compatibility Matrix for MGX Gigabit Ethernet and POS Back Cards
SFPs
|
Part Number/
Min. Version
|
Rev.
|
GLC-SX-MM
(was MGX-GE-SX)
GLC-LH-SM
(was MGX-GE-LHLX)
GLC-ZX-SM
(was MGX-GE-ZX))
|
30-1301-01
30-1299-01
10-1439-01
|
A0
A0
A0
|
Cisco IOS Release Compatibility Information
All IOS firmware can be downloaded from CCO from the following location:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
Using XModem to Download Flash to RPM-XF Cards
Use the xmodem feature to download the flash to an RPM-XF card. During this process, the card should be connected to a target machine through HyperTerminal with settings of 9600, n, 8, and 1.
Step 1 Put the node in monitor mode by entering the priv command to gain access to the privileged commands as follows:
You now have access to the full set of monitor commands. Warning:
some commands will allow you to destroy your configuration and/or
system images and could render the machine unbootable.
Step 2 The xmodem command becomes available and the general syntax of this command and availability of this can be checked by giving xmodem command without any parameters on the CLI, as follows:
The command line options for xmodem are as follows:
Option
|
Definition
|
-c
|
xmodem performs the download using CRC-16 error checking to validate packets. Default is 8-bit CRC.
|
-y
|
xmodem uses Ymodem-batch protocol for downloading, which uses CRC-16 error checking.
|
Note If you do not find the xmodem commands, then the xmodem feature is not available on this rommom version. In that case, you must return the card to Cisco.
