Table Of Contents
About These Release Notes (IOS Release 12.3(2)T6 for MGX Release 1.3.00)
Features Introduced with MGX 8800 Release 1.2.21
VISM-PR to RPM-PR Connectivity
Configuring the Cell Bus Clock (CBC) Rate
LDP on RPM Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1
Multi-LVC on RPM Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1
Bypass Feature for RPM in Cisco IOS Release 12.2(4)T
Features Not Supported in This Release
Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT
CLI Modifications in the MGX Release 1.2.21
CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards
RPM/B and RPM-PR Front Card Resets on the Back Card Removal
RPM/B and RPM-PR Back Ethernet Card Support
MGX-RPM-128M/B Ethernet Back Card Support
RPM/B and RPM-PR Limitations and Restrictions (MGX Release 1.3.00)
Resolved Caveats—Release 12.3(2)T6 for MGX 1.3.00
Resolved Caveats—Release 12.3(2)T5 for MGX 1.3.00
Open Caveats—Release 12.3(2)T6 for MGX 1.3.00
RPM Boot File and Firmware File Names and Sizes
Special Installation and Upgrade Requirements
Cisco IOS Release Compatibility Information
About the Cisco IOS 12.2(15)T5 Release
About the Cisco IOS 12.2(11)T1 Release
About the Cisco IOS 12.2(8)T4 Release
About the Cisco IOS 12.2(8)T1 Release
About the Cisco IOS 12.2(4)T3 Release
About the Cisco IOS 12.2(4)T1 Release
About the Cisco IOS 12.2(4)T Release
About the Cisco IOS 12.2(2)T2 and 12.2(2)T3 Release
About the Cisco IOS 12.1(5.3)T_XT Release
Problems Fixed with Cisco IOS 12.1(5.3)T_XT
Upgrading from an MGX-RPM-128M/B Card to an RPM-PR Card
Upgrade Procedures for RPM Cards in MGX Release 1 (PXM1) Switches
Upgrading RPM Runtime Software
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
Upgrading RPM Boot Software and Runtime Software for 1:N Redundancy
Using XModem to Download Flash to RPM Cards
About These Release Notes (MGX 5.0.00)
Features Introduced with MGX 8800 Release 4.0.10
RPM Image Directory Change From E:RPM to C:/FW
Using the switchredcd Command with RPM-PR Cards to Switch from Active to Standby Card
VISM-PR to RPM-PR Connectivity
Configuring the Cell Bus Clock (CBC) Rate
LDP on RPM-PR in MGX 8850 and MGX 8950
Multi-LVC on RPM in MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T1
Bypass Feature for RPM in Cisco IOS Release 12.2(4)T
Features Not Supported in This Release
CLI Modifications in MGX Release 5.0.00
CWM Recognition of RPM-PR Back Card
RPM Front Card Resets on the Back Card Removal
RPM-PR Back Ethernet Card Support
RPM-PR Limitations and Restrictions (PXM45 and PXM1E)
Resolved Caveats—Release 12.3(2)T6 for MGX 5.0.00
Resolved Caveats—Release 12.3(2)T5 for MGX 5.0.00
Open Caveats—Release 12.3(2)T6 for MGX 5.0.00
RPM Boot File and Firmware File Names and Sizes
Special Installation and Upgrade Requirements
Cisco IOS Release Compatibility Information
About the Cisco IOS 12.2(11)T1 Release
About the Cisco IOS 12.2(8)T4 Release
About the Cisco IOS 12.2(8)T1 Release
About the Cisco IOS 12.2(4)T3 Release
About the Cisco IOS 12.2(4)T1 Release
About the Cisco IOS 12.2(4)T Release
Upgrade Procedures for RPM-PR Cards in MGX 8000 Release 2.1 and Release 3 (PXM45 and PXM1E) Switches
Upgrading RPM Runtime Software
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
Upgrade Procedure for RPM-PR cards in MGX8000 Release 4 (PXM45 and PXM1E) Switches
Using XModem to Download Flash to RPM Cards
Obtaining Technical Assistance
Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T6 for MGX Releases 1.3.00 and 5.0.00
These release notes are part OL-6180-01 Rev. B0, August 18, 2004
Contents
About These Release Notes (IOS Release 12.3(2)T6 for MGX Release 1.3.00)
Note that for MGX Release 1.3.00, the user documentation (command reference, overview, and installation and configuration guides) were not updated. Use the Release 1.1.3 and 1.2.10 documents in addition to this release note.
Product documentation for MGX 8850 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/12/index.htmProduct documentation for MGX 8250 is available at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/12/index.htm
Product documentation for MGX 8230 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/12/index.htmProduct documentation for VISM 3.0(0) is available at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/Product documentation for RPM-PR 2.1 and these release notes are available at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/12/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/12/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/12/rpm/index.htmIf you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
New Features
No new features are introduced with this release.
Features Introduced with MGX 8800 Release 1.2.21
RPM in MGX 8800 Release 1.2.21 supports all new and existing features introduced in the Release 1.2.x baseline. There were four new features introduced for RPM implementations using IOS Release 12.2(15)T5:
•
MPLS CoS Transparency
This feature allows the service provider to set the MPLS experimental field instead of overwriting the value in the customer's IP precedence field. The IP header remains available for the customer's use; the IP packet's CoS is not changed as the packet travels through the multiprotocol label switching (MPLS) network.
Configuration information can be found at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/ftdtmode.htm
•
The MQC acronym refers to the Modular Quality of Service (QoS) Command-Line Interface (CLI). RPM in MGX 8800 Release 1.2.21 supports using the MQC to configure the Compressed Real-Time Protocol (CRTP) header.
Below are the CLI commands introduced to support this feature:
–
–
–
–
–
Configuration information can be found at http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t13/fthdrcmp.htm
•
Configuration information can be found at
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px1e/rel4/scg/rpm.htm•
The frame-based Multicast VPN (MVPN) feature enables the RPM in MGX 8800 Release 1.2.21 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
Previously Released Features
Automatic Cell Bus Clocking
To implement automatic cell bus clocking, a new -autoClkMode option has been added to the xcnfcbclk command. The default is disabled for backward compatibility. When the feature is enabled by entering the xcnfcbclk -autoClkMode enable command, the PXM scans the whole shelf to see whether there are any two RPMs residing on the same cell bus and changes that cell bus to be running at 42MHz clock rate. The clock rate for the rest of the cell buses are not changed. The active PXM updates the disk DB and sends the update to the standby PXM.
When the feature is enabled, the user will not be able to configure the cell bus clock rate manually for any of the cell buses. When disabled with xcnfcbclk -autoClkMode disable command, the PXM will not change the clock rate for any of the cell bus, but will still update the disk DB and send the update to the standby PXM.
Note
Note
Note
The output of dspcbclk command changes to reflect this new feature. A new column is added to show whether the feature is enabled or disabled on the cell buses.When the feature is enabled and an RPM card is inserted, the PXM checks whether the card that resides next to it on the same cell bus is also an RPM card. If both cards are RPM cards, and neither of them is in failed, reserved, unknown, self-test-fail, or no-card state, the cell bus clock rate is automatically set to 42MHz.
Conversely, when the feature is enabled, and an RPM card with a cell bus clock rate of 42MHz is removed or fails, the PXM sets the cell bus to 21MHz, as shown in the following example.
mgx574.1.7.PXM.a > dspcbclkCellBus Rate (MHz) Slot AutoClkMode--------------------------------------------------CB1 21 1, 2 disableCB2 21 3, 4 disableCB3 21 5, 6 disableCB4 21 17 - 22 disableCB5 21 9, 10 disableCB6 21 11, 12 disableCB7 21 13, 14 disableCB8 21 25 - 30 disablemgx574.1.7.PXM.a > cnfcbclk 1 42WARNING: Certain Service Modules will not operate at the clock rate you specified.Please check the Service Modules in the slots where the Cell Bus clock rate iseffected by this command.mgx574.1.7.PXM.a > cnfcbclk 5 42WARNING: Certain Service Modules will not operate at the clock rate you specified.Please check the Service Modules in the slots where the Cell Bus clock rate iseffected by this command.mgx574.1.7.PXM.a > dspcbclkCellBus Rate (MHz) Slot AutoClkMode--------------------------------------------------CB1 42 1, 2 disableCB2 21 3, 4 disableCB3 21 5, 6 disableCB4 21 17 - 22 disableCB5 42 9, 10 disableCB6 21 11, 12 disableCB7 21 13, 14 disableCB8 21 25 - 30 disablemgx574.1.7.PXM.a > xcnfcbclkNot enough arguments (?)xcnfcbclk "-cb <cellBus> -rate <clockRate> -autoClkMode <autoClkEnable>"-cb <cellBus>, where cellBus is a string CB1..CB8-rate <clockRate>, where clockRate is 21 or 42 (MHz)-autoClkMode <autoClkEnable>, where autoClkEnable is enable or disablemgx574.1.7.PXM.a > xcnfcbclk -autoClkMode enablemgx574.1.7.PXM.a > dspcbclkCellBus Rate (MHz) Slot AutoClkMode--------------------------------------------------CB1 42 1, 2 enableCB2 21 3, 4 enableCB3 21 5, 6 enableCB4 21 17 - 22 enableCB5 21 9, 10 enableCB6 42 11, 12 enableCB7 21 13, 14 enableCB8 21 25 - 30 enableVISM-PR to RPM-PR Connectivity
VISM Release 3.0 introduced the new VISM-PR front cards for Cisco MGX Release 1.2.21 and Cisco IOS Release 12.2(15)T. The new VISM-PR-8E1 and VISM-PR-8T1 cards work in the MGX 8230, MGX 8250, and MGX 8850 PXM1-based switches, in combination with the PXM1 Processor Module card. The VISM-PR card supports 144 channels when used with the G.723.1 codec, whereas the current VISM card supports 64 channels with the G.723.1 codec.
Setting connections between a VISM-PR card and a RPM-PR card in your MGX 8230, MGX 8250, or MGX 8850 PXM1-based switch chassis requires that you use the new VBR (NRT)3 connection type.
For more information, refer to the Cisco VISM Installation and Configuration Guide.
Configuring the Cell Bus Clock (CBC) Rate
As of Cisco MGX Release 1.2.10 and Cisco IOS Release 12.2(8)T4), when two RPM-PR cards are on the same cell bus, that is, they occupy adjacent slots (for example, slots 1 and 2 or slots 3 and 4), the cell bus clock (CBC) rate should be manually set to 42MHz. Correspondingly, if there is only one RPM on the cell bus, the clock should be at the default value of 21 MHz.
If, for any reason, one of the adjacent RPM-PRs goes to Failed or Empty state, the CBC for that cell bus must be reconfigured for the Traffic Shaping to work correctly on the active RPM. On MGX 1 switches with Release 1.2.10, the 42MHz to 21 MHz change must be explicitly performed using the cnfcbclk command. Use the dspcbclk command from the PXM1 to confirm the cell bus clock rate.
The following screen output displays the use of the cnfcbclk and dspcbclk commands used to change the clock on cell bus 1 (for slots 1 and 2) from 21 MHz to 42 MHz and confirm the change.
PXM> dspcbclkCellBus Rate (MHz) Slot-------------------------------CB1 21 1, 2CB2 21 3, 4CB3 21 5, 6CB4 21 17 - 22CB5 21 9, 10CB6 21 11, 12CB7 21 13, 14CB8 21 25 - 30PXM> cnfcbclk CB1 42WARNING: Certain Service Modules will not operate at the clock rate you specified.Please check the Service Modules in the slots where the Cell Bus clock rate is effected by this commandmgx3.1.7.PXM.a > dspcbclkCellBus Rate (MHz) Slot-------------------------------CB1 42 1, 2CB2 21 3, 4CB3 21 5, 6CB4 21 17 - 22CB5 21 9, 10CB6 21 11, 12CB7 21 13, 14CB8 21 25 - 30RPM makes use of idle cells for Traffic Shaping and Scheduling. If there are two RPMs in adjacent slots on the same cell bus and one of the RPMs is put into a Failed state by the PXM, while that card is actually alive, then the "Failed" RPM must stop sending idle cells to avoid impacting the Traffic Shaping on the adjacent functional RPM. The command that implements the RPM support for this feature is rpm-auto-cbclk-change.
rpm-auto-cbclk-change enables the RPM to stop sending idle cells in the event of being put into a "FAILED" state by the PXM and thus prevent an impact on the Traffic Shaping on an adjacent functional RPM.
no rpm-auto-cbclk-change which disables the feature to stop sending of idle cells if the RPM is put into a FAILED state. This command may be used if Traffic Shaping is not required.
The following screen output displays an example of the rpm-auto-cbclk-change command.
RPM-11#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-11(config)#int sw1RPM-11(config-if)#rpm-auto-cbclk-changeRPM-11(config-if)#endRPM-11#write memBuilding configuration...[OK]RPM-11#show run int sw1Building configuration...Current configuration :142 bytes!interface Switch1no ip addressno atm ilmi-keepaliverpm-auto-cbclk-changeswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:49:04If Traffic Shaping is not a requirement, enter the no rpm-cbclk-change command, either manually or during card configuration. The following screen output displays an example of the no rpm-auto-cbclk-change command.
RPM-11#config terminalEnter configuration commands, one per line. End with CNTL/Z.RPM-11(config)#int sw1RPM-11(config-if)#no rpm-auto-cbclk-changeRPM-11(config-if)#endRPM-11#write memBuilding configuration...[OK]RPM-11#show run int sw1Building configuration...Current configuration :145 bytes!interface Switch1no ip addressno atm ilmi-keepaliveno rpm-auto-cbclk-changeswitch autoSynch offend! rpm_tag_id Apr 04 2002 02:49:57
Note
LDP on RPM Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1
The MPLS label distribution protocol (LDP), as standardized by the Internet Engineering Task Force (IETF) and as enabled by Cisco IOS software, allows the construction of highly scalable and flexible IP Virtual Private Networks (VPNs) that support multiple levels of services.
LDP provides a standard methodology for hop-by-hop or dynamic label distribution in an MPLS network by assigning labels to routes that have been chosen by the underlying Interior Gateway Protocol (IGP) routing protocols. The resulting labeled paths, called label switch paths (LSPs), forward label traffic across an MPLS backbone to particular destinations. These capabilities enable service providers to implement Cisco's MPLS-based IP VPNs and IP+ATM services across multivendor MPLS networks.
From a historical and functional standpoint, LDP is a superset of Cisco's pre-standard Tag Distribution Protocol (TDP), which also supports MPLS forwarding along normally routed paths. For those features that LDP and TDP share in common, the pattern of protocol exchanges between network routing platforms is identical. The differences between LDP and TDP for those features supported by both protocols are largely embedded in their respective implementation details, such as the encoding of protocol messages, for example.
This software release of LDP provides the means for transitioning an existing network from a TDP operating environment to an LDP operating environment. Thus, you can run LDP and TDP simultaneously on any given router platform. The routing protocol that you select can be configured on a per-interface basis for directly-connected neighbors and on a per-session basis for non-directly-connected (targeted) neighbors. In addition, a label switch path (LSP) across an MPLS network can be supported by LDP on some hops and by TDP on other hops.
MPLS LDP offers the following features:
•
•
•
Multi-LVC on RPM Running MGX Release 1.2.02 and Cisco IOS Release 12.2(8)T1
This feature enables support for initiation of multiple label switched paths (LSPs) per destination on the RPM. Different label switched paths are established for different class of services. This feature enables interface level queueing rather than per-vc level on the RPM based on MPLS class of service policy. With Multi-LVC support, customers can deploy IP VPN services with Class of Service SLAs.
Bypass Feature for RPM in Cisco IOS Release 12.2(4)T
Note
RPM cards have a maximum storage of 128 KB for the NVRAM. This size limitation creates a problem for customers with large configurations, who find it impossible to store the complete configuration in the NVRAM, even with compression enabled.
In order to support storage of large configuration files, a new bypass feature is now available in the 12.2(4)T IOS Release. With the bypass feature enabled, the enhanced "write memory" is used to bypass the NVRAM and save the configuration on:
•
Where ## represents the zero-padded slot number in which the RPM card is seated in the MGX chassis.
To enable the bypass feature, issue the command rpmnvbypass from the IOS run time image—not in the IOS boot image.
To disable the bypass feature, enter the command no rpmnvbypass.
To verify that the bypass feature is either enabled or disabled, enter the show running-configuration command. If the bypass feature is enabled, rpmnvbypass is seen on the display. If it is not seen, the feature is not enabled.
Note
Table 1 contains cautions important to the successful usage of the bypass feature.
Example 1 through Example 5 illustrate how the bypass feature is enabled and disabled, and how to validate each of these actions from the configuration display.
Example 1 Running configuration without the bypass feature enabled
rpm_slot02#show running-configBuilding configuration...Current configuration : 470 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.<new_rel>enable password cisco!ip subnet-zero!!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!endExample 2 Enable the bypass feature (rpmnvbypass)
rpm_slot02#rpm_slot02#configure terminalEnter configuration commands, one per line. End with CNTL/Z.rpm_slot02(config)#rpmnvbypassThe "boot config" statement has been (re)added to yourrunning configuration. Do not remove it else risk notusing the nvbypass featurerpm_slot02(config)#endrpm_slot02#Example 3 Running configuration with bypass feature enabled (note rpmnvbypass at end of output)
rpm_slot02#show running-configBuilding configuration...Current configuration : 515 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.<new_rel>boot config c:auto_config_slot02 <==== Line added as per output aboveenable password cisco!ip subnet-zero!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!rpmnvbypassendExample 4 Disable the bypass feature (no rpmnvbypass)
rpm_slot02#configure terminalEnter configuration commands, one per line. End with CNTL/Z.rpm_slot02(config)#no rpmnvbypassrpm_slot02(config)#endrpm_slot02#Example 5 Running configuration after the bypass feature is disabled
rpm_slot02#show running-configBuilding configuration...Current configuration : 503 bytes!version 12.2service timestamps debug uptimeservice timestamps log uptimeno service password-encryption!hostname rpm_slot02!boot system c:rpm-js-mz.<new_rel>boot config c:auto_config_slot02enable password cisco!ip subnet-zero!!!!interface Switch1no ip addressno atm ilmi-keepaliveswitch autoSynch off!ip classlessno ip http serverip pim bidir-enable!!snmp-server community public ROsnmp-server community private RW!!line con 0line aux 0line vty 0 4no login!endrpm_slot02#Features Not Supported in This Release
The following features are not supported on RPM:
•
•
RPM Redundancy Support
RPM 1:N redundancy is used to switch configuration and traffic from one RPM card to another. The main benefits are:
•
•
•
SNMP MIB
SNMP MGX Release 1 MIB are provided with the delivery of this release. The MIB is in standard ASN.1 format and is 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 release notes that contains the MIB release notes.
For changes in this MIB from the previous release, please refer to the MIB release notes.
Note
Notes and Cautions
The following notes and cautions should be reviewed before using this release.
Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT
Use the following procedure when upgrading from your current RPM/IOS runtime image 12.1(5.3)T_XT and MGX version for MGX Release 1.2.02 and 1.2.10:
Step 1
Step 2
a.
b.
c.
For more detail on the MGX upgrade procedures, refer to the Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (PXM1), Software Version 1.2.10.
UPC Connection Parameters
In Release 1.1.40 and higher, the default PCR is 50 cps, and the default for policing is "enabled." These settings are insufficient for running RPM ISIS protocol over the connection, and with such settings, the ISIS protocol will fail. The PCR value needs to be increased, depending upon the number of interfaces configured for ISIS on the RPM.
Depending upon your connection type, you can use the following CLIs to modify the PCR parameter.
•
•
•
•
Booting the RPM-PR
Refer to Chapter 5, "Configuring the MGX RPM" in the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1, (DOC-7812278=) and for complete details on configuring the RPM-PR cards. (See the "Obtaining Documentation" section for information on how to order a printed copy of this manual or locate the manual online.) A summary of the booting and upgrading procedures is presented here for your convenience.
When the RPM-PR is booted, the boot image must be the first file in the bootflash. If the bootflash does not have a valid boot image as a first file, the card may not be able to boot.
You can reboot the RPM-PR from the PXM by entering the command resetcd <card_number> from the switch CLI, where card_number is the slot number of the RPM-PR that is being rebooted.
Note
Also, you can reboot the RPM-PR from the RPM-PR using the RPM-PR console port and entering the reload command.
Each time you turn on power to the RPM-PR, by inserting the RPM-PR into the MGX 8850, it goes through the following boot sequence:
1.
2.
The source of the Cisco IOS image is determined by the configuration register setting. To verify this setting, you can enter either the show version or show bootvar command. (Refer to the "Viewing the Hardware Configuration" section of the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 (DOC-7812278=).
a.
b.
3.
a.
b.
c.
4.
5.
If you want to load from a specific configuration file, you should enter either the boot config bootflash:<config_file> command or the boot config c:<config_file> command.
6.
The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-PR Card." For information on the Cisco IOS instructions, refer to Appendix C, "IOS and Configuration Basics"of the Cisco MGX Route Processor Module Installation and Configuration Guide, Release 2.1 (DOC-7812510=)
RPM-PR Bootflash Precautions
The RPM-PR bootflash is used to store boot image, configuration and "run time" files. The Flash stores and accesses data sequentially, and the RPM-PR boot image must be the first file stored to successfully boot the card. Erasing the boot image or moving it from the first position on the Flash will cause the card to not boot.
The RPM boot image, which comes loaded on the Flash, will work for all RPM IOS images. Therefore, there is no reason to ever delete or move the factory installed boot image.
Caution
In order to avoid this unnecessary failure, requiring card servicing, you should
•
•
•
As long as the boot file remains intact in the first position on the flash, the RPM will successfully boot.
CLI Modifications in the MGX Release 1.2.21
There are no new or modified RPM/B or RPM-PR CLI commands for MGX Release 1.2.21.
Limitations and Restrictions
CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards
CWM does not distinguish between the Ethernet back card versions installed with the MGX-RPM-128M/B or RPM-PR. There is no functionality difference.
RPM/B and RPM-PR Front Card Resets on the Back Card Removal
The RPM front card may reset on an MGX 8250 and MGX8850 switches with PXM1 as controller card when the ethernet back card is removed or inserted.
This reset problem can be easily avoided if "shut" interface is executed before the removal of the back card.
RPM/B and RPM-PR Back Ethernet Card Support
For Ethernet connectivity with the RPM-PR, the model "/B" four-port Ethernet back card is required (order number: MGX-RJ45-4E/B).
MGX-RPM-128M/B Ethernet Back Card Support
The model "/B" four-port Ethernet back card can be used with the MGX-RPM-128M/B module only in combination with IOS 12.2(2)T2 or higher. The model "/B" back card will not work on the MGX-RPM-128M/B with earlier versions of the IOS.
The order number is order number: MGX-RJ45-4E/B.
Older back cards can be used with any version of the IOS.
model "/B" back card
12.2(2)T2
earlier back card models
Min. IOS for MGX-RPM-128M/B on MGX 8250 is 12.0(7)T
RPM/B and RPM-PR Limitations and Restrictions (MGX Release 1.3.00)
The RPM/B and RPM-PR limitations and restrictions that apply to this release are as follows:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Resolved Caveats—Release 12.3(2)T6 for MGX 1.3.00
Table 3 lists the resolved caveats in Cisco IOS Release 12.3(2)T6 for MGX 1.3.00 as of June 4, 2004.
Resolved Caveats—Release 12.3(2)T5 for MGX 1.3.00
Table 3 lists the resolved caveats in Cisco IOS Release 12.3(2)T5 for MGX 1.3.00 as of April 14, 2004.
Open Caveats—Release 12.3(2)T6 for MGX 1.3.00
Table 4 lists the open caveats in Cisco IOS Release 12.3(2)T6 for MGX 1.3.00 as of June 4, 2004.
Table 4 Open Caveats in Cisco IOS Release 12.3(2)T6 for MGX 1.3.00
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)
CSCed41381
LSNT: Input drops on framed PVC i/f cause ldp session flap
Symptom:
Input cell drops on the ingress frame PVC configured on switch interface which in turn causes LDP/TDP/OSPF flaps sometimes.
Conditions:
This might happen only if there is a lot of core traffic coming on ingress PVC (bigger bandwidth) and gets routed onto small bandwidth egress PVC.
Workaround:
None.
CSCed85540
Symptom:
LSC crashes in LSNT
Condition:
This problem was seen during normal operation in LSNT the RPM-PR cards were running 12.2 15(T)4c
Workaround:
None
CSCed74835
Symptom:
When copy big files from Cisco MGX8850 Route Processor Module (RPM-PR) to MGX8850 hard drive, it silently failed.
Conditions:
This happens only if copy of size greater than 8 MB.
Workaround:
None.
CSCec68542
LSNT:SAR not reassemble properly for big packets cause protocol down
Symptom:
SAR does not reassemble properly for big packets cause protocol down Conditions:
RPM-PR works as LER with dual LSCs
disable/enable multi-vc on RPM-PR
1000 spvcs with vrf enabled
500 eBGP sessions
80Mbps input traffic and 6Mbps output ip traffic
Workaround:
Reload card
CSCdv24154
Notify new tag mtu value after the interface mtu change.
Symptom:
Setting mtu size in xtagatm interface in LSC defaults to 4470
Condition:
Setting mtu size in xtagatm interface in LSC defaults to 4470
Workaround:
None.
CSCea62571
%UTIL-3-TREE: Data structure error with trace back logged on LSC
Symptom:
%UTIL-3-TREE: Data structure error--attempt to remove an unthreaded node from a tree with trace back logged on LSC
Conditions:
LSC hot redundancy reload LSC
Workaround:
Unknown
CSCea85160
snmpwalk on ifDescr should not respond to aal5 mib variable
Symptom:
snmpwalk on ifDescr responds to aal5 mib variable.
Conditions:
This symptom is observed when we query for the ifDescr
Workaround:
None
CSCea85395
BGP suppressed prefixes not reinstated after condition removed
Symptoms:
Previously suppressed prefixes are not automatically installed in the VRF.
Condition:
After VRF reaches max route limit subsequent prefixes are being suppressed and not installed in the VRF table. After the suppress condition is cleared routes should be put into VRF without any manual intervention.
Workaround:
Clear ip bgp
CSCec02155
All VSI sessions down, xtag to down/down state
Symptom:
All VSI sessions go to down and xtag interfaces to down/down state on LSC
Conditions:
RPM-PR work as LSC
Workaround:
Unknown
CSCec26512
After switchredcd 22 LVCs went to Bwait state
Symptom:
After switchover, 22 LVCs went to Bwait state.
Condition:
After switchover, 22 LVCs went to Bwait state.
Workaround:
None.
CSCec68542
Symptom:
In Large scale network, under stressful condition, Segmentation and reassembly (SAR) may not reassemble properly for large packets, causing the protocol to fail.
Condition:
This symptom is observed on a Cisco MGX Route Processor Module PRemium (RPM-PR running 12.2(15)T4B) that functions as a Label Edge Router (LER) that is configured with two label switch controllers (LSCs) under the following conditions:
1) With a script running disable and reenable the multi-virtual-circuit (Multi-VC) mode on the RPM-PR.
2) There are 1000 soft permanent virtual circuits (SPVCs) that have Virtual Private Network (VPN) routing/forwarding (VRF) enabled.
3) There are 500 external Border Gateway Protocol (eBGP) sessions.
4) There is 80-Mbps input traffic and 6-Mbps output IP traffic.
Workaround:
None.
CSCed94598
Symptom:
Route Processor Module (RPM) is overshaping the traffic by 0.3 to 0.5% above SCR.
Condition:
Route Processor Module having version 12.2(15)T4 running, and terminating on a ATM User Service Module (AUSM).
Workaround:
Reduce the SCR value in the RPM by 0.5% to compensate for the shaping error.
CSCee54524
Symptom:
During SCR provisioning (changing the bandwidth) on the ePVCs, the RPM-PR (Route Processor Module) PE may reload.
Condition:
Script based testing to change the bandwidth resulted in the router reload.
Workaround:
Standby card will takeover and resume the operations.
Guest
