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 4.0.11

Contents

About Release 4.0.11

Type of Release

Locating Software Updates

New Features and Enhancements in Release 4.0.11

Frame Discard Feature

Features and Enhancements in Previous Release 4.0.10

LMI AutoSense

addport

xcnfport

cnfport

dspport

Resource Monitoring

Platforms

Add Channel Loopback on AXSM-E (PER 3854)

Platforms

Service Module Core Hot Dump

Platforms

Active PXM Freeze Detection and Recovery (PER 7869)

Platforms

Improved SCM Polling Diagnostics on Active and StandBy PXM

Platforms

Cell Bus Service Module on PXM-45 (Expanded from MGX 4.0.00 Release)

Platform

AXSM/B as Feeder Uplink on MGX 8950

Platforms

Features and Enhancements in Previous Release 4.0.00

Closed User Groups

Platforms

References

Preferred Routes for PNNI Multipeer Group Networks

Platforms

References

Point-to-Multipoint SVC/SPVC Support

Platforms

References

Increased Number of Signaling Interfaces

Platforms

PXM1E-Related Hardware (the PXM1E-8-155 card)

Redundancy Support

Automatic Protection Switching Support

Modular Transceiver Support in the New 8-port OC3/STM1 Back Card

UNI connection support in PXM1E-16-T1E1

ATM Routing in PXM1E

Connection Management

Cell Bus Service Module Support

Virtual Trunks Support in PXM1E

Virtual UNI Support in PXM1E

Feeder Trunk support in PXM1E

PXM1E Diagnostics

AXSM-E as Upstream to Feeder Nodes

Platform

Cell Bus Service Modules on PXM45

Platform

AXSM-32-T1E1-E UNI with IMA

Platforms

PXM45/C

Platforms

AXSM-1-9953-XG

Platforms

AXSM-4-2488-XG

Platforms

Enhancements

Service Class Template (SCT) File Information

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-4-2488-XG

FRSM-12-T3E3

System Requirements

Software/Firmware Certified Releases

MGX and RPM Software Version Compatibility Matrix

Hardware Supported

New Hardware in Release 4.0.11

New Hardware in Release 4.0.10

New Hardware in Previous Release 4.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

Limitations, Restrictions, and Notes for 4.0.11

Limitations

Upgrading to 4.0.10

Higher Level Logical Link Limits

CLI Upgrade

Preferred Route

PXM45/C

192 Signaling Interfaces

Closed User Group (CUG)

Point to Multipoint SVC/SPVC Support

AXSM-32-T1E1-E/PXM1E-16-T1E1

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

AXSM-E as Upstream to Feeder Nodes

IGX Feeder

Policing Accuracy for PXM1E

Maximum Threshold Accuracy for PXM45 and PXM1E

PXM1E-Based Switches

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

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

Preferred Route

Persistent Topology

Manual Clocking

AXSM Cards

AXSM-XG Hardware Limitation

ATM Multicast

RPM-PR and RPM-XF Limitations

Restrictions

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

AXSM Model B Restrictions

Formatting Disks

Saving Configurations

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

Limitations and Restrictions for 2.1.x

General Limitations, Restrictions, and Notes

Limitations for rteopt via parallel links

Important Notes

APS Management Information

Preparing for Intercard APS

Managing Intercard APS Lines

Troubleshooting APS Lines

Installation and Upgrade Procedures

Upgrade Information

Maintenance Information

Upgrade Limitations

Frame Discard

Documentation

Changes to this Document

Notes

Related Documentation

Cisco WAN Manager Release 12

Cisco MGX 8850 (PXM45) Multiservice Switch Release 4

Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4

Cisco MGX 8950 Multiservice Service Release 4

SES PNNI Release 4

Cisco MGX 8830 Multiservice Switch Release 4

Cisco WAN Switching Software Release 9.4

MGX 8850 (PXM1) Edge Concentrator Release 1.2.20

MGX 8250 Edge Concentrator Release 1.2.20

MGX 8230 Edge Concentrator Release 1.2.20

How to Find Multiservice Switch Customer Documents Online

If the Part Number is Known

If the Part Number is Not Known

Ordering Documentation

Documentation on the World Wide Web

Documentation CD-ROM

Documentation Feedback

Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Caveats

MGX 8850, MGX 8830, and MGX 8950 4.0.11 Anomalies

Known Anomalies in Release 4.0.11

Anomalies Resolved in Release 4.0.11

Anomaly Status Change from Previous Release 4.0.10

MGX 8850, MGX 8830, and MGX 8950 4.0.10 Anomalies

Known Anomalies in Release 4.0.10

Anomalies Resolved in Release 4.0.10

Anomaly Status Change from Previous Release 4.0.00

Known Route Processor Module or MPLS Anomalies

MGX-RPM-XF-512 Anomalies

Acronyms

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

---

Contents

About Release 4.0.11

These release notes describes the system requirements, new features, and limitations that apply to Release 4.0.11 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 "Related Documentation" section.

---

Note Release notes for MGX 8950, Release 4.0.11, are combined with this release notes.

---

Type of Release

Release 4.0.11 is a software 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 4.0.11 software:

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

New Features and Enhancements in Release 4.0.11

None.

Frame Discard Feature

New developments have occurred in the CLI for the Frame Discard feature in connection provisioning. Starting with releases 3.0.23 and 4.0.10, two types of frame discard became available. For a detailed explanation, see the addcon or cnfcon description in either the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference (Release 3 or 4) or the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches (Release 3 or 4). Also see the Note in the Installation and Upgrade section of these release notes.

Features and Enhancements in Previous Release 4.0.10

The new features in Release 4.0.10 are listed inTable 1.

:

Table 1 New Features in Release 4.0.10

New Release 4.0.10 Feature	MGX 8850 PXM45(A)	MGX 8850 PXM45/B	MGX 8850 PXM45/C	MGX 8950	MGX 8850 (PXM1E)	MGX 8830
LMI AutoSense	YES	YES	YES	NA	YES	YES
Resource Monitoring	YES	YES	YES	YES	YES	YES
Add Channel Loopback on AXSM-E	YES	YES	YES	NA	NA	NA
Service Module Hot Core Dump	YES(see Note 2)	YES(see Note 2)	YES(see Note 2)	YES	NO	NO
Active PXM Freeze Detection and Recovery	YES	YES	YES	YES	NO	NO
Improved SCM Polling Diagnostics on Active and Standby PXM	YES	YES	YES	YES	YES	YES
MGX-FRSM-HS2/B	NA	YES	YES	NO	YES	YES
MGX-FRSM-2T3E3	NO	YES	YES	NO	YES	YES
AXSM/B Feeder Support	YES	YES	YES	YES(see Note 1)	NA	NA

---

Note 1. Already supported on MGX 8850 and new on MGX 8950.

---

---

Note 2. Except for Cell Bus Service Module

---

LMI AutoSense

The LMI AutoSense feature on the Frame Cards on MGX switches enables a frame relay port to detect the LMI type supported by the frame relay CPE (customer premise equipment). This autosensing feature avoids the need to configure the LMI type on each frame relay port.on the FRSM-8T1/E1 and FRSM-VHS (2CT3, 2T3, 2E3, 2HS2B) cards on PXM1/(PXM45A/B/C)/PXM1E platforms.

The LMI AutoSense feature is supported for Frame Relay and FUNI port types. It is not applicable for Frame Forwarding port types. The detected LMI types will be of the following UNI types:

•AnnexD-UNI

•AnnexA-UNI

•StrataLMI

The LMI AutoSense feature is not supported on NNI interfaces.

The LMI AutoSense feature is configurable at a per port level.

A new MIB variable portLmiSigConfMethod has been added to the existing frPortCnfSigLMIGrpTable MIB table.

The addport, cnfport, xcnfport and dspport CLI commands have been modified to configure/display the new portLmiSigConfMethod MIB variable.

addport

One more parameter lmi_autosense will be added to the addport CLI, which can be optionally specified by the user while adding the port. By default the value will be set to Manual(1).

If the user wants to configure the port for LMI AutoSense, the user needs to set the lmi_autosense parameter value to AutoSense(2) while adding the port using addport.

The addport command syntax for the cards will thus be modified to as shown below

FRSM-8P and FRSM-2CT3.

Syntax:

addport "port_num line_num ds0_speed begin_slot num_slot port_type [lmi_autosense]"

where lmi_autosense can be configured for either mode Manual(1) or AutoSense(2)

FRSM-2T3, FRSM-2E3, FRSM-HS2B.

Syntax:

addport "port_num line_num port_type [lmi_autosense]"

xcnfport

One more parameter "-lmias" has been added to the xcnfport CLI, which can be specified while either adding the port or modifying the port using xcnfport. By default the value is set to Manual(1).

To configure the port for LMI autosense set the "-lmias" parameter value to AutoSense(2) while adding/modifying the port using xcnfport. At the same time, set the port signalling protocol type to noSignalling using the "-sig" option.

The xcnfport command syntax for the cards has been modified as shown below.

Syntax:

xcnfport "-pt <PortNum> -ln <PortLineNum> -en <PortEnable> -rat <PortEqueueServiceRatio> -flag <PortFlagsBetweenFrames> -asy <AsynchMsg> -t391 <T391Timer> -t392 <T392Timer> -n391 <N391Counter> -n392 <N392Counter> -n393 <N393Counter> -enhancedLmi <enhancedLmi> -pta <portAdmin> -svcen <portSvcStatus> -svcuse <portSvcInUse> -pbe <portBertEnable> -m32eqth <EgressQueueThreshold> -lmias <lmi autosense>"

where -lmias <lmi_autosense> can be set to either 1 for Manual or 2 for Autosense.

cnfport

One more parameter lmi_autosense has been added to the cnfport CLI, which can be specified while modifying the port. By default the value is set to Manual(1).

To configure the port for LMI autosense, set the lmi_autosense parameter value to AutoSense(2) and lmiSig to noSignalling while using cnfport.

The cnfport command syntax for the cards has been modified to as shown below:

Syntax:

cnfport "portNum lmiSig asyn ELMI T391 T392 N391 N392 N393 [lmi_autosense]"

where [lmi_autosense] can be set to either 1 for Manual or 2 for AutoSense.

dspport

The existing CLI dspport will be enhanced to display the value of the new MIB variable. The display of this new variable portLmiSigConfMethod will be added between the display of PortSpeed and SignallingProtocolType.

Example:

node.1.4.VHSHS2.a > dspport 1

    SlotNum:                      		4

    PortLineNum:                  		1

    PortNum:                      		1

    PortRowStatus:                		Add

    PortDs0Speed:                 		notUsed

    PortDs0ConfigBitMap(1stDS0):  		0xffffff(1)

    PortEqueueServiceRatio:       		n/a

    PortFlagsBetweenFrames:       		0

    PortSpeed:                    		51840 kbps

    portLmiSigConfMethod:         				Manual

    SignallingProtocolType:       		NoSignalling

    AsynchronousMsgs:             		UPD_UFS disabled

    T391LineIntegrityTimer:       		10 sec

    T392PollingVerificationTimer: 		15 sec

    N391FullStatusPollingCounter: 		6

    N392ErrorThreshold:           		3

    N393MonitoredEventCount:      		4

    EnhancedLmi:                  		Off

    PortState:                    		FailedDuetoLineFailure

    PortSignallingState:          		No Signalling Failure

    CLLMEnableStatus:             		Disable

    CLLMxmtStatusTimer:           		40 ms

    portType:                     		frameRelay

    portEnhancedSIW:              		Disable

    PortIngrPercentUtil:          		0

    PortEgrPercentUtil:           		0

    PortOversubscribed:           		False

    PortSvcStatus:                		Disable

    PortSvcInUse:                 		Not In-Use

    PortSvcShareLcn:              		Card-based

    PortSvcLcnLow:                		0

    PortSvcLcnHigh:               		0

    PortSvcDlciLow:               		0

    PortSvcDlciHigh:              		0

    PortNumNextAvailable:         		2

Resource Monitoring

The feature Resource Monitoring periodically checks the switch resources and takes appropriate actions when either there is a resource shortage or recovery happens. The resources monitored are:

•Memory (all SSI partitions and VxWorks(TM) partition)

•Hard Disk space

•IPC buffers

•CPU

•SSI Sync Timers

•SSI File Descriptors

•VxWorks file descriptors

•System up time

The action includes:

•Alarm

•Trap

•Log

The following are new CLIs for the feature:

•cnfrmrsrc: Configure resource monitoring behavior

•dsprmrsrc: display particular resource information in detail

•dsprmrsrcs: display all the resources in summary

•dsprmalms: display resource related alarms

The following are modification on existing CLI:

•dspcdalm: add resource monitoring category

Platforms

The feature is supported on:

•MGX 8850 (PXM1E, PXM45, AXSM, AXSM-E, FRSM12)

•MGX 8950 (PXM45, AXSM/B, AXSM-XG)

•MGX8830 (PXM1E)

Add Channel Loopback on AXSM-E (PER 3854)

Currently, the addchanloop CLI command on the AXSM-E card offers the local and remote loop option. This would make it consistent with the addchanloop command on the AXSM/B Card.

The local (egress) loop option of addchanloop has been added on the AXSM-E. Special handling is involved where the SABRE chip handles the egress loopback instead of the ATLAS chip.

dspchancnt is supported on the loopback connection.

Limitations:

• OAM and RM cells cannot be looped back, only data cells can be looped.

• All OAM functions will not work on the loopback connections.

• The QE is disabled in the egress direction when the sabre is looped back, so there will be discards at the egress QE; the data cells are actually being looped back through SABRE.

• During the loopback, special loopback LCNs are used. The normal connection LCN will be disabled at that time.

• There are 8 loopback LCNs per card, so only 8 connections can be looped back at a time.This includes ingress and egress loopbacks.

• The users cannot enable remote and local channel loopback at the same time on the same channel.

Platforms

The feature is supported on:

•MGX 8850(AXSM-E)

Service Module Core Hot Dump

In order to ease debugging of either memory leak or memory corruption on service module (SM) cards, core hot dump feature provides the functionality of initiating core hot dump through CLI command of "core hot-dump <file.zip>" on SM. The feature is available on the following service modules:

–AXSM

–AXSM-E

– AXSM-XG

–FRSM12

CBSM (Cell Bus Service Module) is not supported by this feature. Only one SM slot can execute core hot dump at one time. The core hot dump will not cause SM card to reset. The feature can be executed on active and standby SM cards. Each SM slot performing core hot dump will have a core hot dump zip file saved on the active PXM hard disk "C:/" directory. The user can ftp the zipped core file to a their workstation and use a GDB debugger to analyze the core file to analyze the problems. At the PXM CLI prompt, the user can check SM core hot dump status by using the CLI command "core dump-status". The CLI shows slots that are in the process of core hot dump.

Platforms

The feature is supported on:

•MGX 8850 (AXSM/B, AXSM-E, FRSM12)

•MGX8950 (AXSM/B, AXSM-XG)

Active PXM Freeze Detection and Recovery (PER 7869)

The standby PXM monitors the SCM polls coming from the Active PXM. If the standby PXM detects a missing Poll, it waits for configurable maximum consecutive missing polls (Default 13 polls: 19.5 Seconds) and then takes over the mastership and resets the Active PXM.

To ensure the Standby PXM does not reset the Active in case of local SCM path failure, the Active PXM detects the missing Poll responses. It resets the standby PXM (or any Service Module) in configurable consecutive missing poll responses(10 Polls: 15 Seconds recommended).

This feature is not enabled by default on PXM cards. The feature has to be enabled on the Active PXM and the values for MaximumPoll counts from Active and Standby must be configured also.The default value for the standby PXM maximum missing poll before it declares active frozen is 13 counts(19.5 sec) and the default value for the Active PXM maximum poll retries is 9 polls(+1 failure before retries).

Platforms

The feature is supported on:

•MGX 8850(PXM45)

•MGX 8950

Improved SCM Polling Diagnostics on Active and StandBy PXM

The feature is an enhancement in SCM for improving the debugging ability for SCM Poll / RPM heartbeat failures. SCM has a mechanism of monitoring card's health by sending Poll messages (Additionally Heartbeat in RPM). SCM declares a card dead after a certain number of responses are not received and reports the error to Shelf Manager which in turn will reset the Service Module. Currently, there is no debugging information either logged or stored once the card resets. The feature has the capability of storing more information in case of card failure for easier debugging. The possible cause of an SCM Poll/Heartbeat failure could be Failure in the communication path, Failure of the channel on which the Poll/Heartbeat is sent, and Failure on the Service Module. A new mechanism introduced in SCM collects the relevant data for improving failure analysis. A minimum number of failure of Poll/Heartbeat threshold (50% of Maximum Poll Retry limit) would be used to trigger the collection of data from SAR, QE and CBC on the PXM side.

Platforms

The feature is supported on:

•MGX8850(PXM45, PXM1E)

•MGX8950

•MGX8830

Cell Bus Service Module on PXM-45 (Expanded from MGX 4.0.00 Release)

MGX-FRSM-2T3E3 and MGX-FRSM-HS2/B have been added to the list of Cell Bus Service Modules supported on the PXM45/B and PXM45/C.

Platform

The feature is supported on:

•MGX 8850 (PXM45/B, PXM45/C)

AXSM/B as Feeder Uplink on MGX 8950

Previously supported only on the MGX 8850-PXM45, the feeder upstream capability will now be supported on the MGX 8950 as well. This feature enables PXM-1 feeder nodes to be directly connected to the AXSM/B cards on MGX 8950 nodes.

Platforms

The feature is supported on:

•MGX 8950

Features and Enhancements in Previous Release 4.0.00

---

Note Cell bus service modules (CBSMs) were formerly called narrow band service modules (NBSMs). As the MGX product line has grown, the narrow band distinction is no longer appropriate. CBSMs use the MGX cell bus for customer traffic instead of the serial bus used by cards such as AXSM and FRSM-12-T3E3.

Refer to the "Acronyms" section for definitions of acronyms used in these release notes.

---

Release 4.0.00 contains the following new features:

Table 2 lists which switch supports which new feature.

Table 2 MGX Release 4.0.00 Feature Support by Switch 

New Release 4.0.00 Feature	MGX 8850 PXM45(A)	MGX 8850 PXM45/B	MGX 8850 PXM45/C	MGX 8950	MGX 8850 (PXM1E)	MGX 8830
Closed User Groups (CUG)	YES*	YES	YES	YES	YES	YES
Preferred routes for PNNI Multipeer Group Networks	YES	YES	YES	YES	YES	YES
Point to Multipoint SVC/SPVC support (P2MP) - Guru	NO	YES	YES	YES	YES	YES
Increased number of Signaling Interfaces	NO	YES	YES	YES	N/A	N/A
Virtual trunks support in PXM1E	NO	NO	NO	NO	YES	YES
Virtual UNI support in PXM1E	N/A	N/A	N/A	NO	YES	YES
PXM1E as Upstream to Feeder Nodes	N/A	N/A	N/A	NO	YES	YES
AXSM-E Upstream to Feeder Nodes	NO	YES	YES	NO	NO	NO
Cell Bus on PXM451	NO	YES	YES	NO	NO	NO
Additional Narrow Band on PXM1E	N/A	N/A	N/A	NO	YES	YES
AXSM-32-T1E1-E UNI with IMA	NO	YES	YES	NO	N/A	N/A
PXM1E-16-T1E1 UNI with IMA	N/A	N/A	N/A	NO	YES	YES
PXM1E-8-155	N/A	N/A	N/A	N/A	YES	YES
PXM45/C	NO	NO	YES	YES	NO	NO
AXSM-1-9953-XG	NO	NO	NO	YES	NO	NO
AXSM-4-2488-XG	NO	NO	NO	YES	NO	NO

1 Please refer to the CBSM matrix (Table 2) for details. 1 * Closed User Groups is support on PXM45(A) in Release 4.0.10.

Closed User Groups

The Closed User Groups (CUG) supplementary service enables network users to form groups, to and from which access is restricted. A network user may be associated with one CUG, multiple CUGs, or no CUG. Members of a specific CUG can communicate typically among themselves, but in general not with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG (Outgoing Calls Blocked or Incoming Calls Blocked). In addition, a network user can be further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user (Outgoing Access or Incoming Access.).

The feature is based on the ITU-T Q.2955.1 recommendation.

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

References

ITU-T Q.2955.1

Preferred Routes for PNNI Multipeer Group Networks

Preferred routing of connections provides the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route is one which will follow the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route is one which will follow only the configured path; if the configured path is not available, the connection will remain unrouted.

Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

References

PNNI 1.1

Point-to-Multipoint SVC/SPVC Support

The SVC/SPVC point-to-multipoint (P2MP) feature offers the ability for one root SVC/SPVC connection to establish a simple tree topology to one or more leaf connections. The data traffic is uni-directional from root multicast to all leaves, i.e., what is sent from the root data channel is received by all leaves. From the root, leaves can be added to the connection using SETUP/ADD_PARTY signaling messages. Point-to-multipoint is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.0 specs. The implementation is compliant with in Q2971.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•AXSM/B on MGX 8950

•AXSM/B on MGX 8850 (PXM45)

---

Note AXSM/B support is limited due to the capability of the hardware. P2MP connections and throughput are limited.

---

References

UNI 3.0, UNI3.1, UNI4.0, Q2971

Increased Number of Signaling Interfaces

Support for up to 192 PNNI routing/signaling interfaces on MGX 8850 (PXM45/B and PXM45/C). Prior to this release, the platform supports only 99 signaling interfaces. The features enables increased signaling interfaces for interconnecting with other switches or DSLAMs.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

PXM1E-Related Hardware (the PXM1E-8-155 card)

•8-port OC3/STM1and MCC-8-155

•Continues to support existing PXM1 features

•PXM1E 8-port OC3/STM1 will require the UI-S3/B back card

•PXM1E-8-155, new 8-port OC3/STM1 back card with the SFP and MCC-8-155 support.

Redundancy Support

The PXM1E PNNI Controller offers redundancy, offer hitless operation, and Y-Redundancy (1:1) will be supported in PXM1E for the 155 interface.

Service Modules will have 1:N redundancy and 1:1 redundancy as supported by the individual service modules

Automatic Protection Switching Support

Automatic Protection Switching (APS) 1:1 and1+1 for both the Bellcore GR-253 and ITU-T G.783 Annex-A and Annex-B standards will be supported for the OC3 and STM1 interfaces. The MGX-8850-APS-CON plane is required for APS functionality.

Modular Transceiver Support in the New 8-port OC3/STM1 Back Card

The PXM1E will support a single universal back card capable of supporting single-mode and multi-mode fiber connectors for the different reaches in OC3 and STM1.

External field-replaceable transceivers for SMF-IR, SMF-LR and MMF, purchased by the customer, will be supported.

UNI connection support in PXM1E-16-T1E1

In a previous software release (3.0.10), the PXM1E-16-T1E1 card provided support for IMA trunking. In the MGX 4.0.00 release, the same card will support both native ATM UNI and IMA UNI endpoints. Sixteen T1/E1 ports can be mixed and matched for either native UNI or NNI ports and IMA UNI or NNI ports.

ATM Routing in PXM1E

The PXM1E-based switches support the ATM Forum standard PNNI routing/signaling based on the same baseline used for MGX 8850 (PXM45) and BPX/SES systems. It can be a peer to the PXM45-based switches in the single peer group and participate in multipeer groups.

Connection Management

Supports different types of connections—SVC, SVP, S-PVC, and S-PVP. UNI 3.X/4.0 signaling and ILMI are used to setup SVCs and SVPs.

PXM1E will support 13,500 local switching connections and 27,000 routed connections.

Cell Bus Service Module Support

A cell bus service module is an MGX service module that uses the MGX cell bus to transport customer traffic between that service module and other services modules or PXM uplinks. Traditionally, the CBSMs were called narrow band service modules (NBSMs).

For a summary of service modules supported in MGX 8830 and MGX 8850 (PXM1E), please refer to Table 2.

Virtual Trunks Support in PXM1E

Virtual trunks will be supported in the PXM1E ports. A maximum of 31 (physical and virtual) trunks can be supported in a PXM1E card. The feature will be supported in 4-port OC3/STM1, 8-port T3/E3, 8-port OC3/STM1, 16- port T1/E1 and the combo PXM1E cards. SVC, SPVC and SPVP connections can be routed over the virtual trunks.Virtual trunks can originate and terminate between PXM1E, AXSM/A, AXSM/B, AXSM-XG and AXSM-E cards.

Virtual UNI Support in PXM1E

A new port type called Virtual UNI (VUNI) and Enhanced Virtual UNI(EVUNI) is defined in addition to the already defined port types UNI, NNI, VNNI (Virtual Trunk). This feature benefits both the MPLS and PNNI control plane.

Feeder Trunk support in PXM1E

PXM1E ports can accept feeder trunks in any port. IGX 8400, MGX 8230, MGX 8250 and MGX 8850 (PXM1) can be added as feeders to MGX 8830 and MGX 8850 (PXM1E).

PXM1E Diagnostics

Both HMM and online diagnostics report alarms in the Hardware Alarm category under the card alarms.

•HMM reports alarms for all devices when error thresholds are crossed. Further information can be obtained via the CLI dspdeverr <device>. This CLI will have to be issued for each device to ensure that all relevant errors have been observed. The alarm raised by the specific instance of the device (for example, QE1210 - 0 or 1) will also be available in the dspdeverr CLI.

•The CLI dspdiagerr online indicates whether there is error reported by online diagnostics. Further information regarding the error can be obtained from the event logs via a filter using CLI dsplog -mod PXMD.

POST test results printed to the console immediately after execution may display failures. These may be due to tests being attempted for devices not present on the particular PXM1E-board (such as the second ATM policing device on the PXM1E-4-155). The tests are based purely on device offsets and can display spurious results. To confirm/rule-out real and relevant tests, please use the following examples:

Example 1 PXM1E-4-155: ATM policing device 2 and framers 2 and 4 do not exist: Following shows all relevant test cases passed. Although framers 2 and 4 show passed below, those two cases must be ignored.

Power On Self Test Results

Test Name Result Description

BRAM Checksum PASS

QE Ram PASS

CBC Ram PASS

Ethernet Reg PASS

PCI-IDE Reg PASS

Clock Mux PASS

Framer 1 Access PASS

Framer 2 Access PASS

Framer 3 Access PASS

Framer 4 Access PASS

ATLAS 1 Ram PASS

ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched

Hard Disk Access PASS

Example 2 PXM1E-8-T3E3: ATM policing device 2 and framers 3 and 4 do not exist: Following shows all relevant test cases passed.

Power On Self Test Results

Test Name Result Description

BRAM Checksum PASS

QE Ram PASS

CBC Ram PASS

Ethernet Reg PASS

PCI-IDE Reg PASS

Clock Mux PASS

Framer 1 Access PASS

Framer 2 Access PASS

Framer 3 Access FAIL Framer 3 Access 1 Fail

Framer 4 Access FAIL Framer 4 Access 1 Fail

ATLAS 1 Ram PASS

ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched

Hard Disk Access PASS

Example 3 PXM1E-T3E3-155: Following shows all relevant test cases passed.

Power On Self Test Results

Test Name Result Description

BRAM Checksum PASS

QE Ram PASS

CBC Ram PASS

Ethernet Reg PASS

PCI-IDE Reg PASS

Clock Mux PASS

Framer 1 Access PASS

Framer 2 Access PASS

Framer 3 Access PASS

Framer 4 Access PASS

ATLAS 1 Ram PASS

ATLAS 2 Ram PASS

Hard Disk Access PASS

Example 4 PXM1E-8-155: Following shows all relevant test cases passed. For the 8OC3, the ethernet controller test is not done, since the controller is part of the system controller which is not tested in this release.

Power On Self Test Results

Test Name Result Description

BRAM Checksum PASS

QE Ram PASS

CBC Ram PASS

Ethernet Reg NOT_DONE Ethernet Controller Test Not Required.

PCI-IDE Reg PASS

Clock Mux PASS

Framer 1 Access PASS

Framer 2 Access PASS

Framer 3 Access PASS

Framer 4 Access PASS

ATLAS 1 Ram PASS

ATLAS 2 Ram PASS

Hard Disk Access PASS

Example 5 PXM1E-16-T1E1: ATM policing device 2 and framers 1,2,3 and 4 do not exist: Following shows all relevant test cases passed.

Power On Self Test Results

Test Name Result Description

BRAM Checksum PASS

QE Ram PASS

CBC Ram PASS

Ethernet Reg PASS

PCI-IDE Reg PASS

Clock Mux PASS

Framer 1 Access FAIL Framer 1 Access 1 Fail

Framer 2 Access FAIL Framer 2 Access 1 Fail

Framer 3 Access FAIL Framer 3 Access 1 Fail

Framer 4 Access FAIL Framer 4 Access 1 Fail

ATLAS 1 Ram PASS

ATLAS 2 Ram FAIL Ingress SRAM: Pattern Not Matched

Hard Disk Access PASS

AXSM-E as Upstream to Feeder Nodes

Previously supported only with AXSM and AXSM/B cards, the feeder upstream capability will now be supported using the AXSM-E card as well. This feature enables PXM1 and IGX 8400 feeder nodes to be directly connected to the AXSM-E cards on the PXM45 nodes.

Platform

•MGX 8850 (PXM45)

Cell Bus Service Modules on PXM45

This feature allows key Cell Bus Service Modules to be supported on the MGX 8850 (PXM45). Where necessary, these cards can be used in conjunction with the SRME or SRM-3T3/C Service Resource Module for distribution and redundancy purposes. Please see Table 2 for details.

Platform

•MGX 8850 (PXM45)

---

Note Support for these Service Modules is already available on all PXM1 and PXM1E platforms.

---

Table 3 Cell Bus Service Modules (CBSMs) Supported in Release 4.0.00 and 4.0.10 

	MGX 8850				MGX 8830	MGX 8950
Cell Bus Service Modules	PXM45(A)	PXM45/B	PXM45/C	PXM1E	PXM1E	PXM45B/C
MGX-AUSM-8T1/B	NO	NO	NO	YES	YES	NO
MGX-AUSM-8E1/B	NO	NO	NO	YES	YES	NO
AX-CESM-8T1	NO	YES (see Note 1)	YES (see Note1)	NO	NO	NO
MGX-CESM-8T1/B	NO	YES	YES	YES	YES	NO
AX-CESM-8E1	NO	YES	YES	YES	YES	NO
MGX-CESM-T3E3	NO	NO	NO	NO	NO	NO
AX-FRSM-8T1 and AX-FRSM-8E1	NO	YES	YES	YES	YES	NO
AX-FRSM-8T1-C and AX-FRSM-8E1-C	NO	YES	YES	YES	YES	NO
MGX-FRSM-2CT3	NO	YES	YES	YES	YES	NO
MGX-FRSM-2T3E3	NO	YES	YES (see Note 3.)	YES	YES	NO
AX-FRSM-HS1	NO	NO	NO	NO	NO	NO
AX-FRSM-HS2	NO	NO	NO	NO	NO	NO
MGX-FRSM-HS2/B	NA	YES	YES (see Note 3.)	YES	YES	NO
MGX-SRME	YES (see Note 2.)	YES	YES	YES	YES	NO
MGX-SRM-3T3/C	NO	YES	YES	YES	YES	NO
MGX-VISM-8T1 and MGX-VISM-8E1 *	YES	YES	YES	NO	NO	NO
MGX-VISM-PR-8T1 and MGX-VISM-PR-8E1 *	YES	YES	YES	YES	YES	NO

---

Note 1. For better performance, we encourage you to use MGX-CESM-8T1/B on nodes with PXM45/B and PXM45/C processor/ controller cards.

---

---

Note 2. APS is not supported for SRME on PXM45(A).

---

---

Note 3. New and supported in 4.0.10

---

AXSM-32-T1E1-E UNI with IMA

This feature allows the AXSM-32-T1E1-E to support the IMA capability on a UNI, VUNI, and EVUNI interface. This is in addition to the IMA trunking feature already supported in a previous release.

Platforms

•MGX 8850 (PXM45)

PXM45/C

The PXM45/C is a combination ATM switching fabric/processor card. The switching fabric provides 45 Gbps of non-blocking switching capacity, while the processor provides the control plane that delivers ATM networking software, diagnostics, and performance monitoring.

Platforms

•MGX 8850 (PXM45)

•MGX 8950

AXSM-1-9953-XG

The AXSM-1-9953-XG ATM Switch Service Module is a high-density, double-height Service Module for use in the Cisco MGX 8950 Next Generation Multiservice Switch in combination with the high-capacity PXM45 processor switching module and the XM-60 switching module, to deliver OC-192c/STM-64 trunk connectivity.

Up to 12 AXSM-XG service modules can be accommodated in the Cisco MGX 8950.

Platforms

•MGX 8950

AXSM-4-2488-XG

The AXSM-4-2488-XG ATM Switch Service Module is a Quad OC-48/STM-16, double-height service module for use in the Cisco MGX 8950 Next Generation Multiservice Switch. Used in combination with the high-capacity PXM45 processor and the XM-60 switching module it delivers high density connectivity of 4 interfaces of OC-48/STM-16, either in a clear-channel format or as channelized to OC-12/STM-4, OC-3/STM-1, and DS-3.

Up to 12 AXSM-4-2488-XG service modules can reside in the Cisco MGX 8950, to provide up to 48 OC-48/STM-16 interfaces to support service providers that require both high bandwidth and highest network availability. When used in the channelized mode, each service module can carry alternatively up to 64 DS-3 channels, 64 OC-3/STM-1 channels, 16 OC-12/STM-4 channels, or any combination of these 3 types adding up to 64 channels.

Platforms

•MGX 8950

Enhancements

The product enhancement requests (PERs) in Table 4 were introduced in Release 4.0.00.

Table 4 Product Enhancement Requests in Release 4.0.00 

Enhancement Number or Description	Purpose
AUSM CAC based on SCR 1822	This enhancement is for the PXM and the AUSM 8T1E1 cards.As part of this feature an option is provided to the customer per card to select the CAC feature. The option available is SCR based CAC or PCR based.
Scaling to 1 to 2 million connections 1820	The purpose of this enhancement is to introduce several concepts: 1) Global Transaction ID that will be maintained per SM. (AXSM/AXSM-E/AXSM-XG/PXM1E/SES). This will be used by the CWM to check if its db is in sync with that of the switch. 2) Static Connection File will be pre-created by the switch depending that are rules dependent. This will eliminate the need for CWM to wait for file creation and can be directly FTP'ed from the switch. 3) Incremental File that will only contain data necessary for CWM to sync up. CWM will specify the Transaction ID that it is in sync with and the switch will only provide connection data from the same Transaction ID. This will eliminate returning back data that is not needed by CWM.
Persistent Topology 2291	Purpose of this feature is to enable the CWM to maintain a persistent topology information of the entire network. One or more nodes will be designated as gateway nodes. Whenever CWM needs info about the network, it will query gateway nodes to collect the necessary information.
Preferred Route including MPG 2489, 3383	Preferred routing of connections provide the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route follows the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route follows only the configured path; if the configured path is not available, the connection remains unrouted. Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.
Display Hot Standby for AXSME and AXSM-XG 2834	When the CLI command is given on a Standby AXSM or AXSME, for the verification of the persistent information, it reads the information from the Active PXM disk and compares with the configuration in its RAM. First, the number of records for each type of configuration will be compared. Then, the record data itself will be compared for each existing record. It displays any discrepancies on the terminal. In the case of non-persistent information, the Standby AXSM or AXSME obtains the non-persistent information from its active peer and compares it with what it has in its RAM. It displays any discrepancies on the terminal.
Additional CBSM Stats 2965	Additional CBSM stats for FRSM Port/PVC and AUSM.
Reroute speed increase using PXM45/C 3726	Doubling connection reroutes-per-second rate on MGX.
Larger Stat Counters via AXSM-XG 3727	AXSM-XG supports 64 bit stats.
Narrow Band Service Modules on PXM45 3733	Narrowband Service Module support on MGX 8850 PXM45.
MPG Logical Topology configuration and display 4103	Currently, for a user to construct a PNNI topology map, the user depends upon the PNNI CLI commands. This is especially difficult to do for a MPG topology. This enhancement allows CWM to display such topology on its GUI by means of SNMP as well as the traps received from the switch
Dsplog entry sync 4928	Currently, the events which occur on the Service Modules (SMs) are logged ONLY on the disk of Active PXM and are not replicated on the standby PXM. On the other hand, events which occur on either of the PXM itself are replicated on the peer PXM as well. This design leads to these problems: •The user gets an inconsistent view of the events. Some events are replicated while others are not. This leads to hindrance during the debugging. The user generally expects same event-logs on both the PXMs. •It leads to one point of failure for the SM events. If an SM event was logged to a PXM and its hard disk crashes, it is not possible to recover the event from the standby PXM. In order to remove these deficiencies in the event-log application, this project will implement the changes required to replicate the SM events to the standby controller card. This will help in providing a consistent view of the SM events to the user and improve the reliability.
Additional PNNI Stats for Collection 6052, 6053, 6054, 6055	The purpose of this feature is to provide complete network management support (via CWM) to help customers deploying SPVC/P circuits to collect and analyze relevant statistics for the purposes of, but not limited to, trouble shooting the network issues, engineering the network resources and load balancing the traffic.
Remote end of the connection is not informed on endpoint failure -Part of feeder projects 6558	This document describes the functionality of the LMI/XLMI support on AXSM-E/PXM1E in MGX 8850 routing nodes. Starting from MGX Rel2, AXSM already has feeder trunk support. LMI-based feeder trunks on AXSME/PXM1E give the customer the flexibility of attaching MGX Rel1 (which is a concentrator for CPE equipment) and/or IGX 8400 (in feeder mode) to the MGX as the Routing Node. Also, XLMI support on AXSME/PXM1E will enable the customer to connect BPX-based AutoRoute networks to MGX 8850 (PXM45)-based PNNI networks. Feeders can be connected to an MGX 8850 (PXM45) routing node via feeder trunks on AXSM/AXSME. On MGX 8850 (PXM1E) routing nodes, feeders can be directly connected via feeder trunks to the PXM1E.
AIS Delay Timer 6600	Current connection re-routing sends AIS/Abit from both ends of a connection when the connection is de-routed. Sending AIS/Abit during grooming may cause customer to revert to backup facilities. The AIS Delay feature would provide a mechanism to delay AIS/Abit up to a configurable time.
Trunk Deroute Delay Timer 5048	This feature will add the de-route delay feature, currently supported in AutoRoute on the BPX/IGX, to the PNNI networking software. 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 say, LOS, LOF, AIS-P etc.) This feature does not support failure scenarios caused due to dnport, dnpnport and card failures.
Absolute Grooming Threshold 2600	In the current implementation of connection grooming on MGX switches, the connections are chosen for grooming if the cost of the new path available is better (smaller) than the current cost of the connection by a configurable threshold. The threshold is calculated as a percentage of the existing cost of the connection. The percentage of threshold change can be configured through the CLI. This feature will allow grooming to use an absolute cost threshold in addition to percentage of threshold change.

Service Class Template (SCT) File Information

This section contains SCT file information for Release 4.0.10.

PXM1E

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

•PXM1E_SCT.PORT.5

•PXM1E_SCT.PORT.6

The default SCTs provided with Release 4.0.10 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.

PXM1E_SCT.PORT.5.V1:Check sum is = 0x18a4fdad= 413466029

PXM1E_SCT.PORT.6.V1:Check sum is = 0x2cb30eb7= 749932215

PXM1E does not support CARD SCT. See CSCdx55759 for details.

ABR VSVD parameters are not supported due to hardware limitation.

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

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:

•SCT 4 - policing enabled for PNNI, disabled for MPLS

•SCT 5 - policing enabled for PNNI, disabled for MPLS

•SCT 6 - Policing disabled, used for trunks

•SCT 52 - Policing enabled on PNNI, disabled on MPLS

•SCT 53 - Policing disabled on PNNI and MPLS

•SCT 54 - Policing enabled on PNNI, disabled on MPLS

•SCT 55 - Policing disabled on PNNI and MPLS

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

•AXSME_SCT.PORT.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.5.V1:Check sum is = 0x53c67945= 1405516101

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

AXSM-4-2488-XG

These are the new AXSM-4-2488-XG SCT Files:

•SCT 1, 2 - Policing disabled on PNNI and MPLS

•SCT 100, 200, 300, 400, 500 - Policing disabled on PNNI and MPLS

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

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

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

The checksum is:

•AXSMXG_SCT.CARD.1.V1: Check sum is = 0xea8c7cc4= 3935075524

•AXSMXG_SCT.CARD.2.V1: Check sum is = 0x2bb41874= 733223028

•AXSMXG_SCT.PORT.100.V1: Check sum is = 0x7bd15b34= 2077317940

•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 = 0xce44971c= 3460601628

•AXSMXG_SCT.PORT.500.V1: Check sum is = 0x62f8e58f= 1660478863

•AXSMXG_SCT.PORT.101.V1: Check sum is = 0xe6c5b937= 3871717687

•AXSMXG_SCT.PORT.201.V1: Check sum is = 0x54963d54= 1419132244

•AXSMXG_SCT.PORT.301.V1: Check sum is = 0x73945353= 1939100499

•AXSMXG_SCT.PORT.401.V1: Check sum is = 0xc8a295e9= 3366098409

•AXSMXG_SCT.PORT.501.V1: Check sum is = 0x31cbc16d= 835436909

•AXSMXG_SCT.PORT.110.V1: Check sum is = 0x4c3108e9= 1278281961

•AXSMXG_SCT.PORT.210.V1: Check sum is = 0x98470301= 2554790657

•AXSMXG_SCT.PORT.310.V1: Check sum is = 0x65d5be76= 1708506742

•AXSMXG_SCT.PORT.410.V1: Check sum is = 0xa89a40f5= 2828681461

•AXSMXG_SCT.PORT.510.V1: Check sum is = 0x5740c45= 91491397

•AXSMXG_SCT.PORT.111.V1: Check sum is = 0xbf1c77e9= 3206313961

•AXSMXG_SCT.PORT.211.V1: Check sum is = 0x3e304ff3= 1043353587

•AXSMXG_SCT.PORT.311.V1: Check sum is = 0xa0f7eeb7= 2700603063

•AXSMXG_SCT.PORT.411.V1: Check sum is = 0x92193268= 2451124840

•AXSMXG_SCT.PORT.511.V1: Check sum is = 0x852dc30= 139648048

FRSM-12-T3E3

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

•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 user should not change it

•SCT 4 - PNNI

The checksum is:

•FRSM12_SCT.PORT.4 checksum = 0x28539d36

• FRSM12_SCT.CARD.4 checksum = 0x28539d36

System Requirements

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

Software/Firmware Certified Releases

Table 5 lists Cisco WAN or IOS products that are certified with Release 4.0.11.

Table 5 MGX 4.0.11 Certified Release Matrix 

Product	N	N-1	N-2
CWM	12.0.00 P1.1	NA	NA
MGX 8220	5.0.19	4.1.12	NA
MGX 8230 (PXM1) MGX 8250 (PXM1) MGX 8850 (PXM1)	1.2.21	1.2.12	1.1.42 1.1.34
MGX 8850 (PXM45)	4.0.11	3.0.20 3.0.23	2.1.81
MGX 8950 (PXM45)	4.0.11	3.0.20 3.0.23	2.1.81
MGX 8830 (PXM1E) MGX 8850 (PXM1E)	4.0.11	3.0.20/3.0.21 Combo/3.0.23	NA
BPX/IGX	9.4.10	9.3.47 9.3.36	9.2.43
BXM FW	MFY	MFX	MFV
UXM FW	ACJ/ABU	ACJ/ABU	ABU
URM FW	XBC	XBC	NA
SES	4.0.10	3.0.20 3.0.23	1.1.75
IOS RPM-PR	12.2(15)T5	12.2(15)T2	NA
IOS RPM-XF	12.2(15)T5	12.2(15)T2	NA
IOS URM	12.2(13)T	12.2(8)T4	NA
VISM-PR	3.1.2	3.1.1	NA
VISM	3.1.2	2.2.1	NA

MGX and RPM Software Version Compatibility Matrix

Table 6 lists the software that is compatible for use in a switch running Release 4.0.11 software. Note that the AXSM/B cards use the same software as AXSM cards.

Table 6 MGX and RPM Software Version Compatibility Matrix 

Board Pair	Boot Software	Minimum Boot Code Version	Runtime Software	Latest Firmware Version	Minimum Firmware Version
PXM45	pxm45_004.000.011.201_bt.fw	4.0.10	pxm45_004.000.011.201_mgx.fw	4.0.11	4.0.11
PXM45/B	pxm45_004.000.011.201_bt.fw	4.0.10	pxm45_004.000.011.201_mgx.fw	4.0.11	4.0.11
PXM45/C	pxm45_004.000.011.201_bt.fw	4.0.10	pxm45_004.000.011.201_mgx.fw	4.0.11	4.0.11
PXM1E-4-155 (MGX 8850 (PXM1E) chassis)	pxm1e_004.000.011.203_bt.fw	4.0.10	pxm1e_004.000.011.203_mgx.fw	4.0.11	4.0.11
PXM1E-8-T3E3 (MGX 8850 (PXM1E) chassis)
PXM1E-T3E3-155 (MGX 8850 (PXM1E) chassis)
PXM1E-8-155
PXM1E-4-155 (MGX 8830 chassis)	pxm1e_004.000.011.203_bt.fw	4.0.10	pxm1e_004.000.011.203_m30.fw	4.0.11	4.0.11
PXM1E-8-T3E3 (MGX 8830 chassis)
PXM1E-T3E3-155 (MGX 8830 chassis)
AXSM-1-2488	axsm_004.000.011.201_bt.fw	4.0.11	axsm_004.000.011.201.fw	4.0.11	4.0.11
AXSM-16-155
AXSM-4-622
AXSM-16-T3/E3
AXSM-1-2488/B	axsm_004.000.011.201_bt.fw	4.0.11	axsm_004.000.011.201.fw	4.0.11	4.0.11
AXSM-16-155/B
AXSM-4-622/B
AXSM-16-T3/E3/B
AXSM-2-622-E	axsme_004.000.011.203_bt.fw	4.0.11	axsme_004.000.011.203.fw	4.0.11	4.0.11
AXSM-8-155-E
AXSM-16-T3E3-E
AXSM-32-T1E1-E
AXSM-4-2488-XG	axsmxg_004.000.011.203_bt.fw	4.0.11	axsmxg_004.000.011.203.fw	4.0.11	4.0.11
AXSM-1-9953-XG-
FRSM-12-T3E3	frsm12_004.000.011.201_bt.fw	4.0.11	frsm12_004.000.011.201.fw	4.0.11	4.0.11
MGX-SRME	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
SRM-3T3/B	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_021.000.011.200.fw	21.0.11	21.0.11
AX-CESM-8T1	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
MGX-CESM-8T1/B	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
MGX-AUSM-8T1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
MGX-AUSM-8E1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
AX-FRSM-8T1	frsm_8t1e1_FR8_BT_1.0.02.fw	1.0.02	frsm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
AX-FRSM-8E1	frsm_8t1e1_FR8_BT_1.0.02.fw	1.0.02	frsm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
AX-FRSM-8T1-C	frsm_8t1e1_FR8_BT_1.0.02.fw	1.0.02	frsm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
AX-FRSM-8E1-C	frsm_8t1e1_FR8_BT_1.0.02.fw	1.0.02	frsm_8t1e1_021.000.011.200.fw	21.0.11	21.0.11
MGX-FRSM-HS2/B	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_021.000.011.200.fw	21.0.11	21.0.11
MGX-FRSM-2CT3	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_021.000.011.200.fw	21.0.11	21.0.11
MGX-FRSM-2T3E3	frsm_vhs_VHS_BT_1.0.06.fw	1.0.06	frsm_vhs_021.000.011.200.fw	21.0.11	21.0.11
MGX-RPM-PR-256	rpm-boot-mz.122-15.T5	12.2(15)T5	rpm-js-mz.122-15.T5	12.2(15)T5	12.2(15)T5
MGX-RPM-PR-512	rpm-boot-mz.122-15.T5	12.2(15)T5	rpm-js-mz.122-15.T5	12.2(15)T5	12.2(15)T5
MGX-RPM-XF-512	rpmxf-boot-mz.122-15.T5	12.2(15)T5	rpmxf-p12-mz.122-15.T5	12.2(15)T5	12.2(15)T5
MGX-VISM-PR-8T1	vism_8t1e1_VI8_BT_3.1.01.fw	3.1.01	vism_8t1e1_003.051.002.100.fw (CALEA image) vism_8t1e1_003.001.002.100.fw (non-CALEA image)	3.51.2 3.1.2	3.51.2 3.1.2
MGX-VISM-PR-8E1	vism_8t1e1_VI8_BT_3.1.01.fw	3.1.01	vism_8t1e1_003.051.002.100.fw (CALEA image) vism_8t1e1_003.001.002.100.fw (non-CALEA image)	3.51.2 3.1.2	3.51.2 3.1.2

Additional Notes

The following notes provide additional compatibility information for this release:

•You can gracefully upgrade to Release 4.0.11 from Release 2.1.80. A switch running 2.0.16 or below must be upgraded to 2.1.80 before being upgraded to 4.0.11.

•MGX 4.0.11 interoperates with SES PNNI 4.0.10 plus BPX Switch Software (SWSW) 9.4.10 plus BXM MFY.

•This release supports feeder connections from Cisco MGX 8850 Release 1.2.21. 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 CWM Release 12.0.0 Patch 1.1 to manage networks that contain MGX switches running Release 4.0.11.

•The RPM-PR and RPM-XF software in this release is based on IOS release 12.2(15)T5.

•The SNMP MIB release for 4.0.11 is mgx8850rel4010mib.tar.

Table 7 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 7 APS Protocol Support 

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

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

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, and Cisco MGX 8830 Hardware Installation Guide, part OL-3842-01. That guide covers from MGX Release 2 through 4.
It is available at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/hwdoc/index.htm.

---

New Hardware in Release 4.0.11

No new hardware.

New Hardware in Release 4.0.10

No new hardware.

New Hardware in Previous Release 4.0.00

The following new hardware is supported by the Release 4.0.00 software. Features enabled by the hardware are described in Features and Enhancements in Previous Release 4.0.10.

•PXM45/C

•PXM1E-8-155

•MCC-8-155

•SFP-8-155

•AXSM-4-2488-XG

•SMF-4-2488-SFP

•SMFLR-1-2488-SFP

•SMFSR-1-2488-SFP

•AXSM-1-9953-XG

•SMFSR-1-9953

•SMFIR-1-9953

•SMFLR-1-9953

APS Connectors

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

Table 8 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 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 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 9 lists Product IDs, 800 part numbers, and the minimum revision levels for the MGX 8850 (PXM45).

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

In Table 9, 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 9 Card Numbers and Revisions Supported in Release 4.0.11 for MGX 8850 (PXM45) 

Product ID	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-1GE	800-18420-03	-A0
MGX-1OC12POS-IR	800-08359-05	-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-GE-LHLX	30-1299-01	-A0
MGX-GE-SX	30-1301-01	-A0
MGX-GE-ZX	10-1439-01	-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-RPM-PR-256	800-07178-02	-A0
MGX-RPM-PR-512	800-07656-02	-A0
MGX-RPM-XF-512	800-09307-06	-A0
MGX-SMFIR-1-155	800-14460-02	-A0
MGX-SRM-3T3/C	800-05648-01	-A0
MGX-SRME	800-14224-02	-A0
MGX-STM1-EL-1	800-14479-02	-A0
MGX-VISM-PR-8E1	800-07991-02	-A0
MGX-VISM-PR-8E1	800-07991-02	-A0
MGX-VISM-PR-8T1	800-07990-02	-A0
MGX-VISM-PR-8T1	800-07990-02	-A0
MGX-XF-UI	800-09492-01	-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	800-06147-07	-B0
PXM45/B	800-09266-04	-A0
PXM45/C	800-20217-04	-A0
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

Table 10 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)
FRSM-12-T3E3	SMB-6-T3E3	—
PXM45/C	PXM-HD PXM-UI-S3/B	— —
PXM45	PXM-HD	—
	PXM-UI-S3	—
PXM45/B	PXM-HD	—
	PXM-UI-S3	—
AXSM-1-2488	SMFSR-1-2488	Yes
	SMFLR-1-2488	Yes
	SMFXLR-1-2488	Yes
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-SRME	MGX-SMFIR-1-155	Yes
	MGX-STM1-EL-1	Yes
MGX-SRM-3T3/C	MGX-BNC-3T3-M	Yes
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-1OC12POS-IR	—
	MGX-GE-LHLX1	—
	MGX-GE-SX1	—
	MGX-GE-ZX1	—
AX-CESM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
	MGX-RJ48-8E	—
MGX-CESM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
	MGX-RJ48-8E1	—
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	—
	MGX-RJ48-8E1	—
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-RJ48-8E1	—
AX-FRSM-8E1	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-FRSM-2CT3	MGX-BNC-2T3	—
MGX-FRSM-2T3E3	MGX-BNC-2E3	—
	MGX-BNC-2T3	—

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

MGX 8850 (PXM1E) Product IDs and Card Types

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

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

Table 11 Card Numbers and Revisions Supported in Release 4.0.11 for MGX 8850 (PXM1E) 

Product ID	800 P/N	Min. 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-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
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 12 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	Yes
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-SFP22	—
	SMFLR-1-155-SFP1	—
	SMFIR-1-155-SFP1	—
	PXM-UI-S3/B	—
MGX-VISM-PR-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
	MGX-RJ48-8E1	—
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-SRM-3T3/C	MGX-BNC-3T3-M	Yes
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	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-AUSM-8E1/B	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-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	—
	MGX-RJ48-8E1	—
AX-FRSM-8T1	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
	MGX-RJ48-8E1	—
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	—
	MGX-RJ48-8E1	—
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. 2

---

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

---

MGX 8830 Product IDs and card types

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

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

Table 13 Card Numbers and Revisions Supported in Release 4.0.11 for MGX 8830 

Product ID	800 Part Number	Min. Revision
PXM1E-8-155	800-21686-04	-A0
SFP-8-155	800-21518-03	-A0
MCC-8-155	800-22117-02	-A0
PXM-UIS3/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
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-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 14 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	Yes
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-SRM-3T3/C	MGX-BNC-3T3-M	No
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	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-RJ48-8E1	—
MGX-AUSM-8E1/B	AX-SMB-8E1	—
	AX-R-SMB-8E1	—
	AX-RJ48-8E1	—
	AX-R-RJ48-8E1	—
	MGX-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-RJ48-8E1	—
MGX-CESM-8T1/B	AX-RJ48-8T1	—
	AX-R-RJ48-8T1	—
	MGX-RJ48-8E1	—
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	—
	MGX-RJ48-8E1	—
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-RJ48-8E1	—
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 15 lists Product IDs, 800 part numbers, and revision levels for the MGX 8950.

Table 16 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 15 Card Numbers and Revisions Supported in Release 4.0.11 for MGX 8950  

Product ID	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
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
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

Table 16 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	—
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-1OC12POS-IR	—
	MGX-GE-LHLX1	—
	MGX-GE-SX1	—
	MGX-GE-ZX1	—

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

New and Changed Commands

There are no new or changed commands in Release 4.0.11. Some command information in these release notes is repeated from the Release 4.0.10 release notes.

Please refer to the following manuals for details about commands:

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

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

Limitations, Restrictions, and Notes for 4.0.11

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

Limitations

•addcon command should not be run on an AXSM running a 3.0 version when the PXM is a 4.0 version. Using this command in this mixed version configuration can have the side effect of a PXM task exception especially with SPVC DAX connections.

•When a user executes the commands delpart and delport, the controller would send release on the connections routed over NNI links before doing unbind with the pnport. When a new port comes up, the addcon is rejected by CMTask as the old connection is still not released (unbind pending). When unbind finally happens, the old connection gets removed and new control vc can get added. (Please see CSCeb35266 for more information.)

•The SVCC-RCCs between LGNs are not established after the level is changed on one of the LGNs. The Upnode id of the uplinks to the level changed LGN displayed by the command 'dsppnni-inducing-uplink' still shows the old level instead of the new level. The Upnode is enabled quickly after the node level is changed. For example, the following sequence of commands are cut and pasted to change the Upnode level. (Please see CSCeb36703 for more information.)

• 'cnfpnni-node <node-index> -enable false'.

• 'cnfpnni-node -level <level> -nodeId <node-id> -pgId <pg-id>'.

•'cnfpnni-node <node-index> -enable true'.

The workaround of this is to disable and then re-enabled the Upnode with the level changed using the command 'cnfpnni-node'.

•When a delpnni-node is issued for a higher level node, a dynamic memory buffer is leaked. This should not cause a problem unless the dynamic memory partition is low on memory. The workaround for this is to do a switchcc.

•When a user executes the commands delpart and delport, the controller would send release on the connections routed over NNI links before doing unbind with the pnport. When a new port comes up, the addcon is rejected by CMTask as the old connection is still not released (unbind pending). When unbind finally happens, the old connection gets removed and new control vc can get added. (Please see CSCeb35266 for more information.)

•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 to 4.0.10

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

•The statistics associated with the on-line and off-line diag tests (viewed via dspdiagstat) get corrupted after an upgrade to 4.0. A clrdiagstat CLI command should be issued against all slots after an upgrade has been completed. Please see CSCea42260 for more formation.

•The persistent link database is not supported on PXM45(A) cards. Therefore, if the persistent topology gateway node of a peer group has PXM45(A) cards, then before this node is upgraded to the 4.0 release, another node with PXM45/B/C cards have to be configured to be the persistent topology gateway node for this peer group. The node with the PXM45(A) card should then be disabled as the gateway node. Then, proceed with the upgrade for this node.

•To upgrade to 4.0.10, you will not need to upgrade to 3.0.20 if running 3.0.10.

•If you upgrade from 3.0, 3.0(21.100) or any pre-3.0 release to 4.0, the node will report a few instances of the following error message during burnboot and switchcc:

–Error Log for Slot 07: Error Num 5
Event Logged:
07I00229 04/02/2003-17:49:14 SMGR-4-INVD_RET
E:00005 tStDnld19 smgrApiSHMFileDownload
smgrApiSHMFileDownload: Card not in correct state

•Setup and operation of the Preferred Route feature is changed between MGX Release 3 and MGX Release 4. Please refer to the MGX Software Configuration Guide listed in the "Related Documentation" section for information on how to migrate Release 3-based preferred routes into a Release 4-based network after the 4.0 upgrade is complete. For your convenience, the Preferred Routes information from the MGX 3.0.20 release notes is repeated in these notes, in the following section.

---

Caution Due to significant differences in the Preferred Route feature between Release 3 and Release 4, all Preferred Route information is lost during migration to Release 4. To facilitate the recreation of the preferred routes, make sure a record of the routes is available before starting the upgrade.

---

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 4.0 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 VISM and RPM 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.

•The preferred routes can be specified only within a PNNI single peer group meaning all the nodes in the preferred route lie within the same peer group.

•All the nodes in the network should be running Release 3.0.00 software to use the preferred route feature.

•All the links specified in the preferred route should be PNNI links.

•If a node in the PNNI network changes its PNNI node ID, the old entry in the persistent topology database in all the nodes in the network need to be deleted. If any of the preferred routes in any nodes in the network contains the changed node as one of the hops, the preferred route(s) must be modified using the new table index (in the persistent topology database) allocated for the changed node.

•If a node in the PNNI network is deleted via configuration commands from the persistent topology database, if any of the preferred routes configured at that node (where the delete command is executed) contains the deleted node as one of the hops, the preferred route(s) must be deleted/modified manually.

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

•Due to differences in physical port numbering, non-Cisco nodes can only be the terminating nodes in a preferred route.

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

•The preferred route configuration is available using only the CLI at the PXM controller. The configuration of the preferred route will be available with the CWM proxy service agent in a future CWM release.

PXM45/C

Supported only on MGX 8850 (PXM45) and MGX 8950, starting with release 4.0.00.

192 Signaling Interfaces

This feature has been tested on PXM45/B and PXM45/C on MGX 8850 and MGX 8950 platform only. Based on the assumption that the limit for signaling interface of PXM45(A) will remain unchanged, and that for PXM45/B and PXM45/C, the number of signaling interfaces supported will be increased to 192 and the number of physical ports supported will be 4000 (same as the limit for MGX 8850/8830 PXM1E when supporting cell bus service modules).

Closed User Group (CUG)

The following notes pertain to the CUG feature:

•If a Closed User Group(CUG) membership configuration is modified in any manner, the CUG interlock code information maintained by the SVC connections which have already been routed is not altered.

•The CUG feature is not supported on nodes which are configured with right-justified E.164 addresses using cnfe164 justify.

•This feature allows a maximum of 100 CUGs per AESA address at a UNI interface.

•This feature allows CUG membership to be provisioned at a maximum of 200 AESA addresses per node, assuming that none of the AESA addresses are assigned to multiple interfaces. However this limit is not enforced in the software.

•If some of these AESA addresses are assigned to more than one interface, the number of AESA addresses supported by this feature is correspondingly reduced. For instance, if all the addresses on the node are assigned to two interfaces, CUG membership should not be provisioned for more than 100 addresses per node.

•When configuring CUGs on a node, up to 20000 different 20-byte AESA administrative addresses can be specified (200 address with 100 CUGS each) in the leading portion of the CUG interlock codes within the node.

•The space taken by these CUG IC AESAs is shared with that used to store the calling/called party numbers of the in-progress or active connections.

•This feature is now supported on PXM45(A) on MGX 8850 switches

Point to Multipoint SVC/SPVC Support

The following notes pertain to the Point to Multipoint (P2MP) feature:

•This feature is not supported in PXM45(A) and AXSM-E.

•There is a switch xbar design limitation on AXSM-XG specific to P2MP. The Humvee based cards can have only 8 serial links turned on while the Europa based cards would have their 16 serial links enable. When all the targets (leaves) are humvee based, the Europa is getting grants on only 8 links.

•Release 4 is not UNI40 and PNNI P2MP conformace compliant.

•There is an AXSMB switch xbar design limitation for P2MP traffic wherein if some of the ports are shut down and if there are p2mp leaves present in those ports, the cells of those leave will not be delivered while other leaves might get traffic.

AXSM-32-T1E1-E/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.

•Auto-restart(persistent Rx IMA ID) feature is not 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 5ms 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

Cell Bus Service Modules (formerly know 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 (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) 7200

•CBSM (max non-dax) 27K.

AXSM-E as Upstream to Feeder Nodes

These notes apply to the AXSM-E:

•The AXSME cards only work on the MGX 8850 (PXM45).

•Above T3/E3, the AXSM-E port density is only half the density of AXSM and AXSM/B.

•The highest port bandwidth supported on AXSM-E is OC-12/STM-4.

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 CWMGUI may show the connection as incomplete.

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):

•There is no CLI retrieve POST (Power On Self Test) display.

•POST can only be displayed on the console during boot up.

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

•Standby alarms not raised for HMM and Online Diagnostics. Alarms will NOT be raised for HMM and Online Diagnostics on the Standby card.

Reserved VCIs

Here are the reserved VCIs that the customer cannot provision:

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

Non-native Controller Front Card and PXM-HD Card

•Cisco recommends that the hard disk on the PXM1E front card and PXM-HD back card should contains at least 30% of free disk space at all times.

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

•Cisco recommended that customer regularly groom their system hard disk, that is, to remove all old files or outdated runtime and boot images residing under the following directories: C:/FW, C:/RPM, and E:/RPM. Also, any old and core files under C:/ and C:/CNF/ directories. All file removal will be perform by customer from the active pxm.

•Cisco highly recommends that the customer regular backup their saved system configuration to their local server.

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

•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 

---

clrsmcnf Command

These notes pertain to the clrsmcnf command:

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

•New commands dspadjlnalm and dspadjlnalmcnt are now supported on AXSM.

•Port LED lights on AXSM-E 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 card, the LEDs always remain green whether the lines are in LOS irrespective of which lines are Active (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 feature in Release 4.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 Release 4.0.00.

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

Preferred Route

These notes pertain to the preferred route feature:

•RPM and VISM cards do not support preferred routes in 4.0.10 release.

•QoS precedence over Preferred Route does not apply to MPG network (CSCdz40310).

•Preferred route configured with higher node ID cannot be blocked (CSCdz41145, CSCdz49001).

•delpref when Preferred Route in use is allowed in Release 4 and not in Release 3

•The preferred routes can be specified only within a PNNI single peer group meaning all the nodes in the preferred route lie within the same peer group.

•All the nodes in the network should be running Release 4.0.00 software to use preferred route feature

•All the links specified in the preferred should be PNNI links

•If any of the nodes in the pnni network changes its pnni node id, then the old entry in the persistent topology database in all the nodes in the network need to be deleted. If any of the preferred routes in any of the nodes in the network contains the changed node as one of the hops, then the preferred route(s) has to be modified using the new table index (in the persistent topology database) allocated for the changed node.

•If any of the nodes in the pnni network is deleted via configuration commands from the persistent topology database, if any of the preferred routes configured at that node (where the delete command is executed) contains the deleted node as one of the hops, then the preferred route(s) has to be deleted/modified manually.

•If any of the nodes in the pnni network is removed via physical de-commissioning and if any of the nodes in the network had some preferred routes that contain the removed node as one of the hops, then the preferred route(s) has to be deleted/modified manually.

•Due to differences in physical port numbering, non-MSSBU nodes can only be the terminating nodes in a preferred route.

•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 de-routed to route back to its preferred route. The user has to de-route/re-route using configuration commands. (optrte, rrtcon, dncon/upcon etc.)

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 nack us. When the second clock is naked no warning or message is given by the CLI. The NAK can only be found out by looking through the logs. The second clock configured on the AUSM will not be reflected in the clocking database

•If the line carrying the primary or the secondary clock source goes in alarm and a switchcc is done on the switch the clock configuration for the line in alarm will be wiped out. The clock configuration will also be wiped out if any card is rebooted when the clocking line is in alarm. This only applies to AXSM.

•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 on a service module, the primary and secondary (if configured) clock sources will be recommitted even though the primary or secondary clock source is not a port on the service module that was reset. 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. (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

RPM-PR and RPM-XF Limitations

For Release 4.0.10, Route Processor Module (RPM) cards have their own release notes. For details on RPM cards, refer to the "Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for MGX Release 1.2.21 and MGX Release 4.0.10" or the "Release Notes for Cisco MGX Route Processor Module (RPM-XF) for MGX 8850 (PXM45) Release 4.0.10". These release notes are available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm. They are found under the switch name (for example, MGX 8850 (PXM45), Release 4, Route Processor Module, Release Notes).

Restrictions

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

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.

AXSM Model B Restrictions

These restrictions apply to AXSM model B cards:

•The enableaxsmbaps command is a PXM CLI command required to turn on additional APS features on AXSM/B cards in Releases 3.0.x and up. By issuing this command, the card operating mode becomes AXSM Op B. This command is required only while upgrading configured cards with Release 3.0.x images. If the AXSM/B cards do not have any configuration and are upgraded with Release 3.0.x, then the card operating mode would be made as AXSM Op B and it is not required to issued the enableaxsmbaps command.

The command has the following syntax:

• enableaxsmbaps <primary | secondary slot>

•The enableaxsmbaps command should be given after the completion of upgrading to Release 3.0.x. The following requirements are needed to change the card operating mode to AXSM Op B:

•For redundant cards, both the cards should be AXSM/B cards and the image on both cards should be Release 3.0.x and up.

•For non-redundant cards, the card should be an AXSM/B and the image should be Release 3.0.x and up.

Formatting Disks

The hard disks should not be formatted with the Release 4.0.00 backup boot or runtime firmware. The Release 4.0.00 firmware initializes the disks with DOS File System Version 2.0 where as the earlier 2.x releases use DOS File System Version 1.0. As a result, if the hard disks are formatted with Release 3.0.00 firmware, those disks will become unusable in nodes running Release 2.x firmware. Since, Release 4.0.00 firmware is backward compatible, it can use hard disks with DOS File System Version 1.0.

Saving Configurations

The C disk drive should not be used for saving multiple older configurations, images, and core dumps. The disk space on this drive is needed to save event logs and configurations, and the logs and configurations will not be correctly saved if there is inadequate disk space.

•Save on all active PXM45 and PXM1E cards.

Other Limitations and Restrictions

Here are additional notes that pertain to Release 4.0.00:

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

•Bulk Status Enquiry is a proprietary signaling message used to check whether connections across peer nodes are intact. It is triggered automatically upon PXM switchover as well as in other scenarios like SSCOP link establishment. Though Bulk Status Enquiry will not work with Release 2.1 when the peer node is running release 3.0/4.0, there is an automatic fall back mechanism to standards specific "Normal Status Enquiry" procedure in case the bulk procedure fails. Hence, there should be no loss of functionality as a result of this limitation.

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

•Configuration required for preventing CLI lockout on PXM45(A) based via nodes: When a PXM45(A) based node is a via node for PXM45/C based end nodes, a normal deroute followed by a reroute will result in a CLI lockout on the PXM45(A) node. If there are permanently failed connections originating on the PXM45/C end nodes, then the CLI lockout will be extensive. To circumvent this situation, configure the following on the PXM45/C nodes which are adjacent to the PXM45(A) node: cnfnodalcongth -connpendhi 950 -connpendlo 750 Note that this is same as the recommended threshold for PXM45/B. This will ensure that the PXM45/C based nodes do not pump SETUPs towards the PXM45(A) node at a high rate. (CSCdz90598)

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

•PXM disk sync verification will not work if an upgrade is in progress.

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

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

Limitations and Restrictions for 2.1.x

This section is extracted from the MGX 2.1.80 release notes. It describes the following issues for Releases 2.1.60 through 2.1.80:

•General limitations, restrictions, and notes

•APS management information and open issues

•Clearing the configuration on redundant PXM45/B cards

General Limitations, Restrictions, and Notes

The following limitations and restrictions apply to Release 2.1.x and other releases:

•After switchcc, there was some competition for 8,000 buffer resources. Since dbSync could not allocate the buffer to handle its file sync between Active and Standby, the "going to be" Standby card was reset again then came up later.

In 2.1 and earlier, dbSync allocates its resources from the same LOW priority pool as many other applications; therefore, dbSync might fail should the resource in this pool be used up.

In 3.0 and later, there was an enhancement to let critical tasks (dbSync, syncRam.) allocate its resources with a HIGH priority option. This means these tasks can get its resources from both LOW and HIGH priority pool and prevent this problem from happening (CSCdz84282).

•For a graceful upgrade, you must upgrade from version 2.1.80, or 2.0.16 or below to 2.1.80 to 3.0.00.

•Presently, the PXM CLI allows for provisioning of a PNNI controller (controller id 2) on any slot in the chassis, but for this release, such provisioning should be restricted to slot 7 only.

•APS is not supported on AXSM-1-2488/B.

•Of 192 PNNI interfaces, up to 100 interfaces can be signaling ports. The other 92 interfaces should be non-signaling ports, such as non self-supporting ports.

•AXSM-1-2488 and AXSM-1-2488/B cards do not have a policing function enabled.

•The front card hardware (mother board/daughter board) for each card type can support up to two back cards. But in Release 2.1.80, only one AXSM-E back card (i.e., half the port capacity available in hardware) is supported by software. The full port capacity will be supported with a future software release. No hardware changes will be required.

•In Multiple Peer Group (MPG) mode, when one switches over to the standby on a PGL node with 3 levels, it can take several minutes on the standby card for this PGL to come up and the SVC based RCC to setup. This is normal behavior, because PNNI doesn't support hot redundancy. So on switch over, the entire PNNI database has to be rebuilt. (It is like a reboot for PNNI, even though the active calls are not affected.)

•Trace information captured in the error logs of non PXM slots (seen with dsperr -sl <slotnum>) will not translate addresses in the trace to correct symbolic names. Such files with trace data need to be moved off the system using FTP and forwarded to TAC and engineering.

•Support for 3 controllers only (1 for PNNI and 2 for LSC). Controller ID 2 is reserved for a PNNI controller; IDs 3-20 are available for LSC controllers.

•Partition ID 1 is reserved for PNNI.

•The maximum number of logical interfaces (physical trunks, virtual trunks, logical ports) supported in this release with PXM45 cards is 99 and PXM45/B cards is 192.

•If an active AXSM card is stuck in the active INIT state, the standby PXM will not go to the standby Ready state until the active AXSM goes to a steady state. Steady states are: Active Ready, Failed, Mismatch, Empty, Empty Reserved, Standby Ready. With redundancy configured, if a standby AXSM card is stuck in a standby init state, with an active Active AXSM already in a Active Ready state, the standby PXM will go to the standby Ready state without any delay. If both AXSMs in the redundancy pair are not in a steady state, then the standby PXM will not go to the standby Ready state until one or both of the 2 AXSM cards are in the active Ready state.

•If the destination address is reachable for both an IISP and a PNNI link from the same node, ABR connections will not route. The current routing algorithm will always choose IISP links over PNNI links because it is local. Since IISP does not support ABR connections, the connection setup will fail.

•In this release, a Service Class Template (SCT) can be changed with connections present. However, if the change affects services in use, the connections will be rerouted.

•When CWM is used to manage the network, the IP address 10.0.x.x cannot be used as the LAN address (lnPci) for the switch.

•If there are MGX-RPM-PR-256/512 card(s) in the node, after clrallcnf, the standby controller card takes longer to come up. The more MGX-RPM-PR-256/512 cards in the node, the longer the standby controller takes to come up. This also happens when the standby controller card is coming up, and MGX-RPM-PR-256/512 cards are inserted into slots that were not previously used for MGX-RPM-PR-256/512 cards.

Limitations for rteopt via parallel links

The following are limitations for rteopt via parallel link.

link 1 . . . . . .. . . .. . . . .link 2

Node A ------------- Node B -------------- Node C

fwd & bwd aw= 500 fwd & bwd aw= 1000

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

link 3 fwd & bwd aw = 2000

Configuration:

•link 1 has forward and backward admin weight set to 500 (via cnfpnni-intf)

•link 2 has forward and backward admin weight set to 1000

•link 3 has forward and backward admin weight set to 2000

•SPVC connection is routed from Node A to Node C (Master endpoint is at Node A) via link 1 and link 2

Scenario 1

Link 2 is down (e.g., via dnpnport), connections are re-routed right away but Node A hasn't had that info updated in the routing tables.

So SPVC on Node A will have routing cost = 2*500 + 2*1000 = 3000, but since link 2 is down, Node B will choose link 3. But the routing cost on Node A SPVC is still 3000 as it did the calculation during the route search.

Now if link 2 is up, if you do rteopt on Node A, it gets the new route, the new path selected has a cost of 3000.

Since spvc has 3000, it doesn't re-route through link 2.

Scenario 2

Instead of link 2 down, if there is a crankback on link 2, the same result stated above will happen.

Scenario 3 (for CBR and VBR)

Link selection is set as maxavcr or maxcr or random on node B (via cnfpnni-selection) If link 2 has less bandwidth than link 3, and the link selection criteria at Node B is set to maxavcr, Node A will still put the cost as 3000 with least aw calculation, but Node B will choose link 3 (even though it is costlier) because it has more bandwidth.

Scenario 4 (for ABR and UBR)

Link selection doesn't apply to ABR and UBR. (via cnfpnni-selection. This is exactly the same as Scenario 3 as ABR and UBR follow load balancing on parallel links instead of choosing the minaw link.

Scenario 5 (for all types of service categories)

After call setup, if the admin weight is increased on the link on which the call is routed, the routing cost calculated during the call setup will not get changed. So if a rteopt is done after increasing admin weights on the existing links on the connection path, the connections will not get optimized to take the newer path.

Workaround

If you dnpnport on link 2 (connections will be routed via link 3), after uppnport on link 2, then use cnfpnni-intf to change the existing admin weight on link 2 to lesser value, e.g., 800 (from 1000).

So when optrte is executed at Node A, routing cost will be = 2*500 + 800(fwd) + 1000 (bwd) = 2800 for the new route of link 2.

Since all SPVC connections have 3000 as the routing cost, connections will be rerouted on link 2.

Important Notes

This section provides general notes that apply to this release, and covers some procedures that are not yet in the manuals.

•You must use the SCT files released with 2.1.80 (number 2 and 3, which were included in version 2.0.13 are similar to number 2 and 3 for 2.1.80) for the Control VC feature. If you are using the MPLS feature, then you will need to change to SCT 4 or 5, which were released with version 2.1.00.

•By default, 2000 cps and 543 cps will be reserved for SSCOP and PNNI Signalling VC respectively, even when you disable SSCOP and PNNI. These values are configurable by the cnfpnctlvc command.

•Do not execute the delcontroller command when connections/ports still exists. The impact of executing delcontroller with connections is that the connections cannot be recovered until the controller is re-added using addcontroller and the AXSM cards or the entire node has to be reset (otherwise ports remain in the provisioning state). There is now a warning to the user of the impact of the command when there are existing connections/ports.

•Analysis of the code has identified a situation which has a low probability of occurring and in fact has not been encountered in any test scenarios to date. This caution and associated workaround is provided as a precautionary measure. When the link bandwidth for SPVC connections is reaching full capacity, making minimal bandwidth available for new SPVC connections, a Conditions can be encountered where the initial software check believes there is sufficient bandwidth for the new SPVC connection; however, the final software confirmation for available bandwidth may be rejected because there is no bandwidth available. If this problem occurs, the system will recover when the PNNI updates are refreshed. (This will happen at the default time of 30 minutes.) The user can recover from this problem by making the Administrative weight of that link very high to avoid that link from being used.

•When the switch cannot automatically resolve nativity check conflicts, you can force a configuration rebuild from a specific hard disk by establishing a console port session through the corresponding PXM-UI-S3 card and issuing the shmRecoverIgRbldDisk command. This command ignores the nativity check and configures the entire switch according to the configuration on the hard disk.

•PNNI default min VCI is 35 unless changed explicitly. The reason for the default is to reserve VCI=32-34 for other control purposes (e.g., MPLS and NCDP). For users who would like to add MPLS controller in future releases of MGX 8850, it is highly recommend to set the min-vci value to be 35 or more for all partitions on the port where the MPLS partition will be added. By doing so, the TDP signaling vc for MPLS will be established automatically on 0/32. MinVPI is not negotiated by ILMI, so the user should set this parameter same on both nodes.

•In Multiple Peer Group (MPG) mode, when one switches over to the standby on a PGL node with 3 levels, it can take several minutes on the standby card for this PGL to come up and the SVC based RCC to setup. This is normal behavior, because PNNI doesn't support hot redundancy. So on switch over, the entire PNNI database has to be rebuilt. (It is like a reboot for PNNI even though the active calls are not affected.)

APS Management Information

The following tips apply to the use of the dspapsbkplane command and the APS connector, which is sometimes called a backplane. The APS connector must be installed to enable intercard APS.

The APS commands dspapsln, dspapslns, switchapsln, and dspapsbkplane were modified in release 2.1.70.

---

Note Commands dspadjlnalm and dspadjlnalmcnt are available since Release 3.0.00. The command dspadjlnalmcnt is supported on AXSM-E and AXSM/B.

---

The APS command dspadjlnalm was new to release 2.1.70.

Refer to the following command references for details about commands mentioned in these release notes:

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

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

---

Note The issues in this section are seen only in Operational mode 1+1, bi-directional, Rev/non-Rev. If at least one side is configured as 1+1 unidirectional, these problems do not occur.

---

The following are some open issues in this release:

•Reset of active AXSM, removal of active AXSM, or AXSM switchover may cause the lines behind that card to be in a LOS status for 20 to 30 ms. If these lines were active at the time, some additional APS switch will occur; and the corresponding lines at the far-end will be in SF alarms before the standby AXSM is coming up. The momentary loss of signal is due to the hardware limitation; no other workaround is available.

•For AXSM/A hardware only: If multiple active lines are removed at the same time, one line may not switchover.

–To recover, either perform lockout of Protection line and Clear from the far end or perform delete APS for the line, then add the APS line back.

Preparing for Intercard APS

The following components are required for intercard APS:

•two front cards.

•two back cards for every pair of slots hosting APS lines. All lines on cards used for intercard APS must operate in APS pairs or use Y cables.

•an APS connector installed between the two back cards for every pair of slots hosting APS lines, except for AXSM-XG cards in an MGX 8950 chassis.

Use the dspapsbkplane command on both the standby and active card to verify that the APS connector is plugged in properly. The following example shows the results displayed by the dspapsbkplane command when the APS connector is in place:

M8xx0_NY.1.AXSM.a > dspapsbkplane

Line-ID   Primary Card Signal Status       Secondary Card Signal Status

                    Slot #1                             Slot #2        

  1.1               PRESENT                             PRESENT

  1.2               PRESENT                             ABSENT 

  2.1               PRESENT                             ABSENT 

  2.2               PRESENT                             ABSENT 

Remote Front Card : PRESENT 

Top Back Card     : ENGAGED 

Bottom Back Card  : ENGAGED 

The following example shows the results displayed by the dspapsbkplane command when the APS connector is not place:

M8xx0_LA.1.AXSM.a > dspapsbkplane

Line-ID   Primary Card Signal Status       Secondary Card Signal Status

                    Slot #1                             Slot #2        

  1.1               PRESENT                             ABSENT

  1.2               ABSENT                              ABSENT 

  2.1               PRESENT                             ABSENT 

  2.2               ABSENT                              ABSENT 

Remote Front Card : ABSENT 

Top Back Card     : ENGAGED 

Bottom Back Card  : NOT-ENGAGED 

---

Note The dspapsbkplane command should be used only when the standby card is in the Ready state. When the standby card is booting or fails, intercard APS cannot work properly and this command displays "NOT ENGAGED."

---

If the dspapsbkplane command displays the message "APS Line Pair does not exist," suspect that the APS is not configured on a line.

If the dspapsbkplane command shows different values for each of the two cards, suspect that the APS connector is seated properly on one card but not on the other.

The APS connector status is the same for all lines in a single bay because the APS connector interconnects two back cards within the same bay. You need to enter the dspapsbkplane command only once to display the APS connector status for both upper and lower bays.

Enter the dspapslns command to verify APS configuration. If the working and protection lines show OK, both lines are receiving signals.

Managing Intercard APS Lines

In AXSM and AXSM/B intercard APS, either front card can be active, and can be connected to either APS line through the APS connector joining the two back cards. The following process describes how intercard APS communication works:

---

Step 1 The signal leaves the front card at the remote end of the line. (See Figure 1 and Figure 2.)

Step 2 The signal passes through the APS connector and both back card transmit ports at the remote end of the line. (See Figure 1 and Figure 2.)

Step 3 The signal travels through both communication lines to the receive ports on both back cards at the local end. (See Figure 1 and Figure 2.)

Step 4 The active front card processes the signal that is received on the active line. (See Figure 1 and Figure 2.)

Step 5 The standby card monitors only the status of the standby line. (See Figure 1 and Figure 2.)

Step 6 If necessary, the signal passes through the APS connector to the front card. (See Figure 2.)

---

---

Note For AXSM, the front card monitors only one of the receive lines. For AXSM/B, the front card monitors both the receive lines.

---

Figure 1 shows an example of how this process operates in a standard APS configuration, where the primary card monitors the working line and the secondary card monitors the protection line.

Figure 2 shows an example of how the APS communication process operates in a crossed APS configuration, where the secondary card monitors the working line that is attached to the primary card, and the primary card monitors the protection line that is connected to the secondary card.

Figure 1

Standard APS Configuration

Figure 2

Crossed APS Configuration

Line failures are always detected at the receive end of the line. This is where a switchover occurs when a failure is detected. Two different types of switchovers can occur, depending on whether the APS was configured as unidirectional or bidirectional in the cnfapsln command:

•When a failure occurs on a line configured for unidirectional switching, the switch changes lines at the receive end only. A switchover is not necessary at the transmit end because the transmitting back cards send signals on both lines in the 1 +1 APS configuration.

•When a failure occurs on a line configured for bidirectional switching, a switchover occurs at both ends of the line.

If the status of the standby line is good, a switchover from the failed active line to the standby is automatic.

Enter the cnfapsln command to enable an automatic switchover back to the working line after it recovers from a failure, as shown in the following example:

M8xx0_LA.1.AXSM.a > cnfapsln -w 1.1.1 -rv 2

Table 17 describes the configurable parameters for the cnfapsln command.

Table 17 cnfapsln Command Parameters 

-w <working line>	Slot number, bay number, and line number of the active line to configure, in the format: slot.bay.line Example: -w 1.1.1
-sf <signal fault ber>	A number between 3 and 5 indicating the Signal Fault Bit Error Rate (BER), in powers of ten: •3 = 10-3 •4 = 10-4 •5 = 10-5 Example: -sf 3
-sd <SignalDegradeBER>	A power if 10 in the range 5-9 that indicates the Signal Degrade Bit Error Rate (BER): •5 = 10-5 •6 = 10-6 •7 = 10-7 •8 = 10-8 •9 = 10-9 Example: -sd 5
-wtr <Wait To Restore>	The number of minutes to wait after the failed working line has recovered, before switching back to the working line. The range is 5-12. Example: -wtr 5
-dr <direction>	Determines whether the line is unidirectional or bidirectional. •1 = Unidirectional. The line switch occurs at the receive end of the line. •2 = Bidirectional. The line switch occurs at both ends of the line. Note This optional parameter is not shown in the above example because you do not need to set it for a revertive line. Example: -dr 2
-rv <revertive>	Determines whether the line is revertive or non-revertive. •1 = Non-revertive. You must manually switch back to a recovered working line. •2 = Revertive. APS automatically switches back to a recovered working line after the number of minutes set in the -wtr parameter. Example: -rv 1

If you want to manually switch from one line to another, enter the switchapsln <bay> <line> <switchOption> command, as shown in the following example:

M8xx0_node.1.AXSM.a > switchapsln 1 1 6

Manual line switch from protection to working succeeded on line 1.1.1

Table 18 describes the configurable parameters for the cnfapsln command.

Table 18 switchapsln Command Parameters 

Parameter	Description
bay	The working bay number to switch.
line	The working line number to switch.
switchOption	The method of performing the switchover. •1 = Clear previous user switchover requests. Return to working line only if the mode is revertive. •2 = Lockout of protection. Prevents specified APS pair from being switched over to the protection line. If the protection line is already active, the switchover is made back to the working line. •3 = Forced working to protection line switchover. If the working line is active, the switchover is made to the protection line unless the protection line is locked out or in the SF Conditions, or if a forced switchover is already in effect. •4 = Forced protection to working line switchover. If the protection line is active, the switch is made to the working line unless a request of equal or higher priority is in effect. This option has the same priority as option 3 (forced working to protection line switchover). Therefor, if a forced working to protection line switchover is in effect, it must be cleared before this option (forced protection to working line switchover) can succeed. •5 = Manual switchover from working to protection line unless a request of equal or higher priority is in effect. •6 = Manual switchover from protection to working line. This option is only available in the 1+1 APS architecture.
service switch	This is an optional parameter. When set to 1, this field causes all APS lines to switch to their protected lines.

Enter the dspapslns command to verify that the active line switched over from the protection line to the working line, as shown in the following example:

M8xx0_node.1.AXSM.a > dspapslns

Working Prot.  Conf  Oper    Active  WLine PLine WTR   Revt Conf Oper LastUser

Index   Index  Arch  Arch    Line    State State (min)      Dir  Dir  SwitchReq

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

  1.1.1  2.1.1 1+1    1+1    working    OK    OK     5  Yes   bi   bi ManualP->W

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 AXSMB 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 19 to help you determine which APS line is not functioning properly.

---

Note Table 19 is updated for Release 3.0.00.

---

Table 19 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 20 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 20 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 20 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, and Cisco MGX 8830 Software Configuration Guide, Release 4, part OL-3845-01.

Upgrade Information

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

Upgrade Limitations

When connections are built on an AXSM_B card with software version 2.1(80) and the card is replaced with a regular AXSM, the connections remain OK. When this node is upgraded to Release 3.0.10, the card will go into a mismatch state indicating that the reserved card is an AXSM_B. See anomaly CSCdz72564 for details.

Frame Discard

---

Note An important caveat exists for virtual path connections (VPCs) that were added with frame discard enabled before version 3.0.23 or 4.0.10. The switch lets you enable frame discard on a VPC, even though hardware does not support it. If a VPC with frame discard enabled already existed on the node when you upgrade to release 3.0.23, 4.0.10, or later, you cannot subsequently modify the VPC unless you delete it, then re-add it with frame discard disabled. To avoid the need to delete a VPC, disable frame discard on any such VPCs before you upgrade to MGX releases 3.0.23, 4.0.10, or later.

---

The order of software releases was as follows:

•MGX 4.0.00 April 2003

•MGX 3.0.23 May 2003

•MGX 4.0.10 August 2003

•MGX 4.0.11 October 2003

•MGX 4.0.12 October 2003

•MGX 3.0.25 December 2003

Documentation

Please note the following important information about release notes and technical manuals.

Changes to this Document

Table 21 describes changes made to these release notes that caused the release notes to go from OL-4940-01 Rev. A0, September 30, 2003 to OL-4940-01 Rev. B0 on January 21, 2004.

Table 21 Changes that Caused Revision B of this Document

Section	Change
Frame Discard Feature	Describes changes in the behavior of the Frame Discard feature from Releases 3.0.23 to 4.0.12.
Frame Discard	A Note describes an important caveat for virtual path connections (VPCs) that were added with frame discard enabled before releases 3.0.23 or 4.0.10.

Notes

•The technical documentation that supports this release may include descriptions of features not implemented as of this printing.

•Starting in May 2003, the documents listed in the "Related Documentation" section will be available online only. Release Notes became available online only for our June 2002 release. Refer to the "How to Find Multiservice Switch Customer Documents Online" section for notes on how to locate documents online.

•A new manual, MGX and SES Error Messages, Release 4, became available as this release note went into production. This manual is for network operators. The manual describes error messages on the MGX 8850 (PXM45), MGX 8850 (PXM1E), MGX 8950, MGX 8830, and Service Expansion Shelf (SES), and suggests possible corrective actions. This manual is part number OL-4290-01.

Related Documentation

This "Related Documentation" section describes the technical manuals and release notes listed in the "Guide to Cisco Multiservice Switch Documentation." That guide, part DOC-7815358=, shipped with your product.

The following Cisco publications contain information related to the operation of this product and associated equipment in a Cisco WAN switching network.

Cisco WAN Manager Release 12

Table 22 lists the product documentation for the Cisco WAN Manager (CWM) network management system for Release 12.

Table 22 Cisco WAN Manager Release 12 Documentation 

Title	Description
Cisco WAN Manager Installation Guide for Solaris 8, Release 12 OL-3837-01	Provides procedures for installing Release 12 of the CWM network management system and Release 5.4 of CiscoView on a Solaris 8 platform.
Cisco WAN Manager User's Guide, Release 12 OL-3838-01	Describes how to use the CWM Release 12 software, which consists of user applications and tools for network management, connection management, network configuration, statistics collection, and security management.
Cisco WAN Manager SNMP Service Agent Guide, Release 12 OL-3840-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 using SNMP.
Cisco WAN Manager Database Interface Guide, Release 12 OL-3839-01	Provides information about accessing the CWM Informix OnLine database that is used to store information about the network elements.

Cisco MGX 8850 (PXM45) Multiservice Switch Release 4

Table 23 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM45) Multiservice Switch Release 4.

Table 23 Cisco MGX 8850 (PXM45) Release 4 Documentation 

Title	Description
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide OL-3842-01	Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation 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 8950 supports only serial bus based service modules. This hardware installation guide replaces all previous hardware guides for these switches.
Frame Relay Software Configuration Guide and Command Reference for the Cisco MGX 8850 FRSM12 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.
Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches, Release 4 OL-3852-01	Explains how to configure the AXSM cards and 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 MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4 OL-3845-01	Describes how to configure the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches with PXM45 or PXM1E controller cards to operate as ATM core switches or edge switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 4 OL-3846-01	Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.
Cisco Circuit Emulation Software Configuration Guide and Command Reference, Release 4 OL-3853-01	Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides descriptions for all CESM commands.
PNNI Network Planning Guide for MGX and SES Products OL-3847-01	Provides guidelines for planning a PNNI network that uses Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), Cisco MGX 8950, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 OL-3186-01	Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 (PXM45) and MGX 8950 Release 4 switch. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.
Cisco VISM Installation and Configuration Guide, Release 3* OL-2521-01	Describes how to install and configure the Voice Interworking Service Module (VISM) in the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Release 4 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.
Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches. * DOC-7814790=	Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.
* This book was last updated for Release 3.

Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4

Table 24 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4.

Table 24 Cisco MGX 8850 (PXM1E) Release 4 Documentation 

Title	Description
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide OL-3842-01	Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation 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 8950 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, and Cisco MGX 8830 Software Configuration Guide, Release 4 OL-3845-01	Describes how to configure the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches with PXM45 or PXM1E controller cards to operate as ATM core switches or edge switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 4 OL-3846-01	Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.
Cisco Circuit Emulation Software Configuration Guide and Command Reference, Release 4 OL-3853-01	Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides descriptions for all CESM commands.
Cisco Frame Relay Software Configuration Guide and Command Reference, Release 4 OL-3851-01	Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides descriptions for all FRSM commands.
Cisco AUSM Software Configuration Guide and Command Reference for Cisco MGX 8850 (PXM1E) and Cisco MGX 8830, Release 3* DOC-7814254=	Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides descriptions for all AUSM commands.
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, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.
Cisco VISM Installation and Configuration Guide, Release 3* OL-2521-01	Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Release 4 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.
Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches. * DOC-7814790=	Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.
* This book was last updated for Release 3.

Cisco MGX 8950 Multiservice Service Release 4

Table 25 lists the product documentation for the installation and operation of the Cisco MGX 8950 Multiservice Switch Release 4.

Table 25 Cisco MGX 8950 Release 4 Documentation 

Title	Description
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide OL-3842-01	Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation 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 8950 supports only serial us based service modules. This hardware installation guide replaces all previous hardware guides for these switches.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Configuration Guide, Release 4 OL-3845-01	Describes how to configure the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches with PXM45 or PXM1E controller cards to operate as ATM core switches or edge switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 4 OL-3846-01	Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.
Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches, Release 4 OL-3852-01	This guide explains how to configure the AXSM cards and 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.
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, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.
Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4 OL-3186-01	Describes how to install and configure the Cisco MGX Route Processor Module (RPM-XF) in the Cisco MGX 8850 Release 4 switch. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and basic Cisco IOS configuration information.
Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches. * DOC-7814790=	Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.
* This book was last updated for Release 3.

SES PNNI Release 4

Table 26 lists product documentation for understanding, installing, and operating the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller.

Table 26 SES PNNI Controller Release 4 Documentation 

Title	Description
Cisco SES PNNI Controller Software Configuration Guide, Release 3* DOC-7814258=	Describes how to configure, operate, and maintain the SES PNNI Controller.
Cisco SES PNNI Controller Command Reference, Release 3* DOC-7814260=	Provides a description of the commands used to configure and operate the SES PNNI Controller.
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, and Cisco BPX 8600 switches. 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.
* Last updated for Release 3 ** Last updated for Release 1

Cisco MGX 8830 Multiservice Switch Release 4

Table 27 lists the product documentation for the installation and operation of the Cisco MGX 8830 Multiservice Switch Release 4.

Table 27 Cisco MGX 8830 Release 4 Documentation 

Title	Description
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide OL-3842-01	Describes how to install the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches. This documentation 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 8950 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, and Cisco MGX 8830 Software Configuration Guide, Release 4 OL-3845-01	Describes how to configure the Cisco MGX 8950, the Cisco MGX 8850 (PXM1E/PXM45), and the Cisco MGX 8830 switches with PXM45 or PXM1E controller cards to operate as ATM core switches or edge switches. This guide also provides some operation and maintenance procedures.
Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Command Reference, Release 4 OL-3846-01	Describes the PXM commands that are available on the CLI of the Cisco MGX 8830, Cisco MGX 8850, and Cisco MGX 8950 switches.
Cisco Circuit Emulation Software Configuration Guide and Command Reference, Release 4 OL-3853-01	Provides software configuration procedures for provisioning connections and managing the CESM cards supported in this release. Also provides descriptions for all CESM commands.
Cisco Frame Relay Software Configuration Guide and Command Reference, Release 4 OL-3851-01	Provides software configuration procedures for provisioning connections and managing the FRSM cards supported in this release. Also provides descriptions for all FRSM commands.
Cisco AUSM Software Configuration Guide and Command Reference for MGX 8850 (PXM1E) and MGX 8830, Release 3*DOC-7814254=	Provides software configuration procedures for provisioning connections and managing the AUSM cards supported in this release. Also provides descriptions for all AUSM commands.
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, and Cisco BPX 8600 switches. When connected to a PNNI network, each Cisco BPX 8600 series switch requires an SES for PNNI route processing.
Cisco VISM Installation and Configuration Guide, Release 3* OL-2521-01	Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 Release 4 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.
Regulatory Compliance and Safety Information for the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Switches.* DOC-7814790=	Provides regulatory compliance, product warnings, and safety recommendations for the Cisco MGX 8830, Cisco MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 switches.
* This book was last updated for Release 3.

Cisco WAN Switching Software Release 9.4

Table 28 lists the product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.4.

Table 28 Cisco WAN Switching Release 9.4 Documentation 

Title	Description
9.4.00 Version Software Release Notes Cisco WAN Switching System Software OL-3189-01	Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
Cisco BPX 8600 Series Installation and Configuration, Release 9.3.30 DOC-7812907=	Provides a general description and technical details of the Cisco BPX broadband switch.
Cisco WAN Switching Command Reference, Release 9.3.30 DOC-7812906=	Provides detailed information on the general command line interface commands.
Cisco IGX 8400 Series Installation Guide OL-1165-05	Provides hardware installation and basic configuration information for Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.
Cisco IGX 8400 Series Provisioning Guide OL-1166-03	Provides information for configuration and provisioning of selected services for the Cisco IGX 8400 Series switches that are running Switch Software Release 9.3.30 or later.
Cisco IGX 8400 Series Regulatory Compliance and Safety Information DOC-7813227=	Provides regulatory compliance, product warnings, and safety recommendations for the Cisco IGX 8400 Series switch.

MGX 8850 (PXM1) Edge Concentrator Release 1.2.20

---

Note The Release 1.x books have not been updated recently. Please check the Release Notes for the latest information.

---

Table 29 lists the product documentation for the installation and operation of the Cisco MGX 8850 Edge Concentrator.

Table 29 MGX 8850 Edge Concentrator Release 1.2.20 Documentation 

Title	Description
Release Notes for Cisco WAN MGX 8850 (PXM1), MGX 8250, and MGX 8230 Software Version 1.2.20 OL-3244-01	Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
Cisco MGX 8850 Edge Concentrator Installation and Configuration, Release 1.1.3 DOC-7811223=	Provides installation instructions for the Cisco MGX 8850 edge concentrator.
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 edge concentrator.
Cisco MGX 8800 Series Switch System Error Messages, Release 1.1.3 DOC-7811240=	Provides error message descriptions and recovery procedures.
Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3 OL-1154-01	Provides a technical description of the system components and functionality of the Cisco MGX 8850 edge concentrator from a technical perspective.
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 DOC-7812278=	Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B and RPM-PR) in the Cisco MGX 8850, 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 VISM Installation and Configuration Guide, Release 3 OL-2521-01	Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

MGX 8250 Edge Concentrator Release 1.2.20

Table 30 lists the product documentation for the installation and operation of the Cisco MGX 8250 Edge Concentrator.

Table 30 MGX 8250 Multiservice Gateway Documentation 

Title	Description
Release Notes for Cisco WAN MGX 8850 (PXM1), MGX 8250, and MGX 8230 Software Version 1.2.20 OL-3244-01	Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
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 Multiservice Gateway Command Reference, Release 1.1.3 DOC-7811212=	Provides detailed information on the general command line interface commands.
Cisco MGX 8250 Multiservice Gateway Error Messages, Release 1.1.3 DOC-7811216=	Provides error message descriptions and recovery procedures.
Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3 DOC-7811576=	Describes the system components and functionality of the Cisco MGX 8250 Edge Concentrator from a technical perspective.
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 DOC-7812278=	Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B and RPM-PR) in the Cisco MGX 8850, 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 VISM Installation and Configuration Guide, Release 3 OL-2521-01	Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

MGX 8230 Edge Concentrator Release 1.2.20

Table 31 lists the product documentation for the installation and operation of the Cisco MGX 8230 Edge Concentrator.

Table 31 MGX 8230 Edge Concentrator Documentation 

Title	Description
Release Notes for Cisco WAN MGX 8850 (PXM1), MGX 8250, and MGX 8230 Software Version 1.2.20 OL-3244-01	Provides new feature, upgrade, and compatibility information, as well as known and resolved anomalies.
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 Multiservice Gateway Command Reference, Release 1.1.3 DOC-7811211=	Provides detailed information on the general command line interface commands.
Cisco MGX 8230 Multiservice Gateway Error Messages, Release 1.1.3 DOC-78112113=	Provides error message descriptions and recovery procedures.
Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3 DOC-7812899=	Provides a technical description of the system components and functionality of the Cisco MGX 8250 Edge Concentrator from a technical perspective.
Cisco MGX Route Processor Module Installation and Configuration Guide, Release 1.1 DOC-7812278=	Describes how to install and configure the Cisco MGX Route Processor Module (RPM/B and RPM-PR) in the Cisco MGX 8850, 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 VISM Installation and Configuration Guide, Release 3 OL-2521-01	Describes how to install and configure VISM in the Cisco MGX 8850, Cisco MGX 8250, and Cisco MGX 8230 switches. Also provides site preparation procedures, troubleshooting procedures, maintenance procedures, cable and connector specifications, and Cisco CLI configuration information.

How to Find Multiservice Switch Customer Documents Online

There are several ways you can find Multiservice Switch customer documents online.

If the Part Number is Known

Use the following procedure if you know or can find the document's part number.

---

---

Step 1 Obtain the document's part number from the "Guide to Multiservice Switch Documentation" that shipped with your product, or from the "Related Documentation" section in this Preface.

Step 2 In your browser's URL field, type www.cisco.com.

Step 3 In the top right search field, enter the document part number (for example, OL-3842-01) and click on GO.

---

If the Part Number is Not Known

Use the following procedures if you do not know or cannot find the document's part number.

Finding Cisco WAN Manager Documents

To find Cisco WAN Manager customer documents online:

---

---

Step 1 In your browser's URL field, type http://www.cisco.com/univercd/cc/td/doc/product/rtrmgmt/cwm.

Step 2 Look for the CWM release number.

---

Finding Multiservice Switch Documents

To find Multiservice Switch customer documents online:

---

---

Step 1 In your browser's URL field, type http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm.

Step 2 Look for the switch name, then release number (for example, MGX 8850 (PXM1E), then Release 4).

Ordering Documentation

---

Note Starting in April 2003, the documents listed in the "Related Documentation" section will be available online only. To access these documents online, refer to the "How to Find Multiservice Switch Customer Documents Online" section.

---

Other Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order printed Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Some printed documentation is offered through the "Printed Information Ordering" site, which can be accessed through:

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

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

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

•Non-registered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

Documentation on the World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

•http://www.cisco.com (for example, http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm)

•http://www-china.cisco.com

•http://www-europe.cisco.com

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or as an annual subscription as mentioned above.

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn: Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

---

Note To register for Cisco.com, go to http://www.cisco.com/register/

---

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

Caveats

This section provides information about known anomalies.

MGX 8850, MGX 8830, and MGX 8950 4.0.11 Anomalies

Anomalies are organized as follows:

•Known Anomalies in Release 4.0.11

•Anomalies Resolved in Release 4.0.11

•Anomalies Status Change from Previous Release 4.0.10.

Known Anomalies in Release 4.0.11

Table 32 Known Anomalies in Release 4.0.11 

Anomaly	Description
CSCdx62800	Symptoms: MGX45 CLI Reference Manual needs to be updated. Conditions: 4 new commands missing out of the manual. Workaround: None. Headline: CLI: dspmempart, and memshow are not documented in the MGX45 Hardware: PXM45/B
CSCdy23797	Symptom: pntrace commands not completely documented Conditions: MGX CLI Manual vs. the troubleshooting guide. Workaround: None. Headline: Either CLI manual or TSG needs to be update with pntrace commands Hardware: PXM45/B
CSCdy49757	Symptom: AUSM channel, port and SAR counters do not correctly count RM cells received from CPE Conditions: The AUSM channel, port and SAR counters do not correctly handle RM cells when they are generated by the CPE (test-set). When RM cells are received by the AUSM card the baseline behavior is that they should be discarded by the UNI port. Indeed that is what is noted to happen for AUSM on pxm1e. The command dspconload" shows that no traffic is received from the AUSM when a stream of RM cells at 480 cps is generated by the test-set: Workaround: None Headline: ausm channel,port,sar counters do not correctly count rm cells Hardware: ausm-8t1e1
CSCdy59294	Symptom: AUSM/PXM1E transmits invalid PTI=7 cells into network but cannot pass traffic out of far-end AUSM port. Conditions: An abr1 PVC was provisioned between two AUSM-IMA ports: [Test Set A] <---> node1 to node2 <---> [Test Set B] Test set A generated 480 CPS of ATM cells with the PTI field set to 7 (invalid). The payload consisted of 48 byte 6A pattern. The channel, port and SAR counters on node1 indicate that traffic is being sent into the network. On the PXM1E card on node1 the "dspconload" command indicates that all the PTI=7 traffic is sent out the trunk interface. In fact there seems to be RM cell overhead in both directions. The "dspconload" command on node1 indicates that all PTI=7 traffic is being received on the trunk interface. However on the AUSM port on node2 the chan, port and SAR counters all remain at zero. It is very strange that the AUSM card handles PTI=7 cells differently on the Ingress and Egress directions. At one time the PVC was able to transmit PTI=7 cells end to end but it has only been observed to happen once. Workaround: None Headline: AUSM/PXM1e transmits invalid PTI=7 cell, but FE cant see traffic Hardware: ausm-8t1e1
CSCdy78398	Symptom: SAR errors not detected by SCM for 3 minutes. Conditions: Tests consisting of SAR single bit errors were executed on active and standby AXSM cards. Workaround: None Headline: HFIT:SCM polling takes 3 min to detect SAR errors Hardware: axsm1b_oc3
CSCdy82219	Symptom: PNNI ports go into provisioning mode and spvcs fail when fault on active card or card switchover allowed to standby card with fault. Conditions: Utopic 2 Bus CBC to ATMIZER bit tx/rx errors inserted on active or standby cards Workaround: None Headline: HFIT:Utopic 2 Bus CBC to ATMIZER tx/rx bit errors test cases Hardware: axsm1b_oc3
CSCdy86511	Symptom: The AXSM reset due to a software error. The error information is corrupted. Conditions: Node running 2.1(80) software release. Workaround: None Headline: AXSME reset due to error / error information corrupted Hardware: AXSM-E
CSCdz04750	Symptom: The FRSM8 card does not correctly process incoming Frames with incorrect CRC-16 Conditions: The FRSM8 card does not correctly process incoming Frames with incorrect Frame Check Sum sequence. The port should discard these "corrupt" frames under the port counter "RcvFramesDiscCRCError:". Instead the frames get sent into the network. Workaround: unknown Headline: frsm8 does not correctly process incoming frames with correct crc-16 Hardware: pxm1e
CSCdz08738	Symptom: After node rebuild PXM1E went into mismatch with LowerBackcRd Conditions: slot-7 was active and slot-8 was standby. A power off/on was done on the node. After the rebuild slot-7 was coming up as active and slot-8 was coming up as standby. When slot-7 became active it is observed that it is i mismatch with Lower Back Card. When slot-8 became standby there was a switchover so that slot-8 became active and slot-7 reset and came back up as standby. Workaround: None Headline: After node rebuild PXM1E went into mismatch with lowerBackcd Hardware: pxm1e
CSCdz40737	Symptom: dspcnfdiag is not updated after cnfdiagall command for SRM slot. Conditions: The display is not updated after "cnfdiagall" for slot 15,16,31 & 32 (SRM). After a new node was installed we issued the "cnfdiagall enable disable" command. The display does not update the status for SRM slots. Workaround: None Headline: dspcnfdiag is not updated after cnfdiagall command for SRM slot Hardware: pxm1e
CSCdz53209	Symptom: FRSM-2T3 cards came up without boot image. Conditions: New FRSM-2T3 cards were inserted in slot-13 and slot-14. Initially they came in "boot" state. At this time setrev was executed for slot-13 and 14. After setrev both cards came up as active without boot image. Workaround: Unknown Headline: FRSM-2t3 cards came up with out boot image Hardware: pxm1e
CSCdz67977	Symptoms: General error logs for humvee device for the error state change. Conditions: If Elt mismatch errors or other error happen, this could happen if there are some pnports and the communication between active PXM and AXSM's fail Workaround: None. Headline: HMM: Humvee should log more details and take actions on Humvee GenEr Hardware: axsm2
CSCdz78585	Symptom: PXM1E in failed state Conditions: Observed PXM-1E in slot-7 in Failed state with all port LEDs on the front panel glowing Amber and are static. The status LED is red and blinking. The node was upgraded to new release on Friday and the node was last seen in OK state on 01/11/2003 15:00GMT. Today's capture taken 01/13/2003 14:00 GMT shows PXM-1E in slot-7 in Failed state. Workaround: None Headline: PXM1E disk failed and card in failed state Hardware: pxm1e
CSCea08833	Symptom: AXIS appears as the shelf name causing a display error on MGX PXM1e. Conditions: When the customer performs a switchredcd or a resetcd on the FRSM2T3 Workaround: None Headline: Switch name changes to AXIS when doing switchredcd or resetcd. Hardware: pxm1e
CSCea29664	Symptom: Customer reports that on one MGX8850 switch, an AXSM-16-155 card in a particular slot is automatically removed from the shelf and then comes back in service. No manual or CLI intervention. The card is restored after about 2 minutes. This can happen a few times a day with periods of nearly a month with no problems. Card replacement already performed. Conditions: Normal operation for the switch. Workaround: None. Headline: AXSM reset and restore by itself Hardware: axsm
CSCea31637	Symptom: Loopback OAM got dropped at wire rate on AXSME, it will happen on the FRSM12, too. Conditions: SPVC provisioned btw FRSM12 and AXSM/AXSME, pump-in loopback OAM to the port of AXSM/AXSME which has connections with FRSM12 at DS3 rate. The OAM cell will get dropped. Workaround: This happens only in special cases. No workaround for the DS3 rate lpbk OAM drop. Headline: AXSME_8OC3 causing OAM managed pvcs to fail Hardware: frsm12
CSCea42088	Symptom: Can not modify the remote ICR value. Conditions: ABR XPVC connection between axsm-e & bxm. Workaround: None Headline: Need ability to modify the remote ICR for the abr service Hardware: AXSM-E
CSCea46779	Symptom: Hardware alarm reported on PXM45B Conditions: Unknown Workaround: Unknown Headline: PXM45B with broken Humvee-SAR interface Hardware:
CSCea51299	Symptom: AXSM in Yred configuration 1:1 have a strange behavior: StandBy fails becoming in Init/Boot/Empty status, traffic on the active is affected, a reset on the failed card affects the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1 Workaround: So far the work around experimented it's a reset via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appear in "mismatch" status. Need to delete the connection manually, a display of those connection will give back: "ERR: Connection does not exist on controller" Headline: Disk Failure caused active/standby AXSM in failed state Hardware: axsm1
CSCea55232	Symptom: Active card gets reboot then stuck Failed/Empty Resv Conditions: There are some activities such as addcon, dnport/upport Workaround: None Headline: REG4: axsmxg-ch gets cema errors during upport/dnport Hardware: AXSM-XG
CSCea59570	Symptom: Incorrect error message seen after command is executed. Conditions: After adding an APS line to the standby card when it is not in standby. Workaround: None Headline: Adding APS line when the stby card is not stby give wrong error mess Hardware: pxm1e
CSCea64363	Symptom: dspDevErr need to modify to show the device No. Conditions: dspDevErr and dspDevErrhist for CBC, Q1210 and doesn't shows which group of error related to which device No. i.e. in the display the first group of error is for device 1 or 2. Workaround: None Headline: dspDevErr need to be modified to show the device No. Hardware: pxm1e
CSCea64790	Symptom: AXSM in Yred 1:1 configuration has a strange behavior: standby card fails and goes into the Init/Boot/Empty status, traffic on the active card is affected, a reset on the failed card affects the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1. Workaround: Resetting via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appear in "mismatch" status. Need to delete the connections manually. A display of those connections will display the following message: "ERR: Connection does not exist on controller". Headline: Watchdog resets on AXSM observed Hardware: axsm1
CSCea64818	Symptom: Ingress policing not invoked on AXSM-E Conditions: Only occurs on VPC connections Workaround: We should pump data traffic on conn with non-zero VPI and VCI > 31 Headline: AXSM-E: Ingress policing does not work for VPC connections Hardware: AXSM-E
CSCea65034	Symptom: dspDevErr/dspDevhist doesn't work on stdby PXM. Conditions: 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 stdby PXM. Workaround: None Headline: dspDevErr/dspDevhist doesn't work on stdby PXM Hardware: pxm45
CSCea65791	Symptom: dumpconfigs command aborted with error message Conditions: When executing dumconfigs command with terminal option, the command doesn't run completely and aborted in between and show timeout error message. Workaround: None Headline: dumpconfigs command aborted with error message Hardware: pxm1e
CSCea71178	Symptom: axmxg-ch stays with path alarm on port 1.3 after few switchredcd Conditions: Switchredcd was executed Workaround: None Headline: REG4: after few switchredcd the AXSM-XG port 1.3 stuck path alm Hardware: AXSM-XG
CSCea72681	Symptom: AXSM in Yred configuration 1:1 have a strange behavior: StandBy fails in Init/Boot/Empty status, traffic on the active is affected, a reset on the failed card affect the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1 Workaround: So far the work around experimented it's a reset via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appears in "mismatch" status. Need to delete the connection manually, a display of those connection will give back: "ERR: Connection does not exist on controller" Headline: Need protection to ensure that SM don't generate files to fill disk Hardware: axsm1
CSCea80192	Symptom: Native PXM could not takeover the mastership. Native card was stuck in Init and non-native in failed state (reason: BRAM, DISK non-native (from dspcdhealth)) Conditions: A native and a non-native PXM are inserted into a node at the same time and the native card though native to the node is not native to the slot. (E.g., native card in slot 7 is now inserted in slot 8). Workaround: Remove the non-native PXM, the node takes a reset and the native card goes active. Once the native card is Active then the insertion of non-native PXM in the node shall not cause any problem. Headline: pxm which is native could not takeover the mastership Hardware: pxm1e
CSCea85655	Symptom: Standby PXM continuously reboots. Conditions: Do restoreallcnf on the node. Workaround: Remove the "C:/.clrdsk" file, if it is present. Headline: PXM stuck booting after restoreallcnf.clrdsk Hardware: PXM45/B
CSCea89340	Symptom: Line and Path error counters are incrementing but not accurate Conditions: None Workaround: None Headline: PM parameters counters on AXSME T3 are not accurate Hardware: AXSM-E
CSCea89455	Symptom: AXSM/E T3/E3 card reports offline failure Conditions: Full coverage off line diag was executed Workaround: None Headline: AXSM/E T3/E3 Offline diag failure Hardware: AXSM-E
CSCeb01897	Symptom: AXSM/B OC3 came up in empty/reserved state Conditions: Stress testing consisting of node rebuilds were being performed Workaround: Unknown Headline: AXSM/B-OC3 went into empty/res due to SHM_CDF_DISCOVER_TMR_POP Hardware: axsm1b_oc3
CSCeb03881	Symptom: CC to the card may fail after the active backcard is removed when the card to card APS is configured Conditions:1.Card to Card APS enabled 2. active backcard removal Workaround: Insert the backcard back. Headline: Backcard removal causes cc to card fail. Hardware: AXSM-XG
CSCeb05061	Symptom: Offline diag reports Atlas test failures on AXSM-E T3/E3 Conditions: Full coverage offline diag test was executed Workaround: Unknown Headline: AXSM-E T3/E3 fails full cov. off line diag - Atlas test Hardware: AXSM-E
CSCeb05910	Symptom: PM parameters on NBSM's are not accurate Conditions: PM parameters on NBSM's are not accurate Line layer error counters remain at zero. On the other hand, the Path layer counters such as CRC and CRC ES do not correctly reflect the count. Workaround: unknown Headline: PM parameters on NBSMs are not accurate Hardware: pxm1e
CSCeb06582	Headline: MPSM: abit alarm not propagated correctly for some CESM/MPSM-CES con Hardware: pxm1e
CSCeb15291
CSCeb17823	Symptom: Unreliable testdelay measurements Conditions: When tstdelay command is used to measure the Round trip delay. Variable round trip delays are observed between axsm/b or axsm/e endpoints to frsm endpoints on PXM1E. FRSM-8 cards implement the SAR function in software. The OAM cell processing has lower priority than moving the data. Depending on how busy the CPU is, when the SAR receives an OAM loopback cell the tstdelay can produce very long results. Workaround: None Headline: Unreliable tstdelay results for axsm/B/E <--> frsm Hardware: frsm-8t1e1
CSCeb19481	Symptom: Switch alarms reported against a slot on a chassis Conditions: Unknown Workaround: Unknown Headline: XBAR port and slot alarms reported against slot of a chassis Hardware:
CSCeb22068	Symptom:unable to cc to card Conditions: unable to cc to card Workaround: None Headline: Unable to cc to card Hardwar: pxm45b
CSCeb23240	Symptom: Multiple APS-SF-DECL msg posted to evtlog w/o SF BER clearing. Conditions: SF BER in Protection Line. Workaround: None Headline: multiple APS-SF-DECL msg posted to evtlog w/o SF (BER) clearing Hardware: axsm1b_oc3
CSCeb25477	Symptom: On AXSM-E dspchancnt, the display for "Cells discarded in qe" and "CLP0 discarded in qe" include the count of discarded RM cells in addition to user CLP0 cells discarded Conditions: None Workaround: None Headline: AXSME: dspchancnt, CLPO discarded should only show user data Hardware: AXSM-E
CSCeb27898	Symptoms: Hard-disk failed during normal operations. Conditions: Unknown. Workaround: None. Headline: Active standby PXM45 HD failed Hardware: PXM45/B
CSCeb29954	Symptom: Ima link failure doesn't reflect to the pnport resource. This will cause the connection routing issue on the ima links between the MGx2 and PXM1E and MGX2 and MGX2. Conditions: Ima link failure in the ima group. Workaround: On the link between MGX2 and PXM1E, make PXM1e the higher node id. Headline: Ima link failure does not reflect to the pnport resource Hardware: AXSM-E-ima
CSCeb31125	Symptom: Output of dsphotstandby shows both primary and secondary cards as active. Conditions: After doing runrev. Workaround: Unknown Headline: dsphotstandby command shows wrong info when runrev executed: frsm-vhs Hardware: pxm1e
CSCeb33176	Symptom: Active card resets by itself and switchover occurred Conditions: None Workaround: None Headline: AXSM-XG card reset because of hw_timer_TassiException Hardware: AXSM-XG
CSCeb34166	Symptom: If online diags is configured using the "cnfdiag" or "cnfdiagall" command, a subsequent "dspdiagcnf" command shows diagnostics enabled for Cell Bus Service modules, despite the fact the Online diagnostics are not supported on CBSM's. Conditions: The Cell Bus Service modules should be in Active or Standby state when the "cnfdiag" command is issued. Workaround: None. Headline: dspdiagcnf shows online diagnostics enabled by mistake on SM/PXM1E. Hardware: pxm1e
CSCeb34878	Headline: Warning needed when APS disabled on non-redundant PXM1E Hardware: pxm1e
CSCeb36107	Symptom: The Switch is a PXM45/B running 3.0.20 SWSW. Below is the error that scrolls the logs approximately every 10 minutes. The customer has two switches exhibiting the same errors in both switch logs. At the present time no side effects have been noticed and does not seem to effect service on the nodes running AXSM/B and FRSM12-T3 cards. 05A29023 06/11/2003-02:43:56 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1590 dropped 03A29450 06/11/2003-02:35:24 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1962 dropped 05A29022 06/11/2003-02:33:01 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1590 dropped 03A29449 06/11/2003-02:24:28 FIPC-5-LINKOUTERROR Conditions: Currently, both nodes have FRSM12-T3 cards and AXSM/B SM's. Also Redundant PXM45/B CC's. Workaround: NO known at this time. Headline: FIPC-5-LINKOUTERROR Repeated Log error Hardware: PXM45/B
CSCeb38023	Symptom: PXM coredumped with Reset from Shell reason Condition: switchcc was executed Workaround: Unknown Headline: switchcc caused Reset from Shell coredumps on PXM45C Hardware: PXM45/C
CSCeb38659	Symptom: On PXM45 node, the AINI port goes into vc failure. Conditions: Do a resetsys. Workaround: Do a dnpnport and uppnport. Headline: resetsys on PXM45 causes AINI port to vc failure Hardware: PXM45/B
CSCeb38926	Symptoms: Active PXM getting stuck in backup boot after restoreallcnf is done Conditions: restoreallcnf Workaround: Esc+Ctrl+X on the console will reset the card and will come up fine Headline: REG4+:MGX8850 node crashed after doing restoreallcnf, not healthy Hardware: PXM45/B
CSCeb40265	Symptom: clkfrequencythreshold has the option of 1-5 on xcnfln/cnfln on the HS2/B card does not specify the individual value Conditions: xcnfln shows the clkfrquencythreshold 1-5. It does not explain what are the values meant. It did not say what the value of selecting 1 and etc. Workaround: unknown Headline: xcnfln shows the clkfrquencythreshold 1-5. does not show what is mea Hardware: pxm1e
CSCeb40460	Symptom: Incorrect severity seen in CIC event list resulting from real device testing. Conditions: executed reset, switchredcd etc. commands on MGX 8850 to see the effect in CIC. Workaround: None Headline: CIC: AXSM_16OC3 card events being sent into CIC with incorrect severity. Hardware: pxm45
CSCeb45350	Symptom: APS fails to switchover to protection line. Conditions: Backcard of primary/working slot is pulled out. Workaround: None Headline: APS doesn't switch to Prot. when backcard of Working is pulled out Hardware: pxm1
CSCeb46725	Symptom: tCrdmp task logged a sev 3 event log message indicating proxy file protocol error Conditions: resetsys was executed ]Workaround: Unknown Headline: tCrdmp task logged Proxy file protocol error after node rebuild Hardware: AXSM-E
CSCeb48125	Symptom: The software component Hardware Monitor Module, does not reliably detect parity errors on Queueing Engine chip Conditions: This problem was noticed on MGX8850 AXSM-4-622/B card running the firmware version 3.0.(2.100) Workaround: None Headline: HMM and QE48 falsely detects parity error when enabled Hardware: axsm
CSCeb48332	Symptom: Event log messages for certain modules indicate LPID in hex instead of dec. Conditions: Modules such as IFM generate event log messages Workaround: Unknown Headline: LPID should be displayed in dec. not hex to be consistent with cli Hardware: PXM45/B
CSCeb48697	Symptom: dspcds shows UNKNOWN card type when card is in mismatch Conditions: When a slot or the lower bay of a slot is reserved for half height card and insert full height card _ AXSME _ to the s lot, dspcds shows mismatch but UNKNOWN card type. Workaround: use dspcd to see card type. Headline: dspcds shows cd type UNKNOWN when in Mismatch state Hardware: pxm45
CSCeb48731	Symptom: AXSM/B UNI port passes F5 Segment AIS cells to network. Conditions: F5 Segment AIS cells supplied to AXSM UNI port Workaround: Unknown Headline: AXSM/B UNI port passes F5 Segment AIS cell to network Hardware: axsm1b_oc3
CSCeb48739	Symptom: dspcd shows MISMATCH but no reserved type. Conditions: Lower bay reserved from FRSM-8T1 (half height card). Insert full height card - AXSME, dspcd shows mismatch but UNRESERVED. Workaround: dspcd <lower-bay-slot-number> and see if the lower-bay is reserved if so that is the reason for the full-height card to be in mis match. Headline: HARD: dspcd shows MISMATCH but no reserved type Hardware: pxm45
CSCeb49214	Symptom: VSI session messed up after reset redundant RPMXF. Condition: There were 1:N redundant ELSR RPMXFs in the MGX shelf. Reset active RPMXF, immediately reset standby twice, the VSI session messed up. Workaround: Reset Active PXM again. Headline: DE-LSNT:VSI session messaged up after reset redundant RPMXF cards Hardware: PXM45/B
CSCeb50108	Symptom: IOS IPC communication was sent to RPM-XF card on LCN 7. IOS IPC communication should use LCN 2. Conditions: None Workaround: None Headline: PXM45 sends ipc polling request on LCN 7 Hardware: PXM45/B
CSCeb50268	Symptom: DNR getting generated while SF/SD is outstanding Condition: APS int req gets overwritten while Doing a Forced Switch Clear Workaround: None Headline: After forced switch W->P, SFBER on W does not cause W->P switch Hardware: AXSM-E
CSCeb50419	Symptom: Trunk in minor alarm Conditions: The same trunk is clear on the switch and another CWM Workaround: None Headline: axsm-xg trunk in minor alarm Hardware: AXSM-XG
CSCeb51078	Symptom: dumpconfigs command aborted when there is a RPM card in the node. Conditions: when execute dumpconfig command to dump config on a file the command is aborted when it came in to slot 9, which is a RPM card. Workaround: unknown Headline: dumpconfigs command aborted when there is a RPM card in the node Hardware: pxm1e
CSCeb51081	Symptom: Can not pass traffic. Conditions: clrallcnf and re-add the same configuration. Happen very infrequently and hard to reproduce. Workaround: None. Headline: AXSM5 loss traffic without any alarm Hardware: AXSM-XG
CSCeb51323	Symptom: The active pxm1e card got reset by itself, and a switchover was observed Conditions: A switchcc has triggered a node hang, and has cleared itself, before this problem was observed. Workaround: None Headline: SRMEB: Stats manager caused Active PXM1E reset Hardware: pxm1e
CSCeb51696	Symptom: FRSM-8E1 (slot 18) card in fail state (corrupted flash) after issuing burnboot and immediately followed by a resetcd for slot 18. Conditions: Burnboot on CBSM or FRSM-VHS on MGX Node followed by resetcd immediately. Workaround: None. Headline: HARD: switchredcd and resetcd not blocked during burnboot on CBSM Hardware: pxm45
CSCeb51965	Symptom: Loss of node access via LAN/console, AXSM & RPM cards unable to boot up Conditions: Reset all SMs in a MGX8850 node and when they are coming up i.e. some are in INIT state, reset them again. Workaround: None Headline: LSNT: tQeTask & tDispatch Task hogging the CPU Hardware: PXM45/B
CSCeb52781	Symptom: Online diag for SRM or SRMEB-3T3 is enabled when "cnfdiagall enable enable <> <> <>" is executed Conditions: Online diag for SRM or SRMEB-3T3 is enabled when "cnfdiagall enable enable <> <> <>" is executed Workaround: None Headline: SRMEB:No ERR msg while enabling SRM/SRMEB-3T3 Online Diag Hardware: PXM45/B
CSCeb53735	Symptom: PXM switchover due to workQPanic:Kernel work Q overflow. Conditions: In fully loaded shelf with redundant PXM45 cards, slot8 was active and slot7 was standby. PXM switchover happened because Backcard for slot7 was found to be healthier than backcard for slot8. Workaround: Unknown. Headline: DE-LSNT:PXM switchover due to workQPanic: Kernel work Q overflow Hardware: pxm45
CSCeb55258	Symptom: When provisioning a CESM connection we had a failure with the error "connection does not exist in cPro db". The real cause of the failure was a lack of bandwidth on the feeder trunk up to the rev2 node. The error message MUST be changed to a relevant message. In the latest release of 4.0, we have fixed this error message to now say "Requested cell rate (lscr/lpcr/lmcr) is too high." This is still misleading to the customer. They would like the error message to say. "Requested cell rate (lscr/lpcr/lmcr) is unavailable" Conditions: Customer is running 3.0.10 SWSW on CWM 10.5.10Patch 3.2 Workaround: Headline: Misleading error message when provisioning and not enough bandwidth Hardware: pxm45
CSCeb55910	Symptom: CCMA logs IPC send fail messages Conditions: AXSM-E is in init state after going through a reset Workaround: Unknown Headline: CCMA-4-IPCSENDFAIL message logged for AXSM-E in init state Hardware: AXSM-E
CSCeb55991	Symptoms: In the log we see it switch from one clock source to another for no apparent reason in the log. MGX1.7.PXM.a > dsplog -mod CLK_ 07A48828 06/30/2003-19:24:55 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Primary Clock status Trap Send: Status: Locked 07A48827 06/30/2003-19:24:55 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 07A48735 06/30/2003-18:46:56 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Secondary Clock status Trap Send: Status: Locked 07A48734 06/30/2003-18:46:56 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Secondary clock. - 1 dropped 08S02972 06/26/2003-13:26:30 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 07A27728 06/26/2003-13:26:29 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Primary Clock status Trap Send: Status: Locked 07A27727 06/26/2003-13:26:29 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 08S02936 06/26/2003-04:33:21 CLK_-7-SWITCH_CLOCK_DO ----------------------------------------------- MGX1.7.PXM.a > dspclksrcs Primary clock type: bits t1 Primary clock source: 7.35 Primary clock status: ok Primary clock reason: locked Secondary clock type: bits t1 Secondary clock source: 7.36 Secondary clock status: ok Secondary clock reason: locked Active clock: primary source switchover mode: non-revertive --------------- Conditions: MGX PXM45B 3.0.20.100 Workaround: None Headline: Clock Source switching without any logged information Hardware: PXM45/B
CSCeb56175	Symptom: The feature checkin for shmping has a bug that it includes the pxm for ping. Hence, it will always return ok under the condition when the ping should have resulted a non ok result. Hence, under conditions like switchcc the symptom will be that the new active card is unhealthy and brings down the node but the old active cannot bootup. Condition: Standby pxm has an ATMizer level problem that disallows it to communicate with any SM (axsm BBSM). This will go undetected and on switchcc the old standby i.e. new active will be unable to take over as active and bring down the node. Workaround: Standby card will be taken out and the old active new standby should be rebooted. Headline: ShmPing should exclude pinging pxm peer Hardware: pxm45
CSCeb57805	Symptom: loadrev exception happens in cli cmd task Conditions: Executing tests using current development test software. Workaround: None Headline: loadrev exception happens in cli cmd task Hardware: pxm45b
CSCeb58207	Symptom: None of the BERT commands executed is not seen in the dsplog Conditions: All the BERT commands like cnfbert, delbert, dspbert are executed successfully. But the command is not displayed in the dsplog Workaround: unknown Headline: none of the bert commands executed is seen in the dsplog Hardware: pxm1e
CSCeb58227	Symptom: Conns are not derouted upon ILMI timeout when SLP is enable and deroute delay is configured. upon LOS the connections were derouted upon the ILMI timeout when the SLP was enabled and even we had deroute delay configured more then ILMI timers. That was as per function spec. But, in this release we are observing that the connections are derouted upon derouted delay timer is timeout when SLP is enabled and deroute delay is configured. As per ILMI standard, if the SLP is enabled then conns should be derouted when ILMI timeout. Workaround: unknown Headline: conns are not derouted upon ilmi timeout when slp is enabled and dero Hardware: pxm1e
CSCeb58599	Symptom: PXM45B logs diagnostic errors Conditions: Enable onlien/offline diagnostics Workaround: Unknown Headline: MPSM8-DT: PXM45 logs Diag Error when online diag is running on STBY Hardware: pxm45b
CSCeb58912	Symptom: PXM45C reroute rate slower than the expected rate of 350 calls/sec Conditions: During reroute of 30K connections in a 4-node n/w with 2 via nodes. Workaround: None Headline: PXM45C reroute performance < 350 calls/sec Hardware: PXM45/C
CSCeb60130	Symptom: loadrev on frsm with 1:n redundancy, after secondary comes up standby, remove primary nbsm card, secondary is still standby (as expected) now reset secondary nbsm, secondary nbsm in Failed-U state. Conditions: 1:n redundancy, loadrev state. Workaround: None. Headline: HARD: secondary nbsm fail due to reset sec without prim in loadrev Hardware: pxm45
CSCeb61384	Symptom: Unable to delete the PNNI node Conditions: Delete the lowest level and attempt to delete the next level. Workaround: None Headline: Unable to delete the logical node Hardware: PXM45/B
CSCeb61532	Symptom: Node went unreachable and found all T3's down through AXSMs in question, slots 9 and 10. Both cards reset more than once but unknown how many exactly. During at least the third self-reboot of card 10 it was pulled which restored the outage with 9 taking over and stabilizing. Card 10 was then reinserted and came up normally. Conditions: Normal network traffic with some network latency present. Workaround: Pulled card in constant reboot allowing other in pair to take over. This stabilized the condition Headline: MGX went unreachable with AXSMs in continuous reboot Hardware: axsm1
CSCeb61872	Symptom: entPhysicalSoftwareRev varbind empty in traps 60055 and 60056 Conditions: Intermittently occurs on PXM45, PXM1E nodes for RPM-PR slots Workaround: None Headline: sw rev varbind not available when trap 60056 sent for RPM Hardware: pxm1e
CSCeb63216	Symptom: dspclkalms does not reflect standby clock source 'reset' and 'inphase locking' conditions Conditions: External BITs cable from standby PXM was removed and reconnected Workaround: Unknown Headline: dspclkalms does not reflect stdby clk src in reset or in phase locki Hardware: PXM45/B
CSCeb63231	Symptom: bootchange configuration displays incorrect information Conditions: Modifications were made to the (e) field Workaround: Unknown Headline: bootchange displays incorrect info after changing (e) field Hardware: PXM45/B
CSCeb63658	Symptom: HMM had detected a SABRE parity error and reported MAJOR-NON-FATAL ERROR to SHM that reset the AXSM-E card. Conditions: HMM was running. This is a default setting Workaround: None Headline: Increase Sabre error threshold Hardware: AXSM-E
CSCeb64000	Symptom: switchcc loss exceeds 250ms Conditions: 1.No srm's are present in the node 2.a dax conn was added between AXSM16-oc3 and AUSMB-8E1 with a loop on ausm port and a traffic generator on the AXSM port. 3. Traffic is being pumped and loss over the switchcc duration was measured Workaround: None Headline: switchover loss around 630ms, >250ms Hardware: pxm45
CSCeb64863	Symptom: Certain cli command output exceeds the 80 char limit Conditions: None Workaround: None Headline: Policing of 80 char limit for certain cli commands Hardware: PXM45/B
CSCeb65427	Symptom: sometimes issuing the cli command with wrong option or parameter would cause the PXM to reset. Conditions: None Workaround: Headline: Printf Mutex semaphore getting locked Hardware: pxm1e
CSCeb67611	Symptom: No event logs found in dsplog for srme LINK commands Conditions: Addlink and dellink and observed dsplog Workaround: None Headline: SREMB: no event logs found for srme LINK commands Hardware: pxm1e
CSCeb67820	Symptom: After switchover there are spvc connections failed with last cause of no route to destination. dsppnni-svcc-rcc only show one entry. dsppnni-node-list shows in certain nodes Conditions: After switchover node of slot 8 shows static memory is low. there are 48k spvc connections failed due to no route to destination. in the node db, there are two entries with same node id. This causes the local node index to take a value other than 1. In that case, connections can not be routed. Workaround: Perform command switchcc. Headline: CIT50:node db contains two entries with same node id Hardware: pxm45b
CSCeb67843	Symptom: PnCcb hoges the cpu time on the node and idle time goes down to zero Connection fail with Cross Commit failure. Conditions: Could happen when the number of cons on AXSM go above 80K (depending on the VPI/VCI ranges used for the connections). Workaround: None Headline: Failed to add entry in QE48 Conn id table Hardware: axsm1
CSCeb67870	Symptom:SNMP Master Agent on MGX8850 (PXM45/B)went to idle state for approx 45 min Conditions: None Workaround: None Headline: snmp Master Agent went to idle state for approx 45 min Hardware: pxm45b
CSCeb68706	Symptom: Observed message 'file already closed' after runrev executed on FRSM in slot-2 Conditions: After doing a runrev on FRSM in slot-2 of emeapl36, observed a message pop up file already closed'. Following are the CP captures for the node: Workaround: unknown Headline: observed message file already closed after runrev executed on frsm Hardware: pxm1e
CSCeb69124	Symptom: Incremental files deleted slowly (one per hour) when standby is available. Conditions: Standby available Workaround: Use shellcon to delete incremental files Headline: Incremental files are deleted slowly when Standby is available Hardware: pxm45
CSCeb69414	Symptom: pnport of oc192 stays in down in progress for long time(1 min - 7 min) Conditions: Performed commands dnilmi and delpart on the AXSM-XG card. Workaround: None. Headline: Pnport of AXSM-XG oc192 card stay in down in prog for long time Hardware: AXSM-XG
CSCeb69793	Headline: FI: test-13:Hard disk failure: No trap upon fault Hardware: pxm1e
CSCeb70258	Symptom: Incorrect ifName string in trap 60373 Conditions: None Workaround: unknown Headline: Incorrect ifName string in the atm phy trap 60373 Hardware: AXSM-XG
CSCeb71360	Headline: Axsm resets due to Watchdog timeout with PXM running 3.0.23 Hardware: axsm1b_oc3
CSCeb71578
CSCeb76581
CSCeb77548
CSCeb79161	Symptom: Some connections do not get synced over to standby Conditions: Has never occurred in 4.0.x release. this is a defensive fix to protect against subsequent database upgrades. Workaround: None required. Upon switchover, the missed connections are recovered from the disk.
CSCeb80000	Symptom: connection doesn't deroute right away upon dnport with deroute delay on and secure link is disable. Conditions: connection doesn't deroute right away upon dnport with deroute delay on and secure link is disable. Workaround: unknown Headline: conn doesn't deroute right away upon dnport with deroute delay on an Hardware: pxm1e
CSCeb80600	Headline: corrupted stats on pxm1e -- cesm-t1e1 cards under corner configs Hardware: pxm1e
CSCeb81314
CSCeb82476	Symtom: 3 unknown alarms Conditions: customer upgrade software Workaround: revert the upgrade the alarms goes away. Headline: Minor cards alarms seen when upgrade to MGX PXM45/B 3.0(23) Hardware: PXM45/B
CSCeb82771	Symptom: Hard Drive backcard of PXM45B reported failure Condition: Offline diag was executed Workaround: Unknown Headline: HDD fails full coverage off line diag Hardware: PXM45/B
CSCeb83949	Symptom: The dsppnportcac and dsppnportrsrc command output exceeds the standard 80 character line limit. Conditions: Display the dsppnportcac or dsppnportrsrc command on an MGX or SES PXM. Workaround: Increase the terminal window to accommodate the display of a 92 character line. Headline: Policing of 80 char limit for dsppnportcac and dsppnportrsrc command 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 certain cli commands Hardware: axsme
CSCeb84307	Symptom: PXM resets Conditions: dsppnni-path aw nrtvbr cli command was executed Workaround: Unknown Headline: dsppnni-path aw nrtvbr command caused PXM reset Hardware: PXM45/B
CSCeb84390	Symptom: Rx Idle cell does not increment in dsplncnt or dspatmlayercnt Conditions: clear channel card only (AXSMXG_1_OC192 and AXSMXG_16_OC3) Workaround: None Headline: rx idle cell counter does not increment in dsplncnt Hardware: AXSM-XG
CSCeb85464	Symptom: Active PXM reset and coredumped Conditions: switchredcd was executed on one of the AXSM pairs in node Workaround: Unknown Headline: AXSM switchredcd caused PXM to reset and coredump Hardware: PXM45/B
CSCeb87513	Symptom: Pnni link between 2 PXM1E based MGX8850's goes down intermittently. These PXM1E's have IMA backcards. Output of the "dsppnni-link" command on one side shows that it is in "oneWayInside" hello state and the other is in the "attempt" state. Conditions: The PXM1E's are running 4.0(0.201) code. Workaround: Switchcc helps recover from this state. Headline: pnni link on a PXM1E with IMA backcard goes down without recovery Hardware: pxm1e-ima
CSCec02957	Symptom: After resetsys, there is one pnport remains in provisioning state. Conditions: In development network, there are 37 signalling interfaces, 117k+ p2p spvc connections, p2mp 1250 roots and 2060 parties in node. All connections are routed and ok. After commitrev then resetsys, observe there is one pnport remains in provisioning state. Workaround: None Headline: CIT50:port stuck in provisioning after commitrev and resetsys Hardware: axsm1b_oc3
CSCec04902	Symptom: After runrev or resetsys, the new rteopt values for 8 uni ports are shown the default values. Conditions: In development test network, there are 81(55 nni/26 uni) signalling interfaces, 48k p2p spvc connections, one PXM45/C in node. Configured and enabled rteopt for 8 uni ports, then upgrade pxm runtime image from 4.0.x release test image to future release test image. after runrev, those new rteopt values for 8 uni ports are shown default values. this problem happened not just after upgrade, it also happened after resetsys with current 4.0.x release test image. Workaround: None Headline:CIT50:redman donot read > 100 records for Disk_spvc_itf_db Hardware: PXM45/C
CSCec05278	Symptom: OAM CC is not reported failure sometimes. Conditions: disable cc and enable it again on one end of the connection. Workaround: Unknown. Headline: OAM cc is not working consistently as expected Hardware: axsm1
CSCec10933	Symptom: Sofware error reset caused by two tasks hangin on a semaphore Conditions: None Workaround: None Headline: Software Err Reset coredump caused by 2 tasks hanging on a semaphore Hardware: pxm45
CSCec11151	to NCDP clocking mode. Headline: UI-S3 not locked to proper reference after inband references switch Hardware: pxm1e
CSCec12108
CSCec12370
CSCec12428
CSCec12475
CSCec12609
CSCec14029
CSCec14733
CSCec15803
CSCec16527
CSCec18077
CSCec18423
CSCec20568
CSCec20587
CSCec22514
CSCec25929
CSCec29583
CSCec45095
CSCin46303	Symptom: invert_clock param always -1 in db line table for FRSM-HS2B-12IN1 card on 8850. Conditions: adding / configuring X21 or V35 lines. Workaround: None Headline: invert_clock param not updated in db for FRSM-HS2B-12IN1 card on 8850 Hardware: frsm-vhs
CSCin50435	Symptom:degraded x-bar msg after switchcc, causing failure. Conditions: pnni-ats env Workaround: Unknown. Headline: AUTO: degraded x-bar msg after switchcc, causing failure Hardware: all

Anomalies Resolved in Release 4.0.11

CSCeb47830 ssi exception error: snmpSA crash

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

CSCeb69978 workQPanic:HDD ISR cannot clear HDD interrupt due to PCI read failed

CSCeb88172 PXM45C keeps resetting after a switchcc

CSCeb83142 connection fails routing due to wrong util used at slave

CSCec07087 PXM1E: ATLAS HMM should report errors to SHM

Anomaly Status Change from Previous Release 4.0.10

Table 35 lists the anomalies status change from previous release of 4.0.10.

Table 33 MGX 8850 Release 4.0.11 Anomalies Status Change 

Bug ID	Description
CSCdz08738	After node rebuild PXM1E went into mismatch with lowerBackcd; Closed
CSCea55232	REG4: axsmxg-ch gets cema errors during upport/dnport; Unreproducible
CSCea71178	REG4: after few switchredcd the axsmxg port 1.3 stuck path alm; Unreproducible
CSCeb33176	AXSM-XG card reset because of hw_timer_TassiException; Unreproducible
CSCeb48731	AXSM/B UNI port passes F5 Segment AIS cell to network; Closed
CSCeb50419	axsm-xg trunk in minor alarm; Unreproducible
CSCeb58912	PXM45C reroute performance < 350 calls/sec; Closed
CSCeb61532	MGX went unreachable with AXSMs in continuous reboot; Closed
CSCeb63216	does not reflect stdby clk src in reset or in phase locki; Closed
CSCeb77548	if id is same for two different ports in FRSM12 card; Duplicated to CSCec05854
CSCeb84307	dsppnni-path aw nrtvbr command caused PXM reset; Duplicated to CSCea04529

MGX 8850, MGX 8830, and MGX 8950 4.0.10 Anomalies

Anomalies are organized as follows:

•Known Anomalies in Release 4.0.10

•Anomalies Resolved in Release 4.0.10

•Anomalies Status Change from Previous Release 4.0.00.

Known Anomalies in Release 4.0.10

Table 34 Known Anomalies in Release 4.0.10 

Anomaly	Description
CSCdx62800	Symptoms: MGX45 CLI Reference Manual needs to be updated. Conditions: 4 new commands missing out of the manual. Workaround: None. Headline: CLI: dspmempart, and memshow are not documented in the MGX45 Hardware: PXM45/B
CSCdy23797	Symptom: pntrace commands not completely documented Conditions: MGX CLI Manual vs. the troubleshooting guide. Workaround: None. Headline: Either CLI manual or TSG needs to be update with pntrace commands Hardware: PXM45/B
CSCdy49757	Symptom: AUSM channel, port and SAR counters do not correctly count RM cells received from CPE Conditions: The AUSM channel, port and SAR counters do not correctly handle RM cells when they are generated by the CPE (test-set). When RM cells are received by the AUSM card the baseline behavior is that they should be discarded by the UNI port. Indeed that is what is noted to happen for AUSM on pxm1e. The command dspconload" shows that no traffic is received from the AUSM when a stream of RM cells at 480 cps is generated by the test-set: Workaround: None Headline: ausm channel,port,sar counters do not correctly count rm cells Hardware: ausm-8t1e1
CSCdy59294	Symptom: AUSM/PXM1E transmits invalid PTI=7 cells into network but cannot pass traffic out of far-end AUSM port. Conditions: An abr1 PVC was provisioned between two AUSM-IMA ports: [Test Set A] <---> node1 to node2 <---> [Test Set B] Test set A generated 480 CPS of ATM cells with the PTI field set to 7 (invalid). The payload consisted of 48 byte 6A pattern. The channel, port and SAR counters on node1 indicate that traffic is being sent into the network. On the PXM1E card on node1 the "dspconload" command indicates that all the PTI=7 traffic is sent out the trunk interface. In fact there seems to be RM cell overhead in both directions. The "dspconload" command on node1 indicates that all PTI=7 traffic is being received on the trunk interface. However on the AUSM port on node2 the chan, port and SAR counters all remain at zero. It is very strange that the AUSM card handles PTI=7 cells differently on the Ingress and Egress directions. At one time the PVC was able to transmit PTI=7 cells end to end but it has only been observed to happen once. Workaround: None Headline: AUSM/PXM1e transmits invalid PTI=7 cell, but FE cant see traffic Hardware: ausm-8t1e1
CSCdy78398	Symptom: SAR errors not detected by SCM for 3 minutes. Conditions: Tests consisting of SAR single bit errors were executed on active and standby AXSM cards. Workaround: None Headline: HFIT:SCM polling takes 3 min to detect SAR errors Hardware: axsm1b_oc3
CSCdy82219	Symptom: PNNI ports go into provisioning mode and spvcs fail when fault on active card or card switchover allowed to standby card with fault. Conditions: Utopic 2 Bus CBC to ATMIZER bit tx/rx errors inserted on active or standby cards Workaround: None Headline: HFIT:Utopic 2 Bus CBC to ATMIZER tx/rx bit errors test cases Hardware: axsm1b_oc3
CSCdy86511	Symptom: The AXSM reset due to a software error. The error information is corrupted. Conditions: Node running 2.1(80) software release. Workaround: None Headline: AXSME reset due to error / error information corrupted Hardware: AXSM-E
CSCdz04750	Symptom: The FRSM8 card does not correctly process incoming Frames with incorrect CRC-16 Conditions: The FRSM8 card does not correctly process incoming Frames with incorrect Frame Check Sum sequence. The port should discard these "corrupt" frames under the port counter "RcvFramesDiscCRCError:". Instead the frames get sent into the network. Workaround: unknown Headline: frsm8 does not correctly process incoming frames with correct crc-16 Hardware: pxm1e
CSCdz08738	Symptom: After node rebuild PXM1E went into mismatch with LowerBackcRd Conditions: slot-7 was active and slot-8 was standby. A power off/on was done on the node. After the rebuild slot-7 was coming up as active and slot-8 was coming up as standby. When slot-7 became active it is observed that it is i mismatch with Lower Back Card. When slot-8 became standby there was a switchover so that slot-8 became active and slot-7 reset and came back up as standby. Workaround: None Headline: After node rebuild PXM1E went into mismatch with lowerBackcd Hardware: pxm1e
CSCdz40737	Symptom: dspcnfdiag is not updated after cnfdiagall command for SRM slot. Conditions: The display is not updated after "cnfdiagall" for slot 15,16,31 & 32 (SRM). After a new node was installed we issued the "cnfdiagall enable disable" command. The display does not update the status for SRM slots. Workaround: None Headline: dspcnfdiag is not updated after cnfdiagall command for SRM slot Hardware: pxm1e
CSCdz53209	Symptom: FRSM-2T3 cards came up without boot image. Conditions: New FRSM-2T3 cards were inserted in slot-13 and slot-14. Initially they came in "boot" state. At this time setrev was executed for slot-13 and 14. After setrev both cards came up as active without boot image. Workaround: Unknown Headline: FRSM-2t3 cards came up with out boot image Hardware: pxm1e
CSCdz67977	Symptoms: General error logs for humvee device for the error state change. Conditions: If Elt mismatch errors or other error happen, this could happen if there are some pnports and the communication between active PXM and AXSM's fail Workaround: None. Headline: HMM: Humvee should log more details and take actions on Humvee GenEr Hardware: axsm2
CSCdz78585	Symptom: PXM1E in failed state Conditions: Observed PXM-1E in slot-7 in Failed state with all port LEDs on the front panel glowing Amber and are static. The status LED is red and blinking. The node was upgraded to new release on Friday and the node was last seen in OK state on 01/11/2003 15:00GMT. Today's capture taken 01/13/2003 14:00 GMT shows PXM-1E in slot-7 in Failed state. Workaround: None Headline: PXM1E disk failed and card in failed state Hardware: pxm1e
CSCea08833	Symptom: AXIS appears as the shelf name causing a display error on MGX PXM1e. Conditions: When the customer performs a switchredcd or a resetcd on the FRSM2T3 Workaround: None Headline: Switch name changes to AXIS when doing switchredcd or resetcd. Hardware: pxm1e
CSCea29664	Symptom: Customer reports that on one MGX8850 switch, an AXSM-16-155 card in a particular slot is automatically removed from the shelf and then comes back in service. No manual or CLI intervention. The card is restored after about 2 minutes. This can happen a few times a day with periods of nearly a month with no problems. Card replacement already performed. Conditions: Normal operation for the switch. Workaround: None. Headline: AXSM reset and restore by itself Hardware: axsm
CSCea31637	Symptom: Loopback OAM got dropped at wire rate on AXSME, it will happen on the FRSM12, too. Conditions: SPVC provisioned btw FRSM12 and AXSM/AXSME, pump-in loopback OAM to the port of AXSM/AXSME which has connections with FRSM12 at DS3 rate. The OAM cell will get dropped. Workaround: This happens only in special cases. No workaround for the DS3 rate lpbk OAM drop. Headline: AXSME_8OC3 causing OAM managed pvcs to fail Hardware: frsm12
CSCea42088	Symptom: Can not modify the remote ICR value. Conditions: ABR XPVC connection between axsm-e & bxm. Workaround: None Headline: Need ability to modify the remote ICR for the abr service Hardware: AXSM-E
CSCea46779	Symptom: Hardware alarm reported on PXM45B Conditions: Unknown Workaround: Unknown Headline: PXM45B with broken Humvee-SAR interface Hardware:
CSCea51299	Symptom: AXSM in Yred configuration 1:1 have a strange behavior: StandBy fails becaming in Init/Boot/Empty status, traffic on the active is affected, a reset on the failed card affect the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1 Workaround: So far the work around experimented it's a reset via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appear in "mismatch" status. Need to delete the connection manually, a display of those connection will give back: "ERR: Connection does not exist on controller" Headline: Disk Failure caused active/standby AXSM in failed state Hardware: axsm1
CSCea55232	Symptom: Active card gets reboot then stuck Failed/Empty Resv Conditions: There are some activities such as addcon, dnport/upport Workaround: None Headline: REG4: axsmxg-ch gets cema errors during upport/dnport Hardware: AXSM-XG
CSCea59570	Symptom: Incorrect error message seen after command is executed. Conditions: After adding an APS line to the standby card when it is not in standby. Workaround: None Headline: Adding APS line when the stby card is not stby give wrong error mess Hardware: pxm1e
CSCea64363	Symptom: dspDevErr need to modify to show the device No. Conditions: dspDevErr and dspDevErrhist for CBC, Q1210 and doesn't shows which group of error related to which device No. i.e. in the display the first group of error is for device 1 or 2. Workaround: None Headline: dspDevErr need to be modified to show the device No. Hardware: pxm1e
CSCea64790	Symptom: AXSM in Yred 1:1 configuration has a strange behavior: standby card fails and goes into the Init/Boot/Empty status, traffic on the active card is affected, a reset on the failed card affects the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1. Workaround: Resetting via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appear in "mismatch" status. Need to delete the connections manually. A display of those connections will display the following message: "ERR: Connection does not exist on controller". Headline: Watchdog resets on AXSM observed Hardware: axsm1
CSCea64818	Symptom: Ingress policing not invoked on AXSM-E Conditions: Only occurs on VPC connections Workaround: We should pump data traffic on conn with non-zero VPI and VCI > 31 Headline: AXSM-E: Ingress policing does not work for VPC connections Hardware: AXSM-E
CSCea65034	Symptom: dspDevErr/dspDevhist doesn't work on stdby PXM. Conditions: 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 stdby PXM. Workaround: None Headline: dspDevErr/dspDevhist doesn't work on stdby PXM Hardware: pxm45
CSCea65791	Symptom: dumpconfigs command aborted with error message Conditions: When executing dumconfigs command with terminal option, the command doesn't run completely and aborted in between and show timeout error message. Workaround: None Headline: dumpconfigs command aborted with error message Hardware: pxm1e
CSCea71178	Symptom: axmxg-ch stays with path alarm on port 1.3 after few switchredcd Conditions: Switchredcd was executed Workaround: None Headline: REG4: after few switchredcd the axsmxg port 1.3 stuck path alm Hardware: AXSM-XG
CSCea72681	Symptom: AXSM in Yred configuration 1:1 have a strange behavior: StandBy fails in Init/Boot/Empty status, traffic on the active is affected, a reset on the failed card affect the active card too. The active card is not accessible via CC command, reply: "Err: redirection timed out" Conditions: System running code 3.0.20; Yred configuration on AXSM 1:1 Workaround: So far the work around experimented it's a reset via CLI on the "ACTIVE" card, it will restore both the cards but some ghost connections may appears in "mismatch" status. Need to delete the connection manually, a display of those connection will give back: "ERR: Connection does not exist on controller" Headline: Need protection to ensure that SM don't generate files to fill disk Hardware: axsm1
CSCea80192	Symptom: Native PXM could not takeover the mastership. Native card was stuck in Init and non-native in failed state (reason: BRAM, DISK non-native (from dspcdhealth)) Conditions: A native and a non-native PXM are inserted into a node at the same time and the native card though native to the node is not native to the slot. (E.g., native card in slot 7 is now inserted in slot 8). Workaround: Remove the non-native PXM, the node takes a reset and the native card goes active. Once the native card is Active then the insertion of non-native PXM in the node shall not cause any problem. Headline: pxm which is native could not takeover the mastership Hardware: pxm1e
CSCea85655	Symptom: Standby PXM continuously reboots. Conditions: Do restoreallcnf on the node. Workaround: Remove the "C:/.clrdsk" file, if it is present. Headline: PXM stuck booting after restoreallcnf.clrdsk Hardware: PXM45/B
CSCea89340	Symptom: Line and Path error counters are incrementing but not accurate Conditions: None Workaround: None Headline: PM parameters counters on AXSME T3 are not accurate Hardware: AXSM-E
CSCea89455	Symptom: AXSM/E T3/E3 card reports offline failure Conditions: Full coverage off line diag was executed Workaround: None Headline: AXSM/E T3/E3 Offline diag failure Hardware: AXSM-E
CSCeb01897	Symptom: AXSM/B OC3 came up in empty/reserved state Conditions: Stress testing consisting of node rebuilds were being performed Workaround: Unknown Headline: AXSM/B-OC3 went into empty/res due to SHM_CDF_DISCOVER_TMR_POP Hardware: axsm1b_oc3
CSCeb03881	Symptom: CC to the card may fail after the active backcard is removed when the card to card APS is configured Conditions:1.Card to Card APS enabled 2. active backcard removal Workaround: Insert the backcard back. Headline: Backcard removal causes cc to card fail. Hardware: AXSM-XG
CSCeb05061	Symptom: Offline diag reports Atlas test failures on AXSM-E T3/E3 Conditions: Full coverage offline diag test was executed Workaround: Unknown Headline: AXSM-E T3/E3 fails full cov. off line diag - Atlas test Hardware: AXSM-E
CSCeb05910	Symptom: PM parameters on NBSM's are not accurate Conditions: PM parameters on NBSM's are not accurate Line layer error counters remain at zero. On the other hand, the Path layer counters such as CRC and CRC ES do not correctly reflect the count. Workaround: unknown Headline: PM parameters on NBSMs are not accurate Hardware: pxm1e
CSCeb17823	Symptom: Unreliable testdelay measurements Conditions: When tstdelay command is used to measure the Round trip delay. Variable round trip delays are observed between axsm/b or axsm/e endpoints to frsm endpoints on PXM1E. FRSM-8 cards implement the SAR function in software. The OAM cell processing has lower priority than moving the data. Depending on how busy the CPU is, when the SAR receives an OAM loopback cell the tstdelay can produce very long results. Workaround: None Headline: Unreliable tstdelay results for axsm/B/E <--> frsm Hardware: frsm-8t1e1
CSCeb19481	Symptom: Switch alarms reported against a slot on a chassis Conditions: Unknown Workaround: Unknown Headline: XBAR port and slot alarms reported against slot of a chassis Hardware:
CSCeb23240	Symptom: Multiple APS-SF-DECL msg posted to evtlog w/o SF BER clearing. Conditions: SF BER in Protection Line. Workaround: None Headline: multiple APS-SF-DECL msg posted to evtlog w/o SF (BER) clearing Hardware: axsm1b_oc3
CSCeb25477	Symptom: On AXSM-E dspchancnt, the display for "Cells discarded in qe" and "CLP0 discarded in qe" include the count of discarded RM cells in addition to user CLP0 cells discarded Conditions: None Workaround: None Headline: AXSME: dspchancnt, CLPO discarded should only show user data Hardware: AXSM-E
CSCeb27898	Symptoms: Hard-disk failed during normal operations. Conditions: Unknown. Workaround: None. Headline: Active standby PXM45 HD failed Hardware: PXM45/B
CSCeb29954	Symptom: Ima link failure doesn't reflect to the pnport resource. This will cause the connection routing issue on the ima links between the MGx2 and PXM1E and MGX2 and MGX2. Conditions: Ima link failure in the ima group. Workaround: On the link between MGX2 and PXM1E, make PXM1e the higher node id. Headline: Ima link failure does not reflect to the pnport resource Hardware: AXSM-E-ima
CSCeb31125	Symptom: Output of dsphotstandby shows both primary and secondary cards as active. Conditions: After doing runrev. Workaround: Unknown Headline: dsphotstandby command shows wrong info when runrev executed: frsm-vhs Hardware: pxm1e
CSCeb33176	Symptom: Active card resets by itself and switchover occurred Conditions: None Workaround: None Headline: AXSM-XG card reset because of hw_timer_TassiException Hardware: AXSM-XG
CSCeb34734	Symptom: Generated card events in CIC. Conditions: Multi-system installation of CIC Workaround: None Headline: CIC: resetcd on AXSM_16OC3 (MGX 8850) does not create alarm in CIC. Hardware: pxm45
CSCeb35363	Symptom: pnport becomes 'enablenotup' when delay of 249ms induced on one link of the IMA group, causing all user traffic to re-route despite VPC / IMA trunk in active state on the AUSM card for that trunk. The delay later reduced to 50ms but pnport does not recover. Conditions: pnport becomes 'enablenotup' when delay of 249ms induced on one link of the IMA group. Workaround: None Headline: increasing delay on IMA causes pnport to go into enablenotup state Hardware: ausm-8t1e1
CSCeb36107	Symptom: The Switch is a PXM45/B running 3.0.20 SWSW. Below is the error that scrolls the logs approximately every 10 minutes. The customer has two switches exhibiting the same errors in both switch logs. At the present time no side effects have been noticed and does not seem to effect service on the nodes running AXSM/B and FRSM12-T3 cards. 05A29023 06/11/2003-02:43:56 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1590 dropped 03A29450 06/11/2003-02:35:24 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1962 dropped 05A29022 06/11/2003-02:33:01 FIPC-5-LINKOUTERROR ISR ssi_ipc_remote_msg_send FIPC Link snd error 20651; Expected 11, Got 0 - 1590 dropped 03A29449 06/11/2003-02:24:28 FIPC-5-LINKOUTERROR Conditions: Currently, both nodes have FRSM12-T3 cards and AXSM/B SM's. Also Redundant PXM45/B CC's. Workaround: NO known at this time. Headline: FIPC-5-LINKOUTERROR Repeated Log error Hardware: PXM45/B
CSCeb38023	Symptom: PXM coredumped with Reset from Shell reason Condition: switchcc was executed Workaround: Unknown Headline: switchcc caused Reset from Shell coredumps on PXM45C Hardware: PXM45/C
CSCeb38659	Symptom: On PXM45 node, the AINI port goes into vc failure. Conditions: Do a resetsys. Workaround: Do a dnpnport and uppnport. Headline: resetsys on PXM45 causes AINI port to vc failure Hardware: PXM45/B
CSCeb38846	Headline: remote loopback option not available on frsm-8t1e1. Hardware: pxm1e
CSCeb38926	Symptoms: Active PXM getting stuck in backup boot after restoreallcnf is done Conditions: restoreallcnf Workaround: Esc+Ctrl+X on the console will reset the card and will come up fine Headline: REG4+:MGX8850 node crashed after doing restoreallcnf, not healthy Hardware: PXM45/B
CSCeb40265	Symptom: clkfrequencythreshold has the option of 1-5 on xcnfln/cnfln on the HS2/B card does not specify the individual value Conditions: xcnfln shows the clkfrquencythreshold 1-5. It does not explain what are the values meant. It did not say what the value of selecting 1 and etc. Workaround: unknown Headline: xcnfln shows the clkfrquencythreshold 1-5. does not show what is mea Hardware: pxm1e
CSCeb40460	Symptom: Incorrect severity seen in CIC event list resulting from real device testing. Conditions: executed reset, switchredcd etc. commands on MGX 8850 to see the effect in CIC. Workaround: None Headline: CIC: AXSM_16OC3 card events being sent into CIC with incorrect severity. Hardware: pxm45
CSCeb45350	Symptom: APS fails to switchover to protection line. Conditions: Backcard of primary/working slot is pulled out. Workaround: None Headline: APS doesn't switch to Prot. when backcard of Working is pulled out Hardware: pxm1
CSCeb46725	Symptom: tCrdmp task logged a sev 3 event log message indicating proxy file protocol error Conditions: resetsys was executed ]Workaround: Unknown Headline: tCrdmp task logged Proxy file protocol error after node rebuild Hardware: AXSM-E
CSCeb47830	Symptom: SSI exception error Conditions: snmpSA malfunctioned Workaround: None Headline: ssi exception error: snmpSA crash Hardware: pxm45
CSCeb48332	Symptom: Event log messages for certain modules indicate LPID in hex instead of dec. Conditions: Modules such as IFM generate event log messages Workaround: Unknown Headline: LPID should be displayed in dec. not hex to be consistent with cli Hardware: PXM45/B
CSCeb48697	Symptom: dspcds shows UNKNOWN card type when card is in mismatch Conditions: When a slot or the lower bay of a slot is reserved for half height card and insert full height card _ AXSME _ to the s lot, dspcds shows mismatch but UNKNOWN card type. Workaround: use dspcd to see card type. Headline: dspcds shows cd type UNKNOWN when in Mismatch state Hardware: pxm45
CSCeb48731	Symptom: AXSM/B UNI port passes F5 Segment AIS cells to network. Conditions: F5 Segment AIS cells supplied to AXSM UNI port Workaround: Unknown Headline: AXSM/B UNI port passes F5 Segment AIS cell to network Hardware: axsm1b_oc3
CSCeb48739	Symptom: dspcd shows MISMATCH but no reserved type. Conditions: Lower bay reserved from FRSM-8T1 (half height card). Insert full height card - AXSME, dspcd shows mismatch but UNRESERVED. Workaround: dspcd <lower-bay-slot-number> and see if the lower-bay is reserved if so that is the reason for the full-height card to be in mis match. Headline: HARD: dspcd shows MISMATCH but no reserved type Hardware: pxm45
CSCeb50108	Symptom: IOS IPC communication was sent to RPM-XF card on LCN 7. IOS IPC communication should use LCN 2. Conditions: None Workaround: None Headline: PXM45 sends ipc polling request on LCN 7 Hardware: PXM45/B
CSCeb50268	Symptom: DNR getting generated while SF/SD is outstanding Condition: APS int req gets overwritten while Doing a Forced Switch Clear Workaround: None Headline: After forced switch W->P, SFBER on W does not cause W->P switch Hardware: AXSM-E
CSCeb50419	Symptom: Trunk in minor alarm Conditions: The same trunk is clear on the switch and another CWM Workaround: None Headline: axsm-xg trunk in minor alarm Hardware: AXSM-XG
CSCeb51078	Symptom: dumpconfigs command aborted when there is a RPM card in the node. Conditions: when execute dumpconfig command to dump config on a file the command is aborted when it came in to slot 9, which is a RPM card. Workaround: unknown Headline: dumpconfigs command aborted when there is a RPM card in the node Hardware: pxm1e
CSCeb51081	Symptom: Can not pass traffic. Conditions: clrallcnf and re-add the same configuration. Happen very infrequently and hard to reproduce. Workaround: None. Headline: AXSM5 loss traffic without any alarm Hardware: AXSM-XG
CSCeb51323	Symptom: The active pxm1e card got reset by itself, and a switchover was observed Conditions: A switchcc has triggered a node hang, and has cleared itself, before this problem was observed. Workaround: None Headline: SRMEB: Stats manager caused Active PXM1E reset Hardware: pxm1e
CSCeb51965	Symptom: Loss of node access via LAN/console, AXSM & RPM cards unable to boot up Conditions: Reset all SMs in a MGX8850 node and when they are coming up i.e. some are in INIT state, reset them again. Workaround: None Headline: LSNT: tQeTask & tDispatch Task hogging the CPU Hardware: PXM45/B
CSCeb52781	Symptom: Online diag for SRM or SRMEB-3T3 is enabled when "cnfdiagall enable enable <> <> <>" is executed Conditions: Online diag for SRM or SRMEB-3T3 is enabled when "cnfdiagall enable enable <> <> <>" is executed Workaround: None Headline: SRMEB:No ERR msg while enabling SRM/SRMEB-3T3 Online Diag Hardware: PXM45/B
CSCeb53735	Symptom: PXM switchover due to workQPanic:Kernel work Q overflow. Conditions: In fully loaded shelf with redundant PXM45 cards, slot8 was active and slot7 was standby. PXM switchover happened because Backcard for slot7 was found to be healthier than backcard for slot8. Workaround: Unknown. Headline: DE-LSNT:PXM switchover due to workQPanic: Kernel work Q overflow Hardware: pxm45
CSCeb55258	Symptom: When provisioning a CESM connection we had a failure with the error "connection does not exist in cPro db". The real cause of the failure was a lack of bandwidth on the feeder trunk up to the rev2 node. The error message MUST be changed to a relevant message. In the latest release of 4.0, we have fixed this error message to now say "Requested cell rate (lscr/lpcr/lmcr) is too high." This is still misleading to the customer. They would like the error message to say. "Requested cell rate (lscr/lpcr/lmcr) is unavailable" Conditions: Customer is running 3.0.10 SWSW on CWM 10.5.10Patch 3.2 Workaround: Headline: Misleading error message when provisioning and not enough bandwidth Hardware: pxm45
CSCeb55910	Symptom: CCMA logs IPC send fail messages Conditions: AXSM-E is in init state after going through a reset Workaround: Unknown Headline: CCMA-4-IPCSENDFAIL message logged for AXSM-E in init state Hardware: AXSM-E
CSCeb55991	Symptom: In the log we see it switch from one clock source to another for no apparent reason in the log. MGX1.7.PXM.a > dsplog -mod CLK_ 07A48828 06/30/2003-19:24:55 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Primary Clock status Trap Send: Status: Locked 07A48827 06/30/2003-19:24:55 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 07A48735 06/30/2003-18:46:56 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Secondary Clock status Trap Send: Status: Locked 07A48734 06/30/2003-18:46:56 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Secondary clock. - 1 dropped 08S02972 06/26/2003-13:26:30 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 07A27728 06/26/2003-13:26:29 CLK_-7-TRAP_SEND NwClockMgr clkmgrTrapSend Primary Clock status Trap Send: Status: Locked 07A27727 06/26/2003-13:26:29 CLK_-7-SWITCH_CLOCK_DO NwClockMgr clkmgrProcessPollTimerE System has locked to Primary clock. - 1 dropped 08S02936 06/26/2003-04:33:21 CLK_-7-SWITCH_CLOCK_DO ----------------------------------------------- MGX1.7.PXM.a > dspclksrcs Primary clock type: bits t1 Primary clock source: 7.35 Primary clock status: ok Primary clock reason: locked Secondary clock type: bits t1 Secondary clock source: 7.36 Secondary clock status: ok Secondary clock reason: locked Active clock: primary source switchover mode: non-revertive --------------- Conditions: MGX PXM45B 3.0.20.100 Workaround: None Headline: Clock Source switching without any logged information Hardware: PXM45/B
CSCeb56175	Symptom: The feature checkin for shmping has a bug that it includes the pxm for ping. Hence, it will always return ok under the condition when the ping should have resulted a non ok result. Hence, under conditions like switchcc the symptom will be that the new active card is unhealthy and brings down the node but the old active cannot bootup. Condition: Standby pxm has an ATMizer level problem that disallows it to communicate with any SM(axsm BBSM). This will go undetected and on switchcc the old standby i.e. new active will be unable to take over as active and bring down the node. Workaround: Standby card will be taken out and the old active new standby should be rebooted. Headline: ShmPing should exclude pinging pxm peer Hardware: pxm45
CSCeb58207	Symptom: None of the BERT commands executed is not seen in the dsplog Conditions: All the BERT commands like cnfbert, delbert, dspbert are executed successfully. But the command is not displayed in the dsplog Workaround: unknown Headline: none of the bert commands executed is seen in the dsplog Hardware: pxm1e
CSCeb58227	Symptom: Conns are not derouted upon ILMI timeout when SLP is enable and deroute delay is configured. upon LOS the connections were derouted upon the ILMI timeout when the SLP was enabled and even we had deroute delay configured more then ILMI timers. That was as per function spec. But, in this release we are observing that the connections are derouted upon derouted delay timer is timeout when SLP is enabled and deroute delay is configured. As per ILMI standard, if the SLP is enabled then conns should be derouted when ILMI timeout. Workaround: unknown Headline: conns are not derouted upon ilmi timeout when slp is enabled and dero Hardware: pxm1e
CSCeb58912	Symptom: PXM45C reroute rate slower than the expected rate of 350 calls/sec Conditions: During reroute of 30K connections in a 4-node n/w with 2 via nodes. Workaround: None Headline: PXM45C reroute performance < 350 calls/sec Hardware: PXM45/C
CSCeb60130	Symptom: loadrev on frsm with 1:n redundancy, after secondary comes up standby, remove primary nbsm card, secondary is still stan dby (as expected) now reset secondary nbsm, secondary nbsm in Failed-U state. Conditions: 1:n redundancy, loadrev state. Workaround: None. Headline: HARD: secondary nbsm fail due to reset sec without prim in loadrev Hardware: pxm45
CSCeb61384	Symptom: Unable to delete the PNNI node Conditions: Delete the lowest level and attempt to delete the next level. Workaround: None Headline: Unable to delete the logical node Hardware: PXM45/B
CSCeb61532	Symptom: Node went unreachable and found all T3's down through AXSMs in question, slots 9 and 10. Both cards reset more than once but unknown how many exactly. During at least the third self-reboot of card 10 it was pulled which restored the outage with 9 taking over and stabilizing. Card 10 was then reinserted and came up normally. Conditions: Normal network traffic with some network latency present. Workaround: Pulled card in constant reboot allowing other in pair to take over. This stabilized the condition Headline: MGX went unreachable with AXSMs in continuous reboot Hardware: axsm1
CSCeb61872	Symptom: entPhysicalSoftwareRev varbind empty in traps 60055 and 60056 Conditions: Intermittently occurs on PXM45, PXM1E nodes for RPM-PR slots Workaround: None Headline: sw rev varbind not available when trap 60056 sent for RPM Hardware: pxm1e
CSCeb63216	Symptom: dspclkalms does not reflect standby clock source 'reset' and 'inphase locking' conditions Conditions: External BITs cable from standby PXM was removed and reconnected Workaround: Unknown Headline: dspclkalms does not reflect stdby clk src in reset or in phase locki Hardware: PXM45/B
CSCeb63231	Symptom: bootchange configuration displays incorrect information Conditions: Modifications were made to the (e) field Workaround: Unknown Headline: bootchange displays incorrect info after changing (e) field Hardware: PXM45/B
CSCeb63658	Symptom: HMM had detected a SABRE parity error and reported MAJOR-NON-FATAL ERROR to SHM that reset the AXSM-E card. Conditions: HMM was running. This is a default setting Workaround: None Headline: Increase Sabre error threshold Hardware: AXSM-E
CSCeb64000	Symptom: switchcc loss exceeds 250ms Conditions: 1.No srm's are present in the node 2.a dax conn was added between AXSM16-oc3 and AUSMB-8E1 with a loop on ausm port an d a traffic generator on the AXSM port. 3. Traffic is being pumped and loss over the switchcc duration was measured Workaround: None Headline: switchover loss around 630ms, >250ms Hardware: pxm45
CSCeb64863	Symptom: Certain cli command output exceeds the 80 char limit Conditions: None Workaround: None Headline: Policing of 80 char limit for certain cli commands Hardware: PXM45/B
CSCeb65427	Symptom: sometimes issuing the cli command with wrong option or parameter would cause the PXM to reset. Conditions: None Workaround: Headline: Printf Mutex semaphore getting locked Hardware: pxm1e
CSCeb67611	Symptom: No event logs found in dsplog for srme LINK commands Conditions: Addlink and dellink and observed dsplog Workaround: None Headline: SREMB: no event logs found for srme LINK commands Hardware: pxm1e
CSCeb67843	Symptom: PnCcb hogs the cpu time on the node and idle time goes down to zero Connection fail with Cross Commit failure. Conditions: Could happen when the number of cons on AXSM go above 80K (depending on the VPI/VCI ranges used for the connections). Workaround: None Headline: Failed to add entry in QE48 Conn id table Hardware: axsm1
CSCeb68706	Symptom: Observed message 'file already closed' after runrev executed on FRSM in slot-2 Conditions: After doing a runrev on FRSM in slot-2 of emeapl36, observed a message pop up file already closed'. Following are the CP captures for the node: Workaround: unknown Headline: observed message file already closed after runrev executed on frsm Hardware: pxm1e
CSCeb69124	Symptom: Incremental files deleted slowly (one per hour) when standby is available. Conditions: Standby available Workaround: Use shellcon to delete incremental files Headline: Incremental files are deleted slowly when Standby is available Hardware: pxm45
CSCeb69414	Symptom: pnport of oc192 stays in down in progress for long time(1 min - 7 min) Conditions: Performed commands dnilmi and delpart on the AXSM-XG card. Workaround: None. Headline: Pnport of AXSM-XG oc192 card stay in down in prog for long time Hardware: AXSM-XG
CSCeb69793	Headline: FI: test-13:Hard disk failure: No trap upon fault Hardware: pxm1e
CSCeb70258	Symptom: Incorrect ifName string in trap 60373 Conditions: None Workaround: unknown Headline: Incorrect ifName string in the atm phy trap 60373 Hardware: AXSM-XG
CSCeb71360	Symptom: AXSM reset due to watchdog timeout. Conditions: PXM45 on the MGX was running 3.0.23 Workaround: None Further Problem Description: The following messages will be displayed in the dsplog of the PXM corresponding to the AXSM slot. 01U00004 07/20/2003-01:11:19 SYS-7-VERSION tRootTask sysCardInit Boot Code Rev: [003.000.023.202], FW Rev: [003.000.023.202_swtools] 01U00003 07/20/2003-01:11:19 SYS-7-STARTUP tRootTask sysCardInit System is up, Reset Reason: [WatchDog Timeout Reset] 01U00002 07/20/2003-01:11:19 SYS-7-BOOTREGISTERS tRootTask sysCardInit Boot ResetType=0x2 ResetReason=0x43 ResetPc=0x80000038 StatusReg=0x400004 CauseReg=0x400 CacheErr=0xa421f1bb 01U00001 07/20/2003-01:11:19 SSI-6-RESETDUMPTRACE E:00023 tRootTask ssiSaveResetTrace A function trace dump is available from the last reset. Headline: Axsm resets due to Watchdog timeout with PXM running 3.0.23 Hardware: axsm1b_oc3
CSCeb74423	Symptom: When a communication fault is injected using a special FI board and a PXM switchcc is executed after the fault injection, both the PXM would reset Conditions: When we inject a communication fault using a specific fault in a Fault Insertion board, the communication from the standby pxm to the active pxm is lost for a window of 3 minutes. In this timeframe if we execute a switchcc on the PXM, both the PXMs woudl reset. Workaround: None. Headline: Block switchcc/yred while stby axsm is not responding to polling Hardware: axsm1b_oc3
CSCeb77548
CSCeb79161	Symptom: Some connections do not get synced over to standby Conditions: Has never occurred in 4.0.x release. this is a defensive fix to protect against subsequent database upgrades. Workaround: None required. Upon switchover, the missed connections are recovered from the disk.
CSCeb80000	Symptom: connection doesn't deroute right away upon dnport with deroute delay on and secure link is disable. Conditions: connection doesn't deroute right away upon dnport with deroute delay on and secure link is disable. Workaround: unknown Headline: conn doesn't deroute right away upon dnport with deroute delay on an Hardware: pxm1e
CSCeb80600	Headline: corrupted stats on pxm1e -- cesm-t1e1 cards under corner configs Hardware: pxm1e
CSCeb82476	Symtom: 3 unknown alarms Conditions: customer upgrade software Workaround: revert the upgrade the alarms goes away. Headline: Minor cards alarms seen when upgrade to MGX PXM45/B 3.0(23) Hardware: PXM45/B
CSCeb82771	Symptom: Hard Drive backcard of PXM45B reported failure Condition: Offline diag was executed Workaround: Unknown Headline: HDD fails full coverage off line diag Hardware: PXM45/B
CSCeb83142	Symptom: connection fails to route with Last Fail Cause: "Quality of Service unavailable" Conditions: Slave will reject the connection for nrtvbr if slave scr * remote util < 1 Work Around Have slave scr * remote util > 1 Headline: connection fails routing due to wrong util used at slave Hardware: pxm45
CSCeb84307	Symptom: PXM resets Conditions: dsppnni-path aw nrtvbr cli command was executed Workaround: Unknown Headline: dsppnni-path aw nrtvbr command caused PXM reset Hardware: PXM45/B
CSCeb84390	Symptom: Rx Idle cell does not increment in dsplncnt or dspatmlayercnt Conditions: clear channel card only (AXSMXG_1_OC192 and AXSMXG_16_OC3) Workaround: None Headline: rx idle cell counter does not increment in dsplncnt Hardware: AXSM-XG
CSCeb85464	Symptom: Active PXM reset and coredumped Conditions: switchredcd was executed on one of the AXSM pairs in node Workaround: Unknown Headline: AXSM switchredcd caused PXM to reset and coredump Hardware: PXM45/B
CSCeb87513	Symptom: Pnni link between 2 PXM1E based MGX8850's goes down intermittently. These PXM1E's have IMA backcards. Output of the "dsppnni-link" command on one side shows that it is in "oneWayInside" hello state and the other is in the "attempt" state. Conditions: The PXM1E's are running 4.0(0.201) code. Workaround: Switchcc helps recover from this state. Headline: pnni link on a PXM1E with IMA backcard goes down without recovery Hardware: pxm1e-ima
CSCeb88172	Symptom: When upgrading the PXM45/C to 4.0.10, and waiting for the PXM45/C to go to go to a stable condition "Active/Standby pair" we log into the active PXM45/C and issue a switchcc. The switchcc command is successful, but the previous active PXM45/C cannot come back to a standby condition. The card keeps resetting. Conditions: Occurs only when issuing a switchcc command. Workaround: None Headline: PXM45C keeps resetting after a switchcc Hardware: PXM45/C
CSCin46303	Symptom: invert_clock param always -1 in db line table for FRSM-HS2B-12IN1 card on 8850. Conditions: adding / configuring X21 or V35 lines. Workaround: None Headline: invert_clock param not updated in db for FRSM-HS2B-12IN1 card on 8850 Hardware: frsm-vhs
CSCin50435	Symptom:degraded x-bar msg after switchcc, causing failure. Conditions: pnni-ats env Workaround: Unknown. Headline: AUTO: degraded x-bar msg after switchcc, causing failure Hardware: all

Anomalies Resolved in Release 4.0.10

CSCdv50574 delapsln produced incorrect usage statement

CSCdv69400 Enable local loop on addchanloop on AXSM-E

CSCdv87022 oam error while adding connections

CSCdw84887 AXSMXG asic registers needs to be dumped in the core.

CSCdx29779 IPC buffer corruption due to cache coherency - task suspension

CSCdx61758 ResetAtmizerOnPxm1e()/ResetAtmizerOnPxm45() use hard-coded adrs

CSCdx75573 SRME shown as SRM-T3 when it is in INIT state

CSCdx78943 AXM-XG: Dspcd displays NOVRAM Dump with Mismatched BC - axsm5

CSCdx85715 Need equivalent command of dsppnctlvc for higher level SVC based RCC

CSCdy21305 IPC memLeak in ilmiMain task

CSCdy27632 [cnfxbardmin on] does not enable PXM45A/B humvee/xbar links correctl

CSCdy37182 Incorrect dspcd Info Provided For Quad OC48 Back Card On AXSM-XG

CSCdy40482 CTC messages flooding the logs during standby reset

CSCdy61591 Enhance periodic port resynch on PXM to trigger more often

CSCdy61622 Broken HE ready pin can cause XBAR problem

CSCdy81038 dspcds shows failed backcard as ACTIVE

CSCdy82520 CIT40:several nni ports ilmi status stuck in NotApplicable

CSCdz06444 AXG4CH: XG in Failed state after resetcd with 126 EVNNI ports.

CSCdz09843 CIT40:trapSrvTask suspended due to IPC buffer corruption

CSCdz21942 AXGCH: APS1:1; Dspapsln & Dspbecnt reject with incorrect error msg.

CSCdz22884 AXGCHTM:EFCI not updated in cli dspchancnt

CSCdz23198 dspportcnt avg. counts plummets when discard occur

CSCdz23621 Z-RED:Standby RPM-XF vsi master endpoint id is not cleared on PXM

CSCdz26250 AXGCH:dsppaths -ds3 shows path N/A when -ds3 table empty

CSCdz43418 P2MP_DT: addparty create svc UBR instead of CBR with BCOBA

CSCdz45007 AXSME-16T3E3 failed when redundancy is added.

CSCdz47627 PXM45/B/C does not come up after inserting HDD backcard

CSCdz61310 1e: DT Error messages appears on all Xterm sessions

CSCdz63826 P2MP_DT: Nodal conn limit can be exceeded when p2p and p2mp combine

CSCdz65649 1e: DT addapsln should not be allowed if aps mini bkplane is not pre

CSCdz65654 Double free memory problem in function pnni_svc_send_msg_to_sigapi()

CSCdz72159 SYSTEM:Standby PXM should check Active PXM heartbeat

CSCdz79515 burnboot should not be allowed on a downed card

CSCdz80353 memShow on the pxm1e displays a negative number.

CSCdz81163 CLI needs to support formatting for 64 bit objects.

CSCdz81341 Failed to sync up with one PXM45 node-CUT dir not found on this node

CSCdz81780 Memory Usage: Manage through memory pool instead of global

CSCdz82259 In NCDP mode t1 and e1 reference present at the same port 7.35

CSCdz82315 Junk output sent to all CLI by addred

CSCdz83401 dsppnni-election should show active peer group leader node name

CSCdz87239 addred on MGX gives an error message

CSCdz87255 File open doesn't return error for non existent file.

CSCdz90184 VsiErr and VSI_VRM_TRACE does not work on standby PXM45

CSCdz90394 Enhance display of dspnwnodes to include in use field

CSCdz90584 UPGRD: PXM45/B active/stdby in minor alarm after upg from pxm45A

CSCea01025 DIP: tca option prints garbage for SONET line

CSCea02816 UPGRD: at runrev on pxm45, error log shows pnCcb task is not owner

CSCea03515 1e: DT dnport/upport causes high CPU utilization on the node

CSCea04132 1e: DT unwanted messages after clrsrmcnf for SRM-3T3

CSCea04389 ipc name server errors logged on a node

CSCea06889 Even though the slot was empty, it gave error while cc

CSCea07573 Axsmxg connection stat values are incorrect

CSCea07599 Static and Statistics Memory partitions are low in AXSME 4.0 Image

CSCea09461 PXM1e: Reducing port rate by cnfport got rejected with VSI error

CSCea10567 Need to warn/block reset single PXM with disk hw failed

CSCea11030 snmpSA task is stuck- CWM doesn't get traps

CSCea11335 SNMP request caused an exception

CSCea11689 MGX sends card removal trap with alarm severity of 8 - s/b 2

CSCea12511 dspvsiparts show partId as 0 when partId is 1

CSCea13194 REG4: dspchancnt X -r 1 cannot be quit 1e: DT

CSCea13539 CTD & CDV incorrectly copied in atmSoft_getAltenateAdminWt()

CSCea13996 UPGRD: at loadrev, stdby pxm reports SFP mismatch

CSCea14630 IMA bandwidth change not reflected in PNNI

CSCea15325 1e: DT REG4: one-way switchcc loss > 520ms on 8-oc3

CSCea15665 UPGRD: tDbgInTask/tDbgOutTask get TID 11 when telnet from w/in node

CSCea16704 resetcd shows Standby card not ready/available card not redundant

CSCea17820 Null saved ttl i.e. ptr log cluttering CC module

CSCea17835 SHM<->XG SFP: SHM doesn't make secondary cd actv on addred actv mis

CSCea18042 PXM crashes after start traffic between 2 RPMs in the shelf

CSCea19434 UPGRD: during upgrd, pnCcb reports AUDIT release error

CSCea20454 PXM1e: 2cells/s AIS on Swth side Tx after get LMI-Abit frm Feeder

CSCea20600 pnPnni is not the owner of the block

CSCea20706 Require user confirmation for cnfpath -width change

CSCea21717 AXSM with policing enabled, expectation is that gcra1 is enabled

CSCea21837 Cant disable Frame discard parm on VPCs

CSCea21991 1e: HARD unable to upln2.5-2.8 if 8oc3 goes UNRES during h/w upg

CSCea23516 Congestion value help doesn't reflect the new acceptable values

CSCea23534 GDB Syncup with firmware files.

CSCea23761 Implement PCI error interrupt on PXM45/C/pxm1e-8oc3

CSCea24010 OAM error: OamLpbkHandler seen during upgrade

CSCea24098 1e HARD: SHMA-4_API_SEND_ERR on active PXM1E after switchcc/upgrade

CSCea24732 FRSM12:lmiXmtUpdateStatus inside shellcon flag control

CSCea24948 Hotstdby:dsphotstandby check IMA DB record on non-T1E1 cards

CSCea25138 SCM Debug Enhancements for collecting info on Poll/Htbt failures

CSCea25406 UPGRD: addaps on Jcombo, SHMA-INTERCD-APS-RPT logged to error_log

CSCea26305 Add explanation to usage of adding part id to a controller

CSCea26569 Connection show wrong preferred route status after prefroute changed

CSCea26816 1e HARD: SSI-5_DOSFAIL error due to task cutVTask

CSCea26821 1e HARD: tRed error, possible corruption for redTable after abortrev

CSCea27324 1e HARD: NCDT-4-ADDVC_FAIL on standby PXM1E on configuring ncdp

CSCea27538 Diag image hangs on DPDC CPUB

CSCea27656 Dax con: need to update fail cause code if slave is LOS

CSCea27781 cnfconsegep on leaf svc endpoints displays root endpoint vpi/vci

CSCea27803 tstpndelay fails to work on svc leaf endpoint

CSCea27807 BRAM corruption on PXM45B after power cycle and during runtime

CSCea28523 1e HARD: FILM-5-FWRITE_FAILED should not be logged as an error event

CSCea28822 1e HARD: RED-5-SEND_MISMATCH upon removing active sec FRSM-2T3 BC

CSCea28840 1e HARD: downLoadBram failed after remove act pri FRSM-2T3 BC

CSCea28863 Enhance SyncRam to support Max Outstanding IOV Buffer from 8 to 16

CSCea28998 Need to initialize response message in cli2shmCmdIf()

CSCea29118 Place Holder to remove ability to enable/disable sfp security check

CSCea29984 Resource Reservation phase II checkin

CSCea30418 Need to add cefcLastClearConfigTime in the shelf generic files

CSCea30694 dspconsegep on SPVC endpoint show incorrect segment endpoint status

CSCea31745 CIT40:4 NwClockMgr log should be reduced to lower severity

CSCea32116 1e HARD: Autocard and dbClnt event log after delred 1:1 FRSM VHS

CSCea32276 1e HARD: VSIS-5-VSIERR event log due to CMTASK

CSCea32283 1e HARD: SHMA event log due to task tmon on PXM1e-8oc3 and 8E3

CSCea32296 1e HARD: pcemaGETLINFormPort error due to task FTM on PXM1E-4oc3

CSCea32660 Handling of entries in Provisional tree on deletion of part. on SM

CSCea32763 1e HARD: NCDT DISABLE PORT event log when all ncdpports are dn PXM1e

CSCea33031 1e HARD: SHM API Err due to task pcemaSyncTash on PXME-8oc3

CSCea35486 CIT40:some filters for dsppnsysaddr do not work

CSCea37542 REG4: AXMXG-CH dspportcnt syntax is incorrect

CSCea38021 dspcd does not report alarm of standby PXM

CSCea38347 cnfdiagall is done enabling diag for all slots, enables srm3t3 not s

CSCea38739 REG4: clrimadelay failed when IMA group in version fallback

CSCea38855 AUTOMATION: svcblock is broken

CSCea39016 dsppnni-svcc-rcc shows wrong information

CSCea41058 Size of Replicate Directories array must be dynamically calculated.

CSCea41104 set on ChanRowStatus to notInSerivce on down conn does not throw err

CSCea41573 Avoid memory leakage in trapserver for large traps

CSCea41723 Add ICR range check to SES CLI interface (cnfcon and addcon)

CSCea41802 dspdeverr shows redundant info on every screen of a multi-screen o/p

CSCea41991 switchapsln display need to be enhanced

CSCea42097 Resource Reservation phase III checkin

CSCea42240 [SysDiag]: sysdiag clears self diag errors while going STBY->ACTRDY

CSCea42581 Copy OK:65552 bytes copied popup on AXSM telnet session

CSCea43402 pxm1e inserted caused clkalms but dspclkalms result in error message

CSCea44266 REG4: Unknown reserved st. of Combo back card causes APS failure

CSCea44644 PXM45: ping command does not default to 5 and no No. of packets opt.

CSCea45267 REG4: Routing cost not update after conn reroute due to vpi mismatch

CSCea45702 dsptopolinklist displays rmt PnPort ID as a huge -ve no.

CSCea46427 PXM45C/PXM1E-8OC3: HW WD Timeout is not the same as on PXM45A/B

CSCea46677 Non persistent pep code cleanup

CSCea47481 after switchover data stopped on a pvc between two nodes

CSCea48409 dspcons -rteid has incorrect syntax help

CSCea49519 Do not update ptse flush to standby for topo nodes

CSCea49615 UPGRD: on card bringup in 8830 node, srmOnlineBotBay task logs Error

CSCea49652 UPGRD: upon switchcc on pxm1e, ACAR-2-DBINIT from autocard task

CSCea50382 ATMC-5-INTERNAL WARNING need to be cleaned up

CSCea50527 EvtLog:DB2S-4-DBSVR_DOS_FAIL logged on switchcc

CSCea50686 EvtLog:PXMC-4-GENERR message logged after switchcc

CSCea50748 Resource Monitor Files Checkin

CSCea51139 REG4: FRSM12: tstcon/tstdelay result shows 5 channels

CSCea51508 Telnet server enters infinite loop waiting on input

CSCea51517 Supported SM cards need Core Hot Dump feature

CSCea51520 SSI IPC tracing on LCNs, Epids and Card-to-Card data is broken

CSCea51928 cnfdiagall enables diag for empty slots 31 and 32

CSCea52204 pxm45 exception due to a boundary case on conn upload file cleanup

CSCea52282 UPGRD: event_log get conns in CPRO-4-GET_LCN_FAILED for axsmxg

CSCea53625 UPGRD: upon loadrev, the pxm logged RESY-5-BLKZEROPEP (dsplog)

CSCea54679 Secondary clock status showing OK,clock reason is unknown reason

CSCea54763 UPGRD: ssiChunkPoolsShow gets neg. value for nb_alloc_ok, nb_free_ok

CSCea54830 cnfconsegep response dump outputs corrupt screen

CSCea55999 dspload shows service category corruption for partitions

CSCea56491 Link Invalid trap for uplink not include correct local port#

CSCea56548 Clear IP interface stats counters

CSCea56906 PXM45 reset due to pnCcb task crashing

CSCea57084 cnfclkparams does not behave as intended

CSCea57096 if path is up, conn configured but not bound the drop all msgs

CSCea57626 Placeholder for P2MP on PXM1E Feature Checkin

CSCea58703 Debug congestion msg statement is spewed to screen during SVC test

CSCea58817 dspdiagstat failed counter not reset properly

CSCea58913 UPGRD: upon burnboot, axsmxg comes up active/active exp. active/mism

CSCea59011 UPGRD: node gets error_log of RESY-5-PEPNOTEXIST, no entry event_log

CSCea59054 SNMP subagent is not registered leading to GET failures

CSCea59170 UPGRD: upon switchcc on pxm1e, ACAR-2-DBINIT from autocard task

CSCea59289 addchanloop VP greater than 255 doesn't work on NNI link

CSCea59612 dnpnport/uppnport caused all links to go to ILMI failure

CSCea59652 Offline diagnostics fails on AXSM/E card

CSCea61569 CUT: memory leakage

CSCea63353 Dynamic memory corruption - AXSM/B

CSCea63712 Send proper Severity Value in PXM45/PXM1E/AXSM and all traps

CSCea63966 Post passed even PXM boot from wrong boot rev

CSCea64148 Resource Reservation phase III implemented for critical tasks

CSCea64332 Handle sysClkTick wraparound in SSI

CSCea64399 REG4: Pref route: Num of network node poorly display

CSCea64478 Node unreachable: memory is held by pnni tasks

CSCea64753 Event log entry for RDI-L needed

CSCea64778 dspadjlnalmcnt -intvl option should be removed

CSCea64785 AXSM Conn. database corrupted after disk corruption

CSCea64808 ssi exception generated by HwMonitor on AXSM

CSCea65228 REG4: AXSMXG-CH comes up as a Active-F/Active after resetsys.

CSCea65471 Backend functions used by k_entity_get should set errno

CSCea65604 REG4: PNNI task is suspended due to software exception

CSCea65605 limit max cref count in RM to 27000 for PXM45

CSCea65768 dumconfigs executes some macro commands which are not supported on p

CSCea65819 PXM failed due to event log disk write problems

CSCea66038 Provide mechanism to track buffer leak for all SRs applications.

CSCea66438 Bert is enabled on the FRSM8T1 line even though no bert running on P

CSCea66540 REG4: Rrtcon causes traffic outage for extended period of time

CSCea66920 IT/AT: incorrect range/functionality for dspslotlink & dsperr

CSCea66971 Log floods with VSI_4-RMBWCACError

CSCea67065 Connection mismatch due to bulk sync not working correctly

CSCea67241 Port rx RDI alarm on virtual channel

CSCea67896 after switchover standby came up in mismatch state with trunk bc

CSCea68727 Incremental files are not getting deleted from couple of nodes

CSCea68798 Telnet to a node fails with the error indicating No Resource

CSCea68950 CIT40:pnCcb suspended at atmSoft_openSvcParty

CSCea68959 CLI: telnet need to setsockopt SO_KEEPALIVE

CSCea68972 CIT40:port stuck in down in progress with dangling svc

CSCeb69150 PXM reports port alarm on AUSM-IMA card after clearing of line alarm

CSCea69245 pxm1e clock is stuck in interface does not support clockin state

CSCea69606 SRMs in reserved state after clrsrmcnf

CSCea69620 telnet to lan interface fails time to time

CSCea69772 number of pnports is -7

CSCea69946 tracking bug for hw alms issues at customer site

CSCea70636 It is possible to download ver 3 bootcode to Broadcom PDC flash

CSCea71135 Reroute on AXSM-XG caused tVsiSlave toget suspended

CSCea71197 SSI Sync Timer not initialized

CSCea71360 AXSM-XG Cell Bus SAR Reassembly status shows discards occasionally

CSCea71811 pxm1e reporting wrong state of srm-#T3 of slot 16

CSCea71884 Evt Log indicates error, unable to open/create diag log file

CSCea72069 Ports went to building vc after reinsertion of AXSM cards

CSCea72190 deletion of SCT files causing errors, and not updating properly

CSCea72419 SSI exception in SAR ISR caused card reset

CSCea73159 AXSM-XG memory map setup incorrectly

CSCea73315 AXSMXG:Ifname scheme needs to be changed as per CWM req.

CSCea73429 SysDiag causes memleak on Active PXM45 card

CSCea74070 PXM45B switchover happened automatically on MGX8950

CSCea74091 REG4:Reseating both pxms on MGX 8950 freezes the nodes

CSCea74178 REG4: reset SM (Empty) and switchover on PXM1E, showing Failed/Empty

CSCea74359 SHM Fatal/Non-fatal report APIs - pcema(PXM Connmgm)

CSCea74366 SHM Fatal/Non-fatal report APIs - PXM Connmgm-VSIS

CSCea74371 SHM Fatal/Non-fatal report APIs - IP Name Server

CSCea74373 SHM Fatal/Non-fatal report APIs - pcpro

CSCea74378 SHM Fatal/Non-fatal report APIs - SCT File Manager

CSCea74459 Invalid entries in atm_connection for SES endpoints

CSCea74882 Connections fail to route due to svcc-rcc is not up

CSCea75170 parent change trap not sent

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

CSCea75375 CIT40:IPC 8k buffer low and congestion

CSCea75576 pep stuck in vsi-in-progress

CSCea75640 dead code causing confusion - need to be removed

CSCea75675 IPCONN Suspended & PXM45B stuck in reboot for long time

CSCea76411 sysBlinkLedOff leaks 48B of memory every time called

CSCea76798 SCT file for AXSM-XG

CSCea76869 REG4:nbsm dax conns triggers nni routine pep_p

CSCea76994 Entity MIB Changes to support OSMINE certification for ENV devices

CSCea77282 CIT40:pnCcb suspended at resyncGetLegFromSvc

CSCea77528 SRME standby does not initialize properly

CSCea77597 SSI: invariant checks flood event log

CSCea77946 flood of trap 70103, received 1197 in 5 minute period

CSCea78045 AXSM2/B offline full coverage diag always fail

CSCea78166 Connection trap (for some) implementation does not match definition

CSCea78204 CIT40: SES node stays in mem and leg congestion

CSCea78695 REG4:DBSYNC warnings in dsperrs when resetsys

CSCea78828 Both PXM45B failed when upgrading

CSCea78828 Both PXM45B failed when upgrading

CSCea79827 UPGRD: Double free of IPC buffer after IPC reply failure

CSCea80248 CLI task suspended and PXM45 switched over

CSCea80544 UPGRD: remove active pxm45C triggers Exception at interrupt level

CSCea80608 LSNT:stats files go to badfilelist

CSCea80655 Node doesn't recover from congestion during conn reroute

CSCea81631 dspalms cli on PXM45 is not showing anything

CSCea81721 UPGRD: online diag reports, but HMM does not reports card problem

CSCea81791 Need high priority queue for mgmt traffic in Europa SAR

CSCea81820 Primary RPM not reset after IPC seat deletion & secondary take over

CSCea81899 LSNT:error writing file.error 0x38801c for RPM-PR

CSCea82079 optrte produces messages in the log

CSCea82467 rtopt is done even for NNI port

CSCea82643 PnSscop holding sarMgmIpcRxBuffer

CSCea82849 function returning values other than function type

CSCea82887 starvetask error: SCM Leaking Memory(FixDone: Debug Code Added)

CSCea82940 Src node found bypass for ingress & egress ports on same border node

CSCea83015 Active AXSM failed to operate and standby card went to failed to sta

CSCea83031 UPGRD: At runrev on AXSM-OC3B,Sync Timeout Handler fail

CSCea83188 wrong error message when cellbus clk is configured with autosetting

CSCea83257 The ENUM_errCode_genConnErr (117) is not unique/specific

CSCea83345 Active PXM gets reset while core hot dump is aborted on SM

CSCea83402 introduce event logs in atmizer host code

CSCea84077 dsppnni-node-list shows 2 (instead of 1)for the local node

CSCea84180 XBAR: AXSM-32T1E1-E cards not added in the list of serial bus cards

CSCea84287 PXM1E went to idtmon

CSCea84304 REG4: both cards reset after runrev;core dump found

CSCea84616 releasing svc but svc or call id is NULL

CSCea84711 error log - vsi state FULL but peer leg is NULL

CSCea85031 node rebuilt again after a resetsys was executed

CSCea85150 AXSMXG:dspver should show AXSM-XG under card type.

CSCea85217 popup message on telnet session atmSig_build_snmpTrace:port_id..

CSCea85222 Raise the task priority of legacy apps running on the PXM

CSCea85433 Need to enable HMM interrupt for Scheduling, QE, XIF and PIF

CSCea85629 LMI protocol should exchange logical slot/port info

CSCea85850 Leak: Memory leaked by scm message send by shm2ScmCnfPollParms

CSCea86041 MPG preferred route failure. Connection in fail state

CSCea86144 PXM switchover every minute due to pnCcb crashes

CSCea86474 rmmSendCTCMsg task not applicable for PXM1e targets

CSCea87103 Europa CTT corruption during up/dn pnpports

CSCea87281 tstcon fails if more PVCs are added between PXM1E and VISMs

CSCea88075 add diag. codes to collect overflow stats.

CSCea88905 SM needs to check for PCR >= ICR >= MCR when configuring conns

CSCea89254 AXSM-E Local Channel Loopback not functional

CSCea89407 Investigate Atmizer PCI freeze

CSCea89735 dsplns repeatedly dsp all lns when APS 1+1 lns configured only

CSCea89755 Should not consider spoke cost when BN path does not exist

CSCea89860 near-end CurrentPCVs and CurrentPES are not incrementing

CSCea90166 addred fails with back card mismatch error

CSCea90213 Trap server need to map Severity values from apps/SMs

CSCea90476 dspcdalms is not reporting correct alarms after upgrade

CSCea90885 VSI Slave Add control port failed error event msg after addcontrolle

CSCea91209 dspchancnt does not work for p2mp connections

CSCea91227 FRSM-2CT3 card stuck in Standby state

CSCea91250 Online diag flr (cc con flr) of AXSM-E OC3 - no ind in dspdiagerr

CSCea91362 VPI overlap causing dnport failures.

CSCea91382 dspchancnt on pxm1e does not work for control VCs

CSCea91807 PNNI task pnSptAw is running away

CSCea92020 Active PXM gets reset after issuing core hot-dump on service module

CSCea92539 pnCcb Crash

CSCea92707 possible of NNI resource leak !

CSCea92832 ports in down in progress, node snmp unreachable

CSCea92851 axsm and pxm cards reseted by shm

CSCea93216 Incorrect node entry in persistent topo db

CSCea93238 Messages pops up on MGX login window

CSCea93470 pnni connections not shown in dspcons after image upgrade

CSCea93772 Event Log does not show correct info on clk switchover

CSCeb00556 Reject backcard reservation from non-active SMs

CSCeb00576 Backcard unreserve should clear the reserved BC NVID

CSCeb00707 No alarms on VNNI ports

CSCeb01093 PXM45C resets with Work Queue Panic with no coredump

CSCeb01727 Static files should be deleted from standby PXM on clrallcnf/clrsmcn

CSCeb01883 need warning message about conns derouting when dnilmi via cli

CSCeb01891 resetcd fails, log shows task starvation with tNetTask running away

CSCeb01960 CIT40: Cache Exception Handler corruption in Backup Boot in PXM45C

CSCeb02143 Evt Log: SYS-4-ERR SysDiagTimerStop error messages logged during dia

CSCeb02341 Enhance DataXfer connection to allow register up to 16 windows.

CSCeb02467 cc: 1. Zero bytes to be written 2. static mem free event.

CSCeb03383 IDE perftest leaks file descriptors & memory

CSCeb03759 AXSM-XG needs to set reassembly timeout to a reasonable value

CSCeb03930 cpro code review for double commit

CSCeb03966 wr mem fails w/ startup-conf file open failed (Unknown error 1785358

CSCeb04690 link went down after delaps on secondary card

CSCeb05265 AXSME/XG should also use cutwAlarmFileWriteLatest for incr files

CSCeb05876 sscop stuck in reset state

CSCeb06087 RPM-PR should not switchover to redundant if reset flag is disabled

CSCeb06188 SNMP GetNext on Feeder table returns multiple dup responses

CSCeb06258 HARDENING: QE SAR INVMAGIC changes

CSCeb06552 New API to query for Max Elements can be sent at an instant.

CSCeb07265 Semaphore not returned in config upload

CSCeb07649 File created by Sysdiag can grow without limit

CSCeb07718 node rebuilt again after a resetsys was executed

CSCeb07879 received message the alternate tbc is not of combo back

CSCeb07963 HARDENING: Coredump should identify incomplete core and log the same

CSCeb07986 AXSM pair reset w/ DAX conns caused loss of telnet/console port acce

CSCeb08124 CCB task is stuck on ssiTaskDelay after large config reload

CSCeb08242 clrsmcnf takes 150+ sec and always failed/aborted for the 1st time

CSCeb08282 AXSM-E response to CLI dspchanloop not showing loopback type

CSCeb08420 empty slot check for cc command broke AXSM and AXSME builds

CSCeb08432 ciscoWANSscopLinkChange trap being sent out on standby PXM (dropped)

CSCeb08814 AXSM-XG went to Active-F due to scheduling U4 control parity error

CSCeb09028 HARDENING: SM Core configuration needs semaphore protection

CSCeb09216 In error case, spvc leg may be freed without pep indication

CSCeb09273 Need shellcon command to see total count of ais

CSCeb09620 CUTS timers are not working properly after switchovers/switchredcds

CSCeb10288 cc command modification doesn't use SHM API function to get card stat

CSCeb10455 Temporary disable HMM for port device

CSCeb10713 Line never out of SF

CSCeb11493 Inconsistent routing cost

CSCeb11785 P2MPJ loaded addparty failed with SPI PATH and OUT OF LEAF error

CSCeb12259 DISK: Disk goes to busy state

CSCeb12866 Online diag failed with Utopia test receive timeout

CSCeb13117 pxm45 online diag potentially leak ipc on standby

CSCeb13164 pxm45 online diag starts offline timer when swithcc to active

CSCeb13227 pxm45 online diag enhance:add diagHelp, appropriate err checking.

CSCeb13255 connections are derouted before the expiration of sscop timers

CSCeb13272 P2MPJ pnRedman exception triggered during delparties

CSCeb13320 CBM1/CBM0 Ingress Parity errors on PXM

CSCeb13364 CLI clrdiagstat does not work on the standby card

CSCeb13569 replace ssiRamIovCurMaxElementsGet with new SSI API (in all axsm app

CSCeb13967 PXM45 reset due to Tlb Load Exception

CSCeb15236 traps 60103, 60129 received with trap number=-1 at NMS

CSCeb15251 Checkin real issues found during code-review and code-coverage

CSCeb15425 linkinvalid trap missing

CSCeb15476 tstconseg not working properly with option num

CSCeb15543 config files creation fails on pxm

CSCeb15642 addaps line is allowed on AXSM-OC48/B while in AXSM-A OP mode

CSCeb16085 clear static variables and avoid static memory fragmentation

CSCeb17103 null ptr/malloc and free mismatch

CSCeb17121 P2MPJ: node reset when switchcc as subAgent fails to resolve EpId

CSCeb17400 config upload file missing cwaChanIntAbrVSVD and cwaChanExtAbrVSVD

CSCeb17732 Possible fragmentation caused by small mem allocations from heap

CSCeb17785 AXSM-XG switchover during re-routing with dn/uppnport script

CSCeb17786 Popup from CUTV Event Handler

CSCeb18012 cema should revert back reservation/unresv if SHM reporting fails

CSCeb18167 P2MPJ PXM1E-IMA P2MP addparty failed with SPI error

CSCeb18178 add debug counter for AIS send recv from controller

CSCeb18197 Standby card resets thrice and goes into Fail state after resetsys

CSCeb18630 ncdp_db gets updated during loadrev state and blocks runrev

CSCeb18702 cnfpri-routing command should be blocked if p2mp queue is not empty

CSCeb18768 TnCmdTsk03 exception found

CSCeb19078 dspcon for prefer route should show route cost as N/A be it SPG or M

CSCeb19177 Online diags: Hard disk access too frequent. Change to once in 15min

CSCeb19444 pnports in down in progress

CSCeb19644 AXSM/E does not detect and discard OAM cells w/CRC error

CSCeb19917 default val incorrectly specified in cnfintfcongth help syntax

CSCeb20060 SNMP: change binary to mutex semaphore

CSCeb20066 Temporary buffer congestion can cause Diags to stop running

CSCeb20096 cnfsscop command doesn't have parameter range

CSCeb20387 CHNK_XNOT_USED error on standby PXM after switchcc

CSCeb20411 multiple PARMINVALID errors on PXM1E node

CSCeb20426 Memory Congestion on MGX (PXM45)

CSCeb20445 Removal of OC3 uplink port on pxm45 boards

CSCeb20461 pnport remain in vc failure

CSCeb20464 multiple VSIS errors on PXM1e nodes

CSCeb20522 EvtLog:switchcc-CTC-4-EVTSENDTOSTMCHN error message

CSCeb20534 EvtLog:switchcc-MCAST-4-CNFSNMP_ERRORPA

CSCeb20553 EvtLog:switchcc-PROO-4-soPRerrEv

CSCeb20707 Upgrade of SM is locked while the SM remains in active-U state

CSCeb20746 Limit telnet node-to-node to one hop

CSCeb20884 Resetting Service modules caused a switch PXM core

CSCeb21825 NamTask occupy the memory and cause the pnport stay in down in prog

CSCeb22799 All AXSME cards show Resource Alarm Major

CSCeb22910 PXM1E standby card failed with Troot task exception after upgrade

CSCeb23245 AXSM failed after upgrade frm 3.0.20.100 to 4.0.10.2P3

CSCeb23443 Possible truncated/misformed IPC message cause errmsgs on RPMXF

CSCeb23611 IFM_LOG string error in atmcoreifcAct20

CSCeb24166 CLI-IN to wait till the cmd task is done and not accept any cmds bet

CSCeb24722 AXSM-XG: memory leak in AXSM-XG OAM

CSCeb25248 runrev failed after CESM is deleted from 1:n redundancy

CSCeb25592 AXSM-XG: cema error logging enhancement

CSCeb25839 pxm45 online diag: potential LCN leak

CSCeb26030 Chg reqd to prevent unintentional delpart trigger.

CSCeb26052 after runrev both PXM1E reset

CSCeb26138 Remove some commands which are not required

CSCeb26579 VISM <-> SAPI communication lost during VISM reset

CSCeb27325 Unwanted ssi_ipc message on AXSM-XG console

CSCeb27605 Need matching handling of IPC_CRIT_PRI ipc msg on Sar side

CSCeb27631 local variable returned in cwspConfigTable

CSCeb28248 Memory leak due to frequent PTSE refreshes

CSCeb28420 EvtLog:emSyncHumveePort fail messages in log

CSCeb28664 Inserting PXM1E/PXM45 slowly cause incorrect HW initialization

CSCeb28869 Trap Freq test reports failures (or success) twice for each run

CSCeb29029 Enhancement changes for config upload hardening

CSCeb29267 Memory allocation failures at AXSME card

CSCeb29794 RMON related event log messages should be at a higher severity

CSCeb30173 AUTO:tmOn command causes pxm1e to pause indefinitely

CSCeb30373 AXSM does not correctly report sonetPathIntervalESs object

CSCeb30550 NNI links on PXM1E went of resources with only few cons routed

CSCeb30643 Standby PXM got stuck in INIT state: link topo failed to access data

CSCeb30953 CLI session does not timeout after saveallcnf

CSCeb31839 Inconsistency in line alarm reporting with dspcds and dsplns.

CSCeb32256 SARSNDERROR filling up the dsperrs log

CSCeb32410 FM_OPEN errors are filling up the error log

CSCeb32489 VxWorks timer fails after 466/496 days

CSCeb32512 C:CUT directory is synced with standby

CSCeb32523 VISM clk ports was not correctly handle on PXM

CSCeb32526 need to enhance CBC ingress parity error logging

CSCeb32527 Non Fatal IE handling in RELEASE msg. needs to be fixed.

CSCeb32578 Node CPU usage >90% w/mpsm155 sanity - console/ethernet unresponsive

CSCeb33456 Change code handling for RPrime search for p2mp

CSCeb33695 Fix the ssiClkTickGet timer wraparound leading to file create failur

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

CSCeb35244 REG4+: Software err reset core dump generated twice within 15 min.

CSCeb35373 Need more defensive code for prevent invalid address access

CSCeb35412 VNNI link stuck in onewayoutside status

CSCeb35848 Tracing/Debug code for SHM Hardening effort

CSCeb35966 AXSM/E card core-dumps, fails and DB corruption observed

CSCeb36159 HW and card State Alarm on Stdby pxm1e combo after loadrev

CSCeb36393 send trap to indicate the enabling and enabled states of the switch

CSCeb36526 LSNT:RVT process stuck in init state after switchcc

CSCeb37438 PTSE flag changes do not get updated at the receiving nodes

CSCeb37714 svc_cac if_indexs missing in PNNI CC CF file

CSCeb37862 topo gw stuck in enabling state

CSCeb37912 AIS status is not getting updated on the VUNI port

CSCeb38038 dspcon shows con in pref when its not in pref route

CSCeb38189 could not cc to any slot after the switchcc hang problem

CSCeb38985 MOC error caused ILMI failure on AXSM-XG card

CSCeb39148 Offline diag fails with Data path test receive timeout

CSCeb39202 CWM request to reduce traps sent from the switch

CSCeb39220 subagents failed to register

CSCeb39242 Possible memory leaks in SCM.

CSCeb39866 IPC: IPC data buffers should be cache aligned

CSCeb40302 after node rebuild frsm-2t3 card came up in failed state

CSCeb40512 delred fail for LSM in 8830

CSCeb40612 reset of active AXSM in red pair - RM not freeing resources

CSCeb41273 cnfdiagall command does not work after cnfdiag <slot> used

CSCeb42454 CMSC fails to get stats file on 8830 PXM1E with long node name

CSCeb43141 PnCcb is hogging the node after downing the nni port and uni port

CSCeb43213 subagent did not come up on axsmb after upgrade

CSCeb44169 SRCV task is at 60% with a very high stack usage

CSCeb44780 FI : ATM device egress memory fault is not detected by online diag

CSCeb44925 TrapCl errors logged on stdby

CSCeb45101 switchcc shouldn't be executed when stdby pxm has a hardware alarm

CSCeb45254 SRMEB: Add/Del line loop cause APS failure

CSCeb46615 node not shown in dsptopondlist

CSCeb47263 dangling sessions on AXSM cards

CSCeb47692 TrapSrvtask holding memory

CSCeb47749 PCI2PCI Bridge in reset caused sw to lock up

CSCeb47823 unable to cc to Active/Secondary FRSM when Primary slot is empty.

CSCeb48179 Pxm1e stuck in dead lock after running addlink/dellink script

CSCeb48679 AXSM/E UNI port passes F5 Segment Loopback ID=0 cells to n/w

CSCeb48715 AXSM/B UNI port passes F5 Segment Loopback ID=0 cell to n/w

CSCeb48721 AXSM with policing enabled, expectation is that gcra1 is enabled

CSCeb49058 DS3 int on AXSM-B/AXSM-E/PXM1E alm. clear int time is incorrect

CSCeb50248 Shm reset standby PXM1e while it was in offline diag

CSCeb50728 AXSM with policing enabled, expectation is that gcra1 is enabled

CSCeb51610 PXM1E UNI port passes F5 segment loopback ID=0 to n/w

CSCeb51648 The detail QE1210 Log. is needed when SCM poll fails

CSCeb51676 EVENT-CLEANUP:multiple ATMC and ATMS errors fill in dsperrs log

CSCeb51978 Unable to login to Active PXM

CSCeb52114 Wrong trap for sonet path in alarm for AXSMXG card

CSCeb52766 LSNT: PXM45 in Active-F state, mainproc1 suspended

CSCeb53193 HARD: Prim SRM in fail state since tRed instructed to go to fail

CSCeb53201 HARD: RevChgLock corrupted and locks upgrade commands

CSCeb53689 SSI-3_Exception after resetsys

CSCeb54108 Standby PXM coredumps due to pnRedMan software error

CSCeb54229 SHMA-7-NFATAL_MAJ_ERPT filing up the dsperrs log

CSCeb54825 Persistent RM alarms generated due to SSI static med threshold cross

CSCeb55365 HARD: pseudo reserve code from AXSM to RPM does not change

CSCeb55874 PnCcb crash cause PXM45 switchover

CSCeb56475 tRoot Enhancement

CSCeb57712 ata semaphore timeout and watchdog timeout should be 30seconds

CSCeb58943 Invalid SSI trace log in event log

CSCeb59779 Trap 60051 not generated for RPM_PR

CSCeb60025 switchredcd on node resets the PXM1e

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

CSCeb61475 Standby PXM45A resets while getting the image from active card

CSCeb61894 LSNT:connections remain in alarm

CSCeb62400 Cannot do core hot-dump on any SM after core abort-dump

CSCeb62594 Disk spin down to be done only on 20G hard Disk/ add sh cmd for tmou

CSCeb62699 Axsm-xg stdby card reset and failed if keep doing delpart/addpart

CSCeb64022 Active PXM stopped responding and standby got stuck in Init state

CSCeb66181 connections on last port of AXSME/PXM1E/AXSM-XG not sent to CWM

CSCeb68355 AXSM/B does not tx RDI-P when W in LOS and P in RDI

CSCeb72999 Reinserting AXSM-XG causes PNNI link to stay in failed state for long

CSCeb73912 DISK Spin down to be disabled by default

CSCeb74414 avoid calling task delays in reboot (sysToMonitor)

CSCeb75099 All traffic loss when route the conns on AXSM-XG card

CSCeb77459 Observed Bad CRC PDUs during the signaling packets exchange

CSCeb77925 Online diagnostics on AXSM-XG causes large no of OAM cells on that

CSCeb78993 AXSM-XG: OAM Config RAM write verification should ignore misc bits

CSCeb86666 After burnboot and clrallcnf card keeps resetting during post.

CSCin33117 Deletion of P2mp Party resulted in Party FSM failed error

CSCin43381 Allowing VUNI port with VPI number 0

CSCin45167 delred is not successful on pxm card throwing switch error.

CSCin49093 Cant add CUG on e164 addr for uni30-uni40 port from gui if no CUG present

Anomaly Status Change from Previous Release 4.0.00

Table 35 lists the anomalies status change from previous release of 4.0.00.

Table 35 MGX 8850 Release 4.0.10 Anomalies Status Change 

Bug ID	Description
CSCdy53476	Communication failure between Active PXM and all other slots; Unreproducible
CSCdy59933	Unable to diskFormat or ataFormat on non 6Gig PXM-HD; Closed
CSCdy62765	PXM45 After RAMsync Failure No Core Generated.; Closed
CSCdy82452	HFIT: QE48 VC Table and QDB Memory Bank errors; Duplicated to CSCeb48125
CSCdy84895	Need command to display diag results; Duplicated t oCSCea81350
CSCdz56508	UPGRD: dspchans show connection while dspchan/dspcon/dsppncon not; Unreproducible
CSCdz77260	Local NSAP address is all 0 in channel in pxm1e-8-T3E3 card; Unreproducible
CSCea08801	FRSM-2E3 discrepancy in display on dspcds and dspred; Closed
CSCea12690	CIT40:tVsiSlave suspended at vsiSetEgrConnIdDbgInfo(); Unreproducible
CSCea25980	addchanloop 1 & 2 doesn't stop egress traffic; Closed
CSCea26838	Standby in emtyrsvd. after multiple switchcc; Closed
CSCea30843	1e HARD: master cons missing after switchcc and re-routing;Unreproducible
CSCea42260	Diag related counters (dspdiagstat) not updated correctly; Closed
CSCea43017	AXSM-XG ports went into provisioning state, XG in Active-F state; Duplicated to CSCea85031
CSCea48110	AXSM/B OC3 in emptyreserved/empty after node rebuild; Closed
CSCea55814	misleading info upon removal of srms back card; Closed
CSCea56580	spontaneous PXM switchovers with PXM45B and PXM45C; Closed
CSCea58147	Secondary clk is derived, trunk ok but clok is stuck in out of lock; Duplicated to CSCea54679
CSCea64486	UPGRD: connections from AXSM-XG not recovered after card resets; Duplicated to CSCea73159
CSCea68886	Node reset due to too many ISRs from xbar leading to workQPanic; Closed
CSCea69349	clrsmcnf failed to execute; Duplicated to CSCdz53341
CSCea69704	VSI Errors; CM Task; Closed
CSCea72126	AXSM core dumps during switchredcd testing; Duplicated to CSCea63353
CSCea72380	node reseted itself:cmtask was running away; Duplicated to CSCea57626
CSCea72763	missing VPC master end point after multiple resetsys; Closed
CSCea73675	Standby PXM card did not come up after reinsertion because of except; Duplicated to CSCea74091
CSCea74088	REG4:Full coverage on XG failed;CC_CELL_CONNECTION_FAIL; Closed
CSCea74207	REG4: tstdelay while traffic running caused axsm card to reset; Unreproducible
CSCea74217	REG4:Powercycling MGX 8950 takes two cards to fail; Closed
CSCea74333	REG4:AXSME online diag doesn't work; Closed
CSCea74337	REG4:conns stopped reroute; heavy mem leaks when 45c active; Closed
CSCea75337	REG4:Utopia online diag failure on PXM45C; Duplicated to CSCdz09843
CSCea75591	offline diag failure on AXSM-1-9953; Closed
CSCea76835	REG4: HD flooded too many cluster file msg during pxm burnboot; Closed
CSCea80411	UPGRD: after power-cycle, the standby continuous reset reason 43; Closed
CSCea82872	AXSM should not update its TOD information from feeder; Closed
CSCea83922	REG4:switchcc fr PXM45/C slot 8 to pxm45B slot7 caused xbar alarm; Duplicated to CSCea72239
CSCea85519	UPGRD: Active Card resets STBY Card due to protocol timeout; Duplicated to CSCea73429
CSCea91276	PXM experiences on-line diag failure; Closed
CSCea92433	ipc memory buffer indicates that nb free fl is 11; Duplicated to CSCea75060
CSCea92845	Customer could not upgrade boot code; Closed

Known Route Processor Module or MPLS Anomalies

For information about anomalies with the RPM-PR or RPM/B card, refer to "Release Notes for Cisco MGX Route Processor Module (RPM/B and RPM-PR) for MGX Release 1.2.21 and MGX Release 4.0.10."

For information about anomalies with the RPM-XF card, refer to "Release Notes for Cisco MGX Route Processor Module (RPM-XF) for MGX 8850 Release 4.0.10 (PXM45)."

MGX-RPM-XF-512 Anomalies

The new MGX-RPM-XF-512 card supports MGX 8850 (PXM45), Release 4.0.10.

For information about anomalies with the MGX-RPM-XF-512 card, refer to "Release Notes for Cisco MGX Route Processor Module (RPM-XF) for Release 4.0.10 of MGX 8850 (PXM45)".

Acronyms

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

Table 36 Acronyms Used in these Release Notes 

Acronym	Description
AXSM	ATM Switch Service Module
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 "Related Documentation" section.

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

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

Copyright © 2003, 2004 Cisco Systems, Inc.
All rights reserved.