Table Of Contents
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for MGX Release 1.2.10 and MGX Release 3
Contents
About These Release Notes (MGX 1.2.10)
New Features
VISM-PR to RPM-PR Connectivity
Configuring the Cell Bus Clock (CBC) Rate
Previously Released Features
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
RPM Redundancy Support
SNMP MIB
Notes and Cautions
Special Upgrade Procedure for Cisco IOS Release 12.1(5.3)T_XT
UPC Connection Parameters
Booting the RPM-PR
RPM-PR Bootflash Precautions
CLI Modifications in 1.2.10 Baseline
Limitations and Restrictions
CWM Recognition of RPM-PR and MGX-RPM-128M/B Back Cards
RPM/B and RPM-PR Front Card Resets on the Back Card Removal
RPM/B and RPM-PR Back Ethernet Card Support
MGX-RPM-128M/B Ethernet Back Card Support
RPM/B and RPM-PR Limitations and Restrictions (MGX Release 1.2.10)
Problems Fixed in This Release
Known RPM/B and RPM-PR Anomalies
Compatibility Notes
RPM Boot File and Firmware File Names and Sizes
RPM Compatibility Matrix
MGX RPM/B and RPM-PR Hardware
Special Installation and Upgrade Requirements
Cisco IOS Release Compatibility Information
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 Boot Software
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
Historical Information From 1.2.x Baseline
Problems Fixed in Release 1.2.02
Problems Fixed in Release 1.2.01
Problems Fixed in Release 1.2.00
About These Release Notes (MGX 3.0)
New Features
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
Previously Released Features
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
Multiprotocol Label Switching (MPLS) over ATM using VC Merge in MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T
Bypass Feature for RPM in Cisco IOS Release 12.2(4)T
Features Not Supported in This Release
RPM Redundancy Support
SNMP MIB
Notes and Cautions
UPC Connection Parameters
Booting the RPM-PR
RPM-PR Bootflash Precautions
CLI Modifications in MGX Release 3.0
Limitations and Restrictions
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)
Problems Fixed in This Release
Known RPM-PR Anomalies
Compatibility Notes
RPM Boot File and Firmware File Names and Sizes
RPM Compatibility Matrix
MGX RPM-PR Hardware
Special Installation and Upgrade Requirements
Cisco IOS Release Compatibility Information
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 Boot Software
Upgrading RPM Runtime Software
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
Upgrading RPM-PR Boot Software and Runtime Software for 1:N Redundancy
Using XModem to Download Flash to RPM Cards
Historical Information From 2.1.7x Baseline
Known Anomalies in Release 2.1.79
Anomalies Resolved in Release 2.1.79
Anomaly Status Changes in 2.1.79
Known Anomalies in Release 2.1.76
Anomalies Resolved in Release 2.1.76
Anomaly Status Changes in Release 2.1.76
Known Anomalies for Release 2.1.75
Anomalies Resolved in Release 2.1.75
Anomaly Status Changes in Release 2.1.75
Known Anomalies in Release 2.1.70
Anomalies Resolved in Release 2.1.70
Anomaly Status Changes in Release 2.1.70
Known RPM-PR/MPLS Anomalies
Related Documentation
Cisco WAN Manager Release 11
Cisco MGX 8850 (PXM45) Multiservice Switch Release 3
Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3
Cisco MGX 8950 Multiservice Switch Release 3
Service Expansion Shelf PNNI Controller Release 3
Cisco MGX 8830 Multiservice Switch Release 3
Cisco WAN Switching Software Release 9.3.40
MGX 8850 (PXM1) Multiservice Switch Release 1.2.10
MGX 8250 Edge Concentrator Release 1.2.10
MGX 8230 Edge Concentrator Release 1.2.10
Obtaining Documentation
World Wide Web
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Web Site
Cisco TAC Escalation Center
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for MGX Release 1.2.10 and MGX Release 3
Contents
About These Release Notes (MGX 1.2.10)
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 1.2.10, 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/1_1_31/index.htm
Product documentation for MGX 8250 is available at the following URL: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/1_1_31/index.htm
Product documentation for MGX 8230 is available at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/1_1_31/index.htm
Product 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 1.1 and 1.2.10 is available at the following URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8250/rpm/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8230/rpm/index.htm
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
New Features
RPM in MGX 8000 Release 1.2.10 supports all new and existing features introduced in the Release 1.2.x baseline. The following is a new and recent features for RPM implementations using IOS Release 12.2(8)T4.
VISM-PR to RPM-PR Connectivity
VISM Release 3.0 introduces the new VISM-PR front cards. The new VISM-PR-8E1 and VISM-PR-8T1 cards work in the MGX 8230, MGX 8250, and MGX 8850 Release 1 switches, in combination with the PXM1 Processor Module card. The VISM-PR card support 144 channels when used with the G.723.1 codec, whereas the current VISM card support supports 64 channels with the G.723.1 codec.
Setting connections between a VISM-PR card and a RPM-PR card in your MGX8000 Series 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
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.
-------------------------------
WARNING: Certain Service Modules will not operate at the clock rate you specified.
Please check the Service Modules in the slots where the Cell Bus clock rate is
effected by this command
mgx3.1.7.PXM.a > dspcbclk
-------------------------------
RPM 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.
Enter configuration commands, one per line. End with CNTL/Z.
RPM-11(config-if)#rpm-auto-cbclk-change
Building configuration...
Building configuration...
Current configuration :142 bytes
! rpm_tag_id Apr 04 2002 02:49:04
If Traffic Shaping is not a requirement, enter the no rpm-cbclk-change command, either manually or during card configuration. The following screen output displays an example of the no rpm-auto-cbclk-change command.
Enter configuration commands, one per line. End with CNTL/Z.
RPM-11(config-if)#no rpm-auto-cbclk-change
Building configuration...
Building configuration...
Current configuration :145 bytes
! rpm_tag_id Apr 04 2002 02:49:57
Note 
By default on the RPM this feature is enabled.
Previously Released Features
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:
•IETF Standards-based label distribution protocol
•Multi-vendor interoperability
•TDP to LDP migration and interoperability
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 Information about the bypass feature and the IOS commands used to support it was not available at the time of the printing of the RPM documents; therefore, it is included in the these release notes.
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:
•For MGX Release 1, the file auto_config_slot## located in the C:/RPM directory on the PXM1.
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 Because the bypass feature bypasses NVRAM, it is not necessary to compress the configuration file using the command service compress-config.
Table 1 contains cautions important to the successful usage of the bypass feature.
Table 1 Boot Cautions
Caution
|
Why is This Important?
|
When using the bypass feature, you can load the run time IOS image from the PXM hard-drive or from the boot flash.
|
In the case of an RPM module, the IOS image can be loaded in 3 ways:
1. From the PXM hard-drive.
2. From the boot flash.
3. From the network (for example, via TFTP) from the RPM backcard (Ethernet or Fast Ethernet).
When the bypass feature is enabled, the boot config statement:
is automatically generated. The NVRAM configuration is cleared upon entering a write memory command. In order to load from the network, the RPM must have an IP address for its backcard. This information is part of the NVRAM configuration, which was just cleared by enabling the bypass feature. Hence, it is not possible to load the IOS image from the network upon a reload of the RPM after the rpmnvbypass and write memory commands have been executed.
|
Do not execute the command no boot config.
Doing so may prevent the bypass feature from working properly.
|
When the bypass feature is enabled, the boot config statement:
is automatically generated, and the NVRAM configuration is cleared.
Any writes are subsequently directed to the boot config file. This is essential, as a write memory command expects the boot config statement to be present.
If the boot config statement is not present, entering the write memory command would write the configuration into the NVRAM, which is not desirable when the objective is to save a complete configuration when the configuration is large and requires more space.
|
If the command write memory is issued with the bypass feature enabled, and is consequently followed by an RPM card reset, previous versions of the boot image will trigger the RPM card to go into boot mode (unable to load run-time IOS).
|
For safety purposes, the location of the system image is stored in a special area (called the ROMMON area) in the NVRAM. The ROMMON is always intact.
The 12.2(4)T boot image accesses and reads ROMMON in order to load the IOS image. Boot images prior to 12.2(4)T do not read the ROMMON area.
Generally, the IOS boot and run-time images are of the same versions. However, if you change the boot image to one prior to 12.2(4)T, on a reload, the boot image would see that the NVRAM configuration is empty, which is normal when the bypass feature is enabled. But because boot images prior to 12.2(4)T cannot access the ROMMON area, it cannot read the location of the IOS image. Unable to see the IOS image, it instead loads itself.
|
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-config
Building configuration...
Current configuration : 470 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
snmp-server community public RO
snmp-server community private RW
Example 2 Enable the bypass feature (rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#rpmnvbypass
The "boot config" statement has been (re)added to your
running configuration. Do not remove it else risk not
using the nvbypass feature
Example 3 Running configuration with bypass feature enabled (note rpmnvbypass at end of output)
rpm_slot02#show running-config
Building configuration...
Current configuration : 515 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
boot config c:auto_config_slot02 <==== Line added as per output above
snmp-server community public RO
snmp-server community private RW
Example 4 Disable the bypass feature (no rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#no rpmnvbypass
Example 5 Running configuration after the bypass feature is disabled
rpm_slot02#show running-config
Building configuration...
Current configuration : 503 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
boot config c:auto_config_slot02
snmp-server community public RO
snmp-server community private RW
Features Not Supported in This Release
The following features are not supported on RPM:
•MPLS inter AS
•MPLS TE
RPM Redundancy Support
RPM 1:N redundancy is used to switch configuration and traffic from one RPM card to another. The main benefits are:
•Route processing continues even if an RPM fails and there is no operator or direct access to swap the failed card or fix the problem.
•An RPM 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.
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 The old_mib_Format is discontinued as of this release.
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 RPM IOS boot and runtime images should be upgraded before MGX images are upgraded. Please follow the RPM/IOS image upgrade procedure as specified in the "Upgrade Procedures for RPM Cards in MGX Release 1 (PXM-1) Switches" as described in later sections of this Release Notes Document.
Step 2 MGX software should be upgraded next as illustrated in the following steps.
a. install <image-name>
b. newrev <image-name>
c. commit <image-name>
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.
•cnfupccbr
•cnfupcvbr
•cnfupcabr
•cnfupcubr
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 Omitting the card number resets the entire system.
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. The RPM-PR runs diagnostics on the CPU, memory, and interfaces.
2. The system boot software, which is the boot image, executes and searches for a valid Cisco IOS image, which is the RPM-PR runtime software.
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. If the configuration register is set to the factory-default setting of 0x01, RPM-PR will come up and stay in boot mode.
b. If the configuration register is 0x2, the RPM-PR will look for the runtime image either in bootflash or on the PXM1 C:/RPM drive.
3. The search for runtime image is determined by which boot system command is entered.
a. Entering the boot system c:<runtime_image_name> command will result in a search for a runtime image in the C:/RPM directory on the PXM1 hard disk.
b. Entering the boot system bootflash:<runtime_image_name> will result in a search for a run time image in the bootflash.
c. If the boot system bootflash:<runtime_image_name> is not entered, it will result in loading of the first available IOS image from C:/RPM, if one such image is present.
4. If the runtime software is not found after three attempts, the RPM-PR reverts to the boot mode.
5. If a valid Cisco IOS image is found, then the RPM-PR searches for a valid configuration, which can reside in NVRAM or as a configuration file either on the PXM hard disk C:/RPM drive or in bootflash.
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. For normal RPM-PR operation, there must be a valid Cisco IOS image on the PXM-1 C:/RPM drive or in bootflash, and a configuration in NVRAM or configuration file in bootflash or on the PXM disk.
The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-PR Card." 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 1.1 (DOC-7812278=)
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 Erasing or moving the boot image can cause RPM-PR boot failure. When this happens, the RPM card must be returned to Cisco and reflashed.
In order to avoid this unnecessary failure, requiring card servicing, you should
•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 will successfully boot.
CLI Modifications in 1.2.10 Baseline
There are no new or modified RPM/B or RPM-PR CLI commands for MGX Release 1.2.10.
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.
4-port Ethernet back card used with MGX-RPM-128M/B
|
Required 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.2.10)
The RPM/B and RPM-PR limitations and restrictions that apply to this release are as follows:
•The MGX-RPM-128M/B is a NPE-150 based router card capable of sustaining 150,000 pps. The RPM-PR is an NPE-400 based router capable of sustaining over 350,000 pps. The RPM-PR will only operate with IOS 12.1(5.3)T_XT or later. For the following section "RPM" refers to both the MGX-RPM-128M/B and the RPM-PR, (unless specifically called out). Some software versions and limitations are not applicable to the RPM-PR because it does not support IOS versions before 12.1(5.3)T_XT.
•With MGX-RPM-128M/B versions earlier than 12.0.7T1, some limitations in Inter-Process Communication when the MGX-RPM-128M/B is at high loads can cause the PXM to declare that the MGX-RPM-128M/B has Failed. To avoid this with MGX-RPM-128M/B, software releases earlier than 12.0.7T1, throughput is limited to 62,000 pps, and it is recommended that MPLS configurations are limited to 100 interfaces. With RPM software releases from 12.0.7T1, those limitations are removed. In a separate limitation, the number of directly connected OSPF networks supported by an RPM is currently limited to 27. This means that any or all of the subinterfaces supported by the RPM can run OSPF, but the number of distinct OSPF networks supported is limited to 27. (A work around is available and is discussed below.) The limit of 27 arises because of the overheads of supporting separate link-state databases for separate networks.
•In an application where the RPM is a Provider Edge Router in an MPLS Virtual Private Network service, a much better solution in any case is to use a distance-vector routing protocol between the customer routers and the RPM. A distance-vector routing protocol provides exactly the information required for this application: reachability information, and not link-state information. The distance-vector routing protocols supported by the RPM are BGP, RIP v1 and RIP v2, as well as static routing. With RPM software releases from 12.0.7T1, distance-vector routing protocols can be used with as many different networks as subinterfaces.
•Note that if the RPM is acting as a Provider Edge Router in an MPLS Virtual Private Network service, and even if OSPF is running in a customer network, it is not necessary to run OSPF between the customer router and the RPM. If the customer edge devices run Cisco IOS, they can redistribute OSPF routing information into RIP using the IOS commands, redistribute RIP in the OSPF configuration, and redistribute OSPF in the RIP configuration. Similar configurations are possible for BGP. (For more information on re advertisement, see the "Configuring IP Routing Protocol-Independent Features" chapter in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1). Redistribution is not unique to Cisco CPE, and other vendors' equipment also supports redistribution.
•Whenever there are 2 RPM cards on adjacent slots, driven by the same cell bus clock, the clock rate should be set to 42 MHz for traffic shaping, using the command cnfcbclk. This configuration will be lost if the node rebuilds due to resetsys or a power cycle. The user will have to manually re-configure the cell bus clock rate after the rebuild, using the cnfcbclk command.
•On an MGX 8850 node, when the chassis is loaded with 6 or more RPM-PR cards, and if every card is configured to download the IOS runtime image from the PXM-1 hard disk, occasionally, upon entering a resetsys command or after a power cycle, some of the RPM-PR cards may go into the failed state. To reset the failed RPM-PR cards, enter the resetcd <slot #> command for each failed card.
•A single RPM-PR can only function as either an Edge LSR or as an LSC, but not as both.
•Total of (OC12 minus T3) Mbps intrashelf traffic for Cell bus based modules are supported.
•To configure redundancy, the primary and secondary RPM-PR cards need to be in the Active state and the secondary card should not have any configuration.
•Removing a back card does not cause RPM-PR switchover.
•After establishing redundancy between two RPM-PR cards with the addred command, you must enter the copy run start command on the primary RPM-PR card to save the configuration change.
•If a secondary RPM-PR card is redundant to primary cards x and y, you cannot delete redundancy for only card x.
•If you need to enter the softswitch and switchcc commands, Cisco Systems recommends that you wait at least 5 seconds after issuing the softswitch command, and then enter the switchcc command.
•IOS software images on primary and secondary RPM-PR cards do not have to be compatible, but the IOS software on a secondary card should be at the same level as the primary card or higher.
•Whenever the RPM-PR configuration is changed and a user wants to store that configuration, the user must enter the copy run start command on the RPM-PR. If this is not done, the changed configuration will be lost on RPM-PR card reboot or RPM-PR switchover in case of redundancy.
•Even though RPM-PR can have 1999 sub interfaces, the usage of sub interfaces should be planned in such a way that it does not cross a safe limit of 1985. This is because each sub interface takes one IDB (interface descriptor block) and the number of IDBs available in the card is 2000. Further, a user might need some IDBs for the RPM-PR back card and its ports.
•For RPM/B and RPM-PR PVC dax connections, the slave end must be deleted before the master endpoint.
Problems Fixed in This Release
The following is the list of problems fixed in the RPM service module firmware and software for this release. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdw64591
|
Symptoms:
A Cisco Route Processor Module (RPM) may pause indefinitely after the clear ip ospf is executed.
Conditions:
A Cisco Route Processor Module (RPM) may pause indefinitely after the clear ip ospf process EXEC command is issued and display the following message on the console:
%ATMPA-3-BADVCD: Switch1 bad vcd 1460 packet - 05B49847 000900FE
002021FE45000058 00010000 FE00C3A0
Workaround:
Reset the RPM.
|
CSCdx01120
|
Symptoms:
Several rpm-atm hybrid connections provisioned via CWM GUI interface are in "mismatch" state after RPM reload.
Conditions:
1. Provision a rpm-atm hybrid vbr3/abr-1/ubr-1 thru CWM CM GUI
2. "MODIFY" the hybrid connections thru CMGUI
3. Wait for 2 to 3 minutes, they will go into "mismatch" state.
Workaround:
Reapply the same parameters again.
|
CSCdx11351
|
Symptom:
When a permanent virtual circuit (PVC) is deleted from the Cisco WAN Manager (CWM), the Route Processor Module (RPM) resets and produces a flash file.
Conditions:
When a permanent virtual circuit (PVC) is deleted from the Cisco WAN Manager (CWM). This behavior occurs only when a service policy is configured on the connection.
Workaround:
Add the service policy to the PVC after a connection is added. Manually remove the service policy for a connection before deleting the connection and PVC from the CWM.
|
CSCdx20802
|
Symptoms:
Memory fragmentation may cause 2 MB of memory allocation to fail.
Conditions:
This symptom affects edge routers that are configured for multi-virtual circuit (Multi-VC) and that have Label-Controlled ATM (LC-ATM) interfaces connected toward a Multiprotocol Label Switching (MPLS) core. Incremental memory leaks occur after the LC-ATM interface is toggled by issuing the shutdown interface configuration command followed by the no shutdown interface configuration command or after Cisco Express Forwarding (CEF) is enabled and later disabled on the router by issuing the ip cef global configuration command followed by the no ip cef global configuration command. Incremental memory leaks may also be seen when route flaps occur. If the incremental memory leaks continue, memory fragmentation may occur and traffic may stop passing through the LC-ATM interface.
Workaround:
None
|
CSCdx20814
|
Symptoms:
LSC control channel doesn't come up due to VCD conflict
Conditions:
A freed virtual circuit descriptor (VCD) can be reused immediately after the associated virtual circuit (VC) is removed. If the driver fails to remove the VC promptly, a VC creation error may occur on the new VC to which the VCD has been reassigned.
Workaround:
None
|
CSCdx26224
|
Symptom:
The cache l3 bypass global configuration command is missing from the running configuration of an active Route Processor Module (RPM).
Condition:
When a RPM softswitch command is executed on Active RPM card, the Standby (now Active) card is missing l3 bypass global configuration command from the running config.
Workaround:
None
|
CSCdx35197
|
Symptoms:
A write memory request that is received via the Simple Network Management Protocol (SNMP) is rejected if there is already a write memory request in progress.
Conditions:
This symptom is observed on a Route Processor Module-PRemium (RPM-PR) card that is installed in a Cisco switch that is running Cisco IOS Release 12.2(8)T.
Workaround:
None
|
CSCdx36259
|
Symptoms:
Traffic is dropped, and the following message may be displayed in the log:
%ATMPA-3-BADVCD: Switch1 bad vcd 25136 packet - 62308847 1F9DD0FE 000321FE
45000058 00010000 FE0001C2
Conditions:
This symptom is observed on a network in which two provider edge (PE) routers are connected via a label switch controller (LSC). The Multi-virtual circuit (VC) feature is also enabled on the network by entering the tag-switching atm multi-vc ATM subinterface submode command.
Workaround:
None
|
CSCdx38578
|
Symptoms:
An edge router that has the Multi-virtual circuit (VC) feature configured may reload when route flapping occurs.
Conditions:
An edge router that has the Multi-virtual circuit (VC) feature configured may reload when route flapping occurs. This symptom affects edge routers that have the Multi-VC feature configured and that have a label-controlled ATM (LC-ATM) interface that faces the Multiprotocol Label Switching (MPLS) core.
Workaround:
None
|
CSCin07419
|
Symptoms:
After disabling the Cell Bus Clock rate via no rpm auto cbclk; it gets enabled after the card reload.
Conditions:
Route Processor Module (RPM) may return to the default \223ON\224 state and support automatic cell bus clock change after the no rpm auto cbclk change command is issued and the card is reloaded. This condition arises when RPM card is reload.
Workaround:
Issue the no rpm auto cbclk change command explicitly on the reloaded card after every reload.
|
Known RPM/B and RPM-PR Anomalies
The following is the list of known anomalies in the RPM/B and RPM-PR software for this release. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdu47264
|
Symptoms:
Traffic discontinuity on RPM-PR
Conditions:
When we send traffic bursts on the FA card, RPM card stops routing the traffic.
Workaround:
Reseat the FA back card.
|
CSCdw61386
|
Symptoms:
Changing the pvc parameter value on RPM didn't change the local Tx pcr value on PXM.
Conditions:
This condition/issues occurs while modifying PVC parameters for a connection on RPM.
Workaround:
Re-add a new connection
|
CSCdw63102
|
Symptoms:
sh run does not show the name of the user who last modified the running config.
Conditions:
In Cisco IOS Release 12.2(4)T, the name of the last user who modified the running configuration is not displayed when the show running-config EXEC command is issued.
Workaround:
None
|
CSCdw71199
|
Symptoms:
Customer is getting the following error and needs to understand the severity of the error:
<node name deleted> 4: *Feb 11 14:32:38.418: %RPM_VIRTUAL_PORT-3-IPCERR:
switch_vport_send_pxm_with_reply: RPC failed. Error String = timeout.
Error Code = 6
Conditions:
This condition occurs due to the fact that RPC messages were getting blocked on the PXM side for DB to be ready. RPC messages get blocked on PXM for a maximum of 25seconds and by this 25 seconds DB is not ready "%Error:GenErr:Disk update failed. Error Code = 306" error is returned to RPM.
Workaround:
None
|
CSCdw82519
|
Symptoms:
SNMP request get timed out but there's no error message logged.
Conditions:
Busy Network, High Control/Data traffic through IPC.
Workaround:
None
|
CSCdx30607
|
Symptom:
Whenever VC is activated or deactivated on RPM, the following error messages are logged:
02:43:07: %RPM_VIRTUAL_PORT-3-IPCERR: switch_vport_send_pxm_with_reply:
Vport request rejected by PXM. Error String = enErr:Input parameters are
InCorrect.Error Code = 1869756999
Conditions:
On MGX8850 with PXM1 as controller card, it was observed that whenever a VC is activated/deactivated on RPM card - an error message is displayed stating that Vport request is rejected by PXM. Investigation revealed that CONN_STATE_UPDT request is not supported for MGX1 platform. These conn state/update requests should not be sent if it is MGX1 node.
A Vc can be activated/deactivated under the following scenarios:
1. Whenever the interface (the VC is bounded to) goes down/up.
2. Whenever the interface (the VC is bounded to) is administratively downed or upped (i.e using shut/no shut commands).
Workaround:
None.
|
CSCdx33763
|
Symptoms:
Subinterfaces can be successfully deleted while connections configured existed under that subinterface.
Conditions:
Through CLI, subinterface deletion is not allowed if connections are configured under that subinterface. SNMP subinterface deletion command does not behave the same way as it allows the deletion of the subinterface while connections are provisioned under it. After subinterface deletion, sh sw conn still shows the connections.
Workaround:
None
|
CSCdx36735
|
Symptoms:
Service policy configured applied to tag-switched sub-interface on an RPM gets deleted upon a reload.
Conditions:
A service-policy can be applied to a tag-switched sub-interface on an RPM, however, when the RPM is rebooted the service-policy is deleted from the interface. Always happens on a reboot
Workaround:
No workaround, after router is up manually re-apply the service-policy
|
CSCdx36868
|
Symptoms:
Excessive delay noted when modifying policy maps on the mgx RPM card. The connection updates and bulk updates are rejected by the PXM.
Conditions:
The PXM is being constantly polled for an invalid stats collection object. There were bulk updates attempted every few minutes. The config file is extremely large around 477k
Workaround:
None
|
CSCdx37044
|
Symptom:
Administratively shutting down an subinterface generates not only trap for the subinterface in question but also additional traps are generated related to other subinterfaces as well.
Condition:
Administratively shutdown an interface generated additional subinterface down traps related to other subinterfaces which are in "Administratively up" state.
Workaround:
None
|
CSCdx37987
|
Symptoms:
Latency, throughput and packet size issues with RPM-PR
Conditions:
Doing some testing on UBR connections on a RPM-PR module the customer has seen issues with
1. Throughput
2. Latency
3. Packet size
For example, if the customer configured up a connection to provide a bandwidth of 10 Meg, the UBR connection on the RPM-PR would have to be configured for 12601 kbps.
To add to this latency issues are also seen depending on the packet size. Also cell drops are seen which are not due to policing or overloading the Packets Per Second limits of the RPM-PR.
Workaround:
Unknown
|
CSCdx49181
|
Symptoms:
OSPF IA routes not distributed when adding new area to PE
Conditions:
When additional new area is added to the PE, all the LSA3 learned from other PE vial BGP does not get redistributed into this new area.
Workaround:
Execute clear ip ospf redistribution
|
CSCdv19895
|
Symptom:
Incorrect CIR on interop of FRSM and RPM-PR.
Condition:
Discrepancy in cps between RPM-PR and FRSM leading to incorrect CIR.
Workaround:
None
Further information:
RPM-PR uses 53 byte payload whereas FRSM uses 48 byte payload. Customer should set up connections with appropriate PCR/SCR taking into account the discrepancy of payload between RPM-PR and FRSM to get the required cps rate
|
CSCdx62437
|
Symptoms:
RPM reloads when vbr-nrt connection parameters are modified on switch subinterface. No traffic was flowing at the time of the crash.
Condition:
Modifying vbr-nrt connection parameter resets the card.
Workaround:
Unknown
|
CSCdw41946
|
Symptoms:
RPM config file - auto_config_slotXX - goes to zero byte size.
Conditions:
The auto_config_slot<x> file size is set to zero resulting in an invalid configuration.
Workaround:
Unknown
|
CSCdt52963
|
Symptom:
RPM adjusts its clock by GMT offset in all cases
Condition:
After a reset of the RPM the time on the RPM is off by -8 hours. i.e: if the PXM shows 09:00:00 PST and the RPM shows 01:00:00 PST It appears that the RPM assumes the time received from PXM on a reset is a UTC time and will adjust it accordingly to its configured timezone. So, if the PXM is on PST -8 and RPM is PST -8 then the RPM ends up with time that is -16 hours from UTC. PXM configured timezone is PST with a GMT offset of -8
Workaround:
Configure RPM's to be on UTC time
|
CSCdw55029
|
Symptoms:
Failed to cc to Active RPM card
Conditions:
This condition occurs while adding subinterfaces and connection using scripts.
Workaround:
Execute a switchcc command so that the card gets new seat_id.
|
CSCdw45998
|
Symptom:
Need for RPM-PR to initiate switchover on OIR/Failure of 1FE-CP Backcard.
Condition:
Only when traffic is flowing should the switchover be done.
Workaround:
Manual Softswitch
|
CSCdw70376
|
Symptom:
In MGX1 platform, tftp of the config file by the CWM from the RPM-PR card takes a long time to complete.
Condition:
Happens under all conditions
Workaround:
An alternate method to do tftp - fetches the file successfully. The steps are as follows
tftp> get RPM/auto_config_slot03
|
CSCdx01120
|
Symptoms:
Several RPM-ATM hybrid connections provisioned via CWM GUI interface are in "mismatch" state after RPM reload.
Conditions:
1. 1. Provision a rpm-atm hybrid vbr3/abr-1/ubr-1 thru CWM CM GUI
2. "MODIFY" the hybrid connections thru CMGUI
3. wait for 2 to 3 minutes, they will go into "mismatch" state.
Workaround:
Re-apply the same parameters again.
|
CSCdx33333
|
Symptom:
RPM fails to check the health of IOS image on the MGX hard disk via debug rpm check_image now c:<image_name>. Same command is successfully executed against an image in the bootflash.
Conditions:
This condition was observed after successfully upgrading the RPM card to
internally released IOS image.
Workaround:
Unknown.
|
Compatibility Notes
RPM Boot File and Firmware File Names and Sizes
The following table displays the RPM boot and firmware file names and sizes for this release.
Table 2 RPM Boot and Firmware File Names and Sizes
| |
File Name
|
File Size (in bytes)
|
Boot File
|
rpm-boot-mz.1222-8.T4
|
2753444
|
Firmware File
|
rpm-js-mz.122-8.T4
|
9028068
|
RPM Compatibility Matrix
MGX SW version
|
1.1.32
|
1.1.34
|
1.1.40
|
1.2.00 / 2.1.70
|
1.2.02 / 2.1.76
|
1.2.10 / 3.0.00
|
IOS Version
|
12.1(5.3)T_XT
|
12.2(2)T2
|
12.2(4)T
|
12.2(4)T1
|
12.2(8)T11
|
12.2(8)T4
|
CWM
|
10.4.01
|
10.4.01 Patch 1
|
10.5
|
10.5.10
|
10.5.10 Patch 1
|
11.0.00
|
MGX RPM/B and RPM-PR Hardware
Table 3 shows the front card and back card compatibility for the RPM/B and RPM-PR 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 3 Hardware Compatibility Matrix
Front Cards
|
Part Number/
Min. Version
|
Rev.
|
Back Cards
|
Part Number/
Min. Version
|
Rev.
|
MGX-RPM-128M/B
|
800-05743-01
|
A0
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E
MGX-MMF-FDDI
MGX-MMF-FDDI/FD
MGX-SMF-FDDI
MGX-SMF-FDDI/FD
|
800-02735-02
800-03202-02
800-02737-02
800-02857-01
800-03820-01
800-02736-01
800-03822-01
|
A0
A0
A0
A0
A0
A0
A0
|
MGX-RPM-PR-256
|
800-07178-02
|
A0
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E/B
|
800-02735-02
800-03202-02
800-12134-01
|
A0
A0
A0
|
MGX-RPM-PR-512
|
800-07656-02
|
A0
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E/B
|
800-02735-02
800-03202-02
800-12134-01
|
A0
A0
A0
|
Special Installation and Upgrade Requirements
Existing customers should use the upgrade procedures Upgrade Procedures for RPM Cards in MGX Release 1 (PXM1) Switches and Historical Information From 1.2.x Baseline to upgrade. A graceful upgrade from any release previous to the current release is supported. For new customers, the image will be pre-installed and should use the PXM installation procedure to upgrade to future maintenance releases.
Cisco IOS Release Compatibility Information
This section describes the installation requirements and guidelines for RPM modules installed with this release.
All IOS firmware can be downloaded from CCO from the following location:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
About the Cisco IOS 12.2(8)T4 Release
The Cisco IOS 12.2(8)T4 supports existing features on the MGX-RPM-PR and MGX-RPM-128M/B cards.
About the Cisco IOS 12.2(8)T1 Release
The Cisco IOS 12.2(8)T1 supports existing features on the MGX-RPM-PR and MGX-RPM-128M/B cards and the CBC clock rate configuration feature described in "Features Not Supported in This Release" section.
About the Cisco IOS 12.2(4)T3 Release
The Cisco IOS 12.2(4)T3 supports existing features on the MGX-RPM-PR and MGX-RPM-128M/B cards.
About the Cisco IOS 12.2(4)T1 Release
The Cisco IOS 12.2(4)T1 or higher is used with MGX Release 1.2.00. This IOS release supports new RPM features and continues to support existing features on the RPM-PR and MGX-RPM-128M/B cards.
Note that MPLS inter AS and MPLS TE are not supported features on RPM for this release.
About the Cisco IOS 12.2(4)T Release
The Cisco IOS 12.2(4)T or higher is used with MGX Release 1.1.40. This IOS release supports new RPM features and continues to support existing features on the RPM-PR and MGX-RPM-128M/B cards.
Note that MPLS inter AS and MPLS TE are not supported features on RPM for this release.
About the Cisco IOS 12.2(2)T2 and 12.2(2)T3 Release
The Cisco IOS 12.2(2)T2 and the 12.2(2)T3 Releases are used with MGX Releases 1.1.34 and 1.1.40. This IOS release does not support new RPM features, but has been tested with 1.1.34 and continues to support existing features on the RPM-PR and MGX-RPM-128M/B cards.
Please note the following anomaly in IOS Release 12.2(2)T2:
Problem Description:
Customers upgrading to 12.2(2)T2 image with RPMs might see some e-BGP sessions not coming up when the CE router is running an older version of IOS (12.0, 12.0.xT). This issue was first encountered with CE running 12.0(7)T image. In such cases, the CEs running old IOS versions were not able to create BGP sessions to PEs with the newer image (12.2(2)T2).
The issue is fixed in 12.2(2)T3. Customers who face the problems described with the 12.2(2)T2 image, may upgrade to 12.2(2)T3 image.
Symptom:
MPLS PE doesn't advertise BGP network to CE router running an older IOS image
Conditions:
A Cisco router that is running Cisco IOS Release 12.2(3.1)T or 12.2(2)T and is configured as a provider edge (PE) router may not support Label Distribution Protocol (LDP). This defect might cause the PE router not to advertise any Border Gateway Protocol (BGP) routes to a Cisco 2600 series customer edge (CE) router that is running Cisco IOS Release 12.0(18). However, the CE router will advertise routes to the PE router. Entering the neighbor ce-ipaddress don-capability-negotiate command on the PE router does not correct this defect.
Workaround:
Upgrade the CE router from Cisco IOS Release 12.0(18) to Cisco IOS Release 12.2(2)T3.
About the Cisco IOS 12.1(5.3)T_XT Release
The Cisco IOS 12.1(5.3)T_XT or higher is used with MGX Release 1.1.32 and provides support for:
•RPM-PR in any MGX chassis
(Note: RPM-PR is FCS with Release 1.1.32; and General Availability with Release 1.1.34.)
•MGX-RPM-128M/Bs in an MGX 8230 chassis
•Multiple RPM card types
•Cisco IOS 12.1(5.3)T_XT offers no other software features for the RPM.
Note To locate IOS-related anomalies or problems fixed, please refer to IOS release notes.
Problems Fixed with Cisco IOS 12.1(5.3)T_XT
Refer to the Cisco IOS Release 12.1 Release Notes at:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/index.htm
Upgrading from an MGX-RPM-128M/B Card to an RPM-PR Card
To replace an MGX-RPM-128M/B card with an RPM-PR card, the PXM must be running MGX Software Release 1.1.34 or later, and the RPM must be running IOS release 12.2(4)T or later. Then perform the following procedure.
Step 1 Insert the RPM-PR in a test node.
Step 2 Copy the new RPM-PR boot image to the flash. Verify that the boot image is the first file in the flash.
Step 3 Modify the configuration of the file to use the latest IOS image on the c: drive by entering the boot system c:<IOS_filename> command.
Step 4 Enter the write memory command to save the configuration file in NVRAM.
Step 5 Enter the show bootvar command to check the BOOT variable and to verify that the card us configured to boot from the latest image.
Now the RPM-PR card is ready to replace an MGX-RPM-128M/B card.
Step 6 Verify the following before inserting the RPM-PR in the node:
•PXM must be running a minimum firmware release of 1.1.34.
•PXM disk contains the latest IOS image specified for the RPM-PR.
Caution Once an MGX-RPM-128M/B card is replaced with a RPM-PR card, the MGX-RPM-128M/B card can not be re-installed. If an attempt is made to re-install the MGX-RPM-128M/B, the module will be put into 'Mismatch'.
Caution After installing the RPM-PR card, be sure not to mix card redundancy.
Upgrade Procedures for RPM Cards in MGX Release 1 (PXM1) Switches
The following sections describe how to upgrade boot and runtime software on RPM cards in detail.
Upgrading RPM Boot Software
At the factory, a boot file is installed in the bootflash on the RPM card and is used to boot the card. The runtime software is updated more frequently than the boot software. However, the boot software is updated occasionally. When you are updating runtime software, check Table 2 to see if a boot software upgrade is required.
The boot software is stored in bootflash memory on the RPM card. To manage the software in bootflash, you access it as if it were a hard disk. For example, in copy and delete file commands, files are identified as bootflash:filename (which is similar to c:filename).
The following example shows a directory of bootflash contents:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D config D4F7352A 40330 18 686 Jan 30 2001 18:18:41 auto_config_slot09
2 .D config CBF007C1 40660 9 688 Feb 22 2001 15:33:11 slot9.cnf
3 .. image F596869A 2973E8 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.202
Note Although you can display directory contents with the dir bootflash: command, the show flash: command provides more detail. Also, although bootflash and flash are separate entities on other Cisco Systems Routers, both terms refer to the same entity on the RPM.
In the example above, the numbers in the left column indicate the order in which the RPM card will try to load software. The second column shows that the first two files are marked for deletion (D). The last column lists the names of the files stored in bootflash.
When managing the bootflash, you need to keep in mind the following:
•When the RPM card is reset, it tries to load the first undeleted bootable image in bootflash.
•Files are not removed from bootflash until the squeeze flash: command is entered.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards. If this does not work, the card must be returned to the factory to be reprogrammed.
Upgrading RPM Runtime Software
The runtime software on the RPM can be loaded from the following sources:
•The C:RPM directory on the PXM1 hard disk
•Bootflash
•A TFTP server on a LAN to which an RPM back card is connected.
Cisco Systems recommends that you configure the RPM card to load from the C:RPM directory on the PXM1 hard disk. Note that images will load much faster from bootflash, but if you are using multiple RPM cards, it takes longer to complete an upgrade because the runtime software must be copied to each RPM card's bootflash instead of to a single location.
At startup, the RPM card attempts to load the software in the order listed in the startup-config file. The following example shows an excerpt from a startup-config file:
boot system c:rpm-js-mz.122-4.T
boot system bootflash:rpm-js-mz.122-4.T
boot config c:auto_config_slot09
logging rate-limit console 10 except errors
In the startup-config file example, the RPM card attempts to load the runtime software from the PXM1 card (C:rpm-js-mz.122-4.T) first, and if that fails, it attempts to load the image copy stored in bootflash. This configuration takes longer to upgrade, but it assures the card can reboot if someone accidentally removes the file on the PXM1 hard disk.
Note The convention is lowercase c for RPM commands and uppercase C for switch commands.
To configure the RPM to load upgraded runtime software from the PXM1 hard disk, you need to do the following:
•Copy the upgraded file to the PXM1 hard disk
•Update the boot system variable in the router startup-config file to load the new file.
•Reset the RPM card so that it loads the new file.
RPM cards can be configured for 1:N redundancy as well as for non-redundant configurations. The procedures for both types of configuration are in the sections that follow.
Tip To simplify runtime software updates, copy the runtime file in the C:RPM directory and rename it to a generic name such as rpm-js-mz. The production runtime filenames have version numbers appended to them, but you can change this. This approach allows you to perform future upgrades by copying the file to the hard disk, renaming a copy of the file to your generic name, and resetting each card. The approach eliminates the need to reconfigure IOS on each card to recognize the new filename.
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
The following procedure describes how to upgrade boot software and runtime software.
Note The first part of this procedure describes boot software upgrade and the second part describes runtime software upgrade. RPM boot software can be upgraded either in boot mode or in runtime mode. The procedure described here shows an example for runtime mode. The same commands are applicable for upgrading boot software in boot mode.
Step 1 Copy the new boot software file for the RPM card to the switch (C:RPM).
Step 2 Establish a configuration session using any valid user name.
Step 3 Use the cc command to select the RPM card to update.
The switch displays the IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 4 Enter Enable mode for the router.
Step 5 To verify router access to the PXM1 hard disk and display the boot file name, enter dir c: command.
65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot09
65540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.201
84611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T
66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.201
85809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T
104857600 bytes total (83068928 bytes free)
Step 6 To display the files in the bootflash, enter the show flash: command.
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.201
30315128 bytes available (2452872 bytes used)
Step 7 To copy new boot software to the bootflash, use the copy command.
Router#copy c:rpm-boot-mz.122-4.T bootflash:
Destination filename [rpm-boot-mz.122-4.T]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCC
2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tip When prompted for the destination filename, press enter to use the source filename shown in the prompt. To change the destination filename, type a new filename after the prompt.
Step 8 To verify that the file was copied, enter the show flash: command.
Step 9 To mark an older boot file for deletion from the bootflash, use the del bootflash: command as shown in the following example:
Delete filename []? rpm-js-mz
Delete bootflash:rpm-js-mz? [confirm]
Tip To unmark a bootflash file so that it won't be deleted when the squeeze flash: command is run, enter the undelete <number> command, where number is the file number displayed in the left-most column of the show flash: command display.
Step 10 To delete all files that are marked for deletion from bootflash, enter the squeeze flash: command as shown in the following example:
Router(boot)#squeeze flash:
All deleted files will be removed. Continue? [confirm]y
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Step 11 Enter the show flash: command to verify that the bootflash files are as you want them.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards and restart the RPM card. If this does not work, the card must be returned to the factory to be reprogrammed. When you are done managing the bootflash, the
show flash: command should display at least one bootable image, and
the image you want the card to boot from must be the first bootable image in the list.
Tip If the show flash: command does not display a bootable image, copy a bootable image to bootflash as described earlier in this procedure. You can continue to manage the bootflash, even when there are no files in bootflash, until the router is restarted.
Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM card, reset the RPM card using the resetcd <slot> command from the active PXM1 card, then quickly enter the CTRL-[, Break sequence at the RPM console. The command to send a Break depends on the computer platform and software you are using. It may take a couple of attempts to successfully get into rommon mode. When you are in rommon mode, the RPM card displays the rommon 1 > prompt.
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.
This ends the boot software upgrade procedure. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software, you need to restart the RPM card by entering the reload command.
Step 12 Copy the new runtime software file for the RPM card to the switch (C:RPM).
Step 13 Establish a configuration session using any valid user name.
Step 14 If you are using a generic filename for your runtime images, copy the file on the PXM1 hard disk and rename the copied file. For example:
8850_LA.8.PXM.a > copy rpm-js-mz.122-4.T rpm-js-mz
Step 15 If your RPM is already configured to use a file with a generic name, skip to Step 24.
Step 16 Use the cc command to select the RPM card to update.
The switch displays the IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 17 Enter Enable mode for the router.
Step 18 Configure the RPM card to store its configuration on the PXM1 hard disk by entering the following command:
Router> boot config c:auto_config_slot#
Step 19 Display the startup runtime software filename by entering the show bootvar command.
BOOT variable = c:rpm-js-mz.122-4.T,12;
CONFIG_FILE variable = c:auto_config_slot09
BOOTLDR variable does not exist
Configuration register is 0x2
In the example above, the startup runtime software file is C:rpm-js-mz.122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20 Enter the router global configuration mode.
Enter configuration commands, one per line. End with CNTL/Z.
Step 21 If you need to change the boot system filenames, remove the existing boot list using the boot system command as follows:
Router(config)# no boot system
Step 22 Create a new boot list by entering one or more boot system commands as follows:
Router(config)# boot system c:filename
Replace the filename variable with the name of the new runtime file that was previously transferred to the C:RPM directory on the switch. For example:
Router(config)# boot system c:rpm-js-mz
If you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM1 hard disk:
Router(config)# boot system bootflash:rpm-js-mz.122-4.T
Note Before the RPM card can load runtime software from bootflash, you must copy the runtime software to the bootflash. The procedure for copying files from the PXM1 hard disk to bootflash is described in a previous section.
Step 23 Exit global configuration mode and save the new configuration.
Destination filename [startup-config]?
Building configuration...
Step 24 To verify the change, enter the show bootvar or show run commands.
Step 25 Switch to the active PXM1 card and reset the RPM card. For example:
8850_LA.8.PXM.a > resetcd 9
The card in slot number 9, will be reset. Please confirm action
resetcd: Do you want to proceed (Yes/No)? y
Upgrading RPM Boot Software and Runtime Software for 1:N Redundancy
Redundancy must be established before you use the procedure in this section. If redundancy has not been established, upgrade each RPM card using the procedure in the next section, "Upgrading Without Redundancy".
To upgrade the RPM runtime software for 1:N redundancy, use the following procedure. (Note that the directory on the PXM1 card uses (C:) and the directory within the router card uses (c:).)
The following procedure describes how to upgrade boot software and runtime software.
Note The first part of this procedure describes boot software upgrade and the second part describes runtime software upgrade. RPM boot software can be upgraded either in boot mode or in runtime mode. The procedure described here shows an example for runtime mode. The same commands are applicable for upgrading boot software in boot mode.
Step 1 Copy the new boot software file for the RPM card to the switch (C:RPM).
Step 2 Establish a configuration session using any valid user name.
Step 3 Use the cc command to select the RPM card to update.
The switch displays the IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 4 Enter Enable mode for the router.
Step 5 To verify router access to the PXM1 hard disk and display the boot file name, enter dir c: command.
65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot09
65540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.201
84611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T
66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.201
85809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T
104857600 bytes total (83068928 bytes free)
Step 6 To display the files in the bootflash, enter the show flash: command.
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.201
30315128 bytes available (2452872 bytes used)
Step 7 To copy new boot software to the bootflash, use the copy command.
Router#copy c:rpm-boot-mz.122-4.T bootflash:
Destination filename [rpm-boot-mz.122-4.T]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCC
2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tip When prompted for the destination filename, press enter to use the source filename shown in the prompt. To change the destination filename, type a new filename after the prompt.
Step 8 To verify that the file was copied, enter the show flash: command.
Step 9 To mark an older boot file for deletion from the bootflash, use the del bootflash: command as shown in the following example:
Delete filename []? rpm-js-mz
Delete bootflash:rpm-js-mz? [confirm]
Tip To unmark a bootflash file so that it won't be deleted when the squeeze flash: command is run, enter the undelete <number> command, where number is the file number displayed in the left-most column of the show flash: command display.
Step 10 To delete all files that are marked for deletion from bootflash, enter the squeeze flash: command as shown in the following example:
Router(boot)#squeeze flash:
All deleted files will be removed. Continue? [confirm]y
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Step 11 Enter the show flash: command to verify that the bootflash files are as you want them.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards and restart the RPM card. If this does not work, the card must be returned to the factory to be reprogrammed. When you are done managing the bootflash, the
show flash: command should display at least one bootable image, and
the image you want the card to boot from must be the first bootable image in the list.
Tip If the show flash: command does not display a bootable image, copy a bootable image to bootflash as described earlier in this procedure. You can continue to manage the bootflash, even when there are no files in bootflash, until the router is restarted.
Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM card, reset the RPM card using the resetcd <slot> command from the active PXM1 card, then quickly enter the CTRL-[, Break sequence at the RPM console. The command to send a Break depends on the computer platform and software you are using. It may take a couple of attempts to successfully get into rommon mode. When you are in rommon mode, the RPM card displays the rommon 1 > prompt.
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.
This ends the boot software upgrade procedure for the primary card. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software for the primary card, skip steps 12 through 24 and go to step 25 to upgrade the boot software on the secondary card.
Step 12 Copy the new runtime software file for the RPM card to the switch (C:RPM).
Step 13 If you are using a generic filename for your runtime images, copy the file on the PXM1 hard disk and rename the copied file. For example:
8850_LA.8.PXM.a > copy rpm-js-mz.122-4.T rpm-js-mz
Step 14 Establish a configuration session using any valid user name.
Step 15 If your RPM is already configured to use a file with a generic name, skip to Step 25.
Step 16 Use the cc command to select the RPM card to update.
The switch displays the IOS prompt for the router on the RPM card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 17 Enter Enable mode for the router.
Step 18 Configure the RPM card to store its configuration on the PXM1 hard disk by entering the following command:
Router> boot config c:auto_config_slot#
Step 19 Display the startup runtime software filename by entering the show bootvar command.
BOOT variable = c:rpm-js-mz.122-4.T,12;
CONFIG_FILE variable = c:auto_config_slot09
BOOTLDR variable does not exist
Configuration register is 0x2
In the example above, the startup runtime software file is c:rpm-js-mz.122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20 Enter the router global configuration mode.
Enter configuration commands, one per line. End with CNTL/Z.
Step 21 If you need to change the boot system filenames, remove the existing boot list using the boot system command as follows:
Router(config)# no boot system
Step 22 Create a new boot list by entering one or more boot system commands as follows:
Router(config)# boot system c:filename
Replace the filename variable with the name of the new runtime file that was previously transferred to the C:RPM directory on the switch. For example:
Router(config)# boot system c:rpm-js-mz
If you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM1 hard disk:
Router(config)# boot system bootflash:rpm-js-mz.122-4.T
Note Before the RPM card can load runtime software from bootflash, you must copy the runtime software to the bootflash. The procedure for copying files from the PXM1 hard disk to bootflash is described in a previous section.
Step 23 Exit global configuration mode and save the new configuration.
Destination filename [startup-config]?
Building configuration...
Step 24 To verify the change, enter the show bootvar or show run commands.
Step 25 Switch to the active PXM1 card. For example:
Step 26 Switch to the secondary card using the softswitch command as follows:
8850_LA.8.PXM.a > softswitch <fromSlot> <toSlot>
Replace <fromSlot> with the slot number of the primary card. Replace <toSlot> with the slot number of the secondary card.
This step makes the secondary card active and resets the primary RPM card. When the Primary card resets, it loads the upgraded software.
Step 27 cc to the secondary slot.
Step 28 Repeat steps 1through 11.
This ends the boot software upgrade on the secondary card. If you do not want to upgrade the runtime software, go to step 30.
The following steps are for upgrading runtime software on the secondary card.
Step 29 Repeat steps 12through 24.
Step 30 Switch back to the primary card using the softswitch command as follows:
8850_LA.8.PXM.a > softswitch <fromSlot> <toSlot>
Replace <fromSlot> with the slot number of the secondary card. Replace <toSlot> with the slot number of the primary card.
This step makes the primary card active and resets the secondary RPM card. When the reset is complete, the secondary card is ready to run the upgraded software.
Step 31 To verify that the router reboot is complete, enter the dspcds or dspcd <slot> commands. The reboot is complete when the card state displays as Active. Another way to verify router operation is to use the cc slot command. If you can access the router from the switch prompt, the router reboot is complete.
Step 32 If there are other primary cards with redundant (secondary) cards, repeat this procedure for each primary card.
Using XModem to Download Flash to RPM Cards
Use the xmodem feature to download the flash to an RPM/B or RPM-PR card. During this process, the card should be connected to a target machine through HyperTerminal with settings of 9600, n, 8, and 1.
Note This feature is only available for ROMMON image version 12.2(4r)T1 or greater. Use the show version command to the verify the ROMMON version installed on an RPM card.
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:
-s<speed> Set speed of download, where speed may be
1200|2400|4800|9600|19200|38400
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.
|
-s
|
Specifies the download speed. Default is 9600 bps.
|
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.
Note The rommon "xmodem/ymodem" transfer only works on the console port. You can only download files to the router. You cannot use "xmodem/ymodem" to get files from the router.
For example:
rommon 4> xmodem -cys 38400
Do not start sending the image yet...
Invoke this application for disaster recovery. Do you wish to
Note, if the console port is attached to a modem, both the
console port and the modem must be operating at the same baud
rate. Use console speed 38400 bps for download [confirm]
Step 3 At this point, change the preferences in HyperTerminal and adjust the speed from 9600 to 38400.
Note You can continue at the speed of 9600 as well by either not specifying the -s option in the command, or by specifying 9600 explicitly, but it will take longer.
The console will display the following message:
Download will be performed at 38400. Make sure your terminal
emulator is set to this speed before sending file. Ready to
Step 4 Use the Transfer-->Send File option in HyperTerminal to start the image transfer.
In the Filename box, browse and choose the image file to be downloaded. Also since we used the "y" option while invoking the xmodem, set the transfer protocol to ymodem or use Xmodem protocol by not specifying the -y option on the command line.
The transfer screen comes up and transfer starts. (The transfer may not start immediately; wait for some time and it should start.)
After the transfer is completed (it should typically take about 10-15 minutes), the following messages are displayed on HyperTerminal console:
Returning console speed to 9600.
Please reset your terminal emulator to this speed...
Step 5 Return the console speed back to 9600 baud through HyperTerminal's Preferences menu option.
Usually, due to time lag between changing HyperTerminal speed back to 9600 baud, you might see a bunch of garbage. To avoid this, disconnect and reconnect the HyperTerminal to get the console back again.
The system will reset itself from here and will boot with new software image.
Historical Information From 1.2.x Baseline
Problems Fixed in Release 1.2.02
The following is the list of problems fixed in the service module firmware and the Release 1.2.02 software. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdx06855
|
Symptoms:
Configuration is getting corrupted after wr mem in 12.2(4)T to T3 images.
Conditions:
When wr mem is performed, using copy <src> <dst>.
If <src> is running configuration and <dst> is PXM disk, the corruption will occur.
If <src> is running configuration and <dst> is other than PXM disk, corruption will not occur.
Workaround:
Instead of using wr mem, the following 2 steps are the procedure to save configuration properly on the PXM disk.
1. issue copy run bootflash:<dummy-file>
We recommend the dummy-file is named "start-up" to make it more readable. Because we are not writing to the disk, the tag is not added.
2. issue copy bootflash:<dummy-file> start
Because we are saving a file from bootflash to the start-up, this works fine too.
Additional Information:
Note, the problem is seen with 1.2.01 and IOS versions 12.2(4)T3 or lower only. The problem is not seen with MGX 1.2.00 or lower.
|
Problems Fixed in Release 1.2.01
The following is the list of problems fixed in the service module firmware and the Release 1.2.01 software. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Note Due to CSCdx06855, MGX 1.2.01 is no longer generally available and has been deferred. This DDTS has been resolved in MGX 1.2.02.
Bug ID
|
Description
|
CSCdw41946
|
Symptom:
Loss of RPM configuration.
Condition:
The auto_config_slot<x> file size is set to zero resulting in an invalid con- figuration.
Workaround:
UNKNOWN
|
CSCdw55029
|
Symptom:
Failed to CC to RPM card
Conditions:
Added sub interfaces and connection using scripts.
Workaround:
switchcc
|
CSCdw56886
|
An error can occur with management protocol processing. Please use the following URL for further information:
http://www.cisco.com/cgi-bin/bugtool/onebug.pl?bugid=CSCdw65903
|
Problems Fixed in Release 1.2.00
The following is the list of problems fixed in the service module firmware and the Release 1.2.00 software. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdu14185
|
Symptom:
Unable to add RPM connection
Conditions:
Condition was caused by using CM and adding the ATM(RPM) to ATM(RPM) connection from mgx8250 to mgx8230 and the error was: Connection add request to PXM failed.
Workaround:
Using CM to add 3-segment connection: ATM(RPM) - ATM(RPM).
|
CSCdu34346
|
Condition:
Issue the 'addred <primary> <secondary> 2' command. The primary and secondary RPM cards should have different (number or type) of backcards.This condition also applies to the case when each card has one backcard each, both of the same type, but in different slots.
Result:
The following warning is to be expected----
addred:Prim and Sec LineModule type Mismatch. Command will proceed for the card type.
|
CSCdv26571
|
Symptoms:
Communication between PXM and all RPM in the shelf is very slow. sho ipc queue shows that the queue is full.
Conditions:
cc to RPM using two parallel sessions and run extended ping on each of the session.
Workaround:
Run extended pings from telnet sessions instead of cc to the card
|
About These Release Notes (MGX 3.0)
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 3, the user documentation (command reference, overview, and installation and configuration guides) use the MGX Release 3 and Cisco IOS documents in addition to this release note.
For RPM-PR, use the Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 (DOC-7812510=) along with this release note. The RPM-PR documentation can be found at the following MGX 8850 and MGX 8950 Release 2.1 URLs:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850r21/rpmpr/index.htm
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8950/rel21/rpm/index.htm
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
New Features
RPM in MGX 8000 Release 3 supports all new and existing features introduced in the Release 2.1 baseline. The following is a new and recent features for RPM implementations using IOS Release 12.2(8)T4.
Using the switchredcd Command with RPM-PR Cards to Switch from Active to Standby Card
The MGX RPM-PR uses the switchredcd command to manually change the active card to the standby card, similar to other MGX service modules. The switchredcd command replaces the softswitch command that was previously used and is now obsolete.
Be sure to execute the switchredcd command before removing an active RPM-PR card from the MGX 8000 series switch shelf.
See "Upgrade Procedures for RPM-PR Cards in MGX 8000 Release 2.1 and Release 3 (PXM45 and PXM1E) Switches" section and "Upgrading RPM-PR Boot Software and Runtime Software for 1:N Redundancy" section.
For more information on the switchredcd command, refer to the Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3.
VISM-PR to RPM-PR Connectivity
The VISM-PR card support 144 channels when used with the G.723.1 codec, whereas the current VISM card support supports 64 channels with the G.723.1 codec.
The following VISM Release 3.0 features require either the PXM1E or PXM45 card in your MGX 8000 Series switch chassis:
•Expanded Clock Source Selection
•Private Network-to-Network Interface Priority Routing
•Specify a Connection Up or Down
•AAL1 and AAL2 Switched Virtual Circuits
Setting connections between a VISM-PR card and a RPM-PR card in your MGX 8000 Series switch chassis requires that you use the new VBR (NRT) 3 connection type.
If you are using a VISM-PR card in combination with either a PXM1E or PXM45 card, you must use the VBR (NRT) 3 selection when adding a connection. Use the modified addcon or cnfcon commands to configure this connection type.
For more information, refer to the Cisco VISM Installation and Configuration Guide, Release 3.
Configuring the Cell Bus Clock (CBC) Rate
When two RPM-PR cards are on the same cell bus, that is, they occupy adjacent slots (for example, slots 1 and 2, slots 3 and 4), the cell bus clock (CBC) rate will be automatically 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 Release 3, reconfiguration of CBC rate from 42MHz to 21 MHz is done automatically.
RPM 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 will enable 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 will disable 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.
Enter configuration commands, one per line. End with CNTL/Z.
RPM-11(config-if)#rpm-auto-cbclk-change
Building configuration...
Building configuration...
Current configuration :142 bytes
! rpm_tag_id Apr 04 2002 02:49:04
If Traffic Shaping is not a requirement, enter the no rpm-cbclk-change command, either manually or during card configuration. The following screen output displays an example of the no rpm-auto-cbclk-change command.
Enter configuration commands, one per line. End with CNTL/Z.
RPM-11(config-if)#no rpm-auto-cbclk-change
Building configuration...
Building configuration...
Current configuration :145 bytes
! rpm_tag_id Apr 04 2002 02:49:57
Note By default on the RPM this feature is enabled.
Previously Released Features
LDP on RPM-PR in MGX 8850 and MGX 8950
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 or 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 an 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:
•IETF Standards-based Label distribution protocol
•Multi-Vendor Interoperability
•TDP to LDP migration and interoperability
Multi-LVC on RPM in MGX 8850 and MGX 8950 Release 2.1.76 Running 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.
Multiprotocol Label Switching (MPLS) over ATM using VC Merge in MGX 8850 and MGX 8950 Release 2.1.76 Running Cisco IOS Release 12.2(8)T
The virtual circuit (VC) merge facility allows a switch to aggregate multiple incoming flows with the same destination address into a single outgoing flow. Wherever VC merge occurs, several incoming labels are mapped to one single outgoing label. Cells from different virtual channel identifiers (VCIs) going to the same destination are transmitted to the same outgoing VC using multipoint-to-point connections. This sharing of labels reduces the total number of VCs required for label switching.
Without VC merge, each path consumes one label VC on each interface along the path. VC merge reduces the label space shortage by sharing labels for different flows with the same destination. Therefore, VC-Merge connections are unidirectional, and furthermore, all merged connections must be of the same service type.
Note To support VC-merge, the ATM switch requires that AXSM cards allow multiple VC frames to be merged into a single VC without interleaving cells inside AAL5 frames. The RPM is the control point, where LSC resides.
VC Merge is enabled by default when the MPLS over ATM network is configured and is only used when the RPM is used as an LSC (Label Switch Controller). Because it is enabled by default, the only commands necessary are:
no tag-switching atm vc-merge to disable VC Merge
and
tag-switching atm vc-merge to enable VC Merge
For more information, see MPLS Label Switch Controller and Enhancements at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122newft/122t/122t8/ftlsc.htm#xtocid15
Bypass Feature for RPM in Cisco IOS Release 12.2(4)T
Note Information about the bypass feature and the IOS commands used to support it was not available at the time of the printing of the RPM documents; therefore, it is included in the these release notes.
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 command is used to bypass the NVRAM and save the configuration on the file auto_config_slot## located in E:/RPM, where ## represents the zero-padded slot number in which the RPM-PR 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, issue the command no rpmnvbypass.
To verify that the bypass feature is either enabled or disabled, issue 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 Because the bypass feature bypasses NVRAM, it is not necessary to compress the configuration file using the command service compress-config.
Table 4 contains cautions important to the successful usage of the bypass feature.
Table 4 Boot Cautions
Caution
|
Why is This Important?
|
When using the bypass feature, you can only load the run time IOS image from the PXM hard-drive or from the boot flash.
|
In the case of an RPM module, the IOS image can be loaded in 3 ways:
1. From the PXM hard-drive.
2. From the boot flash.
3. From the network (for example, via TFTP) from the RPM back card (Ethernet or Fast Ethernet).
When the bypass feature is enabled, the boot config statement:
is automatically generated. The NVRAM configuration is cleared upon a write memory. In order to load from the network, the RPM has to have an IP address for its backcard. This information is part of the NVRAM configuration, which was just cleared by enabling the bypass feature. Hence, it is not possible to load the IOS image from the network upon a reload of the RPM after the rpmnvbypass and write memory have been executed.
|
Do not execute the command no boot config because doing so may prevent the bypass feature from working properly.
|
When the bypass feature is enabled, the "boot config" statement:
is automatically generated, and the NVRAM configuration is cleared.
Any writes now are directed to the boot config file. This is essential, as a write memory expects the boot config statement to be present.
If the boot config statement isn't present, it would write the configuration into the NVRAM, which of course, is not desirable when the objective is to save a complete configuration when the configuration is large and requires more space.
|
If the command write memory is issued with the bypass feature enabled, and is consequently followed by an RPM card reset, previous versions of the boot image will trigger the RPM card to go into boot mode (unable to load run-time IOS).
|
For safety purposes, the location of the system image is stored in a special area (called the ROMMON area) in the NVRAM. The ROMMON is always intact.
The 12.2(4)T boot image accesses and reads ROMMON in order to load the IOS image. Boot images prior to 12.2(4)T do not read the ROMMON area.
Generally, the IOS boot and run-time images are of the same versions. However, if the user changed his boot image to one prior to 12.2(4)T, on a reload, the boot image would see that the NVRAM configuration is empty (of course, this is normal when the bypass feature is enabled). However, since boot images prior to 12.2(4)T cannot access the ROMMON area, it cannot read there the location of the IOS image. Unable to see the IOS image, it instead loads itself.
|
Example 6 through Example 10 illustrate how the bypass feature is enabled and disabled, and how to validate each of these actions from the configuration display.
Example 6 Running configuration without the bypass feature enabled
rpm_slot02#show running-config
Building configuration...
Current configuration : 470 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
snmp-server community public RO
snmp-server community private RW
Example 7 Enable the bypass feature (rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#rpmnvbypass
The "boot config" statement has been (re)added to your
running configuration. Do not remove it else risk not
using the nvbypass feature
Example 8 Running configuration with bypass feature enabled (note rpmnvbypass at end of output)
rpm_slot02#show running-config
Building configuration...
Current configuration : 515 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
boot config c:auto_config_slot02 <==== Line added as per output above
snmp-server community public RO
snmp-server community private RW
Example 9 Disable the bypass feature (no rpmnvbypass)
rpm_slot02#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
rpm_slot02(config)#no rpmnvbypass
Example 10 Running configuration after the bypass feature is disabled
rpm_slot02#show running-config
Building configuration...
Current configuration : 503 bytes
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
boot system c:rpm-js-mz.<new_rel>
boot config c:auto_config_slot02
snmp-server community public RO
snmp-server community private RW
Features Not Supported in This Release
•MPLS inter AS
•MPLS TE
RPM Redundancy Support
RPM 1:N redundancy is used to switch configuration and traffic from one RPM card to another. The main benefits are:
•Route processing continues even if an RPM fails and there is no operator or direct access to swap the failed card or fix the problem.
•An RPM 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.
SNMP MIB
SNMP MGX Release 3.0 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 The old_mib_Format is discontinued as of this release.
Notes and Cautions
The following notes and cautions should be reviewed before using this release.
UPC Connection Parameters
In Release 2.1.60 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.
•cnfupccbr
•cnfupcvbr
•cnfupcabr
•cnfupcubr
Booting the RPM-PR
Refer to Chapter 5, "Configuring the MGX RPM-PR" in the Cisco MGX Route Processor Module RPM-PR) Installation and Configuration Guide, Release 2.1, (DOC-7812510=) 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 and can result in bootflash corruption. If the bootflash is corrupted, you will have to send the card back for an external burn with a valid boot image.
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 Omitting the card number resets the entire system.
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 or MGX 8950, it goes through the following boot sequence:
1. The RPM-PR runs diagnostics on the CPU, memory, and interfaces.
2. The system boot software, which is the boot image, executes and searches for a valid Cisco IOS image, which is the RPM-PR runtime software.
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 2.1 (DOC-7812510=).
a. If the configuration register is set to the factory-default setting of 0x01, RPM-PR will come up and stay in boot mode.
b. If the configuration register is 0x2, the RPM-PR will look for the runtime image either in bootflash or on the PXM45/B E:RPM drive.
3. The search for runtime image is determined by which boot system command is entered.
a. Entering the boot system e:<runtime_image_name> command will result in a search for a runtime image in the E:RPM directory on the PXM45 hard disk.
b. Entering the boot system bootflash:<runtime_image_name> will result in a search for a run time image in the bootflash.
4. If the runtime software is not found after three attempts, the RPM-PR reverts to the boot mode.
5. If a valid Cisco IOS image is found, then the RPM-PR searches for a valid configuration, which can reside in NVRAM or as a configuration file either on the PXM hard disk E: drive or in bootflash.
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 e:<config_file> command.
6. For normal RPM-PR operation, there must be a valid Cisco IOS image on the PXM45 E: drive or in bootflash, and a configuration in NVRAM or configuration file in bootflash or on the PXM disk.
The first time you boot the RPM-PR, configure the RPM-PR interfaces and save the configuration to a file in NVRAM. Then follow the procedure described in "Initializing the RPM-PR Card." 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 Erasing or moving the boot image can cause RPM-PR boot failure. When this happens, the RPM must be returned to Cisco and reflashed.
In order to avoid this unnecessary failure, requiring card servicing, you should
•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 will successfully boot.
CLI Modifications in MGX Release 3.0
There are no new or modified RPM-PR CLI commands in Release 3.0.
Limitations and Restrictions
CWM Recognition of RPM-PR Back Card
CWM does not distinguish between the Ethernet back card versions installed with the RPM-PR. There is no functionality difference.
RPM Front Card Resets on the Back Card Removal
The RPM front card may reset on an MGX 8850 or MGX 8950 switch 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-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).
RPM-PR Limitations and Restrictions (PXM45 and PXM1E)
The RPM-PR and MPLS limitations and restrictions that apply to this release are as follows:
•In an application where the RPM is a Provider Edge Router in an MPLS Virtual Private Network service, a much better solution in any case is to use a distance-vector routing protocol between the customer routers and the RPM. A distance-vector routing protocol provides exactly the information required for this application: reachability information, and not link-state information. The distance-vector routing protocols supported by the RPM are BGP, RIP v1 and RIP v2, as well as static routing. With RPM software releases from 12.0.7T1, distance-vector routing protocols can be used with as many different networks as subinterfaces.
•Note that if the RPM is acting as a Provider Edge Router in an MPLS Virtual Private Network service, and even if OSPF is running in a customer network, it is not necessary to run OSPF between the customer router and the RPM. If the customer edge devices run Cisco IOS, they can redistribute OSPF routing information into RIP using the IOS commands, redistribute RIP in the OSPF configuration, and redistribute OSPF in the RIP configuration. Similar configurations are possible for BGP. (For more information on re advertisement, see the "Configuring IP Routing Protocol-Independent Features" chapter in the Cisco IOS Release 12.0 Network Protocols Configuration Guide, Part 1). Redistribution is not unique to Cisco CPE, and other vendors' equipment also supports redistribution.
•Whenever there are 2 RPM cards on adjacent slots, driven by the same cell bus clock, the clock rate should be set to 42 MHz for traffic shaping, using the command cnfcbclk. This configuration will be lost if the node rebuilds due to resetsys or a power cycle. The user will have to manually re-configure the cell bus clock rate after the rebuild, using the cnfcbclk command.
•On PXM45-based switches, when the chassis is loaded with 6 or more RPM-PR cards, and if every card is configured to download the IOS runtime image from the PXM45 hard disk, occasionally, upon entering a resetsys command or after a power cycle, some of the RPM-PR cards may go into the failed state. To reset the failed RPM-PR cards, enter the resetcd <slot #> command for each failed card.
•RPM-PR cannot be configured as ELSR (Edge Label Switch Router) with PXM1E as controller card.
•Saveallcnf (issued on the PXM45/B card) captures configuration data saved by the RPM-PR card (as well as AXSM and PXM45 cards), and saves it on the active PXM45/B card's hard disk. Users must have configured RPM to store its configuration on the PXM45/B hard disk (E:/RPM). That is, on RPM, a user should have this line in its running configuration (boot config e:auto_config_slot#). To ensure that the saved file contains the latest RPM configuration, the user needs to execute the copy run start command on each RPM card prior to the saveallcnf command. This way, the RPM files on the active PXM45 hard disk will contain the latest configuration to be saved.
•A single RPM-PR can only function as either an Edge LSR or as an LSC, but not as both.
•Total of (OC12 minus T3) Mbps intrashelf traffic for Cell bus based modules are supported.
•To configure redundancy, the primary and secondary RPM-PR cards need to be in the Active state and the secondary card should not have any configuration.
•Removing a back card does not cause RPM-PR switchover.
•After establishing redundancy between two RPM-PR cards with the addred command, you must enter the copy run start command on the primary RPM-PR card to save the configuration change.
•If a secondary RPM-PR card is redundant to primary cards x and y, you cannot delete redundancy for only card x.
•If you need to enter the switchredcd (formerly softswitch) and switchcc commands, Cisco Systems recommends that you wait at least 5 seconds after issuing the switchredcd command, and then enter the switchcc command.
•IOS software images on primary and secondary RPM-PR cards do not have to be compatible, but the IOS software on a secondary card should be at the same level as the primary card or higher.
•For ELSR to LSC connectivity, default control vc used is 32. If PNNI partition exists with VCI 32 as part of its partition range, then when MPLS partition is added, there are two options to handle the situation:
–Add 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-PR and AXSM, AXSM/B or AXSM-E APS Management Information.
•Whenever the RPM-PR configuration is changed and a user wants to store that configuration, the user must enter the copy run start command on the RPM-PR. If this is not done, the changed configuration will be lost on RPM-PR card reboot or RPM-PR switchover in case of redundancy.
•Even though RPM-PR can have 1999 sub interfaces, the usage of sub interfaces should be planned in such a way that it does not cross a safe limit of 1985. This is because each sub interface takes one IDB (interface descriptor block) and the number of IDBs available in the card is 2000. Further, a user might need some IDBs for the RPM-PR back card and its ports.
Problems Fixed in This Release
The following is the list of problems fixed in the RPM-PR service module firmware and software for this release. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdw64591
|
Symptoms:
A Cisco Route Processor Module (RPM) may pause indefinitely after the clear ip ospf is executed.
Conditions:
A Cisco Route Processor Module (RPM) may pause indefinitely after the clear ip ospf process EXEC command is issued and display the following message on the console:
%ATMPA-3-BADVCD: Switch1 bad vcd 1460 packet - 05B49847 000900FE
002021FE45000058 00010000 FE00C3A0
Workaround:
Reset the RPM.
|
CSCdx01120
|
Symptoms:
Several rpm-atm hybrid connections provisioned via CWM GUI interface are in "mismatch" state after RPM reload.
Conditions:
1. Provision a rpm-atm hybrid vbr3/abr-1/ubr-1 thru CWM CM GUI
2. "MODIFY" the hybrid connections thru CMGUI
3. Wait for 2 to 3 minutes, they will go into "mismatch" state.
Workaround:
Reapply the same parameters again.
|
CSCdx11351
|
Symptom:
When a permanent virtual circuit (PVC) is deleted from the Cisco WAN Manager (CWM), the Route Processor Module (RPM) resets and produces a flash file.
Conditions:
When a permanent virtual circuit (PVC) is deleted from the Cisco WAN Manager (CWM). This behavior occurs only when a service policy is configured on the connection.
Workaround:
Add the service policy to the PVC after a connection is added. Manually remove the service policy for a connection before deleting the connection and PVC from the CWM.
|
CSCdx20802
|
Symptoms:
Memory fragmentation may cause 2 MB of memory allocation to fail.
Conditions:
This symptom affects edge routers that are configured for multi-virtual circuit (Multi-VC) and that have Label-Controlled ATM (LC-ATM) interfaces connected toward a Multiprotocol Label Switching (MPLS) core. Incremental memory leaks occur after the LC-ATM interface is toggled by issuing the shutdown interface configuration command followed by the no shutdown interface configuration command or after Cisco Express Forwarding (CEF) is enabled and later disabled on the router by issuing the ip cef global configuration command followed by the no ip cef global configuration command. Incremental memory leaks may also be seen when route flaps occur. If the incremental memory leaks continue, memory fragmentation may occur and traffic may stop passing through the LC-ATM interface.
Workaround:
None
|
CSCdx20814
|
Symptoms:
LSC control channel doesn't come up due to VCD conflict
Conditions:
A freed virtual circuit descriptor (VCD) can be reused immediately after the associated virtual circuit (VC) is removed. If the driver fails to remove the VC promptly, a VC creation error may occur on the new VC to which the VCD has been reassigned.
Workaround:
None
|
CSCdx26224
|
Symptom:
The cache l3 bypass global configuration command is missing from the running configuration of an active Route Processor Module (RPM).
Condition:
When a RPM softswitch command is executed on Active RPM card, the Standby (now Active) card is missing l3 bypass global configuration command from the running config.
Workaround:
None
|
CSCdx35197
|
Symptoms:
A write memory request that is received via the Simple Network Management Protocol (SNMP) is rejected if there is already a write memory request in progress.
Conditions:
This symptom is observed on a Route Processor Module-PRemium (RPM-PR) card that is installed in a Cisco switch that is running Cisco IOS Release 12.2(8)T.
Workaround:
None
|
CSCdx36259
|
Symptoms:
Traffic is dropped, and the following message may be displayed in the log:
%ATMPA-3-BADVCD: Switch1 bad vcd 25136 packet - 62308847 1F9DD0FE 000321FE
45000058 00010000 FE0001C2
Conditions:
This symptom is observed on a network in which two provider edge (PE) routers are connected via a label switch controller (LSC). The Multi-virtual circuit (VC) feature is also enabled on the network by entering the tag-switching atm multi-vc ATM subinterface submode command.
Workaround:
None
|
CSCdx38578
|
Symptoms:
An edge router that has the Multi-virtual circuit (VC) feature configured may reload when route flapping occurs.
Conditions:
An edge router that has the Multi-virtual circuit (VC) feature configured may reload when route flapping occurs. This symptom affects edge routers that have the Multi-VC feature configured and that have a label-controlled ATM (LC-ATM) interface that faces the Multiprotocol Label Switching (MPLS) core.
Workaround:
None
|
CSCin07419
|
Symptoms:
After disabling the Cell Bus Clock rate via no rpm auto cbclk; it gets enabled after the card reload.
Conditions:
Route Processor Module (RPM) may return to the default \223ON\224 state and support automatic cell bus clock change after the no rpm auto cbclk change command is issued and the card is reloaded. This condition arises when RPM card is reload.
Workaround:
Issue the no rpm auto cbclk change command explicitly on the reloaded card after every reload.
|
Known RPM-PR Anomalies
The following is the list of known anomalies in the RPM-PR software for this release. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the Release Note enclosure of the problem record in Bug Navigator.
Bug ID
|
Description
|
CSCdu47264
|
Symptoms:
Traffic discontinuity on RPM-PR
Conditions:
When we send traffic bursts on the FA card, RPM card stops routing the traffic.
Workaround:
Reseat the FA back card.
|
CSCdw61386
|
Symptoms:
Changing the pvc parameter value on RPM didn't change the local Tx pcr value on PXM.
Conditions:
This condition/issues occurs while modifying PVC parameters for a connection on RPM.
Workaround:
Re-add a new connection
|
CSCdw63102
|
Symptoms:
sh run does not show the name of the user who last modified the running config.
Conditions:
In Cisco IOS Release 12.2(4)T, the name of the last user who modified the running configuration is not displayed when the show running-config EXEC command is issued.
Workaround:
None
|
CSCdw71199
|
Symptoms:
Customer is getting the following error and needs to understand the severity of the error:
<node name deleted> 4: *Feb 11 14:32:38.418: %RPM_VIRTUAL_PORT-3-IPCERR:
switch_vport_send_pxm_with_reply: RPC failed. Error String = timeout.
Error Code = 6
Conditions:
This condition occurs due to the fact that RPC messages were getting blocked on the PXM side for DB to be ready. RPC messages get blocked on PXM for a maximum of 25seconds and by this 25 seconds DB is not ready "%Error:GenErr:Disk update failed. Error Code = 306" error is returned to RPM.
Workaround:
None
|
CSCdw82519
|
Symptoms:
SNMP request get timed out but there's no error message logged.
Conditions:
Busy Network, High Control/Data traffic through IPC.
Workaround:
None
|
CSCdx30607
|
Symptom:
Whenever VC is activated or deactivated on RPM, the following error messages are logged:
02:43:07: %RPM_VIRTUAL_PORT-3-IPCERR: switch_vport_send_pxm_with_reply:
Vport request rejected by PXM. Error String = enErr:Input parameters are
InCorrect.Error Code = 1869756999
Conditions:
On MGX8850 with PXM1 as controller card, it was observed that whenever a VC is activated/deactivated on RPM card - an error message is displayed stating that Vport request is rejected by PXM. Investigation revealed that CONN_STATE_UPDT request is not supported for MGX1 platform. These conn state/update requests should not be sent if it is MGX1 node.
A Vc can be activated/deactivated under the following scenarios:
1. Whenever the interface (the VC is bounded to) goes down/up.
2. Whenever the interface (the VC is bounded to) is administratively downed or upped (i.e using shut/no shut commands).
Workaround:
None.
|
CSCdx33763
|
Symptoms:
Subinterfaces can be successfully deleted while connections configured existed under that subinterface.
Conditions:
Through CLI, subinterface deletion is not allowed if connections are configured under that subinterface. SNMP subinterface deletion command does not behave the same way as it allows the deletion of the subinterface while connections are provisioned under it. After subinterface deletion, sh sw conn still shows the connections.
Workaround:
None
|
CSCdx36735
|
Symptoms:
Service policy configured applied to tag-switched sub-interface on an RPM gets deleted upon a reload.
Conditions:
A service-policy can be applied to a tag-switched sub-interface on an RPM, however, when the RPM is rebooted the service-policy is deleted from the interface. Always happens on a reboot
Workaround:
No workaround, after router is up manually re-apply the service-policy
|
CSCdx36868
|
Symptoms:
Excessive delay noted when modifying policy maps on the mgx RPM card. The connection updates and bulk updates are rejected by the PXM.
Conditions:
The PXM is being constantly polled for an invalid stats collection object. There were bulk updates attempted every few minutes. The config file is extremely large around 477k
Workaround:
None
|
CSCdx37044
|
Symptom:
Administratively shutting down an subinterface generates not only trap for the subinterface in question but also additional traps are generated related to other subinterfaces as well.
Condition:
Administratively shutdown an interface generated additional subinterface down traps related to other subinterfaces which are in "Administratively up" state.
Workaround:
None
|
CSCdx37987
|
Symptoms:
Latency, throughput and packet size issues with RPM-PR
Conditions:
Doing some testing on UBR connections on a RPM-PR module the customer has seen issues with
1. Throughput
2. Latency
3. Packet size
For example is the customer configured up a connection to provide a bandwidth of 10 Meg the UBR connection on the RPM-PR would have to be configured for 12601 kbps.
To add to this latency issues are also seen depending on the packet size. Also cell drops are seen which are not due to policing or overloading the Packets Per Second limits of the RPM-PR.
Workaround:
Unknown
|
CSCdx49181
|
Symptoms:
OSPF IA routes not distributed when adding new area to PE
Conditions:
When additional new area is added to the PE, all the LSA3 learned from other PE vial BGP does not get redistributed into this new area.
Workaround:
Execute clear ip ospf redistribution
|
CSCdv19895
|
Symptom:
Incorrect CIR on interop of FRSM and RPM-PR.
Condition:
Discrepancy in cps between RPM-PR and FRSM leading to incorrect CIR.
Workaround:
None
Further information:
RPM-PR uses 53 byte payload whereas FRSM uses 48 byte payload. Customer should set up connections with appropriate PCR/SCR taking into account the discrepancy of payload between RPM-PR and FRSM to get the required cps rate
|
CSCdx62437
|
Symptoms:
RPM reloads when vbr-nrt connection parameters are modified on switch subinterface. No traffic was flowing at the time of the crash.
Condition:
Modifying vbr-nrt connection parameter resets the card.
Workaround:
Unknown
|
CSCdw41946
|
Symptoms:
RPM config file - auto_config_slotXX - goes to zero byte size.
Conditions:
The auto_config_slot<x> file size is set to zero resulting in an invalid configuration.
Workaround:
Unknown
|
CSCdt52963
|
Symptom:
RPM adjusts its clock by GMT offset in all cases
Condition:
After a reset of the RPM the time on the RPM is off by -8 hours. i.e: if the PXM shows 09:00:00 PST and the RPM shows 01:00:00 PST It appears that the RPM assumes the time received from PXM on a reset is a UTC time and will adjust it accordingly to its configured timezone. So, if the PXM is on PST -8 and RPM is PST -8 then the RPM ends up with time that is -16 hours from UTC. PXM configured timezone is PST with a GMT offset of -8
Workaround:
Configure RPM's to be on UTC time
|
CSCdw55029
|
Symptoms:
Failed to cc to Active RPM card
Conditions:
This condition occurs while adding subinterfaces and connection using scripts.
Workaround:
Execute a switchcc command so that the card gets new seat_id.
|
CSCdw45998
|
Symptom:
Need for RPM-PR to initiate switchover on OIR/Failure of 1FE-CP Backcard.
Condition:
Only when traffic is flowing should the switchover be done.
Workaround:
Manual Softswitch
|
CSCdw70376
|
Symptom:
In MGX1 platform, tftp of the config file by the CWM from the RPM-PR card takes a long time to complete.
Condition:
Happens under all conditions
Workaround:
An alternate method to do tftp - fetches the file successfully. The steps are as follows
tftp> get RPM/auto_config_slot03
|
CSCdx01120
|
Symptoms:
Several RPM-ATM hybrid connections provisioned via CWM GUI interface are in "mismatch" state after RPM reload.
Conditions:
1. 1. Provision a rpm-atm hybrid vbr3/abr-1/ubr-1 thru CWM CM GUI
2. "MODIFY" the hybrid connections thru CMGUI
3. wait for 2 to 3 minutes, they will go into "mismatch" state.
Workaround:
Re-apply the same parameters again.
|
CSCdx33333
|
Symptom:
RPM fails to check the health of IOS image on the MGX hard disk via debug rpm check_image now c:<image_name>. Same command is successfully executed against an image in the bootflash.
Conditions:
This condition was observed after successfully upgrading the RPM card to
internally released IOS image.
Workaround:
Unknown.
|
Compatibility Notes
RPM Boot File and Firmware File Names and Sizes
The following table displays the RPM 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
|
rpm-boot-mz.1222-8.T4
|
2753444
|
Firmware File
|
rpm-js-mz.122-8.T4
|
9028068
|
RPM Compatibility Matrix
MGX SW version
|
2.1.60
|
2.1.70
|
2.1.76
|
2.1.79
|
3.0.00
|
IOS Version
|
12.2(4)T
|
12.2(4)T1
|
12.2(8)T1
|
12.2(8)T4
|
12.2(8)T4
|
CWM
|
10.5
|
10.5.10
|
10.5.10 Patch 1
|
10.5.10 Patch 2
|
11.0.00
|
MGX RPM-PR Hardware
Table 6 shows the front card and back card compatibility for RPM-PR 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 6 Hardware Compatibility Matrix
Front Cards
|
Part Number/
Min. Version
|
Rev.
|
Back Cards
|
Part Number/
Min. Version
|
Rev.
|
MGX-RPM-PR-256
|
800-07178-02
|
A0
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E/B
|
800-02735-02
800-03202-02
800-12134-01
|
A0
A0
A0
|
MGX-RPM-PR-512
|
800-07656-02
|
A0
|
MGX-RJ45-FE
MGX-MMF-FE
MGX-RJ45-4E/B
|
800-02735-02
800-03202-02
800-12134-01
|
A0
A0
A0
|
Special Installation and Upgrade Requirements
Existing customers should use the upgrade procedures Upgrade Procedures for RPM-PR Cards in MGX 8000 Release 2.1 and Release 3 (PXM45 and PXM1E) Switches and Historical Information From 2.1.7x Baseline to upgrade. A graceful upgrade from any release previous to the current release is supported. For new customers, the image will be pre-installed and should use the PXM installation procedure to upgrade to future maintenance releases.
Cisco IOS Release Compatibility Information
This section describes the installation requirements and guidelines for RPM modules installed with this release.
All IOS firmware can be downloaded from CCO from the following location:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
About the Cisco IOS 12.2(8)T4 Release
The Cisco IOS 12.2(8)T4 supports existing features on the MGX-RPM-PR card.
About the Cisco IOS 12.2(8)T1 Release
The Cisco IOS 12.2(8)T1 supports existing features on the MGX-RPM-PR card and the CBC clock rate configuration feature described in "Features Not Supported in This Release" section.
About the Cisco IOS 12.2(4)T3 Release
The Cisco IOS 12.2(4)T3 supports existing features on the MGX-RPM-PR card.
About the Cisco IOS 12.2(4)T1 Release
The Cisco IOS 12.2(4)T1 or higher is used with MGX Release 21.70. This IOS release supports new RPM features and continues to support existing features on the RPM-PR card.
Note that MPLS inter-AS and MPLS TE are not supported features on RPM for this release.
About the Cisco IOS 12.2(4)T Release
The Cisco IOS 12.2(4)T or higher is used with MGX Release 2.1.60. This IOS release supports new RPM features and continues to support existing features on the RPM-PR card.
Note that MPLS inter-AS and MPLS TE are not supported features on RPM for this release.
Upgrade Procedures for RPM-PR Cards in MGX 8000 Release 2.1 and Release 3 (PXM45 and PXM1E) Switches
The following sections describe how to upgrade boot and runtime software on RPM-PR cards in detail.
Upgrading RPM Boot Software
At the factory, a boot file is installed in the bootflash on the RPM-PR card and is used to boot the card. The runtime software is updated more frequently than the boot software. However, the boot software is updated occasionally. When you are updating runtime software, check Table 5 to see if a boot software upgrade is required.
The boot software is stored in bootflash memory on the RPM card. To manage the software in bootflash, you access it as if it were a hard disk. For example, in copy and delete file commands, files are identified as bootflash:filename (which is similar to e:filename).
The following example shows a directory of bootflash contents:
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .D config D4F7352A 40330 18 686 Jan 30 2001 18:18:41 auto_config_slot09
2 .D config CBF007C1 40660 9 688 Feb 22 2001 15:33:11 slot9.cnf
3 .. image F596869A 2973E8 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.202
Note Although you can display directory contents with the dir bootflash: command, the show flash: command provides more detail. Also, although bootflash and flash are separate entities on other Cisco Systems Routers, both terms refer to the same entity on the RPM.
In the example above, the numbers in the left column indicate the order in which the RPM-PR card will try to load software. The second column shows that the first two files are marked for deletion (D). The last column lists the names of the files stored in bootflash.
When managing the bootflash, you need to keep in mind the following:
•When the RPM card is reset, it tries to load the first bootable image in bootflash.
•Files are not removed from bootflash until the squeeze flash: command is entered.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards. If this does not work, the card must be returned to the factory to be reprogrammed.
Upgrading RPM Runtime Software
The runtime software on the RPM can be loaded from the following sources:
•The E:RPM directory on the PXM45 hard disk
•Bootflash
•A TFTP server on a LAN to which an RPM back card is connected.
Cisco Systems recommends that you configure the RPM card to load from the E:RPM directory on the PXM45 hard disk. Note that images will load much faster from bootflash, but if you are using multiple RPM cards, it takes longer to complete an upgrade because the runtime software must be copied to each RPM card's bootflash instead of to a single location.
At startup, the RPM card attempts to load the software in the order listed in the startup-config file. The following example shows an excerpt from a startup-config file:
boot system e:rpm-js-mz.122-4.T
boot system bootflash:rpm-js-mz.122-4.T
boot config c:auto_config_slot09
logging rate-limit console 10 except errors
In the startup-config file example, the RPM card attempts to load the runtime software from the PXM45 card (E:rpm-js-mz.122-4.T) first, and if that fails, it attempts to load the image copy stored in bootflash. This configuration takes longer to upgrade, but it assures the card can reboot if someone accidentally removes the file on the PXM45 hard disk.
Note The convention is lowercase e for RPM-PR commands and uppercase E for switch commands.
To configure the RPM to load upgraded runtime software from the PXM45 hard disk, you need to do the following:
•Copy the upgraded file to the PXM45 hard disk
•Update the boot system variable in the router startup-config file to load the new file.
•Reset the RPM card so that it loads the new file.
RPM-PR cards can be configured for 1:N redundancy as well as for non-redundant configurations. The procedures for both types of configuration are in the sections that follow.
Tip To simplify runtime software updates, copy the runtime file in the E:RPM directory and rename it to a generic name such as rpm-js-mz. The production runtime filenames have version numbers appended to them, but you can change this. This approach allows you to perform future upgrades by copying the file to the hard disk, renaming a copy of the file to your generic name, and resetting each card. The approach eliminates the need to reconfigure IOS on each card to recognize the new filename.
Upgrade Procedure for Boot Software and Runtime Software for Non-Redundant Cards
The following procedure describes how to upgrade boot software and runtime software.
Note The first part of this procedure describes boot software upgrade and the second part describes runtime software upgrade. RPM boot software can be upgraded either in boot mode or in runtime mode. The procedure described here shows an example for runtime mode. The same commands are applicable for upgrading boot software in boot mode.
Step 1 Copy the new boot software file for the RPM-PR card to the switch (E:RPM).
Step 2 Establish a configuration session using any valid user name.
Step 3 Use the cc command to select the RPM-PR card to update.
The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM-PR on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 4 Enter Enable mode for the router.
Step 5 To verify router access to the PXM45 hard disk and display the boot file name, enter dir e: command.
65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot09
65540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.201
84611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T
66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.201
85809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T
104857600 bytes total (83068928 bytes free)
Step 6 To display the files in the bootflash, enter the show flash: command.
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.201
30315128 bytes available (2452872 bytes used)
Step 7 To copy new boot software to the bootflash, use the copy command.
Router#copy c:rpm-boot-mz.122-4T bootflash:
Destination filename [rpm-boot-mz.122-4T]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCC
2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tip When prompted for the destination filename, press enter to use the source filename shown in the prompt. To change the destination filename, type a new filename after the prompt.
Step 8 To verify that the file was copied, enter the show flash: command.
Step 9 To mark an older boot file for deletion from the bootflash, use the del bootflash: command as shown in the following example:
Delete filename []? rpm-js-mz
Delete bootflash:rpm-js-mz? [confirm]
Tip To unmark a bootflash file so that it won't be deleted when the squeeze flash: command is run, enter the undelete <number> command, where number is the file number displayed in the left-most column of the show flash: command display.
Step 10 To delete all files that are marked for deletion from bootflash, enter the squeeze flash: command as shown in the following example:
Router(boot)#squeeze flash:
All deleted files will be removed. Continue? [confirm]y
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Step 11 Enter the show flash: command to verify that the bootflash files are as you want them.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards and restart the RPM card. If this does not work, the card must be returned to the factory to be reprogrammed. When you are done managing the bootflash, the
show flash: command should display at least one bootable image, and
the image you want the card to boot from must be the first bootable image in the list.
Tip If the show flash: command does not display a bootable image, copy a bootable image to bootflash as described earlier in this procedure. You can continue to manage the bootflash, even when there are no files in bootflash, until the router is restarted.
Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM card, reset the RPM card using the resetcd <slot> command from the active PXM45 card, then quickly enter the CTRL-[, Break sequence at the RPM console. The command to send a Break depends on the computer platform and software you are using. It may take a couple of attempts to successfully get into rommon mode. When you are in rommon mode, the RPM card displays the rommon 1 > prompt.
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.
Note This ends the boot software upgrade procedure. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software, you need to restart the RPM card by entering the reload command.
Step 12 Copy the new runtime software file for the RPM-PR card to the switch (E:RPM).
Step 13 Establish a configuration session using any valid user name.
Step 14 If you are using a generic filename for your runtime images, copy the file on the PXM45 hard disk and rename the copied file. For example:
8850_LA.8.PXM.a > copy rpm-js-mz.122-4.T rpm-js-mz
Step 15 If your RPM is already configured to use a file with a generic name, skip to Step 24.
Step 16 Use the cc command to select the RPM-PR card to update.
The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this release note. This procedure details only those commands that are unique to setting up RPM-PR on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 17 Enter Enable mode for the router.
Step 18 Configure the RPM card to store its configuration on the PXM45 hard disk by entering the following command:
Router# boot config e:auto_config_slot#
Step 19 Display the startup runtime software filename by entering the show bootvar command.
BOOT variable = e:rpm-js-mz.122-4.T,12;
CONFIG_FILE variable = c:auto_config_slot09
BOOTLDR variable does not exist
Configuration register is 0x2
In the example above, the startup runtime software file is E:rpm-js-mz.122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20 Enter the router global configuration mode.
Enter configuration commands, one per line. End with CNTL/Z.
Step 21 If you need to change the boot system filenames, remove the existing boot list using the boot system command as follows:
Router(config)# no boot system
Step 22 Create a new boot list by entering one or more boot system commands as follows:
Router(config)# boot system e:filename
Replace the filename variable with the name of the new runtime file that was previously transferred to the E:RPM directory on the switch. For example:
Router(config)# boot system e:rpm-js-mz
If you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM45 hard disk:
Router(config)# boot system bootflash:rpm-js-mz.122-4.T
Note Before the RPM card can load runtime software from bootflash, you must copy the runtime software to the bootflash. The procedure for copying files from the PXM45 hard disk to bootflash is described in a previous section.
Step 23 Exit global configuration mode and save the new configuration.
Destination filename [startup-config]?
Building configuration...
Step 24 To verify the change, enter the show bootvar or show run commands.
Step 25 Switch to the active PXM45 card and reset the RPM card. For example:
8850_LA.8.PXM.a > resetcd 9
The card in slot number 9, will be reset. Please confirm action
resetcd: Do you want to proceed (Yes/No)? y
Upgrading RPM-PR Boot Software and Runtime Software for 1:N Redundancy
Redundancy must be established before you use the procedure in this section. If redundancy has not been established, upgrade each RPM-PR card using the procedure in the next section, "Upgrading Without Redundancy".
To upgrade the RPM-PR runtime software for 1:N redundancy, use the following procedure. (Note that the directory on the PXM45 card uses (E:) and the directory within the router card uses (e:).)
The following procedure describes how to upgrade boot software and runtime software.
Note The first part of this procedure describes boot software upgrade and the second part describes runtime software upgrade. RPM boot software can be upgraded either in boot mode or in runtime mode. The procedure described here shows an example for runtime mode. The same commands are applicable for upgrading boot software in boot mode.
Step 1 Copy the new boot software file for the RPM-PR card to the switch (E:RPM).
Step 2 Establish a configuration session using any valid user name.
Step 3 Use the cc command to select the RPM-PR card to update.
The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this book. This procedure details only those commands that are unique to setting up RPM-PR on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 4 Enter Enable mode for the router.
Step 5 To verify router access to the PXM45 hard disk and display the boot file name, enter dir e: command.
65539 -rw- 815 Sep 13 2001 23:51:10 auto_config_slot09
65540 -rw- 2588780 Mar 22 2001 19:06:54 rpm-boot-mz_002.001.070.201
84611 -rw- 2452768 Apr 05 2001 05:34:44 rpm-boot-mz.122-4.T
66805 -rw- 8529104 Mar 22 2001 19:09:00 rpm-js-mz_002.001.070.201
85809 -rw- 7936012 Apr 05 2001 06:28:54 rpm-js-mz.122-4.T
104857600 bytes total (83068928 bytes free)
Step 6 To display the files in the bootflash, enter the show flash: command.
-#- ED --type-- --crc--- -seek-- nlen -length- -----date/time------ name
1 .. image F596869A 296D88 27 2452744 Feb 28 2001 03:16:05
rpm-boot-mz_002.001.070.201
30315128 bytes available (2452872 bytes used)
Step 7 To copy new boot software to the bootflash, use the copy command.
Router#copy c:rpm-boot-mz.122-4.T bootflash:
Destination filename [rpm-boot-mz.122-4.T]?
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
CCCCCCCCCCCCCCCCCCCC
2334044 bytes copied in 35.768 secs (66686 bytes/sec)
Tip When prompted for the destination filename, press enter to use the source filename shown in the prompt. To change the destination filename, type a new filename after the prompt.
Step 8 To verify that the file was copied, enter the show flash: command.
Step 9 To mark an older boot file for deletion from the bootflash, use the del bootflash: command as shown in the following example:
Delete filename []? rpm-js-mz
Delete bootflash:rpm-js-mz? [confirm]
Tip To unmark a bootflash file so that it won't be deleted when the squeeze flash: command is run, enter the undelete <number> command, where number is the file number displayed in the left-most column of the show flash: command display.
Step 10 To delete all files that are marked for deletion from bootflash, enter the squeeze flash: command as shown in the following example:
Router(boot)#squeeze flash:
All deleted files will be removed. Continue? [confirm]y
Squeeze operation may take a while. Continue? [confirm]
Squeeze of bootflash complete
Step 11 Enter the show flash: command to verify that the bootflash files are as you want them.
Caution If all bootable images are deleted from bootflash, try to reinstall the bootflash file using the Xmodem download procedure found in
Using XModem to Download Flash to RPM Cards and restart the RPM card. If this does not work, the card must be returned to the factory to be reprogrammed. When you are done managing the bootflash, the
show flash: command should display at least one bootable image, and
the image you want the card to boot from must be the first bootable image in the list.
Tip If the show flash: command does not display a bootable image, copy a bootable image to bootflash as described earlier in this procedure. You can continue to manage the bootflash, even when there are no files in bootflash, until the router is restarted.
Tip If the bootflash contains bootable images and the sequence is such that the card will not start, you can enter rommon mode and load the bootable image. To get into rommon mode, establish a console connection to the RPM card, reset the RPM card using the resetcd <slot> command from the active PXM45 card, then quickly enter the CTRL-[, Break sequence at the RPM console. The command to send a Break depends on the computer platform and software you are using. It may take a couple of attempts to successfully get into rommon mode. When you are in rommon mode, the RPM card displays the rommon 1 > prompt.
Once in rommon mode, you can enter the dir bootflash: command to display the images in bootflash. To boot one of the images, enter a boot command the following format: boot bootflash:filename.
See Using XModem to Download Flash to RPM Cards.
This ends the boot software upgrade procedure for the primary card. The following steps are for upgrading the runtime software. If you do not want to upgrade the runtime software for the primary card, skip steps 12 through 24 and go to step 25 to upgrade the boot software on the secondary card.
Step 12 Copy the new runtime software file for the RPM-PR card to the switch (E:RPM).
Step 13 If you are using a generic filename for your runtime images, copy the file on the PXM45 hard disk and rename the copied file. For example:
8850_LA.8.PXM.a > copy rpm-js-mz.122-4.T rpm-js-mz
Step 14 Establish a configuration session using any valid user name.
Step 15 If your RPM is already configured to use a file with a generic name, skip to Step 25.
Step 16 Use the cc command to select the RPM-PR card to update.
The switch displays the IOS prompt for the router on the RPM-PR card. From this point on, all commands are Cisco IOS commands.
Note This procedure assumes that you are familiar with Cisco IOS, which is a topic that is beyond the scope of this release note. This procedure details only those commands that are unique to setting up RPM-PR on the switch. For general Cisco IOS commands, examples are given to show how to complete the task.
Step 17 Enter Enable mode for the router.
Step 18 Configure the RPM card to store its configuration on the PXM45 hard disk by entering the following command:
Router# boot config e:auto_config_slot#
Step 19 Display the startup runtime software filename by entering the show bootvar command.
BOOT variable = e:rpm-js-mz,12;
CONFIG_FILE variable = c:auto_config_slot09
BOOTLDR variable does not exist
Configuration register is 0x2
In the example above, the startup runtime software file is e:rpm-js-mz.122-4.T, and it has a version number attached to it. Another way to view the boot list is to enter the show startup-config command and look for the boot system commands.
Step 20 Enter the router global configuration mode.
Enter configuration commands, one per line. End with CNTL/Z.
Step 21 If you need to change the boot system filenames, remove the existing boot list using the boot system command as follows:
Router(config)# no boot system
Step 22 Create a new boot list by entering one or more boot system commands as follows:
Router(config)# boot system e:filename
Replace the filename variable with the name of the new runtime file that was previously transferred to the E:RPM directory on the switch. For example:
Router(config)# boot system e:rpm-js-mz
If you want to enter additional boot system commands, enter them in the order in which you want the RPM card to use them. The following example adds a statement to load from bootflash if the runtime file is not found on the PXM45 hard disk:
Router(config)# boot system bootflash:rpm-js-mz.122-4.T
Note Before the RPM card can load runtime software from bootflash, you must copy the runtime software to the bootflash. The procedure for copying files from the PXM45 hard disk to bootflash is described in a previous section.
Step 23 Exit global configuration mode and save the new configuration.
Destination filename [startup-config]?
Building configuration...
Step 24 To verify the change, enter the show bootvar or show run commands.
Step 25 Switch to the active PXM45 card. For example:
Step 26 Switch to the secondary card using the switchredcd command as follows:
8850_LA.8.PXM.a > switchredcd <fromSlot> <toSlot>
Replace <fromSlot> with the slot number of the primary card. Replace <toSlot> with the slot number of the secondary card.
This step makes the secondary card active and resets the primary RPM-PR card. When the Primary card resets, it loads the upgraded software.
Step 27 cc to the secondary slot.
Step 28 Repeat steps 1through 11.
This ends the boot software upgrade on the secondary card. If you do not want to upgrade the runtime software, go to step 30.
The following steps are for upgrading runtime software on the secondary card.
Step 29 Repeat steps 12through 24.
Step 30 Switch back to the primary card using the switchredcd command as follows:
8850_LA.8.PXM.a > switchredcd <fromSlot> <toSlot>
Replace <fromSlot> with the slot number of the secondary card. Replace <toSlot> with the slot number of the primary card.
This step makes the primary card active and resets the secondary RPM-PR card. When the reset is complete, the secondary card is ready to run the upgraded software.
Step 31 To verify that the router reboot is complete, enter the dspcds or dspcd <slot> commands. The reboot is complete when the card state displays as Active. Another way to verify router operation is to use the cc slot command. If you can access the router from the switch prompt, the router reboot is complete.
Step 32 If there are other primary cards with redundant (secondary) cards, repeat this procedure for each primary card.
Using XModem to Download Flash to RPM Cards
Use the xmodem feature to download the flash to an RPM/B or RPM-PR 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:
-s<speed> Set speed of download, where speed may be
1200|2400|4800|9600|19200|38400
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.
|
-s
|
Specifies the download speed. Default is 9600 bps.
|
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.
Note The rommon "xmodem/ymodem" transfer only works on the console port. You can only download files to the router. You cannot use "xmodem/ymodem" to get files from the router.
For example:
rommon 4> xmodem -cys 38400
Do not start sending the image yet...
Invoke this application for disaster recovery. Do you wish to
Note, if the console port is attached to a modem, both the
console port and the modem must be operating at the same baud
rate. Use console speed 38400 bps for download [confirm]
Step 3 At this point, change the preferences in HyperTerminal and adjust the speed from 9600 to 38400.
Note You can continue at the speed of 9600 baud as well by either not specifying the -s option in the command, or by specifying 9600 baud explicitly, but it will take longer.
The console will display the following message:
Download will be performed at 38400. Make sure your terminal
emulator is set to this speed before sending file. Ready to
Step 4 Use the Transfer-->Send File option in HyperTerminal to start the image transfer.
In the Filename box, browse and choose the image file to be downloaded. Also since we used the "y" option while invoking the xmodem, set the transfer protocol to ymodem or use Xmodem protocol by not specifying the -y option on the command line.
The transfer screen comes up and transfer starts. (The transfer may not start immediately; wait for some time and it should start.)
After the transfer is completed (it should typically take about 10-15 minutes), the following messages are displayed on HyperTerminal console:
Returning console speed to 9600.
Please reset your terminal emulator to this speed...
Step 5 Return the console speed back to 9600 through HyperTerminal's Preferences menu option.
Usually, due to time lag between changing HyperTerminal speed back to 9600, you might see a bunch of garbage. To avoid this, disconnect and reconnect the HyperTerminal to get the console back again.
The system will reset itself from here and will boot with new software image.
Historical Information From 2.1.7x Baseline
Known Anomalies in Release 2.1.79
Table 7 lists the anomalies and known workarounds for release 2.1.79.
Table 7 Known Anomalies in Release 2.1.79
Bug ID
|
Description
|
S2 Bugs
|
CSCdx30862
|
Symptom: RPM-PR found in empty/reserved the root cause unknown at this time. The RPM-PR card did recover successfully to standby state with a resetcd executed for the suspect slot.
Condition: Online diag data path problem to finding the card in the empty state.
Workaround: None
|
CSCdx36868
|
Symptom: Excessive delay noted when modifying policy maps on the mgx RPM card. The connection updates and bulk updates are rejected by the PXM.
Condition: The PXM is being constantly polled for an invalid stats collection object. There were bulk updates attempted every few minutes. The config file is extremely large around 477k
Workaround: None
|
CSCdx38504
|
Symptom: RPM-PR cannot communicate successfully with the PXM.
Condition: Power cycle the MGX8850, the card recovered in a empty/reserve state The RPM does boot successfully and cab be viewed via the console CLI. the dspcd on the pxm does not recognize the RPM.
Workaround: None
|
S3 Bugs
|
CSCdw53940
|
Symptom: addred warns Prim and Sec LineModule type Mismatch
Condition: when previously Primary RPM-PR contains a backcard and removed later
Workaround: None
|
CSCdx43364
|
Symptom: The OID represents the interface name (ifName). The interface "sw1" is the main switch interface on the RPM. There can be only one main switch interface that can exist per RPM card and multiple sub-Interfaces.. The switch subinterfaces (subinterfaces of the main switch interface) are represented by "sw1.x" on RPM.
This snmp response is returned by the RPM. The ifTable does not display multiple instances for "sw1". The snmp query on ifName seems to always return "sw1" 5 times. This is not correct.
Condition : If we do snmpget on ifName, then it's possible to see multiple records for the same "Sw1" interface. To get the ifIndex for a paticular interface, we can try to walk on ifDescr.
Workaround: None
|
Anomalies Resolved in Release 2.1.79
CSCdx31305; S1; Secondary RPM IPC seat gets deleted when it NAKs the GO-ACTIVE req
CSCdx38360; S1; RPM-PR went into failed/discovering state after multiple swithcc
CSCdx44536; S1; switchredcd for RPMs shouldnt be allowed for cards in discovering
CSCdv76791; S3; dspcd command output does not display card information for RPM
CSCdw43588; S3; After switchover,RPM_PR red card data not exist in config file
Anomaly Status Changes in 2.1.79
Bug ID
|
Description
|
S3 Bugs
|
CSCdu49855
|
JUP: Temporary IPC-error -- pxm45-RPM_PR related. Unreproducible
|
Known Anomalies in Release 2.1.76
Note Please refer to the MGX 8850 2.1.76 release notes for resolved and known anomalies related to the MGX infrastructure.
There are no known anomalies for the MGX 8950 release of 2.1.76.
Table 8 lists the anomalies and known workarounds for release 2.1.76.
Table 8 Known Anomalies in Release 2.1.76
Bug ID
|
Description
|
S2 Bugs
|
CSCdw92534
|
Symptom: Packet loss on SPVC which has RPM as slave end & AXSM as master end
Conditions: When RPM is a slave end & AXSM as master end of a connection and long ping is executed.
Workaround: None.
|
CSCdx10240
|
Symptom: Cell Bus clock rate set incorrectly when two RPM occupy a cell bus.
Condition: For traffic shaping on RPM, two RPM occupying a cell bus need to have cbus clock rate set to 42MHz. In all other conditions, cbus clock rate should be 21MHz. This is manually configurable today using the cnfcbclk cli command. Need to have it automatically set.
Workaround: Use cnfcbclk cli command to set cbus clock rate correctly.
|
S3 Bugs
|
CSCdu49855
|
Symptom: IPC-error for RPM-PR
Condition: None
Workaround: None
|
Anomalies Resolved in Release 2.1.76
Table 9 lists the anomalies resolved in release 2.1.76
Table 9 Anomalies Resolved in Release 2.1.76
Bug
|
Description
|
S1 Bugs
|
|
CSCdw93466
|
Need card reset hold functionality for RPM
|
Anomaly Status Changes in Release 2.1.76
Table 10 lists anomalies that have changed status in Release 2.1.76.
Table 10 Anomalies that have changed status in Release 2.1.76
Anomaly ID
|
Description
|
S2 Anomalies
|
CSCdw71214
|
Switchredcd cmd is not completely disallowed from RPM 1:N mode. Duplicate of CSCdt95815
|
Known Anomalies for Release 2.1.75
Table 11 lists the anomalies and known workarounds for release 2.1.75.
Table 11 Known Anomalies in Release 2.1.75
Bug ID
|
Description
|
S2 Bugs
|
CSCdw71214
|
Symptom: Customer requests that switchredcd provide error message when trying to switch between primary and standby RPM-PR cards w/ 1:N configuration enabled.
Condition: Unknown
Workaround: None
|
Anomalies Resolved in Release 2.1.75
Table 12 lists the anomalies resolved in release 2.1.75.
Table 12 Anomalies Resolved in Release 2.1.75
Bug
|
Description
|
S2 Bugs
|
|
CSCdu53234
|
Jup: RPM-PR back cards cannot be detected with dspcds
|
CSCdw13285
|
Jup & MGX: dspcds show RPM back cards active regardless they are empty
|
CSCdw26680
|
E:RPM directory does not sync between active & standby
|
CSCdw44751
|
Slot remap error possibly caused by RPM 1:n redundancy.
|
CSCdw53900
|
Softswitch failing from secondary to primary for RPM Cards
|
CSCdw70993
|
1:N new active RPM-PR not copying running config from old active
|
CSCdw75504
|
SLT: upg on node with RPMs caused PXM to go into FAILED state.
|
S3 Bugs
|
|
CSCdu18220
|
RPM error msg when exceeding bw on abr cons states pcr/scr s/b mcr
|
CSCdu69875
|
JUP: replications error from RPM-PR while secondary pxm is in INIT
|
CSCdv91589
|
SLT: rpm-pr tries to create data base for standby/secondary rpm-pr
|
CSCdw27985
|
HMM CBC needs to ignore inval slotid to support RPM traffic shaping
|
Anomaly Status Changes in Release 2.1.75
Table 13 lists anomalies that have changed status in Release 2.1.75.
Table 13 Anomalies that have changed status in Release 2.1.75
Anomaly ID
|
Description
|
S1 Anomalies
|
|
CSCdw00887
|
SLT: Some rpm-pr goes to FAIL state when switchcc!. Duplicate of CSCdt60558
|
S2 Anomalies
|
CSCdv41385
|
Jup: One RPM failed on reload/resetcd randomly. Duplicate of CSCdv88233
|
CSCdw07374
|
up: Some of connections are missing in RPM with 2k cons after reload. Unreproducible
|
S3 Anomalies
|
CSCdw06746
|
Incorrect status reported for failed RPM-PR module. Closed
|
Known Anomalies in Release 2.1.70
Table 14
Table 14 Known Anomalies in Release 2.1.70
Bug ID
|
Description
|
S1Bugs
|
CSCdw00887
|
Symptom: Sometimes when RPM_PR card is reloaded, it goes into FAIL state.
Condition: Sometimes RPM_PR some time goes into fail state when switchcc command is executed to switch between slot 7 and slot 8.
Workaround: Do a switchcc back, this will force the RPM_PR to reload and eventually to come up.
|
S2 Bugs
|
CSCdu53234
|
Symptom: RPM-PR back cards can not be detected from PXM
Condition: Performed dspcds
Workaround: cc into the RPM-PR card, Check the backcard presence by doing a "show interface brief"
|
CSCdv41385
|
Symptom: One RPM failed on reload /resetcd randomly
Condition: When the RPM cards comes up. It is unable to register the polling port to pxm randomly. So RPM cannot create the ipc session for polling port. The RPM card goes into fail state.
Workaround: Reload or resetcd again
|
CSCdw07374
|
Symptom: Connections are missing in RPM after a reload.
Condition: While adding 2k connections via a scripts, it was noted that some of the slave end points did not get created or were missing.
Workaround: None
|
S3 Bugs
|
CSCdu57693
|
Symptom: Resetcd on an RPM-PR leads to deletion of all NON-DAX RPM-RPM segments on that card
Condition: Add few non-dax connections on an RPM-PR card. Reset that card. After a while after the card comes up as active, it will be seen that the segments of those non-dax connections on that card are deleted.
Workaround: Perform a "write memory" on the RPM before reset of the card
|
CSCdu70112
|
Symptoms: RPM-PR card reboots after repeated removal/insertion of FE backcard.
Conditions: After the third time insert and ping on the fast ethernet back-card of the RPM-PR -- a bus error causes the RPM-PR to reboot.
Workaround: None
|
lists known anomalies in Release 2.1.70.
Anomalies Resolved in Release 2.1.70
Table 15 lists the anomalies that have been resolved in Release 2.1.70.
Table 15 Anomalies Resolved in Release 2.1.70
Anomaly ID
|
Description
|
|
S1 Anomalies
|
|
CSCdw00887
|
SLT: Some rpm-pr goes to FAIL state when switchcc!
|
CSCdw15710
|
SLT:in the rpm file status for the ok connections is failed
|
S2 Bugs
|
|
CSCdv14066
|
RPM-PR CLI show subinterface existed, but not existed in the agent
|
CSCdv17888
|
JUP:redundant rpm(standby/primary) failed if switchcc/burnboot/runrev
|
CSCdv24248
|
Jup:All RPMs go to boot state for few seconds after PXM switch over
|
CSCdv25962
|
Unable to cc to RPM-PR Card (IPC port failure)
|
CSCdv32157
|
RPM 1:N Redundancy lost on setrev
|
CSCdv40509
|
rpm_port status on rpm card differs from PXM database
|
CSCdv40835
|
Jup: a active rpm (secondary) failed on softswitch to standby
|
CSCdv44062
|
Operational Status UNKNOWN trap generated after deleting RPM subif
|
CSCdv47189
|
delred does not work on RPM slot if prim & sec slots are EMPTY
|
CSCdv54801
|
RPM-PR cannot boot up after 1:N Redundancy
|
CSCdv72612
|
Cannot add redundancy on RPM cards
|
CSCdw13285
|
Jup&MGX:dspcds show RPM backcards active regardless they are empty
|
S3 Bugs
|
|
CSCdu62578
|
Jup: RPM-PR backcards can not be detected with dspcds
|
CSCdv11854
|
clrallcnf works inconsistently on RPM slots
|
Anomaly Status Changes in Release 2.1.70
Table 16 lists anomalies that have changed status in Release 2.1.70.
Table 16 Anomalies that Have Changed Status in Release 2.1.70
Anomaly ID
|
Description
|
S2 Anomalies
|
CSCdv12161
|
dspconinfo on pxm45 shows different count than RPM; Unreproducible
|
CSCdv45704
|
Connection count between PXM mib database and RPM doesn't match; Unreproducible
|
CSCdv47316
|
RPM Redundancy switchover generates sub-if deletion, conn alarm trap; Duplicated
|
Known RPM-PR/MPLS Anomalies
Table 17
Table 17 Known RPM-PR/MPLS Anomalies
Anomaly ID
|
Description
|
S1Anomalies
|
CSCdv19895
|
Symptom: RPM-PR and FRSM Interop.
Condition: During the connection management
Workaround: Unknown
|
lists the anomalies that pertain to the route processor module and the MPLS feature.
Related Documentation
The following Cisco publications contain additional information related to the operation of this product and associated equipment in a Cisco WAN switching network.
Cisco WAN Manager Release 11
The product documentation for the Cisco WAN Manager (CWM) network management system for Release 11 is listed in Table 18.
Table 18 Cisco WAN Manager Release 11 Documentation
Title
|
Description
|
Cisco WAN Manager Installation Guide for Solaris 7, Release 11
DOC-7813567=
|
Provides procedures for installing Release 11 of the CWM network management system and Release 5.4 of CiscoView.
|
Cisco WAN Manager User's Guide, Release 11
DOC-78-13568=
|
Describes how to use the CWM Release 11 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.
|
Cisco WAN Manager SNMP Service Agent, Release 11
DOC-7813569=
|
Provides information about the CWM Simple Network Management Protocol Service Agent, an optional adjunct to CWM that is used for managing Cisco WAN switches using SNMP.
|
Cisco WAN Manager Database Interface Guide, Release 11
DOC-7813542=
|
Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.
|
Cisco MGX 8850 (PXM45) Multiservice Switch Release 3
The product documentation for the installation and operation of the MGX 8850 Multiservice Switch for Release 3 is listed in Table 19.
Table 19 Cisco MGX 8850 (PXM45) Multiservice Switch Release 3 Documentation
Title
|
Description
|
Cisco MGX 8850 Hardware Installation Guide, Release 3 (PXM45/B and PXM1E)
DOC-7814250=
|
Describes how to install the MGX 8850 multiservice switch. This guide explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both broadband and narrow band service modules.
|
Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3
DOC-7814245=
|
Describes how to use the PXM and AXSM commands that are available for the MGX 8850, MGX 8950, and MGX 8830 switches.
|
Cisco Frame Relay Software Configuration Guide and Command Reference for the MGX 8850 FRSM12 Card, Release 3
DOC-7810327=
|
Describes how to use the high-speed Frame Relay (FRSM12) commands that are available for the MGX 8850 switch.
|
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3
DOC-7814577=
|
Describes how to configure MGX 8850 and MGX 8950 switches with PXM45 controller cards to operate as ATM edge or core switches. This guide also provides some operation and maintenance procedures.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco VISM Installation and Configuration Guide, Release 3
OL-2521-01 (online only)
|
Describes how to install and configure VISM1 in several MGX 8000 Series switches. This guide is available online only.
|
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 3
OL-2768-01 (online only)
|
Describes how to install and configure the MGX Route Processor Module (RPM-XF) in the MGX 8850 Release 3 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1
DOC-7812510=
|
Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8850 Release 2.1 and later switches. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides the latest feature, upgrade, and compatibility information, as well as known and resolved anomalies for RPM-PR.
|
Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3
The product documentation for the installation and operation of the Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 is listed in Table 20.
Table 20 Cisco MGX 8850 (PXM1E) Multiservice Switch Release 3 Documentation
Title
|
Description
|
Cisco MGX 8850 Hardware Installation Guide (PXM45/B and PXM1E), Release 3
DOC-7814250=
|
Describes how to install the MGX 8850 multiservice switch. This guide explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both broadband and narrow band service modules.
|
Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3
DOC-7814245=
|
Describes how to use the PXM and AXSM commands that are for the the MGX 8850, MGX 8950, and MGX 8830 switches.
|
Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3
DOC-7814248=
|
Describes how to configure MGX 8850 and MGX 8830 switches with PXM1E controller cards to operate as ATM edge switches. This guide also provides some operation and maintenance procedures.
|
Cisco Frame Relay Software Configuration Guide and Command Reference for MGX Switches (PXM1E)
DOC-7814255=
|
Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides command descriptions for all FRSM commands.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1
DOC-7812510=
|
Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8850 Release 3 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides the latest compatibility information, as well as known and resolved anomalies for RPM-PR.
|
Cisco MGX 8950 Multiservice Switch Release 3
The product documentation for the installation and operation of the MGX 8950 Multiservice Switch for Release 3 is listed in Table 21.
Table 21 Cisco MGX 8950 Multiservice Switch Release 3 Documentation
Title
|
Description
|
Cisco MGX 8950 Hardware Installation Guide, Release 3
DOC-7814147=
|
Describes how to install the MGX 8950 core switch. This guide explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The MGX 8950 switch uses a PXM45/B controller card and provides support for broadband service modules.
|
Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3
DOC-7814245=
|
Describes how to use the PXM and AXSM commands that are available for the MGX 8850, MGX 8950, and MGX 8830 switches.
|
Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 3
DOC-7814577=
|
Describes how to configure MGX 8850 and MGX 8950 switches with PXM45 controller cards to operate as ATM edge or core switches. This guide also provides some operation and maintenance procedures.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1
DOC-7812510=
|
Describes how to install and configure the MGX Route Processor Module (RPM-PR) in the MGX 8950. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides the latest feature, upgrade, and compatibility information, as well as known and resolved anomalies for RPM-PR.
|
Service Expansion Shelf PNNI Controller Release 3
The product documentation for the installation and operation of the Service Expansion Shelf (SES) PNNI Controller is listed in Table 22.
Table 22 SES PNNI Controller Release 3 Documentation
Title
|
Description
|
Cisco SES PNNI Controller Software Configuration Guide, Release 3
DOC-7814258=
|
Describes how to configure, operate, and maintain the SES PNNI Controller.
|
Cisco SES PNNI Controller Command Reference, Release 3
DOC-7814260=
|
Provides a description of the commands used to configure and operate the SES PNNI Controller.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco MGX 8830 Multiservice Switch Release 3
The product documentation for the installation and operation of the MGX 8830 Multiservice Switch Release 3 is listed in Table 23.
Table 23 Cisco MGX 8830 Multiservice Switch Release 3 Documentation
Title
|
Description
|
Cisco MGX 8830 Hardware Installation Guide, Release 3
DOC-7814547=
|
Describes how to install the MGX 8830 edge switch. This guide explains what the switch does and covers site preparation, grounding, safety, card installation, and cabling. The MGX 8830 switch uses a PXM1E controller card and provides PNNI support for narrow band service modules.
|
Cisco MGX 8850 (PXM1E) and MGX 8830 Software Configuration Guide, Release 3
DOC-7814248=
|
Describes how to configure MGX 8850 and MGX 8830 switches with PXM1E controller cards to operate as ATM edge switches. This guide also provides some operation and maintenance procedures.
|
Cisco MGX 8850, MGX 8950, and MGX 8830 Command Reference (PXM45/B and PXM1E), Release 3
DOC-7814245=
|
Describes how to use the PXM and AXSM commands that are available in the CLI of the MGX 8850, MGX 8950, and MGX 8830 switches.
|
Cisco Frame Relay Software Configuration Guide and Command Reference for MGX Switches (PXM1E)
DOC-7814255=
|
Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides command descriptions for all FRSM commands.
|
Cisco MGX and SES PNNI Network Planning Guide for MGX Release 3 and SES Release 3
DOC-7814261=
|
Provides guidelines for planning a PNNI network that uses the MGX 8850 and the MGX 8950 switches and the BPX 8600 switches. When connected to a PNNI network, each BPX 8600 series switch requires a SES for PNNI route processing.
|
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1
DOC-7812510=
|
Describes how to configure the MGX Route Processor Module (RPM-PR) in the MGX 8830 Release 3 switch. Also provides troubleshooting, maintenance, and basic Cisco IOS configuration information. (For RPM-PR software configuration information only.)
|
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1
DOC-7812278=
|
Describes how to install the MGX Route Processor Module (RPM-PR) in the MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting and maintenance information, cable and connector specifications, and basic RPM-PR slot and redundancy limitations and constraints. (For RPM-PR hardware installation information only.)
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides compatibility information, as well as known and resolved anomalies for RPM-PR.
|
Cisco WAN Switching Software Release 9.3.40
The product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.3.40 is listed in Table 24.
Table 24 Cisco WAN Switching Software Release 9.3.40 Documentation
Title
|
Description
|
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30
DOC-7812907=
|
Provides a general description and technical details of the BPX broadband switch.
|
Cisco WAN Switching Command Reference, Release 9.3.30
DOC-7812906=
|
Provides detailed information on the general command line interface commands.
|
Cisco IGX 8400 Series Installation Guide
OL-1165-01 (online only)
|
Provides hardware installation and basic configuration information for IGX 8400 Series switches that are running Switch Software Release 9.3.30 or earlier.
|
Cisco IGX 8400 Series Provisioning Guide
OL-1166-01 (online only)
|
Provides information for configuration and provisioning of selected services for the IGX 8400 Series switches that are running Switch Software Release 9.3.40 or earlier.
|
Cisco IGX 8400 Series Regulatory Compliance and Safety Information
DOC-7813227=
|
Provides regulatory compliance, product warnings, and safety recommendations for the IGX 8400 Series switch.
|
9.3.40 Version Software Release Notes for Cisco WAN Switching System Software
78-13538-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
MGX 8850 (PXM1) Multiservice Switch Release 1.2.10
The product documentation for the installation and operation of the MGX 8850 (PXM1) Multiservice Switch is listed in Table 25.
Table 25 MGX 8850 (PXM1) Multiservice Switch Release 1.2.10 Documentation
Title
|
Description
|
Cisco MGX 8850 Multiservice Switch Installation and Configuration, Release 1.1.3
DOC-7811223=
|
Provides installation instructions for the MGX 8850 multiservice switch.
|
Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3
DOC-7811210=
|
Provides detailed information on the general command line for the MGX 8850 switch.
|
Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3
DOC-7811240=
|
Provides error message descriptions and recovery procedures.
|
Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3
OL-1154-01 (online only)
|
Provides a technical description of the system components and functionality of the MGX 8850 multiservice switch from a technical perspective.
|
Cisco VISM Installation and Configuration Guide, Release 3
OL-2521-01 (online only)
|
Describes how to install and configure VISM in several MGX 8000 Series switches. This guide is available online only.
|
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1
DOC-7812278=
|
Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (Release 1), Software Version 1.2.10 (PXM1)
78-14247-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
MGX 8250 Edge Concentrator Release 1.2.10
The documentation for the installation and operation of the MGX 8250 Edge Concentrator is listed in Table 26.
Table 26 MGX 8250 Edge Concentrator Release 1.2.10 Documentation
Title
|
Description
|
Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3
DOC-7811217=
|
Provides installation instructions for the MGX 8250 Edge Concentrator.
|
Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3
DOC-7811212=
|
Provides detailed information on the general command line interface commands.
|
Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3
DOC-7811216=
|
Provides error message descriptions and recovery procedures.
|
Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3
DOC-7811576=
|
Describes the system components and functionality of the MGX 8250 Edge Concentrator from a technical perspective.
|
Cisco VISM Installation and Configuration Guide, Release 3
OL-2521-01 (online only)
|
Describes how to install and configure VISM in several MGX 8000 Series switches. This guide is available online only.
|
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1
DOC-7812278=
|
Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (Release 1), Software Version 1.2.10 (PXM1)
78-14247-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
MGX 8230 Edge Concentrator Release 1.2.10
The documentation for the installation and operation of the MGX 8230 Edge Concentrator is listed in Table 27.
Table 27 MGX 8230 Edge Concentrator Documentation
Title
|
Description
|
Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3
DOC-7811215=
|
Provides installation instructions for the MGX 8230 Edge Concentrator.
|
Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3
DOC-7811211=
|
Provides detailed information on the general command line interface commands.
|
Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3
DOC-78112113=
|
Provides error message descriptions and recovery procedures.
|
Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3
DOC-7812899=
|
Provides a technical description of the system components and functionality of the MGX 8250 Edge Concentrator from a technical perspective.
|
Cisco VISM Installation and Configuration Guide, Release 3
OL-2521-01 (online only)
|
Describes how to install and configure VISM in several MGX 8000 Series switches. This guide is available online only.
|
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1
DOC-7812278=
|
Describes how to install and configure the MGX Route Processor Module (RPM/B and RPM-PR) in the MGX 8850, MGX 8250, and MGX 8230 Release 1 switch. Also provides site preparation, troubleshooting, maintenance, cable and connector specifications, and basic Cisco IOS configuration information.
|
Release Notes for Cisco MGX 8230, MGX 8250, and MGX 8850 (Release 1), Software Version 1.2.10 (PXM1)
78-14247-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for Release 1.2.10 and Release 3
78-14243-01
|
Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
|
Obtaining Documentation
The following sections explain how to obtain documentation from Cisco Systems.
World Wide Web
You can access the most current Cisco documentation on the World Wide Web at the following URL:
http://www.cisco.com
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Ordering Documentation
Cisco documentation is available in the following ways:
•Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:
•http://www.cisco.com/cgi-bin/order/order_root.pl
•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:
•http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Obtaining Technical Assistance
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
Cisco TAC Web Site
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the Cisco WAN Switching publications.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Feedback
