Guest

Cisco MGX 8800 Series Switches

5.1.20 Release Notes for MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830

  • Viewing Options

  • PDF (941.2 KB)
  • Feedback
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.1.20

Table Of Contents

Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.1.20

Table of Contents

Overview

About Release 5.1.20

Locating Software Updates

Features in Release 5.1.20

Features in Release 5.1.00

MPSM-16-T1E1 Card

Operational Modes

Supported Features

Multilink PPP Feature for CDMA2000 and EV-DO

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics

PNNI Current Route Feature

Operational and Redundancy Limitations

Feature Specifications

PNNI Product Enhancements

PXM1E OAM Enhancement

IP Management Connections through the RPM

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Hardware Supported

Hardware in Release 5.1.00

Product IDs, Card Types, and APS Connectors

Limitations, Restrictions, and Notes for Release 5.1.20

PXM1E Switch Limitations

PXM1E Hardware Limitations

PXM1E Reserved VCIs

PXM1E Point to Multipoint Support

PXM1E Parity Errors

PXM1E Policing Accuracy

PXM45 and PXM1E System Limitations

Maximum Threshold Accuracy

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

SPVC Interoperability Limitations

Service Card Limitations

AXSM-16-155-XG with MCC Back Card Limitations

AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations

AXSM-E Card OAM Limitations

General AXSM Card Limitations

AXSM Card APS Limitations

MPSM Card Limitations

CBSM Card Limitations

IGX Feeder Limitation

Clock Source Limitations

Clearing Card Configuration Notes

PNNI Limitations

Logical Link Limits

Preferred Route Limitations

Priority Route Limitations

Persistent Topology Limitations

Fault Isolation and Trace Limitations

Serial Bus Path Fault Isolation Limitation

Cell Bus Path Fault Isolation and Recovery Limitations

Path and Connection Trace Notes

CLI Access Level Notes

Disk Space Maintenance Notes

Non-native Controller Front Card and PXM-HD Card Notes

Other Limitations and Restrictions

Installation and Upgrade Procedures

Upgrade Information

Upgrading AXSM-XG Cards

Upgrading the VISM-PR Image

Maintenance Information

Anomalies in Release 5.1.20

Known Anomalies in Release 5.1.20

Resolved Anomalies in Release 5.1.20

Status Changed Anomalies

Resolved Anomalies in Previous Releases

Resolved Anomalies in Release 5.1

Resolved Anomalies in Release 5.0.20

Resolved Anomalies in Release 5.0.10

Resolved Anomalies in Release 5.0.00

Known Route Processor Module or MPLS Anomalies

Documentation

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Acronyms


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

Overview

These release notes contain the following sections:

About Release 5.1.20

Features in Release 5.1.20

System Requirements

Limitations, Restrictions, and Notes for Release 5.1.20

Installation and Upgrade Procedures

Anomalies in Release 5.1.20

Resolved Anomalies in Previous Releases

Documentation

Obtaining Documentation

Documentation Feedback

Cisco Product Security Overview

Obtaining Technical Assistance

Obtaining Additional Publications and Information

Acronyms

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

See Table 11 in the "Resolved Anomalies in Release 5.1.20" section.

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.

The PXM45/PXM1E software on Cisco.com was updated from version .200 to version .201 to include the resolved anomaly CSCei67407. See Table 13 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:

http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml

RPM IOS images are located at the following URL:

http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml

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:

Multilink PPP Feature for CDMA2000 and EV-DO

Features in Release 5.1.00

This section contains the descriptions of the following new features in Release 5.1.00:

MPSM-16-T1E1 Card

PNNI Current Route Feature

PNNI Product Enhancements

PXM1E OAM Enhancement

IP Management Connections through the RPM

MPSM-16-T1E1 Card

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.

Operational Modes

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.

Supported Features

This section lists the features that are supported on the MPSM-16-T1E1 card.

Supported Services

The following services are supported:

Frame Relay

ATM

Inverse Multiplexing for ATM (IMA)

Multilink PPP

Any Service Any Port

General Features

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

ATM Features

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

ATM trunking

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)

VCC/VPC shaping

IMA Features

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

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

Feature Specifications

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.

Table 1 PNNI Product Enhancement Requests Incorporated 

PER ID
Description

PER 5672

SVCC-RCC connection configuration

This enhancement introduces a command (cnfpnni-svcc-rcc-param) to configure the connection parameters associated with SVCC-RCC connections at each level of the PNNI hierarchy.

PER 8281

Path bypass selection configuration

In a complex node multiple peer group topology, the path that has the highest available cell rate (AvCR) is advertised as the bypass. Typically this path has higher cost, so the calls routed over the pass bypass might always take the worst path. This enhancement adds an option to the cnfpnni-routing-policy command to specify the criteria for bypass path selection.

PER 8282

Administrative Weigh (AW) Pruning

Currently a trunk is included in the best path selection even if it has a single cell per second of AvCR. This enhancement introduces an AvCR threshold parameter to the cnfpnni-routing-policy command so that trunks with BW below the threshold are excluded from the best path search.

PER 8287

Consistent PNNI Link Selection

Allows application of the same link selection mechanism to connections of all service categories (ABR, UBR, CBR and VBR) on `minAW links'.

Allows provisioning `epsilon-equal AW parallel links' among the `minAW parallel links' between two switches. The switch calculates the `epsilon' value based on user inputs.

If `epsilon-equal AW parallel links' exist between two switches along the selected shortest path, `link selection' applies. For `epsilon-equal AW parallel links', the secondary `link selection criteria' is maxAvCR. If all links have the same AvCR, the connections are routed according to load balance criteria.

PER 8540

Preferred Route Enhancements

The cnfndidrtes command has a new parameter for indicating that the same node is being configured and that the preferred route status should not change. A connection that was on a preferred route before the change would not be groomed by route optimization.

PER 8660

Link Selection Enhancements for multi-peer group (MPG) Pref Rt Conns

PER 8807

Routing Policy Enhancements

This enhancement adds a parameter value to the cnfpnni-routing-policy command that selects from equal administrative weight (AW) paths using the number of minimum hops. If multiple epsilon-equal AW paths with the same minimum-hops exist, a second load balance parameter specifies the tiebreak criteria.


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.


System Requirements

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.

Table 2 Release 5.1.20 Compatibility Matrix 

Switch or Component
Compatible Software Version

MGX 8230 (PXM1)

MGX 8250 (PXM1)

MGX 8850 (PXM1)

MGX 1.3.12

MGX 1.3.11

MGX 8830 (PXM1E)

MGX8830/B (PXM45)

MGX 8850 (PXM1E and PXM45)

MGX 8850/B (PXM1E and PXM45)

MGX 8950 (PXM45)

MGX 5.1.20

MGX 5.0.20

MGX 4.0.17

BPX Switch Software

Switch Software 9.4.12

Switch Software 9.3.47

BXM firmware MFZ

Cisco WAN Manager

15.1.50

MGX 8220 Shelf

MGX 8220 5.0.20

SES PNNI

4.0.15

3.0.25

IOS RPM-PR

12.3(11)T6

12.3.(11)T4

12.3(7)T10

IOS RPM-XF

12.3(11)T6

12.3.(11)T4

12.3(7)T10


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.

Table 3 MGX and RPM Software Version Compatibility Matrix 

Board Pair
Boot Software
Runtime Software

PXM45/B

pxm45_005.001.020.201_bt.fw

pxm45_005.001.020.202_mgx.fw

PXM45/C

pxm45_005.001.020.201_bt.fw

pxm45_005.001.020.202_mgx.fw

PXM45/C MGX 8830/B chassis

pxm45_005.001.020.201_bt.fw

pxm45_005.001.020.202_m30.fw

PXM1E-4-155 MGX 8850 (PXM1E) chassis

pxm1e_005.001.020.201_bt.fw

pxm1e_005.001.020.201_mgx.fw

PXM1E-8-155 MGX 8850 (PXM1E) chassis

PXM1E-8-T3E3 MGX 8850 (PXM1E) chassis

PXM1E-COMBO MGX 8850 (PXM1E) chassis

PXM1E-8-155

PXM1E-4-155 MGX 8830 chassis

pxm1e_005.001.020.201_bt.fw

pxm1e_005.001.020.201_m30.fw

PXM1E-8-T3E3 MGX 8830 chassis

PXM1E-COMBO MGX 8830 chassis

AXSM-1-2488

axsm_005.001.020.200_bt.fw

axsm_005.001.020.200.fw

AXSM-16-155

AXSM-4-622

AXSM-16-T3/E3

AXSM-1-2488/B

axsm_005.001.020.200_bt.fw

axsm_005.001.020.200.fw

AXSM-16-155/B

AXSM-4-622/B

AXSM-16-T3/E3/B

AXSM-2-622-E

axsme_005.001.020.200_bt.fw

axsme_005.001.020.200.fw

AXSM-8-155-E

AXSM-16-T3E3-E

AXSM-32-T1E1-E

AXSM-16-155-XG

axsmxg_005.001.020.200_bt.fw

axsmxg_005.001.020.200.fw

AXSM-4-2488-XG

AXSM-1-9953-XG

MPSM-16-T1E1

mpsm16t1e1_005.001.020.200_bt.fw

mpsm16t1e1_005.001.020.202.fw

MPSM-16-T1E1-PPP

mpsm16t1e1_005.001.020.200.fw

mpsm16t1e1ppp_005.001.020.202.fw

MPSM-T3E3-155

mpsm155_005.001.020.200_bt.fw

mpsm155_005.001.020.202.fw

MPSM-8-T1E1

mpsm_t1e1_030.001.020.200_bt.fw

mpsm_t1e1_030.001.020.200.fw

MGX-SRME

N/A (Obtains from PXM)

N/A (Obtains from PXM)

MGX-SRME/B

N/A (Obtains from PXM)

N/A (Obtains from PXM)

SRM3T3/C

N/A (Obtains from PXM)

N/A (Obtains from PXM)

AX-CESM-8E1

cesm_8t1e1_CE8_BT_1.0.02.fw

cesm_8t1e1_022.001.020.200.fw

AX-CESM-8T1

cesm_8t1e1_CE8_BT_1.0.02.fw

cesm_8t1e1_022.001.020.200.fw

MGX-CESM-8T1/B

cesm_8t1e1_CE8_BT_1.0.02.fw

cesm_8t1e1_022.001.020.200.fw

MGX-AUSM-8T1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

ausm_8t1e1_022.001.020.200.fw

MGX-AUSM-8E1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

ausm_8t1e1_022.001.020.200.fw

AX-FRSM-8T1

frsm_8t1e1_FR8_BT_1.0.06.fw

frsm_8t1e1_022.001.020.200.fw

AX-FRSM-8E1

frsm_8t1e1_FR8_BT_1.0.06.fw

frsm_8t1e1_022.001.020.200.fw

AX-FRSM-8T1-C

frsm_8t1e1_FR8_BT_1.0.06.fw

frsm_8t1e1_022.001.020.200.fw

AX-FRSM-8E1-C

frsm_8t1e1_FR8_BT_1.0.06.fw

frsm_8t1e1_022.001.020.200.fw

MGX-FRSM-HS2/B

frsm_vhs_VHS_BT_1.0.07.fw

frsm_vhs_022.001.020.200.fw

MGX-FRSM-2CT3

frsm_vhs_VHS_BT_1.0.07.fw

frsm_vhs_022.001.020.200.fw

MGX-FRSM-2T3E3

frsm_vhs_VHS_BT_1.0.07.fw

frsm_vhs_022.001.020.200.fw

MGX-RPM-PR-256

rpm-boot-mz.123-11.T6

rpm-js-mz.123-11.T6

MGX-RPM-PR-512

rpm-boot-mz.123-11.T6

rpm-js-mz.123-11.T6

MGX-RPM-XF-512

rpmxf-boot-mz.123-11.T6

rpmxf-p12-mz.123-11.T6


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


Hardware Supported

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)

MGX 8830

MGX 8950

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)

MPSM-16-T1E1

RBBN-16-T1E1-1N

MCC-16-E1-1N

RED-16-T1E1

RCON-1TO3-8850B

Product IDs, Card Types, and APS Connectors

Table 4-Table 7 list part number and revision compatibility for front and back cards in the MGX chassis. The tables also list whether an APS connector is required.

Table 4 MGX Chassis, Card, and APS Configurations Part 1 

Front Card Type
Min. 800 Part Number and Revision
Back Card Types
APS
Con
Min. 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830
PXM1E
MGX 8950
PXM45

PXM45/C

800-20217-04-A0

PXM-HD

800-05052-03-A0

x

x

x

   

PXM-UI-S3/B

800-21557-01-A0

         

PXM45/B

800-09266-04-A0

PXM-HD

800-05052-03-A0

x

x

   

PXM-UI-S3

800-05787-02-A0

         

PXM1E-8-155

800-21686-05-A0

SFP-8-155

SMFIR-1-155-
SFP

SMFLR-1-155-
SFP

MMF-1-155-
SFP

Yes

800-21518-03-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

x

x

   

MCC-8-155

Yes

800-22117-02-A0

         
   

PXM-UI-S3/B

800-21557-01-A0

         

PXM1E-4-155

800-18588-03-A0

MMF-4-155/C

Yes 1

800-07408-02-A0

x

x

   

SMFIR-4-155/C

Yes 1

800-07108-02-A0

         
   

SMFLR-4-155/C

Yes 1

800-07409-02-A0

         
   

PXM-UI-S3/B

800-21557-01-A0

         

PXM1E-8-T3E3

800-18590-03-A0

SMB-8-T3

800-05029-02-A0

x

x

   

SMB-8-E3

800-04093-02-A0

         
   

PXM-UI-S3/B

800-21557-01-A0

         

PXM1E-16-T1E1

800-18658-04-A0

MCC-16-E1

800-19853-02-A0

x

x

   

RBBN-16-T1E1

800-21805-03-A0

         
   

PXM-UI-S3/B

800-21557-01-A0

         

PXM1E-T3E3-155

Also referred to as

PXM1E-COMBO

800-18604-03-A0

MGX-T3E3-155

SMFIR-1-155-
SFP

SMFLR-1-155-
SFP

MMF-1-155-
SFP

800-18698-02-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

x

x

   

PXM-UI-S3/B

800-21557-01-A0

         

1 APS connectors are required if an upgrade to a PXM1E-8-155 card without service interruption is required.


Table 5 MGX Chassis, Card, and APS Configurations Part 2

Front Card Type
Min. 800 Part Number and Revision
Back Card Types
APS
Con
Min. 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830
PXM1E
MGX 8950
PXM45

XM-60

800-04706-06-A0

x

MGX-APS-CON

800-05307-01-A0

x

MGX-8850-APS-
CON

800-20640-01-A0

x

x

MGX-8830-APS-
CON

800-05308-02

x

x

MGX-8950-APS-
CON

800-15308-01-A0

x

MGX8950-EXTD-CON

800-23813-03-A0

x

MPSM-T3E3-155

800-23005-06-A0

SFP-2-155

Yes

800-23170-02-A0

x

x

x

x

   

BNC-3-T3E3

800-23142-04-A0

         
   

SMB-2-155-EL

Yes

800-23171-03-A0

         

MPSM-8-T1E1

800-24473-07-A0

AX-RJ48-8T1

800-02286-01-A0

x

x

x

x

   

AX-R-RJ48-8T1

800-02288-01-A0

         
   

AX-RJ48-8E1

800-02408-01-A0

         
   

AX-R-RJ48-8E1

800-02409-01-A0

         
   

AX-SMB-8E1

800-02287-01-A0

         
   

AX-R-SMB-8E1

800-02410-01-A0

         

MPSM-16-T1E1

800-22339-08

RBBN-16-T1E1-1N

800-23091-03

x (/B chassis only)

x (/B chassis only)

x

x

MCC-16-E1-1N

800-23135-02

RED-16-T1E1

800-23092-04

MCC-16-E1

800-19853-03

x

x

x

x

RBBN-16-T1E1

800-21805-04

RCON-1TO5-8850

800-23094-03

x (/B chassis only)

x (/B chassis only)

 

RCON-1TO3-
8850

800-23196-01

x (/B chassis only)

x (/B chassis only)

x


Table 6 MGX Chassis, Card, and APS Configurations Part 3 

Front Card Type
Min. 800 Part Number and Revision
Back Card Types
APS
Con
Min. 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830
PXM1E
MGX 8950
PXM45

AXSM-1-9953-XG

800-07365-06-A0

SMFSR-1-9953

800-08237-06-A0

x

   

SMFIR-1-9953

800-08246-06-A0

         
   

SMFLR-1-9953

800-08247-06-A0

         

AXSM-4-2488-XG

800-16987-04-A0

SMF-4-2488-
SFP

SMFSR-1-2488-SFP

SMFLR-1-248-
SFP

800-19913-04-A0

10-1421-03


10-1742-01

x

AXSM-1-2488

800-05795-05-A0

SMFSR-1-2488

Yes

800-05490-05-A0

x

   

SMFLR-1-2488

Yes

800-06635-04-A0

         
   

SMFXLR-1-
2488

Yes

800-05793-05-A0

         

AXSM-1-2488/B

800-07983-02-A0

SMFSR-1-2488/B

Yes

800-07255-01-A0

x

x

   

SMFLR-1-2488/B

Yes

800-08847-01-A0

         
   

SMFXLR-1-
2488/B

Yes

800-08849-01-A0

         

AXSM-4-622

800-05774-09-B0

SMFIR-2-622

Yes

800-05383-01-A1

x

   

SMFLR-2-622

Yes

800-05385-01-A1

         

AXSM-4-622/B

800-07910-05-A0

SMFIR-2-622/B

Yes

800-07412-02-B0

x

x

   

SMFLR-2-622/B

Yes

800-07413-02-B0

         

AXSM-2-622-E

800-18521-02-A0

SMFIR-1-622/C

Yes

800-07410-02-A0

x

x

   

SMFLR-1-622/C

Yes

800-07411-02-A0

         

AXSM-16-155-XG

800-20821-06-A0

SFP-8-155

SMFIR-1-155-
SFP

SMFLR-1-155-
SFP

MMF-1-155-
SFP

Yes

800-21518-03-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

x

x

x

   

MCC-8-155

Yes

800-22117-02-A0

         

AXSM-16-155

800-05776-06-A0

MMF-8-155-MT

Yes

800-04819-01-A1

x

   

SMFIR-8-155-
LC

Yes

800-05342-01-A0

         
   

SMFLR-8-155-
LC

Yes

800-05343-01-C0

         

AXSM-16-155/B

800-07909-05-A0

MMF-8-155-
MT/B

Yes

800-01720-02-A0

x

x

   

SMFIR-8-155-
LC/B

Yes

800-07864-02-B0

         
   

SMFLR-8-155-
LC/B

Yes

800-07865-02-B0

         

AXSM-8-155-E

800-18520-02-A0

SMB-4-155

Yes

800-07425-02-A0

x

   

MMF-4-155/C

Yes

800-07408-02-A0

         
   

SMFIR-4-155/C

Yes

800-07108-02-A0

         
   

SMFLR-4-155/C

Yes

800-07409-02-A0

         

AXSM-16-T3E3

800-05778-08-A0

SMB-8-T3

800-05029-02-A0

x

SMB-8-E3

800-04093-02-A0

AXSM-16-T3E3/B

800-07911-05-A0

SMB-8-T3

800-05029-02-A0

x

x

SMB-8-E3

800-04093-02-A0

AXSM-16-T3E3-E

800-18519-02-A0

SMB-8-T3

800-05029-02-A0

x

x

SMB-8-E3

800-04093-02-A0

AXSM-32-T1E1-E

800-22229-01-A0

MCC-16-E1

800-19853-02-A0

x

RBBN-16-T1E1

800-21805-03-A0


Table 7 MGX Chassis, Card, and APS Configurations Part 4 

Front Card Type
Min. 800 Part Number and Revision
Back Card Types
APS
Con
Min. 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830
PXM1E
MGX 8950
PXM45

MGX-SRME

800-14224-02-A0

MGX-SMFIR-1-155

Yes 1

800-14460-02-A0

x

x

x

   

MGX-STM1-
EL-1

Yes 2

800-23175-03-A0

         

MGX-SRME/B

800-21629-03-A0

MGX-BNC-
3T3-M

800-03148-02-A0

x

x

x

x

   

MGX-STM1-
EL-1

800-23175-03-A0

         

MGX-SRM-3T3/C

800-05648-01-A0

MGX-BNC-
3T3-M

800-03148-02-A0

x

x

x

x

MGX-AUSM-
8T1/B

800-04809-01-A0

AX-RJ48-8T1

800-02286-01-A0

x

x

   

AX-R-RJ48-
8T1

800-02288-01-A0

         

MGX-AUSM-
8E1/B

800-04810-01-A0

AX-SMB-8E1

800-02287-01-A0

x

x

AX-R-SMB-
8E1

800-02410-01-A0

AX-RJ48-8E1

800-02408-01-A0

AX-R-RJ48-
8E1

800-02409-01-A0

MGX-RJ48-8E1

800-19310-01-
B0

AX-CESM-8E1

800-02751-02-A0

AX-SMB-8E1

800-02287-01-A0

x

x

x

   

AX-R-SMB-
8E1

800-02410-01-A0

         
   

AX-RJ48-8E1

800-02408-01-A0

         
   

AX-R-RJ48-
8E1

800-02409-01-A0

         
   

MGX-RJ48-8E1

800-19310-01-
B0

         

AX-CESM-8T1

800-02750-03-B0

AX-RJ48-8T1

800-02286-01-A0

x

   

AX-R-RJ48-
8T1

800-02288-01-A0

         

MGX-CESM-
8T1/B

800-08613-02-A0

AX-RJ48-8T1

800-02286-01-A0

x

x

x

   

AX-R-RJ48-
8T1

800-02288-01-A0

         

AX-FRSM-8E1

800-02438-04-A0

AX-SMB-8E1

800-02287-01-A0

x

x

x

AX-FRSM-8E1-C

800-02462-04-A0

AX-R-SMB-
8E1

800-02410-01-A0

x

x

x

AX-RJ48-8E1

800-02408-01-A0

AX-R-RJ48-
8E1

800-02409-01-A0

MGX-RJ48-8E1

800-19310-01-
B0

AX-FRSM-8T1

800-02461-04-A0

AX-RJ48-8T1

800-02286-01-A0

x

x

x

AX-FRSM-8T1-C

800-02461-04-A0

AX-R-RJ48-
8T1

800-02288-01-A0

MGX-FRSM-2CT3

800-06335-01-D0

MGX-BNC-2T3

800-04057-02-A0

x

x

x

MGX-FRSM-
2T3E3

800-02911-07-D0

MGX-BNC-2E3

800-04056-02-A0

x

x

x

   

MGX-BNC-2T3

800-04057-02-A0

         

FRSM-12-T3E32

800-18731-02-A0

SMB-6-T3E3

800-08799-01-A0

x

MGX-FRSM-
HS2/B

800-17066-01-A0

SCSI2-2HSSI/B

800-05463-02-A0

800-05501-01-A0

x

x

   

MGX-12IN1-8S

800-18302-01-A0

         

MGX-RPM-PR-
256

800-07178-02-A0

MGX-MMF-FE

800-03202-02-A0

x

x

x

x

MGX-RPM-PR-
512

800-07656-02-A0

MGX-RJ45-
4E/B

800-12134-01-A0

         
   

MGX-RJ45-FE

800-02735-02-A0

         

MGX-RPM-XF-
512

800-09307-06-A0

MGX-XF-UI

800-09492-01-A0

x

x

   

MGX-1-GE

800-18420-03-A0

         
   

MGX-2-GE

800-20831-04-A0

         
   

MGX-1OC12
POS-IR

800-08359-05-A0

         
   

MGX-2OC12
POS-IR

800-21300-04-A0

         
   

GLC-LH-SM (was MGX-GE-
LHLX)

30-1301-01-A0

         
   

GLC-SX-MM (was MGX-GE-SX1)

30-1299-01-A0

         
   

GLC-ZX-SM (was MGX-GE-ZX1)

10-1439-01-A0

         

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-CON
800-05307-01
MGX-8850-APS-CON
800-20640-01-A0
MGX-8830-APS-CON
800-05308-02
MGX-8950-APS-CON
800-15308-01-A0

MGX 8850 (PXM45)

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155-XG

MGX-SRME

MGX-SRME/B

MPSM-T3E3-1551

MGX 8850 (PXM1E)

PXM1E-4-1552

PXM1E-8-155

MGX-SRME

MGX-SRME/B

MPSM-T3E3-1551

MGX 8830

PXM1E-4-1552

PXM1E-8-155

MPSM-T3E3-1551

MGX 8950

AXSM-16-155/B

AXSM-4-622/B

AXSM-1-2488/B

AXSM-16-155-XG

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:

spvcoverridesvc

spvcoverridesvp

spvpoverridesvp

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:

For GR253:

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

For AnnexB:

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.

PNNI Limitations

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.

Upgrade Information

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.

Maintenance Information

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.

Table 9 Known Anomalies in Release 5.1.20 

Anomaly ID
Description

CSCee07604

Headline: Couple XBAR and HMM_ events clean-up.

Symptom: The standby PXM logs the following information:

 HwMonitor  xbarGetDevIdForXbarPlan
 2940: Errno 0x0: Msg unable to find dev

Condition: When XBAR error ISRs are received.

Workaround: None

Hardware: PXM45

CSCeg29002

Headline: Stuck with free running clock on PXM1E.

Symptom: On PXM1E systems, under some conditions (rare occurrence), if the clock is internal clock, it may not get locked again to primary or secondary clock source until there is card reset.

Condition: This symptom is a rare occurrence on PXM1E when primary clock flaps. This symptom is seen in MGX 4.0, but it can happen in other releases.

Workaround: Perform a switchcc, or if there is only one card, reset the PXM card. Also, it is possible to issue delclksrc and cnfclksrc to recover.

Hardware: PXM1E

CSCeg59069

Headline: CCMA fails to transition to active.

Symptom: The MPSM-16-T1E1 card gets stuck in INIT state. Sometimes only the standby card has this problem and sometimes both the active and standby cards get stuck in the INIT state. A core dump file is generated when the problem occurs.

Condition: The exact scenario under which the problem happens is not known, and the problem rarely occurs.

Workaround: None

Hardware: MPSM-16-T1E1

CSCeg79882

Headline: CLP0 discards on AXSM-E when cnfoamsegep and online diagnostics are enabled.

Symptom: An AXSM-E card shows CLP0 discards when online diagnostic and are enabled or when cnfoamsegep is enabled.

Conditions: AXSM-E card was running 4.0.10.202 when this problem occurred.

Workaround: None.

Hardware: AXSM-E

CSCeh01295

Headline: Need to increase the VC/Cos/SG thresholds for SAR connections.

Symptom: CRC errors observed.

Condition: With connections are passing through a AXSM PNNI link.

Workaround: Nne

Hardware: AXSM/A

CSCeh03624

Headline: 2 sec additional latency for IPCP to converge.

Symptom: After an MLPPP bundle goes to Operation Up, it takes around 2 more seconds for IPCP between MWR and RPM-XF to converge.

Condition: After the MLPPP bundle goes up, MPSM stops sending AIS on the connection to the RPM-XF. Also, the MPSM takes about 0-3 sec to negotiate LCP with XF. This is typically about 2 seconds. This is inherent to the split PPP architecture of this release.

Workaround: None

CSCeh44896

Headline: After a switchcc, the primary clock lock state shows free run on PXM1E.

Symptom: After a switch CC, the primary clock's clock lock state is free run when displayed with the dspcurclk command.

Condition: When the PXM1E is configured with BITS clock sources 1.35 and 1.36, a switchcc causes the issue.

Workaround: Physically remove the clock source cable, or delete and re-add the clock source from the CLI.

Hardware: PXM1E

CSCeh66111

Headline: Alarm in B/W MPSM-MF line and FRSM CAS line takes more than 2 hours to clear.

Symptom: Framing errors on MPSM E1 lines.

Conditions: Occurs with MPSM line in MF or MF-CRC mode, when connected to FRSM-8 in CCS/CCS-CRC mode.

Workaround: Configure a different framing mode for the line.

Hardware: MPSM-16-T1E1

CSCeh62582

Headline: PXM1E combo fails E3 pulse mask.

Symptom: Port 3 has marginal failures on the pulse mask. It has some reflection/noise at the zero reference for a pulse.

Condition: The ports do not have functional problems and the cards have been in the field for four years without any issues. The detection of a 1 or 0 is not affected by this, because the thresholds are higher than the reflection.

Workaround: None

Hardware: PXM1E

CSCeh94891

Headline: Standby PXM45 remains in init state.

Symptom: The standby PXM45 remains in init state.

Condition: The PXM45 is running 3.0 bootcode.

Workaround: Use the cnftopogw on command to turn on the gateway node, then reboot the PXM45. This will allow the standby to be updated properly.

Hardware: PXM45

CSCei03261

Headline: mainProc1 in suspended state.

Symptom: mainProc1 found in suspended state.

Condition: Occurs while resetcd script is running.

Workaround: None

Hardware: PXM45/B

CSCei13891

Headline: Policing on VBR.2 connections allows to many CLP1 cells.

Symptom: VBR.2 connections for both real time and non-real time service types allow CLP1 cells in excess of the PCR and SCR. This could potentially result in network congestion.

Condition: Test setup to determine throughput.

Workaround: None

Hardware: AXSM

CSCei16136

Headline: AXSM fails E3 AIS response.

Symptom: When a port is in loop time mode, upon receipt of AIS, the E3 port should revert to internal clock. Currently all ports remain in loop time mode.

Condition: When port is in loop time mode, upon receipt of line AIS.

Workaround: None

Hardware: AXSM

CSCei17194

Headline: dspcon in conditioned alarm. no log detail on PXM45B controller.

Symptom: PVC connection fails and raises a conditioned alarm, which does not clear.

Condition: Occurs when running a script that repeatedly performs delcon/addcon.

Workaround: Perform delcon/addcon again.

Hardware: MPSM-16-T1E1-PPP

CSCei19268

Headline: Auto-restart sync state stuck in loopbacksync even when tx/rx id are different.

Symptom: The sync state is loopbacksync instead of tempSync when the IMA IDs are different.

Condition: Occurs when IMA ID's are different between groups on AXSME and MPSM-16-T1E1 cards.

Workaround: None

Hardware: MPSM-16-T1E1

CSCei23845

Headline: MPSM stuck in failed state after resetcd script.

Symptom: MPSM-16-T1E1-PPP card stuck in Failed state.

Condition: While running traffic at above OC3 rate in the lower bay and running a script to reset the MPSM cards

Workaround: None

Hardware: MPSM-16-T1E1-PPP

CSCei23863

Headline: Traffic loss in both directions. IPCP is in acksent.

Symptom: When cards are repeatedly reset, one of the bundles (3 of the 4 bundles were ok) in one of the cards did not resume correctly, causing all traffic in both directions to not pass. IPCP is in reqsent state.

Condition: With a 1:N redundancy group, while running a script that repeatedly resets the cards, and while running around 80-85% capacity traffic. This problem does not occur when the traffic rate is low (for example: 40% of capacity), or if the traffic is stopped after about 8-10 sec after the MPSM goes down.

Workaround: Perform dn/upppplink or dn/upmpbundle to restore traffic. This action renegotiates IPCP.

Hardware: MPSM-16-T1E1-PPP

CSCei33337

Headline: Memory leaks after deactivating/activating a non-existent bundle.

Symptom: Memory leaks over time can cause MSPM card to hang.

Condition: Run dnmpbundle/upmpbundle script on a non-existent bundle.

Workaround: None. There is never a need to dn or up a non-existent bundle, and doing so repeatedly should not be done. If the card runs out of memory, it must be reset.

Hardware: MPSM-T3E3-155-PPP

CSCin84727

Headline: Bad release number was included in statistics file for VISM.

Symptom: Enabling statistics on VISM 3.3 card on MGX node is creating a bad file list.

Conditions: Enable statistics from SSM.

Workaround: None.

Hardware: PXM1E

CSCin86763

Headline: The configuration file sent from a switch for AXSM-XG does not having any associated SCT.

Symptom: All of the SCT associations on AXSM-XG card/port vanish after cold start CWM.

Conditions: None.

Workaround: None.

Hardware: AXSM-XG


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

Identifier
Headline

CSCir01835

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

CSCeh12738

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

CSCej17823

PPP link flap during the PXM upgrade prevents graceful upgrade

CSCej62559

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

CSCei67407

RPM-XF addred is blocked when RCON is present.


Table 14 lists the resolved anomalies in Release 5.1.20.

Table 14 Resolved Anomalies in Release 5.1.20 

Anomaly ID
Description

CSCec04754

The status byte in stats file is always set to 1 ERR.

CSCec48191

WatchDog timeout core dump is caused by SAR Queue Full.

CSCef66706

A maximum MRU of 1494 is achieved in the RPM-XF to MWR direction, when a MRU of 1524 is configured.

CSCef67225

Update frNIW in CISCO-WAN-FR-CONN-MIB file; Replace for MPSM-T3E3-155.

CSCef97365

REG5.1 Syncram invalid-unblock error found.

CSCeg03191

The mpsm-oc3 dumps the core after reset.

CSCeg25173

The mpsm-8-t1 dumps the core after reset.

CSCeg47129

REG5.1 Resetsys causes the remote nodes (AXSM-XG OC-3) pnniport into the down state.

CSCeg53512

REG5.1 Standby PXM went into failed state after switchcc and saveallcnf.

CSCeg57198

Core hot-dump on MPSM-16-T1E1 caused traffic to stop.

CSCeg60544

Fan tray trap discrepancy between mgx and mgx2.

CSCeg61656

BW update does not go through when RPM-XF subinterface is down.

CSCeg62874

When a bundle is administratively down and card is reset, the port changes to administratively up.

CSCeg65632

SAR Dispatcher hangs on mutex semaphore, which causes the card to reset.

CSCeg65663

Many SSI exceptions occur on a PXM1e node.

CSCeg69701

Database corruption after upgrading to 5.1.

CSCeg78661

AUSM trap 50918 is missing two varbinds.

CSCeg86507

phpi communication error on the mpsm-oc3/16.

CSCeg87717

PXM45/B system has a significant decrease in SPVC reroute rate performance.

CSCeg88649

ABR configuration is lost after standby reset.

CSCeh03411

Exception error on mpsm card causes card reset and coredump.

CSCeh06279

The tstdelay/tstcon tests failed on all connections.

CSCeh09518

AIS not generated when Port went down on AXSMXG

CSCeh10277

Stby XGoc12 in failed state; switchredcd caused synRamErrs.

CSCeh14484

ABR PCR is not getting copied to channel PCR in the MPSM-8T1-FRM card.

CSCeh15349

Entering the clrchancnt command after stopping traffic does not show traffic cleared.

CSCeh15410

WFQ cannot be disabled on ABR connections.

CSCeh16336

WFQ cannot be enabled on CBR/VBR connections.

CSCeh18931

lmiRootTask Addr exception occurs after switchred.

CSCeh19705

AXSM-XG NNI end points are not generating AIS after UNI end point is removed.

CSCeh24125

OSPF goes down in single link mode with fragmentation enabled after bundle down/up.

CSCeh27127

Standby PXM45C stuck in Init-U/Active after entering loadrev command.

CSCeh29436

Policing drops CLP traffic on CBR.2 connection.

CSCeh29602

Some AXSMXG SCT files have inappropriate values for UBR.2 policing.

CSCeh30900

MPSM takes more than 4 minutes to boot after resetcd because of boot checksum issue.

CSCeh39575

MPLink trap is sent for Switch-side link after operUp, operDown events.

CSCeh46897

No RxAIS on AXSM-XG DS3 path when ominber is sending DS3 AIS to it.

CSCeh47620

Both primary and redundant MPSM cards are in the active state.

CSCeh48942

PPP links go down when protocol reject message is received for PPPmux.

CSCeh49968

pnports with ILMI are stuck in auto config after up/dnpnports.

CSCeh53471

workQPanic on MPSM155.

CSCeh58122

Incorrect speed for OC48 SONET path.

CSCeh63999

Traffic with packet size 1495 or more is dropped on MPSM-16-T1E1-PPP.

CSCeh64669

Need support for cds3RcvAIS count and cds3FEBE count.

CSCeh69278

Intermittent failure in IMA group setup between MPSM and AXSME.

CSCeh70562

Traffic in excess of PCR on UBR.2 connections egress as CLP1.

CSCeh72899

Wrong OIDs populated for Xmt CLP0 and CLP1 cells.

CSCeh78289

Hardware migration for NBSM to MPSM fails.

CSCeh80047

With 1:n redundancy group, primary MPSM stuck in boot when reset by second primary MPSM running a different version.

CSCeh96945

vc-merge fails to create tag vsi connections on AXSME.

CSCeh97670

Headline: MPSM-16-T1E1-PPP cards go to failed state after running resetcd script.

CSCei07636

PHPI communication error.

CSCei09787

Standby PXM stuck in backup boot after sysVersoinSet on active PXM.

CSCin84104

FRSM-8P does not recognize SMB Line Connector Type after upgrade.

CSCin89087

Loadrev causes failure of active/primary MPSM-T3E3-155.

CSCin89618

MEMBLKERROR message while entering clrsmcnf command on MPSM-16-T1E1.


Status Changed Anomalies

Table 15 lists the anomalies that changed status but were not resolved in Release 5.1.20.

Table 15 Status Changed Anomalies in Release 5.1.20 

Anomaly ID
Description

CSCee96728

Headline: When MPSM-16 is inserted in secondary slot, it goes to failed state.

Symptom: MPSM-16-T1E1 standby card goes to failed state sometimes.

Conditions: The exact condition under which this problem happens is not known at this moment. Frequency of this problem happening is rare.

Workaround: Reset the card.

Hardware: MPSM-16-T1E1

CSCef56354

Headline: P2MP SVC: AXSM in via node is not copying cells from root to leaf.

Symptom: Point-to-multipoint (P2MP) SVC is losing traffic in a via node.

The SVC is built properly from the root UNI port to terminating leaf ports. The traffic does not reach the terminating leaf nodes because it is being dropped in the AXSM/B card in the via node between the endpoints.

Conditions: The symptom occurs on PXM45/B based MGX 8850 running 5.0(0.201). AXSM in question is a AXSM_16T3E3_B.

Workaround: None.

Hardware: AXSM1

CSCeg05982

Headline: Intermittent Switch Side Tx: AIS alarm occurs on multiple connections.

Symptom: Multiple connections showed intermittent "Switch side Tx: AIS" alarms. The alarms come and go in a second but keep on flapping.

Conditions: Unknown.

Workaround: Unknown.

Hardware: AXSM1

CSCeg18176

Headline: sysDiag failure caused AXSM-XG cards to reset.

Symptom: AXSM-XG cards are resetting.

Conditions: This symptom occurs with an Online Diag failure.

Workaround: None.

Hardware: AXSM-XG

CSCeg18559

Headline: resetcd on RPM-XF created tRMM exception and PXM45 switchover.

Symptom: PXM45/B switchover when resetcd was executed on a RPM-XF card.

Conditions: While traffic was being pumped to RPM-XF card, router was reloaded via resetcd command. Upon execution of this command, a tRMM task exception occurred, which forced a PXM45 switchover.

Workaround: None.

Hardware: PXM45/B

CSCeg34511

Headline: pnCcb is suspended on PXM45/B.

Symptom: Call Control task gets an exception and causes a system reload.

Conditions: P2P and P2MP calls were being stress tested with frequent trunk resets.

Workaround: None.

Hardware: PXM45/B

CSCeg35481

Headline: Traffic resumes after configuring RPM link when connection is down.

Symptom: Traffic goes between RPM-XF and MPSM when the connection is down.

Conditions With the switch side connection down, the switch side PPP link parameters were configured. Without upping the connection, traffic resumed.

Workaround: None.

Hardware: MPSM-16-T1E1-PPP

CSCeg40352

Headline: Link Persistency OIDs return incorrect values.

Symptom: There are three MIB variables on the PXM45-based MGX switch platform that are populated improperly under a loopback condition on a PNNI link port. This leads the Link Persistency feature to not work properly for the scenario where a PNNI link port is put into loopback.

Conditions: This symptom occurs with PXM45-based MGX running 3.0(20) or 5.0(10.200) configured with PNNI links to another PXM45-based MGX running 3.0(20) or 5.0(10.200).

Also, this symptom occurs with a soft loopback added (local or remote) to the PN port of a PNNI link (AXSM line cards) with CWM 15.0 Patch 2.

Workaround: None.

Hardware: AXSM1B_OC3

CSCeg41300

Headline: MGX 8850 caviIngRcvClp0Cells counter is not incrementing.

Symptom: The caviIngRcvClp0Cells and caviEgrXmtClp0Cells counters from the CISCO- TM-VIRTUAL-IF-MIB are not counting correctly. The caviIngRcvClp0Cells counters are not counting ingress received CLP0 Cells. The value is always 0.

The caviEgrXmtClp0Cells counter is incrementing, but the value is always the same as caviIngXmtClp0Cells although the counters are different on the CLI.

Conditions: Only the caviIngRcvClp0Cells and caviEgrXmtClp0Cells counters are incorrect. The caviEgrRcvClp0Cells and caviIngXmtClp0Cells are the same as on the CLI.

Workaround: Collect the counters from the dspportcnt on the CLI.

Hardware: PXM1E

CSCeg51624

Headline: PHPI exception error on standby card.

Symptom: Exception error occurred on pan PXM.

Conditions: This symptom occurred after an over night resetcd script.

Workaround: None.

Hardware: PXM45/C

CSCeg51848

Headline: Traffic outage (up to 6 secs) is seen when one or two links are disconnected in a bundle.

Symptoms: Loss in ping traffic after cable pullout.

Conditions: This symptom will happen always.

Workaround: None.

Hardware: MPSM-16-T1E1-PPP

CSCeg56466

Headline: MPSM dumps the core after switchred.

Symptom: MPSM core dump after reset.

Conditions: None.

Workaround: None.

Hardware: MPSM-155-T1E1

CSCeg61884

Headline: IPCP is not coming up after resetting MPSM at high traffic rate.

Symptom: IPCP is not coming up to open state.

Conditions: This symptom occurs when resetting the active MPSM while traffic is running at a high rate with static routes configured.

Workaround: Shut/No shut the GigE interface.

Hardware: MPSM

CSCeg63447

Headline: VA flaps constantly on connections between RPM-XF and MPSM (no traffic).

Symptoms:

1. VA is constantly flapping.

2. Two PPPoA connections between RPM-XF and MPSM are in E-AisRdi alarm.

Conditions: Some actions done were to upgrade node/cards to latest image and run sustained traffic over two days.

Workaround: None.

Hardware: MPSM-16-T1E1-PPP

CSCeg63729

Headline: SNMP failed for trapmgr table. Node was unreachable for CWM.

Symptom: Node is unreachable for CWM.

Conditions: SNMP is failing for trapmgr table.

Workaround: None.

Hardware: PXM45/B

CSCeg66818

Headline: Watchdog core dump occurs on a PXM45.

Symptom: Watchdog core dump occurs on a PXM45.

Conditions: This symptom occurs during an upgrade.

Workaround: None.

Hardware: PXM45/B

CSCeg71468

Headline: Watchdog timeout reset occurs during normal operation when PnCcb is active

Symptom: Watchdog timeout reset occurs during node normal operation when PnCcb is active.

Condition: This symptom occurs during normal operation.

Workaround: Not known.

Hardware: PXM1E

CSCin84727

Headline: Bad release number was included in statistics file for VISM.

Symptom: Enabling statistics on VISM 3.3 card on MGX node is creating a bad file list.

Conditions: Enable statistics from SSM.

Workaround: None.

Hardware: PXM1E

CSCin86763

Headline: The configuration file sent from a switch for AXSM-XG does not having any associated SCT.

Symptom: All of the SCT associations on AXSM-XG card/port vanish after coldstart CWM.

Conditions: None.

Workaround: None.

Hardware: AXSM-XG


Resolved Anomalies in Previous Releases

This section contains the resolved anomalies in the following releases:

Release 5.1.00

Release 5.0.20

Release 5.0.10

Release 5.0.00

Resolved Anomalies in Release 5.1

Table 16 lists the anomalies that are resolved in Release 5.1.

Table 16 Resolved Anomalies in Release 5.1 

Anomaly ID
Description

CSCee31416

If card mode is different on stby MPSM-16, upln causes ram sync error

CSCee47465

CBSM-AXSM-XG conn - after switchredcd - traffic stops

CSCee58638

Hardcoding of PXM slot for AXSM-MPSM-155 conns: traffic loss on 8830

CSCee63424

Need support for NAK51-54 in PXM45 VSIS RM to clear dangler conns

CSCee80054

Sby PXM only - not disk from 8850 > 8830 goes into mismatch

CSCee85921

WIN5901: Link stuck in usable after particular error is removed

CSCee91236

MPSM cnfatmlayer command has no ds1 channel option on a T3 line

CSCee92300

Help message refers to obsolete/eng CLIs

CSCee94999

Remove PXM1E backup boot from PXM1E OAM Loopback feature compile

CSCee95294

WIN5984: MPSM16-EIT: some random pnni links fail when added by script

CSCee95371

IMA pnni-link deroute conns when switchred

CSCef02017

MPSM16-EIT: spi path add errors when one of the mpsm in 1:N reboot

CSCef08146

MPSM16-EIT: snmpget on Rcv and Tx Bytes return wrong values for FR Port

CSCef15811

MPSM16EIT: WIN6091 ima grp restart with NNI/ILMI causes card reset

CSCef15971

WIN6545 non supported DPS OAM cell stats handling

CSCef16682

WIN6545 invalid ATM cell with PTI=7 handling and stats update

CSCef20727

rmAllocLcn error during init stage

CSCef21354

Pre-Etch5 card fails to come up due to lack of HW FIFO

CSCef21961

tTnCmdTsk01 hogs CPU on pxm45b in sysBramEvtLogPrint()

CSCef22181

UT anomaly: Block addition of Slave connection on MLP Bundles on MPSM

CSCef22838

PXM45C-8830: Unable to reroute any service type conns except ubr

CSCef26657

Memory Leak under Congestion Scenario w/ Current Route

CSCef27840

MPSM16DT: Instruction Bound Exception caused the pxm1e to reset

CSCef27984

The shaper for a VBR3-nrt PVC runs at SCR instead of PCR

CSCef28074

PHPI communication failure on MPSM after switchcc

CSCef28123

ABR has the same excessive priority as UBR

CSCef28241

PXM45C-8830: pnRedman SSI-3-EXCEPTION

CSCef28565

connection addition failing between MPSM16T1E1 and AXSM

CSCef30937

MPSM was failed after PXM switchcc stress testing

CSCef32181

XG ports in autoconfig for 30 min, after upgrade

CSCef32407

MPSM16DT: mpsm16 card reset due to Bus Monitor Err on mpsm WINPATH

CSCef33722

MPSM16DT: 1:N RED failed to protect when the Primary card failure

CSCef35674

FECN is mapped to EFCI when setEFCIzero and NIW

CSCef35743

WIN6354:MPSM16DT: dnimagrp on NE mpsm16 causes FE mpsm16 to reset

CSCef35755

Ping between MWR and XF goes through even after dncon on MPSM.

CSCef36378

WIN6313: OAM generated from IMA port has wrong CRC10

CSCef38377

PXM1E OAMLP tstpndelay failed with no SM response, connref > 32K

CSCef42054

Active PXM45 switched causing a core file

CSCef43182

MPSM16DT: ausmb card stuck when addimagrp w. out of range number

CSCef44587

EDP sometimes programmed to EPD0 sometimes to EPD1

CSCef45859

CLI dsppnni-path aw cbr caused exception

CSCef46693

switchcc fail due to outstanding database update

CSCef49455

MPSM16DT: Detected 1:N Red config mismatch, act/sdby reset on runrev

CSCef50757

Memory Leak after Repeatedly Downing Then Upping PNNI

CSCef51168

MPSM16DT: Active and Stdby reboot on switchredcd caused by snmpSA Task

CSCef51592

MPSM16DT: Byte Base Egress Service Ratio still work in Frame Base

CSCef52302

SNMPSA exception due to NULL pointer access

CSCef53988

Local Channel loopback on a VPC connection on AXSME flips VCI to 0

CSCef55251

mpsm card stay in failed state after setrev

CSCef56775

Mce thresholds for Q zero not initialized properly on AXSM/B

CSCef58958

Telnet sessions are not being released gracefully

CSCef60038

Loopback tests on CBM via Win1 fails after 447 passes

CSCef62707

PXM45C-8830: dspconinfo, dspcons, dsppncons and others not working

CSCef63916

WIN6784: overrun issue upon dn/upppplink stress testing

CSCef64820

Mfg Diag only shows warning if master clock is not locked

CSCef65717

PXM45C-8830: Traffic loss around 1 sec with y-red on MPSM-OC3

CSCef66764

IMA RX frame length field is not displaying in config GUI

CSCef68719

clrsmcnf causes pnCCb crash and pxm45b resets

CSCef68743

56K link after reset has wrong comet programming

CSCef69457

Access level implementation for inTask commands

CSCef71060

IT: memory allocation/fragmentation issue after extended stress test

CSCef71163

MFRDT: MPSM8T1 all CLI rejected with wrong parsing and timeout on CC

CSCef72844

Missing SRM cards do not cause 1:N Red State to be Blocked

CSCef74066

DupFileList created while collecting stats on MPSM-16T1E1 cards

CSCef74998

Need to bring all links down before renegotiation for cnfmpbundle

CSCef77506

MPSM16DT: IMA nni lnk derouted all connections during switchcc

CSCef79081

MPSM16DT: mpsm standby card stuck init-state during runrev, coredump

CSCef79645

MPSM-Diag: Online diag fail to run on stdby 1:N MPSM-16

CSCef79647

Traffic stops completely on configuring ACFC/PFC on admin dn ppplink

CSCef80396

CRC RM error counter is not counted correctly on scheduler hw chip

CSCef81959

Stby MPSM-T3E3-155 in failed state after loadrev

CSCef82452

dspchancnt is not working on MPSM-PPP

CSCef83027

MPSM16DT: loadrev on 1:N mpsm16 caused standby to Failed-U state

CSCef83728

Switchside PPP links go down after switchred on MPSM

CSCef83782

REG5.1 cutW1Task SSI-3-EXCEPTION

CSCef84575

MFRDT:WinPath Packet Bus Monitor error after link addition WIN6805

CSCef85133

snmpwalk on cimaLinkState gets into an infinite loop

CSCef88428

MPSM-Diag: Offline diag fail to start on 1:1 stdby MPSM

CSCef89132

if mru is nakd and then cnf to default (1500), links stays operDown

CSCef89191

IMA84 SDRAM refresh rate needs to be increased

CSCef90401

MPSM16DT: reset active 1:n red caused CBC-5-INVALID_ARG error

CSCef90982

ATM0: SSI-3-EXCEPTION HwMonitor while reloading RPM-PR

CSCef91392

MPSM-Diag: IMA-84 R/W test does not fail after fault insertion

CSCef92507

semaphore not defined, pxm45 in active-F

CSCef92669

not freeing connTrace msg. in congestion cond.

CSCef92922

REG5.1:AT Intermittently can not do cc 9 in reg-p3 node

CSCef93442

After switchred some of the switch side PPP links go down

CSCef93530

MFRDT:SSI-3-exception when issue dsppaths -ds3

CSCef93921

MRU cannot be changed on cnfppplink for transactCnfPppLink/Db failed

CSCef95524

MLP is not negotiating MRRU - PPP link stay inactive

CSCef96232

MPSM-PP is sending wrong endpoint discriminator on one of the links

CSCef97521

MPSM-16T1 Offline Diag test fails

CSCef97872

cannot addmux after delmux followed by dnmpbundle sometimes

CSCef97890

pnCcb memory leak on pxm45

CSCeg01270

no alarm on MPSM-T3E3-155 VNNI ports when VPCs are failed

CSCeg02154

PNNI: pnSptAwP task crash on SLT node

CSCeg02202

Current Route: current route tables are not getting populated

CSCeg02917

mfr configuration not visible in CWM

CSCeg03366

memory leak by pnSptAwP, pnSptCtdP and pnSptCdvP tasks

CSCeg04876

MPSM-OC3:ds1 lns not shown on CWM, incorrect file sent by switch

CSCeg05676

nni link is in auto config after dn/uppnport on xg side

CSCeg05839

UPG5.1: pxm1e stuck in Empty/Reserve by remove/insert on 5.1(0.29)

CSCeg06814

MPSM-T3E3-155: Unable to upgd redundant cards

CSCeg08005

MFRDT: Unable to allocate buffer after add channloop on mfr conns

CSCeg09699

I2C driver support for winpath B1 chips

CSCeg09701

MFRDT: 1-2 sec FR traffic loss when aps switchover by link removing

CSCeg10557

Shellconn command dspNovram srmfc, <slot#> returns wrong data

CSCeg10741

dspchancnt rcv frames counter programming invalid.

CSCeg10810

frtt on MPSM FR should be in microseconds

CSCeg11715

MPSMOC3 diagnostics enhancements

CSCeg12241

WIN 7309: lcp flaps on PPP links after downing one link

CSCeg12342

MPSM16PER: FrForwarding EGR is tagging BECN when INGR is congested

CSCeg13566

Memory leak issues on some SMs, cannot CC to them

CSCeg13614

MPSM 1:N Red: multiple mpsm-16-t1e1 cards in active-F

CSCeg15558

Endpoint Discriminator shown as Hex on MWR in MPSM-16-T1E1-ppp solution

CSCeg17056

dnbundle/dnppp, then upppp, upbundle, switch side PPP remains down

CSCeg17339

MPSM primary and secondary resets on doing a graceful upgrade

CSCeg17345

WIN7073-REG5.1 Congested PNNI/SSCOP VC on mpsm aftr rcvry from reset

CSCeg17462

AUSM-8T1E1 cannot delete a port, error Connections existing on port

CSCeg17480

Missing MFR slave endpts data in config upld file for MPSM_8E1_FRM

CSCeg18618

Clear trap is not sent after selftest failure 60061 has been sent

CSCeg18974

MLPPP: ppplink trap 60272 having invalid value for lcp_pfc and lcp_acf

CSCeg21347

PPP link goes down on MWR while shown up on MPSM

CSCeg21470

Standby PXM45B stuck in INIT state due to ILMI addr ending w/ 0xff

CSCeg23877

UPG5.1:mpsm-155 went to Active-F-U-Active during runrev

CSCeg24814

PXM Diagnostics enhancements

CSCeg25020

CRC errors on the line when using AMI line coding

CSCeg28234

CS pkts seen with crtp+muxing ON MPSM for cUDP traffic

CSCeg28643

Need to free memory after generating trap

CSCeg29011

ppplink shows down on MPSM & up on MWR after switchred.

CSCeg29724

XM60 insertion causing active PXM45C to reset.

CSCeg29996

WIN 7310: dn and up 3 ppplinks result in long intermittent ping drop

CSCeg32485

MPSM 8T1E1 cannot have vci 32 to 34 included

CSCeg35663

MFRDT: Unable to delete link on standby after link deletion on active

CSCeg36583

MFRDT:WIN7289 bus monitor error during MFR/IMA configuration

CSCeg36788

Active MPSM-8T1E1 comes up to standby after power cycle

CSCeg40360

MPSM E1 cards in lower bay crashed due to CTC exception

CSCeg42093

REG5.1: Switchredcd between LSM and MPSM-8T1E1 is not allowing

CSCeg43495

MPSM in empty state after resetsys if core mask for PXM reset is enabled

CSCeg46596

pnCcb crashed after rsetcd and dn/uppnport

CSCeg48573

REG5.1, 1:N switchredcd not rejected when SRME is not available

CSCeg50990

Transfer Delay Time For ABR Connections is slow (30+ms).

CSCeg52860

Workaround for ATMIzer SAR lockup

CSCeg55688

MPSM-16-T1E1 goes into ACTIVE-F state after switchcc

CSCeg57247

Compressed Packets are dropped on RPM-XF due to Corrupt PID

CSCeg66107

NEW_AXSMB_OC12: No traffic flow after delapsln on 1:1 intracard APS

CSCeg66440

ssi exception error on axsm-xg: ilmi sync task dies

CSCin83809

MLPPP: Bundle gets added with wrong def value of cmpbendPointDiscrimC

CSCin85557

axisImaGroupVersion does not in the config upload file


Resolved Anomalies in Release 5.0.20

Table 17 lists the anomalies that are resolved in Release 5.0.20.

Table 17 Resolved Anomalies in Release 5.0.20 

Anomaly ID
Description

CSCec12381

add/del/dsp chanloop commands should be supported on MPSM

CSCec81892

XGOC3-DEV: BAD SCT is causing axsmxg-oc3 conns to not get rerouted

CSCed21480

Update diagnostic code for AXSM2P and AXSM4P

CSCed55564

mainproc 2 holding pnni_get_buffer

CSCee30100

BulkAddFRTFTPConn(): cannot add conn stats - getting this log

CSCee53753

Wrong physical alarm state causes MFR conns in A-bit alarm

CSCee56603

Incorrect error message for partition overlap on AXSM cards

CSCee61427

PVC can not be deleted from AXSM - Not in Cpro Db

CSCee63073

tree not updating port speed change if mod with row status up/down

CSCee66689

enable the winpath trace buffers

CSCee70227

WIN5669: Bus monitor error with only LMI and link control traffic

CSCee70333

cdsCCV24HrThreshold mib returns out of range value of -1

CSCee70489

MPSM-155 Diag Development/Enhancement

CSCee76355

incorrect error msg while trying to configure invalid link

CSCee77715

link stops receiving control frames after add/delete/add links

CSCee79587

clrsmcnf asked for second time, even when setrev not done first time

CSCee85483

MFREIT: Unable to restart the MFR bundle through CLI

CSCee87948

MFREIT: MFR bundle admin stays in down after upmfrbundle

CSCee88501

ilmi errors in the log for mpsm

CSCee88716

After switchred, port and bundle state are up while link state is not up

CSCee89478

MFREIT: Incorrect link alarm detection while line in loop back

CSCee90076

tracking: PXM alarm report shall include MFR bundle/link alarms.

CSCee90129

tracking: inconsistency issues between SM and CWM

CSCee90160

LMI task reports header or IE invalid on MFR port

CSCee91535

It requires a batter way to reserve BW for control message.

CSCee92813

abr-std NIW PVC on an MPSM155 discards traffic in one direction

CSCee94539

MFREIT: connection alarm counter incorrect for fr/mfr cons in dsptotals

CSCee96562

MFREIT: ddlwp_htTermConnDel fails with WP_ERR_CH_NOT_DISABLE

CSCef00558

MFREIT: Mfr link state in addsent when phy layer is down

CSCef02725

WIN5993: MPSM155 winpath policing failed on FR/CBR w/CIR 93% port rat

CSCef06072

MPSM155: WP_ERR_RATE_OUT_OF_RANGE error is seen in the logs

CSCef07410

SNMP subsystem call to soiRpmPortOpen() failed

CSCef08020

OAMLP clrsmcnf caused AXSMB-OC3 to go to DOWN state

CSCef09520

WIN6041: STL configuration Patch Questions

CSCef10520

WIN6099: WP_ERR_WMM_FIFO_GET after several hours (WP_HostSend)

CSCef10909

Need to send Node License Alarm Trap, and show this alarm in dsplics

CSCef13112

show inventory CLI output has diff PID than in the dspcd output

CSCef13143

AXSM-XG OAM API could cause mem free fail when sending message fail

CSCef16101

MFRDT: Dspportcnt intermittently shows huge counts in FECN/BECN

CSCef21354

Pre-Etch5 card fails to come up due to lack of HW FIFO

CSCef22408

Unclear Err Message for movelic on MPSM card with no licenses

CSCef23594

Incorrect redundant mpsm-8t1e1 card config info upload

CSCef23717

MFRDT: Addmfrlnk with link used by other bundle give improper err msg

CSCef24248

changes to handle the frsm getting stuck in failed state

CSCef24978

event log flooded with FIPC-5-RSLVTIMEOUTWARN

CSCef26833

xg rebooted after upilmi on vnni trunk

CSCef27984

The shaper for a VBR3-nrt PVC runs at SCR instead of PCR

CSCef28059

MPSM dnport causes card reset when port sct missing

CSCef28074

PHPI communication failure on MPSM after switchcc

CSCef28123

ABR has the same excessive priority as UBR

CSCef28907

Exception happens when execute addmfrlnk and addlnloop

CSCef29270

Nonpersistent ABR generate RM and stay 10CPS for some time

CSCef29523

MFRDT: need clarifying the rejecting err message of cnfmfrbundle

CSCef29565

MFRDT: Need warning of dn/upmfrbundle needed after changing link name

CSCef30195

MFRDT: Some CLIs becomes unavailable after ccc to mpsm cards

CSCef30612

MFRDT: dspmfrlnkbucketcnt being logged in log file

CSCef30862

MFRDT: available BW in dspload is only 75% BW showed in dspport

CSCef32074

MFRDT: dcMpsm:addMfrBundle debug message in console should be remove

CSCef32137

MPSM DS3 lines stuck in minor alarm

CSCef32181

xg ports in autoconfig for 30 min, after upgrade

CSCef32258

MFRDT: addcon can use dlci number out of mindlci/maxdlci of partition

CSCef32323

Units definition and display correction for dspportsct cosThr

CSCef35008

MFRDT: fail to detect mfr link misconfig when use same bname/lname

CSCef35674

FECN is mapped to EFCI when setEFCIzero and NIW

CSCef35946

MFRDT: Unable to enable lmiSig while adding mfr port

CSCef35972

POOL Tbl ERROR on screen after switchcc

CSCef36378

WIN6313: OAM generated from IMA port has wrong CRC10

CSCef36403

MFRDT: Cnfpath with Local/Remote loopback is blocked

CSCef36994

MFRDT:WP_ERR_WRR_WEIGHT_MUST_BE_GREATER_THAN_OR_EQUAL_TO_ONE,CardFail

CSCef37040

Minor version change may fail SCT version check in AXSMXG cards

CSCef37113

MFRDT: validateUpIntfc error when mfr port is already added on bundle

CSCef37354

WIN6284: LMI host term conn failed switch-over to new seq number

CSCef37470

setDEone on SIW connection still map CLP

CSCef38377

PXM1E OAMLP tstpndelay failed with no SM response, connref > 32K

CSCef38389

CH_NOT_DISABLE error when cnfport (FR) change -rat

CSCef38628

MFRDT: Bundle is UP without Mfrlnks configured

CSCef39574

AXSME: snmp walk causes emRoot task to run away

CSCef40134

231 level WDDI patches for 1.3.x branch

CSCef42054

Active PXM45 switched causing a core file

CSCef42656

link delay time is not accurate.

CSCef42867

LMI task reports invalid frame length for Status Enquiry

CSCef43327

MFRDT: Dspln needs NOTE: to exclude MFR ports, and need number of MFR links

CSCef44587

EPD sometimes programmed to EPD0 sometimes to EPD1

CSCef45861

MFR bundle and link names require node/slot IDs for uniqueness

CSCef45874

dspmfrlnkalm needs to show detail alarm reasons instead of multp

CSCef47208

Need fast DRAM test for axsm boards

CSCef47271

MFRDT: needs down/up remote mfr bundle after change local bname/lname

CSCef47362

MFRDT: function spec needs update with correct trap# for all CLIs

CSCef47503

MFRDT: mfr trap 60638 reports unknown ifname with secondary/active ca

CSCef49515

MFRDT: Unable to bundle T1 links when channelization scheme different

CSCef49845

MFRDT:WP_ERR_INVALID invalid error code 0x31C while delmfrbundle

CSCef49927

MFRDT: T1 path goes into yellow alarm periodically with mfr link

CSCef50757

Memory Leak after Repeatedly Downing Then Upping PNNI

CSCef51130

MFRDT: Improper or non-accurate error message for mfr related CLIs

CSCef51277

mfr port operState may get stuck in false alarm state

CSCef52092

Proactive support for upcoming MGX 8850 and MGX 8830/B model B chassis

CSCef52237

cnfport -rat failed in FR 2+1 byte mode

CSCef52302

SNMPSA exception due to NULL pointer access

CSCef52440

MFRDT: Unable to updates shelf database while cnfmfrlnk

CSCef53988

Local Channel loopback on a VPC connection on AXSME flips VCI to 0

CSCef54121

need to checkin latest wddi patch

CSCef54454

MFRDT: card in active-f and lost config with exception after delmfrl

CSCef56652

MFRDT: WIN6613 WP_MfrScanAssemblyTimeout returns HST_CMD_FAILED

CSCef56670

MFRDT: Wrong ifType in MFR trap 60633

CSCef56775

Mce thresholds for Q zero not initialized properly on AXSM/B

CSCef57382

PXM45C-8830: pnports stuck in Auto Config state

CSCef58663

MFRDT: Traffic loss at FR ABR, NTA reported at ATM side

CSCef59739

MFRDT: LOW static MEM alarm on all MPSM155 cards

CSCef60012

MFRDT:FIPC-EPHNDLRFAIL in dsperr after Dn/Upmfrbundle or Cnfmfrbundl

CSCef60710

MFRDT: Inconsistent link state when link has yellow alarm

CSCef60716

MFRDT: Link delay value too big when no delay introduced physically

CSCef62624

Unsupported OIDs need to be undefed on MPSM cards

CSCef63405

MFRDT: lmiRootTask suspended cause card reset 3 times WIN6653

CSCef63431

MFRDT: VsiSlave Task suspended during connection deletion WIN6592

CSCef63750

MFRDT: regular FR port stuck in LMI failure after load to 13.157A

CSCef63757

MPSM FM conn parms from upload trap 60641 are incorrect

CSCef65048

MFR port addition is rejected: DDLWP error

CSCef65206

MFRDT: traffic keep dropping when one of MFR links in alarm

CSCef65717

PXM45C-8830: Traffic loss around 1 sec with y-red on MPSM-OC3

CSCef65817

ATM ABR with intvsvd does not slow down during congestion

CSCef66103

MFRDT: traffic loss 100ms when add one or more MFR link

CSCef66104

Need Shell Cmd to Dsp a Map btw path name and the LinkID

CSCef67114

SMFIR SFP in MPSM-T3E3-155 displayed as SMFSR

CSCef67652

dspatmlayercnt always reports 0 for STS3c Channelized DS1 paths.

CSCef67722

MFRDT:LMI NNI ports OperState opposite from FE MFR ports aft upgrade

CSCef68330

Local ACR on AXSME unable to exceed remote PCR

CSCef68719

clrsmcnf causes pnCCb crash and pxm45b resets

CSCef70625

MFRDT: Link stays up when delay exceed limits 300 ms

CSCef71734

MFR addmfrport need to check bundle inhibit state

CSCef74837

On stdby, delmfrlnk may fail after deleting mfr port.

CSCef74965

WIN6653: Tx pool list corrupted if having different buffer size

CSCef75447

After switchred, MFR port with LMI enabled shows wrong state.

CSCef77552

MFRDT: Link delay time great than 0 when lower layer down

CSCef79483

MFRDT: delcons with more numbers caused con deleted on other port

CSCef79588

AXSM-XG SCT files have wrong OID and threshold value

CSCef79694

ssiSemShow gives divide by zero error

CSCef80396

CRC RM error counter is not counted correctly on scheduler hw chip

CSCef81959

stby MPSM-T3E3-155 in failed state after loadrev

CSCef82223

MFRDT: fail to add/cnf LMI on FR port with FR 2+1 byte Eg Qos Scheme

CSCef82937

link stuck in addsend state due to link name mismatch.

CSCef83498

MFRDT: WIN6791 Stratcom LMI failure with 7200 router (unknown DLCI)

CSCef83875

MFRDT: Dspmfrlnkcnt need reset after switched from Stdby to Active

CSCef84575

MFRDT: WinPath Packet Bus Monitor error after link addition WIN6805

CSCef86540

I2C version check should be removed

CSCef89191

IMA84 SDRAM refresh rate needs to be increased

CSCef90042

MFRDT:DE tagging with link delay and default bc and be value

CSCef90492

MFRDT: switchred/FC remove may cause up to 24 sec traffic loss

CSCef91992

The PTSE is dropped on receiving IG with type 36

CSCef92507

semaphore not defined, pxm45 in active-F

CSCef93530

MFRDT:SSI-3-exception when issue dsppaths -ds3

CSCeg01270

no alarm on MPSM-T3E3-155 VNNI ports when VPCs are failed

CSCeg02981

UPG5.1: shm logs error CTC-4-CTC err after upgr pxm fr 4.0.15 to 5.1

CSCeg05624

MFRDT:MFR links up/down periodically after multiple down/up bundles

CSCeg07099

MFRDT:cc command from mpsm ccc session gives inaccurate error message

CSCeg08005

MFRDT: Unable to allocate buffer after add channloop on mfr conns

CSCeg09699

I2C driver support for winpath B1 chips

CSCeg09701

MFRDT: 1-2 sec FR traffic loss when aps switchover by link removing

CSCeg11715

mpsmoc3 diagnostics enhancements

CSCeg15436

Too many logging messages from ccProtoGet, DSPImageGet

CSCeg17345

WIN7073-REG5.1 Congested PNNI/SSCOP VC on mpsm aftr recovery from reset

CSCeg18728

WDDI/DPS patch 246 check in

CSCeg22314

Upgrade from R1.5 to R2.0 - 5.1.2.x fails at diskTbl creation

CSCeg24868

vxsm_parms_evts.h file needs to be auto generated

CSCeg29724

XM60 insertion causing active PXM45C to reset

CSCeg34421

MFRDT: FarEnd bundle name becomes un-defined after mfr name changes

CSCeg35663

MFRDT: Unable to delete link on standby after link deletion on active

CSCeg40316

WDDI sets tag to user_info field only for OAM channel

CSCeg50990

Transfer Delay Time For ABR Connections is slow (30+ms).

CSCeg52860

WatchDog timeout core dump caused by Sar Queue Full

CSCin59675

AUTO:UPC policing parameters are not properly displayed for AXSMXG

CSCin79215

Traps not getting generated for MFR link addition


Resolved Anomalies in Release 5.0.10

Table 18 lists the anomalies that are resolved in Release 5.0.10.

Table 18 Resolved Anomalies in Release 5.0.10 

Anomaly ID
Description

CSCdz87948

AXSM-9952 config clock source not working properly

CSCea51529

PXM45C cards need ECC enabled.

CSCea65034

dspDevErr/dspDevhist doesn't work on stdby PXM

CSCeb28420

EvtLog:emSyncHumveePort fail messages in log

CSCeb83965

Policing of 80 char limit for dsplns on AXSM-E

CSCec63412

MPSMOC3: Card reset after dnport/upport, tVsiSlave task Suspended.

CSCec70107

novram corrupted (fc id) corrupted

CSCec83227

MPEIT: MPSM card resets because of emRoot Exiting

CSCed09998

AXSM-XG support for ABR dual leaky bucket.

CSCed10963

Changes to xcnfalm settings do not take effect without card reset.

CSCed25756

APS 1:1 intra-card, direction change results in mode mismatch error

CSCed43063

cnfcdsct with non-default SCT does not read SCT file correctly

CSCed43129

AXSME card went into Active-F after card came up due to reset

CSCed45527

bootChange applies incorrect default values to some fields

CSCed48943

UPG5: License not release after abort NBSM->MPSM upgd

CSCed52168

plcp stats are not displayed on switch CLI for ds3 Lines

CSCed53501

MP155-DT: Down then up ports cause ABR conns go to mismatch state

CSCed53630

FR traffic cannot pass through E3 G751

CSCed56001

MPSM: con-add of atm/abr1 con with MPSM endpoint failed

CSCed56640

IPCONN: Standby PXM is stuck in INIT forever due to IPCONN sync fail

CSCed56839

WIN4718: MPSM-T3E3-155 resets and does not recover during conn add

CSCed59288

tRootTask: SYS-1-TASKLOSTFATAL system reset on pxm1

CSCed60771

MPSM155-DEV:MPSM alarm changed from major to minor after switchred.

CSCed61340

REG5: DPS on MPSM-8T1E1 stops transmitting cells under stress

CSCed62026

delport fails on MPSM-CES and MPSM-ATM card

CSCed62493

DOS: Inconsistent file size and contents immediately after FTP

CSCed62531

multiples of 50 cps on IMA group ATM port rate limitation

CSCed64456

Rsc. prtn exists on the card but got deleted from PXM1E for MPSM

CSCed65153

MPSM-155-DT: stby MPSM goes into I2C fail after switchred/reset stdby

CSCed65346

Need to throttle event logging for Bad SNMP packets and keep stats

CSCed65476

one frame/cell drops when resuming traffic on another path

CSCed65762

MPSM-155: snmpMibSemTake fail, MPSM hang & reset after Addimalnk/Addbe

CSCed66567

dspportcnt <port#> for atm port states that port does not exist.

CSCed67077

many connections stuck in mismatch alarm after cnfpart -maxcon

CSCed67161

More cell drops seen on IMA connection during pxm/sm switchover

CSCed67543

Bandwidth used by ILMI should be CACed

CSCed67567

MPSM Diag tests cause WP Buss Polling exception

CSCed67641

SNTP updated TOD information more frequently than should be.

CSCed68441

MPSM-155: Delimalnk should be rejected w/ Startimalnktst enabled

CSCed68735

MPSM-155-DT: pnport goes to building vc after conns addition

CSCed69122

MPSM-155-DT: MPSM with IMA trunks comes up as active-F after node reset

CSCed71549

MPSM-155 sends RAI on path defects for DS1 paths.

CSCed71719

APS 1+1: some APS paths go into critical alarm after switchredcd

CSCed72328

call rate enhancement in MPSM OC3 winpath

CSCed73181

MPSM-155: Enabling frame-discard on master fails in h/w

CSCed73552

WIN 5048: traffic drop on FR/ATM conns after mcr reduced to 50

CSCed74374

REG5: RED Active AUSM card stuck in Boot State after Resetcd

CSCed74450

MPSM-155DT: MPSM configures as IMA trunk stuck in Active-F state

CSCed79636

cell discarding at egress when other 2000 connections in alarm

CSCed79767

dspchancnt does not work with -r and -max option on MPSM-155

CSCed81006

MPSM Etch 7 goes into idtmon with the oc3 crdmp feature change

CSCed81492

PNNI commands do not adhere to the 24 lines/page req

CSCed81568

MPSM-155-DT: switchover while rerouting results tVsiSync and tVsiSlave stuck

CSCed81573

Tracking code review for Vxworks prob w/ semaphore (cant cc to card

CSCed81645

MPSM-155-DT: Standby card stuck in init state after active card reset

CSCed81676

Port present on service module, but missing in PAR.

CSCed84291

MPSM-OC3 card went into Active -F state

CSCed84737

CLP failed to set to 0 on FR con when ChangeDEtoCLP map=setCLPzero

CSCed85445

replace ssiRamIovCurMaxElementsGet with new SSI API (in all AXSM app

CSCed85997

SNMP timeouts on MPSM-OC3 card after snmpwalk on IMA tables

CSCed86130

CESM-8T1E1 disables processing of RAI if lineCondition enabled

CSCed88354

XG-UPC non-compliance counters incorrect for framed conns

CSCed88488

XG-UPC tag counter incorrect for GCRA2 on frame mode conns

CSCed89620

AXSMXG offline diag fail on timeout 3 hours later

CSCed89697

MPSM-155: PreferRte failed on MPSM port w/Invalid LinkId

CSCed90393

OAM issues between RPM-XF and MPSM

CSCed91102

FGCRA does not work on MPSM155

CSCed91160

ATM-FR ABR connection stuck in Fail after enabling VSVD on both ends

CSCed91876

XG-UPC hot core dump causes exception

CSCed92346

AIS_COND: CESM cannot send AIS due to line cond via SRM/SRME link

CSCed92601

MPSM-155: tLMClient task can potentially run out of stack

CSCed93586

RPMXF card does not come up; keeps waiting for ctc port registration

CSCed94135

SSH: MGX hangs, CPU hogged, error loop with seconds ssh channel

CSCed94385

Xbar errors on slots with AXSM-E cards

CSCed94878

config FR port sct failed after configuring a non-existent SCT file

CSCed94954

pnCcb exception caused switchover

CSCed95652

Rev.B: CES CAS channel does not receive traffic

CSCed95664

Rev.B: dspWpUtil does not work

CSCed95687

MPSM-155-DT: red card failed after switchover/dnallport/upallport/etc

CSCed95766

Traffic loss when run tstdelay on CBR con with full PCR traffic

CSCed95913

dsppaths command displays DS1 paths out of order in T3 backcard

CSCee00796

ILMI enabled UNI port goes down and up when connection are added

CSCee00828

RevB board takes a long time to download firmware

CSCee02189

MPSM-155-DT: tVsiSlave run away from CPU after dnports/resetcd/upports

CSCee02497

AXSMXG: GFR setting is lost on standby after standby reboot

CSCee02914

Unnecessary em log can be removed in GetPartialLinePmStats()

CSCee03906

Failing adding red still allocates license

CSCee04644

remove <frport_num> parameter option from addbert on MPSM

CSCee05232

Continuous traffic drop on MPSM IMA port upon running stress test

CSCee05255

PNNI crashed after running resetcd script

CSCee07111

OAM on ILMI vpi/vci causes AXSM active/F with QE48 H/w error

CSCee09022

reverting cnfrteopt TOD and VPI/VCI parameters to defaults

CSCee09064

UPG5: AXSM update stdby card with incorrect value for Frame discard

CSCee09072

AXSME: GFR setting is lost on standby card after standby reset

CSCee09158

bootchange cmd on AXSM-E OC12 w/o changes caused card reset

CSCee10237

Fail to automatically create CUT dir if accidently deleted

CSCee11986

RTD on NB-ATM and IMA interfaces is high

CSCee12710

MPSM-155-DT: Redundant cards fail after multiple times switch over

CSCee12720

IPC resolve errors from task tVsiSlave

CSCee14367

PXM reset and coredumped due to descriptor table full

CSCee16049

Cannot add an AUSM connection with a VC number lower than 35

CSCee16959

PXM45 not downloading enable.stats file to SMs after switchredcd

CSCee17245

MPSM8-RAS: Enabling MIAC during boot in atm mode has issues

CSCee18300

PNNI: Reachable address shows old node ATM address

CSCee18428

cpro did not read SCT service type correctly

CSCee18442

MPSM8-RAS: tstcon/tstdelay can reboot MPSM-8T1E1

CSCee19358

HV Add ELT Fails when add/del/add frequently with same rmt info

CSCee19912

MPSM-155: T3/Y-Red, TCB rele-msg memory leak VsiErr after switchover

CSCee20454

MPSM-155-DT: Connections routing fails with WP-ERR-WMM-FIFO-PUT

CSCee20817

AXSM switchover resulted in data outage on AXSM-MPSM conns

CSCee22385

FTP server task write to stale socket - cause file corruption

CSCee24142

Software truncation errors on PCR/SCR for CBR and VBR conns

CSCee24554

MPSM8-RAS: Adding VPC rebooting MPSM-8T1E1

CSCee24831

AXSMXG-FDR: pnRedman fails to update stdby; connections lost

CSCee27978

Inserting both backcards generated multiple ApsModeMismatchClr traps

CSCee28318

SUNI driver needs to insert arbitrary pointer change to downstream

CSCee30064

connections deleted on AUSM switchredcd & PXM reset

CSCee30273

MPSM-155: IMA Grp Down w/Insff-link, but Port is Up, SPVCs are Up.

CSCee31377

MPSM OC3 SIM card failed on upgrade

CSCee31972

UPG5+: XG EVNNI port stuck in down after runrev

CSCee32671

LMI sends incorrect message during timer retry

CSCee35169

AXSM Resets SNMP Subagent Software Exception

CSCee35248

REG5+: AXSME-32-T1E1 loses backcard config after upgrade

CSCee35698

MPSM8-RAS: ATM ABR srcdest is not enabled correctly on channel

CSCee35820

MPSM8-RAS: softswitch should not check b/c if card in red bulk mode

CSCee38216

Card Reset is Setting Stats Ftp Status to ACTIVE. Should be INACTIVE

CSCee39204

No Action taken on Mutex semaphore hang for NON stdout semaphore

CSCee39665

cliRat task died during stdby card coming up

CSCee40457

Standby PXM reset/failed during upgrade

CSCee42145

Switch ASIC semaphore causes CLI freeze-AXSME

CSCee42153

UPG5+: Mem leak from AXSM-XG lmiRootTask

CSCee43147

LMI data corruption if multiple LMI ports configured

CSCee43404

active PXM45B reset by SSI exception

CSCee44283

UPG5+: P2MP failed to commit to AXSM after upgrade

CSCee44466

LMI Control VC should use VSI service type signaling

CSCee44697

ILMI enable/disable not updated in rsc_part table on changing ILMI config.

CSCee44876

MPSM-155: Standby MPSM got reset 6 times overnight w/Cac Fails error

CSCee45538

Switch ASIC semaphore causes CLI freeze-AXSMXG

CSCee45542

Switch ASIC semaphore causes CLI freeze-PXM1E

CSCee45544

Switch ASIC semaphore causes CLI freeze-MPSMOC3

CSCee45558

When LMI goes down - send heart beat messages only

CSCee45645

LMI should accept all msgs from remote end - even if LMI down

CSCee45813

1st traplet from trap 50620 has unmatching checksum

CSCee46860

XBAR: Errors on standby AXSM-E xbar links when the PXM/SM resets

CSCee47465

CBSM-AXSMXG conn - after switchredcd - traffic stops

CSCee48033

add interface id in pnni log for duplicate address or node id

CSCee48346

Execute more than 10K ping commands caused memory corruption

CSCee48721

AXSMXG-FDR:ECC-MBit error causes card Failure

CSCee50647

UPG5+: IMA grp stuck in failed after AUSM->MPSM8 switchover

CSCee52477

Need to remove logging stack trace from ssiStringCopy

CSCee53175

ATM ABR cells discarded at ingress/egress by sct abr_cng_Thr > CLPhi

CSCee54810

-sc option on MPSM cnfln is invalid

CSCee55966

Popup msg on telnet: pipcSend send error: AUTOCARD

CSCee55997

dspports on AXSM-E does not follow 80 char formatting

CSCee56267

WINPATH: IPC between MPSMs failed due to stale message at winpath

CSCee57791

MPSM8-RAS: burnboot on PXM45 and pxm1e cause card to cyclic resets

CSCee59053

dspcd CLI command on Line card does not display VID field

CSCee61427

PVC can not be deleted from AXSM - Not in Cpro Db

CSCee61463

Critical HW Mastership errors declared on PXM after switchcc

CSCee62436

MPSM addcon only allows max CIR to partial port speed.

CSCee62933

REG5+: SSI-3-EXCEPTION Software exception found

CSCee63139

UPG5+: Mem leak on AXSM after line config failure

CSCee63140

dbSvrSync task holding memory block

CSCee63159

vnni port propagation is failing

CSCee65520

PNPERS: MPSM OC3 Stuck in Init state on Node with 4000 ports

CSCee66754

PXM45C: Single Bit ecc errors on resetting PXM intermittently.

CSCee67637

UPG5+: SRMEB failed after switchover from legacy SRM/SRME

CSCee68047

CLI warning message for delpref command

CSCee69222

Excessive MIB-7_MODULE_UNKNOWN event log messages

CSCee70641

pnCcb task got suspended at sscop_chk_txQ_for_statenq_or_bse()

CSCee70837

MPSM-155 went to active-F with SSI exception when far end MPSM remove

CSCee72296

Traps 70235 and 70236 missing a digit for Rte Opt End TOD field

CSCee72388

addcon fails for CBR ATM conns with PCR = 104268 cps

CSCee73008

AXSM-E randomly sets E1 CRC multiframe SA bits, which should be all 1s

CSCee74007

MPSM-8T1E1 keep rebooting due to diag caused exception

CSCee74345

Unable to create 1:n red group between multiple XF cards

CSCee77715

link stops receiving control frames after add/delete/add links

CSCee78093

Wrong physical alarm state causes FR conns in LMI-Abit alarm

CSCee78941

MPSM-DT:sledTask0 suspension, MPSM goes to active-f state

CSCee78995

connections on SM went into mismatch when update counter > 2^15-1

CSCee80833

upport failed on FR port with error of sct reference counter failed

CSCee80886

xg-oc48 in failed/empty after resetcd

CSCee80889

ssi snmp exception error on AXSM-XG

CSCee80910

ilmi as disabled on xg pnport

CSCee81869

Obsolete traps 60126 and 60127 need to be removed

CSCee83187

MPSM-155 pnni trunk stuck in auto-config

CSCee83711

Switch driver error noticed on pxm1e

CSCee84449

Fix for parameter memory timing issue

CSCee85874

WIN5816: Egress OAM Loopback test causes MPSM card to reboot

CSCee88501

ilmi errors in the log for MPSM

CSCee89505

WIN5913: MPSM Card in Active-F state after lmiRootTask exception

CSCee89950

IPC error: IlmiPassup reaches the max queue and drop packets

CSCee91460

switchredcd caused previously active FRSM to constantly reset

CSCee92794

dnport/upport on MPSM FR port causes connections to go into mismatch

CSCee92813

abr-std NIW PVC on an MPSM-155 discards traffic in one direction

CSCee93763

UPG5+: runrev on FRSM from 21.0(12) to 22.0(10) failed

CSCee94585

FR ABR rif and rdf factors are not set correctly via CLI

CSCee95371

IMA pnni-link deroute conns when switchred

CSCee95646

MPSM OC3 in Active-F after addport failed

CSCee96764

redundant card table entry is not deleted after deleting MPSM-155 red

CSCef04048

UPG5+: False resource alm flagged after upgrade from 5.0 to 5.0(10)

CSCef04619

WIN6016: tstdelay on MPSM FR endpoints times out with no data on conn

CSCef12968

Memory Leak on AXSM when issuing multiple tstdelay/tstconseg command

CSCef13315

ClassOfServce (2) option needs to be removed from MPSM cnffrparms

CSCef13392

Add debug code in VSI to verify with HW

CSCef16855

Provide infra support for PPP_ALARM and MFR_ALARM.

CSCef18694

LMI Signaling on both end is not syncing up causing signaling fail

CSCef23594

Incorrect redundant MPSM-8T1E1 card config info upload

CSCef24248

changes to handle the frsm getting stuck in failed state

CSCef24752

per PVC %util parameter is applied to MCR for abr-std connections

CSCef24789

MPSM-OC3 NNI/VNNI links in building VC state

CSCef41542

VISM-PR goes into fail state after power cycle and switchcc

CSCin69908

Trap 50401 containing wrong port number after start bert

CSCin72192

oof_criteria,aisc_check gets populated in line table for E3 interface

CSCin79508

Cannot CC to the card after resetsys or resetcd


Resolved Anomalies in Release 5.0.00

Table 19 lists the anomalies that are resolved in Release 5.0.00.

Table 19 Resolved Anomalies in Release 5.0.00 

Anomaly ID
Description

CSCdv32986

100% data is getting dropped on some connections

CSCdw91580

Removing SRME FC or BC causes switchover time > 250 ms.

CSCdy23797

pntrace command needs to be updated in documentation

CSCdy77053

dspportcnt does not have Ingress counter

CSCdz04524

P2MP_DT: SPVC p2mp parties terminated on AXSM-E stays in FAIL

CSCdz54692

Add additional fields for sonet/ds3 path traps

CSCdz87948

AXSM-9952 config clock source not working properly

CSCea46779

PXM45/B with broken Humvee-SAR interface

CSCea59612

dnpnport/uppnport caused all links to go to ILMI failure

CSCea64363

dspDevErr need to be modified to show the device No.

CSCea75353

DEV: SPVC fail to establish w/ lctd set to sum of trunks ctd

CSCeb05910

PM parameters on NBSMs are not accurate

CSCeb11493

Inconsistent routing cost

CSCeb13272

P2MP pnRedman exception triggered during delparties

CSCeb15291

pxm reports card in active-F and cc to card fails

CSCeb17823

Unreliable tstdelay results for AXSM/B/E <--> frsm

CSCeb20522

EvtLog: switchcc-CTC-4-EVTSENDTOSTMCHN error message

CSCeb20570

EvtLog: switchcc-multiple entries related to CBC/FW ready/not ready

CSCeb28420

EvtLog: emSyncHumveePort fail messages in log

CSCeb35085

Getting error on cell bus caused card to go to failed state

CSCeb38659

resetsys on PXM45 causes AINI port to vc failure

CSCeb38985

MOC error caused ILMI failure on AXSM-XG card

CSCeb40265

xcnfln shows the clkfrquencythreshold 1-5. does not show what is meant

CSCeb40512

delred fail for LSM in 8830

CSCeb41273

cnfdiagall command does not work after cnfdiag <slot> used

CSCeb45254

SRMEB: Add/Del line loop cause APS failure

CSCeb51323

SRMEB: Stats manager caused Active PXM1E reset

CSCeb58207

none of the bert commands executed is seen in the dsplog

CSCeb58227

conns are not derouted upon ilmi timeout when slp is enabled and dero

CSCeb58599

MPSM8-DT: PXM45 logs Diag Error when online diag is running on STBY

CSCeb59239

PM parameters on NBSMs are not accurate

CSCeb60706

PXM45/B reset due to non fatal major error core dump available

CSCeb63198

MPSM8-DT: Connection routed on Prefrte but Pref-rte flag does not set

CSCeb64000

switchover loss around 630 ms, >250 ms

CSCeb67820

CIT50: node db contains two entries with same node id

CSCeb67843

Failed to add entry in QE48 Conn id table

CSCeb68706

observed message file already closed after runrev executed on frsm

CSCeb71578

HARD: No switchover of 1:n red after removing primNBSM then act PXM

CSCeb76581

CIT50: pnRedman suspended at provred_persis_link_addDel

CSCeb80000

conn does not deroute right away upon dnport with deroute delay on an

CSCeb83949

Policing of 80 char limit for dsppnportcac and dsppnportrsrc command

CSCec01073

FRSM HS2/B to support low speed rates like 2.4K

CSCec05854

Do NOT null out ifid for interfaces (back out CSCea32660)

CSCec08533

CESM T3E3 1:1 Redundancy is not functional

CSCec12108

Pnports of AXSM-XG card stay in building vc

CSCec12463

EVENT-CLEANUP: multiple ncdp fill in dsperrs log.

CSCec12609

CIT50: several VSI sev4 error logged from act and standby AXSM/B

CSCec14761

Software Error Reset PXM45

CSCec16762

Cannot cc on AXSM due to max sessions in hang

CSCec23758

FRSM HS1 connections stuck in AIS alarm after card reset.

CSCec27723

Pnni signaling lcn reuse - pnni link cannot establish

CSCec28435

AXSM-E IMA port goes into vc failure after dnpnport and uppnport

CSCec31183

Port Alarm is asserted on standby CESM-T3E3 card after addred

CSCec33505

Receive FIFO not held in reset during dnln.

CSCec35834

Card failed to come back active after reboot (RPM)

CSCec39239

PBUMP: No Direct Path after Downing Trunk and Upping It Back

CSCec40496

Dnport on the Uni port on AXSM-XG card doesn't work

CSCec41322

resetsys caused SM to be reset again due to MCast rcvr loosing msgs

CSCec41394

ILMI-4-GEN-ERR emIlmiStartCfgReg evt generated when card in Init

CSCec42058

Statistical Alarm counters are not ok

CSCec42174

getting xbar alarm with offline diags enabled

CSCec42531

Err on switchcc outstanding database update

CSCec43059

AXSM-XG - Path stay in critical alarm while line is clear

CSCec45604

Re-used port stay in alarm

CSCec45631

UI-S3 Clock Controller fails to enter Free Run mode

CSCec49118

Standby AXSM Failed due to IPC buffer leak on Active AXSM

CSCec49709

Wrong module type message in CWM log for PXM45/C UI-S3B

CSCec51074

backcard aps mux not set accordingly after switchred

CSCec51349

PXM1e reset after pumping high rate oam loopback

CSCec55245

Allowing to turn off rate control feature with ABR configured

CSCec55319

Mem leakage in procResponse: RespCalcC exhausting SSI SNMP partition

CSCec55976

vsiSlave Task suspended recovery action should be Fatal

CSCec56452

DE-LSNT: switchredcd on RPMXF followed by switchcc cause two XF reset

CSCec59926

dump commands pause indefinitely with RPMs and may leak resources

CSCec62846

Failure on the data forwarding path was not detected

CSCec63239

VxWorks timer wrapped around

CSCec63535

AXSM-E: P2MP party in failed state after dnport/upport on leaf port

CSCec63556

AXSM P2MP root does not pass AIS to leaves on LOS/AIS

CSCec63713

AXSM reset with core dump

CSCec65160

dspload shows asymmetric bandwidth on AXSMs

CSCec66028

11010P4C: Trunk is shown into major alarm while there is no alarm on switch

CSCec66037

UBR.2 policing needs to tag all cells

CSCec66881

LSNT:AXSM Xtags does not come up

CSCec67719

HMM and QE48 falsely detects parity error when enabled

CSCec69262

PXM does not switch RPM-XF upon bkcd failures

CSCec69678

Popup: Cannot open input file ALARM:/SM_ALARM_1_13.CF errno = 0x388002

CSCec71316

DT: Connections do not get deprogrammed after dnport on AXSM-E card.

CSCec78432

FRSM-2T3 in a PXM1E chassis transmitting bogus a-bit alarm

CSCec79143

Watchdog resets on AXSM observed

CSCec79734

UPG5: APS adj line stuck in LOS after node rebuild

CSCec82151

MPEIT: pnCcb crash after clrsmcnf on MPSM oc3 card

CSCec83032

Internal Osc priority going back to default value after rebuild

CSCec87046

XGOC3-DEV: SPI Errors due to continuous upilm/dnilmi on AXSM-XG-oc3

CSCec88175

The redundant RPM card did not cover for failed primary.

CSCed01505

threshold for SCM task hanging should be less

CSCed01523

need to fix node rebuild due to standby in init but scm thinks ready

CSCed01970

tDispatch task should give up CPU for other low priority tasks.

CSCed02565

ATLAS Non-Fatal and QE1210 Not-Fatal errors on yred AXSM pair

CSCed09164

Conn mastered at AUSM/FRSM with frm-based policing not prop to slave

CSCed09942

Minor issue on displaying card alarm state

CSCed14131

switchcc fail because standby PXM xbar is degraded

CSCed15676

Channel showing OK state with Controller Abit = 0

CSCed17323

Duplicate entries for conns in the STATS files

CSCed22720

Active PXM1E switched over after Standby Combo back card inserted

CSCed22794

MAINT: P2MP SPVP and SPVC w/ same VPI can be committed on same port

CSCed23150

AXSM VSIS changes wrong IpConn LCN on new cmd with same VP in VPC

CSCed24987

Config upload for AUSM-8T1 sends AUSM-8E1/B as FCDescr and BCState as invalid

CSCed25756

APS 1:1 intra-card, direction change results in mode mismatch error

CSCed26797

oam-pvc manage, encapsulation and protocol ip not set via SNMP

CSCed30255

MAINT Connections not torn down in via node after dnpnport

CSCed30486

Line configuration changes do not get applied to standby APS lines

CSCed30887

Login denial of service with [infinite login prompt] script

CSCed31789

vnni port alarm propagation not there when vpc is down

CSCed33148

pnportsig none port comes up with wrong vpi range max of 255

CSCed33156

Popup msg:Cannot write to C:/, errno 0x38800f

CSCed33292

StdAbr table in the config upload file

CSCed34580

After changing sct file multiple times, cnfport failed to change sct

CSCed35995

Traffic stopped running on 500 ABR cons on AXSM-XG OC3

CSCed36616

AXSM fails to boot with 6 RPM-XF in a node

CSCed39429

ModConn for RPM connection is not actually modifying on the switch.

CSCed39860

snmpget is failing for the node, no chunks for snmp

CSCed40835

DAX cons went to failed state after resetting card

CSCed41216

LDNT: AXSM shows some memory allocation/free failures

CSCed41580

AXSM-XG OC48 stuck in empty reserved after switchred

CSCed41771

UPG5: XG-OC3 generate AIS upon enabling CC OAM on connection

CSCed42998

REG5: AXSM-XG ports in building vc after dn/upallport script

CSCed43063

cnfcdsct with non-default SCT does not read SCT file correctly

CSCed43168

standby CESM shown as active in dspcd output

CSCed43288

Paths and Ports down on XGOX48 due to lowerlayer down line is clear

CSCed44103

ifName varbind out of order for sonet 60126, 60127 traps

CSCed44352

REG5: No XG OC3 Xover after rem ACT/STBY FRU delaps ins stby FRU

CSCed45047

AXSM-XG reloads with fatal exception when adding control-vc

CSCed45061

PXM1E: Telnet sessions cannot be deleted

CSCed45294

UPG5: Mem leak from AXSM ilmiMain and tCpro tasks

CSCed46156

coredump: software error reset

CSCed46245

REG5: A lot of SHM-4-EE-EVT-ALOC_ERR found, maybe memory corrupted

CSCed46458

Invalid IMA Group parameters accepted by switch thru SNMP

CSCed49638

Diag Error: continuity check failed on AXSM-XG

CSCed50096

UPG5: Line stuck in RDI-P after add/del AnnexB APS on AXSM

CSCed51857

Priority bumping does not work as expected when LCNs are exhausted

CSCed53513

Unable to add VP connection on MPSM thru CWM/SNMP

CSCed53671

AXSM-XG pnports in auto config

CSCed55502

Memory block error in cutw

CSCed60203

Clock source is switched in NCDP mode after switchred

CSCed60564

AXSM-XG: Path config reverts to old config after switchredcd

CSCed64351

standby AXSM-XG rebooted after dn/upilmi

CSCed68047

PXM console stuck

CSCed69008

coredump on pxm after reset

CSCed69068

watchdog timeout coredump after resetcd on pxm

CSCed69628

REG5: NNI and VNNI links in auto config when many ports up on XG OC3

CSCed71340

AXSM-XG failures while coming up after node rebuild

CSCed72672

IT-Bug: trap 60622 not match with trap definition in FRSM12-12T3E3

CSCed77102

AXSM-E card went into Active-F state

CSCed84624

VPI0: connection fails; stops attempting after multiple switchcc

CSCed87053

Tnettask failed on AXSM causing card to go to Active-F

CSCed87160

vnni alarm did not clear on AXSM-XG

CSCed88171

Resource Alarm on standby PXM45

CSCed89400

XG-UPC pcr/scr/mcr can not be lowered than 60 cps in XG TALOS

CSCed89620

AXSM-XG offline diag fail on timeout 3 hours later

CSCed94243

Presence of RCON makes cards to go to Mismatch

CSCed94976

pnRedman got suspended: pxms in active-F and init

CSCee00913

8850 stops responding to snmp requests after upgrading PXM image

CSCee02920

AXSM-XG path in alarm after upgrade

CSCee16959

PXM45 not downloading enable.stats file to SMs after switchredcd

CSCin66401

DB showing back card type Mismatch for AXSM-XG though it is active.


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.

Documentation

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.

Obtaining Documentation

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.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

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:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

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 tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

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:

Cisco Systems
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:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

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:

http://www.cisco.com/go/psirt

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:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

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 — security-alert@cisco.com

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 — psirt@cisco.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:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

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:

http://www.cisco.com/techsupport

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:

http://tools.cisco.com/RPF/register/register.do


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:

http://www.cisco.com/techsupport/servicerequest

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:

http://www.cisco.com/techsupport/contacts

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:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

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:

http://www.ciscopress.com

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:

http://www.cisco.com/packet

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:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

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:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

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:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

Acronyms

Table 20 lists acronyms that have been referenced in these release notes.

.

Table 20 Acronyms Used in These Release Notes 

Acronym
Description

AXSM

ATM Switch Service Module. In these release notes, AXSM-A refers to the original AXSM card (A did not appear on the card), and AXSM/B refers to the newer AXSM/B card (B does appear on the card).

ABR

Available bit rate

APS

Automatic Protection Switching

CALEA/LI

Communications Assistance for Law Enforcement Act/ Lawful Intercept

CBSM

Cell bus service module. CBSMs were formerly called narrow band service modules (NBSMs).

CLI

Command Line Interface

CoS

Class of service

CUG

Closed User Group

CWM

Cisco Wide Area Network Manager

GE

Gigabit Ethernet

IAP

Intercept Access Point

IMA

Inverse Multiplexing over ATM

LANE

Local Area Network Emulation

LFI

Link Fragmentation Interleaving

MFR

Multi-Link Frame Relay

MLPPP/LFI

Multi-Link PPP

MPSM

Multi-Protocol Service Module

MTI

Multicast Tunnel Interface

NBSM

Narrow band service module (traditional name for cell bus service modules in Release 4 and higher)

P2MP

Point-to-Multipoint

PE

Provider Edge

PER

Product Enhancement Request

PNNI

Private Network-to-Network Interface

POS

Packet over SONET

POST

Power On Self-Test

PPP

Point-to-Point Protocol

PXM

Processor Switch Module

RPM

Route Processor Module

SFP

Small Form Factor Pluggable Unit

SM

Service Module

SONET

Synchronous Optical NETwork

SPVC

Soft permanent virtual connection

SRM

Service Resource Module

SVC

Switched virtual circuit

VPN

Virtual Private Network

VRF

VPN Routing / Forwarding

XF

Express Forwarding