Table Of Contents
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.1.20
These release notes are Part Number OL-7277-01 Rev I0, March 2007
Table of Contents
These release notes contain the following sections:
About Release 5.1.20
Version .202 of Release 5.1.20 is a patch release that does not introduce new features. The resolved anomalies for Version .202 are listed in Table 10.
The following versions of MPSM software on Cisco.com have been updated to include resolved anomaly CSCeh12738:
•MPSM-16-T1E1—From .200 to .202
•MPSM-16-T1E1-PPP—From .201 to .202
•MPSM-T3E3-155—From .200 to .202
The MPSM-16-T1E1-PPP software on Cisco.com was updated from version .200 to version .201 to include resolved anomalies CSCej17823 and CSCej62559. See Table 12 in the "Resolved Anomalies in Release 5.1.20" section.
These release notes describe the system requirements, new features, and limitations that apply to Release 5.1.20. These notes also contain Cisco support information. Release 5.1.20 is a software and hardware release for the following Cisco MGX switches:
•MGX 8830 (PXM1E)
•MGX 8830/B (PXM45)
•MGX 8850 (PXM1E and PXM45)
•MGX 8850/B (PXM1E and PXM45)
•MGX 8950 (PXM45)
Locating Software Updates
Release 5.1.20 software is located at the following URL:
RPM IOS images are located at the following URL:
Features in Release 5.1.20
This release supports Evolution-Data Optimized (EV-DO) traffic on the MPSM-16-T1E1. EV-DO is a high-speed data overlay for CDMA2000, where the MGX 8850 operates as the aggregation node:
Features in Release 5.1.00
This section contains the descriptions of the following new features in Release 5.1.00:
The MPSM-16-T1E1 is a single-height front card that accommodates one single-height back card and fits into a slot in the upper or lower bay of the following chassis systems:
•MGX 8850 and MGX 8850/B switches
•MGX 8830 and MGX 8830/B switches
The MPSM-16-T1E1 front card supports 16 ports with T1/E1 capabilities, depending upon which back card is installed. Each line can be channelized or unchannelized.
Limitation: Consolidated Link Layer Management for Frame Relay is not supported in this release.
The MPSM-16-T1E1 supports two software modes:
•ATM and Frame Relay services
•Multilink PPP services only
You boot into one mode or the other during initial card startup.
This section lists the features that are supported on the MPSM-16-T1E1 card.
The following services are supported:
•Inverse Multiplexing for ATM (IMA)
•Any Service Any Port
The MPSM-16-T1E1 card supports the following general features:
•Physical interfaces which are configured as channelized or unchannelized ports for 16 T1 or E1 interfaces
•Fault management and performance management for T1 and E1 interfaces
•1:1 hot standby card redundancy (requires 1:1 redundancy back cards and Y-cable)
•1:N cold standby card redundancy (requires 1:N redundancy back cards and RCON connector)
•Standard Cisco MGX RAS features
•Onboard BERT support for NxDS0 and T1/E1 interfaces
•Any Service Any Port (ASAP)
•Optional software features enabled through feature licenses
•SPVCs, SVCs, SPVPs, and PVPs
•Card and port service class templates
•Maximum of 2000 connections (any combination of Frame Relay and ATM connections)
•FR-FR, FR-ATM, ATM-FR, ATM-VISM, and ATM-CE SPVC connection types, where one of the end-points resides on the MPSM-16-T1E1 card
•Connections provisioned on the PNNI control plane on the MGX 8850 platform using the MSF switch architecture based Virtual Switch Interface (VSI)
•Provisioning XPVC endpoints
•OAM fault management
•Statistics collection and upload to Cisco Wan Manager (CWM)
•Configuration upload to CWM
The MPSM-16-T1E1 card supports the following ATM features:
•Handles up to 16 T1/E1 worth of ATM traffic
•T1 and E1 ATM interfaces
•VPCs and VCCs
•Egress VC Shaping
•ABR VS/VD with support for external ABR segment
•ILMI on all ATM interfaces
•Maximum of 32 ATM UNI/NNI/VUNI/VNNI/EVUNI/EVNNI ports with signaling
•Maximum of 2000 ATM connections
•ATM traffic management features (includes ABR VS/VD)
The MPSM-16-T1E1 card supports the following IMA features:
•IMA Version 1.0 and 1.1 with fallback and auto restart support
•Up to 16 IMA groups
•Both T1 and E1 IMA links (T1 and E1 cannot be mixed in the same IMA group.)
•Maximum of 8 links per IMA group
•Differential delay supported is 275 ms for T1 and 220 ms for E1
•CTC and ITC clocking modes supported
Frame Relay Features
The MPSM-16-T1E1 card supports the following Frame Relay features:
•Handles up to 16 T1/E1 worth of Frame Relay traffic
•Ports added on T1/E1 lines or NxDS0 channels in T1/E1 lines
•Maximum Frame Relay port bandwidth is 1.984 Mbps (E1 line with 31 timeslots)
•56 Kbps ports
•Total of 496 Frame Relay logical ports (16 x 31 timeslots in E1)
•Maximum of 2000 Frame Relay connections
•FR UNI, FR NNI, and Frame Forwarding interfaces
•Ingress cut through mode of frame processing (Waiting is not required for the complete frame to arrive. Frame processing and conversion to ATM cells starts as soon as header information is available.)
•Maximum frame size supported is 4510 bytes
•Two-byte Frame Relay header
•Ratio based egress servicing
•FRF.5 (NIW) and FRF.8.1 (SIW) standards
•LMI and Enhanced LMI on all Frame Relay interfaces
•Frame Relay traffic management features
The MPSM-16-T1E1 card supports the following Mulitlink PPP (MLPPP) features:
•PPP and MLPPP
•PPPmux on a MLPPP bundle basis
•Interworking between PPP and PPPoATM
•Maximum of 16 MLPPP bundles
•Maximum of 4 PPP links per MLPPP bundle
•Dynamic (auto) PVC bandwidth on a MLPPP bundle basis
•NxDS0 and T1/E1 PPP links
•1 PPP link per physical line
•Layer 2 QoS to minimize delay of delay sensitive traffic and prioritize control messages
•Four strict priority queues
•CDMA2000® applications with the MWR 1900 and the RPM-XF
•1:N cold standby front card redundancy
•Connections provisioned on the MGX 8850 PNNI control plane using the MSF Switch architecture based Virtual Switch Interface (VSI)
•Licensing of the supported features
Multilink PPP Feature for CDMA2000 and EV-DO
The MPSM-16-T1E1 implements Multilink PPP, which is a key protocol in a larger application defined by CDMA2000. In this application, the MGX 8850 (PXM45) aggregates traffic from several BTS site routers (MWR) and transfers that traffic to an IP network. The aggregation point in the MGX 8850 (PXM45) is the RPM-XF. Traffic from all of the BTS routers are transported over PPP links (typically on T1/E1 links) and brought into the MGX 8850 (PXM45) through an MPSM-16-T1E1 card. The MPSM-16-T1E1 transforms the PPP payload into AAL5 cells, which it sends to the RPM-XF using ciscoPPPoAAL5 encapsulation.
With growth in traffic in the CDMA2000 application, you might need to add additional T1/E1 links between the MWR and the MPSM-16-T1E1. The MLPPP feature simplifies the process of adding incremental bandwidth because it can aggregate capacity of individual T1/E1 lines. Because the IP payloads are small (typically voice) and the overhead associated with PPP (MLPPP) packets increases with smaller payloads, PPPMUX functionality is utilized on the MPSM-16-T1E1. In EV-DO, multiplexing is not utilized.
The connection between MPSM and RPM-XF is setup as a PVC connection. The bandwidth of this PVC depends on the number of operation PPP links on an MP bundle. RPM-XF terminates the PPPoAAL5 data and routes the IP traffic to the backbone IP network.
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
The online diagnostic tests run on regular intervals for both on the active and standby state of the MPSM cards to check the health of the devices and data paths. The online diagnostics test the following devices and data paths:
•Data path from the CPU on the MPSM to the CBC slave loopback on the MPSM via Winpath 0
•Data path from the CPU on MPSM to the CBC master loopback on the PXM via Winpath 1
•Winpath memory access test (packet, parameter, host memory)
•Write/read memory access test for internal devices
•Validate front card NVRAM checksum
•Validate flash checksum
PNNI Current Route Feature
Current Route feature provides the path information for active Point-to-Point (P2P) SPVCs/SPVPs master-end connections. The path information contains the lowest level physical node and egress trunk information of the path on which the connection is currently routed.
This feature utilizes the ATM standards based connTrace message to obtain the current route information. CWM uses the configuration upload file mechanism to request available path information of connections on a periodic or an on-demand basis.
This feature works in single peer group and multiple peer group networks. The current path can be used by the network administrators and planners to engineer the trunk usage and to direct how connections should be routed.
Operational and Redundancy Limitations
The current route feature has the following operational limitations:
•Point-to-multipoint calls are not supported.
•Only SPVC/SPVP connections are supported. CWM does not manage SVC/SVP connections.
•Master ended connections have the current route information. Slave ended connections do not have this information.
•The configuration upload file contains a snapshot of the current route information at the time that the switch receives a configuration upload request from CWM. Therefore, the snapshot might not contain the latest information, and connection trace information that the switch receives after the file is created is not included in the file.
•If congestion occurs on a node, the connTrace message sent by the CLI and by the Current Route feature is dropped. The two connTrace messages are not distinguishable. This limitation also applies to connTrace ACK messages that are received on a congested node.
•After changing a node ID, disable and then re-enable the current route feature on each node in the network using the new CLI command, cnfndcurrte.
This command flushes all existing current route information and starts collecting new information. After disabling the current route feature, wait at least 9 seconds (the time-out period for a connTrace message) before re-enabling it. This inhibits processing of stale connTrace messages.
•The connection path information for a connection traversing more than 20 nodes is not stored in the current route path table. Therefore, such connections do not have current route information.
•The current route path does not include the destination termination port (normally slave endpoint UNI port). The destination port is set to zero in the current route path, which is similar to preferred route.
The current route feature has the following redundancy limitations:
•The current route feature provides redundancy. However, because the current route must not reduce routing performance, some connections might not have redundant current route information on the standby PXM.
For those connections that do not have redundant current route information at the time of a switchcc, their current route information is obtained through the normal scanning on the active card when the old standby becomes the new active.
•After a standby PXM card is inserted and reset, the active card sends the current route information to the standby card only after its state changes from Init to Standby. This avoids increasing the time it takes for the redundant card to come up to the Standby state, ready for switchcc.
The Standby state is not redundant until the current route update is completed. Therefore, a switchcc that occurs before all current route information is sent to the redundant card results in some connections not having current route information on the newly active card. The current route information for those connections is obtained during the normal current route scanning and processing.
•When inserting or resetting the standby PXM, enter the command dspndcurrte and verify that Bulkupdate is complete before performing a switchcc.
The current route feature has the following limits:
•A maximum of 10K path entries per node are supported.
•A maximum of 5K node ID entries per node are supported.
•A maximum of 2K ports on PXM1E systems are supported when current route is enabled.
An attempt to enable the current route feature on a node which has more than 2K ports is not allowed and results in error. If the current route feature is enabled and more than 2K ports are subsequently added, this feature or other applications might not work properly.
•A maximum of 100K connections are supported PXM45/B systems when current route is enabled.
An attempt to enable current route on a node which has more than 100K connections results in error. If the current route feature is enabled and more than 100K connections are subsequently added, this feature or other applications might not work properly.
PNNI Product Enhancements
The Link Selection enhancement adds new functionality to parallel links to which link selection criteria is provisioned to `minAW' (`minAWlinks'). This feature can be activated through the CLI. If these enhancements are not activated, the existing `link selection' behavior preserves.
Table 1 lists the PNNI product enhancement requests incorporated in this release.
PXM1E OAM Enhancement
The PXM1E processes the following OAM loopback cells:
•End-to-end OAM loopback cells —Used for background connection continuity verification. These cells might be sent by a VISM card or router.
•Segment OAM loopback cells— Used for diagnostic testing between segment endpoints. These cells are sent for the following CLI commands: tstdelay, tstconsegep, and tstpndelay.
This release moves the task of extracting and injecting OAM loopback cells at the PXM1E from the Atlas to the QE1210. Unlike with Atlas, the QE1210 can distinguish between segment and end-to-end OAM loopback cells. The QE1210 extracts only the segment OAM loopback cells, while transparently passing the end-to-end OAM loopback cells.
Because the end-to-end OAM loopback cells no longer require software processing, the previous limitations for the OAM loopback cell rate on the PXM1E no longer apply. These cells are now processed in the QE1210 hardware and are limited only by the available line bandwidth.
Each PXM1E segment endpoint has a polling-induced queue extraction delay of up to 10 ms for a segment OAM loopback cell. This delay is not imposed on end-to-end cells or segment cells at non segment endpoints.
IP Management Connections through the RPM
You can manage the MGX 8850 node from the traditional Ethernet or console port, or you can set up one of the following connections:
•Through the AXSM or MPSM cards using an SVC to the PXM card
•Through the RPM card using a PVC to the PXM card
This release changes the PXM svcifconfig command to support management connections through the RPM card.
The IP addresses of hosts accessing the MGX 8850 node are stored in a RAM cache. Because this cache has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.
Use this solution to manage only one MGX 8850 node through RPM, not an entire network of nodes.
Note If you are connected to the MGX node using the RPM and accidentally delete the SPVC, the connection drops. To restore RPM access, you must re-add the SPVC using the console port or Ethernet port.
Note If the clrallcnf, clrcnf, or clrsmcnf commands are executed, the persistent data pertaining to the IP connections is lost and connections are dropped. To restore RPM access, you must reconfigure the RPM and PXM cards for IP connectivity, using the console port or Ethernet port.
This section describes software compatible with this release and lists the supported hardware.
Software/Firmware Compatibility Matrix
Table 2 lists Cisco WAN or IOS products that are compatible with Release 5.1.20.
MGX and RPM Software Version Compatibility Matrix
Table 3 lists the software that is compatible for use in a switch running Release 5.1.20 software.
SNMP MIB Release
The SNMP MIB release for 5.1.20 is mgx8850rel5120mib.tar.
Note SNMP manuals are replaced by the online MIB tool at URL http://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp
This section lists:
•MGX 8850 (PXM45) Product IDs, 800 part numbers, and revision levels
•MGX 8850 (PXM1E) Product IDs, 800 part numbers, and revision levels
•MGX 8830 Product IDs, 800 part numbers, and revision levels
•MGX 8950 Product IDs, 800 part numbers, and revision levels
This section also lists front and back card types, and whether APS connectors are supported for
•MGX 8850 (PXM45)
•MGX 8850 (PXM1E)
Hardware in Release 5.1.00
The following new hardware is introduced in Release 5.1.00.
•MGX 8850/B (PXM1E, PXM45/B, and PXM45/C)
Product IDs, Card Types, and APS Connectors
Table 4 MGX Chassis, Card, and APS Configurations Part 1
Front Card Type Min. 800 Part Number and Revision Back Card Types APSCon Min. 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830PXM1E MGX 8950PXM45
Also referred to as
1 APS connectors are required if an upgrade to a PXM1E-8-155 card without service interruption is required.
Table 7 MGX Chassis, Card, and APS Configurations Part 4
Front Card Type Min. 800 Part Number and Revision Back Card Types APSCon Min. 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830PXM1E MGX 8950PXM45
GLC-LH-SM (was MGX-GE-
GLC-SX-MM (was MGX-GE-SX1)
GLC-ZX-SM (was MGX-GE-ZX1)
1 APS connectors are not required in 8830 chassis.
2 The FRSM-12-T3E3 card is not supported.
Table 8 presents a guide on which APS connector to use with which MGX chassis and front card.
In these tables:
•R- means that this is a redundant card, for AX-R-RJ48-8E1, AX-R-RJ48-8T1, and AX-R-SMB-8E1 cards.
•Either of these connectors work for the AXSM cards in the MGX 8850 (PXM45) switch: MGX-8850-APS-CON or MGX-APS-CON.
•The PXM45 card is not supported in Release 5.0.00 and higher. The PXM45/B and PXM45/C cards are supported.
•The SCSI2-2HSSI/B card has two different 800 part numbers, and both part numbers are valid.
•The PXM1E-COMBO card is also known as PXM1E-T3E3-155 card.
MGX 8950 does not support the AXSM/A or the AXSM-E cards. If these cards are present, they will show up as "Failed" when the dspcds command is issued.
Table 8 APS Connectors Required for Each Chassis and Type of Front Card
Chassis Type MGX-APS-CON800-05307-01 MGX-8850-APS-CON800-20640-01-A0 MGX-8830-APS-CON800-05308-02 MGX-8950-APS-CON800-15308-01-A0
MGX 8850 (PXM45)
MGX 8850 (PXM1E)
1 Required only if running in OC-3 mode.
2 APS connectors are required if you want to upgrade to a PXM1E-8-155 card without interrupting service.
Limitations, Restrictions, and Notes for Release 5.1.20
This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.1.20.
PXM1E Switch Limitations
The following notes apply to PXM1E based switches—MGX 8850 (PXM1E) and MGX 8830:
•Y-red is not supported on the MCC Electrical back card.
•For inter-card APS to work on the PXM1E-8-155, and one front card is missing or not available, both back cards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.
•MPLS controller is not supported on PXM1E.
•PXM1E clock source is supported by VISM-PR, CESM, and AUSM cell bus service module cards. CESM and AUSM can provide one clock source, either primary or secondary.
•Only SPVCs and SPVPs are supported on cell bus service modules. SVCs are not supported on CBSMs.
•No bandwidth CAC support exists on the cell bus service modules, except for the RPM card, which is checked against the OC-3 card rate. For example, for a given RPM, the bandwidth allocated to all connections might not exceed the OC-3 rate. Bandwidth CAC is supported on the PXM1E uplink port.
•The maximum bandwidth to be distributed among cell bus service modules is approximately an OC-10 rate while traffic on the network interfaces on PXM1E can achieve true OC-12 line rate.
•Traffic must be balanced between the cell bus controllers to achieve the OC-10 rate. The traffic must be distributed equally at a rate of about OC-5 on the two cell bus controllers.
The cell bus controllers cannot load share to achieve OC-10 with one cell bus set at an OC-6 rate, and another cell bus set at an OC-4 rate.
Anything above OC-6 is dropped. However, if only one cell bus controller is used and the other cell bus controller is not used, then it can achieve an OC-10 rate. On an MGX 8850, the CBCs are split between the left and right side of the chassis: CBC0 supports slots 1-6 and 17-22 and CBC1 supports slots 9-14 and 25-30. On an MGX 8830, CBC0 supports slots 3,5,10, and 12 and CBC1 supports slots 4,6,11, and 13. Balance is achieved by planning the distribution of your cell base card by evenly distributing from the left side of the chassis and the right side of the chassis.
PXM1E Hardware Limitations
PXM1E hardware limitations are as follows:
•For inter-card APS to work on the PXM1E-8-155 with one front card missing or unavailable, both back cards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.
•During hardware upgrade from PXM1E-4-155 to PXM1E-8-155, at the time when the inserted card types are different (one PXM1E-4-155 card set and one PXM1E- 8-155 card set), the standby trunk back card functionality is not available. Therefore, LED functionality is not available, and APS lines do not work on that backcard. Modular optical transceiver (SFP-8-155) mismatches are not reported for that backcard, and SFP-8-155 mismatches are not reported during hardware upgrades.
•Because the PXM1E-4-155 and PXM1E-8-155 back cards support LC and SC interfaces respectively, the following restriction applies when upgrading from PXM1E-4-155 to PXM1E-8-155 hardware:
After replacing the first PXM1E-4-155 card with the PXM1E-8-155 card set, update cabling for the PXM1E-8-155 interfaces with an LC-SC converter.
Similarly, after the second card set is replaced, perform the same update for the interfaces on the new card set. Otherwise, the upgrade is not graceful and becomes service affecting, until appropriate cables are installed.
•When MGX-8850-APS-CON is used, and one trunk-backcard is removed, screw the remaining backcard in completely to ensure that the contacts are complete.
•When MGX-8850-APS-CON is used, the Combo card and the PXM1E-4-155 card do not require a mini-backplane, but the PXM1E-8-155 does. Therefore, to support graceful upgrade to the PXM1E-8-155 card in the future, insert a mini-backplane with the PXM1E-4-155.
PXM1E Reserved VCIs
You cannot provision the following reserved VCIs:
•On a feeder trunk, VPI.VCI 3.8 is reserved for inband communication with the feeder shelf, and 3.31 is used for the feeder trunk Annex.G ILMI.
•VPI = 0 and VCI = 5 are used for SSCOP for UNI signaling ports.If the port is configured for non-signaling (univer = none), no VPI/VCI is reserved.
•VUNI uses configured VPI and VCI = 5 for SSCOP.
•EVUNI uses minimum VPI and VCI = 5 for SSCOP.
•NNI uses VPI = 0, VCI = 18 for PNNI RCC.
•VNNI uses configured VPI for the port and the VCI = 18 for PNNI RCC.
•EVNNI uses minimum VPI and the VCI = 18 for PNNI RCC.
•VPI = 0 and VCI = 16 are used for ILMI if ILMI is enabled. VUNI and VNNI uses configured VPI for the port and VCI = 16 for ILMI. Similarly, ILMI for EVNNI or EVUNI uses a minimum VPI and VCI = 16.
•If MPLS is configured, VCI = 33 in the similar fashion as above.
•If NCDP is configured, minimum VPI and VCI = 34 for NCDP clocking.
•VPI = 0 and VCI = 31 are used for online diagnostics.
PXM1E Point to Multipoint Support
Point-to-multipoint connections support new real-time and non-real-time applications, for example LAN emulation, distance-learning, live broadcasts, financial data delivery (stock market feeds), white board collaboration, video conferencing, data and file replication, and video on demand.
Multipoint enhances network efficiency because multiple streams of data can be replaced by a single transmission up to the multicast distribution point, typically a MGX with PXM45. Point-to-multipoint differs from broadcast because it replicates packets only to specific destination endpoints in the multicast distribution tree.
The MGX 8830 (PXM1E) and MGX 8850 (PXM1E) can be used in conjunction with an MGX (PXM45) in a network to support point-to-multipoint connections. The PXM45 hardware performs cell replication to multiple destination endpoints. The MGX with PXM1E functions as the originating node or as an intermediate node of a point-to-multipoint connection. If necessary, MGX with PXM1E can perform limited branching or cell replication to support multiple parties, or leaves, of a point-to-multipoint connection.
Enabling cell replication or branching of more than two leaves per root in the PXM1E node is not recommended for mission-critical point-to-multiple connections because of potential ATM cell drops. Cisco plans to enhance the PXM1E embedded hardware in the future to support cell replication for higher root/leaves ratio with minimal cell drops.
PXM1E Parity Errors
The PXM1E handles parity errors as follows:
•If the PXM1E card has a CBC CBH RAM parity error and all connections do not have traffic, then the PXM1E card fails to detect this parity error and does not switch over to the standby card. Also, all service module cards reset.
•The PXM1E standby card comes up even after a QE TS RAM parity error.
PXM1E Policing Accuracy
The PXM1E card has a policing accuracy limitation. The policing rate is defined as 50000000/PCR, so if the PCR is comparable to the OC-12 line rate (1412830), the policing rate parameter is a relative small number (50000000/1412830 = ~35.38996).
Because the PXM1E performs integer division, the decimal results are truncated and the policing parameter is not calculated accurately. Moreover, the policing rate parameter is stored as an exponent (5-bits) and mantissa (9-bits), which cannot represent a small number accurately. Therefore, a 100% accurate policing parameter cannot be configured for large PCR values.
To ensure that you get the rate that you have specified, the software configures policing at the next larger rate that the hardware supports. For example, if you program a connection with PCR = 1400000, the software programs the actual policing rate to be 1428571. For a worse case scenario, if you configure a VBR2 connection with a PCR of 1400010 and the ingress user traffic is 1428570, there is no policing because the ATM policing device would police at rate 1428571 only.
PXM45 and PXM1E System Limitations
The following limitations apply to PXM45 and PXM1E systems:
•Because of granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured PCR rate when WFQ is enabled. For connections that have WFQ enabled, configure a PCR of 101% of the actual required rate. ABR has the same Qbin priority as UBR in the SCT tables. In this case ABR and UBR share excess bandwidth if WFQ is enabled.
•The percentage trunk utilization with overbooking is calculated using the following formula:
–(overbooked MaxCR - overbooked ACR) / overbooked MaxCR. This occurs when inter-operating with SES from Release 3.0.x and higher.
–ACR = MaxCR - (trunk utilization / overbooking factor).
–overbooked ACR = ACR / overbooking factor.
–overbooked MaxCR = MaxCR / overbooking factor.
•The overbooked ACR is calculated differently for MGX and SES.
–On MGX, the bandwidth for all current connections on the port are considered overbooked when calculating the trunk utilization.
–On the SES, the bandwidth for all current connections on the port are not considered overbooked when calculating the trunk utilization.
Therefore, the trunk utilization calculation is lower on the MGX than on the SES when there are existing connections on the port with an overbooking factor configured. This in turn yields a lower percentage trunk utilization on the MGX compared to the SES.
•The PXM45/A card is not supported in Release 5.0.00 and higher.
•Disable complex node for physical nodes (the lowest level node) to decreases memory usage without decreasing functionality. Complex node should only be turned on for logical nodes.
•Simple Network Timing Protocol CWM MIB is not supported.
Maximum Threshold Accuracy
The PXM45 and PXM1E have a limitation with the accuracy of the maximum threshold. The Qbin threshold and VI rate are stored in the form of exponent and mantissa, and some accuracy is lost in expressing the real rate. In testing the thresholds, the lack of accuracy is compounded with both of the Qbin and VI rate (draining rate). Therefore, you cannot calculate an exact 100% correct discard rate.
To ensure that you get the rate that you have specified, the software configures Qbin depth at the next larger rate that the hardware supports. As a result, Int. Cell Gap (ICG) and Relative Service Delay (RSD) are truncated.
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
These notes apply to redundant cards.
•Because of checks to prevent an inserted card from affecting the system, an additional step might be required when inserting two non native PXM45 (or PXM1E) cards in a shelf. Insert the first PXM45, use the clrallcnf command, and allow this to become active before inserting the second PXM45 (or PXM1E).
•After a clrallcnf, explicitly clean up stale SCT files (see anomaly CSCdw80282).
SPVC Interoperability Limitations
SPVCs have the following interoperability limitations:
•NNI SPVC Addendum Version 1.0 is not supported.
•PNNI 1.0 Addendum (Soft PVC MIB) is not supported.
•Terminating single-ended SPVCs on MGX switch with legacy service modules is not supported.
•Origination of single-ended SPVCs, with slavepers flag, from legacy service modules (FRSM, CESM and RPM) is not supported.
•CC (Continuity Check) is not available at the slave end of a single-ended SPVC.
•Reporting AIS detection to CWM is not available at the slave end of a single-ended SPVC.
•The tstdelay command is not available at the slave end of a single-ended SPVC for MGX 8850. For SES-PNNI, the command is available from the PXM even for the slave endpoint.
•The slave end of a single-ended SPVC is not visible to CWM.
•If single-ended SPVCs originate from MGX switches, they can only be configured from the CLI and not from CWM.
•Single-end provisioning is not supported for DAX connections as no value addition is seen for interoperability.
•SPVC statistics are not available for the slave endpoint of a single-ended SPVC because this endpoint is non-persistent.
•When the persistent slave endpoint of an existing SPVC connection is deleted and the master endpoint remains, the connection might get established as a single-ended SPVC connection. In this case, CWM shows the connection as Incomplete.
•Override of SVC connections on a VPI because of an incoming SPVP request for that VPI is not supported. Only the following override options are supported:
Service Card Limitations
This section describes service card limitations.
AXSM-16-155-XG with MCC Back Card Limitations
You might experience the following scenario when card to card APS is configured on one card but not the other:
The Protection Line Status in dspapslns or dspapsln shows OK if the other side has added the card redundancy and activated the line but not the APS. If the back cards are SFP back cards, the Protection Line Status is in SF in the same setup.
From CLI screen on the side of APS added, the only way to find out if the remote APS has been added is through the Receive chanfield and modefield in dspapsln. The following display shows the APS status during configuration:
Receive k2 chanfield - Null Channel
Receive k2 modefield - Undefined
After adding remote APS (with MCC):
Receive k2 chanfield - Null Channel
Receive k2 modefield - UNI1+1 or Bi depending on mode
For ITU (or AnnexA)
Receive k2 chanfield - Null Channel
Receive k2 modefield - Undefined
After adding remote APS:
Receive k2 chanfield - Null Channel
Receive k2 modefield - Undefined
Receive k2 chanfield - Null Channel
Receive k2 modefield - Undefined
After adding remote APS:
Receive k2 chanfield - Working Section 1 or 2
Receive k2 modefield - Undefined
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
The following notes apply to the AXSM-32-T1E1-E and PXM1E-16-T1E1 cards:
•IMA version fall back is part of IMA group operation. If a group is configured with version 1.1 and it is connected to a far end group which is configured with version 1.0, this group falls back to version 1.0.
•The IMA link Loss of IMA Frame (LIF) and Link Out of Delay Synchronization (LODS) defect integration times are configurable.
•ATM layer configuration for line and IMA ports takes an additional parameter, AIS enable. It is enabled by default.
•In T1 mode, payload scrambling is disabled by default and in E1 mode it is enabled by default on all lines and IMA groups.
•Only 10 SVC calls per second is guaranteed.
•FDL support for Loopback code detection is not supported.
•Far End Line Performance counters are supported only for E1. They are not supported for the T1 interface.
•HMM support is not available for the IMA and the Framer devices. When a switchover occurs, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.
•IMA Auto-restart (persistent RX IMA ID) feature is supported.
•IMA groups cannot have links from upper and lower bays together.
•ITC clocking mode on IMA is not supported.
•One-way transmission delay of more than 500 ms on the T1/E1 IMA links is not supported.
•There is 5 ms fluctuation on IMA delay tolerance.
•While the IMA group accumulated delay is being removed with clrimadelay, the following applies:
–Any changes to this IMA group configuration are temporarily blocked.
–Any changes in the FE IMA links in this group can cause the NE IMA group to restart.
•The VC and COSB thresholds are updated when the links are added/deleted from the IMA groups.
•The thresholds for the connections added when there are N links in the group can differ from connections added when there are (N+1) links in the IMA group.
•BERT is only supported on the T1 interfaces. BERT is not supported on E1 interfaces.
•The port number in the pnport (shelf.slot:subslot.port:subport) could be a random number. Do not interpret this number as line or IMA group number. Refer to anomaly CSCdy08500.
•PNNI requires SCR = 453 cells per second and PCR = 969 cells per second for the control connection.
•SSCOP requires of SCR = 126 cells per second and PCR = 2000 cells per second.
AXSM-E Card OAM Limitations
The following notes apply to AXSM-E OAM cells:
•Any connection can receive E2E/OAM loopback cells up to the line rate, as long as the policing policy permits it.
•The AXSM-E card can receive up to 1,500 segment OAM loopback cells per second for all connections operating in the normal mode (not loopback), assuming an even flow rate. Any excessive segment OAM loopback cells are dropped.
For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and each connection passes one segment OAM loopback cell per second, then only 1,500 of the connections can receive loopback cells at any given second. The additional 500 loop back cells are not received for that second.
General AXSM Card Limitations
If ER stamping is used, the rate interval does not provide sufficient accuracy to be completely effective. As a result, when an AXSM card has a PNNI link that is congested with mixed CBR/ABR traffic, cells are dropped. This condition only occurs when ER stamping is enabled and CI is disabled on an AXSM PNNI link where CBR/ABR traffic causes congestion on the link.
Use the CI/EFCI mechanism for rate feedback rather than the ER stamping mechanism, especially if CBR/ABR traffic is expected.
AXSM-XG Signal Level Limitation
The IR/LR/XLR SFP modules need a 10 db attenuator when connected with short cables. Otherwise, the signal overloads the receiver.
ATM Multicast Limitation
Configure an MGX 8950 with ATM multicast as follows:
•MGX 8950 system loaded with AXSM/Bs without AXSM-XG cards in the system
•MGX 8950 system loaded with all AXSM-XG based cards without AXSM/Bs in the system.
An MGX 8950 system with a mix of AXSM-XG and AXSM/B cards is not recommended for the ATM multicast application because of limitations in the backplane serial buses. The workaround for MGX 8950 systems that must have a mix of AXSM-XG and AXSM/B cards is to configure the PNNI node as branching restricted.cnfpnni -node 1 -branchingRestricted on.
Priority Bumping Limitation
When you enable priority bumping on the node, you cannot change the booking factor for AXSM signaling ports. You can still change the booking factor for non-signaling ports.
AXSM Card APS Limitations
Thee APS feature has the following limitations:
•For AXSM APS, the backcard of the active card must be present for correct APS operation.
•AXSM front cards need the corresponding backcard for correct APS operation. In other words, the AXSM cards do not support cross backcard removal—the upper backcard of one AXSM and lower backcard of another AXSM.
•If you remove the upper backcard of the active front AXSM, it triggers an active card switch. At this point the APS is still operational. However, if the lower backcard of the current active AXSM is removed, it will not trigger switching because the standby card is missing the backcard.
•Port LED lights on AXSM-E, AXSM-XG and PXM1E front cards indicate the receive status of physical line connected to it only when the card is in the active state. For a standby AXSM-E, AXSM-XG, and PXM1E card, the LEDs always remains green when the lines are in LOS irrespective of which lines are active.
MPSM Card Limitations
The MPSM cards have the following limitations:
•The MPSM-T3E3-155 card does not support the LMI Autosense feature.
•If a combination of RPM-PR and MPSM-T3E3-155 cards are being installed in slots served by the same cell bus, then enable Option 10 of cnfndparms (auto clock rate setting) before installing the MPSM-T3E3-155 and RPM-PR cards. This note applies when two RPM-PR cards or two MPSM-T3E3-155 cards (or one RPM-PR and one MPSM-T3E3-155 card) are inserted into slots under the same cell bus master, for example, slots 5 and 6 or 3 and 4.
•The MPSM cards are cell bus based cards, and they have limitations that suggest only a few of these cards could be used in a chassis when running at full port rate.
In reality, the full port rate available is rarely used. Statistical multiplexing of traffic across many ports can allow overbooking of the cell bus capacity just as it allows overbooking of trunk capacity. Estimates on how much overbooking is practical without dropping cells relies on the network's characteristics, such as the mix of service types, port speeds, and offered traffic loads as a percentage of port speed or as generated cell rates. Work with your Cisco Customer Engineering representative to help you characterize the quantity of MSPM cards suitable for your network.
•If you order MPSM cards with systems, the MPSM license(s) will be shipped on the PXM card. For more information, refer to MPSM Licensing section of the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1.
MPSM-16-T1E1 Card PPP Limitation
On the RPM-XF, Rated Priority Queue is not supported; SAR based QoS is enabled instead. The traffic on priority queue can exceed the limit even if the class-based weighted fair (CBWF) queues are relatively free. RPM-XF supports absolute priority only, where the upper limit on the traffic is layered using the policing command.
CBSM Card Limitations
Cell Bus Service Modules (CBSM), formerly known as narrowband service modules, have the following limitations:
•When switchredcd is entered at the same time as a PXM switchover occurs, either through the switchcc/resetcd command at the PXM or because of a failure, the switchover can fail.
Conditions: switchredcd is entered at the PXM command line to perform CBSM Switchover, but the PXM switches over (manual or automatic) before the service module switchover is complete.
Symptom: Service module did not switchover after switchredcd.
If the PXM switches over before the CBSM switchover completes, the following can occur:
–The switchover might not be complete and the standby card is in an indeterminate state. The dspcd command from PXM still shows it as 'standby' and later switchover (because of active service module removal or reset) fails, causing loss of traffic. The switchredcd command also fails.
–The switchredcd from PXM again causes the failure because the standby service module is not able to allocate memory.
Workaround: Reset the standby service module card.
•Each CBSM has the following maximum number of connections:
–FRSM-8 = 1,000
–FRSM-2CT3 = 4,000
–FRSM-2T3 = 2,000
–FRSM-2E3 = 2,000
–CESM-8 = 248
IGX Feeder Limitation
After adding an IGX as a feeder to a SES/BPX or MGX node, the IGX has a default node number that might not be unique within the network. If the number is not unique, modified it to a unique node number by entering rnmnd <x>, where x is unique with respect to all other AutoRoute nodes. To find the other node numbers, enter dspnds +n. Failing to assign a unique number could cause the CWM Databroker to incorrectly form hybrid connection database. The CWM GUI might show the connection as incomplete.
Clock Source Limitations
Service modules have the following clock source limitations:
•The AUSM card supports one clock source only. Attempts to configure the secondary clock fail silently.
•The FRSM card does not support clock source configuration. If a clock source is configured on FRSM, it is not be reflected in the database.
•When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. Recommitted means that the primary and secondary get requalified. The node temporarily uses the internal oscillator until the clock is requalified, and then locks onto the primary clock source again.
Clearing Card Configuration Notes
The clear service module configuration feature has the following behavior:
•Cisco does not recommend executing clrsmcnf on more than one card at a time
•If a controller card switchover occurs before the clear service module configuration operation is complete, the clrsmcnf command must be re-entered to ensure that the configuration is completely cleared and to avoid incomplete cleanup.
•The clrsmcnf command might result in discrepancy in the PNNI configuration. For example, some connections might be in the mis-match state.
•If the clrsmcnf command is entered with the <all> option to clear the software version for the slot as well, then cell bus service modules go into the boot/empty state and broadband service modules (for example, AXSM or MPSM-155-T3E3) go into the fail/active state.
•After entering the clrsmcnf command, the card in the specified slot is not usable until the operation has successfully completed.
This section describes limitations to PNNI links and routing.
Logical Link Limits
The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is enabled. The limit is essential to reduce the processing time involved in finding the bypasses between the logical links. Whenever a significant change occurs in bandwidth in one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually found from one logical link to another.
If there are n logical links, the calculation involves the finding n*n bypasses. If the number of logical links n is large, calculating the bypasses requires significant processing resources. The number of logical links can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.
Preferred Route Limitations
Preferred routes have the following limitations:
•Preferred routes are not supported for connections with endpoints on the RPM-PR.
•Upgrading a preferred routing from any Release 3.0.x is non-graceful. During the upgrade, the preferred route identifier information for each connection is lost, and the preferred route identifier must be reprovisioned on the service module cards.
Also, the preferred route table at the PXM controller is lost. Connections that have already been routed with preferred routing remain, and no alarms for these connections occur. If a node in the PNNI network is removed by physical decommissioning and if any nodes in the network had preferred routes that contained the removed node as one of the hops, you must manually delete and modify the preferred route(s).
•When a connection is routed on a route other than its preferred route and if the preferred route becomes available, the connection is not automatically routed back to its preferred route. You must deroute and reroute using configuration commands (optrte, rrtcon, dncon/upcon, and so on). QoS precedence over the preferred route does not apply to multi-peer group networks (CSCdz40310).
•A preferred route configured with a higher node ID cannot be blocked (CSCdz41145, CSCdz49001). Because of differences in physical port numbering, non-MGX nodes can only be the terminating nodes in a preferred route.
•Preferred route status is supported in Release 5.0.00 and up. After an upgrade, manually reconfigure using commands like cnfcon. This step is only needed only once after the upgrade, and does not need to be repeated on subsequent upgrades.
Priority Route Limitations
Priority routing has the following limitations:
•Prioritized reroute of SPVCs is not guaranteed if the SPVCs originate on a signaling port. SPVCs might get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports only.
•The RPM does not support configuration of routing priority. The PXM assigns a priority of 8 to all RPM-mastered SPVCs.
•The addcon command on SES does not support routing priority; all added SPVCs are assigned a routing priority of 8. Use the cnfcon command to change the routing priority of the SPVCs.
•Changing the routing priority for DAX connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if only the endpoint parameters are changed, and routing priority is an end-point parameter. Also, because DAX connections are never derouted even when the UNI port goes down and the rrtcon command does not support DAX connections, the routing priority change never gets reflected. The only way to reflect this change is to enter a dncon and then upcon. Because DAX connections are never derouted, the effect of this limitation is void.
•Priority routing operates in a best effort manner for the following reasons:
–Two in-order releases can still arrive out of order at the master node if they take two different paths.
–Under congestion, releases can be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the congested interfaces. The calls that were not released could be higher priority calls.
•Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can occur after several failed attempts to route higher priority SPVCs. To prevent starvation of lower priority SPVCs after these failures, software starts to route lower priority SPVCs and postpones higher priority SPVCs routing.
Persistent Topology Limitations
The persistent topology feature has the following limitations:
•In a mixed network of pre-Release 4.0.00 and 4.0.00 or later nodes, only the node name and the node ID are shown for a pre-Release 4.0.00 node in the Topo DB. This is because the feature is not present in pre-Release 4.0.00 nodes.
•If a peer group is made up of physical nodes with pre-Release 4.0.00 logical nodes, the information for the logical node is stored in the Topo DB. This is because there is no way to distinguish between physical nodes and pre-Release 4.0.00 logical nodes. Logical nodes with Release 4.0.00 or later software release are not stored in the Topo DB.
•To delete a node information entry from the Topo DB, first remove the node from the network, either by disconnecting the cables or by downing all the links between that node and the network. Wait for an hour. Then, delete that node from the Topo DB. This is done because, even if a node is removed from the Topo DB of all nodes in the peer group, its PTSEs are still stored in the other nodes until they are flushed from those nodes. This would happen within an hour's time, but it is configurable as a PNNI timer value. If the node is deleted from the Topo DB within that hour's time, and the node does switchcc/reboot, then it's possible that the node info for that deleted node will be added back into the Topo DB.
•When the node ID of a node is changed, the old node ID is added back into the Topo DB as a new node entry. In addition, the old node ID still is stored in the Topo DB of all the other nodes in the peer group. To delete this entry, wait for an hour so that the PTSEs with the old node ID is flushed from the DB of all the nodes in the peer group. Then, delete the information of the old node ID from the Topo DB.
•It is possible that the gateway nodes are not in sync in a peer group, and this could happen in many situations. For example, a gateway node is added in a peer group, then a node is deleted from the PG, and another gateway node is configured, then the info for the deleted node would not be in the second gateway node. Another example is that a node is deleted from one gateway node, but not in another gateway node.
When deleting a node from the peer group, the node info must be deleted from all the nodes in that peer group, even the non-gateway-node nodes. Otherwise, the node info for that deleted node will still be in the non-gateway-node nodes. This could cause inconsistencies later if this node is configured to be a gateway node.
Fault Isolation and Trace Limitations
This section describes fault isolation and trace limitations.
Serial Bus Path Fault Isolation Limitation
The Serial Bus Path Fault Isolation feature isolates errors on local cards only. However, when a common error occurs on the switching fabric card, this feature does not resolve the error. As a result, a problem on the PXM card or the XM-60 is reported by all cards that detect the symptoms of this problem.
Cell Bus Path Fault Isolation and Recovery Limitations
Cell bus path fault isolation has the following limitations:
•The isolation procedures can isolate the cell bus path in the serial bus service modules (for example, AXSM, AXSM/B, AXSM-E,) and all communication with the standby controller card and the cell bus service modules (for example, FRSM, CESM). These procedures cannot isolate cell bus path failures involving the ATMizer SAR, which is used for all inter-card communication except polling, between the active controller card and the serial bus based service modules.
•The isolation procedures can isolate the cell bus path failures to the active controller card only. This isolates the active controller card faults for the inter-card communication over the cell bus from the active controller card to the service modules and the standby controller card. It does not isolate the fault if the active controller card fails to communicate with some cards and successfully communicates with the rest on the cell bus.
•At least two cards (two service modules or one service module and one standby PXM) must exist to isolate cell bus path failures to the active controller card.
•Only failures that are detected by periodic polling trigger the isolation procedures. Failures reported from other sources in the system about a service module or the standby controller card, due to the cell bus path failures, do not initiate the isolation procedures. Such failures reset the card for which the failure is reported, even while the active controller card is in the process of isolating the cell bus path failures triggered by the polling failures.
•No separate trap or alarm is generated for the active controller card cell bus path when the fault is isolated to the active controller card. Use the event logs to investigate events triggered by the card reset and/or switchover traps.
•If controller card redundancy is unavailable, isolating the cell bus path failure to the active controller card results in outage. The active controller card is reset.
Path and Connection Trace Notes
The path and connection trace features have the following limitations:
•Path trace is not supported on the control port.
•Path trace does not have the accurate information when there is a crankback on the connect path.
•Path and connection trace after Release 3.0.00 is not compatible with the path and connection trace available with previous releases.
•Path and connection trace supports point to point connections.
•Path and connection trace supports MPG (multi-peer group) and SPG (single-peer group).
CLI Access Level Notes
Configuration of CLI access levels has the following limitations:
•Not all CLI command access levels can be changed and a command cannot be changed to CISCO_GP group access level.
•Only the switch software can generate the access level binary file. This file has an authentication signature which has to be validated before the file can be used. Any manual changes to the file make the file void.
•If the binary file becomes corrupted, then the command access levels revert back to the default values during the card bring-up. To recover, repeat the installation process or retain a copy of the binary file and do cnfcli accesslevel install on that service module.
•Command names are verified, but an invalid command name might be parsed and be added to the binary file. However, this invalid name is ignored later.
•If replication to standby failed, the installation process failed.
The cnfcli accesslevel default command restores all command access levels to default for the service module on which the command is executed. This command does not remove the binary file, so this change is not persistent. If the command is executed on the active card of a redundancy pair, the standby card is not affected. When the card is reset and the binary file exists, it will configure from the binary file when it is brought up.
Disk Space Maintenance Notes
The firmware does not audit the disk space usage and remove unused files, so you must manually manage the disk space in C: and E: drives.
Manually delete unused saved configuration files, core files, and firmware files and the configuration files of the MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards. This avoids a shortage of disk space for storing event logs.
Too remove files from the active controller card:
Step 1 Change to the directory that needs grooming.cc <directory_name>
Step 2 List the directory to identify old files that can be removed and available disk space.ll
Step 3 Remove any old files (you may also use wild cards in the filename).rm <complete_filename>
Step 4 List the directory to see if the file has been removed and disk space is available.ll
Non-native Controller Front Card and PXM-HD Card Notes
The following notes pertain to non-native front card controllers and the PXM-HD card:
•When the front controller cards or the PXM-HD back cards are swapped within the same system, the system performs a non-native card check. As a result, the controller card that attempts to come up as Active/Active might get reset twice.
•When a non-native PXM1E front card or a PXM-HD card is inserted into the standby controller slot, after the standby controller front card becomes Active/Standby, the active controller front card copies its hard disk content over to the standby controller card. The active controller front card does not automatically remove hard disk content from the active or standby controller card.
•The system keeps only the two most recent copies of the saved system configuration in the C:/CNF directory. You can use FTP to transfer all the saved configuration files in C:/CNF to a local server for future reference. All files under C:/CNF are not replicated to the standby controller card under any circumstances.
Other Limitations and Restrictions
Other limitations and restrictions are as follows:
•When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit will be that the VPI value must be within the UNI ATM header limitations.
•If command clrchancnt is executed while a dspchancnt command is currently active, the data displayed is incorrect. Restarting the dspchancnt after the previous one has completed displays correct data.
•The clrsmcnf command does not work for redundant service modules.
•The clrsmcnf does not work if an upgrade is in progress.
•If RPM-PR or RPM-XF is configured as a Label Switch Controller (LSC), execution of clrsmcnf command on those LSC slots is rejected.
•Configuration information is not synchronized between PXMs during upgrades. If any changes are made to the configuration during upgrades, the standby PXM must be rebooted. The standby PXM must be rebooted when it is in a stable state.
•The maximum number of connections supported in Release 3.0.00 or later with PXM45/B is 250,000 connections.
•NCDP is not supported on BPX.
•When you clear the chancnt while you are monitoring the chancnt on the AXSM-XG, the counters return invalid values on the dspchancnt display (see CSCdz33652).
Installation and Upgrade Procedures
Upgrades to Release 5.1 and higher is only from 4.0.17 and higher.
For information on the following installation and upgrade procedures, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1.
The upgrade appendix in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1 contains the following procedures:
•Graceful PXM1E and PXM45 Boot Upgrades
•Non-Graceful PXM1E and PXM45 Boot Upgrades
•Graceful PXM1E and PXM45 Runtime Software Upgrades
•Non-Graceful PXM1E and PXM45 Runtime Software Upgrades
•Graceful Service Module Boot Upgrades
•Non-Graceful Service Module Boot Upgrades
•Graceful Service Module Runtime Software Upgrades
•Non-Graceful Service Module Runtime Software Upgrades
•Graceful RPM-PR and RPM-XF Boot Software Upgrades
•Graceful RPM-PR and RPM-XF Runtime Software Upgrades
•Non-Graceful RPM-PR and RPM-XF Boot Software Upgrades
•Non-Graceful RPM-PR and RPM-SF Runtime Software Upgrades
•Installing SCT Files
Upgrading AXSM-XG Cards
The following notes apply to AXSM-XG card upgrades:
•When installing AXMS-XG cards into a node that has a release earlier than Release 4.0.15, all of the other cards in the node must be upgraded first to Release 5.0.
•When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, or EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header limitations.
Upgrading the VISM-PR Image
If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
The upgrade appendix in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1 contains the following procedures:
•Replacing PXM1E-4-155 cards and with PXM1E-8-155 Cards
•Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards.
Anomalies in Release 5.1.20
This section contains the known, resolved, and changed status anomalies in Release 5.1.20.
Known Anomalies in Release 5.1.20
Table 9 lists the known anomalies in Release 5.1.20.
Resolved Anomalies in Release 5.1.20
Table 10 lists the anomalies that are resolved in Version .202 of Release 5.1.20.
Table 10 Resolved Anomalies in Version .202 of Release 5.1.20
Offline Diag fails for PXM45C H2 boards.
Table 11 lists the anomaly that is resolved in MPSM-16-T1E1, MPSM-16-T1E1-PPP, and MPSM-T3E3-155 version .202 of Release 5.1.20.
Table 11 Resolved Anomaly in MPSM Version .202
Anomaly ID Description
Mask off byte 127 of packet memory I2C
Table 12 lists the anomalies that are resolved in MPSM-16-T1E1-PPP version .201 of Release 5.1.20.
Table 12 Resolved Anomalies in MPSM-16-T1E1-PPP .201
Anomaly ID Description
PPP link flap during the PXM upgrade prevents graceful upgrade
OSPF flaps observed after runrev with traffic going on the PPP links
Table 13 lists the anomaly that is resolved in PXM45/PXM1E version .201 of Release 5.1.20.
Table 13 Resolved Anomaly in PXM45/PXM1E Version .201
Anomaly ID Description
RPM-XF addred is blocked when RCON is present.
Table 14 lists the resolved anomalies in Release 5.1.20.
Status Changed Anomalies
Table 15 lists the anomalies that changed status but were not resolved in Release 5.1.20.
Resolved Anomalies in Previous Releases
This section contains the resolved anomalies in the following releases:
Resolved Anomalies in Release 5.1
Table 16 lists the anomalies that are resolved in Release 5.1.
Resolved Anomalies in Release 5.0.20
Table 17 lists the anomalies that are resolved in Release 5.0.20.
Resolved Anomalies in Release 5.0.10
Table 18 lists the anomalies that are resolved in Release 5.0.10.
Resolved Anomalies in Release 5.0.00
Table 19 lists the anomalies that are resolved in Release 5.0.00.
Known Route Processor Module or MPLS Anomalies
For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(11)T3 for PXM45-based Switches, Release 5.1.
For information about anomalies with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(11)T3 for MGX Releases 1.3.10 and 5.1.00.
A Guide to Cisco Multiservice Switch Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
You can access the most current Cisco documentation at this URL:
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
Product Documentation DVD
The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:
Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at email@example.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
From this site, you will find information about how to:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:
To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•For Emergencies only — firstname.lastname@example.org
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•For Nonemergencies — email@example.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
or view the digital edition at this URL:
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
•World-class networking training is available from Cisco. You can view current offerings at this URL:
Table 20 lists acronyms that have been referenced in these release notes.
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0601R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2006 Cisco Systems, Inc. All rights reserved.