Cisco MGX 8800 Series Switches

Table Of Contents

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.0.00

Contents

About Release 5.0.00

Type of Release

Locating Software Updates

New Features and Enhancements in Release 5.0.00

SRME/B

Platforms

AXSM-16-155-XG

Platforms

AIS Delay, Deroute Delay, Absolute Grooming

Platforms

Soft Reroute

Platforms

Point to Multipoint Support on PXM1E

Platforms

Enhancements to Route Optimization

Platforms

Priority Bumping

Platform

Enhancements

Service Class Template (SCT) File Information

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-XG

FRSM-12-T3

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Hardware Supported

New Hardware in Release 5.0.00

APS Connectors

MGX 8850 (PXM45) Product IDs and Card Types

MGX 8850 (PXM1E) Product IDs and Card Types

MGX 8830 Product IDs and card types

MGX 8950 Product IDs and card types

New and Changed Commands

New and Changed PXM45 Commands

New Commands

Changed Commands

Removed PXM45 Commands

New and Changed PXM1E Commands

New Commands

Changed Commands

Removed PXM1E Commands

New and Changed AXSM Commands

New Commands

Changed Commands

Removed AXSM Commands

New and Changed AXSM-E Commands

New Commands

Changed Commands

Removed AXSM-E Commands

Limitations, Restrictions, and Notes for 5.0.00

Upgrading AXSM-XG card

Upgrading the VISM-PR Image

PXM1E Parity Errors

Upgrading to 5.0

Higher Level Logical Link Limits

CLI Upgrade

Preferred Route

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

Cell Bus Service Modules (formerly known as Narrow Band Service Module) and RPM-PR

IGX Feeder

Policing Accuracy for PXM1E

Maximum Threshold Accuracy for PXM45 and PXM1E

PXM1E-Based Switches

PXM1E Hardware Limitations

Reserved VCIs

AXSM-E OAM

CLI Configurable Access

Controller Card Mastership Sanity Verification

Serial Bus Path Fault Isolation

Cell Bus Path Fault Isolation and Recovery

FRSM-12-T3E3

Port and Connection Limitations

Disk Space Maintenance

Non-native Controller Front Card and PXM-HD Card

clrsmcnf Command

APS

Path and Connection Trace

Simple Network Timing Protocol (SNTP)

Priority Routing

SPVC Interop

Persistent Topology

Manual Clocking

AXSM Cards

AXSM-XG Hardware Limitation

ATM Multicast

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

Troubleshooting APS Lines

Installation and Upgrade Procedures

Upgrade Information

Maintenance Information

Caveats

MGX 8850, MGX 8830, and MGX 8950 5.0.00 Anomalies

Known Anomalies in Release 5.0.00

Resolved Anomalies in Release 5.0.00

Known Route Processor Module or MPLS Anomalies

MGX-RPM-XF-512 and MGX-RPM-PR-256/512 Anomalies

Documentation

Documentation Notes for the April 2004 Product Releases

Changes to this Document

Related Documentation

Technical Manual Order of Use

Technical Manual Titles and Descriptions

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Acronyms

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.0.00

---

These release notes are part OL-4538-01 Rev. C0, May 11, 2005.

Contents

About Release 5.0.00

These release notes describes the system requirements, new features, and limitations that apply to Release 5.0.00 of the, MGX 8850, MGX 8950, and MGX 8830 Multiservice Switches. These notes also contain Cisco support information.

These release notes complement the technical manuals listed in the "Changes to this Document" section.

Type of Release

Release 5.0.00 is a software and hardware release for the following MGX switches:

•MGX 8830 PNNI routing switch

•MGX 8850 (PXM1E)

•MGX 8850 (PXM45)

•MGX 8950

Locating Software Updates

This is the location for the MGX 8850 (PXM45/PXM1E), MGX 8830, and MGX 8950 5.0.00 software:

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

New Features and Enhancements in Release 5.0.00

SRME/B

This new card will be an enhancement of the existing SRME card. Like the SRME, the SRME/B is a single-height card, and the two key functions it supports are: T3 interface along with OC-3, as well as BERT, bulk distribution and 1:N redundancy.

There can be up to 2 SRME/Bs per service bay, for a total of up to 4 SRME/Bs per MGX node. With the MGX 8850, the SRME/Bs in slots 15 and 16 support Service Modules in the upper service bay with BERT, bulk distribution and 1:N redundancy, and the SRME/Bs in slots 31 and 32 provide a similar service to the lower bay. With the MGX 8830, a comparable support is provided by SRME/Bs installed in slots 7 and 14.

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

AXSM-16-155-XG

The AXSM-16-155-XG Service Module addresses the need for enhanced traffic management capabilities over a higher OC-3c/STM-1 port density. This card will provide a different option to customers currently using the AXSM/B and AXSM/E OC-3c/STM-1 modules.

This new AXSM-XG Service Module will support 124K connections and will provide a full 2.4 Gbps of usable bandwidth per card.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

AIS Delay, Deroute Delay, Absolute Grooming

AIS Delay: Sending AIS/Abit during grooming may cause customer to revert to backup facilities. The AIS Delay feature provides a mechanism to delay AIS/Abit up to a configurable time. This feature was supported in Release 4.0. The SNMP support for this feature is provided in Release 5.0.

Deroute Delay: This feature will allow some time for a failed NNI interface to recover at the physical layer, before the switch declares it as failed (due to LOS, LOF, AIS-P, and so forth). This feature was supported in Release 4.0. The SNMP support for this feature is provided in Release 5.0

Absolute Grooming This feature will allow grooming to use an absolute cost threshold in addition to percentage of threshold change. The feature was supported in 4.0. In this release, grooming thresholds have been enhanced to support AW, CTD, and CDV metrics on a per service category basis for both Percentage and Absolute Grooming Thresholds. The SNMP support for this feature is provided in Release 5.0.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Soft Reroute

Currently during grooming process the connection is derouted and rerouted when the connection is on a PNNI routed path. Even when the better/desired route is unavailable the connection shall be derouted and rerouted using PNNI. The soft reroute feature provides the user to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until connection has been established on along a new path. Thus soft route brings higher connection availability. Enhanced grooming process shall use soft reroute to route a connection on better/desired PNNI path

QoS is preserved/improved by soft reroute for the rerouting connection.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Point to Multipoint Support on PXM1E

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 a via node of a point-to-multipoint connection. If necessary, MGX with PXM1E can be enabled to perform limited branching or cell replication to support multiple parties or leaves of a point-to-multipoint connection.

Point-to-multipoint connection is for applications such as data and video broadcasts and LAN emulation. This feature supports new real-time and non-real-time applications, for example: distance-learning, live broadcasts, conferencing applications, financial data delivery (stock market feeds), white board collaboration, video conferencing, data and file replication, and video on demand.

Network efficiency is enhanced since multiple streams of data can be replaced with a single transmission up to the multicast distribution point, typically a MGX with PXM45. Point-to-multipoint differs from broadcast in the sense that it will attempt to replicate packets only to specific destination endpoints in the multicast distribution tree versus sending packets to each endpoint as in straight broadcast.

Platforms

This feature is supported on:

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Enhancements to Route Optimization

The feature enables the CWM to support scheduled/on-demand route optimization. The existing commands are also enhanced to support "Orderly Grooming" and allow users to schedule the route optimization based on "day(s) of the week". Trunk utilization factor is introduced to prevent connections from grooming to heavily loaded trunks.

The enhancements to route optimization enables customers to administer route optimization of connections from the Management station. The route optimization enhancements also include orderly grooming and trunk utilization factor for effectively managing the network.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Priority Bumping

Priority Bumping involves derouting of other lower priority calls (lower than the incoming call priority) in order to free up resources so that the incoming higher priority call can be routed. Calls might have to be derouted on Ingress as well as Egress Interface to free up resources. Bumping can happen at Source, Via or destination nodes. This feature will work for SVCs as well as SPVCs. SVCs which do not have priority signalled from CPE/SAPI (in case of Voice Calls) will use the priority of the Ingress Interface.

Platform

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Enhancements

The product enhancement requests (PERs) in Table 1 were introduced in Release 5.0.00.

Table 1 Product Enhancement Requests in Release 5.0.00 

Enhancement Number or Description	Purpose
Deroute Delay (5048)	See feature description.
Support in PNNI/SMs (AXSM-E, PXM1E) for the CLI commands "tstpndelay" and "cnfconseq" commands. (5494)	For connection fault isolation, MGX provides CLI commands tstpndelay, cnfconsegep, dspconsegep, delconsegep in earlier releases to debug the connection problem. This project adds the corresponding SNMP interfaces support and extends the tool to work on PXM1E uplink, AXSM-E, AXSM-XG cards, in addition to AXSM card and broadband SPVC supports.
AIS Delay, Absolute Grooming (6600)	See feature description.
Secure Remote Terminal Interface (6670)	This feature introduces Secure Shell (SSH) functionality on the MGX. SSH provides a secure way to transfer TCP/IP traffic to/from an MGX node, by encrypting all traffic.
TACACS+ for centralized user/password database (7056)	Prior to Release 5.0, each MGX switch maintained it's own authentication database and performed it's own authentication. In release 5.0, TACACS+ functionality allows setup of one or more centralized authentication servers. MGX switches will now be able to perform authentication against the centralized database making management easier. Also, prior to Release 5.0, MGX software provided five command privilege levels that could be assigned to a user to authorize execution of all commands allowed by the privilege level. There was no support for authorizing specific command execution on a per user basis. TACACS+ will allow customers to configure authorization for a user to execute specific commands.
SNMP support for Memory and CPU utilization statistics (6802)	This feature allows for access to historical and real-time data about Memory usage and CPU utilization statistics via an SNMP interface. Three MIBS will support the above: CISCO-PROCESS_MIB, CISCO-ENHANCED-MEMPOOL-MIB and CISCO-ATM-CONN-INFO-MIB.
POST, Online Diag, and HMM	POST, Online Diag, and HMM have been enhanced to ease usability and reliability. Commands have been modified and added. Starting in release 5.0.0, test failures shall result in recovery actions being taken.

Service Class Template (SCT) File Information

This section contains SCT file information for Release 5.0.00.

PXM1E

The Service Class Template (SCT) bundle in Release 5.0.00 includes updates:

•PXM1E_SCT.PORT.5

•PXM1E_SCT.PORT.6

The default SCTs provided with Release 5.0.00 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 check sum for the SCT files are as follows

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

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

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

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

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

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

Notes:

•PXM1E does not support CARD SCT.

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

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

•Use SCTs with larger vc thresholds configured for the VSI signalling service type. The maximum vc threshold value should be at least 50000 microseconds for the vsi signalling service type New SCTs 5,6 and 54, 55 (Cisco provided SCTs for the T3/E3, Combo cards and IMA group links respectively) have been released with minor version = 1. Custom SCTs need to upgrade to a new minor version if needed with the new recommended vc threshold values. It is possible to gracefully upgrade an SCT with minor version change without any traffic impact. Read the SCT config chapter of the configuration guide for more details on how to upgrade a SCT file to a new minor version.

AXSM and AXSM/B

•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 check sum for the SCT files are as follows

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

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

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

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

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

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

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

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

A user can do dspsctchksum <filename> to confirm that the checksum of the Cisco-released SCT file and the file on the node match.

AXSM-E

These are the new AXSM-E SCT files:

•CARD and PORT SCT 4 - policing enabled for PNNI, disabled for MPLS

•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 new AXSM-E SCT file:

•AXSME_SCT.PORT.4.V1: Check sum is = 0x778eb096

•AXSME_SCT.CARD.4.V1: Check sum is = 0x778eb096

•AXSME_SCT.PORT.5.V1: Check sum is = 0x53c67945= 1405516101

•AXSME_SCT.CARD.5.V1: Check sum is = 0x53c67945= 1405516101

•AXSME_SCT.PORT.6.V1: Check sum is = 0xb69ce935= 3063736629

•AXSME_SCT.PORT.52.V1: Check sum is = 0x199550ec= 429215980

•AXSME_SCT.PORT.53.V1: Check sum is = 0xf6d53485= 4141167749

•AXSME_SCT.PORT.54.V1: Check sum is = 0x2a96b5b9= 714519993

•AXSME_SCT.PORT.55.V1: Check sum is = 0x5403c5ac= 1409533356

•AXSME_SCT.CARD.52.V1: Check sum is = 0xde496f2= 233084658

AXSM-XG

These are the AXSM-4-2488-XG and AXSM-16-155-XG SCT Files:

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

•PORT SCT 100 (OC192), 200 (OC48), 300 (OC12), 400 (OC3), 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 checksum is:

•AXSMXG_SCT.PORT.100.V1: Check sum is = 0x5f948423= 1603568675

•AXSMXG_SCT.PORT.200.V1: Check sum is = 0x81574ebb= 2169982651

•AXSMXG_SCT.PORT.300.V1: Check sum is = 0x5f611c38= 1600199736

•AXSMXG_SCT.PORT.400.V1: Check sum is = 0x4abcdea2= 1253891746

•AXSMXG_SCT.PORT.500.V1: Check sum is = 0x5af0d52f= 1525732655

•AXSMXG_SCT.PORT.101.V1: Check sum is = 0xcc92df2b= 3432177451

•AXSMXG_SCT.PORT.201.V1: Check sum is = 0x5da0215d= 1570775389

•AXSMXG_SCT.PORT.301.V1: Check sum is = 0x778f4d56= 2005880150

•AXSMXG_SCT.PORT.401.V1: Check sum is = 0x3226a623= 841393699

•AXSMXG_SCT.PORT.501.V1: Check sum is = 0x39c8ba23= 969456163

•AXSMXG_SCT.PORT.110.V1: Check sum is = 0xca274606= 3391571462

•AXSMXG_SCT.PORT.210.V1: Check sum is = 0xe270801= 237438977

•AXSMXG_SCT.PORT.310.V1: Check sum is = 0x5a10b97= 94440343

•AXSMXG_SCT.PORT.410.V1: Check sum is = 0x45d6269e= 1171662494

•AXSMXG_SCT.PORT.510.V1: Check sum is = 0xfc5abda1= 4233805217

•AXSMXG_SCT.PORT.111.V1: Check sum is = 0x591c7f4b= 1495039819

•AXSMXG_SCT.PORT.211.V1: Check sum is = 0xea6fdaa3= 3933199011

•AXSMXG_SCT.PORT.311.V1: Check sum is = 0xbabc93fc= 3132920828

•AXSMXG_SCT.PORT.411.V1: Check sum is = 0x2d3fee1f= 759164447

•AXSMXG_SCT.PORT.511.V1: Check sum is = 0xdb32a295= 3677528725

•AXSMXG_SCT.CARD.1.V1: Check sum is = 0xc5c8f89c= 3318282396

•AXSMXG_SCT.CARD.2.V1: Check sum is = 0x22a08e85= 580947589

FRSM-12-T3

The SCT file for FRSM-12-T3E3 has the following changes:

•SCT ID 4 Frame Relay port with UPC enable

•SCT ID 5 Frame Relay port with UPC disable

•SCT ID 6 Frame Forwarding port with UPC enable

•SCT ID 7 Frame Forwarding port with UPC disable.

•SCT 4 and 5 are for Frame Relay service.

•SCT 6 and 7 are for Frame Forwarding service.

•ATM CAC is not supported.

•UPC cannot be configured using SCT

•WFQ and ABR is not supported in the port SCT

•Cosb min rate and excess priority cannot be configured in the port SCT

•Frame_Discard mode is always set and users should not change it

The checksum is:

•FRSM12_SCT.PORT.4.V1: Check sum is = 0x47a581f1= 1202029041

•FRSM12_SCT.PORT.5.V1: Check sum is = 0x6706e0e0= 1728504032

•FRSM12_SCT.PORT.6.V1: Check sum is = 0x7d04c769= 2097465193

•FRSM12_SCT.PORT.7.V1: Check sum is = 0x153066a1= 355493537

•FRSM12_SCT.CARD.4.V1: Check sum is = 0x357d963a= 897422906

•FRSM12_SCT.CARD.5.V1: Check sum is = 0x6702e0d3= 1728241875

•FRSM12_SCT.CARD.6.V1: Check sum is = 0x9488176c= 2491946860

•FRSM12_SCT.CARD.7.V1: Check sum is = 0xc60d6205= 3322765829

System Requirements

This section describes software compatible with this release, and lists the hardware supported in this release.

Software/Firmware Compatibility Matrix

Table 2 lists Cisco WAN or IOS products that are compatible with Release 5.0.00.

Table 2 MGX 5.0.00 Release Compatibility Matrix 

Switch or Component	Compatible Software Version
MGX 8230 (PXM1) MGX 8250 (PXM1) MGX 8850 (PXM1)	MGX 1.3.00 MGX 1.2.21 MGX 1.2.13 MGX 1.1.34
MGX 8850 (PXM45) MGX 8850 (PXM1E) MGX 8950 (PXM45) MGX 8830 (PXM1E)	MGX 5.0.00 MGX 4.0.15 MGX 3.0.25
BPX Switch Software:	Switch Software 9.4.10 Switch Software 9.3.36, 9.3.47 Switch Software 9.2.43
Cisco WAN Manager	CWM 15.0.00
MGX 8220 Shelf:	MGX 8220 5.0.20
VISM-PR	VISM 3.2.1 VISM 3.1.2
MGX 8880 (VXSM)	MGX 5.0.00 VXSM 5.0.00
IOS RPM-PR	12.3(2)T5
IOS RPM-XF	12.3(2)T5

MGX and RPM Software Version Compatibility Matrix

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

Table 3 MGX and RPM Software Version Compatibility Matrix 

Board Pair	Boot Software	Minimum Boot Code Version	Runtime Software	Latest Firmware Version	Minimum Firmware Version
PXM45/B	pxm45_005.000.000.200_bt.fw	5.0.00	pxm45_005.000.000.201_mgx.fw	5.0.00	5.0.00
PXM45/C	pxm45_005.000.000.200_bt.fw	5.0.00	pxm45_005.000.000.201_mgx.fw	5.0.00	5.0.00
PXM1E-4-155 (MGX 8850 (PXM1E) chassis)	pxm1e_005.000.000.200_bt.fw	5.0.00	pxm1e_005.000.000.201_mgx.fw	5.0.00	5.0.00
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.000.000.200_bt.fw	5.0.00	pxm1e_005.000.000.201_m30.fw	5.0.00	5.0.005
PXM1E-8-T3E3 (MGX 8830 chassis)
PXM1E-COMBO (MGX 8830 chassis)
AXSM-1-2488	axsm_005.000.000.200_bt.fw	5.0.00	axsm_005.000.000.201.fw	5.0.00	5.0.00
AXSM-16-155
AXSM-4-622
AXSM-16-T3/E3
AXSM-1-2488/B	axsm_005.000.000.200_bt.fw	5.0.00	axsm_005.000.000.201.fw	5.0.00	5.0.00
AXSM-16-155/B
AXSM-4-622/B
AXSM-16-T3/E3/B
AXSM-2-622-E	axsme_005.000.000.200_bt.fw	5.0.00	axsme_005.000.000.200.fw	5.0.00	5.0.00
AXSM-8-155-E
AXSM-16-T3E3-E
AXSM-32-T1E1-E
AXSM-4-2488-XG	axsmxg_005.000.000.202_bt.fw	5.0.00	axsmxg_005.000.000.202.fw	5.0.00	5.0.00
AXSM-1-9953-XG-
AXSM-16-155-XG
FRSM-12-T3E3	frsm12_005.000.000.200_bt.fw	5.0.00	frsm12_005.000.000.200.fw	5.0.00	5.0.00
MGX-VXSM-155 MGX-VXSM-T1E1	vxsm_005.000.000.200_bt.fw	5.0.00	vxsm_005.000.000.200.fw	5.0.00	5.0.00
MGX-SRME	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A	N/A
MGX-SRME/B	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A	N/A
SRM3T3/C	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A	N/A
AX-CESM-8E1	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
AX-CESM-8T1	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
MGX-CESM-8T1/B	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
MGX-AUSM-8T1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
MGX-AUSM-8E1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
AX-FRSM-8T1	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
AX-FRSM-8E1	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
AX-FRSM-8T1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
AX-FRSM-8E1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.000.003.200.fw	22.0.3	22.0.3
MGX-FRSM-HS2/B	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_022.000.003.200.fw	22.0.3	22.0.3
MGX-FRSM-2CT3	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_022.000.003.200.fw	22.0.3	22.0.3
MGX-FRSM-2T3E3	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_022.000.003200.fw	22.0.3	22.0.3
MGX-RPM-PR-256	rpm-boot-mz.123-2.T5	12.3(2)T5	rpm-js-mz.123-2.T5	12.3(2)T5	12.3(2)T5
MGX-RPM-PR-512	rpm-boot-mz.123-2.T5	12.3(2)T5	rpm-js-mz.123-2.T5	12.3(2)T5	12.3(2)T5
MGX-RPM-XF-512	rpmxf-boot-mz.123-2.T5	12.3(2)T5	rpmxf-p12-mz.123-2.T5	12.3(2)T5	12.3(2)T5
MGX-VISM-PR-8T1	vism_8t1e1_VI8_BT_3.2.00.fw	3.2.0	vism_8t1e1_003.052.010.200.fw (CALEA image) vism_8t1e1_003.002.010.200.fw (non-CALEA image)	3.52.10 3.2.10	3.52.10 3.2.10
MGX-VISM-PR-8E1	vism_8t1e1_VI8_BT_3.2.00.fw	3.2.0	vism_8t1e1_003.052.010.200.fw (CALEA image) vism_8t1e1_003.002.010.200.fw (non-CALEA image)	3.52.10 3.2.10	3.52.10 3.2.10

Additional Notes

The following notes provide additional compatibility information for this release:

•You can gracefully upgrade to Release 5.0.00 from a minimum Release of 3.0.25.

•MGX 5.0.00 interoperates with SES PNNI 4.0.15.

•Please see the "Release Notes for MGX 8850, 8230, and 8250 Software Version 1.2.20" for feeder feature issues. Release notes can be downloaded from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm

•You must use minimum release of CWM Release 15.0.0 Patch 1 to manage networks that contain MGX switches running Release 5.0.00.

Table 4 shows the various types of APS protocols that are supported on the AXSM/A and AXSM/B cards, and the MGX release that provides the support.

Table 4 APS Protocol Support 

Op Mode (APS Protocol)	Card Types
	AXSM/B
Op_A mode (GR253)	Release 2.1.x and higher
Op_B mode (GR253, ITU-T Annex A/B)	Release 3.0.00 and higher

SNMP MIB Release

•The SNMP MIB release for 5.0.00 is mgx8XXXrel5000mib.tar.

Hardware Supported

This section lists:

•MGX 8850 (PXM45) Product IDs, 800 part numbers, and revision levels

•MGX 8850 (PXM1E) Product IDs, 800 part numbers, and revision levels

•MGX 8830 Product IDs, 800 part numbers, and revision levels

•MGX 8950 Product IDs, 800 part numbers, and revision levels

This section also lists front and back card types, and whether APS connectors are supported for:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

---

Note For hardware installation instructions, refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5, part OL-4545-01. That guide covers from MGX Release 2 through 5.It is available at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/hwdoc/index.htm.

---

New Hardware in Release 5.0.00

The following new hardware is supported by the Release 5.0.00 software.

•AXSM-16-155-XG

•SRME/B

•MGX-BNC-3T3-M

•MGX-STM1-EL-1

APS Connectors

Table 5 lists MGX 8850 (PXM45/PXM1E) and MGX 8830 APS connectors.

Table 5 MGX 8850 (PXM45/PXM1E) and MGX 8830 APS Connectors 

MGX 8850 (PXM45) APS Connectors
Hardware	MGX-8850-APS-CON (800-20640-01)	MGX-APS-CON (800-05307-01)
AXSM-16-155 AXSM-16-155/B AXSM-4-622 AXSM-4-622/B AXSM-1-2488 AXSM-1-2488/B AXSM-8-155-E AXSM-2-622-E	Yes Yes Yes Yes Yes Yes Yes Yes	Yes Yes Yes Yes Yes Yes Yes Yes
SFP-8-155 MCC-8-155	Yes Yes	Yes Yes
MGX-SRME	Yes	No
MGX-SRME/B	Yes	No
MGX 8850 (PXM1E) APS Connectors
Hardware	MGX-8850-APS-CON (800-20640-01)	MGX-APS-CON (800-05307-01)
PXM1E-4-155	Yes	Yes
PXM1E-8-155	Yes	Yes
PXM1E-COMBO (See Note Below)	No	No
MGX-SRME	Yes	No
MGX-SRME/B	Yes	No
MGX 8830 APS Connectors
Hardware	MGX-8830-APS-CON (800-05308-02)
PXM1E-4-155	Yes
PXM1E-8-155	Yes
PXM1E-COMBO	No
MGX-SRME	No

---

Note The PXM1E-COMBO card is also known as PXM1E-T3E3-155 card.

---

MGX 8850 (PXM45) Product IDs and Card Types

Table 6 lists Product IDs, 800 part numbers, and the minimum revision levels for the MGX 8850 (PXM45).

Table 7 lists MGX 8850 (PXM45) front and back card types and whether APS connectors are supported in 4.0.1 0.

In Table 6, in the following cards, R- means that this is a redundant card:

•AX-R-RJ48-8E1

•AX-R-RJ48-8T1

•AX-R-SMB-8E1

Also, either of the following connectors work for the AXSM cards in the MGX 8850 (PXM45) switch:

•MGX-8850-APS-CON

•MGX-APS-CON

Table 6 Minimum Card Numbers and Revisions Supported in Release 5.0.00 for MGX 8850 (PXM45) 

Product ID	Minimum 800 Part Number	Minimum Revision
AX-CESM-8E1	800-02751-02	-A0
AX-CESM-8T1	800-02750-03	-B0
AX-FRSM-8E1	800-02438-04	-A0
AX-FRSM-8E1-C	800-02462-04	-A0
AX-FRSM-8T1	800-02461-04	-A0
AX-FRSM-8T1-C	800-02461-04	-A0
AX-RJ48-8E1	800-02408-01	-A0
AX-RJ48-8T1	800-02286-01	-A0
AX-R-RJ48-8E1	800-02409-01	-A0
AX-R-RJ48-8T1	800-02288-01	-A0
AX-R-SMB-8E1	800-02410-01	-A0
AXSM-1-2488	800-05795-05	-A0
AXSM-1-2488/B	800-07983-02	-A0
AXSM-16-155	800-05776-06	-A0
AXSM-16-155/B	800-07909-05	-A0
AXSM-16-T3E3	800-05778-08	-A0
AXSM-16-T3E3/B	800-07911-05	-A0
AXSM-16-T3E3-E	800-18519-02	-A0
AXSM-2-622-E	800-18521-02	-A0
AXSM-32-T1E1-E	800-22229-01	-A0
AXSM-4-622	800-05774-09	-B0
AXSM-4-622/B	800-07910-05	-A0
AXSM-8-155-E	800-18520-02	-A0
AX-SMB-8E1	800-02287-01	-A0
FRSM-12-T3E3	800-18731-02	-A0
MCC-16-E1	800-19853-02	-A0
MCC-8-155	800-22117-02	-A0
MGX-8850-APS-CON	800-20640-01	-A0
MGX-APS-CON	800-05307-01	-A0
MGX-BNC-2E3	800-04056-02	-A0
MGX-BNC-2T3	800-04057-02	-A0
MGX-BNC-3T3-M	800-03148-02	-A0
MGX-CESM-8T1/B	800-08613-02	-A0
MGX-FRSM-2CT3	800-06335-01	-D0
MGX-FRSM-2T3E3	800-02911-07	-D0
MGX-MMF-FE	800-03202-02	-A0
MGX-RJ45-4E/B	800-12134-01	-A0
MGX-RJ45-FE	800-02735-02	-A0
MGX-RJ48-8E1	800-19310-01	-B0
MGX-SMFIR-1-155	800-14460-02	-A0
MGX-SRM-3T3/C	800-05648-01	-A0
MGX-SRME	800-14224-02	-A0
MGX-SRME/B	800-21629-03	-A0
MGX-BNC-3T3-M	800-03148-02	-A0
MGX-STM1-EL-1	800-14479-02	-A0
MGX-STM1-EL-1	800-23175-03	-A0
MGX-VISM-PR-8E1	800-07991-02	-A0
MGX-VISM-PR-8T1	800-07990-02	-A0
MMF-4-155/C	800-07408-02	-A0
MMF-8-155-MT	800-04819-01	-A1
MMF-8-155-MT/B	800-07120-02	-A0
PXM45/B	800-09266-04	-A0
PXM45/C	800-20217-04	-A0
PXM45 (see Note 1 below)	800-06147-07	-B0
PXM-HD	800-05052-03	-A0
PXM-UI-S3	800-05787-02	-A0
PXM-UI-S3/B	800-21557-01	-A0
RBBN-16-T1E1	800-21805-03	-A0
SFP-8-155	800-21518-03	-A0
SMB-4-155	800-07425-02	-A0
SMB-6-T3E3	800-08799-01	-A0
SMB-8-E3	800-04093-02	-A0
SMB-8-T3	800-05029-02	-A0
SMF-4-2488-SFP	800-19913-04	-A0
SMFIR-1-622/C	800-07410-02	-A0
SMFIR-2-622	800-05383-01	-A1
SMFIR-2-622/B	800-07412-02	-B0
SMFIR-4-155/C	800-07108-02	-A0
SMFIR-8-155-LC	800-05342-01	-B0
SMFIR-8-155-LC/B	800-07864-02	-B0
SMFLR-1-2488	800-06635-04	-A0
SMFLR-1-2488/B	800-08847-01	-A0
SMFLR-1-622/C	800-07411-02	-A0
SMFLR-2-622	800-05385-01	-A1
SMFLR-2-622/B	800-07413-02	-B0
SMFLR-4-155/C	800-07409-02	-A0
SMFLR-8-155-LC	800-05343-01	-C0
SMFLR-8-155-LC/B	800-07865-02	-B0
SMFSR-1-2488	800-05490-05	-A0
SMFSR-1-2488/B	800-07255-01	-A0
SMFXLR-1-2488	800-05793-05	-A0
SMFXLR-1-2488/B	800-08849-01	-A0
MGX-VXSM-155	800-15121-06	-A0
MGX-VXSM-T1E1	800-24073-02	-A0
VXSM-BC-4-155	800-21428-06	-A0
VXSM-R-BC	800-21427-05	-A0
VXSM-BC-24T1E1	800-23088-03	-A0
MGX-RCON-1TO5	800-23094-02	-A0
MGX-RJ45-4E/B	800-12134-01	-A0
MGX-RJ45-FE	800-02735-02	-A0
MGX-RJ48-8E1	800-19310-01	-B0
MGX-RPM-PR-256	800-07178-02	-A0
MGX-RPM-PR-512	800-07656-02	-A0
MGX-RPM-XF-512	800-09307-06	-A0
MGX-XF-UI	800-09492-01	-A0
MGX-1-GE	800-18420-03	-A0
MGX-2-GE	800-20831-04	-A0
MGX-1OC12POS-IR	800-08359-05	-A0
MGX-2OC12POS-IR	800-21300-04	-A0
GLC-SX-MM (was MGX-GE-SX)	30-1301-01	-A0
GLC-LH-SM (was MGX-GE-LHLX)	30-1299-01	-A0
GLC-ZX-SM (was MGX-GE-ZX)	10-1439-01	-A0

Table 7 MGX 8850 (PXM45) Front and Back Card Types and Supported APS Connectors

Front Card Type	Back Card Types	Supports APS Connector (MGX APS-CON or MGX-8850-APS-CON)
PXM45/C	PXM-HD	—
	PXM-UI-S3/B	—
PXM45/B	PXM-HD	—
	PXM-UI-S3	—
PXM45 (not supported in Release 5.0.00 and higher)	PXM-HD	—
	PXM-UI-S3	—
AXSM-1-2488	SMFSR-1-2488	Yes
	SMFLR-1-2488	Yes
	SMFXLR-1-2488	Yes
MGX-VXSM-155	VXSM-BC-4-155
MGX-VXSM-T1E1	VXSM-R-BC
	VXSM-BC-24T1E1
AXSM-1-2488/B	SMFSR-1-2488/B	Yes
	SMFLR-1-2488/B	Yes
	SMFXLR-1-2488/B	Yes
AXSM-2-622-E	SMFIR-1-622/C	Yes
	SMFLR-1-622/C	Yes
AXSM-4-622	SMFIR-2-622	Yes
	SMFLR-2-622	Yes
AXSM-4-622/B	SMFIR-2-622/B	Yes
	SMFLR-2-622/B	Yes
AXSM-8-155-E	SMB-4-155	Yes
	MMF-4-155/C	Yes
	SMFIR-4-155/C	Yes
	SMFLR-4-155/C	Yes
AXSM-16-155	MMF-8-155-MT	Yes
	SMFIR-8-155-LC	Yes
	SMFLR-8-155-LC	Yes
AXSM-16-155/B	SMB-4-155	Yes
	MMF-8-155-MT/B	Yes
	SMFIR-8-155-LC/B	Yes
	SMFLR-8-155-LC/B	Yes
AXSM-16-T3E3, AXSM-16-T3E3/B AXSM-16-T3E3-E	SMB-8-T3	—
	SMB-8-E3	—
AXSM-32-T1E1-E	MCC-16-E1	—
	RBBN-16-T1E1	—
FRSM-12-T3E3	SMB-6-T3E3	—
MGX-VISM-PR-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-VISM-PR-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-SRME	MGX-SMFIR-1-155	Yes
	MGX-STM1-EL-1	Yes
MGX-SRME/B	MGX-BNC-3T3-M
	MGX-STM1-EL-1
MGX-SRM-3T3/C	MGX-BNC-3T3-M	—
AX-CESM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-CESM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
AX-FRSM-8T1-C	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1-C	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
AX-FRSM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-FRSM-2CT3	MGX-BNC-2T3	—
MGX-FRSM-2T3E3	MGX-BNC-2E3	—
	MGX-BNC-2T3	—
MGX-RPM-PR-256 MGX-RPM-PR-512	MGX-MMF-FE	—
	MGX-RJ45-4E/B	—
	MGX-RJ45-FE	—
MGX-RPM-XF-512	MGX-XF-UI	—
	MGX-1-GE	—
	MGX-2-GE	—
	MGX-1OC12POS-IR	—
	MGX-2OC12POS-IR	—
	GLC-LH-SM (was MGX-GE-LHLX1 )	—
	GLC-SX-MM(was MGX-GE-SX1)	—
	GLC-ZX-SM (was MGX-GE-ZX1)	—

1 Small form factor pluggable optical transceivers for MGX-1GE back card.

MGX 8850 (PXM1E) Product IDs and Card Types

Table 8 contains Product IDs, minimum 800 part numbers, and revision levels for the MGX 8850 (PXM1E) switch.

Table 9 lists MGX 8850 (PXM1E) front and back card types and whether APS connectors are supported.

Table 8 Minimum Card Numbers and Revisions Supported in Release 5.0.00 for MGX 8850 (PXM1E) 

Product ID	Minimum 800 Part Number	Minimum Revision
SRM-3T3/C	800-05648-01	-A0
BNC-3T3-M	800-03148-02	-A0
MCC-8-155	800-22117-02	-A0
SFP-8-155	800-21518-03	-A0
PXM1E-8-155	800-21686-05	-A0
PXM1E-4-155	800-18588-03	-A0
PXM1E-8-T3E3	800-18590-03	-A0
PXM1E-16-T1E1	800-18658-04	-A0
PXM1E-COMBO (See note below)	800-18604-03	-A0
MMF-4-155/C	800-07408-02	-A0
SMFIR-4-155/C	800-07108-02	-A0
SMFLR-4-155/C	800-07409-02	-A0
PXM-UI-S3/B	800-21557-01	-A0
SMB-8-T3	800-05029-02	-A0
SMB-8-E3	800-04093-02	-A0
MGX-T3E3-155	800-18698-02	-A0
MMF-1-155-SFP1	10-1308-01	-A0
SMFLR-1-155-SFP1	10-1280-01	-A0
SMFIR-1-155-SFP	10-1283-01	-A0
MCC-16-E1	800-19853-02	-A0
RBBN-16-T1E1	800-21805-03	-A0
MGX-VISM-PR-8T1	800-07990-02	-A0
MGX-VISM-PR-8E1	800-07991-02	-A0
MGX-SRME	800-14224-02	-A0
MGX-SRME/B	800-21629-03	-A0
MGX-SRM-3T3/C	800-05648-01	-A0
MGX-BNC-3T3-M	800-03148-02	-A0
MGX-SMFIR-1-155	800-14460-02	-A0
MGX-STM1-EL-1	800-14479-02	-A0
MGX-STM1-EL-1	800-23175-03	-A0
MGX-RPM-PR-256	800-07178-02	-A0
MGX-RPM-PR-512	800-07656-02	-A0
MGX-MMF-FE	800-03202-02	-A0
MGX-RJ45-4E/B	800-12134-01	-A0
MGX-RJ45-FE	800-02735-02	-A0
MGX-RJ48-8E1	800-19310-01	-B0
MGX-AUSM-8T1/B	800-04809-01	-A0
MGX-AUSM-8E1/B	800-04810-01	-A0
AX-CESM-8E1	800-02751-02	-A0
MGX-CESM-8T1/B	800-08613-02	-A0
AX-FRSM-8T1	800-02437-04	-A0
AX-FRSM-8E1	800-02438-04	-A0
AX-FRSM-8T1-C	800-02461-04	-A0
AX-FRSM-8E1-C	800-02462-04	-A0
MGX-FRSM-HS2/B	800-17066-01	-A0
MGX-FRSM-2CT3	800-06335-01	-D0
MGX-FRSM-2T3E3	800-02911-07	-D0
MGX-BNC-2T3	800-04057-02	-A0
MGX-BNC-2E3	800-04056-02	-A0
AX-SMB-8E1	800-02287-01	-A0
AX-R-SMB-8E12	800-02410-01	-A0
AX-RJ48-8E1	800-02408-01	-A0
AX-R-RJ48-8E12	800-02409-01	-A0
AX-RJ48-8T1	800-02286-01	-A0
AX-R-RJ48-8T12	800-02288-01	-A0
MGX-12IN1-8S	800-18302-01	-A0
SCSI2-2HSSI/B3	800-05463-02	-A0
	800-05501-01	-A0
MGX-8850-APS-CON	800-20640-01	-A0
MGX-APS-CON	800-05307-01	-A0

1 These cards are required only if you need modular optics with the PXM1E-COMBO back card. 2 R means that this is a redundant card. 3 The SCSI2-2HSSI/B card has two different 800 part numbers, and both part numbers are valid.

Table 9 MGX 8850 (PXM1E) Front and Back Card Types and Supported APS Connectors 

Front Card Type	Back Card Types	Needs APS-CON?
PXM1E-8-155	SFP-8-155	Yes
	MCC-8-155	Yes
	MMF-1-155-SFP1	Yes
	SMFLR-1-155-SFP1	Yes
	SMFIR-1-155-SFP1	Yes
	PXM-UI-S3/B	—
PXM1E-4-155	MMF-4-155/C	Yes
	SMFIR-4-155/C	Yes
	SMFLR-4-155/C	Yes
	PXM-UI-S3/B	—
PXM1E-8-T3E3	SMB-8-T3	—
	SMB-8-E3	—
	PXM-UI-S3/B	—
PXM1E-16-T1E1	PXM-UI-S3/B	—
	MCC-16-E1	—
	RBBN-16-T1E1	—
PXM1E-COMBO (See note below.)	MGX-T3E3-155	—
	MMF-1-155-SFP2	—
	SMFLR-1-155-SFP1	—
	SMFIR-1-155-SFP1	—
	PXM-UI-S3/B	—
MGX-VISM-PR-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-VISM-PR-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-SRME	MGX-SMFIR-1-155	Yes
	MGX-STM1-EL-1	Yes
MGX-SRME/B	MGX-BNC-3T3-M	Yes
	MGX-STM1-EL-1	Yes
MGX-SRM-3T3/C	MGX-BNC-3T3-M	—
MGX-RPM-PR-256 MGX-RPM-PR-512	MGX-MMF-FE	—
	MGX-RJ45-4E/B	—
	MGX-RJ45-FE	—
MGX-AUSM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-AUSM-8E1/B	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	MGX-RJ48-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
AX-CESM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-CESM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
AX-FRSM-8T1-C	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1-C	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-FRSM-HS2/B	SCSI2-2HSSI/B	—
	MGX-12IN1-8S	—
MGX-FRSM-2CT3	MGX-BNC-2T3	—
MGX-FRSM-2T3E3	MGX-BNC-2E3	—
	MGX-BNC-2T3	—

1 Small form factor pluggable optical transceivers for PXM1E-COMBO back card.

---

Note The PXM1E-COMBO card is also known as PXM1E-T3E3-155 card.

---

MGX 8830 Product IDs and card types

Table 10 lists Product IDs, minimum 800 part numbers, and minimum revision levels for the MGX 8830.

Table 11 lists MGX 8830 front and back card types and whether APS connectors are supported.

Table 10 Minimum Card Numbers and Revisions Supported in Release 5.0.00 for MGX 8830 

Product ID	Minimum 800 Part Number	Minimum Revision
PXM1E-8-155	800-21686-04	-A0
SFP-8-155	800-21518-03	-A0
MCC-8-155	800-22117-02	-A0
PXM-UI-S3/B	800-21557-01	-A0
PXM1E-4-155	800-18588-03	-A0
PXM1E-8-T3E3	800-18590-03	-A0
PXM1E-16-T1E1	800-18658-04	-A0
PXM1E-COMBO (See note below)	800-18604-03	-A0
MMF-4-155/C	800-07408-02	-A0
SMFIR-4-155/C	800-07108-02	-A0
SMFLR-4-155/C	800-07409-02	-A0
SMB-8-T3	800-05029-02	-A0
SMB-8-E3	800-04093-02	-A0
MGX-T3E3-155	800-18698-02	-A0
MMF-1-155-SFP1	10-1308-01	-A0
SMFLR-1-155-SFP1	10-1280-01	-A0
SMFIR-1-155-SFP	10-1283-01	-A0
MCC-16-E1	800-19853-02	-A0
RBBN-16-T1E1	800-21805-03	-A0
MGX-SRME	800-14224-02	-A0
MGX-SRM-3T3/C	800-05648-01	-A0
MGX-BNC-3T3-M	800-03148-02	-A0
MGX-SMFIR-1-155	800-14460-02	-A0
MGX-STM1-EL-1	800-14479-02	-A0
MGX-RPM-PR-256	800-07178-02	-A0
MGX-RPM-PR-512	800-07656-02	-A0
MGX-MMF-FE	800-03202-02	-A0
MGX-RJ45-4E/B	800-12134-01	-A0
MGX-RJ45-FE	800-02735-02	-A0
MGX-RJ48-8E1	800-19310-01	-B0
MGX-AUSM-8T1/B	800-04809-01	-A0
MGX-AUSM-8E1/B	800-04810-01	-A0
AX-CESM-8E1	800-02751-02	-A0
MGX-CESM-8T1/B	800-08613-02	-A0
AX-FRSM-8T1	800-02437-04	-A0
AX-FRSM-8E1	800-02438-04	-A0
AX-FRSM-8T1-C	800-02461-04	-A0
AX-FRSM-8E1-C	800-02462-04	-A0
AX-SMB-8E1	800-02287-01	-A0
AX-R-SMB-8E12	800-02410-01	-A0
AX-RJ48-8E1	800-02408-01	-A0
AX-R-RJ48-8E1	800-02409-01	-A0
AX-RJ48-8T1	800-02286-01	-A0
AX-R-RJ48-8T1	800-02288-01	-A0
MGX-12IN1-8S	800-18302-01	-A0
MGX-FRSM-HS2/B	800-17066-01	-A0
MGX-FRSM-2CT3	800-06335-01	-D0
MGX-FRSM-2T3E3	800-02911-07	-D0
MGX-BNC-2T3	800-04057-02	-A0
MGX-BNC-2E3	800-04056-02	-A0
SCSI2-2HSSI/B3	800-05463-02	-A0
	800-05501-01	-A0
MGX-VISM-PR-8E1	800-07991-02	-A0
MGX-VISM-PR-8T1	800-07990-02	-A0

1 These cards are required only if you need modular optics with the PXM1E-COMBO back card. 2 R means this is a redundant card. 3 The SCSI2-2HSSI/B card has two different 800 part numbers, and both part numbers are valid.

Table 11 MGX 8830 Front and Back Card Types and Supported APS Connectors 

Front Card Type	Back Card Types	Needs APS-CON?
PXM1E-8-155	SFP-8-155	Yes
	MCC-8-155	Yes
	PXM-UI-S3/B	—
PXM1E-4-155	MMF-4-155/C	Yes
	SMFIR-4-155/C	Yes
	SMFLR-4-155/C	Yes
	PXM-UI-S3/B	—
PXM1E-8-T3E3	SMB-8-T3	—
	SMB-8-E3	—
	PXM-UI-S3/B	—
PXM1E-COMBO (See note below.)	MGX-T3E3-155	No
	MMF-1-155-SFP1	—
	SMFLR-1-155-SFP1	—
	SMFIR-1-155-SFP1	—
	PXM-UI-S3/B	—
PXM1E-16-T1E1	MCC-16-E1	—
	RBBN-16-T1E1	—
	PXM-UI-S3/B	—
MGX-SRME	MGX-SMFIR-1-155	No
	MGX-STM1-EL-1	No
MGX-SRME/B	MGX-BNC-3T3-M
	MGX-STM1-EL-1	—
MGX-RPM-PR-256 MGX-RPM-PR-512	MGX-MMF-FE	—
	MGX-RJ45-4E/B	—
	MGX-RJ45-FE	—
MGX-AUSM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-AUSM-8E1/B	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	MGX-RJ48-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
AX-CESM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
AX-CESM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-CESM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
AX-FRSM-8T1-C	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
AX-FRSM-8E1-C	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-FRSM-HS2/B	SCSI2-2HSSI/B	—
	MGX-12IN1-8S	—
MGX-FRSM-2CT3	MGX-BNC-2T3	—
MGX-FRSM-2T3E3	MGX-BNC-2E3	—
	MGX-BNC-2T3	—
MGX-VISM-PR-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
MGX-VISM-PR-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—

1 Small form factor pluggable optical transceivers for the PXM1E-COMBO back card.

---

Note The PXM1E-COMBO card is also known as PXM1E-T3E3-155 card.

---

MGX 8950 Product IDs and card types

Table 12 lists Product IDs, Minimum 800 part numbers, and minimum revision levels for the MGX 8950.

Table 13 lists MGX 8950 front and back card types and whether APS connectors are supported.

---

Note MGX 8950 does not support the AXSM/A or the AXSM-E cards. If these cards are present, they will show up as "Failed" when the dspcds command is issued.

---

Table 12 Minimum Card Numbers and Revisions Supported in Release 5.0.00 for MGX 8950  

Product ID	Minimum 800 Part Number	Minimum Revision
PXM45/B	800-09266-04	-A0
PXM45/C	800-20217-03	-B0
PXM-UI-S3	800-05787-02	-A0
PXM-UI-S3/B	800-21557-01	-A0
PXM-HD	800-05052-03	-A0
AXSM-1-2488/B	800-07983-02	-A0
SMFSR-1-2488/B	800-07255-01	-A0
SMFLR-1-2488/B	800-08847-01	-A0
SMFXLR-1-2488/B	800-08849-01	-A0
AXSM-16-155/B	800-07909-05	-A0
AXSM-4-622/B	800-07910-05	-A0
AXSM-16-T3E3/B	800-07911-05	-A0
MMF-8-155-MT/B	800-07120-02	-A0
SMFIR-8-155-LC/B	800-07864-02	-B0
SMFLR-8-155-LC/B	800-07865-02	-B0
SMFIR-2-622/B	800-07412-02	-B0
SMFLR-2-622/B	800-07413-02	-B0
SMB-8-T3	800-05029-02	-A0
SMB-8-E3	800-04093-02	-A0
SMB-4-155	800-07425-02	-A0
XM-60	800-04706-06	-A0
AXSM-4-2488-XG	800-16987-04	-A0
AXSM-1-9953-XG	800-07365-06	-A0
AXSM-16-155-XG	800-20821-06	-A0
SMF-4-2488-SFP	800-19913-04	-A0
SMFSR-1-2488-SFP	10-1421-03	-A0
SMFLR-1-2488-SFP	10-1742-01	-A0
SMFSR-1-9953	800-08237-06	-A0
SMFIR-1-9953	800-08246-06	-A0
SMFLR-1-9953	800-08247-06	-A0
SFP-8-155	800-21518-03	-A0
MCC-8-155	80022117-02	-A0
MGX-APS-CON-8950	800-15308-01	-A0
MGX8950-EXTDR-CON	800-23813-03	-A0
MGX-MMF-FE	800-03202-02	-A0
MGX-RJ45-4E/B	800-12134-01	-A0
MGX-RJ45-FE	800-02735-02	-A0
MGX-RPM-PR-256	800-07178-02	-A0
MGX-RPM-PR-512	800-07656-02	-A0
MGX-RPM-XF-512	800-09307-06	-A0
MGX-1-GE	800-18420-03	-A0
MGX-2-GE	800-20831-04	-A0
MGX-XF-UI	800-09492-01	-A0
MGX-1OC12POS-IR	800-08359-05	-A0
MGX-2OC12POS-IR	800-21300-04	-A0
GLC-SX-MM (was MGX-GE-SX)	30-1301-01	-A0
GLC-LH-SM (was MGX-GE-LHLX)	30-1299-01	-A0
GLC-ZX-SM (was MGX-GE-ZX)	10-1439-01	-A0

Table 13 MGX 8950 Front and Back Card Types and Supported APS Connectors 

Front Card Type	Back Card Types	Supports APS Connector (MGX-APS-CON-8950)
AXSM-4-2488-XG	SMF-4-2488-SFP (SMFSR-1-2488-SFP SMFLR-1-2488-SFP)	—
AXSM-1-9953-XG	SMFSR-1-9953	—
	SMFIR-1-9953	—
	SMFLR-1-9953	—
AXSM-16-155-XG	SFP-8-155	Yes
	SMFIR-1-155-SFP	—
	SMFLR-1-155-SFP	—
	MMF-1-155-SFP	—
	MCC-8-155	Yes
PXM45/C	PXM-HD	—
	PXM-UI-S3/B	—
PXM45/B	PXM-HD	—
	PXM-UI-S3	—
AXSM-1-2488/B	SMFSR-1-2488/B	Yes
	SMFLR-1-2488/B	Yes
	SMFXLR-1-2488/B	Yes
AXSM-4-622/B	SMFIR-2-622/B	Yes
	SMFLR-2-622/B	Yes
AXSM-16-155/B	SMB-4-155	Yes
	MMF-8-155-MT/B	Yes
	SMFIR-8-155-LC/B	Yes
	SMFLR-8-155-LC/B	Yes
AXSM-16-T3E3/B	SMB-8-T3	—
	SMB-8-E3	—
MGX-RPM-PR-256 MGX-RPM-PR-512	MGX-MMF-FE	—
	MGX-RJ45-4E/B	—
	MGX-RJ45-FE	—
MGX-RPM-XF-512	MGX-XF-UI	—
	MGX-1GE	—
	MGX-2-GE	—
	MGX-1OC12POS-IR	—
	MGX-2OC12POS-IR	—
	GLC-LH-SM (was MGX-GE-LHLX1 )	—
	GLC-SX-MM(was MGX-GE-SX1)	—
	GLC-ZX-SM (was MGX-GE-ZX1)	—

1 Small form factor pluggable optical transceivers for MGX-1GE back card.

New and Changed Commands

This section lists which commands are new, changed, or removed, by card, in MGX Release 5.

Please refer to the following manuals for details about these commands:

•The Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5, part OL-4547-01, available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/cmdref/index.htm

•The Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5, part OL-4548-01, available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/axsm/index.htm

•Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00

New and Changed PXM45 Commands

This section lists commands that are new in, changed in, or removed from MGX Release 5 code for PXM45 cards.

New Commands

The following commands are new in MGX Release 5:

•clrpribumpstats

•cnfaaa-authen

•cnfaaa-author

•cnfaaa-ftpssh

•cnfaaa-ignore-ios

•cnfaaa-priv

•cnfaaa-prompt

•cnfaaa-server

•cnfcdmode

•cnfescreset

•cnflic

•cnfndconnpribump

•cnfndrteopt

•cnfpncpucong

•cnfrteoptthresh

•delaaa-server

•dspaaa

•dspaaa-servers

•dspaaa-stats

•dspaaa-tac-trace

•dspeng

•dspescreset

•dspHwAlms

•dsplicalms

•dspliccd

•dspliccds

•dsplicnodeid

•dsplics

•dspndconnpribump

•dspndrteopt

•dspoptrtereq

•dsppncpucong

•dsppndelay

•dsppndelays

•dsppribumpstats

•dsprcon

•dsprcons

•setaaa-tac-trace

•seteng

•ssh

Changed Commands

This section lists commands that are changed in MGX Release 5 for PXM45 cards. Specifically, the access level changed. In one case (dspcmdabbr), the state changed. Please refer to the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 manual for details.

Commands with Access Level Changes

The following commands had changes to their access level in MGX Release 5:

•checkflash

•clidbxlevel

•cnfpnni-pkttrace

•cnfpntracebuf

•cnfrmrsrc

•dbgaddilmiaddr

•dbgcon

•dbgdelilmiaddr

•dbgfailspvc

•dbgfailsvc

•dbgifm

•dbgilmi

•dbgpncli

•dbgpnni

•dbgpnsnmp

•dbgredman

•dbgsig

•dbgsntp

•dbgsscop

•dbgswover

•dbxclierrcode

•dspcmdabbr (State change)

•dspconsdbg

•dspdbgfailspvc

•dspdbgfailsvc

•dspdbgsig

•dspdbinfo

•dspdbsvrdb

•dspdbsvrdbbyname

•dspdbsvrsecdb

•dspdbsvrsecdbbyname

•dspmempart

•dspmsgq

•dspmsgqs

•dsppnni-dbg

•dsppnni-pkttrace

•dsppntracebuf

•dspsem

•dspsems

•dspsntp-dbg

•dsptask

•dsptasks

•dumptrace

•pntraceconrsrc

•pntraceroute

•pntracevsi

•pntracevsipkt

•printlog

•sesnwatchdog

•showsyserr

•smgrDataShow

•stackdump

•stacktrace

•sumDBShow

•syserr

•trace

Removed PXM45 Commands

The following commands were removed from MGX 5 code:

•pntracecallred

•pntracecon

•pntracegenred

•pntraceilmi

•pntraceitf

•pntraceprovrednode

•pntraceprovredport

•pntracesscop

•vxcd

•vxcopy

•vxll

•vxls

•vxpwd

•vxrename

•vxrm

New and Changed PXM1E Commands

This section lists commands that are new in, changed in, or removed from MGX Release 5 code for PXM1E cards.

New Commands

The following commands are new for PXM1E in MGX Release 5:

•clrpribumpstats

•cnfautorestart

•cnfimaparms

•cnflic

•cnfndconnpribump

•cnfndrteopt

•cnfpncpucong

•cnfrteoptthresh

•dspautorestart

•dspdiagresults

•dspdiagtests

•dspeng

•dspescreset

•dspHwAlms

•dspimaparms

•dsplicalms

•dspliccd

•dspliccds

•dsplicnodeid

•dsplics

•dspndconnpribump

•dspndrteopt

•dspoptrtereq

•dsppncpucong

•dsppndelay

•dsppndelays

•dsppnportpribumprsrc

•dsppostresults

•dsppribumpstats

•seteng

•setshellconnlog

•ssh

Changed Commands

This section lists commands that are changed in MGX Release 5 for PXM1E cards. Specifically, the access level changed. In one case (dspcmdabbr), the state level changed. Please refer to the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 manual for details.

Commands with Access Level Changes

The following commands had changes to their access level in MGX Release 5:

•checkflash

•clidbxlevel

•cnfpnni-pkttrace

•cnfpntracebuf

•cnfrmrsrc

•copychans

•copycons

•dbgaddilmiaddr

•dbgcon

•dbgdelilmiaddr

•dbgfailspvc

•dbgfailsvc

•dbgifm

•dbgilmi

•dbgpncli

•dbgpnni

•dbgpnsnmp

•dbgredman

•dbgsig

•dbgsntp

•dbgsscop

•dbgswover

•dbxclierrcode

•delallcon

•dspcons-dbg

•dspCproCnfg

•dspcprotbls

•dspdbgfailspvc

•dspdbgfailsvc

•dspdbgsig

•dspdbinfo

•dspdbsvrdb

•dspdbsvrdbbyname

•dspdbsvrsecdb

•dspdbsvrsecdbbyname

•dspmempart

•dspmsgq

•dspmsgqs

•dsppnni-dbg

•dsppnni-pkttrace

•dsppntracebuf

•dspsegment

•dspsegments

•dspsem

•dspsems

•dspsntp-dbg

•dspspvcif

•dspspvcifs

•dsptask

•dsptasks

•dumptrace

•pntraceconrsrc

•pntraceroute

•pntracevsi

•pntracevsipkt

•printlog

•sesnwatchdog

•showsyserr

•smgrDataShow

•stackdump

•stacktrace

•sumDBShow

•syserr

•trace

•dspcmdabbr

Removed PXM1E Commands

The following commands were removed from MGX 5 code:

•pntracecallred

•pntracecon

•pntracegenred

•pntraceilmi

•pntraceitf

•pntraceprovrednode

•pntraceprovredport

•pntracesscop

•vxcd

•vxcopy

•vxll

•vxls

•vxpwd

•vxrename

•vxrm

New and Changed AXSM Commands

This section lists commands that are new in, changed in, or removed from MGX Release 5 code for AXSM cards.

New Commands

The following commands are new in MGX Release 5:

•delsesn

•dspeng

•seteng

Changed Commands

This section lists commands that are changed in MGX Release 5 for AXSM cards. Specifically, the access level changed. Please refer to the Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 manual for details.

Commands with Access Level Changes

The following commands had changes to their access level in MGX Release 5:

•checkflash

•clidbxlevel

•clrbucketcstat

•cnfatlaslndiagstat

•cnfcellfilter

•cnfcosbdbg

•cnfrmrsrc

•copychans

•copycons

•dbxclierrcode

•delallcon

•dspatlasdiagcnfcstat

•dspatlasdiagcstat

•dspatlasdiagstatcnf

•dspatlaslndiagstat

•dspbucketcstat

•dspCproCnfg

•dspcprotbls

•dspdbinfo

•dspmempart

•dspmsgq

•dspmsgqs

•dspsegment

•dspsegments

•dspsem

•dspsems

•dspspvcif

•dspspvcifs

•dsptask

•dsptasks

•dspudpdiagcstat

•dspudpdiagstat

•sesnwatchdog

•showsyserr

•syserr

Removed AXSM Commands

No commands for AXSM were removed from MGX 5 code.

New and Changed AXSM-E Commands

This section lists commands that are new in, changed in, or removed from MGX Release 5 code for AXSM-E cards.

New Commands

The following commands are new in MGX Release 5:

•cnfautorestart

•cnfimaparms

•delsesn

•dspautorestart

•dspeng

•dspimaparms

•seteng

Changed Commands

This section lists commands that are changed in MGX Release 5 for AXSM-E cards. Specifically, the access level changed. Please refer to the Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 manual for details.

Commands with Access Level Changes

The following commands had changes to their access level in MGX Release 5:

•checkflash

•clidbxlevel

•cnfrmrsrc

•copychans

•copycons

•dbxclierrcode

•delallcon

•dspCproCnfg

•dspcprotbls

•dspdbinfo

•dspmempart

•dspmsgq

•dspmsgqs

•dspsegment

•dspsegments

•dspsem

•dspsems

•dspspvcif

•dspspvcifs

•dsptask

•dsptasks

•sesnwatchdog

•showsyserr

•syserr

Removed AXSM-E Commands

No commands for AXSM were removed from MGX 5 code.

Limitations, Restrictions, and Notes for 5.0.00

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

•Upgrade from Release 5.0 is only from 3.0.25 and higher.

•The VXSMs, when installed for the first time or after clearing the slot configuration, create default configuration. This creation of default configuration involves writing large amount of data to the hard disk in the node. So, when multiple VXSMs are installed simultaneously or the configuration of multiple VXSMs slots are cleared simultaneously, one or more VXSMs could fail to be installed. This results in following recommendations (refer to CSCed12646):

–install VXSMs using setrev command one at a time. Install another VXSM after the earlier one is installed completely and is Active.

–clear the VXSM slot configuration using clrsmcnf command (with no option where the slot primary software version is preserved) one at a time. Wait till the VXSM rebuilds after clearing the its slot configuration (without clearing the slot primary software version), before clearing the slot configuration of another VXSM slot.

•The percentage trunk utilization with overbooking is calculated using the following formula: overbooked MaxCR - overbooked ACR) / overbooked MaxCR. This will occur when inter-operating with SES from Release 3.0.x and higher.

---

Note ACR = MaxCR - (trunk utilization / overbooking factor) and
overbooked ACR = ACR / overbooking factor
overbooked MaxCR = MaxCR / overbooking factor.

---

–The overbooked ACR is calculated differently between 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.

•PXM45(A) card is not supported in Release 5.0.00 and onwards.

•It is not recommended to turn on complex node for physical nodes (the lowest level node), since this would increase memory usage but would not provide any benefits. Complex node should only be turned on for logical nodes.

•AXSM-16-155-XG with MCC backcards

The users may see following scenario when the card to card APS is configured on one side but not the other side: The Protection Line Status in dspapslns or dspapsln will show "OK" if the other side has added the card redundancy, upped the line but not the APS. If the backcards are SFP backcards, the Protection Line Status will be "SF" in the same setup.

From CLI screen on the side of APS added, the only way to find out remote APS has been added or not is through the Receive chanfield and modefield in dspapsln. Here are the display based on the APS protocol configured:

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

Upgrading AXSM-XG card

•When installing AXSM-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 (i.e., VUNI, VNNI, EVUNI, EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. Keep in mind that the signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit will be that the VPI value must be within the UNI ATM header limitations.

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.

PXM1E Parity Errors

•If CBC CBH RAM has parity error on active PXM1E card, and if there is no traffic passing on any connections, then PXM1E will not detect this parity error and will not switch over to the standby card. Also, all Service Module cards will reset. In a future release of MGX Release 5, the Online Diagnostics module will have a CellBus Parity test that will detect this condition and cause a switchover.

•PXM1E Standby card still comes up when there is a QE TS RAM parity error. In future release of MGX Release 5, Online diagnostics module will detect this condition on the Standby and cause the card to reset

Upgrading to 5.0

•Any invocation of 'reboot 0' from shellconn to reset a PXM card will result in an unconditional core dump on the card with reason "Reset From Shell". As a side effect, customers using the CLI command 'burnboot' to upgrade the PXM boot revision to Release 4.0.10 release from any older release will get a "Reset From Shell" Coredump while upgrading. This Coredump should be ignored. No future upgrades will be affected by this.

•PNNI trunk down temporarily after upgrade from Release 4.0.12 to 5.0. This upgrade problem is only seen in ILMI enabled E-VNNI/E-VUNI ports. As part of CSCec79854 ILMI behavior for E-VNNI and E-VUNI was changed. ILMI will go down as max_vpi and max_vpi_bits are exchanged differently between a virtual interface and non-virtual interface. Workaround has been documented in the DDTS. (refer to anomaly CSCed44174)

Higher Level Logical Link Limits

The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is turned on. The limit is essential to reduce the processing time involved in finding the bypasses between the logical links. Whenever there is a significant change in bandwidth in one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually found from one logical link to another. So if there are n logical links, the calculation involves the finding n*n bypasses. So if the number of logical links n is large, a lot of processing time is used for calculating the bypasses. So the number of logical links per level has to be limited to 30. The number can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.

CLI Upgrade

During an upgrade when the standby card has a 3.0.23 release or later runtime firmware and the active card has a pre-4.0 runtime firmware version, there is no display output from standby when cc command is issued. The error message "Err: cliSipcPsrRead(): received oversized message" appears from the active card. The workaround for this:

1. If PXM, connect to the console port of the standby if need to access it.

2. Complete the upgrade so that both service modules are running the same version.

The number of input characters for the CLI has increased from 256 to 512 bytes to accommodate more than 32 input parameters in 4.0 release firmware. So, when standby is has 4.0 release firmware and active has pre 4.0 release firmware, the active is receiving 512 bytes, thus receiving the error message above.

Preferred Route

Preferred routes are not supported for connections with endpoints on RPM and VISM card types in Releases 4.0 and above. Upgrading a preferred routing configured connection from any Release 3.0.x will be non-graceful. In a future release, the configuration of the preferred route identifier information for each connection will be supported on the Service Module cards instead of on the PXM controller. During the upgrade, the preferred route identifier information for each connection will be lost and the preferred route identifier needs to be reprovisioned on the Service Module cards. Also, the preferred route table at the PXM controller will be lost. Connections that have already been routed with preferred routing will remain, and there will be no alarms for these connections.

If a node in the PNNI network is removed via physical decommissioning, and if any nodes in the network had some preferred routes that contain the removed node as one of the hops, the preferred route(s) must be deleted/modified manually. When a connection is routed on a route other than its preferred route and if the preferred route becomes available, the connection would not be automatically derouted to route back to its preferred route. The user has to deroute/reroute by using configuration commands (optrte, rrtcon, dncon/upcon etc.). QoS precedence over Preferred Route does not apply to MPG network (CSCdz40310). Preferred route configured with higher node ID cannot be blocked (CSCdz41145, CSCdz49001). Due to differences in physical port numbering, non-MGX nodes can only be the terminating nodes in a preferred route.

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

•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 will fall back to version 1.0.

•The IMA link LIF(Loss of IMA Frame) and LODS(Link Out of Delay Synchronization) 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/sec 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 there is switchover, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.

•IMA Auto-restart(persistent RX IMA ID) feature is supported.

•IMA group 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 msec 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 as and 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. It is not supported on E1 interfaces.

•The port number in the pnport(shelf.slot:subslot.port:subport) could be a random number. The user should not interpret this number as line or IMA group number. Refer to DDTS CSCdy08500.

•PNNI requires SCR=453 cells/sec and PCR=969 cells/sec for the control connection.

•SSCOP requires of SCR=126 cells/sec and PCR= 2000 cells/sec.

Cell Bus Service Modules (formerly known as Narrow Band Service Module) and RPM-PR

When switchredcd is done and a PXM switchover (either through switchcc/resetcd on the PXM or due to a failure) happens at the same time (refer to anomaly CSCea36485):

•Conditions: switchredcd is run from PXM Command Line to perform CBSM Switchover. PXM switches over (manual or automatic) before the SM switchover is completed.

•Symptom: SM did not switchover after switchredcd

•If the PXM switches over before the CBSM switchover completes, the following issues can be seen:

–the SM Switchover may not be complete and the standby card will be in an indeterminate state. The dspcd command from PXM will still show it as 'standby' and later switchver (due to Active SM removal or reset) will fail, causing Loss of Traffic. The switchredcd command will also fail.

–The switchredcd from PXM again will cause the failure since the standby SM will not be able to allocate memory.

–Work round: Reset the standby Service Module card.

•CBSM feature is not available for PXM45/A

•CBSM (max dax con) 13,500 connections.

•CBSM (max non-dax) 27,000 connections.

IGX Feeder

When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number, this node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing cli command "rnmnd <x>" where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use cli command "dspnds +n". Failing to do so, CWM Databroker may have incorrectly formed hybrid connection database, the CWM GUI may show the connection as incomplete. IGX feeder is not support on AXSM-XG-16-155.

Policing Accuracy for PXM1E

There is a limitation regarding the policing accuracy for the PXM1E. The policing rate is defined as 50000000/PCR. If the PCR is comparable to the OC12 line rate (1412830), the policing rate parameter is a relative small number (50000000/1412830 = ~35.38996). Since integer division is performed, the decimal values are truncated. As a result, the policing parameter cannot be calculated accurately. Moreover, the policing rate parameter is stored in an exponent (5-bits) and mantissa (9-bits) format, so this format cannot represent a small number very accurately. Combining the above two factors, a 100% accurate policing parameter cannot be configured.

To ensure that the user gets the rate that they have specified, the software configures policing at the next larger rate which the hardware can support. For example, if we program a connection with PCR = 1400000, the software programs the actual policing rate to be 1428571. For a worst case scenario, if the user configures a VBR2 connection with a PCR of 1400010 and the ingress user traffic is 1428570, there won't be any policing because the ATM policing device would police at rate 1428571 only.

Maximum Threshold Accuracy for PXM45 and PXM1E

There is a limitation regarding the maximum threshold accuracy for the PXM45 and PXM1E. 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) and therefore we cannot calculate an exact 100% correct discard rate.

To ensure that the user gets the rate that they have specified, the software configures Qbin depth at the next larger rate which the hardware can support. As a result, Int. Cell Gap(ICG) and Relative Service Delay(RSD) are truncated.

PXM1E-Based Switches

The following notes apply to PXM1E based switches (that is, 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 backcards have to be present. A front card cannot drive the alternate trunk-backcard when its own local trunk-backcard 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 CBSM (Cell Bus Service Module).

•There is no bandwidth CACing support on the cell bus service modules, except for the RPM card, which is checked against the OC3 card rate. For example, for a given RPM, the bandwidth allocated to all connections may not exceed OC3 rate. Bandwidth CACing is supported on the PXM1E uplink port.

•The maximum bandwidth to be distributed among cell bus service modules is ~ OC10 while traffic on the network interfaces on PXM1E can achieve true OC12 line rate.

•Traffic should be balanced between the Cell Bus Controllers to achieve the OC-10 rate. The traffic should be distributed equally at a rate of about OC-5 on the two Cell Bus Controllers. The Cell Bus Controllers can't load share to achieve OC-10 with one Cell Bus set at an OC-6 rate, and another Cell Bus set at an OC-4 rate. Anything above OC-6 will be dropped. However, if only one Cell Bus Controller is used and the other Cell Bus controller is not used, then it can achieve OC-10. On an 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 8830, CBC0 supports slots 3,5,10, and 12 and CBC1 supports slots 4,6,11, and 13. Balance is achieved by planning the distribution of your cell base card by evenly distribute from left side of chassis and right side of chassis.

PXM1E Hardware Limitations

These are the PXM1E hardware limitations:

•For inter-card APS to work on the PXM1E-8-155 with one front card missing or unavailable, both backcards have to be present. A front card cannot drive the alternate trunk-backcard when its own local trunk-backcard 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-backcard functionality will not be available. Therefore, LED functionality will not be available, and APS lines will not work on that backcard.No modular optical transciever(SFP-8-155)-mismatches will be reported for that backcard. No SFP-8-155 mismatches will be reported during hardware upgrades.

•Since the PXM1E-4-155 and PXM1E-8-155 backcards support LC and SC interfaces respectively, the following limitation/restriction applies. For hardware upgrade from PXM1E-4-155, to PXM1E-8-155, it is required that, after the first PXM1E-4-155 card set is replaced by the PXM1E-8-155 card set, any cabling for the PXM1E-8-155 interfaces is updated with a LC-SC converter. Similarly, after the second card-set is replaced, the same needs to be done for the interfaces on the new card-set. If this is not done, the upgrade will not be graceful and will be service affecting, until appropriate cables are setup.

•When MGX-8850-APS-CON is used, and one trunk-backcard is removed, care must be taken to screw the remaining backcard in completely, to ensure that the contacts are complete.

•MGX-8850-APS-CON

–The Combo card does NOT require a mini-backplane. The PXM1E-8-155 REQUIRES a mini-backplane. The PXM1E-4-155 card does not require a mini-backplane but it is RECOMMENDED that one be inserted. This is to support graceful upgrade to PXM1E-8-155 cards in the future. Since the PXM1E-8-155 card requires a mini-backplane, if one is not already present when upgrading from PXM1E-4-155 to PXM1E-8-155, the upgrade cannot be graceful.

Reserved VCIs

Here are the reserved VCIs that the customer cannot provision:

•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, vci=5 is used for SSCOP for UNI signaling ports.(If the port is configured for non signaling (univer = none) then 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, vci=16 is used for ILMI if ILMI is enabled. VUNI, VNNI uses configured VPI for the port and VCI=16 for ILMI. Similarly, ILMI for EVNNI or EVUNI uses minimum vpi and vci=16.

•If MPLS is configured, vci=33 in the similar fashion as above.

•If NCDP is configured, minimum VPI and vci=34 for NCDP clocking.

•VPI=0 and VCI=31 are used for online diagnostics.

AXSM-E OAM

•Any connection can receive E2E/OAM loopback cells up to the line rate (as long as the policing policy permits).

•If the connection is not in the loopback mode and is operating in the normal mode, then the AXSM-E card can receive up to 1,500 segment OAM loopback cells per second. Any excessive segment OAM loopback cell will dropped. This limitation applies for all the connections on a card.

•For example, if there is only one connection, then that connection can receive 1,500 segment OAM loopback cells per second. If there are 2,000 connections on an AXSM-E card and one segment OAM loopback cell per second is being pumped through on each connection, then there can only be up to 1,500 connections to receive loopback cells at any given second, and the additional 500 connections would not receive for that second.

•The limitation is 1,500 segment OAM loopback cells per card and not per connection, the 1,500 cps assumes an even flow rate.

CLI Configurable Access

The following notes pertain to how command access levels can be configured:

•Not all CLI commands are allowed to be changed and a command cannot be changed to CISCO_GP group access level.

•Only the switch software is allowed to generate the binary file. This file has an authentication signature which has to be validated before the file can be used. Any manual changes to the file would 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.

•Currently, command names are verified, but an invalid command name may be parsed and be added to the binary file. However, this invalid name would be ignored later.

•If replication to standby failed, the installation process failed.

•cnfcli accesslevel default restores all command access levels to default for the service module that this command is executed on. It does not remove the binary file and this change is not persistent. If it is executed on the active card of a redundancy pair, the standby card is not affected. When the card is reset and the binary file exists, it will configure from the binary file when it is brought up.

Controller Card Mastership Sanity Verification

Because the solution provided in this release can only detect and log invalid mastership state transitions, an outage may still occur.

Serial Bus Path Fault Isolation

The Serial Bus Fault Isolation feature only addresses isolating errors on the local cards. However, when a common error occurs on the switching fabric card, this solution does not address this. As a result, if there is a problem on the PXM card or the XM60, the fault is going to be reported against all cards that detected the symptoms of this problem.

Cell Bus Path Fault Isolation and Recovery

The following notes pertain to cell bus path faults:

•The isolation procedures can isolate the Cell Bus path involving the QE SAR that is used for polling the Serial Bus based Service Modules (e.g., AXSM, AXSM/B, AXSM-E,) and all the communication with the standby controller card and the Cell Bus Based Service Modules (e.g., FRSM, CESM). These procedures can't isolate the Cell Bus path failures involving ATMizer SAR that is used for the inter-card communication except polling, between the active controller card and the Serial Bus based Service Modules (e.g., AXSM, AXSM/B, AXSM-E).

•The isolation procedures isolate the Cell Bus path failures to the active controller card only. This means, it is determined whether the active controller card has the fault for the inter-card communication over the Cell Bus from the active controller card to the Service Modules and the standby controller card or not. 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.

•There should be at least 2 cards (2 Service Modules or 1 Service Module and 1 standby PXM) for the isolation procedures to be able to isolate the Cell Bus path failures to the active controller card.

•Only the failures detected by periodic polling triggers the isolation procedures. Failures reported from other sources in the system against a Service Module or the standby controller card due to the Cell Bus path failures don't initiate the isolation procedures, and which results in resetting that card against 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.

•There is no separate trap/alarm generated against the active controller card Cell Bus path when the fault is isolated to the active controller card. Only the event logs will be available that can be used during the manual investigation triggered by the card reset and/or switchover traps.

•If there is no controller card redundancy available, isolating the Cell Bus path failure to active controller card results in outage as the active controller card will be reset.

FRSM-12-T3E3

The following limitations summarize the FRSM-12-T3E3 adherence to the current Functional Specification:

---

Note The FRSM-12-T3E3 card does not support E3.

---

•CLLM will not be supported: The FRSM-12-T3E3 card can support connection level congestion through ATM EFCI. It also supports FR-ATM interworking of ECN and EFCI. Frame level congestion only happens in full line rate of sub-15 byte frames, therefore the hardware will only support Port Level Congestion Management in the Frame Relay domain.

•BERT is not supported.

•Sub-rate DS3 is not supported.

•Online and Offline Diagnostics is not supported.

•Complete core dump is not supported.

Port and Connection Limitations

The following are port and connection limitations pertaining to the new FRSM-12-T3E3 card:

Port limitations:

•4 bytes header length with Stratacom LMI is not supported

•LMI on Frame Forwarding port is not supported

•If LMI is configured, Port header length cannot be changed

Connection Limitations:

•Single ended connections can only originate from FRSM12. Single-ended connections terminating on FRSM12 are not supported.

•The command chanType cannot be modified

•If Port header length is 2 bytes, Max DLCI number is 1023

•If Port header length is 2 bytes, the restricted DLCIs are 0, 1007 and 1023

•If Port header length is 4 bytes, the restricted DLCIs are 0 and 8257535

•To add a Frame Forward connection, the port should be configured to Frame Forward type.

•For Frame Forwarding ports, the maximum configurable connection(s) is 1.

•For Frame Relay ports, the maximum configurable connection(s) is 4000.

•If the connection is in loopback, it cannot be modified

•CIR can only be 0 for UBR connections

•If CIR equals to 0, Bc should also be zero, Be and zeroCirConEir should be nonzero.

•If CIR not equals to 0, Bc should be nonzero

•If chanType is Frame Forward, chanFECNconfig should be setEFCIzero, chanCLPtoDEmap should be ignoreCLP, chanDEtoCLPmap should not be mapCLP

•If chanType is NIW or NIWReplacem chanFECNconfig should be setEFCIzero, chanCLPtoDEmap should not be setDEzero or setDEone

•If chanType is frSIW_transparent or frSIW_translate, chanCLPtoDEmap should not be ignoreCLP

Maximum connections depending on LMI type:

•Annex A/D LMI, 2 byte header, FRF 1.2 not enabled: 898 conns

•Annex A/D LMI, 2 byte header, FRF 1.2 enabled: 1000 conns (port max)

•Annex A/D LMI, 4 byte header, FRF 1.2 not enabled: 640 conns

•Annex A/D LMI, 4 byte header, FRF 1.2 enabled: 4000 conns (port max)

•Strata LMI, 2 byte header, FRF 1.2 not enabled: 560 conns

•Strata LMI, 2 byte header, FRF 1.2 enabled: 1000 conns (port max)

Disk Space Maintenance

Because the firmware doesn't audit the disk space usage and remove unused files, the disk space in C: and E: drives should be manually monitored. Manually delete any 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 to avoid a shortage of disk space required to store event logs, configuration upload files in the C: drive and the configuration of MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards in the E: drive.

The following steps are recommended to remove files on the system from the active controller card:

---

Step 1 Change to the directory that needs grooming.

CLI cc <directory_name> 

Step 2 List the directory to identify old files that can be removed and available disk space.

CLI ll 

Step 3 To remove any old files (you may also use wildcards in the filename):

CLI rm <complete_filename> 

Step 4 List the directory to see if the file has been removed and disk space is available:

CLI ll 

---

Non-native Controller Front Card and PXM-HD Card

•When the front controller cards or the PXM-HD back cards are swapped within the same system, the system will perform a non-native card check, as a result, the controller card that attempts to come up as Active/Active may get resets 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 will copy its hard disk content over to the standby controller card. The active controller front card will not perform any automatic hard disk contents removal from neither the active nor standby controller card.

•The system will keep only the two most recent copy of the saved system configuration under C:/CNF directory. Customer may use ftp protocol to ftp all the saved configuration under C:/CNF to their local server for future references. All files under C:/CNF will not replicated over to the standby controller card under any circumstances.

clrsmcnf Command

These notes pertain to the clrsmcnf command:

•Cisco does not recommend executing clrsmcnf on more than one card at a time

•For the clear service module configuration feature, if there is a controller card switchover before the clear service module configuration operation is complete, the clrsmcnf command needs to be re-issued to ensure that the configuration is completely cleared to avoid any incomplete cleanup.

•For the clear service module configuration feature, using the clrsmcnf command may result in discrepancy in the PNNI configuration. For example, some connections may be in the mis-match state.

•If the clrsmcnf command is given with the <all> option to clear the software version for the slot as well, then the card will go into the boot/empty state after the operation is complete.

•While using the clrsmcnf command, the card in the specified slot is not usable until the operation has successfully completed.

APS

These notes pertain to the APS feature:

•For AXSM APS, the backcard of the active card MUST be present for APS to function.

•AXSMs need the backcard of the active front card for the APS to work. This implies that AXSMs do not support the cross backcard removal, upper backcard of one AXSM and lower backcard of another AXSM.

•If you remove the upper backcard of the active front AXSM, it will trigger switching active card. At this point the APS is OK. However, if the lower backcard of the current active AXSM is removed at this time, it will not trigger switching active card since the standby card is missing one of the backcard. At this point the lower backcard APS does not work since the backcard of the active front card is missing.

•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 active state. For a standby AXSM-E, AXSM-XG, and PXM1E cards, the LEDs always remain green whether the lines are in LOS irrespective of which lines are Active (refer to anomaly CSCdv68576).

Path and Connection Trace

These notes pertain to the path and connection trace features:

•Path trace is not supported on the control port.

•Path trace will not have the accurate information when there is a crankback on the connect path.

•Path and Connection trace since Release 3.0.00 is not compatible with the path and connection trace available with previous releases.

•Path and Connection trace supports point to point connections.

•Path and Connection trace supports MPG (multi-peer group) and SPG (single-peer group).

Simple Network Timing Protocol (SNTP)

The CWM MIB is not supported in the release.

Priority Routing

These notes pertain to the priority routing feature:

Prioritized reroute of SPVCs is not guaranteed, if the SPVCs originate on a signaling port. SPVCs may get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports.

•RPM does not support configuration of routing priority. All RPM mastered SPVCs will be assigned a routing priority of 8 by the PXM.

•addcon command on SES does not have support for specifying the routing priority. All the added SPVCs are assigned a routing priority of 8. cnfcon can be used to change the routing priority of the SPVCs.

•Changing the routing priority for dax connections, will not change the priority of the associated SVCs, this is because the SPVCs will not be derouted and rerouted if just the end-point parameters are changed, and routing priority is an end-point parameter. Also since dax connections are never derouted even when the UNI port goes down and rrtcon command is not supported for dax connections, the routing priority change will never get reflected. The only way for this to get reflected is to do a dncon and upcon. The very fact that dax connections are never derouted, the effect of this limitation is voided.

•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 scenarios we can expect RELEASEs to be transmitted out-of-order. This is because we do not want to hold up the release of other calls if we are not able to send RELEASEs on one of the interfaces, as it is congested. The calls that we are unable to release could be higher priority calls.

–Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can happen if we have attempted several times to route higher priority SPVCs, but failed. To prevent starvation of lower priority SPVCs, software will start to route lower priority SPVCs and software will get to the higher priority SPVCs at a later point in time.

SPVC Interop

These notes pertain to SPVC interoperability:

•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 Legacy Service Modules is not supported.

•Origination of Single ended spvcs (with -slavepersflag) from Legacy Service Modules (FRSM, CESM and RPM) is not supported.

•CC (Continuity Check) shall not be available at the slave end of a single-ended SPVC.

•Reporting AIS detection to CWM shall not be available at the slave end of a single-ended SPVC.

•tstdelay shall not be available at the slave end of a single-ended SPVC for MGX 8850. In case of SES-PNNI, the command is available from the PXM even for the slave endpoint.

•The slave end of a single-ended SPVC shall not be visible to CWM.

•If Single-ended SPVCs are originated from MGX switches, they can only be configured via CLI and not from CWM in the current release.

•Single-end Provisioning will not be supported for DAX connections as no value addition is seen for Interoperability.

•SPVC Statistics shall not be available for the slave endpoint of a single-ended SPVC because this endpoint is non-persistent.

•When the persistent slave endpoint of an existing SPVC connection is deleted and the master endpoint is allowed to remain, the connection may get established as a single-ended spvc connection. In this case, CWM will show the connection as "Incomplete."

•Override of SVC connections on a VPI due to an incoming SPVP request for that VPI is not supported The following override options alone are supported:

–spvcoverridesvc

–spvcoverridesvp

–spvpoverridesvp.

Persistent Topology

These notes pertain to the persistent topology feature:

•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 will be 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 release logical nodes, then the info for the logical node will be stored in the Topo DB, because there is no way to distinguish between physical nodes and pre-Release 4.0.00 release logical nodes. Logical nodes with Release 4.0.00 or later SW release will not be stored in the Topo DB.

•To delete a node info entry from the Topo DB, first remove the node itself from the network, either by disconnecting the cables, or 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 will still be stored in the other nodes, until they are flushed from those nodes. This would happen within an hour's time, but it is configurable as a PNNI timer value. If the node is deleted from the Topo DB within that hour's time, and the node does switchcc/reboot, then it's possible that the node info for that deleted node will be added back into the topo db.

•When the node id of a node is changed, the old node id is added back into the Topo DB as a new node entry. In addition, the old node id will still be stored in the topo DB of all the other nodes in the PG. In order 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 PG, and then delete the info 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 PG, the node info must be deleted from all the nodes in that PG, 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.

Manual Clocking

These notes pertain to manual clocking:

•AUSM can support only one clock. If a second clock is configured on the same AUSM card AUSM will negative acknowledge us. Attempts to configure the second clock will fail silently.

•NO clock sources supported on FRSM. If a clock source is configured on FRSM it will not be reflected in our database.

•When resetcd is invoked, the primary and secondary (if configured) clock sources will be recommitted. However, the clock on which the node is latched on to will not be requalified. Only the backup clock will be qualified if present. Recommitted means that the primary and secondary will get requalified and the node will temporarily latch onto the internal oscillator, After the clock is requalified, the node will lock onto the primary clock source once again.

AXSM Cards

If ER stamping is used, the rate interval does not provide sufficient accuracy to be completely effective. As a result, when an AXSM card is supporting a PNNI link which is congested with mixed CBR/ABR traffic, cells will be dropped. This Conditions only occurs when ER stamping is enabled and CI is disabled on an AXSM PNNI link, along with CBR/ABR traffic running so as cause congestion on the link.

We recommend that the CI/EFCI mechanism be used for rate feedback rather than the ER stamping mechanism, especially if CBR/ABR traffic is expected. Refer to anomaly CSCdw63829.

AXSM-XG Hardware Limitation

The IR/LR/XLR SFP modules will need a 10 db attenuator when connected with short cables. Otherwise we will be exceeding the specification for receiver sensitivity on the Rx.

ATM Multicast

The recommended configuration for MGX 8950 with ATM multicast application is as follows:

•MGX 8950 system loaded with AXSM/Bs without any AXSM-XG cards in the system

•MGX 8950 system loaded with all AXSM-XG based cards without AXSM/Bs in the system.

•The MGX 8950 system having a mix of AXSM-XG based card and AXSM/Bs is not a recommended configuration for ATM Multicast application. The limitation is due to the behavior of backplane serial buses in the system. The suggested workaround:

–In order for the MGX 8950 system with AXSM-XG based card and AXSM/B to be present in the network supporting ATM Multicast the PNNI Node configuration can be made as branching restricted. cnfpnni-node 1 -branchingRestricted on

Other Limitations and Restrictions

•When configuring virtual interfaces (i.e. VUNI, VNNI, EVUNI, EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. Keep in mind that the signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit will be that the VPI value must be within the UNI ATM header limitations.

•If command clrchancnt is executed while a dspchancnt command is currently active then the data displayed will be incorrect. Restarting the dspchancnt after the previous one has completed will display correct data.

•clrsmcnf will not work for redundant service modules.

•clrsmcnf will not work if an upgrade is in progress.

•If RPM-PR or RPM-XF is configured as a LSC (Label Switch Controller), execution of clrsmcnf command on those LSC slots will be rejected - as designed.

•Configuration information will not be synchronized between PXMs during upgrades. If there are any changes to the configuration during upgrades, the standby pxm needs to be rebooted. The standby PXM needs to be rebooted when it's in a stable state.

•The maximum number connections supported in Release 3.0.00 or later with PXM45/B is 250,000 connections.

•NCDP is not supported on BPX.

•CSCdz33652 - when you clear the chancnt while you are monitoring the chancnt. Once this happens we get garbage for the counters on the dspchancnt display. (AXSM-XG)

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

•Due to checks to prevent an inserted card from affecting the system, an additional step may be required when inserting two nonnative 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, the user needs to explicitly clean up stale SCT files (refer to anomaly CSCdw80282).

Troubleshooting APS Lines

Port light behavior changed in Release 3.0.00 as follows:

Port lights on AXSM /B front cards indicate the receive status of APS lines. The active front card always displays the status of the active line. The standby card always displays the status of the inactive line. If only one APS line fails, the line failure LED is always displayed on the standby front card.

Port lights on AXSM/B front cards indicate the receive status of the Physical Line connected to it. For example, when APS is configured for working line as 5.1.3 and protection line as 6.1.3, regardless of which card is active, port LED on card 5 will show the receive status of 5.1.3 and card 6 will show the receive status of 6.1.3.

---

Note The remainder of this section is the same as for Release 2.1.80 unless otherwise noted as updated for Release 3.0.00.

---

---

Caution When the active front card and the active line are in different slots and the inactive line has failed, it is easy to incorrectly identify the failed line as the line in the standby slot. To avoid disrupting traffic through the active line, verify which physical line is at fault before disconnecting the suspect line.

---

If the active line fails and the standby line is not available, the switch reports a critical alarm.

If the active line fails and the standby line takes over, the former standby line becomes the new active line, and the switch reports a major alarm.

If an AXSM/A front card fails, APS communication between the redundant front cards fails. This can result in one of the following situations:

•If both APS lines were working before the failure, an APS line failure causes a switchover to the protection line

•If either APS line failed prior to a front card failure, a failure on the active line does not cause a switchover to the other line. Because the standby front card failed, it cannot monitor the standby line and report when the line has recovered. This means that the active card cannot use the standby line until the standby front card is replaced and the line problem corrected.

Use the following procedure to troubleshoot APS lines.

---

Step 1 Enter the dsplns command to determine if the line in alarm is an APS line. The dsplns  command shows which lines are enabled for APS:

M8xx0_.1.node.a > dsplns

                                           Medium Medium 

  Sonet  Line     Line     Line    Frame   Line   Line     Alarm   APS 

  Line  State     Type     Lpbk   Scramble Coding Type     State   Enabled

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

   1.1     Up sonetSts12c NoLoop   Enable  Other ShortSMF    Clear Enable

   1.2     Up sonetSts12c NoLoop   Enable  Other ShortSMF    Clear Disable

   2.1     Up sonetSts12c NoLoop   Enable  Other ShortSMF    Clear Disable

   2.2     Up sonetSts12c NoLoop   Enable  Other ShortSMF    Clear Disable

If the line in alarm is an APS line, and has always functioned properly as an APS line, proceed to Step 2.

If the line in alarm has never functioned properly as an APS line, verify that the following are true:

•redundant front and back cards are in the appropriate bays and are installed at both ends of the line.

•cable is properly connected to both ends of the line.

•enter the dspapsbkplane command to verify that the APS connector is installed properly at both ends of the line.

Step 2 Enter the dspapslns command at both ends of the communication line to determine whether one or both lines in an APS pair are bad. Use Table 14 to help you determine which APS line is not functioning properly.

---

Note Table 14 is updated for Release 3.0.00.

---

Table 14 Troubleshooting APS Line Problems Using the dspaps Command 

Active Line	Working Line	Protection Line	Working Line LED	Protection Line LED	Description
Working	OK	OK	Green	Green	Active card is receiving signal on working and protection lines. This does not guarantee that transmit lines are functioning properly. You must view the status on remote switch.
Protection	SF	OK	Green for AXSM/A, Red for AXSM/A, Green for AXSM/B	Red	Active card is receiving signal on the protection line. No signal received on the working line.
Working	OK	SF	Green	Red	Active card is receiving signal on the working line. No signal received on the protection line.
Working	SF	SF	Red	Red	Active card is not receiving signal from either line. The working line was the last line to work.
Protection	SF	SF	Red	Red	Active card is not receiving signal from either line. The protection line was the last line to work.
Working	UNAVAIL	UNAVAIL			The card set is not complete. One or more cards have failed or been removed. See Table 15 to troubleshoot card errors.

If one or both lines appear to be bad, determine whether the working or protection line is in alarm. Troubleshoot and correct the standby line first. Replace the components along the signal path until the problem is resolved.

•If the dspapslns command at either end of the line indicates a front or back card problem, resolve that problem first. (See Table 15 to troubleshoot card problems).

•If the dspapslns command shows a signal failure on the standby line, replace that line.

•If the standby line is still down, replace the cards along the signal path.

Table 15 Troubleshooting Card Problems 

APS Line Failure	Possible Cause
All lines in upper and lower bays	Suspect a bad or removed front card. If both front cards are good, both back cards may be bad.
All lines in upper bay only. Lower bay APS lines ok.	Suspect bad upper bay back card.
All lines in lower bay only. Upper bay APS lines OK.	Suspect bad lower bay back card.

---

Installation and Upgrade Procedures

For information on the following installation and upgrade procedures, please refer to the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

Upgrade Information

The upgrade appendix in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 contains the following procedures:

•Graceful PXM1E Boot Upgrades from Release 3.0

•Graceful PXM1E Boot Upgrades from Release 3.0.20

•Non-Graceful PXM1E Boot Upgrades

•Graceful PXM1E Runtime Software Upgrades

•Non-Graceful PXM1E Runtime Software Upgrades

•Graceful PXM45, AXSM, and FRSM-12-T3E3 Runtime Software Upgrades

•Non-Graceful PXM45, AXSM, and FRSM-12-T3E3 Runtime Software Upgrades

•Graceful AXSM or FRSM-12-T3E3 Boot Upgrades

•Non-Graceful AXSM or FRSM-12-T3E3 Boot 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 Boot Software Upgrades

•Graceful RPM-PR Runtime Software Upgrades

•Non-Graceful RPM-PR Boot Software Upgrades

•Non-Graceful RPM-PR Runtime Software Upgrades

•Installing SCT Files

Maintenance Information

The upgrade appendix in the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 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.

Caveats

This section provides information about known anomalies.

MGX 8850, MGX 8830, and MGX 8950 5.0.00 Anomalies

Anomalies are organized as follows:

•Known Anomalies in Release 5.0.00

•Resolved Anomalies in Release 5.0.00

Known Anomalies in Release 5.0.00

Table 16 Known Anomalies in Release 5.0.00 

Bug ID	Description
CSCea42088	Symptom: Can not modify the remote ICR value. Conditions: ABR XPVC connection between AXSM-E and bxm. Workaround: None Headline: Need ability to modify the remote ICR for the abr service Hardware: AXSM-E
CSCea65034	Symptom: dspDevErr/dspDevhist doesn't work on standby PXM. Condition: According to function specification of HMM on PXM1E the Device- triggered test are run on both Active and standby PXMs, but the dspDevErr and dspDevErrhist doesn't work on standby PXM. Workaround: None Headline: dspDevErr/dspDevhist doesn't work on standby PXM Hardware: pxm45
CSCeb28420	Symptom: Event log indicates emSyncHumveePort failures Condition: None Workaround: None Headline: EvtLog:emSyncHumveePort fail messages in log Hardware: AXSM-E
CSCeb38926	Symptom: Active PXM stays in backup boot after restoreallcnf is done Conditions: restoreallcnf was performed Workaround: None Headline: REG4+:MGX8850 node stuck while booting up after a reset Hardware: PXM45/B
CSCeb83965	Symptom: Certain CLI command output exceeds the 80 char limit Conditions: None Workaround: None Headline: Policing of 80 char limit for dsplns on AXSM-E Hardware: AXSM-E
CSCed09998	Symptom: With a custom SCT configured on the AXSM with only GCRA2 enabled [either set to tag or discard] policing will not function correctly. This problem will only happen if GCRA1 is disabled. Conditions: The problem only pertains to non-compliant traffic that should be either tagged or discarded by GCRA2 as configured in the SCT. Non-compliant cells are still counted and can bee seen in dspchancnt, but no action is taken. Workaround: Enable GCRA1 policing as well, or to disable policing entirely on the connection. Headline: AXSM-XG support for ABR dual leaky bucket. Hardware: AXSM-XG
CSCed10963	Symptom: Changes to xcnfalm parameters changes to not take effect. Conditions: FRSM2-C23T3 F/W 10.0.15 Workaround: Resetting the card or issuing a addds3loop/delds3loop command on the port, both of which are service effecting, and are the only ways to have the parameter changes take effect. Headline: Changes to xcnfalm settings do not take effect without card reset. Hardware:
CSCed42482	Symptom: get_nest failed for feeder Conditions: None Workaround: Switchover to standby PXM Headline: getnext failing for feeder request Hardware: PXM45/B
CSCed43129	Symptom AXSM-E card went into Active-F state Conditions: Card was reset by overnight script Workaround: None Headline: AXSM-E card went into Active-F after card came up due to reset Hardware: AXSM-E
CSCed45061	Symptom: Cannot telnet to MGX because all telnet sessions show incorrectly as being in use. These cannot be deleted by delsesn. Conditions: PXM1E running 3.0.23. Workaround: switchcc Headline: PXM1E: Telnet sessions cannot be deleted Hardware: pxm1e
CSCed45527	Symptom: Issuing the "bootchange" CLI and updating the netmask field causes hostname and filename fields to get populated incorrectly Conditions: None Workaround: Type in some values in the hostname and filename fields before updating netmask Headline: bootChange applies incorrect default values to some fields Hardware: PXM45/B
CSCed56640	Symptom: Standby PXM is stuck in INIT state during rebuild. Conditions: Due to communication failure between Active PXM and the Standby PXM, RAM synchronization of IPCONN application fails. Workaround: Manually reset the Standby PXM. Headline: IPCONN: Standby PXM is stuck in INIT forever due to IPCONN sync fail Hardware: PXM45/B
CSCed59288	Symptom: 01/27/2004-21:45:48 08 tRootTask SYS-1-TASKLOSTFATAL Trouble-Task[tLicMgrSrvr]: action is SYSTEM RESET Conditions: PXM1 - 1.3(00.047) Workaround: None Headline: tRootTask:SYS-1-TASKLOSTFATAL system reset on pxm1 Hardware:
CSCed61671	Symptom: Both the Active and Standby PXM trunk back card is declared MISMATCH. Conditions: 1. During switchcc, the active pxm resets and come back as mismatch. Since this is a feature mismatch in Release 3.x, this puts the active card also in mismatch. 2. Rarely during power cycle or resetcd or resetsys. Workaround: You can reset the standby card from the active. The standby will reset and likely to come up without mismatch. At this time, the active will still be in mismatch. If the standby comes up without mismatch, the active will reset and both the cards will come up with out any mismatches. Headline: PXM1E-16T1E1 comes up with TBC in Mismatch Hardware: pxm1e-ima
CSCed62493	Symptom: A file copied from the PXM hard disk to another location appear to be truncated and incomplete. Conditions: If a file is transferred to the PXM hard disk and immediately copied to another location, only partial file gets copied. Workaround: After transferring the file to the PXM hard disk, wait for at least 5 seconds before accessing the file. Headline: DOS: Inconsistent file size and contents immediately after FTP Hardware: pxm45
CSCed65346	Symptom: MGX 8850 platform only supports SNMPv1 packets. On receipt of SNMPv2 or SNMPv3 packets, an event is logged and the packet is dropped. However, the logging of these messages is not throttled, and the event logged can be filled up very quickly logging 1 event per received packet with unknown SNMP version. Conditions: Always. Workaround: None. Headline: Need to throttle event logging for Bad SNMP packets and keep stats Hardware: all
CSCed67641	Symptom: The sntp should update TOD information if and only if offset value is larger than 200. Conditions: When the calculation for offset (seconds field) value is 0xffffffff (-1) and fractional sec is not larger than 200ms. We should not update TOD information. Workaround: Increase the polling timer to larger value (ex. 1024). Headline: SNTP updated TOD information more frequently than should be. Hardware: pxm45
CSCed74374	Symptom: AUSM card stuck in Boot State Conditions: Reset Active RED (1:N) card Workaround: None Headline: REG5: RED Active AUSM card stuck in Boot State after Resetcd Hardware: pxm1e
CSCed81573	Symptom: cc session to an FRSM_2E3 card would fail Condition: None Workaround: None Headline: Tracking code review for Vxworks prob w/ semaphore (cant cc to card Hardware: frsm-vhs
CSCed86130	Symptom: Line can not detect RAI if LineCondition feature is enabled on any channel on the line. Conditions: Line should have at least one structured channel with LineCondition enabled on it. Workaround: None Headline: CESM-8t1e1 disables processing of RAI if lineCondition enabled. Hardware: cesm-8t1e1
CSCed86771	Symptoms: Pull/insert RPM-XF while running call rate, made the card to reload and failed. Conditions: While running 360K BHCA (Busy Hour Call Attempts) with 120 sec CHT. Upon pulling one of RPM-XF card and putting it back into the rack, this RPM-XF card rebooted and went to failed state. Workaround: None Headline: Pull RPM while running call rate and RPM failed Hardware: rpm-xf
CSCed89620	Symptom: After offline diag is done on AXSM-XG, it takes 3 hours before the card come back to standby state. Conditions: AXSM-XG fails to send offline diag result to PXM45. Workaround: PXM45 will reset the AXSM-XG card if it does not receive the offline diag result in 3 hours. User can also reset the AXSM-XG card manually. Typically the full coverage offline diag takes about 17 minutes to complete. Headline: AXSM-XG offline diag fail on timeout 3 hours later Hardware: AXSM-XG
CSCed93586	Symptom: Cisco MGX Route Processor Module-PRemium (RPM-PR) and RPM-XF may not go ACTIVE due to continuous resets. Conditions: This might happen only if 1. On Processor switch module (PXM), IPC seat id exceeds 0x0FFF000. 2. If Cisco IOS release running on RPM-PR and XF supports "IPC Split Init feature". Workaround: ipc_clear_stat (from PXM shellconn) will reset the IPC seat id to default. Note: Refer CSCdz63416 for more details on "IPC split Init feature". Headline: RPMXF card does not come up; keeps waiting for ctc port registration Hardware: pxm45
CSCed94954	Symptom: pnCcb task had an exception. Conditions: This happens only if Priority Bumping feature is enabled on a switch. This happened during an overnight script which resets all service modules on the switch every 20 minutes. Workaround: None. Headline: pnCcb exception caused switchover Hardware: PXM45/B
CSCee05255	Symptom: pnPnni task suspended. Conditions: This happened during an overnight script which resets all service modules on the switch every 20 minutes. Workaround: None. Headline: PNNI crashed after running resetcd script Hardware: pxm45
CSCee06558	Symptom: Secondary clock source went through re-qualification Conditions: Clock source was BITs input on PXM and switchredcd was issued on SM Workaround: None Headline: Sec.Clk on PXM BITs port requalified on SM switchover Hardware: PXM45/B
CSCee08180	Symptom: Watchdog timeout reset Condition: normal working condition Workaround: None Headline: Watchdog timeout reset on node a51 Hardware: PXM45/C
CSCee09022	Symptom: Default values for TOD and VPI/VCI parameters in cnfrteopt not reinstituted Conditions: TOD and VPI/VCI configured to specific value and then reverted to default ranges Workaround: None Headline: reverting cnfrteopt TOD and VPI/VCI parameters to defaults Hardware: PXM45/B
CSCee09158	Symptom: AXSM-E OC12 card resets Conditions: Bootchange command issued without changing any of the parameter values Workaround: None Headline: bootchange cmd on AXSM-E OC12 w/o changes caused card reset Hardware: AXSM-E
CSCee10237	Symptom: C:CUT directory is missing and not recreated on card reboot Conditions: C:CUT directory is accidently deleted by the user. Workaround: Manually create the C:CUT directory. Headline: Fail to automatically create CUT dir if accidently deleted Hardware: pxm45
CSCee10294	Symptom: VSI major errors reported in event log Condition: Connections on card were being modified for % util Workaround: when this following error message is seen on standby, please reset the standby which brings up the standby card to a clean state. 10S62829 03/23/2004-15:08:59 VSI_-4-RMLCNREDError tVsiSlave VrmModStdbyDelList4AddC [ERROR 0xE509 602] Deleted list is empty.: 0, 0, 0, 0, 0 Headline: VSI error messages - conn ID add/delete problems Hardware: AXSM1b_oc3
CSCee12720	Symptom: VSI major error recorded in event log Conditions: None Workaround: None Headline: IPC resolve errors from task tVsiSlave Hardware: AXSM1b_oc12
CSCee17164	Symptom: dspatmlayercnt shows all zero on the lower bay. Conditions: XG card with lower bay Workaround: None Headline: dspatmlayercnt shows all zeros on lower bay line on AXSM-16-155-XG Hardware: AXSM-XG
CSCee20817	Symptom: Data outage on connections from MPSM endpoints routed over AXSM interfaces Conditions: switchover executed on AXSM. Workaround: Unknown Headline: AXSM switchover resulted in data outage on AXSM-MPSM conns Hardware: AXSM1b_oc12

Resolved Anomalies in Release 5.0.00

CSCdv32986 100% data is getting dropped on some connections

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

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 P2MPJ 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 mea

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 630ms, >250ms

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 doesn't 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 Cant cc on AXSM due to max sessions in hang

CSCec23758 FRSM HS1 connections stuck in AIS alarm after card reset.

CSCec27723 Pnni signalling lcn reuse - pnni link cannot establish

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

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

CSCec33505 Receive FIFO not held in reset during dnln.

CSCec35834 Card failed to come back active after reboot (RPM)

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

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

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

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

CSCec42058 Statistical Alarm counters are not ok

CSCec42174 getting xbar alarm with offline diags enabled

CSCec42531 Err on switchcc outstanding database update

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

CSCec45604 Re-used port stay in alarm

CSCec45631 UI-S3 Clock Controller fails to enter Free Run mode

CSCec49118 Standby AXSM Failed due to IPC buffer leak on Active AXSM

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

CSCec51074 backcard aps mux not set accordingly after switchred

CSCec51349 PXM1e reset after pumping high rate oam loopback

CSCec55245 Allowing to turn off rate control feature with ABR configured

CSCec55319 Mem leakage in procResponse RespCalcC exhausting SSI SNMP partition

CSCec55976 vsiSlave Task suspended recovery action should be Fatal

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

CSCec59926 dump commands pause indefinitely with RPMs and may leak resources

CSCec62846 Failure on the data forwarding path was not detected

CSCec63239 VxWork 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:Cant 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 Configupload 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:Can't 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-XGOC3

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 axsmxg path in alarm after upgrade

CSCee16959 PXM45 not downloading enable.stats file to SMs after switchredcd

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

Known Route Processor Module or MPLS Anomalies

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

MGX-RPM-XF-512 and MGX-RPM-PR-256/512 Anomalies

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

For information about anomalies with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T5 for MGX Releases 1.3.00 and 5.0.00.

Documentation

A Guide to Cisco Multiservice Switch and Media Gateway Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.

Documentation Notes for the April 2004 Product Releases

The April 2004 release includes new hardware or features for the following releases:

•Cisco MGX Release 5 for the MGX 8880 Media Gateway

•Cisco MGX Release 5 for these multiservice switches:

–Cisco MGX 8850 (PXM1E)

–Cisco MGX 8850 (PXM45)

–Cisco MGX 8950

–Cisco MGX 8830

•Cisco MGX Release 1.3, for these multiservice switches:

–Cisco MGX 8850 (PXM1)

–Cisco MGX 8230

–Cisco MGX 8250

•Cisco VXSM Release 5. The Voice Switch Service Module (VXSM) card is new for this release.

•Cisco WAN Manager Release 15. The Cisco WAN Manager (CWM) network management software is improved for this release. The previous release of CWM was 12. CWM Release 15 introduces a helpful new documentation feature: web-based online Help. To invoke online Help, press F1 on a PC, press the Help key on a UNIX workstation, or select Help from the main or popup menu.

Other components of multiservice WAN products, such as the Service Expansion Shelf (SES) and WAN switching software have no new features for the April 2004 release, therefore, their existing documentation was not updated.

Changes to this Document

Table 17 describes changes made to these release notes that caused the release notes to go from OL-4538-01 Rev. A0 to OL-4538-01 Rev. B0 on May 17, 2004. The revision was made because a new AXSM-XG image is available.

Table 17 Changes that Caused Revision B of this Document

Section	Change
"Resolved Anomalies in Release 5.0.00" section	Anomaly CSCee02920 was fixed and added to this list. The anomaly was removed from Table 16.
Table 3	The firmware for the AXSM-XG card changed to version axsmxg_005.000.000.202.

Related Documentation

This section describes the technical manuals and release notes that support the April 2004 release of Cisco Multiservice Switch products.

Technical Manual Order of Use

Use the technical manuals listed here in the following order:

---

Step 1 Refer to the documents that ship with your product. Observe all safety precautions.

•Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES)—This document familiarizes you with safety precautions for your product.

•Guide to Cisco Multiservice Switch and Media Gateway Documentation—This document explains how to find documentation for MGX, BPX, and SES multiservice switches and media gateways as well as CWM network management software. These documents are available only online.

•Installation Warning Card—This document provides precautions about installing your cards. It explains such subjects as removing the shipping tab and inserting cards properly into the correct slots.

Step 2 Refer to the release notes for your product.

Step 3 If your network uses the CWM network management system, upgrade CWM. (If you are going to install CWM for the first time, do so after Step 4.) Upgrade instructions are included in the following documents:

•Cisco WAN Manager Installation Guide, Release 15

•Cisco WAN Manager User's Guide, Release 15

Step 4 If your network contains MGX and SES products, refer to this manual for planning information:

•Cisco PNNI Network Planning Guide for MGX and SES Products

Step 5 Refer to these manuals for information about installing cards and cables in the MGX chassis:

•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 for installing cards and cables in these chassis.

•Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for installing cards and cables in the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.

Step 6 Refer to the manuals that help you configure your MGX switch and processor cards:

•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 for these chassis.

•Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.

Step 7 Refer to the manual that supports the additional cards you intend to install in your switch. For example:

•The services books can help you establish ATM, Frame Relay, or circuit emulation services on your switch.

•The VISM book can help you set up your switch as a voice gateway, and the RPM book can help you implement IP on the switch.

Step 8 Additional books, such as command reference guides and error message books, can help with the daily operation and maintenance of your switch.

---

---

Note Manual titles may be different for earlier software releases. The titles shown in Table 18 are for the April 2004 release.

---

Technical Manual Titles and Descriptions

Table 18 lists the technical manuals and release notes that support the April 2004 multiservice switch product releases. Books and release notes in Table 18 are listed in order of use and include information about which multiservice switch or media gateway the document supports.

The books for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches were not updated for the April 2004 release, therefore, some information about configuring and using the new MPSM-8-T1E1 card in these switches is included in the following books:

•Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

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

•Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

Information about how to install or upgrade to the MPSM-8-T1E1 card in Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches is in the Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00.

---

Note Refer to each product's release notes for the latest information on features, bug fixes, and more.

---

Terms

Two main types of ATM cards are used in MGX switches: AXSM and AUSM. AXSM stands for ATM Switching Service Module. AUSM stands for ATM UNI (User Network Interface) Service Module.

CWM stands for Cisco WAN Manager, our multiservice switch network management system.

Legacy service module refers to a previously introduced card. For this release, the term is used specifically for the CESM-8-T1E1, FRSM-8-T1E1, and AUSM-8-T1E1 cards, which can now be replaced by the new MPSM-8-T1E1 card.

MPSM stands for Multiprotocol Service Module.

RPM stands for Route Processor Module.

SES stands for Service Expansion Shelf.

VISM stands for Voice Interworking Service Module.

VXSM stands for Voice Switch Service Module.

Table 18 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases) 

Document Title and Part Number	BPX with SES Rel. 4	MGX 8230 Rel. 1.3	MGX 8250 Rel. 1.3	MGX 8850 (PXM1) Rel. 1.3	MGX 8830 Rel. 5	MGX 8850 (PXM1E) Rel. 5	MGX 8850 (PXM45) Rel. 5	MGX 8950 Rel. 5	MGX 8880 Rel. 5.
Overview and Safety Documents
Guide to Cisco Multiservice Switch and Media Gateway Documentation DOC-7814807=	x	x	x	x	x	x	x	x	x
Installation Warning Card DOC-7812348=	x	x	x	x	x	x	x	x	x
Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES) DOC-7814790=	—	x	x	x	x	x	x	x	x
Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 OL-5190-01	—	—	—	—	—	—	—	—	x
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 OL-4538-01	—	—	—	—	x	x	x	x
Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00 OL-4539-01	—	x	x	x	—	—	—	—	—
Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00 OL-4627-01	—	—	—	—	—	—	x	—	x
Release Notes for Cisco WAN Manager, Release 15.0.00 OL-4151-01	—	—	—	—	x	x	x	x	x
Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.2.10 OL-4544-01	—	x	x	x	x	x	x	—	x
Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 OL-4536-01	—	—	—	—	—	—	x	x	x
Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T5 for MGX Releases 1.3.00 and 5.0.00 OL-4535-1	—	x	x	x	x	x	x	x	x
Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.31 DOC-7812899=	—	x	—	—	—	—	—	—	—
Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.31 DOC-7811576=	—	—	x	—	—	—	—	—	—
Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.31 OL-1154-01	—	—	—	x	—	—	—	—	—
Hardware Installation Guides
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 OL-4545-01	—	—	—	—	x	x	x	x	x
Cisco Service Expansion Shelf Hardware Installation Guide, Release 11 DOC-786122=	x	—	—	—	—	—	—	—	—
Planning and Configuration Guides
Cisco PNNI Network Planning Guide for MGX and SES Products OL-3847-01	x	—	—	—	x	x	x	x	x
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 OL-4546-01	—	—	—	—	x	x	x	x	x
Cisco WAN Manager Installation Guide, Release 15 OL-4550-01	—	—	—	—	x	x	x	x	x
Cisco WAN Manager User's Guide, Release 15 OL-4552-01	—	—	—	—	x	x	x	x	x
Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.31 DOC-7811223=	—	—	—	x	—	—	—	—	—
Cisco SES PNNI Controller Software Configuration Guide, Release 31 DOC-7814258=	x	—	—	—	—	—	—	—	—
Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.31 DOC-7811215=	—	x	—	—	—	—	—	—	—
Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.31 DOC-7811217=	—	—	x	—	—	—	—	—	—
Service Module Configuration and Reference Guides
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 78-12510-02	—	x	x	x	—	—	—	—	—
Cisco Frame Relay Software Configuration Guide and Command Reference for the Cisco MGX 8850 (PXM45) FRSM-12-T3E3 Card, Release 31 DOC-7810327=	—	—	—	—	—	—	x	—	—
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 52 OL-4540-01	—	2	2	2	x	x	—	—	—
Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 52 OL-4541-01	—	2	2	2	x	x	x	—	—
Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 52 OL-0453-01	—	2	2	2	x	x	x	—	—
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 41 OL-5087-01	—	—	—	—	—	—	x	x	—
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4548-01	—	—	—	—	—	—	x	x	x
Cisco ATM and Frame Relay Services (MPSM-T3E3-155) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4554-01	—	—	—	—	x	x	x	—	—
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5 OL-4625-01	—	—	—	—	—	—	x	—	x
Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.21 OL-4359-01	—	x	x	x	x	x	x	—	x
Reference Guides
Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.31 DOC-78112113=	—	x	—	—	—	—	—	—	—
Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.31 DOC-7811211=	—	x	—	—	—	—	—	—	—
Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.31 DOC-7811212=	—	—	x	—	—	—	—	—	—
Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.31 DOC-7811216=	—	—	x	—	—	—	—	—	—
Cisco MGX 8800 Series Switch Command Reference, Release 1.1.31 DOC-7811210=	—	x	x	x	—	—	—	—	—
Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.31 DOC-7811240=	—	x	x	x	—	—	—	—	—
Cisco SES PNNI Controller Command Reference, Release 31 DOC-7814260=	x	—	—	—	—	—	—	—	—
Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 OL-4547-01	—	—	—	—	x	x	x	x	x
Cisco WAN Manager SNMP Service Agent, Release 15 OL-4551-01	—	—	—	—	x	x	x	x	x
Cisco WAN Manager Database Interface Guide, Release 15 OL-4587-01	—	—	—	—	x	x	x	x	x
Cisco MGX and Service Expansion Shelf Error Messages, Release 5 OL-4553-01	x	—	—	—	x	x	x	x	x

1 This document was not updated for the April 2004 release. 2 Some configuration and command information is included in this book for using the multiprotocol service module (MPSM-8-T1E1) in a Cisco MGX 8230, MGX 8250, or MGX 8850 (PXM1) switch.

---

Note For the April 2004 product release, there are no new features for the Service Expansion Shelf (SES) of the BPX switch and BPX WAN switching software. Therefore, documentation for these items was not updated. Table 18 lists the most recent technical manuals and release notes for these products.

---

Table 18 also lists the latest documentation available for the Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches. These switches use the PXM1 processor card. Although there are new features in MGX Release 1.3 for these switches, only the release notes were updated. And the following books contain some information about configuring the MPSM-8-T1E1 card for use in these switches:

•Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

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

•Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

Table 19 lists the documents that ship with product.

Table 20 contains alphabetized titles and descriptions of all the manuals and release notes listed in Table 18.

Table 19 Documents that Ship with Multiservice Switch Products 

Document Title	Description
Guide to Cisco Multiservice Switch and Media Gateway Documentation DOC-7814807=	Describes how to find the manuals and release notes that support multiservice switches and network management products. These documents are available only online. This guide ships with product.
Installation Warning Card DOC-7812348=	Contains precautions that you should take before you insert a card into a slot. This Warning Card ships with product.
Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES) DOC-7814790=	Provides regulatory compliance information, product warnings, and safety recommendations for all the Cisco MGX multiservice switches: MGX 8230, MGX 8250, MGX 8850 (PXM1), MGX 8850 (PXM45), MGX 8850 (PXM1E), MGX 8830 and MGX 8950. Also provides such information for the MGX 8880 Media Gateway. This book ships with product.

Table 20 Descriptions of Technical Manuals and Release Notes for Cisco Multiservice Switch Products 

Document Title	Description
Cisco ATM and Frame Relay Services (MPSM-T3E3-155) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4554-01	Provides software configuration procedures for provisioning ATM and Frame Relay connections on the new MPSM-T3E3-155 multiprotocol service module. Also describes all MPSM-T3E3-155 commands.
Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4540-01 A0	Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also describes all AUSM commands. Includes software configuration procedures for provisioning connections and managing the new MPSM-8-T1E1 card as an AUSM card replacement.
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4548-01	Explains how to configure the AXSM cards and provides a command reference that describes the AXSM commands in detail. The AXSM cards covered in this manual are the AXSM-XG, AXSM/A, AXSM/B, AXSM-E, and AXSM-32-T1E1-E.
Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-0453-01	Provides software configuration procedures for provisioning connections and managing the Circuit Emulation Service Module (CESM) cards supported in this release. Also describes all CESM commands. Includes software configuration procedures for provisioning connections and managing the new MPSM-8-T1E1 card as a CESM card replacement.
Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5 OL-4541-01	Provides software configuration procedures for provisioning connections and managing the Frame Relay Service Module (FRSM) cards supported in this release. Also describes all FRSM commands. Includes software configuration procedures for provisioning connections and managing the new MPSM-8-T1E1 card as an FRSM card replacement.
Cisco MGX 8230 Edge Concentrator Installation and Configuration, Release 1.1.3 DOC-7811215=	Provides installation instructions for the Cisco MGX 8230 edge concentrator.
Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3 DOC-7812899=	Describes the system components and function of the Cisco MGX 8250 edge concentrator.
Cisco MGX 8230 Multiservice Gateway Command Reference, Release 1.1.3 DOC-7811211=	Provides detailed information on the general command line interface commands.
Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3 DOC-78112113=	Provides error message descriptions and recovery procedures.
Cisco MGX 8250 Edge Concentrator Installation and Configuration, Release 1.1.3 DOC-7811217=	Provides installation instructions for the Cisco MGX 8250 edge concentrator.
Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3 DOC-7811576=	Describes the system components and function of the Cisco MGX 8250 edge concentrator.
Cisco MGX 8250 Multiservice Gateway Command Reference, Release 1.1.3 DOC-7811212=	Provides detailed information on the general command line interface commands.
Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3 DOC-7811216=	Provides error message descriptions and recovery procedures.
Cisco MGX 8800 Series Switch Command Reference, Release 1.1.3 DOC-7811210=	Provides detailed information on the general command line for the Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 edge concentrators.
Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3 DOC-7811240=	Provides error message descriptions and recovery procedures for Cisco MGX 8850 (PXM1), Cisco MGX 8250, and Cisco MGX 8230 edge concentrators.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 OL-4545-01	Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. Also describes how to install the MGX 8880 Media Gateway. This document explains what each switch does and covers site preparation, grounding, safety, card installation, and cabling. The Cisco MGX 8850 switch uses either a PXM45 or a PXM1E controller card and provides support for both serial bus-based and cell bus-based service modules. The Cisco MGX 8830 switch uses a PXM1E controller card and supports cell bus-based service modules. The Cisco MGX 8950 supports only serial bus-based service modules. The Cisco MGX 8880 uses a PXM45/C controller card, and supports only serial bus-based service modules. This hardware installation guide replaces all previous hardware guides for these switches.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 OL-4546-01	Describes how to configure the Cisco MGX 8880 Media Gateway. Also describes how to configure Cisco MGX 8850 (PXM1E), Cisco MGX 8850 (PXM45), and Cisco MGX 8830 switches to operate as ATM edge switches and the Cisco MGX 8950 switch to operate as a core switch. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 OL-4547-01	Describes the PXM commands that are available in the CLI of the Cisco MGX 8850 (PXM45), Cisco MGX 8850 (PXM1E), Cisco MGX 8950, and Cisco MGX 8830 switches. Also describes the PXM commands that are available in the CLI of the Cisco MGX 8880 Media Gateway.
Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 DOC-7811223=	Provides installation instructions for the Cisco MGX 8850 (PXM1) edge concentrator.
Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3 OL-1154-01	Describes the system components and function of the Cisco MGX 8850 (PXM1) edge concentrator.
Cisco MGX and Service Expansion Shelf Error Messages, Release 5 OL-4553-01	Provides error message descriptions and recovery procedures.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 OL-5087-01	Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 (PXM45) and Cisco MGX 8950 switch. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.
Cisco MGX Route Processor Module (RPM-PR) Installation and Configuration Guide, Release 2.1 78-12510-02	Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B or RPM-PR) in the Cisco MGX 8850 (PXM1), the Cisco MGX 8250, and the Cisco MGX 8230 edge concentrators. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.
Cisco PNNI Network Planning Guide for MGX and SES Products OL-3847-01	Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, or Cisco BPX 8600 switches or the MGX 8880 Media Gateway. When connected to a PNNI network, each Cisco BPX 8600 Series switch requires an SES for PNNI route processing.
Cisco Service Expansion Shelf Hardware Installation Guide, Release 1 DOC-786122=	Provides instructions for installing and maintaining an SES controller.
Cisco SES PNNI Controller Command Reference, Release 3 DOC-7814260=	Describes the commands used to configure and operate the SES PNNI controller.
Cisco SES PNNI Controller Software Configuration Guide, Release 3 DOC-7814258=	Describes how to configure, operate, and maintain the SES PNNI controller.
Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.2 OL-4359-01	Describes how to install and configure the Voice Interworking Service Module (VISM) in the Cisco MGX 8830, Cisco MGX 8850 (PXM45), and Cisco MGX 8850 (PXM1E) multiservice switches. Provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.
Cisco Voice Switch Services (VXSM) Configuration and Command Reference Guide for MGX Switches, Release 5 OL-4625-01	Describes the features and functions of the new Voice Switch Service Module (VXSM) in the Cisco MGX 8880 Media Gateway and in the Cisco MGX 8850 (PXM45 and PXM1E) multiservice switches. Also provides configuration procedures, troubleshooting procedures, and Cisco CLI configuration information.
Cisco WAN Manager Database Interface Guide, Release 15 OL-4587-01	Provides information about accessing the CWM Informix database that is used to store information about the network elements.
Cisco WAN Manager Installation Guide, Release 15 OL-4550-01	Provides procedures for installing Release 5 of the CWM network management system.
Cisco WAN Manager SNMP Service Agent, Release 15 OL-4551-01	Provides information about the CWM Simple Network Management Protocol service agent, an optional adjunct to CWM that is used for managing Cisco WAN switches through SNMP.
Cisco WAN Manager User's Guide, Release 15 OL-4552-01	Describes how to use the CWM Release 15 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management. Note The CWM interface now has built-in documentation support in the form of online Help. On a PC, press F1 to access Help; on a UNIX workstation, press the Help key. Alternatively, on either system you can select Help from the main or popup menu.
Cisco Frame Relay Software Configuration Guide and Command Reference for the Cisco MGX 8850 (PXM45) FRSM-12-T3E3 Card, Release 3 DOC-7810327=	Describes how to use the high-speed Frame Relay (FRSM-12-T3E3) commands that are available in the CLI of the Cisco MGX 8850 (PXM45) switch.
Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00 OL-4539-01	Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies.
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00 OL-4538-01	Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies.
Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00 OL-5190-01	Provides new feature and compatibility information, as well as information about known and resolved anomalies.
Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T5 for MGX Releases 1.3.00 and 5.0.00 OL-4535-01	Provides upgrade and compatibility information, as well as information about known and resolved anomalies.
Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 OL-4536-01	Provides upgrade and compatibility information, as well as information about known and resolved anomalies.
Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.2.10 OL-4544-01	Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies.
Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00 OL-4627-01	Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies.
Release Notes for Cisco WAN Manager, Release 15.0.00 OL-4151-01	Provides new feature, upgrade, and compatibility information, as well as information about known and resolved anomalies.

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/univercd/home/home.htm

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

Documentation DVD

Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.

Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Cisco Marketplace:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments 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 can perform these tasks:

•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 and notices for Cisco products is available at this URL:

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

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from 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 might have identified a vulnerability in a Cisco product, contact PSIRT:

•Emergencies — security-alert@cisco.com

•Nonemergencies — psirt@cisco.com

---

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:

http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on

---

In an emergency, you can also reach PSIRT by telephone:

•1 877 228-7302

•1 408 525-6532

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support 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, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support 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 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 TAC 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 TAC 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)—Your 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 operation 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 your network is impaired, but 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.

•Cisco Marketplace provides a variety of Cisco books, reference guides, 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

•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

•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 21 lists acronyms that have been referenced in these release notes.

Table 21 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
MLPPP/LFI	Multi-Link PPP
MTI	Multicast Tunnel Interface
NBSM	Narrow band service module (traditional name for what we are calling cell bus service modules in Release 4 and higher)
P2MP	Point-to-Multipoint
PE	Provider Edge
PER	Product Enhancement Request
PNNI	Private Network-to-Network Interface
POS	Packet over SONET
POST	Power On Self-Test
PPP	Point-to-Point Protocol
PXM	Processor Switch Module
RPM	Route Processor Module
SFP	Small Form Factor Pluggable Unit
SONET	Synchronous Optical NETwork
SPVC	Soft permanent virtual connection
SRM	Service Resource Module
SVC	Switched virtual circuit
VPN	Virtual Private Network
VRF	VPN Routing / Forwarding
XF	Express Forwarding

This document is to be used in conjunction with the documents listed in the "Changes to this Document" section.

Copyright © 2005 Cisco Systems, Inc. All rights reserved.