Guest

Cisco MGX 8800 Series Switches

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

 Feedback

Table Of Contents

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

Contents

About Release 4.0.15

Type of Release

Locating Software Updates

New Features and Enhancements in Release 4.0.15

Frame Discard Feature

New Features and Enhancements in Release 4.0.12

Point-to-Multipoint Support

Capabilities

Crossbar Limitations

AXSM/A Limitations

AXSM/B Limitations

AXSM-E Limitations

PXM1E Limitations

New Features and Enhancements in Release 4.0.11

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 Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

Hardware Supported

New Hardware

New Hardware in Release 4.0.15

New Hardware in Release 4.0.12

New Hardware in Release 4.0.11

New Hardware in Release 4.0.10

New Hardware in 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.15

Limitations

PXM1-E Parity Errors

Upgrading to 4.0.10

Higher Level Logical Link Limits

CLI Upgrade

Preferred Route

PXM45/C

192 Signaling Interfaces

Closed User Group (CUG)

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

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

Notes

Changes to this Document

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

Obtaining Technical Assistance

Cisco Connection Online

Technical Assistance Center

Caveats

MGX 8850, MGX 8830, and MGX 8950 4.0.15 Anomalies

Known Anomalies in Release 4.0.15

Anomalies Resolved in Release 4.0.15

Anomaly Status Change from Previous Release

MGX 8850, MGX 8830, and MGX 8950 4.0.12 Anomalies

Anomalies Resolved in Release 4.0.12

MGX 8850, MGX 8830, and MGX 8950 4.0.11 Anomalies

Anomalies Resolved in Release 4.0.11

MGX 8850, MGX 8830, and MGX 8950 4.0.10 Anomalies

Anomalies Resolved in Release 4.0.10

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


Contents

About Release 4.0.15

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

Type of Release

Release 4.0.15 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.15 software:

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

New Features and Enhancements in Release 4.0.15

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.

New Features and Enhancements in Release 4.0.12

Point-to-Multipoint Support

The SVC/SPVC point-to-multipoint (P2MP) feature offers the ability for an endpoint (termed the root endpoint) to establish a simple tree topology to multiple endpoints (termed leaf endpoints). The data traffic is uni-directional in the direction from the root to all the leaves. When P2MP calls are established using signaling, leaves can be added to a root endpoint using SETUP/ADD_PARTY signaling messages. Point-to-multipoint is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.01 specs. The implementation is compliant with in Q2971.

P2MP calls can also be setup by provisioning a `root' endpoint using the addcon CLI command. The `leaf' endpoints can then be added by using the addparty CLI command.

There are finite limits on the numbers of p2mp connections that can be supported on different MGX platforms. Table 1 depicts this.

Table 1 Point to Multipoint Support

 
MGX 89501
MGX 88502
BPX/SES
MGX 8830

Total number of connections (p2p and p2mp)

250000

250000

100000

27000

Total number of P2MP connections2

5000

5000

500

500

Number of parties per P2MP connection3

1000 4

1000

100

100

Number of branches

128

128

1

32

Number of parties per node

10000

10000

1000

1000

1 P2MP feature is supported only on PXM45/B or PXM45/C.

2 This is the number of P2MP roots that can be setup on a node

3 The number of parties for a given P2MP connection can be more than the number of leaves on that connection. There can be multiple endpoint references on a given leaf endpoint

4 This is the number of P2MP roots that can be setup on a node.


The capability to replicate ATM traffic on MGX varies with the type of hardware used. A brief note on the replication mechanism in MGX will help the user understand the limitations associated with specific hardware.

Figure 1 Replicating Traffic

In Figure 1, D1 - D4 are destination cards in a MGX node A. S1 is a source card on Node A, where the root endpoint of the P2MP connection is provisioned. In this example, there is a P2MP connection which has leaves on D1 and D3 of node A and on D1 and D4 of node B. The first stage of multicast is called the slot multicast. This is performed by the crossbar module on the MGX. Although the replication takes place on the crossbar, the slots towards which replication should take effect is instructed by the source card S1 on node A. After slot multicast cells arrive on the replication engines on slots D1 and D3 of node A. Here the second stage of multicast is performed by the destination cards and is termed port multicast. Port multicast on slot D1 (node A) delivers data to a leaf on one of its port and to a branch on another of its port. On the slot D3 (node A) there exists only one leaf endpoint. Data from the branching point is delivered to S1 of node B. Here again there is a slot multicast operation followed by port multicast at each of the destination card slots (D1 and D4).

It should be noted that some of the destination cards may not be able to perform port multicast operation. For example, in the above example if D4 on node B is incapable of doing port multicast and if there were to be multiple leaves on it, the replication needs to be performed at D1 on node A. This would mean that there would be two connections carrying the same data from node A to node B.

Capabilities

Table 2 lists multicast capabilities by card.

Table 2 Multicast Capabilities by Card

 
AXSM/A
AXSM/B
AXSM-E
AXSM-XG
PXM1E

Slot Multicast

YES

YES

YES

YES

NO

Port Multicast

YES

YES

NO1

YES

NO

1 Only one leaf is supported on AXSM-E. Please see section on AXSM-E limitations


Crossbar Limitations

The MGX 8850 is equipped with a maximum of 8 switching planes on the crossbar module. MGX 8950 can have as many as 16 switching planes on the crossbar module.

Most of the broadband SMs (AXSM-A, AXSM-B, AXSM-E, FRSM12, RPM-XF) have access to just 8 switching planes. The AXSM-XG is the only broadband SM that can access all 16 switching planes (however, it can use all 16 of them only on a MGX 8950).

When there is unicast traffic to be sent from source card S1 to destination D1, S1 would put forth a request on any of the available 8 / 16 switch planes. The crossbar would negotiate access to the destination slot D1 on the requested switch plane. If the destination grants the request, the cell is transferred from S1 to D1 on the requested switch plane. If not granted (for some reason serial link from crossbar to D1 is busy/down), then S1 would attempt on other switch planes.

However, in case of multicast traffic, the crossbar accepts multicast root cells from S1 (without negotiating access to all possible destination slots) and makes best effort to forward cells to all relevant destination slots.

This leads to the following limitations:

· If the serial link between the crossbar and the destination slot is brought down (either administratively or by online diagnostics), the multicast cells destined on that serial link will never depart the crossbar. This will cause loss of multicast traffic. This will not impact unicast traffic, as the source card would have been denied access on that switching plane, which would then force the source card to attempt sending on other serial links.

· In the case of a MGX 8950, the AXSM-XG hardware would enable the use of all 16 serial links. However, if the AXSM-XG is sending traffic towards an AXSM-A (or any card which supports only 8 serials), there can be effectively only 8 serial links that can be really functional. In case of unicast traffic, the 8-link limit gets enforced because of the end-to-end negotiation between source and destination cards. However, in case of multicast traffic, the crossbar absorbs traffic from the source card on all 16 links and will drop traffic on 8 of them (as the destination cannot take it). This implies that on a MGX 8950, the P2MP feature works reliably only if a chassis is populated only with AXSM-XG cards. This limitation however, does not impact unicast traffic.

AXSM/A Limitations

To understand these limitations a brief description of the serial bus request generation mechanism towards crossbar is needed:

The crossbar is configured for `Unicast preferred' implying that it will honor requests from the service modules in the following order (for a specific destination slot):

Unicast Primary w/ speedup

Multicast Primary w/ speedup

Unicast Primary

Multicast Primary

Unicast Secondary

The broadband service modules can generate two types of requests (primary and secondary) for unicast traffic based on the number of switch planes and number of cells in the input queue. And the service modules can generate one "Unicast Primary" and multiple "Unicast secondary" requests at any point of time (every S-Tick). The limitation in AXSM/A has to do with not supporting the speedup option in its request towards the crossbar.

Suppose a source card has 8 cells in the queue for the same destination and switch is made of 4 switch planes, the source card will generate one "Unicast Primary" and 3 "Unicast secondary" requests. For multicast traffic there is no secondary request, all multicast requests are primary only. There could be a scenario where multiple source cards are trying to send both "Unicast" and "multicast" traffic to the same (congested) destination. In that case, one source card's "Multicast primary" request can win over the other source cards "Unicast secondary requests". Traffic from only one source card to the same destination will not be an issue as the card gives priority to unicast traffic.

Example 1

Card A is sending OC48 CBR unicast traffic to Card B.
Card C is sending OC24 UBR multicasttraffic to Card B.
Card B can sink in only OC48 worth of traffic from A and C.
Result: Card A will see some ingress discards. The same behavior will be seen for unicast 
traffic as well. This stems from the fact that card A cannot assert speedup requests 
towards the crossbar in order to assure guaranteed traffic.
Example 2
Card A is sending OC24 CBR multicast traffic to Card B.
Card C is sending OC48 UBR unicast traffic to Card B.
Card D is sending OC48 UBR unicast traffic to Card B.
Card B can sink in only OC48 work of traffic from A, C and D.
Result: Card A will see some ingress discards.

AXSM/B Limitations

AXSM-B hardware resolved the issue of `speedup' signal assertion. Thus the above mentioned problem was addressed.

However, both AXSM-A and AXSM-B have a common limitation. During the `port multicast' performed at the destination cards, the multicast root cells are replicated and queued on to several leaf connections. The root cells are queued up in a cache while awaiting replication. This cache is about 32 cell deep. When there is a burst of traffic from several different P2MP connections and if the replication is not done fast enough, there is a possibility of cache overflow. This results in loss of data on multicast connections.

AXSM-E Limitations

AXSM-E hardware does not support the `port multicast' operation. However, when used as a trunk, AXSM-E would be required to carry P2MP calls, without having to perform the branching (or replication) functionality. PNNI recognizes this limitation of AXSM-E and ensures that branching is not done on an AXSM-E, when it is an AXSM-E port is used as a trunk.

Because of the same limitation, AXSM-E can host only a single leaf of a multicast connection. It should be noted that when several P2MP parties (leaves) are added to a P2MP connection, only one leaf could be terminated on an AXSM-E for a given P2MP connection

In this release there is yet another limitation for leaves terminated on AXSM-E. If there are multiple leaves terminated on a node and if one of the leaves terminates on an AXSM-E (note that there can be only one leaf on AXSM-E), then it is likely that the call setup to the AXSM-E leaf may not setup reliably (i.e. if there is a de-route/re-route of the connection, there is no guarantee on the leaf call setup)

However, if there is only one leaf in the node and this leaf is on an AXSM-E, the call setup to the AXSM-E will be setup reliably.

PXM1E Limitations

PXM1E does not support branching (for p2mp connections) in this release. PXM1E can however be a via node for p2mp connections in 4.0.15.

New Features and Enhancements in Release 4.0.11

None.

Features and Enhancements in Previous Release 4.0.10

The new features in Release 4.0.10 are listed inTable 3.

:

Table 3 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 (PXM45) and new on MGX 8950.



Note 2. Except for Cell Bus Service Module


LMI AutoSense

The LMI AutoSense feature on the Frame Relay 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)

MGX 8830 (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)

MGX 8950 (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:

MGX 8850(PXM45, PXM1E)

MGX 8950

MGX 8830

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 4 lists which switch supports which new feature.

Table 4 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)

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

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 4 for details.

Platform

MGX 8850 (PXM45)


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


Table 5 Cell Bus Service Modules (CBSMs) Supported in Release 4.0.00, 4.0.10, 4.0.11, and 4.0.12 

 
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

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 *

NO

NO

NO

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 release 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 6 were introduced in Release 4.0.00.

Table 6 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 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. 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:

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

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

PORT SCT 6 - Policing disabled, used for trunks

CARDand PORT SCT 52 - Policing enabled on PNNI, disabled on MPLS

PORT SCT 53 - Policing disabled on PNNI and MPLS

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

PORT SCT 55 - Policing disabled on PNNI and MPLS

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

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

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

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

AXSME_SCT.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:

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

PORT SCT 100(OC192), 200(OC48), 300(OC12), 400(OC3), 500(DS3) - Policing disabled on PNNI and MPLS

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

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

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

The checksum is:

AXSMXG_SCT.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 Compatibility Matrix

Table 7 lists Cisco WAN or IOS products that are compatible with Release 4.0.15.

Table 7 MGX 4.0.15 Release Compatibility Matrix 

Switch or Component
Certified Software Version

MGX 8230 (PXM1)

MGX 8250 (PXM1)

MGX 8850 (PXM1)

MGX 1.2.21**

MGX 1.2.13

MGX 1.2.0.2

MGX 1.1.34

MGX 8850 (PXM45)

MGX 8850 (PXM1E)

MGX 8950 (PXM45)

MGX 8830 (PXM1E)

MGX 4.0.15**

MGX 4.0.12

MGX 4.0.10

MGX 3.0.25**

MGX 3.0.23**

MGX 3.0.20

MGX 2.1.81**

BPX Switch Software:

9.4 Release, 9.4.10**

9.3 Release, 9.3.36, 9.3.47**

9.2 Release, Switch Software 9.2.43

BPX SES Shelf:

SES 4.0.15**

SES 4.0.10

SES 3.0.25**

SES 3.0.23

SES 3.0.20

SES 1.1.75

Cisco WAN Manager

CWM 12.0.00 Patch 1.1**

CWM 12.0.00 Patch 2**

MGX 8220 Shelf:

MGX 8220 4.1.12

MGX 8220 5.0.20**

MGX 8220 5.0.19

VISM-PR

VISM Release 3.1.2**

VISM Release 2.2.1

IOS RPM-PR

12.3(2)T5**

IOS RPM-XF

12.3(2)T5**


** Releases that are certified with 4.0.15

MGX and RPM Software Version Compatibility Matrix

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

Table 8 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.015.202_bt.fw

4.0.15

pxm45_004.000.015.202_mgx.fw

4.0.15

4.0.15

PXM45/B

PXM45/C

PXM1E-4-155 (MGX 8850 (PXM1E) chassis)

pxm1e_004.000.015.202_bt.fw

4.0.15

pxm1e_004.000.015.202_mgx.fw

4.0.15

4.0.15

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.015.202_bt.fw

4.0.15

pxm1e_004.000.015.202_m30.fw

4.0.15

4.0.15

PXM1E-8-T3E3 (MGX 8830 chassis)

PXM1E-T3E3-155 (MGX 8830 chassis)

AXSM-1-2488

axsm_004.000.015.202_bt.fw

4.0.15

axsm_004.000.015.203.fw

4.0.15

4.0.15

AXSM-16-155

AXSM-4-622

AXSM-16-T3/E3

AXSM-1-2488/B

axsm_004.000.015.202_bt.fw

4.0.15

axsm_004.000.015.203.fw

4.0.15

4.0.15

AXSM-16-155/B

AXSM-4-622/B

AXSM-16-T3/E3/B

AXSM-2-622-E

axsme_004.000.015.202_bt.fw

4.0.15

axsme_004.000.015.202.fw

4.0.15

4.0.15

AXSM-8-155-E

AXSM-16-T3E3-E

AXSM-32-T1E1-E

AXSM-4-2488-XG

axsmxg_004.000.015.202_bt.fw

4.0.15

axsmxg_004.000.015.202.fw

4.0.15

4.0.15

AXSM-1-9953-XG-

FRSM-12-T3E3

frsm12_004.000.015.202_bt.fw

4.0.15

frsm12_004.000.015.202.fw

4.0.15

4.0.15

MGX-SRME

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

SRM-3T3/C

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

AX-CESM-8E1

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

AX-CESM-8T1

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

MGX-CESM-8T1/B

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

MGX-AUSM-8T1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

1.0.02

ausm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

MGX-AUSM-8E1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

1.0.02

ausm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

AX-FRSM-8T1

frsm_8t1e1_FR8_BT_1.0.02.fw

1.0.02

frsm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

AX-FRSM-8E1

frsm_8t1e1_FR8_BT_1.0.02.fw

1.0.02

frsm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

AX-FRSM-8T1-C

frsm_8t1e1_FR8_BT_1.0.02.fw

1.0.02

frsm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

AX-FRSM-8E1-C

frsm_8t1e1_FR8_BT_1.0.02.fw

1.0.02

frsm_8t1e1_021.000.012.200.fw

21.0.12

21.0.12

MGX-FRSM-HS2/B

frsm_vhs_VHS_BT_1.0.06.fw

1.0.06

frsm_vhs_021.000.012.200.fw

21.0.12

21.0.12

MGX-FRSM-2CT3

frsm_vhs_VHS_BT_1.0.06.fw

1.0.06

frsm_vhs_021.000.012.200.fw

21.0.12

21.0.12

MGX-FRSM-2T3E3

frsm_vhs_VHS_BT_1.0.06.fw

1.0.06

frsm_vhs_021.000.012.200.fw

21.0.12

21.0.12

MGX-RPM-PR-256

rpm-boot-mz.123-2.T5

12.3(2)T5

rpm-js-mz.123-2.T5

12.3(2)T5

12.3(2)T5

MGX-RPM-PR-512

rpm-boot-mz.123-2.T5

12.3(2)T5

rpm-js-mz.123-2.T5

12.3(2)T5

12.3(2)T5

MGX-RPM-XF-512

rpmxf-boot-mz.123-2.T5

12.3(2)T5

rpmxf-p12-mz.123-2.T5

12.3(2)T5

12.3(2)T5

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.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.15 from a minimum Release of 2.1.80.

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

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

You must use minimum release of CWM Release 12.0.0 Patch 1.1 to manage networks that contain MGX switches running Release 4.0.15.

The RPM-PR and RPM-XF software in this release is based on IOS release 12.3(2)T5.

The SNMP MIB release for 4.0.15 is mgx8850rel4010mib.tar.

Table 9 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 9 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

This section lists hardware introduced in MGX 4.x releaess.

New Hardware in Release 4.0.15

MGX-2GE

MGX-2OC12POS

New Hardware in Release 4.0.12

No new hardware.

New Hardware in Release 4.0.11

No new hardware.

New Hardware in Release 4.0.10

No new hardware.

New Hardware in 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 10 lists MGX 8850 (PXM45/PXM1E) and MGX 8830 APS connectors.

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

In Table 11, 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 11 Card Numbers and Revisions Supported in Release 4.0.15 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-2GE

800-20831-04

-B0

MGX-1OC12POS-IR

800-08359-05

-A0

MGX-2OC12POS-IR

800-21300-04

-B0

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-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 12 lists MGX 8850 (PXM45) front and back card types and whether APS connectors are supported in 4.0.10.

Table 12 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-RJ48-8E1

MGX-SRME

MGX-SMFIR-1-155

Yes

MGX-STM1-EL-1

Yes

MGX-SRM-3T3/C

MGX-BNC-3T3-M

MGX-RPM-PR-256
MGX-RPM-PR-512

MGX-MMF-FE

MGX-RJ45-4E/B

MGX-RJ45-FE

MGX-RPM-XF-512

MGX-XF-UI

MGX-1GE

MGX-2GE

MGX-1OC12POS-IR

MGX-2OC12POS-IR

MGX-GE-LHLX1

MGX-GE-SX1

MGX-GE-ZX1

AX-CESM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

MGX-CESM-8T1/B

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-FRSM-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

AX-FRSM-8T1-C

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-FRSM-8E1-C

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

AX-FRSM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

MGX-FRSM-2CT3

MGX-BNC-2T3

MGX-FRSM-2T3E3

MGX-BNC-2E3

MGX-BNC-2T3

1 Small form factor pluggable optical transceivers for MGX-1GE and MGX -2GE back cards.


MGX 8850 (PXM1E) Product IDs and Card Types

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

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

Table 13 Card Numbers and Revisions Supported in Release 4.0.15 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 14 MGX 8850 (PXM1E) Front and Back Card Types and Supported APS Connectors 

Front Card Type
Back Card Types
Needs APS-CON?

PXM1E-8-155

SFP-8-155

Yes

MCC-8-155

Yes

MMF-1-155-SFP1

Yes

SMFLR-1-155-SFP1

Yes

SMFIR-1-155-SFP1

Yes

PXM-UI-S3/B

PXM1E-4-155

MMF-4-155/C

Yes

SMFIR-4-155/C

Yes

SMFLR-4-155/C

Yes

PXM-UI-S3/B

PXM1E-8-T3E3

SMB-8-T3

SMB-8-E3

PXM-UI-S3/B

PXM1E-16-T1E1

PXM-UI-S3/B

MCC-16-E1

RBBN-16-T1E1

PXM1E-COMBO (see the 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-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

MGX-RPM-PR-256
MGX-RPM-PR-512

MGX-MMF-FE

MGX-RJ45-4E/B

MGX-RJ45-FE

MGX-AUSM-8T1/B

AX-RJ48-8T1

AX-R-RJ48-8T1

MGX-AUSM-8E1/B

AX-SMB-8E1

AX-R-SMB-8E1

MGX-RJ48-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-CESM-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

MGX-CESM-8T1/B

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-FRSM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-FRSM-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

AX-FRSM-8T1-C

AX-RJ48-8T1

AX-R-RJ48-8T1

AX-FRSM-8E1-C

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

MGX-FRSM-HS2/B

SCSI2-2HSSI/B

MGX-12IN1-8S

MGX-FRSM-2CT3

MGX-BNC-2T3

MGX-FRSM-2T3E3

MGX-BNC-2E3

MGX-BNC-2T3

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



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


MGX 8830 Product IDs and card types

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

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

Table 15 Card Numbers and Revisions Supported in Release 4.0.15 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-UI-S3/B

800-21557-01

-A0

PXM1E-4-155

800-18588-03

-A0

PXM1E-8-T3E3

800-18590-03

-A0

PXM1E-16-T1E1

800-18658-04

-A0

PXM1E-COMBO (See note below)

800-18604-03

-A0

MMF-4-155/C

800-07408-02

-A0

SMFIR-4-155/C

800-07108-02

-A0

SMFLR-4-155/C

800-07409-02

-A0

SMB-8-T3

800-05029-02

-A0

SMB-8-E3

800-04093-02

-A0

MGX-T3E3-155

800-18698-02

-A0

MMF-1-155-SFP1

10-1308-01

-A0

SMFLR-1-155-SFP1

10-1280-01

-A0

SMFIR-1-155-SFP

10-1283-01

-A0

MCC-16-E1

800-19853-02

-A0

RBBN-16-T1E1

800-21805-03

-A0

MGX-SRME

800-14224-02

-A0

MGX-SRM-3T3/C

800-05648-01

-A0

MGX-BNC-3T3-M

800-03148-02

-A0

MGX-SMFIR-1-155

800-14460-02

-A0

MGX-STM1-EL-1

800-14479-02

-A0

MGX-RPM-PR-256

800-07178-02

-A0

MGX-RPM-PR-512

800-07656-02

-A0

MGX-MMF-FE

800-03202-02

-A0

MGX-RJ45-4E/B

800-12134-01

-A0

MGX-RJ45-FE

800-02735-02

-A0

MGX-RJ48-8E1

800-19310-01

-B0

MGX-AUSM-8T1/B

800-04809-01

-A0

MGX-AUSM-8E1/B

800-04810-01

-A0

AX-CESM-8E1

800-02751-02

-A0

MGX-CESM-8T1/B

800-08613-02

-A0

AX-FRSM-8T1

800-02437-04

-A0

AX-FRSM-8E1

800-02438-04

-A0

AX-FRSM-8T1-C

800-02461-04

-A0

AX-FRSM-8E1-C

800-02462-04

-A0

AX-SMB-8E1

800-02287-01

-A0

AX-R-SMB-8E12

800-02410-01

-A0

AX-RJ48-8E1

800-02408-01

-A0

AX-R-RJ48-8E1

800-02409-01

-A0

AX-RJ48-8T1

800-02286-01

-A0

AX-R-RJ48-8T1

800-02288-01

-A0

MGX-12IN1-8S

800-18302-01

-A0

MGX-FRSM-HS2/B

800-17066-01

-A0

MGX-FRSM-2CT3

800-06335-01

-D0

MGX-FRSM-2T3E3

800-02911-07

-D0

MGX-BNC-2T3

800-04057-02

-A0

MGX-BNC-2E3

800-04056-02

-A0

SCSI2-2HSSI/B3

800-05463-02

-A0

800-05501-01

-A0

MGX-VISM-PR-8E1

800-07991-02

-A0

MGX-VISM-PR-8T1

800-07990-02

-A0

1 These cards are required only if you need modular optics with the PXM1E-COMBO back card.

2 R means this is a redundant card.

3 The SCSI2-2HSSI/B card has two different 800 part numbers, and both part numbers are valid.


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

Front Card Type
Back Card Types
Needs APS-CON?

PXM1E-8-155

SFP-8-155

Yes

MCC-8-155

Yes

PXM-UI-S3/B

PXM1E-4-155

MMF-4-155/C

Yes

SMFIR-4-155/C

Yes

SMFLR-4-155/C

Yes

PXM-UI-S3/B

PXM1E-8-T3E3

SMB-8-T3

SMB-8-E3

PXM-UI-S3/B

PXM1E-COMBO (See note below.)

MGX-T3E3-155

No

MMF-1-155-SFP1

SMFLR-1-155-SFP1

SMFIR-1-155-SFP1

PXM-UI-S3/B

PXM1E-16-T1E1

MCC-16-E1

RBBN-16-T1E1

PXM-UI-S3/B

MGX-SRME

MGX-SMFIR-1-155

No

MGX-STM1-EL-1

No

MGX-SRM-3T3/C

MGX-BNC-3T3-M

MGX-RPM-PR-256
MGX-RPM-PR-512

MGX-MMF-FE

MGX-RJ45-4E/B

MGX-RJ45-FE

MGX-AUSM-8T1/B

AX-RJ48-8T1

AX-R-RJ48-8T1

MGX-AUSM-8E1/B

AX-SMB-8E1

AX-R-SMB-8E1

MGX-RJ48-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

AX-CESM-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

AX-CESM-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

   

MGX-CESM-8T1/B

AX-RJ48-8T1

AX-R-RJ48-8T1

   

AX-FRSM-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

AX-FRSM-8T1-C

AX-RJ48-8T1

AX-R-RJ48-8T1

   

AX-FRSM-8E1-C

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

MGX-FRSM-HS2/B

SCSI2-2HSSI/B

MGX-12IN1-8S

MGX-FRSM-2CT3

MGX-BNC-2T3

MGX-FRSM-2T3E3

MGX-BNC-2E3

MGX-BNC-2T3

MGX-VISM-PR-8T1

AX-RJ48-8T1

AX-R-RJ48-8T1

   

MGX-VISM-PR-8E1

AX-SMB-8E1

AX-R-SMB-8E1

AX-RJ48-8E1

AX-R-RJ48-8E1

MGX-RJ48-8E1

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



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


MGX 8950 Product IDs and card types

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

Table 18 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 17 Card Numbers and Revisions Supported in Release 4.0.15 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

MGX-2GE

800-20831-04

-B0

MGX-2OC12POS-IR

800-21300-04

-B0

MGX-1OC12POS-IR

800-08359-05

-A0

MGX-1GE

800-18420-03

-A0


Table 18 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-2GE

MGX-1OC12POS-IR

MGX-2OC12POS-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 command in Release 4.0.15.

The following commands were new or changed in Release 4.0.12:

addlink, dellink

cnfscmpollparms, dspscmpollparms

dspchancnt

dspclksrc

dsppnportcac, dsppnportrsrc

dsplog

dsplns, dspapslns, dspapsln

dumpconfigs

dumptrace, upallports, dnallports, dspdeverr, dspdevhist

There were 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.15

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

Limitations

Upgrading AXSM-XG cards

To upgrade AXSM-XG cards from an older Release 4 to a current Release 4, all other AXSM cards in the chassis should be running a Release 4. This is necessary because AXSM-XG card requires all other service module cards in the shelf support reception of IPC Version 2 (64 bit aligned) messages. The following error is displayed on the CLI during the upgrade if this restriction is not met:

ERR: Requested revision has IPC incompatibility with other card(s) in shelf. Make sure all cards are running the same major revision.

The following problems occur when a delpart command is executed:

2 ports with different physical ids but the same logical port id can exist on the PXM in a rare error case related to a delpart command. To avoid this problem, the network administrator should do the following: (CSCeb77548)

If a delpart command has been used on a port with phyId X and ifId Y, before re-using the same ifId Y to do an addpart on a port with a different phyId Z, do the following: A delpnport command should be done for port X on the PXM to ensure that the earlier port (X) is completely deleted from the PXM.

If any form of pre-provisioning has been done on a port on the PXM, (e.g. dnpnport followed by uppnport), if a delpart is now done for this port, trap 70006 is not sent to the CWM. In this case, the trunk will not be deleted from CWM (CSCeb81958)

"delpnport" from CWM does not delete a port on the PXM if a "delpart" command had been used on the port earlier from the Service Module. (CSCeb78837)

A PNNI link is deleted using delpart but shown in major alarm in the network Monitor of CWM because the trap 70006 is not sent to CWM. In this case, the trunk will not be deleted from CWM. (CSCin55488, this is similar to CSCeb81958.)

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


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, document the routes before starting the upgrade.

PXM1-E Parity Errors

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

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

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.

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

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.

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 segment OAM loopback cells per card and not per connection, the 1,500 cps assumes an even flow rate.

CLI Configurable Access

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

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

Only the switch software is allowed to generate the binary file. This file has an authentication signature which has to be validated before the file can be used. Any manual changes to the file would make the file void.

If the binary file becomes corrupted, then the command access levels revert back to the default values during the card bring-up. To recover, repeat the installation process or retain a copy of the binary file and do cnfcli accesslevel install on that service module.

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

If replication to standby failed, the installation process failed.

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

Controller Card Mastership Sanity Verification

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

Serial Bus Path Fault Isolation

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

Cell Bus Path Fault Isolation and Recovery

The following notes pertain to cell bus path faults:

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

The isolation procedures isolate the Cell Bus path failures to the active controller card only. This means, it is determined whether the active controller card has the fault for the inter-card communication over the Cell Bus from the active controller card to the Service Modules and the standby controller card or not. It does not isolate the fault if the active controller card fails to communicate with some cards and successfully communicates with the rest on the Cell Bus.

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

Only the failures detected by periodic polling triggers the isolation procedures. Failures reported from other sources in the system against a Service Module or the standby controller card due to the Cell Bus path failures don't initiate the isolation procedures, and which results in resetting that card against which the failure is reported, even while the active controller card is in the process of isolating the Cell Bus path failures triggered by the polling failures.

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

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

FRSM-12-T3E3

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


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


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

BERT is not supported.

Sub-rate DS3 is not supported.

Online and Offline Diagnostics is not supported.

Complete core dump is not supported.

Port and Connection Limitations

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

Port limitations:

4 bytes header length with Stratacom LMI is not supported

LMI on Frame Forwarding port is not supported

If LMI is configured, Port header length cannot be changed

Connection Limitations:

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

The command chanType cannot be modified

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

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

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

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

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

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

If the connection is in loopback, it cannot be modified

CIR can only be 0 for UBR connections

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

If CIR not equals to 0, Bc should be nonzero

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

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

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

Maximum connections depending on LMI type:

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

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

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

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

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

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

Disk Space Maintenance

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

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 3.0.00 is not compatible with the path and connection trace available with previous releases.

Path and Connection trace supports point to point connections.

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

Simple Network Timing Protocol (SNTP)

The CWM MIB is not supported in 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.

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.15, 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) IOS Release 12.3(2)T5 for MGX Releases 1.2.21 and 4.0.15" and "Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for MGX 8850 and MGX 8950 Release 4.0.15 (PXM45)".These release notes are available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm.

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 2

Standard APS Configuration

Figure 3

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 19 describes the configurable parameters for the cnfapsln command.

Table 19 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 20 describes the configurable parameters for the cnfapsln command.

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


Note Table 21 is updated for Release 3.0.00.


Table 21 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 22 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 22 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 22 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

MGX 4.0.15 January 2004

Documentation

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

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.

Changes to this Document

Table 23 describes changes made to these release notes that caused the release notes to go from OL-5178-01 Rev. A0 to OL-5178-01 Rev. B0 on March 7, 2004. The revision was made because MGX 4.0.15 is now qualified to work with IOS 12.3(2)T5.

Table 23 Changes that Caused Revision B of this Document

Section
Change

Table 7

12.2(15)T5 was replaced with 12.3(2)T5, and versions of code were updated accordingly.

Table 8

Replaced 12.2(15)T5 with 12.3(2)T5

Replaced rpm-boot-mz.122-15.T5 with rpm-boot-mz.123-2.T5

Replaced rpm-js-mz.122-15.T5 with rpm-js-mz.123-2.T5

Repaced rpmxf-boot-mz.122-15.T5 with rpmxf-boot-mz.123-2.T5

Replaced rpmxf-p12-mz.122-15.T5 with rpmxf-p12-mz.123-2.T5

The bullet before Table 9

"The RPM-PR and RPM-XF software in this release is based on IOS release 12.2(15)T5" was changed to "The RPM-PR and RPM-XF software in this release is based on IOS release 12.3(2)T5."

Table 23

This "Changes to this Document" section was added to describe why the document was revised to Revision B.

"Preferred Route" section

The term "non-MSSBU" was changed to "non-MGX."


Table 24 describes changes that caused the release notes to go from OL-5178-01 Rev. B0 to OL-5178-01 Rev. C0 on March 16, 2004. The revision was made because MGX 4.0.15 interoperates with a new version of IOS that now suports additional RPM cards.

Table 24 Changes that Caused Revision C of this Document 

Section
Change

"New Hardware in Release 4.0.15" section

Added MGX-2GE and MGX-2OC12POS cards.

Table 11

Added MGX-2GE and MGX-2OC12POS-IR cards.

Table 12

Added MGX-2GE and MGX-2OC12POS-IR to MGX-RPM-XF-512

Table 17

Added MGX-2GE and MGX-2OC12POS-IR.

Table 18

Added MGX-2GE and MGX-2OC12POS-IR to MGX-RPM-XF-512.

"RPM-PR and RPM-XF Limitations" section

Added updated RPM release note titles.


Related Documentation

This "Related Documentation" section describes the technical manuals and release notes listed in the "Guide to Cisco Multiservice Switch Documentation." The 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 25 lists the product documentation for the Cisco WAN Manager (CWM) network management system for Release 12.

Table 25 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 26 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM45) Multiservice Switch Release 4.

Table 26 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 27 lists the product documentation for the installation and operation of the Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4.

Table 27 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 28 lists the product documentation for the installation and operation of the Cisco MGX 8950 Multiservice Switch Release 4.

Table 28 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 29 lists product documentation for understanding, installing, and operating the Service Expansion Shelf (SES) Private Network-to-Network Interface (PNNI) Controller.

Table 29 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 30 lists the product documentation for the installation and operation of the Cisco MGX 8830 Multiservice Switch Release 4.

Table 30 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 31 lists the product documentation for the installation and operation of the Cisco WAN Switching Software Release 9.4.

Table 31 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 32 lists the product documentation for the installation and operation of the Cisco MGX 8850 Edge Concentrator.

Table 32 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 33 lists the product documentation for the installation and operation of the Cisco MGX 8250 Edge Concentrator.

Table 33 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 34 lists the product documentation for the installation and operation of the Cisco MGX 8230 Edge Concentrator.

Table 34 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.

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online 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.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, 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 CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

WWW: www.cisco.com

Telnet: cco.cisco.com

Modem using standard connection rates and the following terminal settings: VT100 emulation; 8 data bits; no parity; and 1 stop bit.

From North America, call 408 526-8070

From Europe, call 33 1 64 46 40 82

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language
E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com


In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Caveats

This section provides information about known anomalies.

MGX 8850, MGX 8830, and MGX 8950 4.0.15 Anomalies

Anomalies are organized as follows:

Known Anomalies in Release 4.0.15

Anomalies Resolved in Release 4.0.15

Anomalies Status Change from Previous Release

Anomaly
Description

CSCdv32986

Symptom: SAR doesn't service some connection after starting and stopping data several times.

Conditions: Initiate the data traffic. Stop and start it again for several time. Sar will stop servicing for some connections.

Workaround: None

Headline: 100% data is getting dropped on some connections

Hardware: frsm-vhs

CSCdy23797

Symptom: pntrace commands not completely documented

Conditions: None

Workaround: None.

Headline: command needs to be updated in documentation

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

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

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

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






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

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 modifed to show the device No.

Hardware: pxm1e

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

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

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

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

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 NBSMs are not accurate

Conditions: PM parameters on NBSMs 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

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

CSCeb20570

Symptom: multiple instances of firmware ready/not ready and CBC ready/not ready in event log

Conditions: switchcc was executed

Workaround: Unknown

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

Hardware: PXM45/B

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

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

CSCeb35883

Symptom: Port stays in alarm when line is in logical loopback.

Conditions: When line is put into logical loopback on FRSM-HS2/B card with HS1_2HSSI backcard interface, port did not come out of alarm.

Workaround: None

Headline: FRSM-HS2/B port in alarm when line is in logical loop

Hardware: frsm-vhs

CSCeb38659

Symptom: On PXM45 node, the AINI port goes into vc failure.

Conditions: Executed the command resetsys.

Workaround: Perform the commands dnpnport and uppnport.

Headline: resetsys on PXM45 causes AINI port to vc failure

Hardware: PXM45/B

CSCeb38846

Symptom: Remote Line/Port loopback option not available in FRSM8T1/E1 for MGX-2 which is available in MGX-1

Reports following error : switch.a.PXM. > cnfbert -cbif 17.1.0 -pat 1 -lpbk 15 -sbe 1 -en 4 Error!! Bert Pattern could not sync. Test failed Error!! BERT pattern could not sync.

Conditions: feature not available in cnfbert command

Workaround: None

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






CSCeb47830

Symptom: SSI exception error

Conditions: snmpSA malfunctioned

Workaround: None

Headline: AXSME - ssi exception error: snmpSA crash

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

CSCeb49614






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

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

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

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

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

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

CSCeb72485

Symptom: The CESM port will get stuck in RcvAIS due to an alarm loop.

Conditions: This should be specific to a hard loopback or to equipment that transmits back exactly the same T1 state as received (without interpretation).

With a test set or any equipment on one end of a CESM connection and a loopback on the remote end when there is an ATM PVC failure, there is an alarm loop which prevents the circuit from coming up even after the ATM PVC is restored.

Workaround: Once in this state, to recover the line alarm must be cleared.

This can be accomplished by plugging in a good T1 or by resetting the CESM.

Further Problem Description:

The CESM should send AIS out of the T1 ports when there is an ATM failure. This is happening correctly.

When the failure clears, the CESM is still receiving AIS from the hard loop. This then causes the CESM to fail the PVC due to the line alarm.

Due to this there is an alarm loop.

Headline: CESM cannot clear RcvAIS when connected to physical loop

Hardware: cesm-8t1e1

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

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

CSCec09847

Symptom: Software reset occurred after a resetsys was issued.

Conditions: resetsys was issued from the CLI.

Workaround: None

Headline: Autocard fails to start in a MGX 8850 node

Hardware: pxm45b

CSCec12370






CSCec12463






CSCec14733






CSCec14761






CSCec16762






CSCec18077






CSCec18779






CSCec31183






CSCec33505






CSCec35834






CSCec36941








CSCec41394






CSCec42174






CSCec43059







CSCec45442







CSCec45631







CSCec48191






CSCec49709






CSCec51074






CSCec51153






CSCec51349






CSCec56452






CSCec60515






CSCec62158






CSCec66028






CSCec69678






CSCec71316






CSCec78432








CSCec82251






CSCec83347






CSCed01505






CSCed01523






CSCed01526






CSCed01970






CSCed02565






CSCed40495






CSCed09164






CSCed09942






CSCed14131






CSCed23150






CSCed27617







CSCed31663






CSCed33156






CSCed35770

Headline: Standby PXM45 resets by itself

Symptom : The Standby PXM45/B resets by itself.

Conditions : None

Workaround : None

Hardware: PXM45/B

CSCed39429






CSCed41921

Headline: PXM45/B fails to go standby after sysVersionSet

Symptom : The 2nd PXM45/B does not come to standby mode.

Conditions : Performing "sysVersionSet" after a "clrallcnf".

Workaround : Reset the failed PXM45/B from the Active PXM45/B.

Hardware: pxm45


Known Anomalies in Release 4.0.15

Anomalies Resolved in Release 4.0.15

CSCeb28420 EvtLog:emSyncHumveePort fail messages in log

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

CSCec44812 Sw Fab If ASIC ILT SRAM par err must be detected/recovered from

CSCec55319 Mem leakage in procResponse::RespCalcC exhausting SSI SNMP partition

CSCec55976 vsiSlave Task suspended recovery action should be Fatal

CSCec57716 SSI stack usage exceeds threshold messages in evt. log

CSCec59926 dump commands pause indefinitely with RPMs and may leak resources

CSCec63239 VxWork timer wrapped around

CSCec63535 AXSME:P2MP party in failed state after dnport/upport on leaf port

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

CSCec63713 AXSM reset with core dump

CSCec65160 dspload shows asymmetric bandwidth on AXSMs

CSCec66037 UBR.2 policing needs to tag all cells

CSCec66881 LSNT:AXSM Xtags does not come up

CSCec67719 HMM and QE48 falsely detects parity error when enabled

CSCec68661 XGOC3-DEV: RM Alarms on AXSMB-OC3 after upgrade

CSCec69262 PXM does not switch RPM-XF upon bkcd failures

CSCec79143 Watchdog resets on AXSM observed

CSCec79734 UPG5: APS adj line stuck in LOS after node rebuild

CSCec82151 MPEIT:pnCcb crash after clrsmcnf

CSCec83032 Internal Osc priority going back to default value after rebuild

CSCec86279 ABR tagging problem on PXM-1E Combo STM-1

CSCed01918 AUTO:Upgrade to 4.0.15 AXSME image fails

CSCed17323 Duplicate entries for conns in the STATS files

CSCed22720 Active PXM1E switched over after Standby Combo back card inserted

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

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

CSCed30255 PBUMP connections not torn down in via node after dnpnport

CSCed30486 Line configuration changes do not get applied to standby APS lines

CSCed42682 AXSM-1/B diag enhancement

Anomaly Status Change from Previous Release

Table 35 Anomaly Status Change from Previous Release

Anomaly
Description

CSCdy78398

HFIT:SCM polling takes 3 min to detect SAR errors; Closed

CSCdy82219

HFIT:Utopic 2 Bus CBC to ATMIZER tx/rx bit errors test cases; Closed

CSCdz67977

HMM: Humvee should log more details and take actions on Humvee GenEr; Duplicate of CSCea41517

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

CSCea80192

pxm which is native could not takeover the mastership; Closed

CSCea89455

AXSM/E T3/E3 Offline diag failure; Unreproducible

CSCeb01897

AXSM/B-OC3 went into empty/res due to SHM_CDF_DISCOVER_TMR_POP; Closed

CSCeb05061

AXSM-E T3/E3 fails full cov. off line diag; Unreproducible

CSCeb19481

XBAR port and slot alarms reported against slot of a chassis; Unreproducible

CSCeb27898

Active standby PXM45 HD failed; Closed

CSCeb33176

AXSM-XG card reset because of hw_timer_TassiException; Unreproducible

CSCeb38926

REG4+:MGX8850 node crashed after doing restoreallcnf, not healthy; Unreproducible

CSCeb48332


CSCeb50108

PXM45 sends ipc polling request on LCN 7; Unreproducible

CSCeb50419

axsm-xg trunk in minor alarm; Unreproducible

CSCeb51965

LSNT: tQeTask & tDispatch Task hogging the CPU, Duplicate of CSCed01970

CSCeb69414

Pnport of axsm-xg oc192 card stay in down in prog for long time; Unreproducible

CSCeb82476

Minor cards alarms seen when upgrade to MGX PXM45/B 3.0(23); Duplicate of CSCea69946

CSCeb82771

HDD fails full coverage off line diag; Unreproducible

CSCec32286

BU EFA of PXM45C HD backcard; Closed

CSCec38355

Active PXM45B card locked up & node got isolated; Closed

CSCec45095

LSNT:Switchcc invokes SAR Auto Recovery; Duplicate of CSCec42437

CSCec48361

On IMA slots multiple errors - featuremismatch; Junked

CSCec54212

Need troubleshooting commands like addchanloop,cnfchandbg on PXM1E; Closed

CSCec56829

UPGRD: SSI-4-STKCHK exceeds threshold due to task tRMM; Duplicate of CSCdz50777

CSCec57564

shmPslotInfoGet() uses more than 3K of stack space; Closed

CSCec58287

MGX45 Reset twice and dumped cores, needs investigation; Duplicate of cat open-4015.txt | filt

CSCec64982

UPG5: XG-192 APS adj line LOS but LED not in red; Closed


MGX 8850, MGX 8830, and MGX 8950 4.0.12 Anomalies

Anomalies are organized as follows:

Anomalies Resolved in Release 4.0.12

Anomalies Resolved in Release 4.0.12

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

CSCdz04524 P2MP_DT: SPVC p2mp parties terminated on AXSME stays in FAIL

CSCdz66395 CIT40: OAM CC config is allowed from CLI on PXM1E.

CSCdz83876 dspclksrc displays internal clock source after switchcc

CSCea20818 mem.leak: CMtask holds ipc_get_floating_mblk

CSCea23761 Implement PCI error interrupt on pxm45c/pxm1e-8oc3

CSCea59570 Adding APS line when the stby card is not stby give wrong error mess

CSCea65791 dumpconfigs command aborted with error message

CSCea72681 Need protection to ensure that SM don't generate files to fill disk

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

CSCea84491 UPGRD: resetsys, err_log logged FIPC-5-EPHNDLRFAIL from pnConPro

CSCea92407 Path Alm on Protection line does not get intg. when Pri line Red/Yel

CSCea93644 CLI_CONSITENCY: AXSM-XG does not support some of AXSME commands

CSCeb03881 Backcard removal causes cc to card fail.

CSCeb06582 MPSM: abit alarm not propagated correctly for some CESM/MPSM-CES con

CSCeb13176 Incorrect reporting sequence could cause loss of diag error results

CSCeb13369 After Offline diags executes, FSM should go to IDLE, not READY state

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

CSCeb17823 Unreliable tstdelay results for axsm/B/E <--> frsm

CSCeb18768 TnCmdTsk03 exception found

CSCeb22068 Unable to cc to card

CSCeb23240 multiple APS-SF-DECL msg posted to evtlog w/o SF (BER) clearing

CSCeb23400 Need HMM error counters for QE, XIF, PIF

CSCeb25477 AXSME: dspchancnt, CLPO discarded should only show user data

CSCeb29954 Ima link failure does not reflect to the pnport resource

CSCeb31125 dsphotstandby command shows wrong info when runrev executed:frsm-vhs

CSCeb32478 taskIndex and sizeof(gSysTaskTable) expect larger range.

CSCeb34166 dspdiagcnf shows online diagnostics enabled by mistake on SM/PXM1E.

CSCeb34878 Warning needed when APS disabled on non-redundant PXM1E

CSCeb36107 FIPC-5-LINKOUTERROR Repeated Log error

CSCeb38023 switchcc caused Reset from Shell coredumps on PXM45C

CSCeb40512 delred fail for LSM in 8830

CSCeb42487 possible memory corruption issues dsperr.

CSCeb46725 tCrdmp task logged Proxy file protocol error after node rebuild

CSCeb47830 ssi exception error: snmpSA crash

CSCeb48697 dspcds shows cd type UNKNOWN when in Mismatch state

CSCeb48739 HARD: dspcd shows MISMATCH but no reserved type

CSCeb49580 HARD: no alarm cause in lower bay nbsm when rsvd for bbsm

CSCeb50179 HARD: Improper error message for addred with incomp FRSMHS2B BC

CSCeb50268 After forced switch W->P, SFBER on W does not cause W->P switch

CSCeb50631 HARD: Incorrect error message for addred 1:n bulk mode

CSCeb51038 HARD: Secondary NBSM used as Bulk and Non-Bulk

CSCeb51056 HARD:Incorrect Error Message when error in addred

CSCeb51078 dumpconfigs command aborted when there is a RPM card in the node

CSCeb51081 AXSM5 loss traffic without any alarm

CSCeb51137 Hard: CBSM in empty state when burnboot followed by addred

CSCeb51176 HARD: CBSM addred not blocked when primary SM in burnboot

CSCeb51323 SRMEB: Stats manager caused Active PXM1E reset

CSCeb51696 HARD: switchredcd and resetcd not blocked during burnboot on CBSM

CSCeb52781 SRMEB:No ERR msg while enabling SRM/SRMEB-3T3 Online Diag

CSCeb54282 HARD: dspred doesn't show Active-U during nbsm upgrades

CSCeb54310 HARD: FRSM8E1 wnt to failed state when runrev followed by abortrev

CSCeb54369 HARD: dspred doesn't show blkd for pri/sec with lower/higher version

CSCeb54823 Manual setting of CB4,CB8 allowable clock rate throws error message

CSCeb55258 Misleading error message when provisioning and not enough bandwidth

CSCeb55874 PnCcb crash cause PXM45 switchover

CSCeb55910 CCMA-4-IPCSENDFAIL message logged for AXSM-E in init state

CSCeb56175 ShmPing should exclude pinging pxm peer

CSCeb57712 ata semaphore timeout and watchdog timeout should be 30seconds

CSCeb57805 loadrev exception happens in cli cmd task

CSCeb58207 none of the bert commands executed is seen in the dsplog

CSCeb58417 clrsmcnf fails on multiple slots

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

CSCeb58943 Invalid SSI trace log in event log

CSCeb59779 Trap 60051 not generated for RPM_PR

CSCeb60025 switchredcd on node resets the PXM1e

CSCeb60130 HARD: secondary nbsm fail due to reset sec without prim in loadrev

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

CSCeb62428 bringup tools needed for hardware debug

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

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

CSCeb63658 Increase HW error threshold.

CSCeb64000 switchover loss around 630ms, >250ms

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

CSCeb64756 Del/add partition causes the pnport stay in vc-failure.

CSCeb64863 Policing of 80 char limit for certain cli commands

CSCeb65427 Printf Mutex semaphore getting locked

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

CSCeb66476 Not able to ftp the configVerify distribution zip file to any node

CSCeb67611 SRMEB: No event logs found for srme LINK commands

CSCeb67820 CIT50:node db contains two entries with same node id

CSCeb67870 snmp Master Agent went to idle state for approx 45 min

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

CSCeb68706 observed message file already closed after runrev executed on frsm

CSCeb69085 need the event log. for QE1210 and CBC

CSCeb69124 Incremental files are deleted slowly when Standby is available

CSCeb69793 FI: test-13:Hard disk failure: No trap upon fault

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

CSCeb70169 Stack usage exceeds threshold (70 percent): Task=tRVT

CSCeb70258 Incorrect ifName string in the atm phy trap 60373

CSCeb70361 PXM1E: pushing ACO/HIST does not generate core-dump on pxm1e

CSCeb71464 CLI for Active PXM Freeze Detection and Recovery

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

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

CSCeb73912 DISK Spin down to be disabled by default

CSCeb74414 avoid calling task delays in reboot (sysToMonitor)

CSCeb74423 Block switchcc/yred while stby axsm is not responding to polling

CSCeb74822 ATMizer send fails because of xmtBuff full

CSCeb75099 All traffic loss when route the conns on axsm-xg card

CSCeb76581 CIT50:pnRedman suspended at provred_persis_link_addDel

CSCeb77003 PNNI gdb enhancements.

CSCeb77459 Observed Bad CRC PDUs during the signaling packets exchange

CSCeb77524 soft reset the card when tRootTask does not get CPU

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

CSCeb79161 Request the correct conn DB for ramSync

CSCeb79598 STATS UPLOAD: T3 LINE - Number of Keys = 0 byte order incorrect

CSCeb80366 Implement diag changes for pxm1e-combo respin (JA removal)

CSCeb80600 corrupted stats on pxm1e -- cesm-t1e1 cards under corner configs

CSCeb80634 Implement pxm45/pxm1e diagnostics enhancements

CSCeb81314 snmpget/walk of standby SM can cause denial of service

CSCeb81848 AUTO:AXSM/AXSME fails to come up after upgrade

CSCeb83142 connection fails routing due to wrong util used at slave

CSCeb83347 printf() in cliSmEptWrite() caused flood of messages

CSCeb83949 Policing of 80 char limit for dsppnportcac and dsppnportrsrc command

CSCeb83965 Policing of 80 char limit for certain cli commands

CSCeb85464 AXSM switchredcd caused PXM to reset and coredump

CSCeb85657 P2MP parties fail to route over faked uplinks

CSCeb86666 After burnboot and clrallcnf card keeps resetting during post.

CSCeb87513 pnni link on a PXM1E with IMA backcard goes down without recovery

CSCeb88172 PXM45C keeps resetting after a switchcc

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

CSCec02957 CIT50:port stuck in provisioning after commitrev and resetsys

CSCec04064 ATmizer SAR ingress/egress path diagnostics reqd for PXM1E

CSCec04212 failed stdby PXM caused AXSM cds to go into failed state.

CSCec04754 status byte in stats file always set to 1 ERR

CSCec04902 CIT50:redman donot read > 100 records for Disk_spvc_itf_db

CSCec05278 OAM cc is not working consistently as expected

CSCec07087 PXM1E: ATLAS HMM should report errors to SHM

CSCec08533 CESM T3E3 1:1 Redundancy is not functional

CSCec10875 the first two intervals of a new connection has wrong stats data

CSCec10933 Software Err Reset coredump caused by 2 tasks hanging on a semaphore
CSCec11151 UI-S3 not locked to proper reference after inband references switch
CSCec11356 LSNT:GLCNs downed for Service module cards

CSCec11994 CTC app stage spawn state machine is susceptibe to error

CSCec12108 Pnports of AXSM-XG card stay in building vc

CSCec12454 Getting the details of error log failed with wrong error message

CSCec12475 EVENT-CLEANUP: multiple IFM-5_critical errors fill in dsperrs log

CSCec12609 CIT50:several VSI sev4 error logged from act and stdby AXSMB

CSCec13851 QMC errors on AXSM1P Etch5 cards

CSCec14029 cnfpasswd command not recorded into the LOG for PXM45/PXM1E

CSCec14485 User should not be forced to enter ICR if VSVD if off

CSCec15230 Software Error Reset core dump on PXM45 node

CSCec15803 Svc number show as -1 in the partition of AXSM-XG card

CSCec16448 Can not add con with line rate on HS2/B low rate

CSCec16527 Changing maxbw using cnfpnportcac causes rsrc alloc. inconsistency

CSCec17149 Dspcons does not report AIS alarm on SPVP connections

CSCec17721 OAM cc is not working properly on axsm-xg card

CSCec20081 Add performance profiling code to CCB

CSCec20568 DCMP msg has uninitialized fields

CSCec20587 Invalid pref route value in DCMP can cause pnCcb exception

CSCec22514 PXM card reset caused by killing the telnet session

CSCec23958 Offline diags causes near end and far end pm errors on active card

CSCec24908 tsmTermdTas suspended due to invalid guard magic word

CSCec25188 MPSM8-DT: Online diag detects DataPath Test Timeout

CSCec25929 COSB stats is not cleared correctly

CSCec27723 Pnni signalling lcn reuse - pnni link cannot establish

CSCec28435 AXSME IMA port goes into vc failure after dnpnport and uppnport

CSCec28667 addimalnk for E1 path of invalid line type (E1CRC) addressloadexcept

CSCec29583 Interop of MGX 5.0 & 4.0 with PB & MPG enabled causes routing issues

CSCec33139 Not able to add redundancy between 2 RPM-PR cards

CSCec33311 blanket bugid for sprintf violations

CSCec33758 Spoke cost of destination PG should not be added to routing cost

CSCec33808 Crankback on failure of call forwarding should not be SEBI

CSCec35459 SRM redundancy not updated properly after upgrade

CSCec36965 FRSM resets due to config upload

CSCec37734 saveallcnf save config file with wrong date

CSCec38330 Send TOD update to RPM -XF cards too

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

CSCec39798 CMTask causes an SSI exception in PXM1E running 3.0.20

CSCec40496 Dnp*ort on the Uni port on axsmxg card doesnt work

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

CSCec49356 tVsiSlave on AXSM crashes on multiple nodes around the same time

MGX 8850, MGX 8830, and MGX 8950 4.0.11 Anomalies

Anomalies are organized as follows:

Anomalies Resolved in Release 4.0.11

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

MGX 8850, MGX 8830, and MGX 8950 4.0.10 Anomalies

Anomalies are organized as follows:

Anomalies Resolved in Release 4.0.10

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 MGX 8950

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

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. In these release notes, AXSM-A refers to the original AXSM card (A did not appear on the card), and AXSM/B refers to the newer AXSM/B card (B does appear on the card).

ABR

Available bit rate

APS

Automatic Protection Switching

CALEA/LI

Communications Assistance for Law Enforcement Act/ Lawful Intercept

CBSM

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

CLI

Command Line Interface

CoS

Class of service

CUG

Closed User Group

CWM

Cisco Wide Area Network Manager

GE

Gigabit Ethernet

IAP

Intercept Access Point

IMA

Inverse Multiplexing over ATM

LANE

Local Area Network Emulation

LFI

Link Fragmentation Interleaving

MLPPP/LFI

Multi-Link PPP

MTI

Multicast Tunnel Interface

NBSM

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

P2MP

Point-to-Multipoint

PE

Provider Edge

PER

Product Enhancement Request

PNNI

Private Network-to-Network Interface

POS

Packet over SONET

POST

Power On Self-Test

PPP

Point-to-Point Protocol

PXM

Processor Switch Module

RPM

Route Processor Module

SFP

Small Form Factor Pluggable Unit

SONET

Synchronous Optical NETwork

SPVC

Soft permanent virtual connection

SRM

Service Resource Module

SVC

Switched virtual circuit

VPN

Virtual Private Network

VRF

VPN Routing / Forwarding

XF

Express Forwarding