Cisco MGX 8800 Series Switches

Table Of Contents

Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.2.10

Table of Contents

Overview

About Release 5.2.10

Type of Release

Locating Software Updates

Features and Enhancements in Release 5.2.10

Features in Release 5.2.00

MGX-VXSM-T3 Card

AXSM-8-622-XG Card

Graceful Upgrades to AXSM-XG Cards

Multilink PPP on the MPSM-T3E3-155 Card

PXM45/C Support in the MGX 8830/B Chassis

Mobile PNNI Support

Compression and Multiplexing Support for RPM-PR Cards

Service Class Template (SCT) File Information

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-XG

MPSM-T3E3-155

MPSM-16-T1E1

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 EVDO

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

Product IDs, Card Types, and APS Connectors

New and Changed Commands

Mobile PNNI

Graceful Upgrade

Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card

Limitations, Restrictions, and Notes

MGX Chassis Bandwidth Limitations

Bandwidth Limits

Card Placement Guidelines

Bandwidth Oversubscription

PXM1E Switch Limitations

PXM1E Hardware Limitations

PXM1E Reserved VCIs

PXM1E Point to Multipoint Support

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 Channel Loopback Limitation

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

Known Anomalies in Release 5.2.10

Resolved Anomalies in Release 5.2.10

Status Changed Anomalies

Resolved Anomalies in Previous Releases

Resolved Anomalies in Release 5.2.00

Resolved Anomalies in Release 5.1.20

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

Documentation Updates

Cisco PNNI Network Planning Guide for MGX and SES Products Updates

Cisco Frame Relay Services (FRSM/MPSM-8-T1E1) Configuration Guide and
Command Reference for MGX Switches, Release 5.2

Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 Updates

Appendix A: Downloading and Installing Software Upgrades

Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG

Supported Configurations

Limitations

Preparing to Upgrade

Converting Custom SCTs

Graceful Upgrade Procedure

Non-Graceful Upgrade Procedure

Appendix B: MPSM Licensing

MPSM Licensing Information

MPSM License Overview

PXM License Pool

Viewing License Data

Viewing All Node Licenses

Viewing Licenses for a Specific MPSM Card Type

Viewing Licenses for All Cards

Viewing Licenses for a Specific Card

Viewing License Updates History

Viewing License Alarms

Adding Licenses Obtained from Cisco.com

Viewing the Product Authorization Key Online

Obtaining Node IDs

Requesting Licenses

Adding Licenses to the License Pool

Moving Licenses from an MPSM Card to the License Pool

Allocating Feature Licenses to a Card

Recovering Feature Licenses That are Not In Use

Saving and Restoring the License Configuration

Transferring Licenses Between Switches

Transferring Licenses

MPSM License Alarms

Node License Alarms

Slot License Alarms

Grace Period

Rekeying Feature Licenses

MPSM License Concepts and Terms

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 Release 5.2.10

---

Part Number OL-9187-01 Revision E0, March, 2007

Table of Contents

Overview

These release notes contain the following sections:

•About Release 5.2.10

•Features in Release 5.2.00

•Features in Release 5.1.20

•Features in Release 5.1.00

•System Requirements

•New and Changed Commands

•Limitations, Restrictions, and Notes

•Installation and Upgrade Procedures

•Anomalies in Release 5.2.10

•Resolved Anomalies in Previous Releases

•Documentation Updates

•Appendix A: Downloading and Installing Software Upgrades

•Appendix B: MPSM Licensing

•Documentation

•Obtaining Documentation

•Documentation Feedback

•Cisco Product Security Overview

•Obtaining Technical Assistance

•Obtaining Additional Publications and Information

•Acronyms

About Release 5.2.10

Version .206 of Release 5.2.10 is a patch release that does not introduce new features. The resolved anomalies for Version .206 are listed in Table 10.

Version .204 of Release 5.2.10 is a patch release that does not introduce new features. The resolved anomalies for Version .204 are listed in Table 11.

Version .201 of Release 5.2.10 adds Unique Device Identifier (UDI) compliance for the Cisco MGX 8830/B chassis and backplane, and Version .202 changes the Cisco product identifier from MGX8830/B to MGX8830/B-CH. The resolved anomalies for Version .202, .201, and .200 are listed in Table 12, Table 13, and Table 14.

These release notes describe the system requirements and limitations that apply to Release 5.2.10 of the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Multiservice Switches, and provide Cisco support information.

These releases notes contain updates to the MPSM Licensing appendix of the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2. See Appendix B: MPSM Licensing.

Type of Release

Release 5.2.10 is a software release for the following Cisco MGX switches:

•MGX 8830 (PXM1E)

•MGX 8830/B (PXM1E and PXM45)

•MGX 8850 (PXM1E and PXM45)

•MGX 8850/B (PXM1E and PXM45)

•MGX 8950 (PXM45)

Locating Software Updates

Release 5.2.10 software is located at:

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

Route Processor Module (RPM) Cisco IOS software images are located at:

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

Features and Enhancements in Release 5.2.10

Version .201 of Release 5.2.10 adds UDI compliance for the Cisco MGX 8830/B chassis, and Version .202 changes the Cisco product identifier (PID) from MGX8830/B to MGX8830/B-CH. The UDI consists of the Cisco product identifier, version identifier (VID), and serial number (SN).

The show inventory command displays the PID, VID, and SN for each product in the chassis. The following example shows typical UDI information for the Cisco MGX 8830/B chassis:

M8830_SF.1.PXM.a > show inventory

NAME: "1"     , DESCR: "Cisco MGX8830 Model B, 14 Slot chassis"

PID: MGX8830/B-CH, VID:    , SN: -----

NAME: ""      , DESCR: "Cisco MGX8830 Model B Backplane"

PID: MGX8830/B-CH, VID: V01, SN: SCA09380009

Features in Release 5.2.00

Release 5.2.00 has the following features:

•MGX-VXSM-T3 Card

•AXSM-8-622-XG Card

•Graceful Upgrades to AXSM-XG Cards

•Multilink PPP on the MPSM-T3E3-155 Card

•PXM45/C Support in the MGX 8830/B Chassis

•Mobile PNNI Support

•Compression and Multiplexing Support for RPM-PR Cards

•Service Class Template (SCT) File Information

MGX-VXSM-T3 Card

Release 5.2.00 introduces a third VXSM card for the support of T3 lines. The card consists of a front card with six T3 ports and a half height back card with three T3 ports. The front card can be configured with either a single back card or two back cards.

AXSM-8-622-XG Card

The AXSM-8-622-XG is an 8-port OC-12/STM-4 card that supports clear-channel OC-12c/STM-4 or OC-12/STM-4 channelized down to OC-3c/STM-1 and DS3. This card complements the family of AXSM-XG cards, which includes the AXSM-16-155-XG, AXSM-4-2488-XG, and AXSM-1-9953-XG.

The AXSM-8-622-XG card has the following functionality:

•Independent channelization of each line.

•Common software for the MGX 8850, MGX 8830, and MGX 8950 chassis

•Maximum bandwidth is 2.4 Gbps when installed in a MGX 8850 or MGX 8830 chassis

•Maximum bandwidth is full card bandwidth when installed in MGX 8950 chassis

•Trap generation to CWM signals configuration changes and alarm status

•VSI support for PNNI and MPLS controllers

•Up to 128 total logical interfaces

•Up to 16 Classes of Service per logical interface

•Trunk and port interfaces on same card

•Virtual trunk support

•Resource Management

–Interface resource partitioning among PNNI and MPLS controllers

–Dynamic resource partitioning

–Ingress CAC of logical ports based on maximum chassis slot bandwidth

•Connection Management

–Up to 128K connections (VCs+VPs)

–Up to 64 groups per card, divisible into any mix of OC-12c/STM-4, OC-3c/STM-1, and DS-3 channels up to the total card capacity

–SVC/SVP, SPVC/SPVP and LVC

–Symmetric and asymmetric connections

–VC merge for AAL 5 traffic

–Point to multipoint connections

•Traffic Management

–Enhanced CAC support

–Congestion management

–Per VC/VP traffic policing

–Per VC/VP traffic shaping

–ABR with VS/VD

•OAM support: compliance with ITU-T I.610

•ILMI: compliance with ATM Forum 4.0

•Statistics: similar to AXSM-E

•Redundancy

–Card redundancy using hot standby

–APS backup with 1:1 and 1+1, inter-card and intra-card, and facility protection with single front card and two back cards

•Online and offline diagnostics

•Feeder support

–You can directly connect feeder nodes to unchannelized AXSM-8-622-XG ports.

–Supports all feeder functions available with AXSM and AXSM/B cards.

•BPX product support

The AXSM-8-622-XG supports direct connection to BPX nodes with all ENNI functions available on AXSM and AXSM/B.

The AXSM-8-622-XG card has the following restrictions:

•All lines on the same bay must have the same SONET/SDH configuration

•Up to 1 ms of traffic loss after reconfiguration of lines/paths on the same bay

•The AXSM-XG does not support AutoRoute CoS queues

Graceful Upgrades to AXSM-XG Cards

In this release, you can gracefully upgrade AXSM, AXSM/B and AXSM-E cards to AXSM-XG cards. The AXSM-16-155-XG and AXSM-8-622-XG cards have a higher port density than the equivalent AXSM-E cards, and the AXSM-16-155-XG and AXSM-8-622-XG have better traffic management support than their AXSM/B counterparts.

Graceful upgrades simplify the process of migrating to the newer AXSM-XG cards. During the upgrade, the MGX control processor transfers the configuration/connection database from the previously installed AXSM card to the new AXSM-XG, which preserves all connection configurations. The upgrade process might cause an outage of up to four minutes.

You can install and operate any number of AXSM-XG cards in conjunction with AXSM, AXSM/B or AXSM-E in an MGX 8850 chassis equipped with the PXM45 processor. You can install and operate any number of AXSM-XG cards in conjunction with AXSM/B in an MGX 8950.

Card redundancy is supported only between identical front and back card pairs. For example, an AXSM-16-155-XG can only be redundant to another AXSM-16-155-XG, where the two front cards use an identical set of back cards.

For more information about the upgrade procedure, see Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG.

Multilink PPP on the MPSM-T3E3-155 Card

This release adds Multilink PPP (MLPPP) to the MPSM-T3E3-155 card. MLPPP includes the following capabilities:

•Support for MLPPP

•PPPmux on a MLPPP bundle basis

•Interworking between MLPPP and PPPoATM

•NxDS0 and DS1 PPP links

•Maximum of 84 PPP links per card

•Maximum of 84 MLPPP bundles per card

•Maximum of 6 PPP links per MLPPP bundle

•Dynamic (auto) PVC bandwidth on a MLPPP bundle basis

•Layer 2 QoS to minimize delay of delay sensitive traffic and prioritize control messages

•Support for three strict priority queues

•Support for the CDMA2000 and EVDO

•1:1 hot standby front card redundancy

•Operational load management

The MLPPP feature has the following restriction:

•Supported on the BNC-3-T3E3 back card only and only in channelized mode. In other words, MLPPP is not supported for E3 in any form or unchannelized T3.

PXM45/C Support in the MGX 8830/B Chassis

A PXM45/C controller in an MGX8830/B chassis provides support for a selection of narrowband and broadband interfaces in an 8-slot chassis. The PXM45/C controller's 45Gbps switch matrix makes it possible to aggregate and switch traffic from a mix narrowband, DS3/E3, OC-3c/STM-1 and OC-12/STM-4 ATM ports, and simplifies the process of scaling a network node as connection counts increase.

Mobile PNNI Support

This release adds the Mobile PNNI feature to the existing PNNI functionality. Generally a PNNI network has a fixed hierarchy where each element has a fixed point of attachment. Mobile PNNI extends a fixed network infrastructure to mobile ATM switches that are roaming in the network. To maintain connectivity when the location of the mobile ATM switch changes, mobile switches are allowed to dynamically change peer group membership. To implement this feature, you establish a link to the fixed network; the mobile network then finds the proper peer group and hierarchy and joins the network.

Mobile PNNI allows each mobile network to build its own PNNI hierarchy and integrate the hierarchy of the fixed network as a logical group node (LGN). In the context of mobile PNNI, it is called Mobile LGN. A mobile logical group node has the capability to dynamically change its membership from one peer group to another as it attaches to different fixed switches. A mobile logical group node is only allowed to join a parent peer group of one of the fixed switches.

The ATM forum describes mobile PNNI in publication AF-RA-0123.000, PNNI addendum for mobility extensions Version 1.0, which is available at the following location:

ftp://ftp.atmforum.com/pub/approved-specs/af-ra-0123.000.pdf

Compression and Multiplexing Support for RPM-PR Cards

The MGX-RPM-1FE-CP (one-port, Fast Ethernet-Co-processor) back card is an MGX8850/RPM-PR back card that off-loads the following processes from the Route Processor Module (RPM-PR):

•Compression/decompression of Real-time Transport Protocol (RTP)/User Datagram Protocol (UDP) headers (cRTP/cUDP)

•Multiplexing/demultiplexing of Point-to-Point Protocol (PPP) frames

This feature was previously supported on PXM1 systems only. This release extends this capability to PXM1E/PXM45 systems.

For more information, refer to:

http://cisco.com/en/US/products/hw/routers/ps4062/prod_module_install_config_guide09186a00801f42d7.html

Service Class Template (SCT) File Information

This section contains SCT file information for Release 5.2.00.

PXM1E

The default SCTs provided are as follows:

•SCT 5—Policing enabled. In general, this is for use on UNI ports.

•SCT 6—Policing disabled. In general, this is for use on NNI ports.

The filenames and checksums for the SCT files are as follows:

•PXM1E_SCT.PORT.5.V1: Checksum is = 0xa287c4ee= 2726806766

•PXM1E_SCT.PORT.6.V1: Checksum is = 0x79f6c93d= 2046216509

•PXM1E_SCT.PORT.52.V1: Checksum is = 0x199550ec= 429215980

•PXM1E_SCT.PORT.53.V1: Checksum is = 0xf6d53485= 4141167749

•PXM1E_SCT.PORT.54.V1: Checksum is = 0xa39611dc= 2744521180

•PXM1E_SCT.PORT.55.V1: Checksum is = 0x11a518f1= 296032497

Notes:

1. PXM1E does not support CARD SCT.

2. ABR VSVD parameters are not supported due to hardware limitation.

3. The above PXM1E SCT files apply to MGX 8850 (PXM1E) and MGX 8830

4. Use SCTs with VC thresholds of at least 50000 microseconds for the VSI signaling service type. New SCTs 5,6 and 54, 55 (SCTs for the T3/E3, Combo cards, and IMA group links, respectively) update the VC threshold and have minor version = 1. Upgrade your custom SCTs to the new recommended VC thresholds and change the minor version. You can gracefully upgrade an SCT with a minor version change without interrupting traffic. The SCT chapter of the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 explains how to upgrade a SCT file to a new minor version.

AXSM and AXSM/B

The AXSM and AXSM/B SCTs have the following characteristics:

•SCT 2—Policing enabled, PNNI

•SCT 3—Policing disabled, PNNI

•SCT 4—Policing enabled, MPLS and PNNI

•SCT 5—Policing disabled, MPLS and PNNI

The filenames and checksums for the SCT files are as follows:

•AXSM_SCT.PORT.0.V1:Cchecksum is = 0x6aadd6c6= 1789777606

•AXSM_SCT.PORT.2.V1: Checksum is = 0x78ccfb22= 2026699554

•AXSM_SCT.PORT.3.V1: Checksum is = 0x987919a7= 2558073255

•AXSM_SCT.PORT.4.V1: Checksum is = 0x775bfaa2= 2002516642

•AXSM_SCT.PORT.5.V1: Checksum is = 0xe84c696a= 3897321834

•AXSM_SCT.CARD.0.V1: Checksum is = 0x6aadd6c6= 1789777606

•AXSM_SCT.CARD.2.V1: Checksum is = 0x78ccfb22= 2026699554

•AXSM_SCT.CARD.3.V1: Checksum is = 0x987919a7= 2558073255

•AXSM_SCT.CARD.4.V1: Checksum is = 0x775bfaa2= 2002516642

•AXSM_SCT.CARD.5.V1: Checksum is = 0xe84c696a= 3897321834

To confirm that the checksum of the SCT file and the file on the node match, enter dspsctchksum <filename>.

AXSM-E

The AXSM-E SCTs have the following characteristics:

•CARD and PORT SCT 5—Policing enabled for PNNI, disabled for MPLS

•PORT SCT 6—Policing disabled, used for PNNI ports.

•CARD and PORT SCT 52—Policing enabled on PNNI, disabled on MPLS

•PORT SCT 53—Policing disabled on PNNI and MPLS

•PORT SCT 54— Policing enabled on PNNI, disabled on MPLS

•PORT SCT 55—Policing disabled on PNNI and MPLS

The following are checksums for the AXSM-E SCT file:

•AXSME_SCT.PORT.5.V1: Checksum is = 0x793c56d0= 2033997520

•AXSME_SCT.PORT.6.V1: Checksum is = 0xe92db9a5= 3912087973

•AXSME_SCT.PORT.52.V1: Checksum is = 0x51241b7a= 1361320826

•AXSME_SCT.PORT.53.V1: Checksum is = 0x34bdf8b9= 884865209

•AXSME_SCT.PORT.54.V1: Checksum is = 0xb5df2c5c= 3051301980

•AXSME_SCT.PORT.55.V1: Checksum is = 0xc5d355c8= 3318961608

•AXSME_SCT.CARD.5.V1: Checksum is = 0x793c56d0= 2033997520

•AXSME_SCT.CARD.52.V1: Checksum is = 0x972810ac= 2535985324

AXSM-XG

The AXSM-XG SCTs have the following characteristics:

•CARD SCT 2—Policing disabled on PNNI and MPLS. Applied in ingress direction based on backplane bandwidth.

•PORT SCT 100 (OC-192), 200 (OC-48), 300 (OC-12), 400 (OC-3), 500 (DS3)—Policing disabled on PNNI and MPLS

•PORT SCT 101, 201, 301, 401, 501—Policing disabled on PNNI and enabled on MPLS

•PORT SCT 110, 210, 310, 410, 510—Policing enabled on PNNI and disabled on MPLS

•PORT SCT 111, 211, 311, 411, 511—Policing enabled on PNNI and enabled on MPLS

The SCT filenames and checksums are:

•AXSMXG_SCT.PORT.100.V1: Checksum is = 0x2342cfdf= 591581151

•AXSMXG_SCT.PORT.200.V1: Checksum is = 0x2814a68d= 672441997

•AXSMXG_SCT.PORT.300.V1: Checksum is = 0x7e2bf17= 132300567

•AXSMXG_SCT.PORT.400.V1: Checksum is = 0xa602de0a= 2785205770

•AXSMXG_SCT.PORT.500.V1: Checksum is = 0xd6d07790= 3603986320

•AXSMXG_SCT.PORT.101.V1: Checksum is = 0x7f3935c0= 2134455744

•AXSMXG_SCT.PORT.201.V1: Checksum is = 0x6e41c693= 1849804435

•AXSMXG_SCT.PORT.301.V1: Checksum is = 0x98ba0700= 2562328320

•AXSMXG_SCT.PORT.401.V1: Checksum is = 0xae33e067= 2922635367

•AXSMXG_SCT.PORT.501.V1: Checksum is = 0x11988936= 295209270

•AXSMXG_SCT.PORT.110.V1: Checksum is = 0xd431808= 222500872

•AXSMXG_SCT.PORT.210.V1: Checksum is = 0x2835432c= 674579244

•AXSMXG_SCT.PORT.310.V1: Checksum is = 0x4f4c4a34= 1330399796

•AXSMXG_SCT.PORT.410.V1: Checksum is = 0xe4a7ed75= 3836210549

•AXSMXG_SCT.PORT.510.V1: Checksum is = 0xecc0047c= 3972007036

•AXSMXG_SCT.PORT.111.V1: Checksum is = 0x68397de6= 1748598246

•AXSMXG_SCT.PORT.211.V1: Checksum is = 0x6e61632e= 1851876142

•AXSMXG_SCT.PORT.311.V1: Checksum is = 0xdf23911a= 3743650074

•AXSMXG_SCT.PORT.411.V1: Checksum is = 0xecd7efce= 3973574606

•AXSMXG_SCT.PORT.511.V1: Checksum is = 0xe920f6c3= 3911251651

•AXSMXG_SCT.CARD.2.V1: Checksum is = 0xb58b69a8= 3045812648

•AXSMXG_SCT.CARD.3.V1: Checksum is = 0xb4e1239a= 3034653594

MPSM-T3E3-155

The SCT files for the MPSM-T3E3-155 card have the following characteristics:

•Port SCT 1—Optimized for UNI connections that use 5 or more T1/E1 lines.

•Port SCT 2—Optimized for NNI connections that use 5 or more T1/E1 lines.

•Port SCT 3—Optimized for IMA or MFR UNI connections that use 4 T1/E1 lines or less.

•Port SCT 4—Optimized for IMA or MFR NNI connections that use 4 T1/E1 lines or less.

The SCT filenames and checksums are:

•MPSM155_SCT.PORT.1.V1: Checksum is = 0x88569bf5= 2287377397

•MPSM155_SCT.PORT.2.V1: Checksum is = 0x21e18676= 568428150

•MPSM155_SCT.PORT.3.V1: Checksum is = 0x3cb04789= 1018185609

•MPSM155_SCT.PORT.4.V1: Checksum is = 0xd63b320a= 3594203658

•MPSM155_SCT.CARD.1.V1: Checksum is = 0x808b3c54= 2156608596

MPSM-16-T1E1

The SCT files for the MPSM-16-T1E1 card have the following characteristics:

•Port SCT 3—Use for UNI ports less than or equal to 4 T1 in bandwidth.

•Port SCT 4—Use for NNI ports less than or equal to 4 T1 in bandwidth.

The MPSM-16-T1E1 SCT filenames and checksums are:

•MPSM16T1E1_SCT.PORT.3.V1: Checksum is = 0x3cb04789= 1018185609

•MPSM16T1E1_SCT.PORT.4.V1: Checksum is = 0xd63b320a= 3594203658

•MPSM16T1E1_SCT.CARD.1.V1: Checksum is = 0x808b3c54= 2156608596

Features in Release 5.1.20

Release 5.1.20 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 EVDO

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 (MLPPP)

•Any Service Any Port

General Features

The MPSM-16-T1E1 card supports the following general features:

•Physical interfaces configurable 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.

•Support for SPVCs, SVCs, SPVPs, and PVPs.

•Support for card and port service class templates.

•Maximum of 2000 connections. Any combination of Frame Relay and ATM connections is allowed.

•Support for 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. The MPSM-16-T1E1 cannot be the CE end point for ATM-CE connections because the MPSM-16-T1E1 does not support circuit emulation.

•Connections provisioned on the PNNI control plane on the MGX 8850 platform using the MSF switch architecture based VSI (Virtual Switch Interface).

•Support for provisioning Extended Permanent Virtual Circuits (XPVC) endpoints. A XPVC is an end-to-end virtual circuit (VC) that spans multiple networks using AutoRoute and PNNI protocols.

•Support for 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:

•Support for IMA version 1.0 and 1.1 with fallback and auto restart support.

•Support for up to 16 IMA groups.

•Support for 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.

•Support for CTC and ITC clocking modes.

Frame Relay Features

The MPSM-16-T1E1 card supports the following Frame Relay features:

•Supports the bandwidth of 16 T1/E1 lines.

•Ports can be 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 time slots).

•Support for 56 Kbps ports.

•Support for a total of 496 Frame Relay logical ports (16 x 31 time slots in E1).

•Maximum of 2000 Frame Relay connections.

•FR UNI, FR NNI, and Frame Forwarding interfaces.

•Ingress cut through mode of frame processing (No waiting 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.

•Support for 2-byte Frame Relay header.

•Ratio based egress servicing.

•Support for FRF.5 (NIW) and FRF.8.1 (SIW) standards.

•LMI and Enhanced LMI on all Frame Relay interfaces.

•Frame Relay traffic management features.

MLPPP Features

The MPSM-16-T1E1 card supports the following Mulitlink PPP features:

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

•Support for 4 strict priority queues.

•Support for CDMA2000 applications with the MWR 1900 and the RPM-XF.

•1:N cold standby front card redundancy supported.

•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 EVDO

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

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 through 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 uses 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 use 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 conn-trace 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 is used.

Table 1 lists the PNNI product enhancement requests incorporated in this release.

Table 1 PNNI Product Enhancements

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 MPG (multi-peer group) 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 nonsegment 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 Cisco IOS software products that are compatible with Release 5.2.10.

Table 2 Release 5.2.10 Compatibility Matrix 

Switch or Component	Compatible Software Version
MGX 8230 (PXM1) MGX 8250 (PXM1) MGX 8850 (PXM1)	MGX1.3.14 MGX 1.3.12 MGX 1.3.11
MGX 8830/B (PXM45/C)	MGX 5.2.10 MGX 5.2.00
MGX 8830 (PXM1E) MGX 8830/B (PXM1E) MGX 8850 (PXM1E and PXM45) MGX 8850/B (PXM1E and PXM45) MGX 8950 (PXM45)	MGX 5.2.10 MGX 5.2.00 MGX 5.1.20 (202)
BPX Switch Software	Switch Software 9.4.12 Switch Software 9.3.51 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)T9 12.3(11)T7 12.3(7)Tx
IOS RPM-XF	12.3(11)T9 12.3(11)T7 12.3(7)Tx
VISM-PR	3.3.25 3.3.20 3.3.10 3.3
VXSM	5.2.10 5.2.00

MGX and RPM Software Version Compatibility Matrix

Table 3 lists the software that is compatible for use in a switch running Release 5.2.00 software.

Table 3 MGX and RPM Software Version Compatibility Matrix 

Board Pair	Boot Software	Runtime Software
PXM45/B	pxm45_005.002.010.204_bt.fw	pxm45_005.002.010.206_mgx.fw
PXM45/C	pxm45_005.002.010.204_bt.fw	pxm45_005.002.010.206_mgx.fw
PXM45/C MGX 8830/B chassis	pxm45_005.002.010.204_bt.fw	pxm45_005.002.010.206_m30.fw
PXM1E-4-155 MGX 8850 (PXM1E) chassis	pxm1e_005.002.010.204_bt.fw	pxm1e_005.002.010.204_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.002.010.204_bt.fw	pxm1e_005.002.010.204_m30.fw
PXM1E-8-T3E3 MGX 8830 chassis
PXM1E-8-155 MGX 8830 chassis
PXM1E-COMBO MGX 8830 chassis
AXSM-1-2488	axsm_005.002.010.200_bt.fw	axsm_005.002.010.200.fw
AXSM-16-155
AXSM-4-622
AXSM-16-T3/E3
AXSM-1-2488/B	axsm_005.002.010.200_bt.fw	axsm_005.002.010.200.fw
AXSM-16-155/B
AXSM-4-622/B
AXSM-16-T3/E3/B
AXSM-2-622-E	axsme_005.002.010.200_bt.fw	axsme_005.002.010.200.fw
AXSM-8-155-E
AXSM-16-T3E3-E
AXSM-32-T1E1-E
AXSM-16-155-XG	axsmxg_005.002.011.200_bt.fw	axsmxg_005.002.011.201.fw
AXSM-8-622-XG
AXSM-4-2488-XG
AXSM-1-9953-XG
MPSM-16-T1E1	mpsm16t1e1_005.002.010.200_bt.fw	mpsm16t1e1_005.002.010.200.fw
MPSM-16-T1E1-PPP	mpsm16t1e1_005.001.020.200_bt.fw1	mpsm16t1e1ppp_005.001.020.202.fw
MPSM-T3E3-155	mpsm155_005.002.010.200_bt.fw	mpsm155_005.002.010.200.fw
MPSM-T3E3-155-PPP	mpsm155_005.002.010.200_bt.fw	mpsm155ppp_005.002.010.200.fw
MPSM-8-T1E1	mpsm_t1e1_030.002.010.200_bt.fw	mpsm_t1e1_030.002.010.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.002.010.200.fw
AX-CESM-8T1	cesm_8t1e1_CE8_BT_1.0.02.fw	cesm_8t1e1_022.002.010.200.fw
MGX-CESM-8T1/B	cesm_8t1e1_CE8_BT_1.0.02.fw	cesm_8t1e1_022.002.010.200.fw
MGX-AUSM-8T1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	ausm_8t1e1_022.002.010.200.fw
MGX-AUSM-8E1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	ausm_8t1e1_022.002.010.200.fw
AX-FRSM-8T1	frsm_8t1e1_FR8_BT_1.0.06.fw	frsm_8t1e1_022.002.010.200.fw
AX-FRSM-8E1	frsm_8t1e1_FR8_BT_1.0.06.fw	frsm_8t1e1_022.002.010.200.fw
AX-FRSM-8T1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	frsm_8t1e1_022.002.010.200.fw
AX-FRSM-8E1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	frsm_8t1e1_022.002.010.200.fw
MGX-FRSM-HS2/B	frsm_vhs_VHS_BT_1.0.07.fw	frsm_vhs_022.002.010.200.fw
MGX-FRSM-2CT3	frsm_vhs_VHS_BT_1.0.07.fw	frsm_vhs_022.002.010.200.fw
MGX-FRSM-2T3E3	frsm_vhs_VHS_BT_1.0.07.fw	frsm_vhs_022.002.010.200.fw
MGX-RPM-PR-256	rpm-boot-mz.123-11.T9	rpm-js-mz.123-11.T9
MGX-RPM-PR-512	rpm-boot-mz.123-11.T9	rpm-js-mz.123-11.T9
MGX-RPM-XF-512	rpmxf-boot-mz.123-11.T9	rpmxf-p12-mz.123-11.T9
MGX-VXSM-155	vxsm_005.002.010.201_bt.fw	vxsm_005.052.010.201.fw (CALEA image) vxsm_005.002.010.201.fw (non-CALEA image)
MGX-VXSM-T3
MGX-VXSM-T1E1
MGX-VISM-PR-8T1	vism_8t1e1_VI8_BT_3.2.00.fw	vism-8t1e1-003.053.025.201.fw (CALEA image) vism-8t1e1-003.003.025.201.fw (non-CALEA image)
MGX-VISM-PR-8E1

1 Obtain the MPSM-16-T1E1-PPP version 005.001.020.200 boot code from the Release 5.1.20 bundle that is located on Cisco.com.

SNMP MIB Release

The SNMP MIB file for release 5.2.10 is mgx8850rel5210mib.tar.

---

Note SNMP manuals are replaced by the online MIB tool at :
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

Hardware in Release 5.2.10

Release 5.2.10 does not introduce new hardware.

Product IDs, Card Types, and APS Connectors

The following tables list part number and revision compatibility for front and back cards in the MGX chassis. The table also lists whether an APS connector is required.

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

Front Card Type	Minimum 800 Part Number and Revision	Back Card Types	APS Con	Minimum 800 Part Number and Revision	MGX 8850 and 8850/B PXM45	MGX 8850 and 8850/B PXM1E	MGX 8830/B PXM45	MGX 8830 and 8830/B 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	Yes	800-21518-03-A0	—	x	—	x	—
		SMFIR-1-155- SFP	Yes	10-1283-01-A0
		SMFLR-1-155- SFP	Yes	10-1280-01-A0
		MMF-1-155-SFP		10-1308-01-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	—	800-18698-02-A0	—	x	—	x	—
		SMFIR-1-155- SFP	—	10-1283-01-A0
		SMFLR-1-155- SFP	—	10-1280-01-A
		MMF-1-155- SFP	—	10-1308-01-A0
		PXM-UI-S3/B	—	800-21557-01-A0

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

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

Front Card Type	Minimum 800 Part Number and Revision	Back Card Types	APS Con	Minimum 800 Part Number and Revision	MGX 8850 and 8850/B PXM45	MGX 8850 and 8850/B PXM1E	MGX 8830/B PXM45	MGX 8830 and 8830/B 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
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)	x1	x1	—
		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)	—	—	—
RCON-1TO3-8830	800-23197-01	—	—	—	—	—	x	x	—

1 The MGX 8830/B chassis must use the RED-16-T1E1 back card for 1:N redundancy.

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

Front Card Type	Minimum 800 Part Number and Revision	Back Card Types	APS Con	Minimum 800 Part Number and Revision	MGX 8850 and 8850/B PXM45	MGX 8850 and 8850/B PXM1E	MGX 8830/B PXM45	MGX 8830 and 8830/B 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	—	800-19913-04-A0	—	—	—	—	x
		SMFSR-1-2488-SFP		10-1421-03
		SMFLR-1-2488-SFP		10-1742-01
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-8-622-XG	800-21445-06	SFP-4-622	Yes	800-22143-05	x	—	x	—	x1
AXSM-4-622	800-05774-09-B0	SMFIR-2-622 SMFLR-2-622	Yes	800-05383-01-A1	x	—	—	—	—
			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	Yes	800-21518-03-A0	x	—	x	—	x1
		SMFIR-1-155- SFP		10-1283-01-A0
		SMFLR-1-155- SFP		10-1280-01-A0
		MMF-1-155- SFP		10-1308-01-A0
		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
MGX8950- EXTDR-CON	800-23813-03-A0	—	—	—	—	—	—	—	x1

1 MGX8950-EXTDR-CON is required for AXSM-16-155-XG and AXSM-8-622-XG cards in the Cisco MGX 8950 chassis.

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

Front Card Type	Minimum 800 Part Number and Revision	Back Card Types	APS Con	Minimum 800 Part Number and Revision	MGX 8850 and 8850/B PXM45	MGX 8850 and 8850/B PXM1E	MGX 8830/B PXM45	MGX 8830 and 8830/B 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	—
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	—	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 AX-R-RJ48- 8T1	—	800-02286-01-A0	x	x	—	x	—
			—	800-02288-01-A0
MGX-VXSM-155	800-15121-06-A0	VXSM-BC-4-155	—	800-21428-06-A0	x	—	—	—	—
MGX-VXSM-T3	800-4074-02- A0	VXSM-BC-3T3	—	800-3095-03	x	—	—	—	—
MGX-VXSM-T1E1	800-24073-02-A0	VXSM-BC- 24T1E1	—	800-23088-03-A0	x	—	—	—	—
MGX-VISM-PR- 8T1	800-07990-02-A0	AX-RJ48-8T1	—	800-02286-01-A0	x	x	x	x	—
		AX-R-RJ48- 8T1	—	800-02288-01-A0
MGX-VISM-PR- 8E1	800-07991-02-A0	AX-SMB-8E1		800-02287-01-A0	x	x	x	x	—
		AX-R-SMB- 8E1		800-02410-01-A0
		AX-RJ48-8E1		800-02286-01-A0
		AX-R-RJ48- 8E1		800-02409-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	x	x	—	x	—
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 summarizes the correct APS connector for each MGX chassis and front card.

•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 later. 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 display "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 8830/B (PXM45)	—	—	AXSM-16-155-XG AXSM-8-622-XG AXSM-2-622-E	—
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.

New and Changed Commands

This sections lists the updated commands for the following features:

•Mobile PNNI

•Graceful Upgrade

•Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card

Mobile PNNI

The following commands are modified to support mobile PNNI configuration:

•addpnni-node

•cnfpnni-intf

•cnfpnni-routing-policy

•dsppnni-intf

•dsppnni-node

•dsppnni-ptse

•dsppnni-routing-policy

For complete command information, see the Cisco MGX 8800/8900 Series Command Reference, Release 5.2.

Graceful Upgrade

This section lists the updated commands for the AXSM-XG graceful upgrade feature. For more information about the upgrade procedure, see Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG.

The following commands are modified to support the graceful upgrade feature:

•loadrev

•runrev

For complete command information, see the Cisco MGX 8800/8900 Series Command Reference, Release 5.2.

Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card

Online insertion or removal (OIR) of the MGX-RPM-1FE-CP back card for the RPM-PR card requires the following RPM-PR commands:

•Privileged exec mode command hw-module slot <slot> {stop | start}

•Configuration mode command hw-module slot <slot> shutdown {powered | unpowered}

To perform online insertion or removal in privileged exec mode:

---

Step 1 Enter hw-module slot <slot> stop

Step 2 Perform online insertion or removal.

Step 3 Enter hw-module slot <slot> start

---

To perform online insertion or removal in configuration mode:

---

Step 1 Enter hw-module slot <slot> shutdown powered | unpowered

Step 2 Perform online insertion or removal.

Step 3 Enter no hw-module slot <slot> shutdown powered | unpowered

---

Limitations, Restrictions, and Notes

This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.2.10.

MGX Chassis Bandwidth Limitations

The total bandwidth of all cards and configured ports in your MGX switch must not exceed the total switch capacity. If you install more cards or configure more ports than your switch can support, your switch may drop traffic. This section describes the bandwidth limits, card placement, and oversubscription options for narrowband cards. It also provides the solution for anomaly CSCei02096.

Bandwidth Limits

An MGX 8850 (PXM45) chassis supports up to OC-12 aggregate bandwidth for narrowband cards, within the following limitations:

•Each pair of slots in the upper bay supports a total of OC-6 aggregate cellbus throughput.

•Each pair of slots in the lower bay supports a total of OC-6 aggregate cellbus throughput.

•Each half of the lower bay can support total OC-6 aggregate cellbus bandwith.

•The left half of the switch can support a total of OC-9 aggregate cellbus throughput. This includes both the top and bottom bays, combined.

•The right half of the switch can support a total of OC-9 aggregate cellbus throughput. This includes both the top and bottom bays, combined.

---

Note These limits do not apply to broadband cards such as the AXSM, AXSME, AXSM-XG, RPM-XF and VXSM. Broadband cards use a serial bus, rather than the cell bus.

---

Card Placement Guidelines

To fully use the bandwidth of MPSM-T3E3-155 cards, install cards according to the following guidelines:

•Install MPSM-T3E3-155 cards so that they are balanced on the left side and right side of your switch (8 slots apart). For example, if you are installing two active MPSM-T3E3-155 cards in your switch, and you place one MPSM-T3E3-155 card in slot 6, then you should place the second MPSM-T3E3-155 in slot 14.

•Install no more than four active MPSM-T3E3-155 cards in a single Cisco MGX switch.

•Install broadband cards, such as RPM-XF and AXSM cards, between MPSM-T3E3-155 cards. These cards use a different backplane bus and do not affect the narrowband bandwidth.

Placement of the MPSM-T3E3-155 is especially important because of the total card capacity. Other narrowband cards also utilize cellbus capacity, but they have smaller bandwidth requirements and place less load on the backplane.

Bandwidth Oversubscription

You can install more than the recommended number of cards under the following circumstances:

•You do not configure the full port rate available to each card installed in your switch.

•You use statistical multiplexing of traffic to support overbooking of cell bus traffic. Statistical multiplexing works better for a T3 port that is channelized down to DS1s than it does for a T3 port that uses its full T3 capacity.

If you do not have such information available when installing your switch, you must follow the general recommendations to provide adequate bandwidth margins.

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 (CBC) to achieve the OC-10 rate. The traffic must be distributed equally at a rate of about OC-5 on the two CBCs.

The CBCs 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. Traffic above the OC-6 rate is dropped. However, if only one CBC is used and the other CBC is not used, then the CBC 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 traffic by evenly distributing cell-based cards on the left and right sides 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 back card. Modular optical transceiver (SFP-8-155) mismatches are not reported for that back card, 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 back card is removed, screw the remaining back card in completely to ensure that the contacts are fully engaged.

•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 a 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. 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 rate is actually 1428571.

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 you are interoperating with SES from Release 3.0.x and later.

–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 later.

•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 obtain 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 nonpersistent.

•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 Channel Loopback Limitation

The channel loopback tests the integrity of the connection (channel) at the local UNI or across the network. The system returns an error message if the connection is broken or incorrect data arrives at the end of the loopback. The maximum number of connection loopbacks that can exist on an AXSM is 8 for Release 2.1 and later. The addchanloop command in the Cisco MGX 8800/8900 Series Command Reference, Release 5.2 incorrectly states the limit as 256.

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 Autorestart (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 back card of the active card must be present for correct APS operation.

•AXSM front cards need the corresponding back card for correct APS operation. In other words, the AXSM cards do not support cross back card removal—the upper back card of one AXSM and lower back card of another AXSM.

•If you remove the upper back card of the active front AXSM, it triggers an active card switch. At this point the APS is still operational. However, if the lower back card of the current active AXSM is removed, it does not trigger switching because the standby card is missing the back card.

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

•The MPSM-8T1-FRM and MPSM-8E1-FRM cards do 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 MPSM cards suitable for your network.

•If you order MPSM cards with systems, the MPSM licenses can be shipped on the PXM card. For more information, see Appendix B: MPSM Licensing.

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 switch over 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, modify 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 a 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. Attempts to configure the clock source are not recorded 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:

•Do not execute 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 a discrepancy in the PNNI configuration. For example, some connections might be in the mismatch 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) enter 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 number 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 for finding the bypasses between the logical links. A significant change in bandwidth in one of the links within the peer group triggers the bypass calculation. 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 from any Release 3.0.x is nongraceful. 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 routes.

•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 multipeer 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 later. After an upgrade, manually reconfigure using commands like cnfcon. This step is necessary one time 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, the 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 happens within one hour, 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 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 (multipeer 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 must 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 a card is reset and the binary file exists, the card is configured 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.

To 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 all be the same 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 range(see CSCdz33652).

•If you clear the channel counters using the clrchancnt command while you are monitoring the channel counts using the dspchancnt command, the counters return incorrect values. To display correct data, enter the dspchancnt again .

•The clrsmcnf command does not work for redundant service modules.

•The clrsmcnf does not work while 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. You must reboot the standby PXM after it enters a stable state to synchronize changes made during the upgrade.

•Release 3.0.00 or later with PXM45/B supports up to 250,000 connections.

•The BPX does not support NCDP.

Installation and Upgrade Procedures

Do not upgrage to Release 5.1 and later from Release 4.0.17 and earlier.

For information on the following installation and upgrade procedures, refer to the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.

Upgrade Information

The upgrade appendix in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 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-XF 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.

For information about graceful upgrades of AXSM-XG cards, see Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG.

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 8800/8900 Series Configuration Guide, Release 5.2 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.2.10

This section contains the known, resolved, and changed status anomalies in Release 5.2.10.

For information about anomalies with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.2.10.

For information about anomalies with the VISM card, refer to Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.25.

For information about anomalies with the RPM-XF card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(11)T9 for PXM45-based Switches, Release 5.2.10 .

For information about anomalies with the RPM-PR card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(11)T9 for MGX Releases 1.3.12 and 5.2.10.

Known Anomalies in Release 5.2.10

Table 9 lists the known anomalies in Release 5.2.10.

Table 9 Known Anomalies in Release 5.2.10 

Anomaly ID	Description
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
CSCeh20665	Headline: AXSM-XG NVRAM gets corrupted Symptom: AXSM-XG cards show up as having a corrupted NVRAM. Condition: If an AXSM-XG card is moved to a different slot or chassis type (for example 8850 to 8950) while the chassis/PXM is powered off there is a remote chance that the NVRAM will be corrupted and the card will fail to boot on the next card initialization. Workaround: Ensure that the chassis and PXMs are powered up before installing the AXSM-XG cards in the new slot. Hardware: AXSM-XG
CSCeh93023	Headline: Standby card reset for RAM sync error during line/path decommission Symptom: On an MPSM-T3E3-155 card configured with redundancy, executing a delppplink followed immediately by a dnpath results in a RamSync error on the standby card and the card resets. This problem is repeatable only from the test script, not from the CLI. Condition: RamSync Error which causes standby card reset. Verify by entering dsperrhist <slot>. Workaround: Because this occurs only with delppplink followed immediately by dnpath, you can work around the problem by adding a 1 second delay between the two commands. Hardware: MPSM-T3E3-155-PPP
CSCeh94891	Headline: Standby PXM45 in init state Symptom: Standby PXM45 is stuck in init state. Condition: PXM45 on MGX running 3.0 bootcode. Workaround: Use cnftopogw on to turn on the gateway node, then reboot PXM45. This will allow the standby to be updated correctly. Hardware: PXM45/C
CSCeh95285	Headline: TRL in IMA lines is not moving after swithcc in node Symptom: An IMA group between an PXM1e-T1e1 and AUSM did not recover after switchcc. Condition: TRL for AUSM was stuck at a line which was in critical alarm and the IMA group never came back. Workaround: Deleting the line that has critical alarm from the IMA group. Hardware: PXM1E-IMA
CSCei17194	Headline: dspcon in conditioned alarm. no log detail on PXM45/B 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
CSCei47617	Headline: Line error increasing on SRME/B T3 while in loop Symptom: SRME/B card with T3 interfaces constantly registering line errors. Condition: Loopback Workaround: None Hardware: SRM/SRME
CSCei66081	Headline: Invalid message code for conntrace on SES Symptom: conntrace from a SES might timeout if a PNNI node of another vendor is on the path. dspconntracebuffer 3.1 100 125 Last update time: Jul 22 2005 6:48:13 Result: FAILURE Reason: Time Out Physical PortId: 3.1 VPI:100 VCI:125 Condition: SES is on the path of multi-vendor PNNI network. Workaround: Use dsppncon for the connection segment within the SES network. Hardware: SES
CSCei71643	Headline: Switchover of MPSM-PPP T3 cards exceeds 8 second requirement Symptom: Variable time outage on traffic loss with different rate of traffic when executing switchover on MPSM-T3 redundancy group. Condition: Traffic outage increases as the traffic increases Workaround: None Hardware: MPSM-T3E3-155 OC3-PPP
CSCej48870	Headline: Switchredcd causes bundle mismatch and DiskDB mismatch error on MPSM. Symptom: On a MPSM switchover, an error message is logged in the Event Log. This message indicates a checksum mismatch between MPSM and PXM. Conditions: These mismatches occur when both of these conditions are present: 1. A Standby MPSM goes to Active state. 2. Prior to the Standby going Active, a link/bundle was deleted on the old Active card before the Active card went to Active Ready state. Workaround: None. The event log is harmless. Hardware: MPSM-T3E3-155-PPP, MPSM-16-T1E1-PPP

Resolved Anomalies in Release 5.2.10

Table 10 lists the anomalies that are resolved in Version .206 of Release 5.2.10.

Table 10 Resolved Anomalies in Version .206 of Release 5.2.10 

Identifier	Headline
CSCir01835	Offline Diag fails for PXM45C H2 boards.
CSCek51943	Standby PXM1E back card went to mismatch (APS was configured).
CSCej29385	SRME card alarms on CWM because there are no cards in slots.
CSCek29124	Interoperability problems with connection trace.

Table 11 lists the anomalies that are resolved in Version .204 of Release 5.2.10.

Table 11 Resolved Anomalies in Version .204 of Release 5.2.10 

Identifier	Headline
CSCek28316	CWM can not do conntrace more than 5 times
CSCek36879	switchcc causes active VISM calls to drop
CSCek38109	After upgrading from 5.1 to 5.2 CBR conns go into cond alarm state
CSCek40639	Upgrade to 5.2 or greater causes AW parameter set to default
CSCek44255	Impedence mismatch on SRME-3 Y cable - CAB-BNC-Y/B
CSCek45997	PXM45 reroute timer triggered when interface was down
CSCek47955	PXM45C fails/resets when receiving ABR call setup w/PB and filters
CSCin99532	Node lost inband connectivity with mbuf allocation failed log

Table 12 lists the anomaly that is resolved in Version .202 of Release 5.2.10.

Table 12 Resolved Anomaly in Version .202 of Release 5.2.10 

Identifier	Headline
CSCek38380	entPhysicalModelName for 8830/B chassis should display MGX8830/B-CH

Table 13 lists the anomalies that are resolved in Version .201 of Release 5.2.10.

Table 13 Resolved Anomalies in Version .201 of Release 5.2.10 

Identifier	Headline
CSCek31375	UDI compliance of 8830/B chassis required
CSCek30597	snmpwalk on AXSM-4-2488-XG and AXSM-1-9953-XG loops at cssLOSs

Table 14 lists the resolved anomalies in Release 5.2.10.

Table 14 Resolved Anomalies in Release 5.2.10 

Identifier	Headline
CSCed61774	First bulk mode line in temp LOS after SRM/SRME switchover
CSCed89128	MPSM8 Minor IMA alarm not reported on PXM with dspcds
CSCee06096	Unused MPSM FR/CES PAR interfaces shown up after resetsys
CSCee07604	Couple XBAR and HMM_ events clean-up
CSCee47346	MPSM-ATM does not send FRM, BRM until 1 cell of data is sent
CSCeh53982	The dspfeature allows diabling of IMA feature which is wrong info
CSCeh72899	Wrong OIDs populated for Xmt CLP0 and CLP1 cells
CSCeh77872	MPSM-155 : Incorrect default sonet Tx path trace string
CSCeh85523	Display needs change. Err:failed to access or program HW.
CSCei21340	Configuration option is needed for alarm integration time in AXSMA/B
CSCei35633	Paths fail after switchredcd is issued on MPSM0C3
CSCei44706	dspload shows non-existent partition info for AXSMB card
CSCei59862	ILMI goes down when traffic is stopped
CSCei61908	Slips and dropped pings with AMI configured on MPSM
CSCei75053	pnniport interface stuck in building vc for AXSMXG-OC12 card
CSCej15496	AXSM-XG OC3 FRUs not detected consistently
CSCej32681	Alarms seen on BXM when configured for APS if remote end switches cards
CSCej35237	Connection provisioning blocked in MPSM16 if line 1.1 has no port
CSCej37652	PXM1E back card went to mismatch after switchcc when APS was configur
CSCej42146	UBR.2 policing is not consistent across AXSM-A/B/E and AXSM-XG
CSCej46233	Buffer overflow error when addlnloop on a ds3 ln
CSCej53700	LMI failure between MPSM -8t1e1 & Router due to LMI sequence no. mismatch
CSCej71362	MIB table dsx3CurrentTable is not populated for AXSM-T3 card
CSCej72907	MIB tables for AXSM-OC3 current line, path, sonet counters not populated
CSCej82475	CLP 0 discards on ABR connections when intvsvd is enabled
CSCej84077	connection trace is not standards compliant
CSCej89464	dsppathalmcnt -vt: Elapsed time is empty
CSCek01493	Connection goes into alarm for NNI-NNI interface
CSCek24836	AXSM-XG switchredcd causes local loops to be lost
CSCin91349	Version, h/w rev, and other info not shown in MIB in FRSM-2E3 card
CSCin94473	Invalid data exception while associating SCT file with card/port
CSCin96562	MER+: AXSMXG-OC192 is throwing EM-4-EM_ERROR while doings dsppaths
CSCin96877	MER+: IMA BW reduction does not result in reroute of CBR connection
CSCin97305	LMI failure between MPSM & Router due to LMI sequence no. mismatch
CSCin97474	SFM DB shows wrong file size on disk of the stat file

Status Changed Anomalies

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

Table 15 Status Changed Anomalies in Release 5.2.10 

Anomaly ID	Description
CSCei13891	Headline: Policing on VBR.2 connections allowing more CLP1 cells Symptom: More CLP1 cells being allowed than should be allowed. This could potentially result in network congestion. Condition: VBR.2 Connections for both rt and nrt types. Workaround: None Hardware: AXSM Status: Closed
CSCej31959	Headline: Intermittent AAL2 Invalid Len. CPS count. Symptom: Invalid AAL2 length observed on connection from VISM-PR to PXM1E. Condition: PXM1E and VISM-PR cards running PXM1E 5.2.00.200 and VISM 3.3.20 images. Workaround: None Hardware: VISM-PR-8T1 Status: Closed

Resolved Anomalies in Previous Releases

This section contains the resolved anomalies in the following releases:

•Release 5.2.00

•Release 5.1.20

•Release 5.1.00

•Release 5.0.20

•Release 5.0.10

•Release 5.0.00

Resolved Anomalies in Release 5.2.00

Table 16 lists the resolved anomalies in Release 5.2.00.

Table 16 Resolved Anomalies in Release 5.2.00 

Identifier	Headline
CSCeg29002	Stuck with free running clock on PXM1E.
CSCeg37735	CutW tasks can cause high CPU util. result false alarm generation.
CSCeg47129	REG5.1 Resetsys cause the remote nodes (AXSM-XG OC-3) pnniport in down
CSCeg53512	REG5.1 Standby pxm gone to failed state after switchcc and saveallcnf
CSCeg59069	CCMA fails to transition to active
CSCeg68920	PXM reset when console receives external script containing %n
CSCeh00187	Avg CPU utilization goes up to 82% for OC3 card running at 44 cps
CSCeh01295	Need to increase the VC/Cos/SG thresholds for SAR connections.
CSCeh02198	12-DT:Igress dest. slot bandwidth DB audit fails after up/dn port
CSCeh03624	2 sec additional latency for IPCP to converge
CSCeh05887	12-DT: SCT 500s files are corrupted
CSCeh11515	AXSM-XG does not discard Unassigned cells on SPVP with VPI = 0 (OC3)
CSCeh12738	Mask off byte 127 of packet memory I2C
CSCeh13430	12-DT: All sscops stuck in reset; ipc msg allocate fail after xg reset
CSCeh18475	Connection down and rerouted after APS Pline removed (AnnexB only)
CSCeh23166	fail to detect SD = 9 when SD was set to 9 on APS line
CSCeh32190	AXSM-E OC-12 core dump upon delpart MPLS and PNNI partitions
CSCeh40420	SES: Coding Standard Bits in Call State IE are incorrectly set
CSCeh44896	Following a switchcc primary clock lock state shows free run on PXM1E
CSCeh62582	PXM1E combo fails E3 pulse mask
CSCeh62878	HW Para: PXM1E combo fails E3 AIS response
CSCeh65399	12-DT: Redundant xg cards stuck in init after switchover
CSCeh71950	Upgrading FRSM HS2B DTE line cause line alarm.
CSCeh91015	Add an action on QE Errors to reset PXM if seem multiple times
CSCeh93732	SSI exception error on axsm-xg. It is in sunni core dump area.
CSCeh95399	Loop timing on AXSM-XG-OC3 cause CV LOF on remote end
CSCei13826	Cannot switch from ausm to MPSM after adding mpsm as redundant card
CSCei14150	Conn goes into mismatch on MPSM after switchreds missing on PXM
CSCei14239	T3E3 IT: full throughput traffic caused redundancy switchred issues
CSCei16136	AXSM fails E3 AIS response
CSCei23845	MPSM stuck in failed state after resetcd script
CSCei23863	Traffic loss in both directions; IPCP is in acksent
CSCei29441	CLI blocks adding 1:1 redundancy on MPSM-T3 with RCON in quadrant
CSCei33337	Memory leaks after deactivating/activating a non-existent bundle
CSCei36072	AXSM-XG-OC12: Coredump on the card
CSCei37771	dspcd on AXSM-XG shows negative #SVC after pulling FRUs.
CSCei38749	One end of MPSM line in LOF other end shows clear
CSCei40399	MPSM-16-T1E1—Config mismatch between PRM and PHPI fatal error during upgrade
CSCei44593	cnfpart failed with cannot modify LCN range due to configured conn
CSCei46236	IMA Groups and Links Disappeared After Running Scripts
CSCei50321	AXSM-XG Core Dumps After Performing switchred
CSCei52004	DaxCon between AXSM-XG <-> RPM-XF failed tstdelay/ping
CSCei55066	Mixed mode legacy cards redundancy with MPSM-8T1E1 should not be allowed
CSCei62648	126 terminated connections created on OC-48 PNNI trunk
CSCei70718	AXSM-XG failed to boot on software error
CSCei78895	Customer not able to provision on MPSM-T3E3-155 card via CWM
CSCei87684	dnport fails with software error in AXSM-XG
CSCej17823	PPP link flap during the PXM upgrade prevents graceful upgrade
CSCej17823	PPP link flap during the PXM upgrade prevents graceful upgrade
CSCej62559	OSPF flaps observed after runrev with traffic going on the PPP links
CSCek23839	dspload CLI displays data of wrong partition in AXSM-A/B
CSCin84727	Bad release number was included in statistics file for VISM
CSCin86763	The config file sent from switch for AXSM-XG not having any sct associated
CSCin89927	Active and standby MPSM-155 core dumped after resetcd of standby
CSCin93775	SPVC connections in failed and getting winpath error

Resolved Anomalies in Release 5.1.20

Table 17 lists the resolved anomalies in Release 5.1.20.

Table 17 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.
CSCeh12738	Mask off byte 127 of packet memory I2C
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.
CSCei67407	RPM-XF addred is blocked when RCON is present.
CSCej17823	PPP link flap during the PXM upgrade prevents graceful upgrade
CSCej62559	OSPF flaps observed after runrev with traffic going on the PPP links
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.

Resolved Anomalies in Release 5.1

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

Table 18 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: MPSM-16: some random pnni links fail when added by script
CSCee95371	IMA pnni-link deroute conns when switchred
CSCef02017	MPSM16: spi path add errors when one of the mpsm in 1:N reboot
CSCef08146	MPSM16: snmpget on Rcv and Tx bytes return wrong values for FR port
CSCef15811	MPSM16:WIN6091 IMA group 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 PXM45/B 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 with 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 MPSM-16-T1E1 and AXSM
CSCef30937	MPSM failed after PXM switchcc stress testing
CSCef32181	XG ports in autoconfig for 30 min, after upgrade
CSCef32407	MPSM-16 card reset due to Bus Monitor Err on MPSM WINPATH
CSCef33722	MPSM16 1:N RED failed to protect when the primary card failure
CSCef35674	FECN is mapped to EFCI when setEFCIzero and NIW
CSCef35743	WIN6354: MPSM-16 dnimagrp on NE MPSM causes FE MPSM-16 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	MPSM-16: AUSM/B card stuck when addimagrp 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	MPSM-16 detected 1:N Red config mismatch, act/sdby reset on runrev
CSCef50757	Memory Leak after Repeatedly Downing Then Upping PNNI
CSCef51168	MPSM-16: Active and Stdby reboot on switchredcd caused by snmpSA task
CSCef51592	MPSM-16: 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 AXSM-E flips VCI to 0
CSCef55251	MPSM card stays 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 PXM45/B 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: MPSM-8T1 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-16-T1E1 cards
CSCef74998	Need to bring all links down before renegotiation for cnfmpbundle
CSCef77506	MPSM-16:IMA nni lnk derouted all connections during switchcc
CSCef79081	MPSM-16: 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	MPSM-16: loadrev on 1:N MPSM-16 caused standby to Failed-U state
CSCef83728	Switchside PPP links go down after switchred on MPSM
CSCef83782	REG5.1 cutW1Task SSI-3-EXCEPTION
CSCef84575	MFR: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	MPSM-16: 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	MFR: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	MPSM-16PER: 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 PXM45/B 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 and up on MWR after switchred
CSCeg29724	XM60 insertion causing active PXM45/C 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 19 lists the anomalies that are resolved in Release 5.0.20.

Table 19 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 AXSM-XG-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 MPSM-155 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 PXM45/B 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 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	MPSM-OC3 diagnostics enhancements
CSCeg15436	Too many logging messages from ccProtoGet, DSPImageGet
CSCeg17345	WIN7073-REG5.1 Congested PNNI/SSCOP VC on MPSM after 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 20 lists the anomalies that are resolved in Release 5.0.10.

Table 20 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 does not work on stdby PXM
CSCeb28420	EvtLog: emSyncHumveePort fail messages in log
CSCeb83965	Policing of 80 char limit for dsplns on AXSM-E
CSCec63412	MPSM-OC3: 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	AXSM-E 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 (cannot 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 MPSM-155
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 back card
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	AXSM-XG: 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	AXSM-E: GFR setting is lost on standby card after standby reset
CSCee09158	bootchange cmd on AXSM-E OC12 without 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	AXSM-XG-FDR: pnRedman fails to update stdby; connections lost
CSCee27978	Inserting both back cards 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 back card 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-AXSM-XG
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-AXSM-XG 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	AXSM-XG-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 21 lists the anomalies that are resolved in Release 5.0.00.

Table 21 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	back card 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.

Documentation Updates

This section provides updates for the following documents:

•Cisco PNNI Network Planning Guide for MGX and SES Products Updates

•Cisco Frame Relay Services (FRSM/MPSM-8-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2

•Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 Updates

Cisco PNNI Network Planning Guide for MGX and SES Products Updates

The first version of the PXM45 card, sometimes called the PXM45A, is not supported on Release 5.0 and later. Also, the PXM45 does not support point-to-multipoint connections.

Table 22 describes the document updates that clarify these points and resolve CSCei54818.

Table 22 Updates to Cisco PNNI Network Planning Guide for MGX and SES Products

Chapter	Update
Chapter 2, Table 2.1, Note 3	Old note: PXM45, which is the first released version of the PXM45 card and is sometimes called PXM45A, is not supported on Release 5.1 switches. Revised note: The first version of the PXM45 card, sometimes called the PXM45A, is not supported on Release 5.0 and later.
Chapter 2, Table 2.1	New note: PXM45 does not support P2MP connections.

Cisco Frame Relay Services (FRSM/MPSM-8-T1E1) Configuration Guide and
Command Reference for MGX Switches, Release 5.2

LMI Autosense is not supported on MPSM-8T1-FRM and MPSM-8E1-FRM cards. Therefore, the LMI Autosense steps in the following procedures apply to the FRSM cards only:

•Chapter 2, "Adding Frame Relay Ports"

•Chapter 2, "Configuring Frame Relay Ports"

Also, the LMI Autosense options in the following commands apply to the FRSM card only:

•addport

•cnfport

•xcnfport

Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 Updates

The following sections are updated:

•Appendix A—Graceful upgrades to AXSM-XG

•Appendix F—MPSM licensing updates

For information about updated commands for the graceful update feature, see the Cisco MGX 8800/8900 Series Command Reference, Release 5.2.

Appendix A: Downloading and Installing Software Upgrades

Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG

The AXSM-16-155-XG and AXSM-8-622-XG cards have a higher port density than the equivalent AXSM-E cards, and the AXSM-16-155-XG and AXSM-8-622-XG have better traffic management support than their AXSM/B counterparts. Using the procedures in this section, you can gracefully upgrade AXSM, AXSM/B and AXSM-E cards to AXSM-XG cards.

Graceful upgrades simplify the process of migrating to the newer AXSM-XG cards. During the upgrade, the MGX control processor transfers the configuration/connection database from the previously installed AXSM card to the new AXSM-XG, which preserves all connection configurations. The upgrade process might cause an outage of up to four minutes.

A cable adapter (PN 39-0258-01) is available for AXSM-XG upgrades (single-mode and multimode).

Supported Configurations

Graceful hardware upgrades from AXSM-A/B/E OC-3/OC-12 release 4.0.17 or later to AXSM-XG OC-3/OC-12 in standalone or redundancy mode with Y-cable configurations are supported.

---

Note Graceful migration applies to AXSM A/B/E OC-3 and OC-12 cards only.

---

Limitations

The following limitations apply to graceful upgrades:

•AXSM-A/B do not support Y-cable in MMF configuration

•AXSM-XG-622 lines cannot be set to both SONET and SDH on the same bay. If the card to upgrade has both SONET and SDH lines on the same back card, separate the lines into different bays before starting the migration.

•AXSM OC-48 cards cannot be gracefully upgraded to AXSM-XG OC-48 cards in the MGX 8950 chassis because the back cards are physically incompatible. However, non-graceful upgrade is supported.

•Upgrade of AXSM-A/B/E with SMB-4-155 to AXSM-XG with an electrical back card (MCC-8-155) is not supported because of hardware limitations of the MCC-8-155 back card.

•No more than 6 SCTs can be loaded onto the AXSM-XG at one time.

Preparing to Upgrade

Before performing the upgrade procedures, perform the following tasks:

•Upgrade all custom SCT files (See Converting Custom SCTs).

•Upgrade all other cards to Release 5.2. This is very important, because failure to upgrade will cause connections on the upgraded card to other AXSM cards to change to the mismatch state.

•Verify that the AXSM to upgrade has less than 126,976 connections, which is the maximum number of AXSM-XG connections.

•Verify that the system is in good working order. This includes checking for alarms and verifying redundancy operation. Resolve any existing problems before starting the upgrade.

•Do not attempt to upgrade an electrical back card with APS.

Converting Custom SCTs

The AXSM-A/B/E SCT files are not compatible with the AXSM-XG SCT files. The upgrade procedure automatically updates the default SCT files to the new format. However, customers that use custom SCTs must convert them to the AXSM-XG format before performing the upgrade. The following tables show the AXSM SCT mapping for Cisco-provided SCTs.

Table 23 AXSM-A/B to AXSM-XG SCT Mapping 

AXSM-A/B	AXSM-XG
AXSM_SCT.CARD.0.V1	AXSMXG_SCT.CARD.2.V1
AXSM_SCT.CARD.2.V1	AXSMXG_SCT.CARD.2.V1
AXSM_SCT.CARD.3.V1	AXSMXG_SCT.CARD.2.V1
AXSM_SCT.CARD.4.V1	AXSMXG_SCT.CARD.2.V1
AXSM_SCT.CARD.5.V1	AXSMXG_SCT.CARD.2.V1
AXSM_SCT.PORT.0.V1	AXSMXG_SCT.PORT.410.V1 (OC-3) / AXSMXG_SCT.PORT.310.V1 (OC-12)
AXSM_SCT.PORT.2.V1	AXSMXG_SCT.PORT.410.V1 (OC-3) / AXSMXG_SCT.PORT.310.V1 (OC-12)
AXSM_SCT.PORT.3.V1	AXSMXG_SCT.PORT.400.V1 (OC-3) / AXSMXG_SCT.PORT.300.V1 (OC-12)
AXSM_SCT.PORT.4.V1	AXSMXG_SCT.PORT.410.V1 (OC-3) / AXSMXG_SCT.PORT.310.V1 (OC-12)
AXSM_SCT.PORT.5.V1	AXSMXG_SCT.PORT.400.V1 (OC-3) / AXSMXG_SCT.PORT.300.V1 (OC-12)

Table 24 AXSM-E to AXSM-XG SCT Mapping 

AXSM-E	AXSM-XG
AXSME_SCT.CARD.5.V1	AXSMXG_SCT.CARD.2.V1
AXSME_SCT.CARD.52.V1	AXSMXG_SCT.CARD.2.V1
AXSME_SCT.PORT.0.V1	AXSMXG_SCT.PORT.410.V1 (OC-3) / AXSMXG_SCT.PORT.310.V1 (OC-12)
AXSME_SCT.PORT.5.V1	AXSMXG_SCT.PORT.410.V1 (OC-3) / AXSMXG_SCT.PORT.310.V1 (OC-12)
AXSME_SCT.PORT.6.V1	AXSMXG_SCT.PORT.400.V1 (OC-3) / AXSMXG_SCT.PORT.300.V1 (OC-12)

To convert custom AXSM-A/B/E SCTs to AXSM-XG SCTs:

---

Step 1 Map the existing AXSM-A/B/E SCT to the new AXSM-XG SCT using Table 23 or Table 24.

For example, if the existing SCT was derived from AXSM_SCT.PORT.2.V1 (which has policing enabled for PNNI), the new SCT must be derived from AXSMXG_SCT.PORT.410.V1(which is specific for the OC-3 card and has policing enabled for PNNI).

Step 2 Using a tool such as CWM, port the custom settings from the existing AXSM-A/B/E SCT to the new AXSM-XG SCT.

Step 3 Save the new AXSM-XG SCT using the same SCT ID that the existing SCT uses.

For example, if the existing SCT is named AXSM_SCT.PORT.40.V1, save the new SCT as AXSMXG_SCT.PORT.40.V1.

---

Graceful Upgrade Procedure

This section explains how to gracefully upgrade an AXSM-A/B/E card to an AXSM-XG card, and includes an example of upgrading an AXSM-A card to an AXSM-8-622-XG card.

---

Note If you experience problems with the upgrade, you can cancel it using the abortrev command.

---

The following display shows the example system, which includes two redundant AXSM/A cards to be upgraded, using the PXM dspcd command. Slot 10 is the active card, and slot 11 is the standby card. Inter-card APS is not configured, but lines 10.1.1 and 11.1.1 are connected using a single mode fiber Y-cable.

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 20, 2005 22:38:56 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Active      AXSM_4OC12        NONE       11          PRIMARY SLOT

11   Standby/Active     AXSM_4OC12        NONE       10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

To perform a graceful upgrade of a AXSM A/B/E to AXSM-XG card, follow these steps.

---

Step 1 Delete any intercard APS configured on the AXSM A/B/E cards to be upgraded using the delapsln command.

---

Note Deleting APS may cause traffic outages.

---

Step 2 From the AXSM A/B/E card, enter the dspconinfo command and record the existing connection information. You will use this information later to verify successful migration of existing connections to the new AXSM-XG card.

Step 3 From the PXM issue the loadrev command, specifying the active slot of the redundancy pair, software version, and axsmxg keyword. The axsmxg keyword specifies that you are upgrading both hardware and software.

For example:

M8850_NY.7.PXM.a > loadrev 10 5.1(206.15)A axsmxg

one or more card(s) in the logical slot may be reset.

loadrev: Do you want to proceed (Yes/No)? y

Replace the card in slot 11 with AXSMXG now

M8850_NY.7.PXM.a > 

After entering the loadrev command, the card in slot 11 changes to the Mismatch state. For example:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 20, 2005 22:51:50 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: MAJOR

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active-U/Active    AXSM_4OC12        NONE       11          PRIMARY SLOT

11   Mismatch-U/Empty   AXSM_4OC12        MAJOR      10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

Step 4 Insert the new AXSM-XG front card, back cards, and cables in the standby slot of the redundancy pair. The AXSM-XG card comes up in the STANDBY-U state.

The output of the PXM dspcds command for the example is as follows.

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 21, 2005 00:04:47 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: MAJOR

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active-U/Active    AXSM_4OC12        NONE       11          PRIMARY SLOT

11   Standby-U/Active   AXSM-8-622-XG     MAJOR      10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

---

Note The card may remain in Mismatch state if old hardware was still plugged in after a card reset with the new card type.

---

Step 5 Load the boot code on the standby AXSM-XG card using the PXM burnboot command, specifying the standby slot number and the boot code version. The standby AXSM-XG card is reset and upgraded to the specified boot software version.

For example:

M8850_NY.7.PXM.a > burnboot 11 5.1(206.15)A

WARNING! burnboot is a destructive command if used improperly. 

Please DO NOT Abort or Reset the PXM/SM when the command is in progress, 

as this may corrupt the Boot image. 

The card in slot 11 will be reset.

burnboot: Do you want to proceed (Yes/No)? y

Step 6 If SCM is being used for statistics collection, disable statistics collection using the SCM GUI.

---

Note You cannot disable statistics collection using the MGX CLI; you must use the SCM GUI.

---

Step 7 From the PXM, enter the runrev command, specifying the active slot of a redundancy pair, the version number, and the axsmxg keyword.

---

Note In some cases, such as failed slot hardware, you must force the action using the -f option.

---

For example:

M8850_NY.7.PXM.a > runrev 10 5.1(206.15)A axsmxg

one or more card(s) in the logical slot may be reset.

runrev: Do you want to proceed (Yes/No)? y

Replace the card in slot 10 with AXSMXG now

M8850_NY.7.PXM.a > 

After issuing the runrev command, the PXM dspcds command shows card 10 in the Mismatch state.

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 21, 2005 00:52:00 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: MAJOR

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Mismatch-U/Empty   AXSM_4OC12        MAJOR      11          PRIMARY SLOT

11   Active-U/Active    AXSM-8-622-XG     NONE       10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

Step 8 Insert the second AXSM-XG hardware, including front card, back cards, and cables.

Removing the existing hardware from the active slot invokes a redundancy switchover, and the standby AXSM-XG card transitions to the ACTIVE-U state.

The newly inserted AXSM-XG card becomes the standby card and transitions to the STANDBY-U state.

The output of the PXM dspcds command is as follows:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 21, 2005 01:01:06 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Standby-U/Active   AXSM-8-622-XG     NONE       11          PRIMARY SLOT

11   Active-U/Active    AXSM-8-622-XG     NONE       10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

---

Note The card may remain in Mismatch state if old hardware was still plugged in after a card reset with the new card type.

---

Step 9 If SCM is being used for statistics collection, verify that the new card is ready for statistics collection and then enable statistics collection using the SCM GUI.

---

Note You cannot enable statistics collection using the MGX CLI.

---

Step 10 Load the boot code on the second AXSM-XG card using the PXM burnboot command, specifying the new standby slot number and the boot code version. The new standby AXSM-XG card is reset and upgraded to the specified boot software version. For example:

M8850_NY.7.PXM.a > burnboot 10 5.1(206.15)A

WARNING! burnboot is a destructive command if used improperly. 

Please DO NOT Abort or Reset the PXM/SM when the command is in progress, 

as this may corrupt the Boot image. 

The card in slot 10 will be reset.

burnboot: Do you want to proceed (Yes/No)? y

M8850_NY.7.PXM.a > 

Step 11 Restore APS if it was previously present using the addapsln command.

Step 12 Verify that both cards have become ACTIVE-U and STANDBY-U using the PXM dspcds command:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 21, 2005 01:13:23 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Standby-U/Active   AXSM-8-622-XG     NONE       11          PRIMARY SLOT

11   Active-U/Active    AXSM-8-622-XG     NONE       10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

Step 13 Verify that the upgrade was successful.

a. From the AXSM-XG card, enter the dspconinfo command and verify successful migration of all existing connections to the AXSM-XG redundancy pair. If necessary, wait for the migration to complete.

b. From the AXSM-XG card, enter the dspcd command and verify that all line, port, partition, and connections are correct, and that it displays the type of card from which this AXSM-XG was upgraded.

---

Note You can revert to the previous hardware and software using the abortrev command.

---

Step 14 From the PXM, enter the commitrev command, specifying the slot number, version number, and axsmxg keyword.

M8850_NY.7.PXM.a > commitrev 10 5.1(206.15)A axsmxg

M8850_NY.7.PXM.a > 

After entering the PXM commitrev command, the PXM dspcds command displays the following:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   May. 21, 2005 01:18:03 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

02   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Standby/Active     AXSM-8-622-XG     NONE       11          PRIMARY SLOT

11   Active/Active      AXSM-8-622-XG     NONE       10          SECONDARY SLOT

12   Active/Active      AXSM_1OC48        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

M8850_NY.7.PXM.a > 

---

Non-Graceful Upgrade Procedure

This section explains how to upgrade AXSM-A/B/E cards to AXSM-XG cards, and includes an example of upgrading an AXSM-A card to an AXSM-8-622-XG card.

The following display shows the card status in the example system, using the PXM dspcd command. The AXSM/A card in slot 12 is operating normally and is ready to upgrade.

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   Jun. 22, 2005 18:44:09 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       02          PRIMARY SLOT

02   Standby/Active     AXSM_4OC12        NONE       01          SECONDARY SLOT

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Empty       RPM               NONE       NA          NO REDUNDANCY

11   Empty              ---               ---        ---         ---    

12   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

27   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

To perform a non-graceful upgrade of a AXSM A/B/E to AXSM-XG card, follow these steps.

---

Step 1 From the AXSM A/B/E card, enter the dspconinfo command and record the existing connection information. You will use this information later to verify successful migration of existing connections to the new AXSM-XG card.

Step 2 From the PXM issue the loadrev command, specifying the slot of the card to upgrade, software version, and axsmxg keyword. The axsmxg keyword specifies that you are upgrading both hardware and software.

M8850_NY.7.PXM.a > loadrev 12 5.1(206.20)A axsmxg

one or more card(s) in the logical slot may be reset.

loadrev: Do you want to proceed (Yes/No)? y

M8850_NY.7.PXM.a >  

After entering the loadrev command, the card in slot 12 changes to the Active-U state. For example:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   Jun. 22, 2005 19:16:32 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: MAJOR

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       02          PRIMARY SLOT

02   Standby/Active     AXSM_4OC12        NONE       01          SECONDARY SLOT

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Empty       RPM               NONE       NA          NO REDUNDANCY

11   Empty              ---               ---        ---         ---    

12   Active-U/Active    AXSM_4OC12        MAJOR      NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

27   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

M8850_NY.7.PXM.a > 

Step 3 If SCM is being used for statistics collection, disable statistics collection using the SCM GUI.

---

Note You cannot disable statistics collection from the MGX CLI; you must use the SCM GUI.

---

Step 4 From the PXM card, enter the runrev command, specifying the slot number, the version number, and the axsmxg keyword.

For example:

M8850_NY.7.PXM.a > runrev 12 5.1(206.20)A axsmxg 

one or more card(s) in the logical slot may be reset.

runrev: Do you want to proceed (Yes/No)? y

Replace the card in slot 12 with AXSMXG now

After entering the runrev command, card 12 changes to the Mismatch state.

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   Jun. 22, 2005 19:16:32 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: MAJOR

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       02          PRIMARY SLOT

02   Standby/Active     AXSM_4OC12        NONE       01          SECONDARY SLOT

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Empty       RPM               NONE       NA          NO REDUNDANCY

11   Empty              ---               ---        ---         ---    

12   Mismatch-U/Empty   AXSM_4OC12        MAJOR      NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

27   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

Step 5 Insert the new AXSM-XG front card, back cards, and cables. The new AXSM-XG card comes up in the ACTIVE-U state.

Enter the PXM dspcds command again:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   Jun. 22, 2005 19:40:26 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       02          PRIMARY SLOT

02   Standby/Active     AXSM_4OC12        NONE       01          SECONDARY SLOT

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Empty       RPM               NONE       NA          NO REDUNDANCY

11   Empty              ---               ---        ---         ---    

12   Active-U/Active    AXSM-8-622-XG     NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

27   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

---

Note The card may remain in Mismatch state if old hardware was still plugged in after issue of card reset with the new card type.

---

Step 6 Load the boot code on the AXSM-XG card using the PXM burnboot command, specifying the slot number and the boot code version. The standby AXSM-XG card is reset and upgraded to the specified boot software version. For example:

M8850_NY.7.PXM.a > burnboot 12 5.1(206.20)A

WARNING! burnboot is a destructive command if used improperly. 

Please DO NOT Abort or Reset the PXM/SM when the command is in progress, 

as this may corrupt the Boot image. 

The card in slot 12 will be reset.

burnboot: Do you want to proceed (Yes/No)? y

Step 7 If SCM is being used for statistics collection, verify that the new card is ready for statistics collection and then enable statistics collection using the SCM GUI.

---

Note You cannot enable statistics collection using the MGX CLI.

---

Step 8 Verify that the upgrade was successful.

a. From the AXSM-XG card, enter the dspconinfo command and verify successful migration of all existing connections to the AXSM-XG. If necessary, wait for the migration to complete.

b. From the AXSM-XG card, enter the dspcd command and verify that all line, port, partition, and connections are correct, and that it displays the type of the card from which this AXSM-XG was upgraded.

---

Note You can revert to the previous hardware and software using the abortrev command.

---

Step 9 From the PXM, enter the commitrev command, specifying the slot number, version number, and axsmxg keyword.

M8850_NY.7.PXM.a > commitrev 12 5.1(206.20)A axsmxg

After you enter the PXM commitrev command, the PXM dspcds command displays the following:

M8850_NY.7.PXM.a > dspcds

M8850_NY                         System Rev: 05.01   Jun. 22, 2005 21:06:30 GMT

Chassis Serial No:   SAA03211181 Chassis Rev: B0     GMT Offset: 0

                                                     Node Alarm: NONE

Card Front/Back         Card              Alarm      Redundant   Redundancy 

Slot Card State         Type              Status     Slot        Type   

---  ----------         --------          --------   -------     -----  

01   Active/Active      AXSM_4OC12        NONE       02          PRIMARY SLOT

02   Standby/Active     AXSM_4OC12        NONE       01          SECONDARY SLOT

03   Active/Active      VXSM_155          NONE       NA          NO REDUNDANCY

04   Active/Active      AXSME_16T3E3      NONE       NA          NO REDUNDANCY

05   Active/Active      AXSM_4OC12        NONE       NA          NO REDUNDANCY

06   Active/Active      AXSM_16OC3_B      NONE       NA          NO REDUNDANCY

07   Active/Active      PXM45C            NONE       08          PRIMARY SLOT

08   Standby/Active     PXM45C            NONE       07          SECONDARY SLOT

09   Active/Active      RPM_PR            NONE       NA          NO REDUNDANCY

10   Active/Empty       RPM               NONE       NA          NO REDUNDANCY

11   Empty              ---               ---        ---         ---    

12   Active/Active      AXSM-8-622-XG     NONE       NA          NO REDUNDANCY

13   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY

14   Empty              ---               ---        ---         ---    

15   Empty              ---               ---        ---         ---    

16   Empty              ---               ---        ---         ---    

27   Empty              ---               ---        ---         ---    

29   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY

30   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY

31   Empty              ---               ---        ---         ---    

32   Empty              ---               ---        ---         ---    

M8850_NY.7.PXM.a > 

Appendix B: MPSM Licensing

MPSM Licensing Information

The Cisco multiprotocol service module (MPSM) family of cards includes MPSM-T3E3-155, MPSM-16-T1E1, and MPSM-8-T1E1 service modules. The MPSM-T3E3-155 and MPSM-16-T1E1 cards both support two software images, one for ASAP and another for MLPPP. With proper licensing, these cards can provide multiple services or features. License management software on the card grants and enforces the use of licensed services.

This appendix explains license management functions and procedures. It includes the following sections:

•MPSM License Overview

•PXM License Pool

•Viewing License Data

•Adding Licenses Obtained from Cisco.com

•Moving Licenses from an MPSM Card to the License Pool

•Allocating Feature Licenses to a Card

•Recovering Feature Licenses That are Not In Use

•Saving and Restoring the License Configuration

•Transferring Licenses Between Switches

•MPSM License Alarms

•Rekeying Feature Licenses

•MPSM License Concepts and Terms

MPSM License Overview

This appendix helps you with the following MPSM licensing scenarios:

•You purchase MPSM cards and licenses as part of an initial chassis purchase. Cisco loads the licenses on the PXM card before shipment.

•You purchase spare MPSM cards with licenses. Cisco loads the licenses on the MPSM card before shipment. You subsequently move the licenses from the MPSM card to the PXM license pool. See the "Moving Licenses from an MPSM Card to the License Pool" procedure.

•You purchase MPSM licenses alone, without hardware. You request license keys from Cisco.com using the Product Authorization Key (PAK) printed on the sales order, and then add licenses to the PXM license pool. See the "Adding Licenses Obtained from Cisco.com" procedure.

---

Note We recommend purchasing MPSM licenses alone, separate from the hardware.

---

•You must transfer MPSM licenses from one MGX switch to another. You must contact Cisco TAC and request transfer license keys. See the "Transferring Licenses Between Switches" procedure.

•You must rekey MPSM licenses that are in an alarm state. You must contact Cisco TAC and request rekey license keys. See the "Rekeying Feature Licenses" procedure.

---

Note You can purchase MGX systems, spares, and MPSM licenses from Cisco.com.

---

---

Tip Although Table 25 summarizes available licenses, read the entire appendix to understand the terms and processes used for MPSM licensing. For example, if your shelf activates a Node License Alarm, you have a 5-day grace period to recover licenses without interrupting service. After you read this appendix, contact Cisco TAC for additional assistance.

---

Table 25 lists MPSM licenses available for MPSM cards.

Table 25 Licensed Services for MPSM Cards 

Card Type	License	Description	Software Release Support
			5.0.20	5.1.20	5.2.00 and later
MPSM-8-T1E1	MPSM-RC-8-LIC	Rate Control—Enables either Standard ABR or Foresight features for Frame Relay connections.	x	x	x
MPSM-16-T1E1	MPSM-RC-16-LIC	Rate Control—Enables the Standard ABR feature for Frame Relay connections.		x	x
	MPSM-MS-16-LIC	Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.		x	x
	MPSM-ML-16-LIC	MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).		x	x
	MPSM-PPP-16-LIC	MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).		x	x
	MPSM-SR-16-LIC	1:N Redundancy		x	x
MPSM-T3E3-155	MPSM-CH-HS-LIC	Channelization—Enables channelization of the physical port into multiple DS0s for Frame Relay service and DS1s for ATM service.	x	x	x
	MPSM-RC-HS-LIC	Rate Control—Enables the Standard ABR feature for Frame Relay connections.	x	x	x
	MPSM-MS-HS-LIC	Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.	x	x	x
	MPSM-ML-HS-LIC	MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).	x	x	x
	MPSM-PPP-HS-LIC	MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).			x

MPSM licenses have the following characteristics:

•Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card requires the same licenses as the primary cards it protects.

•Licenses are authorized for a specific backplane serial number. Licenses for one type of card cannot be used on another type of card.

•For the MPSM-T3E3-155 or MPSM-16-T1E1 cards, if a license is not allocated to the service module, the configuration commands for that feature return a licensing error.

•Licenses are bundled by card type, so you purchase licenses for each MPSM card type separately.

PXM License Pool

A pool of licenses is stored on the PXM hard disk and is managed by the PXM controller. Figure 1 illustrates the license pool and shows how the PXM controller adds, transfers, and allocates licenses from the pool.

Figure 1 Switch License Pool

When a card needs to use a license, it checks out the license out of the depository. The license becomes unavailable to all other cards while it is checked out. For example, if a standard ABR connection is provisioned on an MPSM-8-T1E1 card configured for Frame Relay services, a rate control license in the pool is checked out or allocated to that card. If the ABR connection is removed and no other ports on the card have provisioned standard ABR connections, the rate control feature license is checked back into the license pool and becomes available for other cards.

When a license is checked out, the switch records the assignment of the feature to a card and enables the feature on the card. The license remains in the license pool until explicitly removed. The only way to safely remove a license from the pool is to explicitly transfer it to another switch.

Viewing License Data

Display commands allow you to view node license data, card license data, or license history data. The following sections describe ways to view the license data.

Viewing All Node Licenses

To view all node licenses, enter the dsplics command as follows:

M8830_CH.1.PXM.a > dsplics

M8830_CH                         System Rev: 04.09   Mar. 08, 2004 00:15:51 GMT

MGX8830                                              Node Alarm: CRITICAL

Node License Alarm : Minor

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-T3E3-155      MultiSrvc    4          1          3        

                   Channelize   4          1          3        

                   Multilink    4          0          4        

                   RateControl  4          1          3        

Use the dsplics command to show all licenses in the license pool, the number of licenses are in use, and the number that are available for use.

Viewing Licenses for a Specific MPSM Card Type

To view the licenses for a specific MPSM card type, enter the dsplics -cd cardtype, where cardtype is a number that specifies the MPSM card type:

•1 = MPSM-8-T1E1

•2 = MPSM-16-T1E1

•3 = MPSM-T3E3-155

For example:

M8830_CH.1.PXM.a > dsplics -cd 3

M8830_CH                         System Rev: 04.09   Mar. 08, 2004 00:08:45 GMT

MGX8830                                              Node Alarm: CRITICAL

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-T3E3-155      MultiSrvc    4          1          3        

                   Channelize   4          1          3        

                   Multilink    4          0          4        

                   RateControl  4          1          3 

The dsplics -cd command displays the same information as the dsplics, command, but it limits the display to a single card type.

Viewing Licenses for All Cards

To view the licenses allocated or programmed for all cards, enter the dspliccds command. The dspliccds command is a nonprivileged command and is available on the PXM45 and PXM1E cards.

The following output shows licenses for all MPSM card types.

M8830_CH.1.PXM.a > dspliccds

M8830_CH                         System Rev: 05.00   Apr. 11, 2004 19:08:26 GMT

MGX8830                                              Node Alarm: CRITICAL

      Card            Card Lic    Prov    License       Alloc    

Slot  Type            Alarm       Status  Type          lics      

----  -------------   --------    ------  -------       ----  

 1    --              --          --      --            --    

 2    --              --          --      --            --        

 3    MPSM-T3E3-155   No          Yes     MultiSrvc     1      

                                          Channelize    1     

                                          MultiLink     1 

                                          RateControl   1    

 4    MPSM-T3E3-155   Minor       Yes     MultiSrvc     1           

 5    MPSM-T3E3-155   Minor       No      MultiSrvc     1     

                                          MultiLink     1     

 6    MPSM-T3E3-155   No          Yes     --            --   

 9    --              --          --      --            --    

 10   MPSM-8T1E1      No          Yes     RateControl   1   

 11   MPSM-8T1E1      No          Yes     --            --   

 12   MPSM-8T1E1      No          Yes     RateControl   1   

 13   MPSM-16T1E1     No          Yes     MultiSrvc     1 

                                          MultiLink     1 

                                          RateControl   1      

                                          PPP           1            

 ...

The following output shows programmed licenses of all cards. A programmed license is a license that is shipped on a card from the factory.

M8850_SF.7.PXM.a > dspliccds -prog

M8850_SF                         System Rev: 05.02   Jan. 24, 2006 06:51:43 GMT

MGX8850                                              Node Alarm: MAJOR

                         Licenses  License      Programmed

Slot  Card Type          moved     Type         Licenses 

----  -------------   --------    -------       ----------  

 1    --              --          --            --              

 2    --              --          --            --               

 3    MPSM-T3E3-155   No          MultiSrvc     1      

                                  Channelize    1     

                                  MultiLink     1     

 4    MPSM-T3E3-155   Yes         MultiSrvc     1     

                                  Channelize    1        

 5    MPSM-T3E3-155   Yes         MultiSrvc     1     

                                  MultiLink     1

                                  RateControl   1

 6    MPSM-T3E3-155   N/A         --            --       

 9    --              --          --            --       

 10   MPSM-8T1E1      No          RateControl   1   

 11   MPSM-8T1E1      N/A         --            0   

 12   MPSM-8T1E1      Yes         RateControl   1

 13   MPSM-16T1E1     N/A         --            0   

 ...

Viewing Licenses for a Specific Card

To view the license usage for a single card within a switch, enter the dspliccd command on either the PXM or the MPSM. The following output shows license details for card 11, displayed from a PXM card:

M8830_CH.11.PXM.a > dspliccd  11

M8830_CH                         System Rev: 04.00   Feb. 27, 2003 17:28:26 GMT

Chassis Serial No:   SAA02390010 Chassis Rev: E4     GMT Offset: 0

                                                     Node Alarm: NONE

Card License Alarm:           Minor

Service Module Type:          MPSM-T3E3-155

Service Module Serial Number: 3SA4567011

Provisioning allowed:         Yes

Grace-Period Remaining:       3 Days 4 Hours

=========================================================

Allocated License Type        Qty    

----------------------        ----     

Multi-Srvc                    1             

Channelize                    1             

=========================================================

Programmed License Type       Qty 

-----------------------       ----     

Multi-Srvc                    1             

Channelize                    1                   

=========================================================

Programmed Licenses Registered:           YES           

License Registration Node:                MyNodeBuilding3

License Registration Chassis Serial No:   8SA931247821

License Creation Timestamp:               Oct 25, 2003 14:20:40

License Registration Timestamp:           Dec 02, 2003 19:33:12

=========================================================

The following license states might occur:

•If the grace period has already expired, the following output appears:

Provisioning allowed:        No 
Grace-Period Status:          Expired

•If the slot is running normally without a license alarm, only the following output appears:

Provisioning allowed:         Yes

An allocated license is one that has been assigned to a card. A programmed license is a license that has been shipped on a card from the factory. It must be moved to the license pool before it can be allocated to a card.

In the following example, the dspliccd command is entered at an MPSM card prompt, so you do not have to enter the slot number:

M8830_CH.12.MPSM155[FR].a > dspliccd

Card License Alarm:              None

Service Module Type:             MPSM-T3E3-155

Service Module Serial Number:    SAD073504CT

Provisioning (addcon) Allowed:   YES

=========================================================

Needed License Type               Needed Licenses

-------------------               ---------------

Multi-Srvc                        1             

Channelize                        1             

=========================================================

Allocated License Type            Allocated licenses

----------------------            ------------------

Multi-Srvc                        1             

Channelize                        1             

=========================================================

Programmed  License Type          Programmed licenses

------------------------          -------------------

Multi-Srvc                        1             

Channelize                        1             

=========================================================

Programmed License Registered:   YES

License registration node:       M8830_CH

License registration chassis:    8SA931247821

=========================================================

A needed license is a one that is required by the MPSM card to provide a desired feature.

Viewing License Updates History

To display a history of all license updates on the switch, enter the dsplics -history command as follows:

M8830_CH.1.PXM.a > dsplics -history

M8830_CH                         System Rev: 04.09   Mar. 08, 2004 00:20:22 GMT

MGX8830                                              Node Alarm: CRITICAL

Licensed           Chassis or     Update    Update     License

CardType           Card Serial#   Method    Sequence#  Update Time

----------------   ------------   --------  ---------  -----------

MPSM-T3E3-155      SAG06152SZM    Addition  1          WED OCT 08 19:58:54 2003

Viewing License Alarms

To display a list of license feature alarms, enter the dsplicalms command as follows:

M8830_CH.1.PXM.a > dsplicalms

M8830_CH                         System Rev: 04.09   Mar. 08, 2004 00:20:59 GMT

MGX8830                                              Node Alarm: CRITICAL

Slot  Critical   Major     Minor   ||  Slot  Critical   Major     Minor 

----  --------  -------   -------  ||  ----  --------  -------   -------

 1          0        0         0   ||   8          0        0         0

 2          0        0         0   ||   9          0        0         0

 3          0        0         0   ||  10          0        0         0

 4          0        0         0   ||  11          0        0         0

 5          0        0         0   ||  12          0        0         0

 6          0        0         0   ||  13          0        0         0

 7          0        0         0   ||  14          0        0         0

Adding Licenses Obtained from Cisco.com

This section explains how to use the Cisco.com licensing tool and your Product Authorization Key (PAK) to request MPSM licenses, and describes how to add the licenses to an MGX switch. Use this procedure only when you are adding licenses for existing hardware. If you are purchasing new MGX switches or MPSM cards, you can order the licenses when you order the hardware.

The general procedure is as follows:

1. Purchase additional licenses from Cisco and receive a PAK by mail. You can view the PAK number online as soon as the sales order is fulfilled. See the "Viewing the Product Authorization Key Online" procedure.

2. Obtain the node ID for the MGX switch in which you plan to install the licenses. See the "Obtaining Node IDs" procedure.

3. Request a license key using the Cisco.com licensing tool. See the "Requesting Licenses" procedure.

4. Add licenses to the PXM license pool on the MGX switch. See the "Adding Licenses to the License Pool" procedure.

Viewing the Product Authorization Key Online

If you have an active CCO account on Cisco.com and know your sales order number, you can view the sales order online and view the Product Authorization Key (PAK). You do not need to wait for the PAK to arrive by conventional mail.

To view the PAK number online, perform the following steps:

---

Step 1 Log on to Cisco.com and open your customer order.

Step 2 Check the Show Serial Number box. The PAK number appears in the Product column.

---

Obtaining Node IDs

MPSM licenses are keyed to a specific MGX switch. For that reason, you must specify the MGX node ID when requesting licenses.

To obtain the node ID, perform the following steps:

---

Step 1 Establish a configuration session using a username with SERVICE_GP privileges or greater.

Step 2 Display the switch serial number used for licensing by entering the dsplicnodeid command. If no licenses are installed, the switch generates a node license ID as shown in the following example:

M8850_SF.7.PXM.a > dsplicnodeid

The BkPL recorded Lic Seq Num did not exist. Creating with 0.

NodeID=SCA062300GF:000000:005:002:211

If the switch has an existing node license ID, it is displayed as follows:

M8850_SF.7.PXM.a > dsplicnodeid

NodeID=SCA062300GF:000001:005:002:211

Step 3 Record the node ID and log out.

---

Requesting Licenses

You can request licenses online using the Cisco licensing tool. To complete the request, you need your PAK key and node ID of the switch you wish to license.

To request licenses, perform the following steps:

---

Step 1 Access the Cisco licensing tool at the following URL:

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

The following page opens.

Step 2 At the prompt, enter the PAK number.

Step 3 Click Submit.

The following page opens, displaying the number of purchased, fulfilled, and available licenses:

Step 4 Enter the number of licenses to register.

Step 5 Click Submit.

The following page opens.

Step 6 Enter the customer information.

Step 7 In the Serial Number field, enter the node ID of the target switch.

---

Note Do not enter the serial number.

---

Step 8 In the Product Authorization Key field, enter your PAK number.

Step 9 Click Submit. You will receive the license by e-mail.

---

Adding Licenses to the License Pool

After you receive the license e-mail, you can add the licenses on the MGX switch. You have two options for adding licenses:

•Use the license file attached to the e-mail

•Use the license key in the body of the e-mail

You can use the license key or file only once because the MGX node ID changes after you add the license.

To add licenses to an MGX switch, perform the following steps:

---

Step 1 If you are adding licenses from the license file, FTP the license file to the C:/LICENSE directory on the destination switch.

Step 2 Establish a configuration session using a username with SERVICE_GP privileges or greater.

Step 3 If you are adding licenses from the license file, verify that the license file exists. Otherwise, skip this step.

M8850_SF.7.PXM.a > cd LICENSE

ls

. 

.. 

Lmpsm16t1e1_20051221181923966.dat 

In the file system : 

    total space :  818961 K bytes

    free  space :  677443 K bytes

Step 4 Display current licenses, for example for MPSM-16-T1E1 cards:

M8850_SF.7.PXM.a > dsplics -cd 2

M8850_SF                         System Rev: 05.02   Dec. 28, 2005 06:54:34 GMT

MGX8850                                              Node Alarm: MAJOR

Node License Alarm : None

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-16-T1E1       MultiSrvc    2          0          2        

                   RateControl  2          0          2        

                   MultiLink    2          0          2        

                   PPP          4          1          3 

Step 5 Enter the cnflic command.

•To add licenses using a license file, enter cnflic -f filename,

where filename is the e-mail attachment name.

•To add licenses using a license key, enter cnflic key,

where key is the license key string in the e-mail body.

The following example shows how to add a license using the license file:

M8850_SF.7.PXM.a > cnflic -f Lmpsm16t1e1_20051221181923966.dat

Update method         : Addition

Card type             : MPSM-16-T1E1

Creation date/time    : THU DEC 22 02:19:23 2005

Grace period (days)   : 0

Update sequence number: 30

License serial number : L0000007923

Num of features       : 4

---------------     -----

License Type        Qty 

---------------     -----

MultiSrvc           2    

RateControl         2    

MultiLink           2    

PPP                 2    

Please confirm the above license information.

cnflic: Do you want to proceed (Yes/No)? y

The following example shows how to add a license using the license key string:

M8850_SF.7.PXM.a > cnflic 
010502d395743af39a3ba51ef3f9be256ba5ec90c12bc22563d8b236d882b0d8919fec8d3e4126f4b555d96653
4a9384cf88ce1666

Update method         : Addition

Card type             : MPSM-16-T1E1

Creation date/time    : THU DEC 22 02:19:23 2005

Grace period (days)   : 0

Update sequence number: 30

License serial number : L0000007923

Num of features       : 4

---------------     -----

License Type        Qty 

---------------     -----

MultiSrvc           2    

RateControl         2    

MultiLink           2    

PPP                 2    

Please confirm the above license information.

cnflic: Do you want to proceed (Yes/No)? y 

Step 6 To verify that new licenses have been installed, enter the dsplics command.

M8850_SF.7.PXM.a > dsplics -cd 2

M8850_SF                         System Rev: 05.02   Dec. 28, 2005 06:59:04 GMT

MGX8850                                              Node Alarm: MAJOR

Node License Alarm : None

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-16-T1E1       MultiSrvc    4          0          4        

                   RateControl  4          0          4        

                   MultiLink    4          0          4        

                   PPP          6          1          5        

---

Caution To avoid losing licenses during a configuration restoration, save the switch configuration after installing the new licenses by using the saveallcnf command.

---

Step 7 Enter the saveallcnf command.

---

Moving Licenses from an MPSM Card to the License Pool

If a license is purchased at the same time as the MPSM card, the license is programmed on the MPSM card. A license that is programmed on an MPSM card is unavailable to that card and all other cards in the switch. To enable use of the license, you must move the license from the MPSM card to the PXM license pool.

You can only move licenses from an MPSM card to the PXM license pool. You cannot move licenses back to an MPSM card. If you want to transfer licenses to another switch, see the "Transferring Licenses Between Switches" procedure.

To move licenses from an MPSM card to the PXM license pool, perform the following steps:

---

Step 1 Establish a configuration session using a username with SERVICE_GP privileges or greater.

Step 2 Enter the cc command to move to the CLI prompt for the MPSM card.

Step 3 Enter the movelic command as follows:

M8850_SF.1.28.MPSM8T1.FRM.a > movelic

------------------------------------------------

Programmed License Type #Programmed

----------------------- -----------

Rate-Control 1

Do you want to proceed (Yes/No)? Yes

Card Licenses have been moved to license pool.

---

Caution To avoid losing licenses during a configuration restoration, save the switch configuration after moving the new licenses into the PXM license pool by using the saveallcnf command.

---

Step 4 Enter saveallcnf.

---

Allocating Feature Licenses to a Card

To allocate a feature license to an MPSM card, configure the card to use the licensed feature. For example, to allocate the IMA feature to a card, use the addimagrp command to create an IMA group. Licenses are also allocated to redundant cards, so if you use the addred command to configure a secondary card for a primary card, licenses are allocated to the secondary card. When the secondary card serves multiple primary cards, the secondary card receives one of each type of license used by the primary cards it serves.

If the license pool on the switch has an available license for that feature on the MPSM card type, the license is automatically allocated to the card. Once a license is allocated to the card, it is no longer available for use on other cards until it returns to the license pool (See the "Recovering Feature Licenses That are Not In Use" procedure").

If you configure a card to use a feature for which no licenses are available, the command that requires the feature fails.

Recovering Feature Licenses That are Not In Use

Feature licenses are automatically returned to the license pool when the card configuration no longer requires them. The following actions can be used to remove the configuration for featured licenses:

•Use the CLI commands to remove the feature configuration. For example, if you delete all channelized ports (delport) on a card, the channelized feature is no longer required and is returned to the license pool.

•Clear the entire configuration on the service module (clrsmcnf).

•Clear the entire configuration on the switch (clrallcnf).

•Delete a redundant card configuration. This action releases any licenses reserved for the secondary card, provided that those licenses are no longer required for other primary cards.

When licenses are returned to the license pool, they are immediately available for use on other MPSM cards.

Saving and Restoring the License Configuration

MPSM feature licenses are backed up and restored with the complete switch configuration as described in the "Managing the Configuration Files" section in Chapter 9, "Switch Operating Procedures".

---

Caution To avoid losing feature licenses, always save the switch configuration after you move, transfer, or add licenses, by using the saveallcnf command.

---

Transferring Licenses Between Switches

When you transfer licenses between switches, you remove licenses from one switch and add them to another switch.

To transfer licenses:

1. Obtain the node IDs for the source and destination MGX switches for the transfer. See the "Obtaining Node IDs" procedure.

2. Call the Cisco TAC, provide the node IDs, and request a transfer license. You cannot use the online Cisco license tool to transfer licenses. You receive transfer licenses by e-mail.

3. Remove the licenses from the source switch and add the licenses to the destination switch. See the "Transferring Licenses" procedure.

Transferring Licenses

You can transfer licenses using license files or license keys. In either case, you use the license file or key you receive from Cisco to remove the licenses from the source switch. The source switch then generates a license file and key that you use to add the licenses to the destination switch. You can use license keys or files only one time because the node IDs change after you remove or add licenses.

Removing the Licenses From the Source Switch

To remove licenses from the source switch, perform the following steps:

---

Step 1 If you are transferring licenses using the license file, FTP the transfer license file to the C:/LICENSE directory on the source switch.

Step 2 Establish a configuration session with the source switch using a username with SERVICE_GP privileges or greater.

Step 3 If you are transferring licenses using the license file, verify that the license file is in the LICENSE directory. Otherwise, skip this step.

M8850_SF.7.PXM.a > cd LICENSE

M8850_SF.7.PXM.a > ls

. 

.. 

Lmpsm16t1e1_20051229100127934.dat 

In the file system : 

    total space :  818961 K bytes

    free  space :  675506 K bytes

Step 4 Display current licenses. For example, for MPSM-16-T1E1 cards:

M8850_SF.7.PXM.a > dsplics -cd 2

M8850_SF                         System Rev: 05.02   Jan. 04, 2006 06:51:53 GMT

MGX8850                                              Node Alarm: MAJOR

Node License Alarm : None

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-16-T1E1       MultiSrvc    4          0          4        

                   RateControl  4          0          4        

                   MultiLink    4          0          4        

                   PPP          6          1          5

Step 5 Enter the cnflic command to remove licenses from the source switch.

•To use a license file, enter cnflic -f filename,

where filename is the e-mail attachment name.

•To use a license key, enter cnflic key,

where key is the license key string in the e-mail body.

The following example shows how to remove licenses using the license file:

M8850_SF.7.PXM.a > cnflic -f Lmpsm16t1e1_20051229100127934.dat

Update method         : Xfer-out

Card type             : MPSM-16-T1E1

Creation date/time    : THU DEC 29 18:01:27 2005

Grace period (days)   : 0

Update sequence number: 31

License serial number : L0000008665

Num of features       : 4

---------------     -----

License Type        Qty 

---------------     -----

MultiSrvc           2    

RateControl         2    

MultiLink           2    

PPP                 2    

Please confirm the above license information.

cnflic: Do you want to proceed (Yes/No)? y

license file has been generated as: C:/LICENSE/LX-M8850_SF-31.lic

license is: 
010501cdd9a1d5a125587521d9fcf15c5006769a004afa3fee67f73b7ad0c1e44cd4a45fbf466cb7bdb7f61fb6
673ceaef1c0e38c24a741ebcb294c4

This step removes the licenses identified for transfer from the license pool, and these licenses are no longer available for use on the source switch.

This step also generates a new license key and a new license file, which you use to add the licenses to the destination switch. The license key appears in the command output. The license file is stored in the C:/LICENSE directory.

Step 6 Record the name of the license file and the license key string.

Step 7 Verify that the licenses are removed.

M8850_SF.7.PXM.a > dsplics -cd 2

M8850_SF                         System Rev: 05.02   Jan. 04, 2006 06:57:46 GMT

MGX8850                                              Node Alarm: MAJOR

Node License Alarm : None

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-16-T1E1       MultiSrvc    2          0          2        

                   RateControl  2          0          2        

                   MultiLink    2          0          2        

                   PPP          4          1          3        

---

Adding the Licenses to the Destination Switch

To add licenses to the destination switch, perform the following steps:

---

Step 1 If you are transferring licenses using a license file, use FTP to get the generated license file from the C:/LICENSE directory on the source switch, and then put the license file into the C:/LICENSE directory on the destination switch. Use the filename you recorded in Step 6 of the previous procedure.

Step 2 Establish a configuration session with the destination switch using a username with SERVICE_GP privileges or greater.

Step 3 If you are transferring licenses using a license file, verify that the license file is in the LICENSE directory. Otherwise, skip this step.

M8850_LA.8.PXM.a > cd LICENSE

M8850_LA.8.PXM.a > ls

. 

.. 

LX-M8850_SF-31.lic

In the file system : 

    total space :  818961 K bytes

    free  space :  675506 K bytes

Step 4 Enter the cnflic command to add the licenses to the destination switch.

•To use a license file, enter cnflic -f filename,

where filename is the generated filename you recorded in Step 6 of the previous procedure.

•To use a license key, enter cnflic key,

where key is the license key string you recorded in Step 6 of the previous procedure.

The following example shows how to add licenses to the destination switch using the license file:

M8850_LA.8.PXM.a > cnflic -f LX-M8850_SF-31.lic

Update method         : Xfer-in

Card type             : MPSM-16-T1E1

Creation date/time    : THU DEC 29 18:01:27 2005

Grace period (days)   : 0

Update sequence number: 8

License serial number : L0000008665

Num of features       : 4

---------------     -----

License Type        Qty 

---------------     -----

MultiSrvc           2    

RateControl         2    

MultiLink           2    

PPP                 2    

Please confirm the above license information.

cnflic: Do you want to proceed (Yes/No)? y  

Step 5 To verify that the transferred licenses are installed on the destination switch, enter the dsplics command.

M8850_LA.8.PXM.a > dsplics -cd 2

M8850_LA                         System Rev: 05.01   Jan. 05, 2006 06:02:10 GMT

MGX8850                                              Node Alarm: CRITICAL

Node License Alarm : None

Licensed           License      Licenses   Licenses   Licenses

Card Type          Type         Installed  Allocated  Available

-----------------  -----------  ---------  ---------  ---------

MPSM-16-T1E1       MultiSrvc    4          0          4        

                   RateControl  4          0          4        

                   MultiLink    4          0          4        

                   PPP          4          0          4 

---

Caution To avoid losing licenses during a configuration restoration, save the switch configuration at the source and destination switches by using the saveallcnf command.

---

Step 6 Enter the saveallcnf command.

---

MPSM License Alarms

MPSM feature license alarms can occur at the node level or slot level of the switch. The following sections describe these alarms:

•Node License Alarms

•Slot License Alarms

Node License Alarms

Node license alarms occur under the following conditions:

•A switch configuration that was saved before licenses were added or transferred to and from the PXM license pool is restored. Any mismatch between the actual license sequence number and the restored license sequence number generates a minor node license alarm. To prevent this type of alarm, always save the switch configuration (saveallcnf) after you move, transfer, or add licenses.

•The switch configuration is restored on a different node, or the Cisco MGX chassis is replaced with another chassis. Because licenses are authorized for a specific backplane serial number, such conditions cause a mismatch between the physical backplane serial number and serial number recorded in the database.

When a node license alarm is raised, all cards that are using feature licenses go into the slot license alarm state. If no licenses are in use by the cards, no slot license alarms are raised.

On PXM45 and PXM1E platforms, use the PXM dspndalms command to troubleshoot the node license alarm. As shown in the following example on the PXM45 platform, the output of this command indicates if the switch is in the node license alarm state:

M8850_SF.8.PXM.a > dspndalms

Node Alarm Summary

Alarm Type                     Critical        Major          Minor

----------                     --------       -------        -------

Clock Alarms                         0             0              0

Switching Alarms                     0             0              0

Environment Alarms                   0             0              0

Card Alarms                          0             0              0

Node License Alarm                   0             0              1

You clear node license alarms and restore normal operation by validating (rekeying) licenses in the license pool. For more information, see the "Rekeying Feature Licenses" procedure.

---

Note If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any other license management tasks.

---

Slot License Alarms

Slot license alarms are raised under the following conditions:

•When a node license alarm is raised, all cards that are using feature licenses enter the slot license alarm state. You clear s lot license alarms raised under this condition by rekeying the PXM license pool. See the "Rekeying Feature Licenses" procedure.

•The slot in alarm has acquired or oversubscribed one or more licenses while these licenses were not available in the license pool. You clear slot license alarms raised under this condition by adding the required number of licenses to the PXM license pool or by releasing corresponding licenses from other slots so that they become available to the slot in alarm. If slots in alarm have redundancy, you must add licenses to cover both the primary and secondary slots to clear the alarms.

On PXM1E and PXM45 platforms, use the PXM dsplicalms command to troubleshoot slot license alarms. The output of this command indicates which MPSM cards are in the slot license alarm state. The following example shows the output of the PXM dsplicalms command on the PXM45 platform. In this example, the MPSM card in slot 28 is in slot license alarm:

M8850_SF.8.PXM.a > dsplicalms

M8850_SF                         System Rev: 05.00   Jul. 10, 2004 04:35:12 GMT

MGX8850                                              Node Alarm: MINOR

Slot  Critical   Major     Minor   ||  Slot  Critical   Major     Minor 

----  --------  -------   -------  ||  ----  --------  -------   -------

 1          0        0         0   ||  17          0        0         0

 2          0        0         0   ||  18          0        0         0

 3          0        0         0   ||  19          0        0         0

 4          0        0         0   ||  20          0        0         0

 5          0        0         0   ||  21          0        0         0

 6          0        0         0   ||  22          0        0         0

 7          0        0         0   ||  23          0        0         0

 8          0        0         0   ||  24          0        0         0

 9          0        0         0   ||  25          0        0         0

10          0        0         0   ||  26          0        0         0

11          0        0         0   ||  27          0        0         0

12          0        0         0   ||  28          0        0         1

13          0        0         0   ||  29          0        0         0

14          0        0         0   ||  30          0        0         0

15          0        0         0   ||  31          0        0         0

16          0        0         0   ||  32          0        0         0

M8850_SF.8.PXM.a >

On PXM1E and PXM45 platforms, the output of the PXM dspliccd <slot> command also shows the card license alarm state, and displays the remaining time left in the alarm grace period and if provisioning is allowed with the addcon command. The following example shows the output of the PXM dspliccd <slot> command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:

M8850_SF.8.PXM.a > dspliccd 28

M8850_SF                         System Rev: 05.00   Jul. 10, 2004 05:02:24 GMT

MGX8850                                              Node Alarm: MINOR

Card License Alarm:             Minor

Service Module Type:            MPSM-8T1-FRM

Service Module Serial Number:   SAG07208RRA

Provisioning Allowed:           Yes

Grace-Period Remaining:         4 Days, 22 Hrs

=========================================================

Allocated License Type      Quantity

--------------------        --------

RateControl                 1

=========================================================

Programmed License Type     Quantity

--------------------        --------

RateControl                 1

=========================================================

Programmed License Registered:           Yes

License Registeration Node:              M8850_SF

License Registeration Chassis Serial No: SCA062300GF

On PXM1E and PXM45 platforms, the dspcd command indicates if a card is in slot license alarm. If the card is in the slot license alarm state, the cardIntegratedAlarm is minor and the cardMinorAlarmBitMap indicates License Alarm. The following example shows the output of the dspcd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:

M8850_SF.1.28.MPSM8T1.FRM.a > dspcd 

  ModuleSlotNumber:          28

  FunctionModuleState:       Active

  FunctionModuleType:        MPSM-8T1-FRM

  FunctionModuleSerialNum:   SAG07208RRA

  FunctionModuleHWRev:       02

  FunctionModuleFWRev:       030.000.004.016-P2

  FunctionModuleResetReason: Reset by PXM

  LineModuleType:            LM-RJ48-8T1

  LineModuleState:           Present

  mibVersionNumber:          102

  configChangeTypeBitMap:    No changes

  cardIntegratedAlarm:       Minor

  cardMinorAlarmBitMap:      LICENSE ALARM

      Front Card Info        

  PCB PART NO-(800 LEVEL):   800-22480-04 

  PCB PART_NO-(73 LEVEL):    73-8466-04 

  PCB REVISION (800 LEVEL):   

  PCB SERIAL NO:             SAG07208RRA 

  CLEI CODE:                 0 

  MANUFACTURING ENG:         0x0        

  RMA TEST HISTORY:          0x0        

      Back Card Info        

  PCB PART NO-(800 LEVEL):   000-00000-00 

  PCB PART NO-(73 LEVEL):    00-00000-00 

  PCB REVISION (800 LEVEL):  AA 

  FAB PART NO-(28 LEVEL):    28-02011-01 

  PCB SERIAL NO:             648467 

  MANUFACTURING ENG:         0x1C       

  RMA HISTORY:               0x0 

On PXM1E and PXM45 platforms, the output of the MPSM dspliccd command also shows if a card is in slot license alarm. The following example shows the output of the dspliccd command of an MPSM-8T1-FRM card in a PXM45 platform in the slot license alarm state:

M8850_SF.1.28.MPSM8T1.FRM.a > dspliccd

Card License Alarm:              Minor

Service Module Type:             MPSM8T1E1

Service Module Serial Number:    SAG07208RRA

Provisioning (addcon) Allowed:   YES

=========================================================

Needed License Type               Needed Licenses

-------------------               ---------------

RateControl                       1

=========================================================

Allocated License Type            Allocated licenses

----------------------            ------------------

RateControl                       1

=========================================================

Programmed  License Type          Programmed licenses

------------------------          -------------------

RateControl                       1

=========================================================

Programmed License Registered:   YES

License registration node:       M8850_SF

Type <CR> to continue, Q<CR> to stop: 

License registration chassis:    SCA062300GF

=========================================================

---

Note If the switch is in node license alarm, you must rekey the PXM license pool before proceeding with any other license management tasks. (See the "Rekeying Feature Licenses" procedure.)

---

Grace Period

When the switch is in slot license alarm, you have a grace period of 5 days (120 hours) to resolve the alarms. During the first 4 days (96 hours), traps are sent every 24 hours. For the final 24 hours of the grace period, traps are sent every hour of operation. If the alarms are not cleared, the following actions are taken:

•An event is logged indicating the expiration of the grace period for a given slot needing licenses.

•A trap is sent hourly indicating the expiration of the grace period.

•Configuration commands for the licensed feature are disabled.

The following example shows the license status on an MPSM-16-T1E1 card after the grace period expires:

M8850_SF.7.PXM.a > dspliccd 27

M8850_SF                         System Rev: 05.02   Feb. 13, 2006 02:04:05 GMT

MGX8850                                              Node Alarm: CRITICAL

Card License Alarm:             Minor

Service Module Type:            MPSM-16-T1E1-PPP

Service Module Serial Number:   SAD0823086B

Provisioning Allowed:           No

Grace Period:                   Expired

=========================================================

Allocated License Type      Quantity

--------------------        --------

PPP                         1

=========================================================

Programmed License Type     Quantity

--------------------        --------

=========================================================

Programmed Licenses Registered:          N/A

License Registration Node:               --

License Registration Chassis Serial No:  --

The following example shows the error message if you try to add a connection after the grace period expires:

M8850_SF.27.MPSM16T1E1PPP[FR].a > addcon 16 1000 5 3 1 190461 -slave 
4700918100000000059A3F981B0000010B180200.0.2001 -lpcr 51600 -lscr 51600 -rpcr 51600 
-rscr 51600

ERR: Adding connections is blocked due to Node/Slot license alarm

After you rekey or add licenses to the PXM license pool, provisioning is restored and the switch exits the license alarm state.

Rekeying Feature Licenses

Use this rekey procedure to clear node license alarms.

The general procedure is as follows:

1. Obtain the node ID of the switch with Node License Alarms. See the "Obtaining Node IDs" procedure.

2. Contact Cisco TAC, provide the node ID, and request a rekey license. You will receive the license in an e-mail, which contains the license key and an attached license file.

3. Install the rekey license.

To install a rekey license, perform the following steps:

---

Step 1 If you are rekeying licenses using the license file, FTP the license file to the C:/LICENSE directory on the switch.

Step 2 Establish a configuration session with the switch using a username with SERVICE_GP privileges or greater.

Step 3 Enter the cnflic command.

•To add licenses using a license file, enter cnflic -f filename,

where filename is the e-mail attachment name.

•To add licenses using a license key, enter cnflic key,

where key is the license key string in the e-mail body.

The following example shows how to rekey a license using the license key:

M8850_SF.8.PXM.a > cnflic 
01050004e435730660768401f6608ec42404477f35d311f226fb3bd2992a92359da94c979d7ed2bff3d24c4630
25c1

Update method         :Rekey

Card type             :----

Creation date/time    :TUE JUL 06 21:02:43 2004

Grace period (days)   :0

Update sequence number:7

License serial number :L0000000502

Num of features       :0

---------------     -----

License Type        Qty 

---------------     -----

Please confirm the above license information.

cnflic:Do you want to proceed (Yes/No)? y

The following example shows how to rekey a license using a license file:

M8850_SF.8.PXM.a > cnflic -f L_20040706140923521.dat

Update method         :Rekey

Card type             :----

Creation date/time    :TUE JUL 06 21:09:23 2004

Grace period (days)   :0

Update sequence number:8

License serial number :L0000003455

Num of features       :0

---------------     -----

License Type        Qty 

---------------     -----

Please confirm the above license information.

cnflic:Do you want to proceed (Yes/No)? y

Step 4 To verify that license alarms are clear, enter the dspndalms command as follows:

M8850_SF.8.PXM.a > dspndalms

Node Alarm Summary

Alarm Type                     Critical        Major          Minor

----------                     --------       -------        -------

Clock Alarms                         0             0              0

Switching Alarms                     0             0              0

Environment Alarms                   0             0              0

Card Alarms                          0             0              0

Node License Alarm                   0             0              0

In this example, after applying the rekey license to the destination switch, the switch is no longer in Node License Alarm.

---

Caution To avoid losing licenses during a configuration restoration, save the switch configuration after applying the rekey license by using the saveallcnf command.

---

Step 5 Enter the saveallcnf command.

---

MPSM License Concepts and Terms

Table 26 lists the terminology used for managing feature licenses on MPSM cards.

Table 26 Feature License Terminology for MPSM Cards 

Term	Explanation
Allocated Licenses	To provide a feature or service, the PXM card allocates an available license to the MPSM card.
Available Licenses	The installed licenses which are not allocated are said to be available in the license pool for use by MPSM cards.
Encrypted Key	A lengthy string of characters that describe all information about purchased licenses as well as the node to which it can be applied.
Grace Period	Under certain conditions, if a sufficient number of licenses are not available or if licenses are invalid, the system continues to operate for a period of time without impacting service. This period is called the Grace Period, which is 5 days (120 hours). Note Within this period, it is responsibility of the system owner to purchase and install the required number of licenses to avoid service degradation after this period expires.
Installed Licenses	Refers to the purchased licenses which were added to the PXM license pool. The installed licenses in the license pool can be used by the service modules plugged into the MGX node. Licenses are used by the modules on as-needed basis.
License Pool	License Pool is a persistent database of all installed licenses on an MGX node. Service modules are allocated licenses from this pool to provide services and features. Licenses are added to the pool by installing them on the node using cnflic or movelic CLI commands.
Moving Licenses	When programmed licenses migrate from a module NVRAM into the license pool and become installed, you are moving the licenses from a card to the license pool.
Needed Licenses	Licenses that are required by an MPSM card to provide desired services or features. For an MPSM card to operate normally, it must have same number of allocated licenses as needed licenses.
Programmed Licenses	When the licenses are supplied in the NVRAM of a module, they are programmed licenses. These licenses cannot be allocated to any module, but they can be installed in a node by moving them from NVRAM of the module to the license pool owned by the MGX node.
Registering Licenses	When licenses are moved from the MPSM card NVRAM to the license pool, the process is also referred to as registering licenses with the node.
Rekey License	If a license becomes invalid for any reason, you must revalidate the license. The license that achieves this purpose is the Rekey License. Rekey license is the same as RAK.
Transferring Licenses	You can migrate installed licenses from the license pool of one MGX node to the license pool of another MGX node. This process is referred to as transferring licenses.

Documentation

A Finding Cisco User Documentation Online 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 27 lists acronyms that have been referenced in these release notes.

.

Table 27 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 greater)
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
VISM	Voice Interworking Service Module
VPN	Virtual Private Network
VRF	VPN Routing / Forwarding
VXSM	Voice Switch Service Module
XF	Express Forwarding

CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0601R)

© 2006 Cisco Systems, Inc. All rights reserved.