5.0.20 Release Notes for MGX 8850 (PXM1E/PXM45), MGX 8950, and MGX 8830 [Cisco MGX 8800 Series Switches]

Table Of Contents

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

Contents

About Release 5.0.20

Changes to Release 5.0.20

Type of Release

Locating Software Updates

Features and Enhancements in Release 5.0.20

Multilink Frame Relay on MPSM-T3E3-155

Features

Restrictions

Multilink Frame Relay Quick Start Provisioning Procedures

Multilink Frame Relay General Provisioning Procedures

Adding a Port to the MFR Bundle

Deleting an MFR Bundle, Link, or Port

Port Oversubscription on MPSM-T3/E3-155

Channel Loopback on MPSM-T3E3-155

Restrictions

Enhancement to Statistics Counters on MPSM-T3E3-155

Features and Enhancements in Previous Release 5.0.10

CES Line Conditioning

Platforms

MPSM Service Modules

MPSM Licenses

Platforms

PXM45 RAS

Platforms

Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)

Platforms

License Management

Platforms

AXSM-16-155-XG Feeder Support

Limitation

Platforms

Unique Device Identifier (UDI)

Limitations

Platforms

Features and Enhancements in Previous Release 5.0.00

SRME/B

Platforms

AXSM-16-155-XG

Platforms

AIS Delay, Deroute Delay, Absolute Grooming

Platforms

Soft Reroute

Platforms

Point to Multipoint Support on PXM1E

Limitation

Platforms

Enhancements to Route Optimization

Platforms

Priority Bumping

Platforms

Enhancements

Service Class Template (SCT) File Information

MPSM-155

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-XG

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

Additional Notes

SNMP MIB Release

Hardware Supported

New Hardware in Release 5.0.20

New Hardware in Release 5.0.10

Product IDs, Card Types, and APS Connectors

New and Changed Commands

New and Changed MPSM-T3E3-155 Commands

New Multilink Frame Relay Commands

addmfrbundle

addmfrlnk

addmfrport

clrmfrbundlecnt

clrmfrbundlecnts

clrmfrlnkcnt

clrmfrlnkcnts

cnfmfrbundle

cnfmfrlnk

delmfrbundle

delmfrlnk

dnmfrbundle

dspmfrbundle

dspmfrbundlealm

dspmfrbundlealms

dspmfrbundlebucketcnt

dspmfrbundlecnt

dspmfrbundles

dspmfrlnk

dspmfrlnkalm

dspmfrlnkalms

dspmfrlnkbucketcnt

dspmfrlnkcnt

dspmfrlnks

upmfrbundle

New Channel Loopback Commands

addchanloop

delchanloop

dspchanloop

Changed Commands

Removed Commands

Commands Changed in Release 5.0.10

PXM45 Commands

PXM1E Commands

AXSM and AXSM-E Commands

Limitations, Restrictions, and Notes for 5.0.20

AXSM-16-155-XG with MCC Back Cards

Upgrading AXSM-XG Cards

Upgrading the VISM-PR Image

MPSM Notes

PXM1E Parity Errors

Upgrading to 5.0

Higher Level Logical Link Limits

CLI Upgrade

Preferred Route

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

Cell Bus Service Modules (Formerly Known as Narrow Band Service Modules) and RPM-PR

IGX Feeder

Policing Accuracy for PXM1E

Maximum Threshold Accuracy for PXM45 and PXM1E

PXM1E-Based Switches

PXM1E Hardware Limitations

Reserved VCIs

AXSM-E OAM

CLI Configurable Access

Controller Card Mastership Sanity Verification

Serial Bus Path Fault Isolation

Cell Bus Path Fault Isolation and Recovery

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

Priority Bumping

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

Troubleshooting APS Lines

Installation and Upgrade Procedures

Upgrade Information

Maintenance Information

Anomalies

MGX 8850, MGX 8830, and MGX 8950 5.0.20 Anomalies

Known Anomalies in Release 5.0.20

Resolved Anomalies in Release 5.0.20

Anomalies Status Change in Release 5.0.20

Resolved Anomalies in Previous Releases

Resolved Anomalies in Release 5.0.10

Resolved Anomalies in Release 5.0.00

Known Route Processor Module or MPLS Anomalies

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

Documentation

Obtaining Documentation

Cisco.com

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Acronyms

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

These release notes are Part Number OL-6856-01 Rev. G0, March 2007.

Contents

About Release 5.0.20

Version .205 of Release 5.0.20 is a patch release that does not introduce new features. The resolved anomalies for Version .205 are listed in Table 24.

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

For a list of the open and resolved anomalies in this release, see the "MGX 8850, MGX 8830, and MGX 8950 5.0.20 Anomalies" section.

Changes to Release 5.0.20

Table 1 summarizes the software changes in Release 5.0.20.

Table 1 Changes to Release 5.0.20 Software

Revision Date on Cisco.com

Software

Version Change

Resolved Anomalies

Reference

11/14/05

MPSM-T3E3-155

.201 to .202

CSCei35633

CSCej32681

CSCej15496

Table 25 in Resolved Anomalies in Release 5.0.20

AXSM-XG

.203 to .204

09/09/05

PXM45

.202 to .203

CSCei67407

CSCei82475

Table 26 in Resolved Anomalies in Release 5.0.20

PXM1E

.202 to .203

AXSM-XG

.202 to .203

MPSM-T3E3-155

.200 to .201

CSCei59862

CSCei65805

AXSM/B

.200 to .201

05/12/05

PXM45

.201 to .202

CSCec04754

CSCec48191

CSCeg25173

CSCeg62909

CSCeg68790

CSCeg76224

CSCeg88649

CSCeh14484

CSCeh15349

CSCeh15410

CSCeh16336

CSCeh19705

CSCeh21259

CSCeh21549

CSCeh23987

Table 27 in Resolved Anomalies in Release 5.0.20

PXM1E

.201 to .202

AXSM-XG

.201 to .202

MPSM-8-T1E1

.201 to .202

Type of Release

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

•MGX 8830 PNNI routing switch

•MGX 8850 (PXM1E)

•MGX 8850 (PXM45)

•MGX 8950

Locating Software Updates

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

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

Features and Enhancements in Release 5.0.20

This section contains the following new features and enhancements in Release 5.0.20:

•Multilink Frame Relay on MPSM-T3E3-155

•Port Oversubscription on MPSM-T3/E3-155

•Channel Loopback on MPSM-T3E3-155

•Enhancement to Statistics Counters on MPSM-T3E3-155

Multilink Frame Relay on MPSM-T3E3-155

Multilink Frame Relay (MFR) combines multiple individual links into one logical interface, called an MFR bundle. Multilink bundles help bridge the gap between DS1 and DS3 bandwidths, and can increase resiliency because the failure of a link usually does not bring down the whole bundle. In the MPSM-T3E3-155, each link is a T1 path on a channelized DS3 line or path.

The bundle interface serves as the Frame Relay data link, and performs the same functions as a physical Frame Relay interface. The bundle interface is visible to peers, so you configure Frame Relay functionality on the bundle interface. This section describes how to provision Mulitlink Frame Relay (MFR) services on the MPSM-T3E3-155 card.

Note Before you perform the procedures in this section, you must first configure the MPSM-T3E3-155 card and lines.

Features

The MPSM-T3E3-155 provides the following features:

•MFR supported on the 3-port channelized T3 back card and the 2-port channelized OC-3 back cards.

•Maximum of 42 bundles with up to 12 links per bundle.

•Support for Class A, Class B, and Class C bandwidth classes.

•Bundling of links that belong to different channelized T3 (up to 3 T3s) or STS-1s (up to 3 STS-1s).

•Aggregation of only full T1/E1 links. MFR bundles with NxDS0 links are not supported.

•12 bit sequence number format.

•Two-byte Frame Relay header supported.

•Support only for Extended Super Frame (ESF).

•Both UNI and NNI mode as per FRF.16.1 are supported.

•MPSM is transparent to end-to-end MFR and cannot be the initiating or terminating end for end-to-end MFR.

•FRF.2.1 Annex 1 is supported on NNI-type bundle interfaces.

Restrictions

The MPSM-T3E3-155 has the following restrictions:

•Aggregation of full T1 links only; MFR bundles with n x DS0 links are not supported

•Blending T1 and E1 is not supported

•Two-byte Frame Relay header (for example, 10 bit DLCI) is supported

•Four-byte Frame Relay header for extended addressing is not supported. Frame Relay extended addressing uses a 23-bit DLCI field that enables support for thousands of DLCIs in NNI networks.

•Frame Relay fragmentation is not supported.

•Super Frame (SF) mode is not supported. Only ESF (Extended Super Frame) mode is supported for MFR services.

•A maximum of 200 DLCIs per bundle is supported.

Multilink Frame Relay Quick Start Provisioning Procedures

This section provides quick start procedures for provisioning MFR on the MPSM-T3E3-155.

.

Command

Comments

Step 1

addmfrbundle
related commands:

dspmfrbundle
cnfmfrbundle
delmfrbundle

Add a MFR bundle using default parameters. Refer to Creating an MFR Bundle for detailed instructions on adding an MFR bundle.

Step 2

cnfmfrbundle
related commands:

addmfrbundle
cnfmfrbundle
delmfrbundle

Configure MFR bundle parameters. Refer to Configuring an MFR Bundle for detailed instructions on configuring an MFR bundle.

Step 3

addmfrlnk
related commands:

cnfmfrlnk
dspmfrlnk
delmfrlnk

Add links to the MFR bundle. Refer to Adding Links to an MFR Bundle for detailed instructions on adding an MFR link.

Step 4

addmfrport
related commands:

dspport
cnfport
delport

Add an MFR port. Refer to Adding a Port to the MFR Bundle for detailed instructions on adding an MFR port.

Step 5

addcon

related commands:

cnfcon
dspcon
delcon

Add SPVCs for the MFR service.

Multilink Frame Relay General Provisioning Procedures

This section contains procedures for provisioning MFR on the MPSM-T3E3-155. You create SPVCs for MFR the same way that you create Frame Relay SPVCs.

Note To support MFR, both ends of a physical link must be MFR capable, and the MFR configuration must match on both ends.

Creating an MFR Bundle

The MPSM-T3E3-155 implements MFR service using MFR bundles, which contain one or more serial links. When you add a bundle, the MPSM-T3E3-155 creates the corresponding Frame Relay data link layer interface for the service. After adding a bundle, you can then add MFR links to the bundle.

When you add a bundle using the addmfrbundle command, you specify the bundle number and activation class only; all other bundle parameters assume default values. You subsequently configure other bundle parameters using the cnfmfrbundle command. For example, after adding a Class C bundle you also need to configure the minimum number of links that must be operational before the bundle is operational.

To create an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 Create an MFR bundle using the addmfrbundle command.
M8850_SF.10.MPSM155[FR].a > addmfrbundle <bundleNum> <activationClass>
Table 2 describes the parameters for the addmfrbundle command.

Table 2 addmfrbundle Command Parameters

bundleNum

Bundle Number, range 1-42

activationClass

Bundle activation class:

•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2=Class B—All the bundle links must be operational for the MFR Bundle to be operational

•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

This command creates a MFR bundle with the default configuration shown in Table 3.

Table 3 MFR Bundle Default Configuration

Parameter

Description

minimumLinks

Specifies the minimum number of active links required for a Class-C MFR bundle to be operational. The default value is 1 link

helloTimer

Specifies the interval in seconds at which to send hello messages. The default is 10 seconds.

ackTimer

Specifies the maximum time period to wait for an acknowledgement message from the far end. The default is 4 seconds.

maxRetry

Specifies maximum number of times to re-try sending a hello message to the far end if an acknowledgement message is not returned. The default is 2 retries.

bundleName

Identifies the near-end bundle. The default bundle name is of the form node.slot.bundle, for example M8850_SF.Slot10.Bundle03

The following example creates MFR bundle 3 with Class A service type using default bundle parameters:
M8850_SF.10.MPSM155[FR].a > addmfrbundle 4 3
Step 3 To verify that the MFR bundle has been created, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle.
M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
    Bundle Number                   : 4
    Activation Class                : C
    Minimum Links                   : 1
    Admin state                     : Up
    Oper State                      : Down
    Hello Timer (seconds)           : 10
    Ack Timer (seconds)             : 4
    Max Retry Count                 : 2
    Maximum Bundle Links            : 12
    Configured Number of Links      : 0
    Active Number of Links          : 0
    Available Bandwidth             : 0
    Near End Bundle Name            : M8850_SF.Slot10.Bundle04
    Far End Bundle Name             : <not defined>
Configuring an MFR Bundle

When you add an MFR bundle, most of the configuration options are defaults (See Table 3). For example, if you want to add a bundle with a minimum number of links that is greater than one, you have to configure the minimum number of links is this procedure.

To configure an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 If the MFR bundle is administratively up, bring it down by entering the dnmfrbundle <bundleNum> command.

Step 3 Configure MFR bundle parameters using the cnfmfrbundle command.
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle <bundleNum>  
[-class <activationclass>] [-minlinks <minimumlinks>] 
[-hellotimer <hellotimer>] [-acktimer <acktime>] 
[-maxretry <maxretry>] [-bname <bundleName>]
Table 4 describes the parameters for the cnfmfrbundle command.

Table 4 cnfmfrbundle Command Parameters

Parameter

Description

-bundle

Identifies the MFR bundle number.

Enter the dspmfrbundles command to display all MFR bundles on the card.

-class

Bundle activation class:

•1=Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2=Class B—All the bundle links must be operational for the MFR Bundle to be operational

•3=Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

-minlinks

Minimum number of Links for Class-C activation class, range 1-12.

-hellotimer

Interval for sending hello messages, range 1-180 seconds.

-acktimer

Maximum time period to wait for an acknowledgement from the far end, range 1-10 seconds

-maxretry

Maximum number of Retries (Maximum retries), range 1-5 retries.

-bname

Near-end bundle name:

A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters, with a maximum of 49 characters.

In the following example, the user increases the minimum number of links for a Class C MFR bundle to 4 and sets the maximum number of retries to 4.
M8850_SF.9.MPSM155[FR].a > dnmfrbundle 4 
M8850_SF.9.MPSM155[FR].a > cnfmfrbundle -bundle 4 -minlinks 4 -maxretry 4
Step 4 Restore the bundle to the administrative up state by entering the upmfrbundle <bundleNum> command.

Step 5 To verify MFR bundle configuration, enter the dspmfrbundle <bundleNum> command, specifying the number of the bundle you want to display.
M8850_SF.10.MPSM155[FR].a > dspmfrbundle 4
    Bundle Number                   : 4
    Activation Class                : C
    Minimum Links                   : 4
    Admin state                     : Up
    Oper State                      : Down
    Hello Timer (seconds)           : 10
    Ack Timer (seconds)             : 4
    Max Retry Count                 : 4
    Maximum Bundle Links            : 12
    Configured Number of Links      : 0
    Active Number of Links          : 0
    Available Bandwidth             : 0
    Near End Bundle Name            : M8850_SF.Slot10.Bundle04
    Far End Bundle Name             : <not defined>
Adding Links to an MFR Bundle

After you have established and configured an MFR bundle, you can add links to the bundle. Adding a link sends an Add-Link request message to the far-end of the bundle. A link is actively operating in a bundle only after the following conditions are met:

•An Add-Link acknowledgement is received from the Far end for the transmitted Add-Link message.

•An Add-Link request is received from the Far-end.

After both messages are received from the far-end, the MFR link is ready to transmit and receive data. Depending on the Activation Class of the bundle, the Bundle Up Indication is sent by the MFR Bundle layer to the Frame Relay Data Link layer under the following conditions.

•Class A bundles—After receiving link activation confirmation for one link.

•Class B bundles—After receiving link activation confirmation for all links in the bundle.

•Class C bundles—After a predefined number of links in the bundle confirm activation.

To add a link to an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 Bring up the links (paths) that you want to add to the MFR bundle by entering the uppath [-path_filter] <path_num> command. To display all available paths, enter the dsppaths -all command.

Step 3 Add links to the MFR bundle by entering the addmfrlnk command. The new link has a default name with the format node.card.link.
M8850_SF.10.MPSM155[FR].a > addmfrlnk <link> <bundleNum> 
Table 5 describes the parameters for the addmfrlnk command.

Table 5 addmfrlnk Command Parameters

Parameter

Description

link

Specifies a DS1 or E1 path:

•DS3 payload: bay.line.sts:ds1

•VT payload: bay.line.sts:vtg.vt

•VT structured: bay.line.sts:tug3.vtg.vt

where: bay=1, line=1-3, sts=0-3, ds1=1-28,
tug3=1-3, vtg=1-7, vt=1-4 (VT15) or 1-3 (VT2)

Note Enter the dsppaths -all command to display all available paths on the card.

bundleNum

Bundle number, in the range 1-42

Note Enter the dspmfrbundles command to display all bundles on the card.

The following example adds link 1.1:11 (bay 1, DS3 1, DS1 11) to bundle 4.
M8850_SF.10.MPSM155[FR].a > addmfrlnk 1.1:11 4
Step 4 To verify that the link was added to the MFR bundle, enter the dspmfrlnk <linkNum> command, specifying the number of the bundle.
M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
  Link Number                      : 1.1:11
  Bundle Number                    : 4
  Link State                       : Down
  Link Alarm State                 : Other
  Link Delay (Rtt in msec)         : 0
  Link Near End Name               : M8850_SF.Slot10.Link11
  Link Far End Name                : <not defined>
  Link Far End Bundle Name         : <not defined>
  Link PHY Operational Status      : Down
Configuring MFR Links

Optionally, reconfigure the near-end name of the MFR link. Links have a default near-end name in the format node.slot.link, for example M8850_SF.Slot10.Link11.

To rename a link, perform the following steps.

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 Reconfigure the link by entering the cnfmfrlnk command.
M8850_SF.10.MPSM155[FR].a > cnfmfrlnk -link <lnkNum> -lname <linkname> 
Table 6 describes the parameters for the cnfmfrlnk command.

Table 6 cnfmfrlnk Command Parameters

Parameter

Description

-link

Specifies the MFR link number:

Note Enter the dspmfrlnks command to display all MFR links on the card.

-lname

Near-end link name:

A null -terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters with a maximum of 49 characters.

In the following example, the user changes the MFR link name to M8850_SF.Slot09.Bundle04.Link11.
M8850_SF.9.MPSM155[FR].a > cnfmfrlnk -link 1.1.1:1 -lname M8850_SF.Slot09.Bundle04.Link11 
Step 3 To verify MFR link configuration, enter the dspmfrlnk <lnkNum> command.
M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:11
  Link Number                      : 1.1:11
  Bundle Number                    : 4
  Link State                       : Down
  Link Alarm State                 : Other
  Link Delay (Rtt in msec)         : 0
  Link Near End Name               : M8850_SF.Slot09.Bundle04.Link11
  Link Far End Name                : <not defined>
  Link Far End Bundle Name         : <not defined>
  Link PHY Operational Status      : Down
Adding a Port to the MFR Bundle

You need to add a port to an MFR bundle to connect it to other endpoints.

To add a port to an MFR bundle, perform the following steps:

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 Prepare to add a port to the MFR bundle:

a. Determine the bundle number on which you will add the port. To display a list of the MFR bundle numbers, enter the dspmfrbundles command.

b. Verify that the bundle and port number you want to use are not already configured. To display a list of the Frame Relay ports already configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context.

When you add a port, you must specify a port number that is unique on the MPSM-T3E3-155 card. For example, if port number (If Num) 5 is assigned, you cannot use port 5 on any other line or bundle on that MPSM-T3E3-155 card.

Step 3 Add and configure an MFR port for the MFR bundle by entering the addmfrport command:
M8850_SF.10.MPSM155[FR].a >addmfrport <ifNum> <bundle> <portType> <sct> 
[-rat <rat>] [-oversub <oversub>] 
[-lmiSig <lmiSigType> ] [-asynUpdt <updateType>] 
[-elmi <elmiState>][-segLmi <segLmiStatus>] 
[-t391 <t391Value>] [-t392 <t392Value>] 
[-n391 <n391Value>] [-n392 <n392Value>][-n393 <n393Value>] 
Table 7 lists the parameter descriptions for adding MFR ports.

Table 7 addmfrport Command Parameters

ifNum

A number for the port, in the range 1-1003.

bundleNum

The MFR bundle number, in the range 1-42.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

portType

Type of logical interface (port):

•1 = Frame Relay Service

•3 = Frame Forward (Not applicable for MFR bundles)

sct

The Service class template (SCT) for the port, range 0-255.

Default: 0

Note The port SCT file must exist and be registered on the PXM disk before it is available for use. Enter the PXM dspscts command to view all registered SCT files on the PXM card.

-rat

The egress service ratio of the high priority and the low priority queues, range 0-15.

•Enter 0 to indicate that no service ratio is configured. In this case, bandwidth is allocated to both the high priority and the low priority queues on demand, which means that traffic is dynamically allocated on a first-come, first-serve basis.

•The default setting is 1. In this case, the traffic of the CBR and rt-VBR service categories is allocated to the high priority queue, while the traffic of the nrt-VBR, ABR, and UBR service categories is allocated to the low priority queue.

-oversub

Oversubscription control:

•1 = enable

•2 = disable (default)

-lmiSig

LMI signaling protocol type:

•2 = No Signaling (default)

•3 = StrataLMI

•4 = AnnexAUNI

•5= AnnexDUNI

•6 = AnnexANNI

•7 = AnnexDNNI

Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.

-asynUpdt

Enables or disables asynchronous updates. Asynchronous updates are an extension to the LMI protocol that notify the user immediately of changes in PVC and Multicast status. Before enabling this feature, make sure that any DTE equipment you are connected to supports asynchronous updates from the network.

Asynchronous update control:

•1 = Disable both Asynchronous Status Updates and Unsolicited Full Status (default)

•2 = Enable Asynchronous Status Updates

•3 = Enable Unsolicited Full Status

•4 = Enable Asynchronous Status Updates and Unsolicited Full Status

-elmi

Enable or disable enhanced LMI. Enhanced LMI enables the automatic exchange of Frame Relay QoS parameter information between the DTE and DCE. When enabled on both the DTE and the MPSM port, this allows the DTE device to learn QoS parameters from the frame relay port and use them for traffic shaping, configuration, or management purposes.

•1 = enable

•2 = disable (default)

-segLmi

Segmented LMI control:

•1 = enable

•2 = disable (default)

-t391

T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends Status Enquiry messages to the network (DCE) every T391 seconds. An error is recorded if a Status message is not received within T391 seconds. The T391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 5-30. Default: 10

-t392

T392 timer. This is the Polling Verification timer. The network (DCE) expects Status Enquiry messages from the user (DTE) every T392 seconds. If the network does not receive a Status Enquiry message from the user within T392 seconds and the timer expires, then the network records a missing Status Enquiry message by incrementing the N392 counter. This timer value must be set greater than the T391 timer. The T392 timer always applies to the network. It applies to the network and user if NNI bi-directional polling is present. Range 5-30. Default: 15

-n391

N391 counter. This setting establishes the Full Status (status of all PVCs) polling cycle. The user (DTE) sends a Full Report Status Enquiry to the network (DCE) every N391 polls. The N391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 1-255. Default: 6

-n392

N392 counter. This setting specifies the UNI/NNI error threshold. This is the number of errors during N393 events that will cause an error condition. This counter should be less than or equal to the N393 counter. This counter can apply to both the user (DTE) and the network (DCE). Range 1-10. Default: 3

-n393

N393 counter. This setting is the monitored UNI/NNI events count, which must be greater than the N392 counter. N392 errors during N393 events will cause an error condition. If the N393 counter is set to a value much less than the N391 counter, the port could go in and out of an error condition without notification to either the user equipment or the network. This counter can apply to both the user (DTE) and the network (DCE). The value of this parameter should be greater than that for the -n392 parameter. Range: 1-10. Default: 4

Step 4 To display a list of all Frame Relay ports configured on the MPSM-T3E3-155 card, enter the dspports command in the Frame Relay service context. Port numbers are listed in the ifNum (interface number) column. If you want to view information on a particular port, note the number of that port.

In the following example, the user adds MFR port 4 to bundle number 4 with service class template 0.
M8850_SF.10.MPSM155[FR].a > addmfrport 4 4 1 0
Step 5 To verify the port, enter the dspports command:
M8850_SF.10.MPSM155[FR].a > dspports
ESR: Egress queue Service Ratio                                                
                                SCT DS0    Port                 E   FRF        
If   Line/Path   Admn Oper if   In  Start  Speed      Signaling LMI 12   MFR   
Num  Num         Stat Stat Type Use (Num)  kbps   ESR Type      St  Frg Bundle  
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------ 
   4         N/A   Up LLDn   FR   0    N/A   1532   1      None Off Off   4
  11       1.1:1   Up   Up   FR   0  1(24)   1536   1      None Off Off N/A
  12       1.1:2   Up   Up   FR   0   1(4)    256   1      None Off Off N/A
  13         N/A   Up   Up   FR   0    N/A   6131   1      None Off Off   1
  21       1.2:1   Up   Up   FR   0  1(24)   1536   1      None Off Off N/A
  22       1.2:2   Up   Up   FR   0   1(4)    256   1      None Off Off N/A
  23         N/A   Up   Up   FR   0    N/A   6131   1      None Off Off   2
Deleting an MFR Bundle, Link, or Port

Use the following procedure to delete an MFR bundle, link, or port.

Step 1 Establish a configuration session with the MPSM-T3E3-155 using a user name with GROUP1 privileges or higher.

Step 2 To delete an MFR port, enter the delport <ifNum> command. You must delete connections to the port before deleting the port.

Step 3 To delete an MFR link, enter the delmfrlnk <link> command. You must delete the port before deleting the last link.

Deleting a link sends a Remove-Link request message to the far-end of the link. The bundle stops transmitting data on the link after the Remove-Link request has been sent. However, data received on the link is processed until the acknowledgement for the Remove-Link request is received.

Step 4 To delete an MFR bundle, enter the delmfrbundle <bundleNum> command. You must delete all links from the bundle before deleting the bundle.

Step 5 To verify the deletion of ports, links, or bundles, enter the dspports, dspmfrlnks, or dspmfrbundles commands respectively.

Port Oversubscription on MPSM-T3/E3-155

This release adds Frame Relay port oversubscription to the MPSM-T3/E3-155 card. When enabled, the total committed information rate of all connections on the port can exceed the physical port rate. However, traffic is always limited to the physical port rate.

This feature affects the following commands:

•addport—new -oversub option to enable or disable oversubscription for a new port

•cnfport—new -oversub option to enable or disable oversubscription for an existing port

•dspport— also displays activation and oversubscription status for a port

The following table describes the oversubscription option.

-oversub <value>

Oversubscription control. Enter a number to enable or disable the oversubscription indicator, as follows:

•1 = enable

•2 = disable

Channel Loopback on MPSM-T3E3-155

Channel loopback is a feature that loops all channel traffic (data and OAM) back to the source. There are two types of loopback:

•Ingress—loops incoming line (CPE) traffic back to the line

•Egress—loops outgoing (network) traffic back to the switch

You specify the type of loopback when you activate a channel loopback. You activate, deactivate, and display channel loopbacks using the commands shown in Table 8. Channel loopback configurations are persistent, so they survive a card reset.

Table 8 MPSM-T3E3-155 Channel Loop Commands

Command

Description

addchanloop

Activates a channel loopback

delchanloop

Deactivates a channel loopback

dspchanloop

Displays channels in loopback

Restrictions

The following restrictions apply to channel loopbacks:

•A connection cannot be modified when a loopback is activated.

•A maximum of 8 connection loopbacks can be configured on MPSM-T3/E3-155 card

•Frame Relay connections support Egress loopback only.

Enhancement to Statistics Counters on MPSM-T3E3-155

The dspchancnt command now displays additional Frame Relay statistics. Frame Relay traffic is transmitted and received in AAL5 frames. Table 9 describes the AAL5 statistics for Frame Relay.

Table 9 AAL5 Statistics

Counter

Description

Rcv AAL5 frames

The number of ingress (line) AAL5 frames received.

Rcv CLP0 cells

The number of ingress CLP0 cells received.

Rcv CLP1 cells

The number of ingress CLP1 cells received.

Xmt AAL5 frames

The number of egress (backplane) AAL5 frames transmitted.

Xmt CLP0 cells

The number of egress CLP0 cells transmitted.

Xmt CLP1 cells

The number of egress CLP1 cells transmitted.

Table 10 describes the OAM statistics counters for Frame Relay.

Table 10 OAM Statistics

Counter

Description

Rcv OAM Seg Lpbk Cells

The number of ingress OAM segment loopback cells received.

Rcv OAM E2E Lpbk Cells

The number of ingress end-to-end OAM segment loopback cells received.

Xmt OAM Seg Lpbk Cells

The number of egress OAM segment loopback cells transmitted.

Xmt OAM E2E Lpbk Cells

The number of egress end-to-end OAM segment loopback cells transmitted.

Table 11 describes the ABR statistics for Frame Relay connections.

Table 11 ABR Statistics

Counter

Description

Xmt FRM cells to network

The number of egress Forward RM cells transmitted.

Xmt BRM cells to network

The number of egress Backward RM cells transmitted.

Rcv FRM cells from network

The number of ingress Forward RM cells received.

Rcv BRM cells from network

The number of egress Backward RM cells received.

Features and Enhancements in Previous Release 5.0.10

This section contains the following new features and enhancements in Release 5.0.10:

•CES Line Conditioning

•MPSM Service Modules

•PXM45 RAS

•Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)

•License Management

•AXSM-16-155-XG Feeder Support

•Unique Device Identifier (UDI)

CES Line Conditioning

Previously, on a CESM card with structured ports, the line is not conditioned when an OAM AIS is received on a VC. For unstructured ports, the line is conditioned (AIS is sent on the line). Non line conditioning is a problem for applications that convert T1 to E1. For this application, a structured port of 24 time slots is created on both ends. Therefore, when the T1 line goes into alarm, the far end E1 line stays up.

This feature enables CESM-8-T1E1 and MPSM-8-T1E1 cards in CES mode to send AIS on the line if OAM AIS is received on any channel irrespective of other channels on the line. When line conditioning (lineCondition) is enabled on a connection and OAM AIS is received on the connection from the network, AIS is generated on the line. AIS generation is irrespective of other active connections on the line. Similarly, when the VC stops receiving OAM AIS from the network, AIS generation on the line is stopped. This parameter is only applicable to connections on a structured port.

The following limitations apply to CES conditioning:

1. This channel parameter is not available for configuration upload.

2. Two ends of the CES channels have enabled the line condition, and two ends of the lines have physical loop back. After removing one loop back and inserting back, two ends of the lines are stuck in alarm. The channel is also stuck in alarm.

3. Two ends of the CES channels have enabled the line condition, and two ends of the lines are connected to CPE. Two CPEs that keep having alarms and alarm recovering might cause the line to be stuck in alarm. However, this occurrence is of a very low probability.

Workaround for limitations 2 and 3 is to add a soft loop back (addnloop) to one line, or, disable the line condition from one end of the channel.

Platforms

The feature is supported on the following MGX switches:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

MPSM Service Modules

The MPSM is the next-generation Multi-Protocol Service Module that is intended to support Any-Service-Any-Port (ASAP) or Any-Service-Any-Card (ASAC) functionality. MPSM-8-T1E1 provides the same services currently provided by the FRSM, AUSM, and CESM Cell Bus Service Modules (CBSMs).

The following MPSM cards are supported:

•MPSM-8-T1E1

– ATM

–Frame Relay

–Circuit Emulation

–IMA

–Inline BERT testing

–ASAC

–Same 8-port backcard support as the current CBSMs (AX-RJ48-8E1, AX-RJ48-8E1, AX-SMB-8E1, AX-R-RJ48-8T1, AX-R-RJ48-8E1, AX-R-SMB-8E1)

•MPSM-T3E3-155

–ATM

–Frame Relay

–ASAP

–Inline BERT testing

–OC-3/STM-1 back card with APS support - (SFP-2-155 requires SMFIR-1-155-SFP Optics)

–T3E3 back card (BNC-3-T3E3)

MPSM Licenses

You can purchase MGX systems, spares, and MPSM licenses from www.cisco.com, specifically, http://www.cisco.com/order/apollo/configureHome.html.

Table 12 lists the MPSM licensed services that are available.

Table 12 Available Licensed Services for MPSM-8-T1E1 and MPSM-T3E3-155 Cards

Name of Licensed Service

Product ID of Licensed Service for MPSM-8-T1E1 Card

Product ID of Licensed Service for MPSM-T3E3-155 Card

Description

Multiservice

—

MPSM-MS-HS-LIC(=)

The Multiservice License allows simultaneous provisioning of both ATM and Frame Relay connections on the MPSM-T3E3-155 module.

One license of this type is required by a licensable service module.

RateControl

MPSM-RC-8-LIC (=)

MPSM-RC-HS-LIC(=)

MPSM-8-T1E1: The Rate Control license provides either Standard ABR or Foresight features to Frame Relay connections on the MPSM-8-T1E1 card.

MPSM-T3E3-155: The Rate Control License allows the use of a Standard ABR feature for Frame Relay connections.

One Rate Control license is required by a licensable service module.

Channelization

—

MPSM-CH-HS-LIC(=)

The Channelization License allows the physical port to support multiple DS0s for Frame Relay service and/or DS1s for ATM service.

One license of this type is required by a licensable service module.

Multilink

—

MPSM-ML-HS-LIC(=)

This license covers multilink features, which include IMA (Inverse Multiplexing for ATM) and MFR.

One license of this type is required by a licensable service module.

Note Redundant cards require the same licenses as the primary cards they protect. For 1:N redundancy, a redundant card needs one of each type of license used by the primary cards it protects.

MPSM licenses enable the optional MPSM features listed in Table 13. These features are enabled whenever a feature license is available in the license pool.

Table 13 Feature Options for MPSM Services

Licensed Feature

MPSM-8T1E1

MPSM-T3E3-155

ATM

Circuit Emulation

Frame Relay

ATM

Frame Relay

Rate Control

—

—

X

—

X

Channelization

—

—

—

X

X

Multiservice¹

—

—

—

X

X

Multilink²

—

—

—

X

MFR

¹The multiservice feature allows ATM and Frame Relay services to run simultaneously only on MPSM-T3E3-155 cards.

²The multilink feature enables IMA support for ATM services.

Additional information about MPSM licensing is available as follows:

•For MPSM card specifications, refer to the data sheets at http://www.cisco.com/en/US/products/hw/modules/ps2706/products_data_sheets_list.html.

•For detailed procedures about managing MPSM licenses (for example, with movelic, cnflic, and other commands), refer to Appendix F of the Cisco MGX 8850 (PXM1E/PXM45), MGX 8950, MGX 8830, and MGX 8880 Configuration Guide, Release 5 at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/scg/mgx5scg.pdf. For example, this appendix explains how to transfer license between nodes, and how to relieve a license alarm state.

•For additional information about MPSM cards, refer to the MGX product documentation listings at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/index.htm, starting with Release 5.

Platforms

The feature is supported on:

•MGX 8850 (PXM45, PXM1E)

•MGX 8830 (PXM1E)

PXM45 RAS

The RAS enhancements to the PXM45 platform for Release 5.0.10 include the addition of nine new device tests to the existing Online Diagnostics suite. These enhancements also include the introduction of a new Power On Self Test (POST) functionality to validate hardware upon card bootup. No new configuration needs to be performed to run these tests. POST tests run by default upon card bootup. The new Online Diagnostics tests are configured in the same way as existing tests.

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8830 (PXM45)

•MGX 8950 (PXM45)

Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)

According to ATM forum's TM4.0, ABR connections should have zero in CLP and EFCI bits in the ATM cell. To follow this recommendation, all Frame Relay cards reset CLP and EFCI bits of all outgoing ATM cells irrespective of the value of DE and FECN bits of the incoming frames.

In releases prior to 5.0.10, RM cell generation and DE --> CLP, FECN --> EFCI mapping control are available as a FRSM-8T1E1 card level features for StdABR connections. You can enable or disable RM cell generation and mapping through the command cnfstdabrctrl. Once enabled, all of the StdABR connections on the card behave in the same way.

In this release, you can enable or disable StdABR options at the port level, instead of the card level, by using the CLI command: cnfportstdabrctrl or xcnfport. The CLI command cnfstdabrctrl will be obsolete with the new firmware release.

The RM cell generation options remain the same for the port level as the card level. These options are

1. No RM cell generation, no mapping

2. No RM cell generation, mapping

3. RM cell generation, no mapping

4. RM cell generation, mapping

Platforms

The feature is supported on:

•MGX 8850 (PXM45/B, PXM45/C, FRSM-8T1E1, MPSM-8-T1E1, PXM1E)

•MGX 8830 (PXM1E)

License Management

Some new cards can provide optional services and features in addition to standard features. These optional features can be enabled by installing specific licenses on the node. The following licenses can be installed:

1. MPSM-8-T1E1 cards might require Rate Control (only for FR) licenses.

2. MPSM-T3E3-155 cards might require the following licenses: Multilink (which covers both IMA and MFR), Channelization, Rate Control (only for FR), and Multiservice.

Note CBSM licenses will not transfer to MPSM-8-T1E1 cards. Contact Cisco to obtain MPSM replacement licenses.

Note See Appendix F of the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 for more information about MPSM license procedures.

Platforms

The feature is supported on:

•MGX 8850 (PXM45, PXM1E)

•MGX 8830 (PXM1E)

AXSM-16-155-XG Feeder Support

Previously supported on AXSM and AXSM-E cards, the feeder upstream capability is now supported using the AXSM-16-155-XG card. This feature enables PXM1 feeder nodes to be directly connected to PXM45 8850 and 8950 platforms.

Limitation

IGX feeder nodes are not currently supported.

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950 (PXM45)

Unique Device Identifier (UDI)

Cisco is adopting the Unique Device Identifier (UDI) product identification standard. UDI is an asset management feature that helps Cisco customers better track their Cisco products. Using UDIs, customers can further automate electronic inventory systems and better calculate uptime, thus reducing operating expenses.

The UDI is a combination of identifiers that create a unique value. The UDI includes the orderable Product Identifier (PID), the hardware version identifier (VID), and the product serial number (SN).

MGX releases 5.0.10 and higher support the Cisco-wide UDI initiative. To be compliant with this initiative, the following enhancements have been made for various physical entities, which include non-legacy service modules, switch chassis, and backplanes:

•Five MIB objects of the entityPhysicalTable (in Entity MIB) are populated to provide information about the physical entity in accordance with UDI specifications. Of these five fields, the following combination is called the UDI:

PID (18 Characters) + VID (3 Characters) + SN (11 Characters).

•Though the entityPhysical MIB table can be retrieved to view the above mentioned objects, a new CLI command, show inventory, is required by the UDI initiative. The new command's syntax and output fully conform to UDI standards.

For questions about UDI, contact udi-info@cisco.com.

Limitations

For older service modules, the VID field is not available because VID was not programmed into older service modules' NVRAM. Thus, this object is likely to be missing from older service modules, making older modules non-compliant.

Platforms

UDI is supported on platforms with MGX release 5.0.10 or higher. The feature is supported on:

•MGX 8850 (PXM45

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

Features and Enhancements in Previous Release 5.0.00

This section contains the following new features and enhancements in Release 5.0.00:

•SRME/B

•AXSM-16-155-XG

•AIS Delay, Deroute Delay, Absolute Grooming

•Soft Reroute

•Point to Multipoint Support on PXM1E

•Enhancements to Route Optimization

•Priority Bumping

•Enhancements

SRME/B

This new card is an enhancement of the existing SRME card. Like the SRME, the SRME/B is a single-height card, and the key functions it supports are

•T3 interface along with OC-3

•BERT

•Bulk distribution

•1:N redundancy

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

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

AXSM-16-155-XG

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

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

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

AIS Delay, Deroute Delay, Absolute Grooming

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

Deroute Delay: This feature allows 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, and so forth). This feature was supported in Release 4.0. The SNMP support for this feature is provided in Release 5.0

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

Platforms

This feature is supported on:

•MGX 8850 (PXM45/PXM1E))

•MGX 8950

•MGX 8830 (PXM1E)

Soft Reroute

Currently during grooming process, the connection is derouted and rerouted when the connection is on a PNNI routed path. Even when the desired route is unavailable, the connection is derouted and rerouted using PNNI.

The soft reroute feature allows the user to move a routed SPVC/P from an incumbent working path to a new path with minimal loss of traffic. The existing connection along the path is not derouted until the connection has been established along a new path. Thus, soft route brings higher connection availability. Enhanced grooming process use soft reroute to route a connection on a desired PNNI path.

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

Platforms

This feature is supported on:

•MGX 8850 (PXM45/PXM1E)

•MGX 8950

•MGX 8830 (PXM1E)

Point to Multipoint Support on PXM1E

MGX 8830 (PXM1E) and MGX 8850 (PXM1E) can be used in conjunction with an MGX (PXM45) in a network to support point-to-multipoint connections. The PXM45 hardware performs cell replication to multiple destination endpoints. The MGX with PXM1E functions as the originating node or as a via node of a point-to-multipoint connection. If necessary, MGX with PXM1E can be enabled to perform limited branching or cell replication to support multiple parties or leaves of a point-to-multipoint connection.

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

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

Limitation

Enabling cell replication or branching of more than two leaves per root in the PXM1E node is not recommended for mission-critical point-to-multiple connections due to potential ATM cell drops. Cisco plans to enhance the PXM1E embedded hardware in the future to support cell replication for higher root/leaves ratio with minimal cell drops.

Platforms

This feature is supported on:

•MGX 8850 (PXM1E)

•MGX 8830 (PXM1E)

Enhancements to Route Optimization

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

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

Platforms

This feature is supported on:

•MGX 8850 (PXM45/PXM1E)

•MGX 8950

•MGX 8830 (PXM1E)

Priority Bumping

Priority Bumping involves derouting of other lower priority calls (lower than the incoming call priority) in order to free up resources so that the incoming higher priority call can be routed. Calls might have to be derouted on ingress and egress interfaces to free up resources. Bumping can happen at source, via, or destination nodes. This feature works for SVCs as well as SPVCs. SVCs, which do not have priority signals from CPE/SAPI (in case of voice calls) use the priority of the ingress interface.

Platforms

This feature is supported on:

•MGX 8850 (PXM45/PXM1E)

•MGX 8950

•MGX 8830 (PXM1E)

Enhancements

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

Table 14 Product Enhancement Requests in Release 5.0.00

Enhancement Number or Description

Purpose

Deroute Delay (5048)

See feature description.

Support in PNNI/SMs (AXSM-E, PXM1E) for the CLI commands: tstpndelay and cnfconseq (5494)

For connection fault isolation, MGX provides CLI commands tstpndelay, cnfconsegep, dspconsegep, and delconsegep in earlier releases to debug the connection problem. This project adds the corresponding SNMP interface support and extends the tool to work on PXM1E uplink, AXSM-E, AXSM-XG, AXSM cards, and also broadband SPVC supports.

AIS Delay, Absolute Grooming (6600)

See feature description.

Secure Remote Terminal Interface (6670)

This feature introduces Secure Shell (SSH) functionality on the MGX. SSH provides a secure way to transfer TCP/IP traffic to/from an MGX node, by encrypting all traffic.

TACACS+ for centralized user/password database (7056)

Prior to Release 5.0, each MGX switch maintained its own authentication database and performed its own authentication. In Release 5.0, TACACS+ functionality allows setup of one or more centralized authentication servers.

MGX switches are able to perform authentication against the centralized database, making management easier. Also, prior to Release 5.0, MGX software provided five command privilege levels that could be assigned to a user to authorize execution of all commands allowed by the privilege level. Prior releases do not support authorizing specific command executions on a per user basis. TACACS+ allows customers to configure authorization for a user to execute specific commands.

SNMP support for Memory and CPU utilization statistics (6802)

This feature allows access to historical and real-time data about memory usage and CPU utilization statistics via an SNMP interface. Three MIBS support the above: CISCO-PROCESS_MIB, CISCO-ENHANCED-MEMPOOL-MIB, and CISCO-ATM-CONN-INFO-MIB.

POST, Online Diag, and HMM

POST, Online Diag, and HMM have been enhanced to ease usability and reliability. Commands have been modified and added. Starting in Release 5.0.0, test failures result in recovery actions being taken.

Service Class Template (SCT) File Information

This section contains SCT file information for Release 5.0.20.

MPSM-155

The following are MPSM-155 SCT Files:

•MPSM155_SCT.PORT.1.V1: policing enabled; for ATM/FR ports > 4 T1 in bandwidth

•MPSM155_SCT.PORT.2.V1: policing disabled; for ATM/FR ports > 4 T1 in bandwidth

•MPSM155_SCT.PORT.3.V1:policing enabled; for ATM/FR ports <= 4 T1 in bandwidth

•MPSM155_SCT.PORT.4.V1: policing disabled; for ATM/FR ports <= 4 T1 in bandwidth

•MPSM155_SCT.CARD.1.V1: controls queue settings in the ingress

In addition, the card is equipped with default port and card SCTs built into the code. In case a problem occurs with loading any of the SCT files from the disk, the default SCT is used. The default port SCT is typically the same as MPSM155_SCT.PORT.4.V1. The default card SCT is the same as MPSM155_SCT.CARD.1.V1.

The following are the checksums for the SCT files:

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

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

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

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

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

PXM1E

The SCT bundle in Release 5.0.20 includes the following updates:

•PXM1E_SCT.PORT.5

•PXM1E_SCT.PORT.6

The default SCTs provided with Release 5.0.20 are as follows:

•SCT 5 - policing enabled. In general, this is for use on UNI ports.

•SCT 6 - policing disabled. In general, this is for use on NNI ports.

The checksums for the SCT files are as follows:

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

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

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

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

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

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

See the following notes:

•PXM1E does not support CARD SCT.

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

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

•Use SCTs with larger VC thresholds configured for the VSI signaling service type. The maximum VC threshold value must be at least 50000 microseconds for the VSI signaling service type. New SCTs 5,6 and 54, 55 (Cisco provided SCTs for the T3/E3, Combo cards and IMA group links respectively) have been released with minor version = 1.

Custom SCTs need to be upgraded to a new minor version if needed with the new recommended VC threshold values. You can gracefully upgrade an SCT with minor version change without any traffic impact. Refer to the SCT config chapter of the configuration guide for more details on how to upgrade a SCT file to a new minor version.

AXSM and AXSM/B

The following are the AXSM and AXSM/B files:

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

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

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

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

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

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

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

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

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

Enter dspsctchksum <filename> to confirm that the checksum of the Cisco-released SCT file and the file on the node match. For example:

dspsctchksum C:SCT/TEMP/AXSM_SCT_PORT.3.V1.

AXSM-E

These are the AXSM-E SCT files:

•CARD and PORT SCT 4: Policing enabled for PNNI, disabled for MPLS

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

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

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

•PORT SCT 53: Policing disabled on PNNI and MPLS

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

•PORT SCT 55: Policing disabled on PNNI and MPLS

The following are checksums for SCT files:

•AXSME_SCT.PORT.4.V1: Checksum is = 0x778eb096

•AXSME_SCT.CARD.4.V1: Checksum is = 0x778eb096

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

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

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

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

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

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

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

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

AXSM-XG

The following are the AXSM-4-2488-XG and AXSM-16-155-XG SCT files:

•CARD SCT 2 (OC-48), 3 (OC-192): Policing disabled on PNNI and MPLS. Applied in ingress direction based on backplane bandwidth

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

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

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

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

The checksums are

•AXSMXG_SCT.PORT.100.V1: Checksum is = 0xfc0dc9dd= 4228762077

•AXSMXG_SCT.PORT.200.V1: Checksum is = 0x14148d56= 336891222

•AXSMXG_SCT.PORT.300.V1: Checksum is = 0x618a697= 102278807

•AXSMXG_SCT.PORT.400.V1: Checksum is = 0xdd03a005= 3708002309

•AXSMXG_SCT.PORT.500.V1: Checksum is = 0xd6be5c66= 3602799718

•AXSMXG_SCT.PORT.101.V1: Checksum is = 0x58042fbe= 1476669374

•AXSMXG_SCT.PORT.201.V1: Checksum is = 0x5a41ad5c= 1514253660

•AXSMXG_SCT.PORT.301.V1: Checksum is = 0x96efee80= 2532306560

•AXSMXG_SCT.PORT.401.V1: Checksum is = 0xe41b6263= 3826999907

•AXSMXG_SCT.PORT.501.V1: Checksum is = 0xbbb33b3d= 3149085501

•AXSMXG_SCT.PORT.110.V1: Checksum is = 0xe50e1203= 3842904579

•AXSMXG_SCT.PORT.210.V1: Checksum is = 0x143429f1= 338962929

•AXSMXG_SCT.PORT.310.V1: Checksum is = 0x4c8230b1= 1283600561

•AXSMXG_SCT.PORT.410.V1: Checksum is = 0x1a8d6f6b= 445476715

•AXSMXG_SCT.PORT.510.V1: Checksum is = 0xbf38fdc7= 3208183239

•AXSMXG_SCT.PORT.111.V1: Checksum is = 0x410477e4= 1090811876

•AXSMXG_SCT.PORT.211.V1: Checksum is = 0x5a6149f7= 1516325367

•AXSMXG_SCT.PORT.311.V1: Checksum is = 0xdd59789a= 3713628314

•AXSMXG_SCT.PORT.411.V1: Checksum is = 0x22be71c9= 582906313

•AXSMXG_SCT.PORT.511.V1: Checksum is = 0xa42ddc9e= 2754469022

•AXSMXG_SCT.CARD.2.V1: Checksum is = 0xb564349e= 3043243166

•AXSMXG_SCT.CARD.3.V1: Checksum is = 0x72d4f2c1= 1926558401

System Requirements

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

Software/Firmware Compatibility Matrix

Table 15 lists Cisco WAN or IOS products that are compatible with Release 5.0.20.

Table 15 MGX 5.0.20 Release Compatibility Matrix

Switch or Component

Compatible Software Version

MGX 8230 (PXM1)

MGX 8250 (PXM1)

MGX 8850 (PXM1)

MGX 1.3.11

MGX 1.3.10

MGX 1.3.00

MGX 1.2.23

MGX 1.2.22

MGX 1.2.21

MGX 1.2.13

MGX 8850 (PXM45)

MGX 8850 (PXM1E)

MGX 8950 (PXM45)

MGX 8830 (PXM1E)

MGX 5.0.20

BPX Switch Software

Switch Software 9.4.10

Switch Software 9.3.36, 9.3.45, 9.3.47, 9.3.51

Switch Software 9.2.43, 9.2.45

Cisco WAN Manager

CWM 15.0.00 P3

CWM 15.0.00 P2

CWM 15.0.00 P1

CWM 15.0.00

MGX 8220 Shelf

MGX 8220 5.0.20

SES PNNI

4.0.15

3.0.25

VXSM

VXSM 5.0.20

VISM-PR

VISM 3.3

VISM 3.2.11¹

IOS RPM-PR

12.3(7)T3

IOS RPM-XF

12.3(7)T3

¹VISM Release 3.2.11 replaces VISM Release 3.2.10.

MGX and RPM Software Version Compatibility Matrix

Table 16 lists the software that is compatible for use in a switch running Release 5.0.20 software.

Table 16 MGX and RPM Software Version Compatibility Matrix

Board Pair

Boot Software

Minimum
Boot
Code
Version

Runtime Software

Latest
Firmware
Version

Minimum
Firmware
Version

PXM45/B

pxm45_005.000.020.203_bt.fw

5.0.20

pxm45_005.000.020.205_mgx.fw

5.0.20

5.0.20

PXM45/C

pxm45_005.000.020.203_bt.fw

5.0.20

pxm45_005.000.020.205_mgx.fw

5.0.20

5.0.20

PXM1E-4-155 MGX 8850 (PXM1E) chassis

pxm1e_005.000.020.203_bt.fw

5.0.20

pxm1e_005.000.020.203_mgx.fw

5.0.20

5.0.20

PXM1E-8-155 MGX 8850 (PXM1E) chassis

PXM1E-8-T3E3 MGX 8850 (PXM1E) chassis

PXM1E-COMBO MGX 8850 (PXM1E) chassis

PXM1E-8-155

PXM1E-4-155 MGX 8830 chassis

pxm1e_005.000.020.203_bt.fw

5.0.20

pxm1e_005.000.020.203_m30.fw

5.0.20

5.0.20

PXM1E-8-T3E3 MGX 8830 chassis

PXM1E-COMBO MGX 8830 chassis

MPSM-T3E3-155

mpsm155_005.000.020.202_
bt.fw

5.0.20

mpsm155_005.000.020.202.fw

5.0.20

5.0.20

AXSM-1-2488

axsm_005.000.020.201_bt.fw

5.0.20

axsm_005.000.020.201.fw

5.0.20

5.0.20

AXSM-16-155

AXSM-4-622

AXSM-16-T3/E3

AXSM-1-2488/B

axsm_005.000.020.201_bt.fw

5.0.20

axsm_005.000.020.201.fw

5.0.20

5.0.20

AXSM-16-155/B

AXSM-4-622/B

AXSM-16-
T3/E3/B

AXSM-2-622-E

axsme_005.000.020.200_bt.fw

5.0.20

axsme_005.000.020.200.fw

5.0.20

5.0.20

AXSM-8-155-E

AXSM-16-
T3E3-E

AXSM-32-
T1E1-E

AXSM-16-155-
XG

axsmxg_005.000.020.204_bt.fw

5.0.20

axsmxg_005.000.020.204.fw

5.0.20

5.0.20

AXSM-4-2488-
XG

AXSM-1-9953-
XG

MGX-VXSM-
155

vxsm_005.000.002.200_bt.fw

5.0.20

vxsm_005.050.002.200.fw
(CALEA image)

vxsm_005.000.002.200.fw
(non-CALEA image)

5.0.20

5.0.20

MGX-VXSM-
T1E1

vxsm_005.000.002.200_bt.fw

5.0.20

vxsm_005.050.002.200.fw
(CALEA image)

vxsm_005.000.002.200.fw
(non-CALEA image)

5.0.20

5.0.20

MGX-SRME

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

MGX-SRME/B

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

SRM3T3/C

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

MPSM-8-T1E1

mpsm_t1e1_030.000.020.202_
bt.fw

30.0.20

mpsm_t1e1_030.000.020.202.fw

30.0.20

30.0.20

AX-CESM-8E1

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

AX-CESM-8T1

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

MGX-CESM-
8T1/B

cesm_8t1e1_CE8_BT_1.0.02.fw

1.0.02

cesm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

MGX-AUSM-
8T1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

1.0.02

ausm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

MGX-AUSM-
8E1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

1.0.02

ausm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

AX-FRSM-8T1

frsm_8t1e1_FR8_BT_1.0.06.fw

1.0.06

frsm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

AX-FRSM-8E1

frsm_8t1e1_FR8_BT_1.0.06.fw

1.0.06

frsm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

AX-FRSM-8T1-C

frsm_8t1e1_FR8_BT_1.0.06.fw

1.0.06

frsm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

AX-FRSM-8E1-C

frsm_8t1e1_FR8_BT_1.0.06.fw

1.0.06

frsm_8t1e1_022.000.020.200.fw

22.0.20

22.0.20

MGX-FRSM-
HS2/B

frsm_vhs_VHS_BT_1.0.07.fw

1.0.07

frsm_vhs_022.000.020.200.fw

22.0.20

22.0.20

MGX-FRSM-
2CT3

frsm_vhs_VHS_BT_1.0.07.fw

1.0.07

frsm_vhs_022.000.020.200.fw

22.0.20

22.0.20

MGX-FRSM-
2T3E3

frsm_vhs_VHS_BT_1.0.07.fw

1.0.07

frsm_vhs_022.000.020.200.fw

22.0.20

22.0.20

MGX-RPM-PR-
256

rpm-boot-mz.123-7.T3

12.3(7)T3

rpm-js-mz.123-7.T3

12.3(7)
T3

12.3(2)T5

MGX-RPM-PR-
512

rpm-boot-mz.123-7.T3

12.3(7)T3

rpm-js-mz.123-7.T3

12.3(7)
T3

12.3(7)T3

MGX-RPM-XF-
512

rpmxf-boot-mz.123-7.T3

12.3(7)T3

rpmxf-p12-mz.123-7.T3

12.3(7)
T3

12.3(7)T3

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

3.2.0

vism-8t1e1-003.053.000.200.fw (CALEA image)

vism-8t1e1-003.003.000.200.fw (non-CALEA image)

3.53.00

3.3.00

3.53.00

3.3.00

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

3.2.0

vism-8t1e1-003.053.000.200.fw (CALEA image)

vism-8t1e1-003.003.000.200.fw (non-CALEA image)

3.53.00

3.3.00

3.53.00

3.3.00

Additional Notes

None.

SNMP MIB Release

The SNMP MIB release for 5.0.20 is mgx8xxxrel5020mib.tar.

Note SNMP manuals are replaced by the online MIB tool at URL http://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp

Hardware Supported

This section lists:

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

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

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

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

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

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

New Hardware in Release 5.0.20

No new hardware was introduced in Release 5.0.20.

New Hardware in Release 5.0.10

The following new hardware is introduced in Release 5.0.10:

•MPSM-T3E3-155

•SFP-2-155

•SMB-2-155-EL

•MPSM-8-T1E1

•MGX-XF-UI/B

•AXSM-8-155-XG

Product IDs, Card Types, and APS Connectors

MGX 8850 (PXM45/PXM1E), MGX 8950, and MGX 8830 Product IDs and Card Types

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

Table 18 presents a guide on which APS connector to use with which MGX chassis and front card.

In these tables:

•R- means that this is a redundant card, for AX-R-RJ48-8E1, AX-R-RJ48-8T1, and AX-R-SMB-8E1 cards.

•Either of these connectors work for the AXSM cards in the MGX 8850 (PXM45) switch: MGX-8850-APS-CON or MGX-APS-CON.

•The PXM45 card is not supported in Release 5.0.00 and higher. The PXM45/B and PXM45/C cards are supported.

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

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

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

Table 17 MGX Chassis, Card, and APS Connector Configurations

Front Card Type

Min. 800 Part Number and Revision

Back Card Types

APS

Con

Min. 800 Part Number and Revision

MGX 8850

PXM45

MGX 8850

PXM1E

MGX 8830

PXM1E

MGX 8950

PXM45

PXM45/C

800-20217-04-A0

PXM-HD

—

800-05052-03-A0

x

—

—

x

PXM-UI-S3/B

—

800-21557-01-A0

PXM45/B

800-09266-04-A0

PXM-HD

—

800-05052-03-A0

x

—

—

x

PXM-UI-S3

—

800-05787-02-A0

PXM1E-8-155

800-21686-05-A0

SFP-8-155

SMFIR-1-155-SFP

SMFLR-1-155-SFP

MMF-1-155-SFP

Yes

800-21518-03-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

—

x

x

—

MCC-8-155

Yes

800-22117-02-A0

PXM-UI-S3/B

—

800-21557-01-A0

PXM1E-4-155

800-18588-03-A0

MMF-4-155/C

Yes ^¹

800-07408-02-A0

—

x

x

—

SMFIR-4-155/C

Yes ¹

800-07108-02-A0

SMFLR-4-155/C

Yes¹

800-07409-02-A0

PXM-UI-S3/B

—

800-21557-01-A0

PXM1E-8-T3E3

800-18590-03-A0

SMB-8-T3

—

800-05029-02-A0

—

x

x

—

SMB-8-E3

—

800-04093-02-A0

PXM-UI-S3/B

—

800-21557-01-A0

PXM1E-16-T1E1

800-18658-04-A0

MCC-16-E1

—

800-19853-02-A0

—

x

x

—

RBBN-16-T1E1

—

800-21805-03-A0

PXM-UI-S3/B

—

800-21557-01-A0

PXM1E-T3E3-155

Also referred to as

PXM1E-COMBO

800-18604-03-A0

MGX-T3E3-155

SMFIR-1-155-SFP

SMFLR-1-155-SFP

MMF-1-155-SFP

—

800-18698-02-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

—

x

x

—

PXM-UI-S3/B

—

800-21557-01-A0

XM-60

800-04706-06-A0

—

—

—

—

—

—

x

MGX-APS-CON

800-05307-01-A0

—

—

—

x

—

—

—

MGX-8850-APS-
CON

800-20640-01-A0

—

—

—

x

x

—

—

MGX-8830-APS-
CON

800-05308-02-

—

—

—

—

—

x

—

MGX-8950-APS-
CON

800-15308-01-A0

—

—

—

—

—

—

x

MGX8950-EXTDR-CON

800-23813-03-A0

—

—

—

—

—

—

x

MPSM-T3E3-155

800-23005-06-A0

SFP-2-155

Yes

800-23170-02-A0

x

x

x

—

BNC-3-T3E3

—

800-23142-04-A0

SMB-2-155-EL

Yes

800-23171-03-A0

MPSM-8-T1E1

800-24473-07-A0

AX-RJ48-8T1

—

800-02286-01-A0

x

x

x

—

AX-R-RJ48-8T1

—

800-02288-01-A0

AX-RJ48-8E1

—

800-02408-01-A0

AX-R-RJ48-8E1

—

800-02409-01-A0

AX-SMB-8E1

—

800-02287-01-A0

AX-R-SMB-8E1

—

800-02410-01-A0

AXSM-1-9953-XG

800-07365-06-A0

SMFSR-1-9953

—

800-08237-06-A0

—

—

—

x

SMFIR-1-9953

—

800-08246-06-A0

SMFLR-1-9953

—

800-08247-06-A0

AXSM-4-2488-XG

800-16987-04-A0

SMF-4-2488-SFP

SMFSR-1-2488-
SFP

SMFLR-1-2488-
SFP

—

800-19913-04-A0

10-1421-03

10-1742-01

—

—

—

x

AXSM-1-2488

800-05795-05-A0

SMFSR-1-2488

Yes

800-05490-05-A0

x

—

—

—

SMFLR-1-2488

Yes

800-06635-04-A0

SMFXLR-1-2488

Yes

800-05793-05-A0

AXSM-1-2488/B

800-07983-02-A0

SMFSR-1-2488/B

Yes

800-07255-01-A0

x

—

—

x

SMFLR-1-2488/B

Yes

800-08847-01-A0

SMFXLR-1-
2488/B

Yes

800-08849-01-A0

AXSM-4-622

800-05774-09-B0

SMFIR-2-622

Yes

800-05383-01-A1

x

—

—

—

SMFLR-2-622

Yes

800-05385-01-A1

AXSM-4-622/B

800-07910-05-A0

SMFIR-2-622/B

Yes

800-07412-02-B0

x

—

—

x

SMFLR-2-622/B

Yes

800-07413-02-B0

AXSM-2-622-E

800-18521-02-A0

SMFIR-1-622/C

Yes

800-07410-02-A0

x

—

—

—

SMFLR-1-622/C

Yes

800-07411-02-A0

AXSM-16-155-XG

800-20821-06-A0

SFP-8-155

SMFIR-1-155-SFP

SMFLR-1-155-SFP

MMF-1-155-SFP

Yes

800-21518-03-A0

10-1283-01-A0

10-1280-01-A0

10-1308-01-A0

x

—

—

x

MCC-8-155

Yes

800-22117-02-A0

AXSM-16-155

800-05776-06-A0

MMF-8-155-MT

Yes

800-04819-01-A1

x

—

—

—

SMFIR-8-155-LC

Yes

800-05342-01-A0

SMFLR-8-155-LC

Yes

800-05343-01-C0

AXSM-16-155/B

800-07909-05-A0

MMF-8-155-MT/B

Yes

800-01720-02-A0

x

—

—

x

SMFIR-8-155-
LC/B

Yes

800-07864-02-B0

SMFLR-8-155-
LC/B

Yes

800-07865-02-B0

AXSM-8-155-E

800-18520-02-A0

SMB-4-155

Yes

800-07425-02-A0

x

—

—

—

MMF-4-155/C

Yes

800-07408-02-A0

SMFIR-4-155/C

Yes

800-07108-02-A0

SMFLR-4-155/C

Yes

800-07409-02-A0

AXSM-16-T3E3 AXSM-16-T3E3/B

AXSM-16-T3E3-E

800-05778-08-A0

800-07911-05-A0

800-18519-02-A0

SMB-8-T3

—

800-05029-02-A0

x

x

x

—

—

x

SMB-8-E3

—

800-04093-02-A0

AXSM-32-T1E1-E

800-22229-01-A0

MCC-16-E1

—

800-19853-02-A0

x

—

—

—

RBBN-16-T1E1

—

800-21805-03-A0

MGX-VXSM-155

800-15121-06-A0

VXSM-BC-4-155

—

800-21428-06-A0

x

—

—

—

MGX-VXSM-T1E1

800-24073-02-A0

VXSM-R-BC

—

800-21427-05-A0

x

—

—

—

VXSM-BC-
24T1E1

—

800-23088-03-A0

MGX-VISM-PR-8T1

800-07990-02-A0

AX-RJ48-8T1

—

800-02286-01-A0

x

x

x

—

AX-R-RJ48-8T1

—

800-02288-01-A0

MGX-VISM-PR-8E1

800-07991-02-A0

AX-SMB-8E1

—

800-02287-01-A0

x

x

x

—

AX-R-SMB-8E1

—

800-02410-01-A0

AX-RJ48-8E1

—

800-02408-01-A0

AX-R-RJ48-8E1

—

800-02409-01-A0

MGX-RJ48-8E1

—

800-19310-01-B0

MGX-SRME

800-14224-02-A0

MGX-SMFIR-1-155

Yes ²

800-14460-02-A0

x

x

x

—

MGX-STM1-EL-1

Yes ²

800-23175-03-A0

MGX-SRME/B

800-21629-03-A0

MGX-BNC-3T3-M

—

800-03148-02-A0

x

x

x

—

MGX-STM1-EL-1

—

800-23175-03-A0

MGX-SRM-3T3/C

800-05648-01-A0

MGX-BNC-3T3-M

—

800-03148-02-A0

x

x

x

—

MGX-AUSM-8T1/B

800-04809-01-A0

AX-RJ48-8T1

—

800-02286-01-A0

x

x

—

AX-R-RJ48-8T1

—

800-02288-01-A0

MGX-AUSM-8E1/B

800-04810-01-A0

AX-SMB-8E1

—

800-02287-01-A0

x

x

—

AX-R-SMB-8E1

—

800-02410-01-A0

AX-RJ48-8E1

—

800-02408-01-A0

AX-R-RJ48-8E1

—

800-02409-01-A0

MGX-RJ48-8E1

—

800-19310-01-B0

AX-CESM-8E1

800-02751-02-A0

AX-SMB-8E1

—

800-02287-01-A0

x

x

x

—

AX-R-SMB-8E1

—

800-02410-01-A0

AX-RJ48-8E1

—

800-02408-01-A0

AX-R-RJ48-8E1

—

800-02409-01-A0

MGX-RJ48-8E1

—

800-19310-01-B0

AX-CESM-8T1

800-02750-03-B0

AX-RJ48-8T1

—

800-02286-01-A0

x

—

—

—

AX-R-RJ48-8T1

—

800-02288-01-A0

MGX-CESM-8T1/B

800-08613-02-A0

AX-RJ48-8T1

—

800-02286-01-A0

x

x

x

—

AX-R-RJ48-8T1

—

800-02288-01-A0

AX-FRSM-8E1

800-02438-04-A0

AX-SMB-8E1

—

800-02287-01-A0

x

x

x

—

AX-FRSM-8E1-C

800-02462-04-A0

AX-R-SMB-8E1

—

800-02410-01-A0

AX-RJ48-8E1

—

800-02408-01-A0

AX-R-RJ48-8E1

—

800-02409-01-A0

MGX-RJ48-8E1

—

800-19310-01-B0

AX-FRSM-8T1

800-02461-04-A0

AX-RJ48-8T1

—

800-02286-01-A0

x

x

x

—

AX-FRSM-8T1-C

800-02461-04-A0

AX-R-RJ48-8T1

—

800-02288-01-A0

—

—

—

—

MGX-FRSM-2CT3

800-06335-01-D0

MGX-BNC-2T3

—

800-04057-02-A0

x

x

x

—

MGX-FRSM-2T3E3

800-02911-07-D0

MGX-BNC-2E3

—

800-04056-02-A0

x

x

x

—

MGX-BNC-2T3

—

800-04057-02-A0

FRSM-12-T3E3³

800-18731-02-A0

SMB-6-T3E3

—

800-08799-01-A0

x

—

—

—

MGX-FRSM-HS2/B

800-17066-01-A0

SCSI2-2HSSI/B

—

800-05463-02-A0

800-05501-01-A0

x

x

—

MGX-12IN1-8S

—

800-18302-01-A0

MGX-RPM-PR-256

800-07178-02-A0

MGX-MMF-FE

—

800-03202-02-A0

x

x

x

x

MGX-RPM-PR-512

800-07656-02-A0

MGX-RJ45-4E/B

—

800-12134-01-A0

MGX-RJ45-FE

—

800-02735-02-A0

MGX-RPM-XF-512

800-09307-06-A0

MGX-XF-UI

—

800-09492-01-A0

x

—

—

x

MGX-1-GE

—

800-18420-03-A0

MGX-2-GE

—

800-20831-04-A0

MGX-1OC12POS-IR

—

800-08359-05-A0

MGX-2OC12POS-IR

—

800-21300-04-A0

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

—

30-1301-01-A0

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

—

30-1299-01-A0

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

—

10-1439-01-A0

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

²APS connectors are not required in 8830 chassis.

³The FRSM-12-T3E3 card is not supported.

Table 18 APS Connectors Required for Each Chassis and Type of Front Card

Chassis Type

MGX-APS-CON

800-05307-01

MGX-8850-APS-CON

800-20640-01-A0

MGX-8830-APS-CON

800-05308-02

MGX-8950-APS-CON

800-15308-01-A0

MGX 8850 (PXM45)

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155-XG

MGX-SRME

MGX-SRME/B

MPSM-T3E3-155 1

—

—

MGX 8850 (PXM1E)

—

PXM1E-4-155 2

PXM1E-8-155

MGX-SRME

MGX-SRME/B

MPSM-T3E3-155 1

—

—

MGX 8830

—

—

PXM1E-4-155 2

PXM1E-8-155

MPSM-T3E3-155 1

—

MGX 8950

—

—

—

AXSM-16-155/B

AXSM-4-622/B

AXSM-1-2488/B

AXSM-16-155-XG

1. Required only if running in OC-3 mode.

2: APS connectors are required if you want to upgrade to a PXM1E-8-155 card without interrupting service.

New and Changed Commands

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

In this section:

•A means the command is available in the Active card state.

•S means the command is available in the Standby card state.

•I means the command is available in the Init card state.

Refer to the following documents for details about commands:

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

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

•Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.x

New and Changed MPSM-T3E3-155 Commands

This section lists commands that are new, changed, or removed in Release 5.0.20 code for MPSM-T3E3-155 cards.

New Multilink Frame Relay Commands

The following Multilink Frame Relay commands are new in Release 5.0.20.

Table 19 lists the MFR commands on the MPSM-T3E3-155 card and provides a brief functional description of each command.

Table 19 MPSM-T3E3-155 Multilink Frame Relay Commands and Descriptions

Command

Description

addmfrbundle

Adds the MFR Bundle

addmfrlnk

Adds the MFR Link to a MFR Bundle

addmfrport

Adds the MFR Port and configures the Frame relay parameters for the MFR Bundle

clrmfrbundlecnt

Clears all the counts associated with a MFR Bundle

clrmfrbundlecnts

Clears all the counts associated with all MFR Bundles provisioned on the card

clrmfrlnkcnt

Clears the counters associated with a link on a specific MFR Bundle

clrmfrlnkcnts

Clears the counters associated with all links on a specific MFR Bundle

cnfmfrbundle

Modifies the configuration of the MFR Bundle

cnfmfrlnk

Configures the MFR Link in a MFR Bundle

delmfrbundle

Deletes the MFR Bundle

delmfrlnk

Deletes a specific link belonging to a specific bundle

dnmfrbundle

Puts the MFR Bundle in administratively DOWN state

dspmfrbundle

Displays the configuration of a MFR Bundle

dspmfrbundlealm

Displays the alarm status for a MFR Bundle

dspmfrbundlealms

Displays alarm status for all MFR Bundles provisioned on the card

dspmfrbundlebucketcnt

Displays the MFR bundle bucket counters

dspmfrbundlecnt

Displays the counters associated with a MFR Bundle

dspmfrbundles

Displays all the MFR Bundles provisioned on the card

dspmfrlnk

Displays the configuration of a MFR link

dspmfrlnkalm

Displays the alarm status of the specified link associated with a specific MFR Bundle

dspmfrlnkalms

Displays the alarm status of all links associated with a specific MFR Bundle

dspmfrlnkbucketcnt

Displays the MFR link bucket counters

dspmfrlnkcnt

Displays the counters associated with a MFR link

dspmfrlnks

Displays all MFR links on the MPSM

upmfrbundle

Puts the MFR Bundle in administratively UP state

addmfrbundle

Add Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the addmfrbundle command to add an MFR bundle.

Syntax

addmfrbundle <bundleNum> <activationClass>

Syntax Description

bundleNum

Bundle Number, range 1-42

activationClass

Bundle activation class:

•1 = Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2 = Class B—All the bundle links must be operational for the MFR Bundle to be operational

•3 = Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

cnfmfrbundle, delmfrbundle, dspmfrbundle

Example

In the following example, the user adds MFR bundle number 5 with Class A activation.
M8850_SF.10.MPSM155[FR].a > addfmrbundle 3 1
Note Adding a bundle does not automatically create an MFR port for the bundle. Add the MFR port using the addmfrport command.

addmfrlnk

Add Multi-link Frame Relay Link

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the addmfrlnk command to add links to an MFR bundle.

Syntax

addmfrlnk <link> <bundleNum>

Syntax Description

link

Specifies a DS1 or E1 path:

•DS3 payload: bay.line.sts:ds1

•VT payload: bay.line.sts:vtg.vt

•VT structured: bay.line.sts:tug3.vtg.vt

where: bay=1, line=1-3, sts=0-3, ds1=1-28,
tug3=1-3, vtg=1-7, vt=1-4 (VT15) or 1-3 (VT2)

Note Enter the dsppaths -all command to display all available paths on the card.

bundleNum

Bundle number, range 1-42.

Note Enter the dspmfrbundles command to display all bundles on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

cnfmfrlnk, dspmfrlnk, delmfrlnk, dspmfrbundles

Example

In the following example, the user adds DS1 link 1.1:11 to bundle 3.
M8850_SF.10.MPSM155[FR].a > addmfrlnk 1.1:11 3 
addmfrport

Add Multi-link Frame Relay Port

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the addmfrport command to add and configure a port for an MFR bundle.

Syntax

addmfrport <ifNum> <bundle> <portType> <sct>
[-rat <rat>] [-oversub <oversub>]
[-lmiSig <lmiSigType> ] [-asynUpdt <updateType>]
[-elmi <elmiState>][-segLmi <segLmiStatus>]
[-t391 <t391Value>] [-t392 <t392Value>]
[-n391 <n391Value>] [-n392 <n392Value>][-n393 <n393Value>]

Syntax Description

ifNum

A number for the port, in the range 1-1003.

bundleNum

The MFR bundle number, in the range 1-42.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

portType

Type of logical interface (port):

•1 = Frame Relay Service

•3 = Frame Forward (Not applicable for MFR bundles)

sct

The Service class template (SCT) for the port, range 0-255.

Default: 0

Note The SCT file must exist on the PXM disk. Enter the cnfcdsct command to verify that the appropriate SCT exists on the PXM.

-rat

The egress service ratio of the high priority and the low priority queues, range 0-15.

•Enter 0 to indicate that no service ratio is configured. In this case, bandwidth is allocated to both the high priority and the low priority queues on demand, which means that traffic is dynamically allocated on a first-come, first-serve basis.

•The default setting is 1. In this case, the traffic of the CBR and rt-VBR service categories is allocated to the high priority queue, while the traffic of the nrt-VBR, ABR, and UBR service categories is allocated to the low priority queue.

-oversub

Oversubscription control:

•1 = enable

•2 = disable (default)

-lmiSig

LMI signaling protocol type:

•2 = No Signaling (default)

•3 = StrataLMI

•4 = AnnexAUNI

•5 = AnnexDUNI

•6 = AnnexANNI

•7 = AnnexDNNI

Note When LMI is configured, the maximum number of connections per port for Strata LMI port is 560 and for Annex A/D UNI/NNI port is 898.

-asynUpdt

Enables or disables asynchronous updates. Asynchronous updates are an extension to the LMI protocol that notify the user immediately of changes in PVC and Multicast status. Before enabling this feature, make sure that any DTE equipment you are connected to supports asynchronous updates from the network.

Asynchronous update control:

•1 = Disable both Asynchronous Status Updates and Unsolicited Full Status (default)

•2 = Enable Asynchronous Status Updates

•3 = Enable Unsolicited Full Status

•4 = Enable Asynchronous Status Updates and Unsolicited Full Status

-elmi

Enable or disable enhanced LMI. Enhanced LMI enables the automatic exchange of Frame Relay QoS parameter information between the DTE and DCE. When enabled on both the DTE and the MPSM port, this allows the DTE device to learn QoS parameters from the frame relay port and use them for traffic shaping, configuration, or management purposes.

•1 = enable

•2 = disable (default)

-segLmi

Segmented LMI control:

•1 = enable

•2 = disable (default)

-t391

T391 timer. This is the Link Integrity Verification polling timer. The user (DTE) sends Status Enquiry messages to the network (DCE) every T391 seconds. An error is recorded if a Status message is not received within T391 seconds. The T391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 5-30. Default: 10

-t392

T392 timer. This is the Polling Verification timer. The network (DCE) expects Status Enquiry messages from the user (DTE) every T392 seconds. If the network does not receive a Status Enquiry message from the user within T392 seconds and the timer expires, then the network records a missing Status Enquiry message by incrementing the N392 counter. This timer value must be set greater than the T391 timer. The T392 timer always applies to the network. It applies to the network and user if NNI bi-directional polling is present. Range 5-30. Default: 15

-n391

N391 counter. This setting establishes the Full Status (status of all PVCs) polling cycle. The user (DTE) sends a Full Report Status Enquiry to the network (DCE) every N391 polls. The N391 counter always applies to the user equipment. It applies to the user and network if NNI bi-directional polling is present. Range 1- 255. Default: 6

-n392

N392 counter. This setting specifies the UNI/NNI error threshold. This is the number of errors during N393 events that will cause an error condition. This counter should be less than or equal to the N393 counter. This counter can apply to both the user (DTE) and the network (DCE). Range 1-10. Default: 3

-n393

N393 counter. This setting is the monitored UNI/NNI events count, which must be greater than the N392 counter. N392 errors during N393 events will cause an error condition. If the N393 counter is set to a value much less than the N391 counter, the port could go in and out of an error condition without notification to either the user equipment or the network. This counter can apply to both the user (DTE) and the network (DCE). The value of this parameter should be greater than that for the -n392 parameter. Range: 1-10. Default: 4

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

cnfport, delport, dspport

Example

In the following example, the user adds a port for MFR bundle 3, specifying Frame Relay Service and the default service class template.
M8850_SF.10.MPSM155[FR].a > addmfrport 111 3 1 0
clrmfrbundlecnt

Clear counts on a Multi-Link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the clrmfrbundlecnt command to clear the statistics counters for an MFR bundle.

Syntax

clrlmfrbundlecnt <bundleNumber>

Syntax Description

bundleNumber

Specifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: yes

State: active

Privilege: any

Related Commands

dspmfrbundlecnt

Example

In the following example, the user clears the counters for bundle 5.
M8850_SF.10.MPSM155[FR].a > clrmfrbundlecnt 5
clrmfrbundlecnts

Clear all counters on a Multi-Link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the clrmfrbundlecnts command to clear the statistics counters on all MFR Bundles.

Syntax

clrlmfrbundlecnts

Syntax Description

This command does not have any parameters.

Attributes

Log: yes

State: active

Privilege: any

Related Commands

dspmfrbundlecnt

Example

In the following example, the user clears all counters for all MFR bundles.
M8850_SF.10.MPSM155[FR].a > clrmfrbundlecnts
clrmfrlnkcnt

Clear Multi-link Frame Relay Link Counts

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the clrmfrlnkcnt command to clear the statistics counters for an MFR link.

Syntax

clrmfrlnkcnt <link>

Syntax Description

link

Specifies the MFR link for which to clear statistics.

Enter the dspmfrlnks command to display all MFR links on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

dspmfrlnkcnt, dspmfrlnks

Example

In the following example, the user clears counters for link 1.1:11.
M8850_SF.10.MPSM155[FR].a > clrmfrlnkcnt 1.1.:11
clrmfrlnkcnts

Clear all Multi-link Frame Relay Link Counts on a Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the clrmfrlnkcnts command to clear all statistics counters for all MFR links.

Syntax

clrmfrlnkcnts

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

dspmfrlnkcnt

Example

In the following example, the user clears all link counters.

M8850_SF.10.MPSM155[FR].a > clrmfrlnkcnts

cnfmfrbundle

Configure Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the cnfmfrbundle command to configure an MFR bundle.

Syntax

cnfmfrbundle -bundle <bundleNum>
[-class <activationclass>] [-minlinks <minimumlinks>]
[-hellotimer <hellotimer>] [-acktimer <acktime>]
[-maxretry <maxretry>] [-bname <bundleName>]

Syntax Description

-bundle

Identifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

-class

Bundle activation class:

•1 = Class A—At least one bundle links must be operational for the MFR Bundle to be operational

•2 = Class B—All the bundle links must be operational for the MFR Bundle to be operational

•3 = Class C—Configured number of bundle links must be operational for the MFR Bundle to be operational.

-minlinks

Minimum number of Links for Class-C activation class, range 1-12.

-hellotimer

Interval for sending hello messages, range 1-180 seconds

-acktimer

Maximum time period to wait for an acknowledgement from the far end, range 1-10 seconds

-maxretry

Maximum number of Retries (Maximum retries), range 1-5 retries.

-bname

Near-end bundle name:

A null-terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters, with a maximum of 49 characters.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrbundle, delmfrbundle, dspmfrbundle, dspmfrbundles

Example

In the following example, the user sets the hello timer to 20 seconds for MFR bundle 3.
M8850_SF.10.MPSM155[FR].a > cnfmfrbundle -bundle 3 -hellotimer 20 
cnfmfrlnk

Configure Multi-link Frame Relay Link

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the cnfmfrlnk command to configure the name of an MFR link.

Syntax

cnfmfrlnk -link <lnkNum> -lname <linkname>

Syntax Description

-link

Specifies the MFR link number:

Note Enter the dspmfrlnks command to display all MFR links on the card.

-lname

Near-end link name:

A null -terminated string consisting of ASCII characters A-Z, a-z, 0-9 and any printable characters with a maximum of 49 characters.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrlnk, delmfrlnk, dspmfrlnk, dspmfrlnks

Example

In the following example, the user sets the name of MFR link 1.1:11 to GoldenGateLink111.
M8850_SF.10.MPSM155[FR].a > cnfmfrlnk -link 1.1:11 -lname GoldenGAteLink111
delmfrbundle

Delete Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the delmfrbundle command to delete an MFR bundle. You must remove all links from the bundle before deleting the bundle.

Syntax

delmfrbundle <bundleNumber>

Syntax Description

bundleNumber

Specifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrbundle, cnfmfrbundle, dspmfrbundle, dspmfrbundles

Example

In the following example, the user deletes MFR bundle 3.
M8850_SF.10.MPSM155[FR].a > delmfrbundle 3
delmfrlnk

Delete a Multi-link Frame Relay Link

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the delmfrlnk command to delete a link from an MFR bundle. You must delete the MFR port before deleting the last link from the bundle.

Syntax

delmfrlnk <link>

Syntax Description

link

Specifies the MFR link to delete.

Note Enter the dspmfrlnks command to display all MFR links on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrlnk, cnfmfrlnk, dspmfrlnk, dspmfrlnks

Example

In the following example, the user deletes MFR link 1.1:11.

M8850_SF.10.MPSM155[FR].a > delmfrlnk 1.1.11

dnmfrbundle

Down a Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dnmfrbundle command to deactivate an MFR bundle.

Syntax

dnmfrbundle <bundleNumber>

Syntax Description

bundleNumber

Specifies the number of the MFR bundle to bring down.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

upmfrbundle, dspmfrbundles

Example

In the following example, the user brings down MFR bundle 2.
M8850_SF.10.MPSM155[FR].a > dnmfrbundle 2
Warning: Traffic loss will result on all connections on this MFR bundle.
Do you want to proceed (Yes/No) ? y

dspmfrbundle

Display Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundle command to display configuration information and operational status for an MFR bundle.

Syntax

dspmfrbundle <bundleNumber>

Syntax Description

bundleNumber

Identifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: no

State: active

Privilege: any

Related Commands

addmfrbundle, cnfmfrbundle, delmfrbundle

Example

In the following example, the user displays MFR bundle 1.
M8850_SF.10.MPSM155[FR].a > dspmfrbundle 1
    Bundle Number                   : 1
    Activation Class                : A
    Minimum Links                   : 1
    Admin state                     : Up
    Oper State                      : Up
    Hello Timer (seconds)           : 10
    Ack Timer (seconds)             : 4
    Max Retry Count                 : 2
    Maximum Bundle Links            : 12
    Configured Number of Links      : 4
    Active Number of Links          : 4
    Available Bandwidth             : 6176000
    Near End Bundle Name            : M8850_SF.Slot10.Bundle01
    Far End Bundle Name             : M8850_SF.Slot10.Bundle02
dspmfrbundlealm

Display Multi-link Frame Relay Bundle Alarm

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundlealm command to display the alarm status of an MFR bundle.

Syntax

dspmfrbundlealm <bundleNum>

Syntax Description

bundleNum

Identifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: no

State: active

Privilege: any

Related Commands

dspmfrbundlealms

Example

In the following example, the user displays the alarm status of MFR bundle 1.
M8850_SF.10.MPSM155[FR].a > dspmfrbundlealm 1
Bundle Number                 : 1
Admin State                   : Up
Oper State                    : Up
Alarm State                   : Clear 
dspmfrbundlealms

Display Multi-link Frame Relay Bundle Alarm

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundlealms command to display alarm status for all MFR bundles provisioned on the card.

Syntax

dspmfrbundlealms

Syntax Description

None

Attributes

Log: no

State: active

Privilege: any

Related Commands

dspmfrbundlealm

Example

In the following example, the user displays the alarm status of all MFR bundles.
MM8850_SF.10.MPSM155[FR].a > dspmfrbundlealms
 Mfr     Admin    Oper     Alarm
Bundle   State    State    State
--------------------------------
     1      Up       Up    Clear
     2      Up       Up    Clear 
dspmfrbundlebucketcnt

Display Multi-link Frame Relay Interval Counters

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundlebucketcnt command to display interval statistics for an MFR bundle.

Syntax

dspmfrbundlebucketcnt <group> <intvl>

Syntax Description

group

Identifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

intvl

Statistics interval number, range 0-96

Attributes

Log: no

State: active

Privilege: any

Related Commands

dspmfrbucketcnt, dspmfrbundles

Example

In the following example, the user displays statistics for interval 1 on MFR bundle 2.
M8850_SF.10.MPSM155[FR].a > dspmfrbundlebucketcnt 2 1
  Bundle Number             : 2         
  Interval Number           : 1         
  Resequence Errors         : 0 
dspmfrbundlecnt

Display Multi-link Frame Relay Bundle Counters

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundlecnt command to display statistics for an MFR bundle.

Syntax

dspmfrbundlecnt <bundleNum>

Syntax Description

bundleNum

Identifies the MFR bundle number.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: no

State: active

Privilege: any

Related Commands

clrmfrbundlcnts, dspmfrbundles

Example

In the following example, the user displays the counters on MFR bundle 1.
M8850_SF.10.MPSM155[FR].a > dspmfrbundlecnt 1
  Bundle Number                    : 1
  Resequence Errors                : 0
dspmfrbundles

Display Multi-link Frame Relay Bundles

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrbundles command to display summary information for all MFR bundles.

Syntax

dspmfrbundles

Syntax Description

None

Attributes

Log: no

State: active

Privilege: any

Related Commands

addmfrbundle, cnfmfrbundle, delmfrbundle

Example

In the following example, the user displays all MFR bundles.
M8850_SF.10.MPSM155[FR].a > dspmfrbundles
 Mfr     Activation    Minimum    Configured  Active  Admin   Oper    Max Diff
Bundle     Class        Links        Links     Links  State   State      Delay
------------------------------------------------------------------------------
     1            A          1             4       4     Up      Up        300
     2            A          1             4       4     Up      Up        300
dspmfrlnk

Display a Multi-link Frame Relay Link

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnk command to display an MFR link.

Syntax

dspmfrlnk <link>

Syntax Description

link

Identifies the MFR link number to display.

Note Enter the dspmfrlnks command to display all MFR links on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrlnk, cnfmfrlnk, delmfrlnk, dspmfrlnks

Example

In the following example, the user displays MFR link 1.1:3.
M8850_SF.10.MPSM155[FR].a > dspmfrlnk 1.1:3
  Link Number                      : 1.1:3
  Bundle Number                    : 1
  Link State                       : Up
  Link Alarm State                 : Clear
  Link Delay (Rtt in msec)         : 21
  Link Near End Name               : M8850_SF.Slot10.Link03
  Link Far End Name                : M8850_SF.Slot10.Link31
  Link Far End Bundle Name         : M8850_SF.Slot10.Bundle02
  Link PHY Operational Status      : Up
dspmfrlnkalm

Displays Multi-link Frame Relay Link Alarm

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnkalm command to display alarm status of a link.

Syntax

dspmfrlnkalm <link>

Syntax Description

link

Identifies the MFR link number.

Note Enter the dspmfrlnks command to display all MFR links on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrlnk, cnfmfrlnk, dspmfrlnk

Example

In the following example, the user displays alarms on link 1.1:3.
M8850_SF.10.MPSM155[FR].a > dspmfrlnkalm 1.1:3
Link  Number           : 1.1:3
Bundle Number          : 1
Link State             : Up
Link Alarm State       : Clear
PHY Operational Status : Up
dspmfrlnkalms

Displays Multi-link Frame Relay Link Alarms

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnkalms command to display alarm status for all links associated with MFR bundles.

Syntax

dspmfrlnkalms

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

dspmfrlnkalm

Example

In the following example, the user displays link alarms.
M8850_SF.10.MPSM155[FR].a > dspmfrlnkalms
Link      Bundle    Link        Link Alarm   PHY Oper
Num        Num      State         State       State
--------------------------------------------------------------------
    1.1:3       1        Up         Clear          Up
    1.1:4       1        Up         Clear          Up
    1.1:5       1        Up         Clear          Up
    1.1:6       1        Up         Clear          Up
    1.2:3       2        Up         Clear          Up
    1.2:4       2        Up         Clear          Up
    1.2:5       2        Up         Clear          Up
    1.2:6       2        Up         Clear          Up
dspmfrlnkbucketcnt

Display Multi-link Frame Relay Interval Statistics

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnkbucketcnt command to display interval statistics for an MFR link.

Syntax

dspmfrlnkbucketcnt <link> <intvl>

Syntax Description

link

Identifies the MFR link number for which to display statistics.

Note Enter the dspmfrlnks command to display all MFR links on the card.

intvl

Statistics interval, range 0-96

Attributes

Log: no

State: active

Privilege: any

Related Commands

dspmfrlnkcnt, dspmfrlnks

Example

In the following example, the user displays statistics for interval 1 of link 1.1:3.
M8850_SF.10.MPSM155[FR].a > dspmfrlnkbucketcnt 1.1:3 1
  Link Number               : 1.1:3     
  Interval Number           : 1         
  Frames Control Tx         : 170            
  Frames Control Rx         : 170            
  Frames Control Invalid Rx : 0              
  Timer Expired Count       : 0              
  Loopback Suspected Count  : 0              
  Unexpected Sequence Count : 0              
  Mismatch Count            : 0 
dspmfrlnkcnt

Display Multi-link Frame Relay Link Statistics

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnkcnt command to display statistics for an MFR link.

Syntax

dspmfrlnkcnt <link>

Syntax Description

link

Identifies the MFR link number for which to display statistics.

Note Enter the dspmfrlnks command to display all MFR links on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

dspmfrlnkbucketcnt

Example

In the following example, the user displays statistics for link 1.1:3 in MFR bundle 1.
M8850_SF.10.MPSM155[FR].a > dspmfrlnkcnt 1.1:3
  Link Number                        : 1.1:3
  Bundle Number                      : 1
  Link State                         : Up
  Control Frames Tx on Link          : 10988
  Control Frames Rx on Link          : 10980
  Invalid Control Frames Rx on Link  : 0
  Timer Expired Count                : 8
  Loopback Suspected Count           : 0
  Delayed/Duplicated Frames          : 0
  Inconsistent Bundle Count          : 0 
dspmfrlnks

Display Multi-link Frame Relay Links

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the dspmfrlnks command to display summary information about all MFR links.

Syntax

dspmfrlnks

Syntax Description

None

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrlnk, delmfrlnk, cnfmfrlnk, dspmfrlnk

Example

In the following example, the user displays all MFR links on a bundle.
M8850_SF.10.MPSM155[FR].a > dspmfrlnks
     Link    Bundle      Link   Link Alarm       Link     PHY Oper
      Num       Num     State        State   Delay(ms)       State
------------------------------------------------------------------
    1.1:3         1        Up        Clear          21          Up
    1.1:4         1        Up        Clear          21          Up
    1.1:5         1        Up        Clear          20          Up
    1.1:6         1        Up        Clear          19          Up
    1.2:3         2        Up        Clear          21          Up
    1.2:4         2        Up        Clear          21          Up
    1.2:5         2        Up        Clear          20          Up
1.2:6 2 Up Clear 20 Up

upmfrbundle

Up a Multi-link Frame Relay Bundle

Service Context—Frame Relay

Modules—MPSM-T3E3-155

Enter the upmfrbundle command to change the administrative state of an MFR bundle to up.

Syntax

upmfrbundle <bundleNumber>

Syntax Description

bundleNumber

Specifies the MFR bundle number to activate.

Note Enter the dspmfrbundles command to display all MFR bundles on the card.

Attributes

Log: yes

State: active

Privilege: GROUP1

Related Commands

addmfrbundle, delmfrbundle

Example

In the following example, the user brings up bundle 1.
M8850_SF.10.MPSM155[FR].a > upmfrbundle 1
New Channel Loopback Commands

The following channel loopback commands are new in Release 5.0.20.

Table 20 MPSM-T3E3-155 Channel Loop Commands

Command

Description

addchanloop

Activates a channel loopback

delchanloop

Deactivates a channel loopback

dspchanloop

Display channels in loopback
addchanloop

Add Channel Loop
Service Context—ATM, Frame Relay

Modules—MPSM-T3E3-155, MPSM-16T1E1

Enter the addchanloop command to place a channel in loopback mode.

Syntax (ATM Context)

addchanloop <IfNum> <vpi> <vci> <loopback>

Syntax Description (ATM Context)

ifNum

Interface number (port number) of the channel to configure.

•MPSM-16-T1E1 range: 1-499

•MPSM-T3E3-155 range: 1-1003

Note Enter the dspcons command in the ATM CLI context to display the port number, VPI, and VCI for all active ATM channels.

vpi

VPI, in the range 0-4095

vci

VCI, in the range 32-65535

loopback

The desired loopback type:

•1=RemoteLoop (Ingress)

•2=LocalLoop (Egress)

Syntax (Frame Relay Context)

addchanloop <IfNum> <dlci>

Syntax Description (Frame Relay Context)

ifNum

Interface number (port number) of the channel to configure.

•MPSM-16-T1E1 range: 1-499

•MPSM-T3E3-155 range: 1-1003

Note Enter the dspcons command in the Frame Relay CLI context to display the port number and DLCI for all active Frame Relay ports.

dlci

Data-link connection identifier, in the range 1-1022 for a 2-byte header, or 1-8388607 for 4-byte header.

Related Commands

dspchanloop, delchanloop, dspcons

Attributes

Log: yes

State: active

Privilege: GROUP1

Example (ATM Service Context)

In the following example, the user activates a local loopback on port 12, VPI 35, VCI 120.
M8830_CH.12.MPSM155[ATM].a > addchanloop 12 35 120 2
Example (Frame Relay Service Context)

In the following example, the user activates a loopback on port 11, DLCI 150.
M8830_CH.12.MPSM155[FR].a > addchanloop 11 150
delchanloop

Delete Channel Loop

Service Context—ATM, Frame Relay

Modules—MPSM-T3E3-155, MPSM-16T1E1

Enter the delchanloop command to deactivate a channel loopback.

Syntax (ATM Context)

delchanloop <IfNum> <vpi> <vci>

Syntax Description (ATM Context)

ifNum

Interface number (port number) of the channel from which to remove a loopback.

Note Use the dspcons command in the ATM CLI context to display the port number, VPI, and VCI for all active ATM ports.

vpi

The channel VPI.

vci

The channel VCI.

Syntax (Frame Relay Context)

delchanloop <IfNum> <dlci>

Syntax Description (Frame Relay Context)

ifNum

Interface number (port number) of the channel from which to remove a loopback.

Note Use the dspcons command in the Frame Relay CLI context to display the port number and DLCI for all active Frame Relay ports.

dlci

The Data-link connection identifier.

Related Commands

dspchanloop, addchanloop, dspcons

Attributes

Log: yes

State: active

Privilege: GROUP1

Example (ATM Service Context)

In the following example, the user deactivates the loopback on interface 17, VPI 44 and VCI 55.
M8850_SF.10.MPSM155[ATM].a > delchanloop 17 44 55
Warning: Please clear the stats for this conn to get the updated counters !
Example (Frame Relay Service Context)

In the following example, the user deactivates the loopback on interface 3, DLCI 130.
M8850_SF.10.MPSM155[FR].a > delchanloop 3 130
Warning: Please clear the stats for this conn to get the updated counters !
dspchanloop

Display Channel Loop

Service Context—ATM, Frame Relay

Modules—MPSM-T3E3-155, MPSM-16T1E1

Enter the dspchanloop command to display channel loopback information.

Syntax (ATM or Frame Relay Context)

dspchanloop <IfNum>

Syntax Description (ATM or Frame Relay Context)

ifNum

Interface number (port number) of the channel to display.

Note Use the dspports command to display the port numbers for all active channels in the current CLI context.

Related Commands

addchanloop, delchanloop

Attributes

Log: yes

State: active

Privilege: GROUP1

Example

n the following example, the user displays loopback information for port 5.
M8850_SF.27.MPSM16T1E1[FR].a > dspchanloop 5
Loop Back Connections on Interface 5
     Conn LCN   ifNum         Dlci
       110       5          500
Changed Commands

The following commands changed in Release 5.0.20:

•addport—new -oversub option to enable or disable oversubscription for a new port

•cnfport—new -oversub option to enable or disable oversubscription for an existing port

•dspport— also displays activation and oversubscription status for a port

•dspchancnt— new statistics counters for Frame Relay

Removed Commands

No commands were removed from Release 5.0.20 code.

Commands Changed in Release 5.0.10

This section contains the commands that are changed in Release 5.0.10.

PXM45 Commands

This section lists commands that are new in, changed in, or removed from MGX Release 5.0.10 code for PXM45 cards. It also lists the privilege level and state in which the command can be used.

New Commands

The following commands are new in MGX Release 5.0.10:

•dspdiagresults ANYUSER A|S

•dspdiagtests ANYUSER A|S

•dsppostresults ANYUSER A|S

•show ANYUSER A|S|I

Changed Commands

This section lists commands that are changed in MGX Release 5.0.10 for PXM45 cards. Refer to the Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5 manual for details.

Commands with Access Level Changes

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

•dspDevErr ANYUSER A|S state (from A to A|S)

•dspDevErrHist ANYUSER A|S state (from A to A|S)

•dspHwAlms ANYUSER A|S state (from A to A|S)

Removed PXM45 Commands

No commands were removed from MGX 5.0.10 code.

PXM1E Commands

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

New Commands

The following command is new for PXM1E in MGX Release 5.0.10:

•show ANYUSER A|S|I

Changed Commands

No commands were changed in MGX Release 5.0.10 for PXM1E cards.

Commands with Access Level Changes

No access levels were changed in MGX 5.0.10 code.

Removed PXM1E Commands

No commands were removed from MGX 5.0.10 code.

AXSM and AXSM-E Commands

There were no new or changed commands for AXSM and AXSM-E cards in MGX Release 5.0.10.

Limitations, Restrictions, and Notes for 5.0.20

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

•Due to granularity limitations in the AXSME hardware, cell traffic does not reach the configured PCR rate when WFQ is enabled. You must configure connections that have WFQ enabled with a PCR of 101% of the actual required rate. ABR has the same Qbin priority as UBR in the SCT tables. In this case ABR and UBR share excess bandwidth if WFQ is enabled.

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

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

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

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

•The percentage trunk utilization with overbooking is calculated using the following formula:

overbooked MaxCR - overbooked ACR) / overbooked MaxCR. This will occur when inter-operating with SES from Release 3.0.x and higher.

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

–The overbooked ACR is calculated differently between MGX and SES.

–On MGX, the bandwidth for all current connections on the port are considered overbooked when calculating the trunk utilization.

–On the SES, the bandwidth for all current connections on the port are NOT considered overbooked when calculating the trunk utilization.

–Therefore, the trunk utilization calculation is lower on the MGX than on the SES when there are existing connections on the port with an overbooking factor configured. This in turn yields a lower percentage trunk utilization on the MGX compared to the SES.

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

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

AXSM-16-155-XG with MCC Back Cards

You might see the following scenario when the card to card APS is configured on one side but not the other side:

The Protection Line Status in dspapslns or dspapsln shows "OK" if the other side has added the card redundancy and upped the line but not the APS. If the backcards are SFP backcards, the Protection Line Status is in "SF" in the same setup.

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

For GR253:

Receive k2 chanfield - Null Channel

Receive k2 modefield - Undefined

After adding remote APS (with MCC):

Receive k2 chanfield - Null Channel

Receive k2 modefield - UNI1+1 or Bi depending on mode

For ITU (or AnnexA)

Receive k2 chanfield - Null Channel

Receive k2 modefield - Undefined

After adding remote APS:

Receive k2 chanfield - Null Channel

Receive k2 modefield - Undefined

For AnnexB:

Receive k2 chanfield - Null Channel

Receive k2 modefield - Undefined

After adding remote APS:

Receive k2 chanfield - Working Section 1 or 2

Receive k2 modefield - Undefined

Upgrading AXSM-XG Cards

The following notes apply to AXSM-XG card upgrades:

•When installing AXMS-XG cards into a node that has a release earlier than Release 4.0.15, all of the other cards in the node must be upgraded first to Release 5.0.

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

Upgrading the VISM-PR Image

If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.

Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.

MPSM Notes

See the following MPSM notes:

•Neither the MPSM-8-T1E1 card nor the MPSM-T3E3-155 card support the LMI Autosense feature that is supported for FRSM cards since Release 1.2.21.

•If a combination of RPM-PR and MPSM-T3E3-155 cards are being installed in slots covered by the same cell bus, then enable Option 10 of cnfndparms (auto clock rate setting) before installing the MPSM-T3E3-155 and RPM-PR cards. This note applies when two RPM-PR cards or two MPSM-T3E3-155 cards (or one RPM-PR and one MPSM-T3E3-155 card) are inserted into slots under the same cell bus master, for example, slots 5 and 6 or 3 and 4.

•The MPSM cards are cell bus based cards, and they have some limitations that make it seem that only a few of these cards could be used in a chassis when running at full port rate.

In reality, the full port rate available is rarely used. Statistical multiplexing of traffic across many ports can allow overbooking of the cell bus capacity just as it allows overbooking of trunk capacity. Estimates on how much overbooking is practical without dropping cells relies on the network's characteristics such as the mix of service types, port speeds, and offered traffic loads as a percentage of port speed or as generated cell rates. Work with your Cisco Customer Engineering representative to help you characterize the quantity of MSPM cards suitable for your network.

•If you order MPSM cards with systems, the MPSM license(s) will be shipped on the PXM card. For more information, refer to Appendix F of the Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5.

PXM1E Parity Errors

The following parity errors are

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

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

Upgrading to 5.0

The following notes apply to upgrading to Release 5.0:

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

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

Higher Level Logical Link Limits

The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is turned on. The limit is essential to reduce the processing time involved in finding the bypasses between the logical links. Whenever a significant change occurs in bandwidth in one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually found from one logical link to another.

If there are n logical links, the calculation involves the finding n*n bypasses. If the number of logical links n is large, a lot of processing time is used for calculating the bypasses. The number of logical links per level must be limited to 30. The number can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.

CLI Upgrade

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

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. When standby has 4.0 release firmware and active has pre 4.0 release firmware, the active is receiving 512 bytes, thus receiving the error message above.

Preferred Route

Preferred routes are not supported for connections with endpoints on RPM card types in Releases 4.0 and above.

Upgrading a preferred routing configured connection from any Release 3.0.x is non-graceful. During the upgrade, the preferred route identifier information for each connection is lost, and the preferred route identifier needs to be reprovisioned on the Service Module cards.

Also, the preferred route table at the PXM controller is lost. Connections that have already been routed with preferred routing remain, and no alarms for these connections occur. If a node in the PNNI network is removed via physical decommissioning and if any nodes in the network had some preferred routes that contained the removed node as one of the hops, the preferred route(s) must be deleted and modified manually.

When a connection is routed on a route other than its preferred route and if the preferred route becomes available, the connection is not automatically derouted to route back to its preferred route. You must deroute and reroute by using configuration commands (optrte, rrtcon, dncon/upcon, and so forth). QoS precedence over Preferred Route does not apply to MPG network (CSCdz40310).

A preferred route configured with a higher node ID cannot be blocked (CSCdz41145, CSCdz49001). Due to differences in physical port numbering, non-MGX nodes can only be the terminating nodes in a preferred route.

Preferred route status is supported, starting with MGX Release 5.0.00. This feature requires you to issue commands, such as cnfcon on each connection after an upgrade. This step is only needed once after the upgrade, and does not need to be repeated on subsequent upgrades.

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

The following notes apply:

•IMA version fall back is part of IMA group operation. If a group is configured with version 1.1 and it is connected to a far end group which is configured with version 1.0, this group falls back to version 1.0.

•The IMA link Loss of IMA Frame (LIF) and Link Out of Delay Synchronization (LODS) defect integration times are configurable.

•ATM layer configuration for line and IMA ports takes an additional parameter, AIS enable. It is enabled by default.

•In T1 mode, payload scrambling is disabled by default and in E1 mode it is enabled by default on all lines and IMA groups.

•Only 10 SVC calls per second is guaranteed.

•FDL support for Loopback code detection is not supported.

•Far End Line Performance counters are supported only for E1. They are not supported for the T1 interface.

•HMM support is not available for the IMA and the Framer devices. When a switchover occurs, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.

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

•IMA group cannot have links from upper and lower bays together.

•ITC clocking mode on IMA is not supported.

•One way transmission delay of more than 500 msec on the T1/E1 IMA links is not supported.

•There is 5 ms fluctuation on IMA delay tolerance.

•While the IMA group accumulated delay is being removed with clrimadelay, the following applies:

–Any changes to this IMA group configuration are temporarily blocked.

–Any changes in the FE IMA links in this group can cause the NE IMA group to restart.

•The VC and COSB thresholds are updated when the links are added/deleted from the IMA groups.

•The thresholds for the connections added when there are N links in the group can differ from connections added when there are (N+1) links in the IMA group.

•BERT is only supported on the T1 interfaces. BERT is not supported on E1 interfaces.

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

•PNNI requires SCR = 453 cells per second and PCR = 969 cells per second for the control connection.

•SSCOP requires of SCR = 126 cells per second and PCR = 2000 cells per second.

Cell Bus Service Modules (Formerly Known as Narrow Band Service Modules) and RPM-PR

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

•Conditions: switchredcd is run from PXM command line to perform CBSM Switchover. PXM switches over (manual or automatic) before the Service Module (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 might not be complete and the standby card is in an indeterminate state. The dspcd command from PXM still shows it as 'standby' and later switchver (due to active SM removal or reset) fails, causing loss of traffic. The switchredcd command also fails.

–The switchredcd from PXM again causes the failure since the standby SM is not able to allocate memory.

–Work round: Reset the standby Service Module card.

•CBSM feature is not available for PXM45/A.

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

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

IGX Feeder

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

Policing Accuracy for PXM1E

A limitation exists with the policing accuracy for the PXM1E. The policing rate is defined as 50000000/PCR. If the PCR is comparable to the OC-12 line rate (1412830), the policing rate parameter is a relative small number (50000000/1412830 = ~35.38996).

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. This format cannot represent a small number accurately. Combining the above two factors, a 100% accurate policing parameter cannot be configured.

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

Maximum Threshold Accuracy for PXM45 and PXM1E

A limitation exists with 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). Therefore, you cannot calculate an exact 100% correct discard rate.

To ensure that you get the rate that you have specified, the software configures Qbin depth at the next larger rate 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—MGX 8850 (PXM1E) and MGX 8830:

•Y-red is not supported on the MCC Electrical back card.

•For inter-card APS to work on the PXM1E-8-155, and one front card is missing or not available, both backcards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.

•MPLS controller is not supported on PXM1E.

•PXM1E clock source is supported by VISM-PR, CESM, and AUSM cell bus service module cards. CESM and AUSM can provide one clock source, either primary or secondary.

•Only SPVCs and SPVPs are supported on cell bus service modules. SVCs are not supported on CBSMs.

•No bandwidth CACing support exists on the cell bus service modules, except for the RPM card, which is checked against the OC-3 card rate. For example, for a given RPM, the bandwidth allocated to all connections might not exceed the OC-3 rate. Bandwidth CACing is supported on the PXM1E uplink port.

•The maximum bandwidth to be distributed among cell bus service modules is approximately an OC-10 rate while traffic on the network interfaces on PXM1E can achieve true OC-12 line rate.

•Traffic must be balanced between the cell bus controllers to achieve the OC-10 rate. The traffic must be distributed equally at a rate of about OC-5 on the two cell bus controllers.

The cell bus controllers cannot load share to achieve OC-10 with one cell bus set at an OC-6 rate, and another cell bus set at an OC-4 rate.

Anything above OC-6 is dropped. However, if only one cell bus controller is used and the other cell bus controller is not used, then it can achieve an OC-10 rate. On an MGX 8850, the CBCs are split between the left and right side of the chassis: CBC0 supports slots 1-6 and 17-22 and CBC1 supports slots 9-14 and 25-30. On an MGX 8830, CBC0 supports slots 3,5,10, and 12 and CBC1 supports slots 4,6,11, and 13. Balance is achieved by planning the distribution of your cell base card by evenly distributing from the left side of the chassis and the right side of the chassis.

PXM1E Hardware Limitations

PXM1E hardware limitations are as follows:

•For inter-card APS to work on the PXM1E-8-155 with one front card missing or unavailable, both back cards must be present. A front card cannot drive the alternate trunk back card when its own local trunk back card is absent.

•During hardware upgrade from PXM1E-4-155 to PXM1E-8-155, at the time when the inserted card types are different (one PXM1E-4-155 card set and one PXM1E- 8-155 card set), the standby trunk back card functionality is not available. Therefore, LED functionality is not available, and APS lines do not work on that backcard.No modular optical transceiver (SFP-8-155) mismatches are reported for that backcard. No SFP-8-155 mismatches are 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 a 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 is not graceful and becomes service affecting, until appropriate cables are setup.

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

•MGX-8850-APS-CON limitation is

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. It is recommended that one be inserted to support graceful upgrade to PXM1E-8-155 cards in the future. Since the PXM1E-8-155 card requires a mini-backplane, if one is not already present when upgrading from PXM1E-4-155 to PXM1E-8-155, the upgrade cannot be graceful.

Reserved VCIs

You cannot provision the following reserved VCIs:

•On a feeder trunk, VPI.VCI 3.8 is reserved for inband communication with the feeder shelf, and 3.31 is used for the feeder trunk Annex.G ILMI.

•VPI = 0 and VCI = 5 are used for SSCOP for UNI signaling ports.If the port is configured for non signaling (univer = none), no VPI/VCI is reserved.

•VUNI uses configured VPI and VCI = 5 for SSCOP.

•EVUNI uses minimum VPI and VCI = 5 for SSCOP.

•NNI uses VPI = 0, VCI = 18 for PNNI RCC.

•VNNI uses configured VPI for the port and the VCI = 18 for PNNI RCC.

•EVNNI uses minimum VPI and the VCI = 18 for PNNI RCC.

•VPI = 0 and VCI = 16 are used for ILMI if ILMI is enabled. VUNI and VNNI uses configured VPI for the port and VCI = 16 for ILMI. Similarly, ILMI for EVNNI or EVUNI uses a minimum VPI and VCI = 16.

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

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

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

AXSM-E OAM

The following notes apply to AXSM-E OAM cells:

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

•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 cells are dropped. This limitation applies for all the connections on a card.

For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and 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. The additional 500 connections are not received 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 might be parsed and be added to the binary file. However, this invalid name is ignored later.

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

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

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 the error. 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 (for example, AXSM, AXSM/B, AXSM-E,) and all communication with the standby controller card and the Cell Bus Based Service Modules (for example, FRSM, CESM). These procedures cannot 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.

•The isolation procedures isolates 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.

•At least two cards (two service modules or one service module and one standby PXM) must exist 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, do not initiate the isolation procedures. This 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.

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

•If no controller card redundancy is available, isolating the cell bus path failure to active controller card results in outage. The active controller card is reset.

Disk Space Maintenance

Because the firmware does not audit the disk space usage and remove unused files, the disk space in C: and E: drives must be manually monitored.

Manually delete any unused saved configuration files, core files and firmware files and the configuration files of the MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards to avoid a shortage of disk space required to store event logs: configuration upload files in the C: drive and the configuration of MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards in the E: drive.

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

Step 1 Change to the directory that needs grooming.
CLI cc <directory_name> 
Step 2 List the directory to identify old files that can be removed and available disk space.
CLI ll 
Step 3 Remove any old files (you may also use wild cards in the filename).
CLI rm <complete_filename> 
Step 4 List the directory to see if the file has been removed and disk space is available.
CLI ll 
Non-native Controller Front Card and PXM-HD Card

The following notes pertain to non-native front card controllers and the PXM-HD card:

•When the front controller cards or the PXM-HD back cards are swapped within the same system, the system performs a non-native card check. As a result, the controller card that attempts to come up as Active/Active might get reset twice.

•When a non-native PXM1E front card or a PXM-HD card is inserted into the standby controller slot, after the standby controller front card becomes Active/Standby, the active controller front card copies its hard disk content over to the standby controller card. The active controller front card does not perform any automatic hard disk content removal from the active or standby controller card.

•The system keeps only the two most recent copy of the saved system configuration under the C:/CNF directory. You can use ftp protocol to ftp all the saved configuration under C:/CNF to their local server for future reference. All files under C:/CNF are not replicated over to the standby controller card under any circumstances.

clrsmcnf Command

These notes pertain to the clrsmcnf command:

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

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

•For the clear service module configuration feature, using the clrsmcnf command might result in discrepancy in the PNNI configuration. For example, some connections might 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 goes into the boot/empty state after the operation is complete.

•If the clrsmcnf command is given with the <all> option, for cell bus service module, the card goes into boot/empty state. For a broadband service module (for example, AXSM or MPSM-155-T3E3), the card goes into fail/active state.

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

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

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

•Port LED lights on AXSM-E, AXSM-XG and PXM1E front cards indicate the receive status of physical line connected to it only when the card is in active state. For a standby AXSM-E, AXSM-XG, and PXM1E cards, the LEDs always remain green whether the lines are in LOS irrespective of which lines are Active (refer to anomaly CSCdv68576).

Path and Connection Trace

These notes pertain to the path and connection trace features:

•Path trace is not supported on the control port.

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

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

•Path and connection trace support point to point connections.

•Path and connection trace support MPG (multi-peer group) and SPG (single-peer group).

Simple Network Timing Protocol (SNTP)

The CWM MIB is not supported in the release.

Priority Routing

These notes pertain to the priority routing feature:

Prioritized reroute of SPVCs is not guaranteed if the SPVCs originate on a signaling port. SPVCs might 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 are assigned a routing priority of 8 by the PXM.

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

•Changing the routing priority for dax connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if just the endpoint 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 the rrtcon command is not supported for dax connections, the routing priority change never gets reflected. The only way for this to get reflected is to do a dncon and upcon. Since 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 releases can be expected to be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the interfaces because it is congested. The calls that were not released could be higher priority calls.

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

SPVC Interop

These notes pertain to SPVC interoperability:

•NNI SPVC Addendum Version 1.0 is not supported.

•PNNI 1.0 Addendum (Soft PVC MIB) is not supported.

•Terminating single-ended SPVCs on MGX switch with 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 is not available at the slave end of a single-ended SPVC.

•tstdelay is not 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 is not visible to CWM.

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

•Single-end provisioning is not supported for DAX connections as no value addition is seen for interoperability.

•SPVC statistics are not available for the slave endpoint of a single-ended SPVC because this endpoint is non-persistent.

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

•Override of SVC connections on a VPI 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 are shown for a pre-Release 4.0.00 node in the Topo DB. This is because the feature is not present in pre-Release 4.0.00 nodes.

•If a peer group is made up of physical nodes with pre-Release 4.0.00 logical nodes, the information for the logical node is stored in the Topo DB. This is because there is no way to distinguish between physical nodes and pre-Release 4.0.00 logical nodes. Logical nodes with Release 4.0.00 or later software release are not stored in the Topo DB.

•To delete a node information entry from the Topo DB, first remove the node from the network, either by disconnecting the cables or by downing all the links between that node and the network. Wait for an hour. Then, delete that node from the Topo DB. This is done because, even if a node is removed from the Topo DB of all nodes in the peer group, its PTSEs are still stored in the other nodes until they are flushed from those nodes. This would happen within an hour's time, but it is configurable as a PNNI timer value. If the node is deleted from the Topo DB within that hour's time, and the node does switchcc/reboot, then it's possible that the node info for that deleted node will be added back into the topo db.

•When the node ID of a node is changed, the old node ID is added back into the Topo DB as a new node entry. In addition, the old node ID still is stored in the Topo DB of all the other nodes in the peer group. To delete this entry, wait for an hour so that the PTSEs with the old node ID is flushed from the DB of all the nodes in the peer group. Then, delete the information of the old node ID from the Topo DB.

•It is possible that the gateway nodes are not in sync in a peer group, and this could happen in many situations. For example, a gateway node is added in a peer group, then a node is deleted from the PG, and another gateway node is configured, then the info for the deleted node would not be in the second gateway node. Another example is that a node is deleted from one gateway node, but not in another gateway node.

•When deleting a node from the peer group, the node info must be deleted from all the nodes in that 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 provides negative acknowledgement. Attempts to configure the second clock will fail silently.

•No clock sources are supported on FRSM. If a clock source is configured on FRSM, it will not be reflected in the database.

•When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. However, the clock to which the node is latched is not requalified. Only the backup clock is qualified if present. Recommitted means that the primary and secondary get requalified, and the node temporarily latches onto the internal oscillator. After the clock is requalified, the node locks 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 are dropped. This condition only occurs when ER stamping is enabled and CI is disabled on an AXSM PNNI link with CBR/ABR traffic running to cause congestion on the link.

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

AXSM-XG Hardware Limitation

The IR/LR/XLR SFP modules need a 10 db attenuator when connected with short cables. Otherwise the specification for receiver sensitivity on the receiver is exceeded.

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:

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

Priority Bumping

When you enable priority bumping on the node, you cannot change the booking factor for AXSM signaling ports. You can change the booking factor for non-signaling ports.

Other Limitations and Restrictions

Other limitations and restrictions are as follows:

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

•If command clrchancnt is executed while a dspchancnt command is currently active, the data displayed is incorrect. Restarting the dspchancnt after the previous one has completed displays correct data.

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

•The clrsmcnf does not work if an upgrade is in progress.

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

•Configuration information is not synchronized between PXMs during upgrades. If any changes are made to the configuration during upgrades, the standby PXM must be rebooted. The standby PXM must be rebooted when it is in a stable state.

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

•NCDP is not supported on BPX.

•CSCdz33652: When you clear the chancnt while you are monitoring the chancnt, the counters return invalid values on the dspchancnt display (AXSM-XG).

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

These notes apply to redundant cards.

•Due to checks to prevent an inserted card from affecting the system, an additional step might be required when inserting two non native PXM45 (or PXM1E) cards in a shelf. Insert the first PXM45, use the clrallcnf command, and allow this to become active before inserting the second PXM45 (or PXM1E).

•After a clrallcnf, explicitly clean up stale SCT files (see anomaly CSCdw80282).

Troubleshooting APS Lines

Port light behavior changed in Release 3.0.00.

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

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

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.

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

•APS connector is installed properly at both ends of the line (dspapsbkplane).

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

Upgrade Information

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

•Graceful PXM1E Boot Upgrades from Release 3.0.10 or higher

•Non-Graceful PXM1E Boot Upgrades

•Graceful PXM1E Runtime Software Upgrades

•Non-Graceful PXM1E Runtime Software Upgrades

•Graceful PXM45 and AXSM Runtime Software Upgrades

•Non-Graceful PXM45 and AXSM Runtime Software Upgrades

•Graceful AXSM Boot Upgrades

•Non-Graceful AXSM Boot Upgrades

•Graceful Service Module Boot Upgrades

•Non-Graceful Service Module Boot Upgrades

•Graceful Service Module Runtime Software Upgrades

•Non-Graceful Service Module Runtime Software Upgrades

•Graceful RPM-PR Boot Software Upgrades

•Graceful RPM-PR Runtime Software Upgrades

•Non-Graceful RPM-PR Boot Software Upgrades

•Non-Graceful RPM-PR Runtime Software Upgrades

•Installing SCT Files

Maintenance Information

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

•Replacing PXM1E-4-155 cards and with PXM1E-8-155 Cards

•Replacing PXM45/A or PXM45/B Cards with PXM45/C Cards.

Anomalies

This section provides information about anomalies.

MGX 8850, MGX 8830, and MGX 8950 5.0.20 Anomalies

Anomalies are organized as follows:

•Known Anomalies in Release 5.0.20

•Resolved Anomalies in Release 5.0.20

•Anomalies Status Change in Release 5.0.20

Known Anomalies in Release 5.0.20

Table 23 lists the known anomalies in Release 5.0.20 as of March 7, 2005.

Table 23 Known Anomalies in Release 5.0.20

Bug ID

Description

CSCec30621

Headline: Several OIDs in cwRsrcPartConfEntry return incorrect values

Symptom: When querying specific OIDs via SNMP, unexpected values returned. Problem is with these OIDs:

•cwRsrcPartEgrPctBwUsed .1.3.6.1.4.1.9.9.125.1.1.1.1.7

•cwRsrcPartIngPctBwUsed .1.3.6.1.4.1.9.9.125.1.1.1.1.8

•cwRsrcPartEgrPctBwAvail .1.3.6.1.4.1.9.9.125.1.1.1.1.9

•cwRsrcPartEgrPctBwAvail .1.3.6.1.4.1.9.9.125.1.1.1.1.10

Conditions: This problem is not configuration dependent.

Workaround: None.

Further Problem Description: The value returned is not the percentage of bandwidth as the MIB describes. The value actually returned is the allocated number of cells.

Hardware: AXSM1

CSCee10294

Headline: VSI error messages - conn ID add/delete problems

Symptom: VSI major errors reported in event log

10S62829 03/23/2004-15:08:59 VSI_-4-RMLCNREDError tVsiSlave VrmModStdbyDelList4 AddC [ERROR 0xE509 602] Deleted list is empty.: 0, 0, 0, 0, 0

Conditions: Connections on card were being modified for % util

Workaround: When this following error message is seen on standby, please reset the standby which brings up the standby card to a clean state.

10S62829 03/23/2004-15:08:59 VSI_-4-RMLCNREDError tVsiSlave VrmModStdbyDelList4

AddC [ERROR 0xE509 602] Deleted list is empty.: 0, 0, 0, 0, 0

Hardware: axsm1b_oc3

CSCee63184

Headline: snmpwalk on resource partition table is failing

Symptom: SNMP walk fails.

Conditions: While walking on the resource partition table.

Workaround: None.

Hardware: pxm1e

CSCee89724

Headline: SM bkup boot flash burning improvement

Symptom: MGX SMs and PXM does not response to active pxm polling during burning boot. The card types include: AXSM/a/b, AXSM-E, AXSM-XG, MPSM 8 T1E1, and MPSM-OC3, PXM45, and pxm1e.

Conditions: Burnboot was being executed on the card.

Workaround: None.

Hardware: all

CSCee91236

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

Symptom: cnfatmlayer command on MPSM-155 with 3xT3 backcard has no ds1 option.

Condition: cnfatmlayer command is used.

Workaround: None.

Hardware: MPSM-155

CSCee92300

Headline: Help message refers to obsolete/eng CLIs

Symptom: Obsolete/eng CLIs are referred in the help message.

Conditions: Switchcc is executed when standby crossbar is degraded for any reason.

Workaround: None.

Hardware: pxm45b

CSCef15971

Headline: dspatmlayercnt cmd incorrectly counts errd OAM cells as valid

Symptom: dspatmlayercnt command on MPSM-OC3 incorrectly counts errored OAM cells as valid.

Condition: Errored OAM cells were generated by setting CRC-10 to the wrong value.

Workaround: None.

Hardware: MPSM-155

CSCef16682

Headline: dspatmlayercnt command incorrectly counts PTI = 7 cells

Symptom: dspatmlayercnt incorrectly counts PTI = 7 cells.

Condition: dspatmlayercnt command is used to monitor cells being generated with invalid PTI cells.

Workaround: None.

Hardware: MPSM-155

CSCef21961

Headline: tTnCmdTsk01 hogs CPU on PXM45/B in sysBramEvtLogPrint()

Symptom: none telnet responses on PXM45 due to a CPU usage by tTnCmdTsk01.

Conditions: None.

Workaround: None.

Hardware: PXM45/B

CSCef30937

Headline: MPSM was failed after PXM switchcc stress testing

Symptom: MPSM was failed after PXM switchcc stress testing

Conditions: None.

Workaround: None.

Hardware: pxm45b

CSCef48747

Headline: REG5.1: WatchDog timeout core dump found on PXM1E card

Symptom: Watchdog coredump after resetsys/restoreallcnf

Conditions: Resetsys/restoreallcnf

Workaround: None

Hardware: pxm45b

CSCef55251

Headline: mpsm card stay in failed state after setrev

Symptom: MPSM-OC3 and MPSM-8T1E1 go to failed state

Conditions: When the cards are on the same cell bus master (eg: slots 1&2, 3&4 etc) and the cards are being brought up simultaneously.

Workaround: Reset MPSM-OC3 first and then keep resetting MPSM-8T1E1 until MPSM-OC3 comes back up as Active.

Hardware: mpsm-155

CSCef56354

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

Symptom: P2MP (point to multipoint) SVC loosing traffic in a via node. The SVC is built properly from the root uni port to terminating leaf ports. The traffic does not reach the terminating leaf nodes as it is being dropped in the AXSM/B card in the via node in between.

Conditions: PXM45B based MGX 8850 running 5.0(0.201). AXSM in question is AXSM_16T3E3_B.

Workaround: None

Hardware: axsm1

CSCef58958

Headline: Telnet sessions are not being released gracefully

Symptom: Unable to telnet to MGX 8850. Session shows Err: no resource for new session

Conditions: Multiple logins in a short period of time

Workaround: Active PXM can be reset by running specific commands from the standby PXM

Hardware: pxm45B

CSCef64820

Headline: Mfg Diag only shows warning if master clock is not locked

Symptom: Performing "initall" in the offline diagnostics does not fail the test. It only displays some warning message.

Conditions: PXM45 in the standby slot is present but not initialized. Or the clock on this standby PXM is not present or way out of tolerance.

Workaround: None

Hardware: pxm45c

CSCef67225

Headline: update CISCO-WAN-FR-CONN-MIB frNIW frNIWReplace for MPSM

Symptom: update CISCO-WAN-FR-CONN-MIB frNIW and frNIWReplace for MPSM

Conditions: using MIBs with 15.0.00-P2K in conjunction with MPSM 5.0.10

Workaround: None

Hardware: mpsm-oc3

CSCef69457

Headline: accesslevel implementation for inTask commands

Symptom: Any session control commands (ccc, sesntimeout, sesnwatchdog, showsyserr, syserr, timeout, sh, telnet, ssh...) that has its privilege level changes was still executable by login user with lower privilege level.

Conditions: Telnet for example is one of those commands should not been allowed by the user with lesser access level privileges. This would not be an issue if TACACS+ Command Authorization were used.

Workaround: TACACS+ Command Authorization mode can be used as the work around.

Hardware: pxm45B

CSCef71163

Headline: MFRDT:MPSM8T1 all CLI rejected with wrong parsing & timeout on CC.

Symptom: All CLI rejected with wrong parsing & timeout on CC.

Conditions: Using copychans to recreate this issue.

Workaround: Start a new Telnet session. CC to the card and then execute the cli.

Hardware: mpsm-8t1e1

CSCef87875

Headline: Standby PXM45B reset during VISM upgrade

Symptom: Standby PXM45B card reset and dumped core during VISM upgrade

Conditions: VISM boot code and firmware were being upgraded

Workaround: None

Hardware: pxm45b

CSCeg10557

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

Symptom: PXM1E shellconn command on the active PXM1E dspNovram "srmfc" <standby slot#> always returns the data for the active SRM slot.

Conditions: MGX1E shelf populated with PXM1E running 4.0(11.203)

Workaround: None

Hardware: pxm1e

CSCeg10810

Headline: frtt on MPSM FR should be in microseconds

Symptom: Inconsistent units and conversion for frtt on MPSM FR conns

Conditions: MPSM-155 FR image

Workaround: None

Hardware: mpsm-155

CSCeg18559

Headline: resetcd on RPMXF created tRMM exception and PXM45 switchover.

Symptoms: PXM45B switchover when resetcd was executed on RPM-XF card

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

Workaround: None

Hardware: pxm45b

CSCeg29002

Headline: stuck with free running clock on pxm1e

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

Conditions: Rare occurrence on PXM1e when primary clock flaps. Seen on MGX 4.0, but can happen on other releases.

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

Hardware: pxm1e

CSCeg36583

Headline: MFRDT:WIN7289 bus monitor error during MFR/IMA configuration

Symptom: Active card reset and failed to come up as standby due to RAM sync fails

Conditions: Multiple MFR bundles up and operational, delete the MFR links on local end, add IMA group with the same links used by MFR bundles, then delete MFR links on far end.

Workaround: None

Hardware: mpsm-155

CSCeg36788

Headline: Active mpsm8t1e1 comes up to standby after power cycle

Symptom: Non-redundant MPSM8T1 is stuck in Standby state

Conditions: After multiple power cycles and switchccs

Workaround: None

Hardware: pxm1e

CSCeg37735

Headline: CutW tasks can cause high CPU util. result false alarm generation.

Symptom: Customer reported CPU Peak Utilization alarms from OK to LOW and then back from LOW to OK in a few minutes.

Conditions: These were observed when cutWTasks create config upload files during CWM synchup. But at the same time it is creating this "false" alarm by resource monitoring.

Workaround: None.

Hardware: pxm45b

CSCeg38370

Headline: SNMP Timeout for Topology MIB when the node is reachable

Symptom: Trunk is unreachable in CWM

Conditions: Trunk is unreachable in CWM

Workaround: None

Hardware: pxm45c

CSCeg40352

Headline: Link Persistency OIDs return incorrect values

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

Conditions: PXM45-based MGX running 3.0(20) or 5.0(10.200) configured with PNNI links to another PXM45-based MGX running 3.0(20) or 5.0(10.200) and a soft loopback added (local or remote) to the PN port of a PNNI link (AXSM line cards). CWM 15.0 Patch 2.

Workaround: None.

Hardware: axsm1b_oc3

CSCeg41300

Headline: MGX 8850 caviIngRcvClp0Cells counter is not incrementing.

Symptom: The caviIngRcvClp0Cells and caviEgrXmtClp0Cells counters from the CISCO-ATM-VIRTUAL-IF-MIB are not counting correctly. The caviIngRcvClp0Cells counter are not counting ingress received Clp0 Cells. The value is always 0. The caviEgrXmtClp0Cells counter is incrementing, but the value is always the same as caviIngXmtClp0Cells although the counters are different on the cli.

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

Workaround: Collect the counters from a dspportcnt on the cli.

Hardware: pxm1e

CSCeg43495

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

Symptom: Card stays in Empty state after resetsys

Conditions: When core for reset from PXM is enabled

Workaround: Execute 'resetcd'

Hardware: all MPSMs

CSCin86268

Headline: DDLW-4-FR_WP_ERR (ddlwp_frIngrChanFlowDel) error log after resetsys.

Symptom: DDLW-4-FR_WP_ERR (tVsiSlave ddlwp_frIngrChanFlowDel) error log (corresponding to fully loaded MPSM155 slot) was observed after resetsys on 8830 PXM1E node. A few "switchcc" were executed some time before that.

Conditions: 8830 PXM1E Node resetsys with fully loaded MPSM155.

Workaround: None

Resolved Anomalies in Release 5.0.20

Table 24 lists the anomalies that are resolved in Version .205 of Release 5.0.20.

Table 24 Resolved Anomalies in Version .205 of Release 5.0.20

Identifier

Headline

CSCir01835

Offline Diag fails for PXM45C H2 boards.

CSCek42173

For SCT 5&6, ingress cells on OC3 port for PXM1E are flagged invaild.

CSCin99532

Node lost inband connectivity with mbuf allocation failed log

Table 25 lists the anomalies that are resolved in MPSM-T3E3-155 version .202 and AXSM-XG version .204 of Release 5.0.20.

Table 25 Resolved Anomalies in MPSM-T3E3-155 and AXSM-XG

Bug ID

Description

CSCei35633

Paths fail after switchredcd is issued on MPSM-T3E3-155.

CSCej15496

AXSM-XG OC3 FRUs not detected consistently.

CSCej32681

Alarms seen on BXM when configured for APS if remote end switches cards.

Table 26 lists the anomalies that are resolved in PXM45/PXM1E and AXSM-XG version .203, and AXSM/B and MPSM-T3E3-155 version .201 of Release 5.0.20.

Table 26 Resolved Anomalies in PXM45/PXM1E, AXSM/B, AXSM-XG, and MPSM-T3E3-155

Bug ID

Description

CSCei59862

ILMI goes down when traffic is stopped.

CSCei65805

Configurable ABR policer to enable tagging of MCR violation.

CSCei67407

RPM-XF addred is blocked when RCON is present.

CSCei82475

CLP 0 discards on ABR connections when intvsvd is enabled.

Table 27 lists the anomalies that are resolved in PXM45/PXM1E, AXSM-XG, and MPSM-8-T1E1 version .202 of Release 5.0.20.

Table 27 Resolved Anomalies in PXM45/PXM1E, AXSM-XG, and MPSM-8-T1E1

Bug ID

Description

CSCec04754

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

CSCec48191

WatchDog timeout core dump caused by Sar Queue Full

CSCeg25173

The MPLS-8-T1E1dumps the core after reset

CSCeg62909

Boot image corrupted during burnboot process

CSCeg68790

dsprcon cli command missing73-level PN and VID

CSCeg76224

Support for SFP detection

CSCeg88649

ABR configuration lost after stby reset

CSCeh14484

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

CSCeh15349

clrchancnt after stopping traffic does not show traffic cleared

CSCeh15410

WFQ cannot be disabled on ABR connections

CSCeh16336

WFQ cannot be enabled on CBR/VBR connections

CSCeh19705

AXSM-XG NNI end points do not generate AIS when UNI end point is removed.

CSCeh21259

addcon -intvsvd off is rejected on the first try with ABR WFQ disable port

CSCeh21549

ABR VC Queue shaper is enabled even after WFQ is disabled in SCT file

CSCeh23987

The dspsct command on the AXSM-XG should not show the VC WFQ_ENB field

Table 28 lists the anomalies that are resolved in version .200 of Release 5.0.20.

Table 28 Resolved Anomalies in Release 5.0.20

Bug ID

Description

CSCec12381

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

CSCec81892

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

CSCed21480

Update diagnostic code for AXSM2P and AXSM4P

CSCed55564

mainproc 2 holding pnni_get_buffer

CSCee30100

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

CSCee53753

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

CSCee56603

Incorrect error message for partition overlap on AXSM cards

CSCee61427

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

CSCee63073

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

CSCee66689

enable the winpath trace buffers

CSCee70227

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

CSCee70333

cdsCCV24HrThreshold mib returns out of range value of -1

CSCee70489

MPSM155 Diag Development/Enhancement

CSCee76355

incorrect error msg while trying to configure invalid link

CSCee77715

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

CSCee79587

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

CSCee85483

MFREIT: Unable to restart the MFR bundle through CLI

CSCee87948

MFREIT: MFR bundle admin stays in down after upmfrbundle

CSCee88501

ilmi errors in the log for mpsm

CSCee88716

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

CSCee89478

MFREIT: Incorrect link alarm detection while line in loop back

CSCee90076

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

CSCee90129

tracking: inconsistency issues between SM and CWM

CSCee90160

LMI task reports header or IE invalid on MFR port

CSCee91535

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

CSCee92813

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

CSCee94539

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

CSCee96562

MFREIT: ddlwp_htTermConnDel fails with WP_ERR_CH_NOT_DISABLE

CSCef00558

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

CSCef02725

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

CSCef06072

MPSM155: WP_ERR_RATE_OUT_OF_RANGE error is seen in the logs

CSCef07410

SNMP subsystem call to soiRpmPortOpen() failed

CSCef08020

OAMLP clrsmcnf caused AXSMB-OC3 to go to DOWN state

CSCef09520

WIN6041: STL configuration Patch Questions

CSCef10520

WIN6099: WP_ERR_WMM_FIFO_GET after several hours (WP_HostSend)

CSCef10909

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

CSCef13112

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

CSCef13143

AXSMXG OAM API could cause mem free fail when sending message fail

CSCef16101

MFRDT: Dspportcnt intermittently shows huge counts in FECN/BECN

CSCef21354

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

CSCef22408

Unclear Err Message for movelic on MPSM card with no licenses

CSCef23594

Incorrect redundant mpsm-8t1e1 card config info upload

CSCef23717

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

CSCef24248

changes to handle the frsm getting stuck in failed state

CSCef24978

event log flooded with FIPC-5-RSLVTIMEOUTWARN

CSCef26833

xg rebooted after upilmi on vnni trunk

CSCef27984

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

CSCef28059

MPSM dnport causes card reset when port sct missing

CSCef28074

PHPI communication failure on MPSM after switchcc

CSCef28123

ABR has the same excessive priority as UBR

CSCef28907

Exception happens when execute addmfrlnk and addlnloop

CSCef29270

Nonpersistent ABR generate RM and stay 10CPS for some time

CSCef29523

MFRDT: need clarifying the rejecting err message of cnfmfrbundle

CSCef29565

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

CSCef30195

MFRDT: Some CLIs becomes unavailable after ccc to mpsm cards

CSCef30612

MFRDT: dspmfrlnkbucketcnt being logged in log file

CSCef30862

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

CSCef32074

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

CSCef32137

MPSM DS3 lines stuck in minor alarm

CSCef32181

xg ports in autoconfig for 30 min, after upgrade

CSCef32258

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

CSCef32323

Units definition and display correction for dspportsct cosThr

CSCef35008

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

CSCef35674

FECN is mapped to EFCI when setEFCIzero and NIW

CSCef35946

MFRDT: Unable to enable lmiSig while adding mfr port

CSCef35972

POOL Tbl ERROR on screen after switchcc

CSCef36378

WIN6313: OAM generated from IMA port has wrong CRC10

CSCef36403

MFRDT: Cnfpath with Local/Remote loopback is blocked

CSCef36994

MFRDT:WP_ERR_WRR_WEIGHT_MUST_BE_GREATER_THAN_OR_EQUAL_TO_ONE,CardFail

CSCef37040

Minor version change may fail SCT version check in AXSMXG cards

CSCef37113

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

CSCef37354

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

CSCef37470

setDEone on SIW connection still map CLP

CSCef38377

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

CSCef38389

CH_NOT_DISABLE error when cnfport (FR) change -rat

CSCef38628

MFRDT: Bundle is UP without Mfrlnks configured

CSCef39574

AXSME: snmp walk causes emRoot task to run away

CSCef40134

231 level WDDI patches for 1.3.x branch

CSCef42054

Active PXM45 switched causing a core file

CSCef42656

link delay time is not accurate.

CSCef42867

LMI task reports invalid frame length for Status Enquiry

CSCef43327

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

CSCef44587

EPD sometimes programmed to EPD0 sometimes to EPD1

CSCef45861

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

CSCef45874

dspmfrlnkalm needs to show detail alarm reasons instead of multp

CSCef47208

Need fast DRAM test for axsm boards

CSCef47271

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

CSCef47362

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

CSCef47503

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

CSCef49515

MFRDT: Unable to bundle T1 links when channelization scheme different

CSCef49845

MFRDT:WP_ERR_INVALID invalid error code 0x31C while delmfrbundle

CSCef49927

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

CSCef50757

Memory Leak after Repeatedly Downing Then Upping PNNI

CSCef51130

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

CSCef51277

mfr port operState may get stuck in false alarm state

CSCef52092

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

CSCef52237

cnfport -rat failed in FR 2+1 byte mode

CSCef52302

SNMPSA exception due to NULL pointer access

CSCef52440

MFRDT: Unable to updates shelf database while cnfmfrlnk

CSCef53988

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

CSCef54121

need to checkin latest wddi patch

CSCef54454

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

CSCef56652

MFRDT: WIN6613 WP_MfrScanAssemblyTimeout returns HST_CMD_FAILED

CSCef56670

MFRDT: Wrong ifType in MFR trap 60633

CSCef56775

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

CSCef57382

PXM45C-8830: pnports stuck in Auto Config state

CSCef58663

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

CSCef59739

MFRDT: LOW static MEM alarm on all MPSM155 cards

CSCef60012

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

CSCef60710

MFRDT: Inconsistent link state when link has yellow alarm

CSCef60716

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

CSCef62624

Unsupported OIDs need to be undefed on MPSM cards

CSCef63405

MFRDT: lmiRootTask suspended cause card reset 3 times WIN6653

CSCef63431

MFRDT: VsiSlave Task suspended during connection deletion WIN6592

CSCef63750

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

CSCef63757

MPSM FM conn parms from upload trap 60641 are incorrect

CSCef65048

MFR port addition is rejected: DDLWP error

CSCef65206

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

CSCef65717

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

CSCef65817

ATM ABR with intvsvd does not slow down during congestion

CSCef66103

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

CSCef66104

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

CSCef67114

SMFIR SFP in MPSM-T3E3-155 displayed as SMFSR

CSCef67652

dspatmlayercnt always reports 0 for STS3c Channelized DS1 paths.

CSCef67722

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

CSCef68330

Local ACR on AXSME unable to exceed remote PCR

CSCef68719

clrsmcnf causes pnCCb crash and pxm45b resets

CSCef70625

MFRDT: Link stays up when delay exceed limits 300 ms

CSCef71734

MFR addmfrport need to check bundle inhibit state

CSCef74837

On stdby, delmfrlnk may fail after deleting mfr port.

CSCef74965

WIN6653: Tx pool list corrupted if having different buffer size

CSCef75447

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

CSCef77552

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

CSCef79483

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

CSCef79588

AXSM-XG SCT files have wrong OID and threshold value

CSCef79694

ssiSemShow gives divide by zero error

CSCef80396

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

CSCef81959

stby MPSM-T3E3-155 in failed state after loadrev

CSCef82223

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

CSCef82937

link stuck in addsend state due to link name mismatch.

CSCef83498

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

CSCef83875

MFRDT: Dspmfrlnkcnt need reset after switched from Stdby to Active

CSCef84575

MFRDT: WinPath Packet Bus Monitor error after link addition WIN6805

CSCef86540

I2C version check should be removed

CSCef89191

IMA84 SDRAM refresh rate needs to be increased

CSCef90042

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

CSCef90492

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

CSCef91992

The PTSE is dropped on receiving IG with type 36

CSCef92507

semaphore not defined, pxm45 in active-F

CSCef93530

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

CSCeg01270

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

CSCeg02981

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

CSCeg05624

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

CSCeg07099

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

CSCeg08005

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

CSCeg09699

I2C driver support for winpath B1 chips

CSCeg09701

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

CSCeg11715

mpsmoc3 diagnostics enhancements

CSCeg15436

Too many logging messages from ccProtoGet, DSPImageGet

CSCeg17345

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

CSCeg18728

WDDI/DPS patch 246 check in

CSCeg22314

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

CSCeg24868

vxsm_parms_evts.h file needs to be auto generated

CSCeg29724

XM60 insertion causing active PXM45C to reset

CSCeg34421

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

CSCeg35663

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

CSCeg40316

WDDI sets tag to user_info field only for OAM channel

CSCeg50990

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

CSCeg52860

WatchDog timeout core dump caused by Sar Queue Full

CSCeg62909

Boot image corrupted during burnboot process

CSCeg68790

dsprcon cli command missing73-level PN and VID

CSCeg76224

Support for SFP detection

CSCeg88649

ABR configuration lost after stby reset

CSCeh03046

SNMP agent should allow setting loopback state to noLpbk from nonDestructive

CSCeh15349

clrchancnt after stopping traffic does not show traffic cleared

CSCeh15410

WFQ cannot be disabled on ABR connections

CSCeh16336

WFQ cannot be enabled on CBR/VBR connections

CSCin59675

AUTO:UPC policing parameters are not properly displayed for AXSMXG

CSCin79215

Traps not getting generated for MFR link addition

Anomalies Status Change in Release 5.0.20

Table 29 lists the anomaly that has changed status in Release 5.0.20.

Table 29 Anomalies Status Change in Release 5.0.20

Bug ID

Description

CSCef16695

MPSM card does not implement the tstpingoam command

CSCee63184

snmpwalk on resource partition table is failing

CSCee68209

Bulk add abr1 conn to mpsm-8t1e1-atm often failed through proxy

CSCee69639

EIT-8830:AXSME-OC12 is stuck in Failed State with an SSI-3-Exception

CSCee70695

VSI slave/vsi master communication got corrupted

CSCee73638

IPC errors:ilmi did not come up after dn/upilmi

CSCee79092

Stby MPSM-OC3 is stuck in INIT state

CSCee88168

Conn failed due to user cell rate not avail. and cross-commit failure

CSCef01952

Secondary rpm-pr card wont go to standby after reset, cycles boot-empty

CSCef24613

Dangling connections at pxm found but doesn't exist at sm

CSCeg43061

PXM1E failed to bootup after power recycle

Resolved Anomalies in Previous Releases

Anomalies are organized as follows:

•Resolved Anomalies in Release 5.0.10

•Resolved Anomalies in Release 5.0.00

Resolved Anomalies in Release 5.0.10

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

Table 30 Resolved Anomalies in Release 5.0.10

Bug ID

Description

CSCdz87948

AXSM-9952 config clock source not working properly

CSCea51529

PXM45C cards need ECC enabled.

CSCea65034

dspDevErr/dspDevhist doesn't work on stdby PXM

CSCeb28420

EvtLog:emSyncHumveePort fail messages in log

CSCeb83965

Policing of 80 char limit for dsplns on AXSM-E

CSCec63412

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

CSCec70107

novram corrupted (fc id) corrupted

CSCec83227

MPEIT:MPSM card resets because of emRoot Exiting

CSCed09998

AXSMXG support for ABR dual leaky bucket.

CSCed10963

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

CSCed25756

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

CSCed43063

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

CSCed43129

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

CSCed45527

bootChange applies incorrect default values to some fields

CSCed48943

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

CSCed52168

plcp stats are not displayed on switch CLI for ds3 Lines

CSCed53501

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

CSCed53630

FR traffic cannot pass through E3 G751

CSCed56001

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

CSCed56640

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

CSCed56839

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

CSCed59288

tRootTask: SYS-1-TASKLOSTFATAL system reset on pxm1

CSCed60771

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

CSCed61340

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

CSCed62026

delport fails on MPSM-CES and MPSM-ATM card

CSCed62493

DOS: Inconsistent file size and contents immediately after FTP

CSCed62531

multiples of 50 cps on IMA group ATM port rate limitation

CSCed64456

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

CSCed65153

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

CSCed65346

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

CSCed65476

one frame/cell drops when resuming traffic on another path

CSCed65762

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

CSCed66567

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

CSCed67077

many connections stuck in mismatch alarm after cnfpart -maxcon

CSCed67161

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

CSCed67543

Bandwidth used by ILMI should be CACed

CSCed67567

MPSM Diag tests cause WP Buss Polling exception

CSCed67641

SNTP updated TOD information more frequently than should be.

CSCed68441

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

CSCed68735

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

CSCed69122

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

CSCed71549

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

CSCed71719

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

CSCed72328

call rate enhancement in MPSM OC3 winpath

CSCed73181

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

CSCed73552

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

CSCed74374

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

CSCed74450

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

CSCed79636

cell discarding at egress when other 2000 connections in alarm

CSCed79767

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

CSCed81006

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

CSCed81492

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

CSCed81568

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

CSCed81573

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

CSCed81645

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

CSCed81676

Port present on service module, but missing in PAR.

CSCed84291

MPSM-OC3 card went into Active -F state

CSCed84737

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

CSCed85445

replace ssiRamIovCurMaxElementsGet with new SSI API (in all AXSM app

CSCed85997

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

CSCed86130

CESM-8T1E1 disables processing of RAI if lineCondition enabled

CSCed88354

XG-UPC non-compliance counters incorrect for framed conns

CSCed88488

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

CSCed89620

AXSMXG offline diag fail on timeout 3 hours later

CSCed89697

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

CSCed90393

OAM issues between RPM-XF and MPSM

CSCed91102

FGCRA does not work on MPSM155

CSCed91160

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

CSCed91876

XG-UPC hot core dump causes exception

CSCed92346

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

CSCed92601

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

CSCed93586

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

CSCed94135

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

CSCed94385

Xbar errors on slots with AXSM-E cards

CSCed94878

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

CSCed94954

pnCcb exception caused switchover

CSCed95652

Rev.B: CES CAS channel does not receive traffic

CSCed95664

Rev.B: dspWpUtil does not work

CSCed95687

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

CSCed95766

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

CSCed95913

dsppaths command displays DS1 paths out of order in T3 backcard

CSCee00796

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

CSCee00828

RevB board takes a long time to download firmware

CSCee02189

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

CSCee02497

AXSMXG: GFR setting is lost on standby after standby reboot

CSCee02914

Unnecessary em log can be removed in GetPartialLinePmStats()

CSCee03906

Failing adding red still allocates license

CSCee04644

remove <frport_num> parameter option from addbert on MPSM

CSCee05232

Continuous traffic drop on MPSM IMA port upon running stress test

CSCee05255

PNNI crashed after running resetcd script

CSCee07111

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

CSCee09022

reverting cnfrteopt TOD and VPI/VCI parameters to defaults

CSCee09064

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

CSCee09072

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

CSCee09158

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

CSCee10237

Fail to automatically create CUT dir if accidently deleted

CSCee11986

RTD on NB-ATM and IMA interfaces is high

CSCee12710

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

CSCee12720

IPC resolve errors from task tVsiSlave

CSCee14367

PXM reset and coredumped due to descriptor table full

CSCee16049

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

CSCee16959

PXM45 not downloading enable.stats file to SMs after switchredcd

CSCee17245

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

CSCee18300

PNNI: Reachable address shows old node ATM address

CSCee18428

cpro did not read SCT service type correctly

CSCee18442

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

CSCee19358

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

CSCee19912

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

CSCee20454

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

CSCee20817

AXSM switchover resulted in data outage on AXSM-MPSM conns

CSCee22385

FTP server task write to stale socket - cause file corruption

CSCee24142

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

CSCee24554

MPSM8-RAS: Adding VPC rebooting MPSM-8T1E1

CSCee24831

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

CSCee27978

Inserting both backcards generated multiple ApsModeMismatchClr traps

CSCee28318

SUNI driver needs to insert arbitrary pointer change to downstream

CSCee30064

connections deleted on AUSM switchredcd & PXM reset

CSCee30273

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

CSCee31377

MPSM OC3 SIM card failed on upgrade

CSCee31972

UPG5+: XG EVNNI port stuck in down after runrev

CSCee32671

LMI sends incorrect message during timer retry

CSCee35169

AXSM Resets SNMP Subagent Software Exception

CSCee35248

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

CSCee35698

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

CSCee35820

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

CSCee38216

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

CSCee39204

No Action taken on Mutex semaphore hang for NON stdout semaphore

CSCee39665

cliRat task died during stdby card coming up

CSCee40457

Standby PXM reset/failed during upgrade

CSCee42145

Switch ASIC semaphore causes CLI freeze-AXSME

CSCee42153

UPG5+: Mem leak from AXSM-XG lmiRootTask

CSCee43147

LMI data corruption if multiple LMI ports configured

CSCee43404

active PXM45B reset by SSI exception

CSCee44283

UPG5+: P2MP failed to commit to AXSM after upgrade

CSCee44466

LMI Control VC should use VSI service type signalling

CSCee44697

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

CSCee44876

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

CSCee45538

Switch ASIC semaphore causes CLI freeze-AXSMXG

CSCee45542

Switch ASIC semaphore causes CLI freeze-PXM1E

CSCee45544

Switch ASIC semaphore causes CLI freeze-MPSMOC3

CSCee45558

When LMI goes down - send heart beat messages only

CSCee45645

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

CSCee45813

1st traplet from trap 50620 has unmatching checksum

CSCee46860

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

CSCee47465

CBSM-AXSMXG conn - after switchredcd - traffic stops

CSCee48033

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

CSCee48346

Execute more than 10K ping commands caused memory corruption

CSCee48721

AXSMXG-FDR:ECC-MBit error causes card Failure

CSCee50647

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

CSCee52477

Need to remove logging stack trace from ssiStringCopy

CSCee53175

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

CSCee54810

-sc option on MPSM cnfln is invalid

CSCee55966

Popup msg on telnet: pipcSend send error: AUTOCARD

CSCee55997

dspports on AXSM-E does not follow 80 char formatting

CSCee56267

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

CSCee57791

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

CSCee59053

dspcd CLI command on Line card does not display VID field

CSCee61427

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

CSCee61463

Critical HW Mastership errors declared on PXM after switchcc

CSCee62436

MPSM addcon only allows max CIR to partial port speed.

CSCee62933

REG5+: SSI-3-EXCEPTION Software exception found

CSCee63139

UPG5+: Mem leak on AXSM after line config failure

CSCee63140

dbSvrSync task holding memory block

CSCee63159

vnni port propagation is failing

CSCee65520

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

CSCee66754

PXM45C: Single Bit ecc errors on resetting PXM intermittently.

CSCee67637

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

CSCee68047

CLI warning message for delpref command

CSCee69222

Excessive MIB-7_MODULE_UNKNOWN event log messages

CSCee70641

pnCcb task got suspended at sscop_chk_txQ_for_statenq_or_bse()

CSCee70837

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

CSCee72296

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

CSCee72388

addcon fails for CBR ATM conns with PCR = 104268 cps

CSCee73008

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

CSCee74007

MPSM-8T1E1 keep rebooting due to diag caused exception

CSCee74345

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

CSCee77715

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

CSCee78093

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

CSCee78941

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

CSCee78995

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

CSCee80833

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

CSCee80886

xg-oc48 in failed/empty after resetcd

CSCee80889

ssi snmp exception error on AXSM-XG

CSCee80910

ilmi as disabled on xg pnport

CSCee81869

Obsolete traps 60126 and 60127 need to be removed

CSCee83187

MPSM-155 pnni trunk stuck in auto-config

CSCee83711

Switch driver error noticed on pxm1e

CSCee84449

Fix for parameter memory timing issue

CSCee85874

WIN5816: Egress OAM Loopback test causes MPSM card to reboot

CSCee88501

ilmi errors in the log for MPSM

CSCee89505

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

CSCee89950

IPC error: IlmiPassup reaches the max queue and drop packets

CSCee91460

switchredcd caused previously active FRSM to constantly reset

CSCee92794

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

CSCee92813

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

CSCee93763

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

CSCee94585

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

CSCee95371

IMA pnni-link deroute conns when switchred

CSCee95646

MPSM OC3 in Active-F after addport failed

CSCee96764

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

CSCef04048

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

CSCef04619

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

CSCef12968

Memory Leak on AXSM when issuing multiple tstdelay/tstconseg command

CSCef13315

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

CSCef13392

Add debug code in VSI to verify with HW

CSCef16855

Provide infra support for PPP_ALARM and MFR_ALARM.

CSCef18694

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

CSCef23594

Incorrect redundant MPSM-8T1E1 card config info upload

CSCef24248

changes to handle the frsm getting stuck in failed state

CSCef24752

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

CSCef24789

MPSM-OC3 NNI/VNNI links in building VC state

CSCef41542

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

CSCin69908

Trap 50401 containing wrong port number after start bert

CSCin72192

oof_criteria,aisc_check gets populated in line table for E3 interface

CSCin79508

Cannot CC to the card after resetsys or resetcd

Resolved Anomalies in Release 5.0.00

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

Table 31 Resolved Anomalies in Release 5.0.00

Bug ID

Description

CSCdv32986

100% data is getting dropped on some connections

CSCdw91580

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

CSCdy23797

pntrace command needs to be updated in documentation

CSCdy77053

dspportcnt does not have Ingress counter

CSCdz04524

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

CSCdz54692

Add additional fields for sonet/ds3 path traps

CSCdz87948

AXSM-9952 config clock source not working properly

CSCea46779

PXM45/B with broken Humvee-SAR interface

CSCea59612

dnpnport/uppnport caused all links to go to ILMI failure

CSCea64363

dspDevErr need to be modified to show the device No.

CSCea75353

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

CSCeb05910

PM parameters on NBSMs are not accurate

CSCeb11493

Inconsistent routing cost

CSCeb13272

P2MP pnRedman exception triggered during delparties

CSCeb15291

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

CSCeb17823

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

CSCeb20522

EvtLog: switchcc-CTC-4-EVTSENDTOSTMCHN error message

CSCeb20570

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

CSCeb28420

EvtLog: emSyncHumveePort fail messages in log

CSCeb35085

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

CSCeb38659

resetsys on PXM45 causes AINI port to vc failure

CSCeb38985

MOC error caused ILMI failure on AXSM-XG card

CSCeb40265

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

CSCeb40512

delred fail for LSM in 8830

CSCeb41273

cnfdiagall command does not work after cnfdiag <slot> used

CSCeb45254

SRMEB: Add/Del line loop cause APS failure

CSCeb51323

SRMEB: Stats manager caused Active PXM1E reset

CSCeb58207

none of the bert commands executed is seen in the dsplog

CSCeb58227

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

CSCeb58599

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

CSCeb59239

PM parameters on NBSMs are not accurate

CSCeb60706

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

CSCeb63198

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

CSCeb64000

switchover loss around 630 ms, >250 ms

CSCeb67820

CIT50: node db contains two entries with same node id

CSCeb67843

Failed to add entry in QE48 Conn id table

CSCeb68706

observed message file already closed after runrev executed on frsm

CSCeb71578

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

CSCeb76581

CIT50: pnRedman suspended at provred_persis_link_addDel

CSCeb80000

conn doesn't deroute right away upon dnport with deroute delay on an

CSCeb83949

Policing of 80 char limit for dsppnportcac and dsppnportrsrc command

CSCec01073

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

CSCec05854

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

CSCec08533

CESM T3E3 1:1 Redundancy is not functional

CSCec12108

Pnports of AXSM-XG card stay in building vc

CSCec12463

EVENT-CLEANUP: multiple ncdp fill in dsperrs log.

CSCec12609

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

CSCec14761

Software Error Reset PXM45

CSCec16762

Cant cc on AXSM due to max sessions in hang

CSCec23758

FRSM HS1 connections stuck in AIS alarm after card reset.

CSCec27723

Pnni signalling lcn reuse - pnni link cannot establish

CSCec28435

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

CSCec31183

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

CSCec33505

Receive FIFO not held in reset during dnln.

CSCec35834

Card failed to come back active after reboot (RPM)

CSCec39239

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

CSCec40496

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

CSCec41322

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

CSCec41394

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

CSCec42058

Statistical Alarm counters are not ok

CSCec42174

getting xbar alarm with offline diags enabled

CSCec42531

Err on switchcc outstanding database update

CSCec43059

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

CSCec45604

Re-used port stay in alarm

CSCec45631

UI-S3 Clock Controller fails to enter Free Run mode

CSCec49118

Standby AXSM Failed due to IPC buffer leak on Active AXSM

CSCec49709

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

CSCec51074

backcard aps mux not set accordingly after switchred

CSCec51349

PXM1e reset after pumping high rate oam loopback

CSCec55245

Allowing to turn off rate control feature with ABR configured

CSCec55319

Mem leakage in procResponse: RespCalcC exhausting SSI SNMP partition

CSCec55976

vsiSlave Task suspended recovery action should be Fatal

CSCec56452

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

CSCec59926

dump commands pause indefinitely with RPMs and may leak resources

CSCec62846

Failure on the data forwarding path was not detected

CSCec63239

VxWorks timer wrapped around

CSCec63535

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

CSCec63556

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

CSCec63713

AXSM reset with core dump

CSCec65160

dspload shows asymmetric bandwidth on AXSMs

CSCec66028

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

CSCec66037

UBR.2 policing needs to tag all cells

CSCec66881

LSNT:AXSM Xtags does not come up

CSCec67719

HMM and QE48 falsely detects parity error when enabled

CSCec69262

PXM does not switch RPM-XF upon bkcd failures

CSCec69678

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

CSCec71316

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

CSCec78432

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

CSCec79143

Watchdog resets on AXSM observed

CSCec79734

UPG5: APS adj line stuck in LOS after node rebuild

CSCec82151

MPEIT: pnCcb crash after clrsmcnf on MPSM oc3 card

CSCec83032

Internal Osc priority going back to default value after rebuild

CSCec87046

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

CSCec88175

The redundant RPM card did not cover for failed primary.

CSCed01505

threshold for SCM task hanging should be less

CSCed01523

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

CSCed01970

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

CSCed02565

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

CSCed09164

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

CSCed09942

Minor issue on displaying card alarm state

CSCed14131

switchcc fail because standby PXM xbar is degraded

CSCed15676

Channel showing OK state with Controller Abit = 0

CSCed17323

Duplicate entries for conns in the STATS files

CSCed22720

Active PXM1E switched over after Standby Combo back card inserted

CSCed22794

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

CSCed23150

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

CSCed24987

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

CSCed25756

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

CSCed26797

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

CSCed30255

MAINT Connections not torn down in via node after dnpnport

CSCed30486

Line configuration changes do not get applied to standby APS lines

CSCed30887

Login denial of service with [infinite login prompt] script

CSCed31789

vnni port alarm propagation not there when vpc is down

CSCed33148

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

CSCed33156

Popup msg:Can't write to C:/, errno 0x38800f

CSCed33292

StdAbr table in the config upload file

CSCed34580

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

CSCed35995

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

CSCed36616

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

CSCed39429

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

CSCed39860

snmpget is failing for the node, no chunks for snmp

CSCed40835

DAX cons went to failed state after resetting card

CSCed41216

LDNT: AXSM shows some memory allocation/free failures

CSCed41580

AXSM-XG OC48 stuck in empty reserved after switchred

CSCed41771

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

CSCed42998

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

CSCed43063

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

CSCed43168

standby CESM shown as active in dspcd output

CSCed43288

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

CSCed44103

ifName varbind out of order for sonet 60126, 60127 traps

CSCed44352

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

CSCed45047

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

CSCed45061

PXM1E: Telnet sessions cannot be deleted

CSCed45294

UPG5: Mem leak from AXSM ilmiMain and tCpro tasks

CSCed46156

coredump: software error reset

CSCed46245

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

CSCed46458

Invalid IMA Group parameters accepted by switch thru SNMP

CSCed49638

Diag Error: continuity check failed on AXSM-XG

CSCed50096

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

CSCed51857

Priority bumping does not work as expected when LCNs are exhausted

CSCed53513

Unable to add VP connection on MPSM thru CWM/SNMP

CSCed53671

AXSM-XG pnports in auto config

CSCed55502

Memory block error in cutw

CSCed60203

Clock source is switched in NCDP mode after switchred

CSCed60564

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

CSCed64351

standby AXSM-XG rebooted after dn/upilmi

CSCed68047

PXM console stuck

CSCed69008

coredump on pxm after reset

CSCed69068

watchdog timeout coredump after resetcd on pxm

CSCed69628

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

CSCed71340

AXSM-XG failures while coming up after node rebuild

CSCed72672

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

CSCed77102

AXSM-E card went into Active-F state

CSCed84624

VPI0: connection fails; stops attempting after multiple switchcc

CSCed87053

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

CSCed87160

vnni alarm did not clear on AXSM-XG

CSCed88171

Resource Alarm on standby PXM45

CSCed89400

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

CSCed89620

AXSM-XG offline diag fail on timeout 3 hours later

CSCed94243

Presence of RCON makes cards to go to Mismatch

CSCed94976

pnRedman got suspended: pxms in active-F and init

CSCee00913

8850 stops responding to snmp requests after upgrading PXM image

CSCee02920

AXSM-XG path in alarm after upgrade

CSCee16959

PXM45 not downloading enable.stats file to SMs after switchredcd

CSCin66401

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

Known Route Processor Module or MPLS Anomalies

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

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

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

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

Documentation

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

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

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

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

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

Documentation DVD

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

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

Cisco Ordering tool:

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

Cisco Marketplace:

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

Ordering Documentation

You can find instructions for ordering documentation at this URL:

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

You can order Cisco documentation in these ways:

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

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

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

Documentation Feedback

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

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

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

From this site, you can perform these tasks:

•Report security vulnerabilities in Cisco products.

•Obtain assistance with security incidents that involve Cisco products.

•Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

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

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

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

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

•Emergencies — security-alert@cisco.com

•Nonemergencies — psirt@cisco.com

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

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

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

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

•1 877 228-7302

•1 408 525-6532

Obtaining Technical Assistance

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

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

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

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

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

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

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

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

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

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

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

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

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

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

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

Acronyms

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

.

Table 32 Acronyms Used in These Release Notes

Acronym

Description

AXSM

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

ABR

Available bit rate

APS

Automatic Protection Switching

CALEA/LI

Communications Assistance for Law Enforcement Act/ Lawful Intercept

CBSM

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

CLI

Command Line Interface

CoS

Class of service

CUG

Closed User Group

CWM

Cisco Wide Area Network Manager

GE

Gigabit Ethernet

IAP

Intercept Access Point

IMA

Inverse Multiplexing over ATM

LANE

Local Area Network Emulation

LFI

Link Fragmentation Interleaving

MFR

Multi-Link Frame Relay

MLPPP/LFI

Multi-Link PPP

MPSM

Multi-Protocol Service Module

MTI

Multicast Tunnel Interface

NBSM

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

P2MP

Point-to-Multipoint

PE

Provider Edge

PER

Product Enhancement Request

PNNI

Private Network-to-Network Interface

POS

Packet over SONET

POST

Power On Self-Test

PPP

Point-to-Point Protocol

PXM

Processor Switch Module

RPM

Route Processor Module

SFP

Small Form Factor Pluggable Unit

SM

Service Module

SONET

Synchronous Optical NETwork

SPVC

Soft permanent virtual connection

SRM

Service Resource Module

SVC

Switched virtual circuit

VPN

Virtual Private Network

VRF

VPN Routing / Forwarding

VXSM

Voice Switching Service Module

XF

Express Forwarding

CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.

Cisco MGX 8800 Series Switches

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

Hierarchical Navigation

Downloads

Table Of Contents

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

Contents

About Release 5.0.20

Changes to Release 5.0.20

Type of Release

Locating Software Updates

Features and Enhancements in Release 5.0.20

Multilink Frame Relay on MPSM-T3E3-155

Features

Restrictions

Multilink Frame Relay Quick Start Provisioning Procedures

Multilink Frame Relay General Provisioning Procedures

Creating an MFR Bundle

Configuring an MFR Bundle

Adding Links to an MFR Bundle

Configuring MFR Links

Adding a Port to the MFR Bundle

Deleting an MFR Bundle, Link, or Port

Port Oversubscription on MPSM-T3/E3-155

Channel Loopback on MPSM-T3E3-155

Restrictions

Enhancement to Statistics Counters on MPSM-T3E3-155

Features and Enhancements in Previous Release 5.0.10

CES Line Conditioning

Platforms

MPSM Service Modules

MPSM Licenses

Platforms

PXM45 RAS

Platforms

Standard Available Bit Rate (ABR) Mapping Changes (PER 4148)

Platforms

License Management

Platforms

AXSM-16-155-XG Feeder Support

Limitation

Platforms

Unique Device Identifier (UDI)

Limitations

Platforms

Features and Enhancements in Previous Release 5.0.00

SRME/B

Platforms

AXSM-16-155-XG

Platforms

AIS Delay, Deroute Delay, Absolute Grooming

Platforms

Soft Reroute

Platforms

Point to Multipoint Support on PXM1E

Limitation

Platforms

Enhancements to Route Optimization

Platforms

Priority Bumping

Platforms

Enhancements

Service Class Template (SCT) File Information

MPSM-155

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-XG

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

Additional Notes

SNMP MIB Release

Hardware Supported

New Hardware in Release 5.0.20

New Hardware in Release 5.0.10

Product IDs, Card Types, and APS Connectors

MGX 8850 (PXM45/PXM1E), MGX 8950, and MGX 8830 Product IDs and Card Types

New and Changed Commands

New and Changed MPSM-T3E3-155 Commands