Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco ...

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

Revised: June 26, 2008, OL-11771-03

ContentsThe content of this document is arranged into the following major sections:

About This Release, page 5

Locating Software Updates, page 6

Features in Release 5.4.30, page 6

Detecting Parity Error on a Standby AXSM, page 6

Refreshing the AXSM Virtual Connection Table, page 6


Provisioning Connections on Failed IMA Port, page 7


DTMF Squelching, page 9

Bidirectional Forwarding Detection Version 1, page 9

DSCP Marking on RPM-XF Management Interface, page 9

Flash MIB Support, page 10

SNMPv3, page 10

Trap Squelch Feature, page 10

Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45C, page 10


MPSM Licensing Changes, page 11

Americas Headquarters:

© 2007 Cisco Systems, Inc. All rights reserved.

Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA

Contents

Support for Clear Channel E1 Lines, page 12

Support for BERT Tests on Clear Channel T3/E3 Lines, page 12


Enhanced VXSM Card Support, page 13

Non-Redundant Upgrade Procedure, page 13

Redundant Upgrade Procedure, page 13

Cisco MGX 8800 Series Operating and Storage Environment, page 14

Guidance for Operating and Storage Environments, page 14

Operating Environment Specifications, page 14

Non-operating and Storage Environment Specifications, page 15


Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO, page 15

Summary of MLPPP Changes, page 16

MLPPP Configuration, page 16

MLPPP Upgrade Considerations, page 17

Fractional T1/E1 Links for ATM Services, page 17

Fractional T1/E1 Configuration, page 17

Fractional T1/E1 Configuration Limitations, page 18

Security Enhancements, page 19

SFTP and SSH Features, page 19

Remote IP Management Connection Enhancements, page 20

Management Connection Limitations, page 21

Configuring an RPM Management Connection, page 21

Management Configuration—Example, page 22

Routing Enhancement for AXSM-XG Cards, page 23

Platform Enhancements, page 24

Cisco MGX 8830/B Enhancements, page 24

RPM-PR Ethernet Back Card, page 25



MGX-VXSM-T3 Card, page 26

AXSM-8-622-XG Card, page 26

Graceful Upgrades to AXSM-XG Cards, page 28

Multilink PPP on the MPSM-T3E3-155 Card, page 28

PXM45/C Support in the Cisco MGX 8830/B Chassis, page 29

Mobile PNNI Support, page 29

Compression and Multiplexing Support for RPM-PR Cards, page 29


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

OL-11771-03

Contents


MPSM-16-T1E1 Card, page 30

Operational Modes, page 30

Supported Features, page 30

Multilink PPP Feature for CDMA2000 and EV-DO, page 33

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics, page 33

Private Network Node Interface Current Route Feature, page 33

Operational and Redundancy Limitations, page 34

Feature Specifications, page 35

PNNI Product Enhancements, page 35

PXM1E OAM Enhancement, page 36

System Requirements, page 37

Software/Firmware Compatibility Matrix, page 37

MGX and RPM Software Version Compatibility Matrix, page 38

SNMP MIB Release, page 40

Supported Hardware, page 40

Hardware in Release 5.4.30, page 41

Product IDs, Card Types, and APS Connectors, page 41

Service Class Template File Information, page 53

PXM1E SCT Files, page 53

AXSM and AXSM/B SCT Files, page 53

AXSM-E SCT Files, page 54

AXSM-XG SCT Files, page 54

MPSM-T3E3-155 SCT Files, page 55

MPSM-16-T1E1 SCT Files, page 56

New and Changed Commands, page 56

New Commands in Release 5.4.30, page 56

New Commands in Release 5.4.10, page 57

Changed Commands in Release 5.4.00, page 60

Changed MPSM Commands, page 61

Changed PXM Commands, page 61

Changed AXSM Commands, page 61



Changed MPSM Commands, page 62

Changed PXM Commands, page 82

Changed AXSM-XG Commands, page 91

MGX Release 5.4.30 Limitations, Restrictions, and Notes, page 91


OL-11771-03

Contents

Upgrade Limitation, page 91

BERT Limitation, page 91

MGX Voltage Measurement Limitation, page 91

MGX Chassis Bandwidth Limitations, page 92

Bandwidth Limits, page 92

Card Placement Guidelines, page 92

Bandwidth Oversubscription, page 93

PXM1E Switch Limitations, page 93

PXM1E Hardware Limitations, page 94

PXM1E Reserved Virtual Channel Identifiers, page 94

PXM1E Point to Multipoint Support, page 95

PXM1E Parity Errors, page 95

PXM1E Policing Accuracy, page 95

PXM45 and PXM1E System Limitations, page 96

Maximum Threshold Accuracy, page 96

Clearing the Configuration on Redundant PXM45 and PXM1E Cards, page 96

SPVC Interoperability Limitations, page 97

Service Card Limitations, page 97

AXSM-16-155-XG with MCC Back Card Limitations, page 97

AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations, page 98

AXSM-E Card OAM Limitations, page 99

General AXSM Card Limitations, page 99

AXSM Card APS Limitations, page 100

MPSM Card Limitations, page 100

CBSM Card Limitations, page 101

IGX Feeder Limitation, page 102

Clock Source Limitations, page 102

Clearing Card Configuration Notes, page 102

PNNI Limitations, page 102

Logical Link Limits, page 102

Preferred Route Limitations, page 103

Priority Route Limitations, page 103

Persistent Topology Limitations, page 104

Fault Isolation and Trace Limitations, page 105

Serial Bus Path Fault Isolation Limitation, page 105

Cell Bus Path Fault Isolation and Recovery Limitations, page 105

Path and Connection Trace Notes, page 105

CLI Access Level Notes, page 106


OL-11771-03

About This Release

Disk Space Maintenance Notes, page 106

Non-native Controller Front Card and PXM-HD Card Notes, page 107

Other Limitations and Restrictions, page 107

Installation and Upgrade Procedures, page 107

Supported Upgrade Paths, page 108

Upgrade Information, page 108

Upgrading AXSM-XG Cards, page 109

Upgrading the VISM-PR Image, page 109

Maintenance Information, page 109

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

Supported Upgrade Paths, page 108

Open Caveats, page 110

Resolved Caveats, page 111

Release 5.4.30, page 112













Documentation Updates, page 150

Documentation, page 151

Acronyms, page 151

Obtaining Documentation, Obtaining Support, and Security Guidelines, page 153

About This ReleaseThese release notes describe the system requirements, new features, and limitations that apply to Release 5.4.30. These notes also contain Cisco support information.

Release 5.4.30 is a software release for the following Cisco multiservice switches (MGXs):

• Cisco MGX 8830 (Processor Switch Module, or PXM1E)

• Cisco MGX 8830/B (PXM1E and PXM45)


OL-11771-03

Features in Release 5.4.30

• Cisco MGX 8850 (PXM1E and PXM45)

• Cisco MGX 8850/B (PXM1E and PXM45)

• Cisco MGX 8950 (PXM45)

Note To verify that you have the latest version of Cisco IOS required to support the new features included in this release, please check Cisco IOS availability status at Cisco.com.

Locating Software UpdatesRelease 5.4.30 software is located at:

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

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

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

Features in Release 5.4.30Release 5.4.30 includes the following new features for the Cisco MGX platforms:

• Detecting Parity Error on a Standby AXSM, page 6

• Refreshing the AXSM Virtual Connection Table, page 6

Detecting Parity Error on a Standby AXSMOn an AXSM card, the queuing engine QE48 maintains the virtual connection table (VCT). In rare instances, parity errors occur in VCT memory. This leads to failure of the active AXSM card and, subsequently, the standby card.

Whenever both cards fail, a traffic outage occurs until one of the cards becomes active. In Release 5.4.30, the probability of dual AXSM failure is reduced by proactively detecting the error on the standby card.

Note This feature does not require any configuration by the user. As soon as the standby AXSM card is upgraded to the new image, the feature comes into effect.

Note Only AXSM B supports this feature.

Refreshing the AXSM Virtual Connection TableOn an AXSM card, the queuing engine QE48 maintains the virtual connection table (VCT). In rare instances, parity errors occur in VCT memory. The hardware monitoring module (HMM) monitors these parity errors and resets the card if the number of parity errors exceeds a predefined threshold value. If the customer does not have a redundancy card, the slot either fails or resets when the number of errors crosses the threshold value.


OL-11771-03

http://www.cisco.com/en/US/products/sw/iosswrel/products_ios_cisco_ios_software_category_home.html


In Release 5.4.30 and later releases, if the parity error is caused by the VCT memory bit flip, then the VCT memory is refreshed so that it corrects the bit flip. The VCT memory refresh avoids resetting the card and prevents the outage. The VCT refresh cycle time for 128K connections is close to 12 minutes. A new command is added to enable this feature. For more information about the commands introduced, refer to the section New and Changed Commands, page 56.

Note Only AXSM B supports this feature.

Limitations

The following limitations apply:

• The outages due to transient hardware errors cannot be resolved using this feature.

• Only point-to-point connections are refreshed.

• This feature introduces a maximum of 600 ms of delay in connection provisioning and re-routing.

Features in Release 5.4.10Release 5.4.10 includes the following new feature for the Cisco MGX platforms:

• Provisioning Connections on Failed IMA Port, page 7

Provisioning Connections on Failed IMA PortThe provisioning of connections on a failed IMA port was allowed in release 5.0.11. In release 5.3.20, the same feature is not allowed. This change in behavior of MPSM firmware affects user’s operations and a user cannot provision connections in the same way they used to do it for 5.0.11 release. This was happening because of the feature BWUPD (bandwidth update). In BWUPD feature, the VSI master does not allow provisioning of SPVC end points on IMA UNI ports if there is not enough bandwidth left on the port. When 5.3.20 firmware is present, it will update the VSI master that the bandwidth available on the IMA port is zero. So when a user tries to provision the connection, the system does not allow provisioning.

In this release, a new card level CLI is introduced to enable or disable BWUPD (bandwidth update) feature. Also, a new IMA group level CLI is introduced to override the default settings of BWUPD feature while adding an IMA group. For more information about the commands introduced, refer to the section New and Changed Commands, page 56.

Changes in Provisioning the Connections

This section explains what a user has to do to provision the SPVC end points on a failed IMA UNI ports, and at the same time utilize the BWUPD feature for IMA NNI trunks.

New Installation

For new installation, perform the following steps:

Step 1 Disable BWUPD feature at card level.


OL-11771-03


cnfcdbwupd 2

Step 2 Enable BWUPD feature on NNI Port. Do it after adding the IMA group.

cnfimagrpbwupd <group> 1

Note No changes are required for existing UNI port provisioning for new installation.

Upgrading from 5.0.11

For upgrading to 5.3.20 from 5.0.11, perform the following steps:

Step 1 Disable BWUPD feature at card level.

cnfcdbwupd 2

Step 2 Disable BWUPD on each UNI port.


Note No changes are required for existing NNI port provisioning.

Provisioning Connections after Upgrading from 5.0.11

Perform the following steps for provisioning the connections after upgrading from 5.0.11:

Step 1 Enable BWUPD feature on NNI Port. Do it after adding the IMA group.


Note No changes are required for UNI port provisioning.

Follow the same steps for upgrading from 5.3.20.

Limitations


• The support is only through CLI. SNMP support is not provided.

• For each IMA group, only one port is configured. If there is more than one virtual port configured, all the ports will pick up the same configuration of the IMA group.

Features in Release 5.4.00Release 5.4.00 has the following new and changed features:

• DTMF Squelching, page 9

• Bidirectional Forwarding Detection Version 1, page 9

• DSCP Marking on RPM-XF Management Interface, page 9

• Flash MIB Support, page 10


OL-11771-03


• SNMPv3, page 10

• Trap Squelch Feature, page 10

DTMF SquelchingVersion .201 of this release contains the enhancements to VXSM to completely squelch DTMF digits. This feature can be provisioned using the CLI commands shown below.

Note These CLI commands are not new for this release. They already exist in the product.

For H.248

Syntax Description cnfh248profdtmf <Index> <DigitOnDuration> <DtmfPauseDuration> <DetectLongDigitDuration> <SuppressBearerDigit>

Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.

For XGCP

Syntax Description cnfxgcpprofdtmf <ProfileIndex> <SuppressBearerDigit>

Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.

Bidirectional Forwarding Detection Version 1Bidirectional Forwarding Detection version 1 (BFDv1) improves protocol convergence times by rapidly detecting failures in the path between routers. This is especially important for media that does not provide failure signaling, such as Ethernet, because the OSPF protocol can take a second or more to detect a signaling loss using hello messages. This is too long for some applications and can result in excessive data loss, especially at gigabit rates. BFDv1 quickly detects a media failure so that the OSPF protocol can quickly update routes.

DSCP Marking on RPM-XF Management InterfaceThis release supports Differentiated Services Code Point (DSCP) or IP Precedence marking for quality of service (QoS) configurations on the RPM-XF management back cards. With this enhancement, the RPM-XF supports Layer 3 QoS on the Fast Ethernet management back card.

Limitations

The following limitations apply to the DSCP marking of management packets on the RPM_XF management back card:

• The RPM-XF does not support DSCP marking for the interface to the MGX switch cell bus.


OL-11771-03


• The RPM-XF management back card can be used for only management traffic, not data traffic.

Flash MIB SupportNetwork management systems (NMS) can manage software images stored in boot flash using SNMP when the device supports the CISCO-FLASH-MIB. The RPM-XF supports the CISCO-FLASH-MIB in this and later releases. For MGX 8800/8900 multiservice switches, the NMS can query objects defined in the CISCO-FLASH-MIB through the PXM management interface or the RPM-XF management interface.

SNMPv3Simple Network Management Protocol Version 3 (SNMPv3) is a standards-based protocol for network management. SNMPv3 provides secure access to devices using a combination of authentication and encryption of packets over the network. This assures that data can be collected securely from SNMP devices and that configuration messages cannot be viewed or altered.

The security features provided in SNMPv3 are:

• Message integrity—Ensuring that a packet has not been tampered with in transit.

• Authentication—Determining that the message is from a valid source.

• Encryption—Scrambling the contents of a packet prevent it from being seen by an unauthorized source.

Trap Squelch FeatureThe large number of traps a large system can generate can degrade the performance of a network management system. The trap squelch feature helps limit the number of traps that Cisco MGX switches generate. You can either block all traps of a specific type or limit the rate of specified traps.

Limitations


• The squelch list holds up to 200 trap types.

• The minimum value of the sampling interval is five minutes and the maximum value is 30 minutes.

Support for AXSM-1-2488/B Card in 8830/B Chassis with PXM45CWith this release, support for the AXSM-1-2488/B card in the MGX 8830/B chassis has been added. The AXSM-1-2488/B card is already supported in the MGX 8850 and 8950 chassis.

Features in Release 5.3.20Release 5.3.20 has the following new and changed features:

• MPSM Licensing Changes


OL-11771-03


• Support for Clear Channel E1 Lines

• Support for BERT Tests on Clear Channel T3/E3 Lines

MPSM Licensing ChangesRelease 5.3.20 enforces licenses through sales and support, rather than through software locks. Table 1 lists the MPSM licenses that are required for MPSM services and features. You must purchase licenses for the services and features that you plan to use on each MPSM card.

Note Before upgrading to Release 5.3.20, enter saveallcnf to preserve existing licensing information.

Table 1 Licensed Services for MPSM Cards

Card Type License Description Software Release Support

5.0.20 5.1.205.2.00 and later

MPSM-8-T1E1 MPSM-RC-8-LIC Rate Control—Enables either Standard ABR or Foresight features for Frame Relay connections.

x x x

MPSM-16-T1E1 MPSM-RC-16-LIC Rate Control—Enables the Standard ABR feature for Frame Relay connections.

x x

MPSM-MS-16-LIC Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.

x x

MPSM-ML-16-LIC MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).

x x

MPSM-PPP-16-LIC MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).

x x

MPSM-SR-16-LIC 1:N Redundancy x x

MPSM-T3E3-155 MPSM-CH-HS-LIC Channelization—Enables channelization of the physical port into multiple DS0s for Frame Relay service and/or DS1s for ATM service.

x x x

MPSM-RC-HS-LIC Rate Control—Enables the Standard ABR feature for Frame Relay connections.

x x x

MPSM-MS-HS-LIC Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.

x x x

MPSM-ML-HS-LIC MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).

x x x

MPSM-PPP-HS-LIC MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).

x


OL-11771-03


Release 5.3.20 removes the PXM commands that support software locks and license alarms, and changes the commands that display alarm information. The following commands are removed or changed:

• Removed PXM commands:

– cnflic

– dsplicalms

– dspliccd

– dspliccds

– dsplicnodeid

– dsplics

• Changed PXM commands:

– clrallcnf—No longer has the clrLicense argument

– dspcdalms—No longer displays license alarms

– dspndalms—No longer displays license alarms

The MIB for Release 5.3.20 does not change, but returned license information is no longer valid.

Support for Clear Channel E1 LinesRelease 5.3.20 adds support for E1 clear channel on MPSM-16-T1E1 cards. Clear channel E1 dedicates the entire E1 bandwidth (2048 Kbps) to a single data stream, and does not contain DS0 channels. To implement this feature, a new line type (dsx1E1CLEAR) is added to the cnfln command. You can configure Frame Relay, ATM, or IMA ports on lines configured for E1 clear channel.

The addport command syntax does not change, but you must use the default values for ds0speed (64K), ds0beg (1), and ds0num (32) when adding a clear channel, even though the line is not actually channelized.

For example, the following commands configure line 1.10 for clear channel, add port 11 to the line with type frameRelayService and the default SCT, and then add a slave connection with DLCI 400, channel type frNIW, high-priority service, and CIR of 2048 Kbps. Notice that the default values for addport correctly configure the channelization parameters for clear channel operation.

M8850_SF.27.MPSM16T1E1[FR].a > cnfln 1.10 -lt 9M8850_SF.27.MPSM16T1E1[FR].a > addport 11 1.10 1 0M8850_SF.27.MPSM16T1E1[FR].a > addcon 11 400 1 1 2 2048000

For more information about configuring lines, see the Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, Release 5.2, “Preparing MPSM-T3E3-155 and MPSM-16-T1E1 Cards and Lines for Communication.”

Support for BERT Tests on Clear Channel T3/E3 LinesRelease 5.3.20 adds support for BERT tests on clear channel T3/E3 lines on MPSM-T3E3-155 cards. To support this feature, the following commands now accept a line number (bay.line) for the bertifNum argument:

• addbert

• cnfbert

• delbert


OL-11771-03


• dspbert

• dspbertcap

• dspbertstats

• insbiterror

• startbert

• stopbert

Additionally, the dsplnalm and dsplnalms commands display the BERT status for a T3/E3 line.

For more information about configuring BERT tests, see Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16T1E1) Configuration Guide and Command Reference, “Card Management on MPSM-T3E3-155 and MPSM-16-T1E1.”

Features in Release 5.3.10Release 5.3.10 includes the following new features and warnings.

Enhanced VXSM Card SupportRelease 5.3.10 supports the Processor Switch Module Hard Disk Voice (PXM-HDV) back card, which supports four or more VXSM cards on a Cisco MGX 8850 switch. The size of the D partition on the PXM-HDV back card is 2000 Mb.

Non-Redundant Upgrade Procedure

To migrate from PXM-HD to PXM-HDV back cards in a non-redundant configuration, perform the following steps:

Step 1 Upgrade the PXM boot and runtime images to release 5.3.10 using the normal upgrade procedure.

Step 2 Upgrade boot and runtime to 5.3.10

Step 3 Enter the saveallcnf command, and ftp the saved configuration file to another host.

Step 4 Replace the PXM-HD back card with the PXM-HDV back card.

Step 5 Retrieve the saved configuration file using ftp.

Step 6 Enter the restoreallcnf command.

Redundant Upgrade Procedure

To migrate from PXM-HD to PXM-HDV back cards in a redundant configuration, perform the following steps:

Step 1 Upgrade the PXM boot and runtime images to release 5.3.10 using the normal upgrade procedure.

Step 2 Replace the standby card back card with a PXM-HDV back card and wait for the PXM-HDV back card to retrieve configuration information from the active PXM-HD back card.


OL-11771-03


Step 3 Enter the switchcc command to force a switchover.

Step 4 Replace the remaining back card with a PXM-HDV back card.

Cisco MGX 8800 Series Operating and Storage EnvironmentThis section describes the operating and storage environments for the Cisco MGX 8800 series multiservice switches, and explains how to prevent oxidation and corrosion problems.

Guidance for Operating and Storage Environments

Dew points indicate the amount moisture in the air. The higher the dew point, the higher the moisture content of the air at a given temperature. Dew point temperature is defined as the temperature to which the air would have to cool (at constant pressure and constant water vapor content) in order to reach saturation. A state of saturation exists when the air is holding the maximum amount of water vapor possible at the existing temperature and pressure

When the Relative Humidity is high, the air temp and dew point temperatures are very close. The opposite it true when the Relative Humidity is low. When the dew point temperature and air temperature are equal, the air is saturated with moisture. Locations with high relative humidities have air that is close to being saturated with moisture. When saturated air cools it cannot hold as much moisture and can cause moisture migration and penetration into the system. This moisture can cause corrosion of internal components.

A storage environment that experiences temperature and/or humidity variations over a short period of time can create a condensing environment, and this is considered an uncontrolled environment. An environment that maintains constant temperature and humidity is considered and climate controlled environment. A temperature and humidity controlled operating and storage environment is required at all times to prevent condensation that can subsequently lead to oxidation of plated metal parts. Cisco recommends that both long term and short term storage environments be climate controlled to prevent humidity and temperature variations that create condensation. Buildings in which climate is controlled by air-conditioning in the warmer months and by heat during the colder months usually maintain an acceptable level of humidity for system equipment.

Note Consult your facilities engineers to evaluate and ensure your storage environment meets the definition of a non-condensing environment.

To prevent oxidation, avoid touching contacts on boards and cards, and protect the system from extreme temperature variations and moist, salty environments.

Operating Environment Specifications

The following specifications define the operating environment:

• Temperature, ambient

– Minimum Temperature: 32 degrees Fahrenheit (0 degrees Celsius)

– Maximum Temperature: 104 degrees Fahrenheit (40 degrees Celsius)

• Humidity, ambient (non-condensing)

– Minimum: 10%


OL-11771-03


– Maximum: 85%

• Altitude

– Minimum: Sea level

– Maximum: 10,000 feet (3,050 meters)

Non-operating and Storage Environment Specifications

The following specifications define the non-operating and storage environments:

• Temperature, ambient

– Minimum: -4 degrees Fahrenheit (-20 degrees Celsius)

– Maximum: 149 degrees Fahrenheit (65 degrees Celsius)

• Humidity, ambient (non-condensing)

– Minimum: 5%

– Maximum: 95%

• Altitude

– Minimum: Sea level

– Maximum: 10,000 feet (3,050 meters)

Features in Release 5.3.00This release includes the following new features:

• Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO

• Fractional T1/E1 Links for ATM Services

• Security Enhancements

• Remote IP Management Connection Enhancements

• Routing Enhancement for AXSM-XG Cards

• Platform Enhancements

• Cisco MGX 8830/B Enhancements

• RPM-PR Ethernet Back Card

Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DOCDMA2000 applications can use the Cisco MGX 8850 (PXM45) platform to aggregate traffic from several Base Transceiver Station (BTS) routers and transfer that traffic to an IP network. This application relies on the Multilink Point-to-Point Protocol (MLPPP), which carries traffic between the BTS routers and MPSM service modules. This capability was introduced in earlier releases; this release enhances the MLPPP features on the MPSM and RPM-XF cards.


OL-11771-03


The MLPPP feature for MPSM-16-T1E1 and MPSM-T3E3-155 cards includes:

• Support for multiple fractional point-to-point links on T1/E1 lines or paths. Each link can be part of a different bundle.

• Support for up to 8 PPP links per bundle.

• Support for up to 64 (MPSM-16-T1E1) or 256 (MPSM-T3E3-155) links per card.

• Support for up to 64 (MPSM-16-T1E1) or 128 (MPSM-T3E3-155) bundles per card.

• MLPPP load balancing for PPP links with unequal bandwidth.

• Support for the OC-3/STM1 back card in CDMA2000 solutions (MPSM-T3E3-155 only).

The RPM-XF supports:

• 2000 Context IDs (CIDS). Each CID uniquely identifies a flow, which may be a voice call or a data stream.

Summary of MLPPP Changes

Table 2 compares the features of Release 5.2 to Release 5.3:

MLPPP Configuration

The MLPPP features in Release 5.3 do not change the MLPPP configuration procedures and command syntax; only the valid ranges for links and bundles change (see Table 2). For more information about command updates, see the “Changed MPSM Commands” section on page 62.

For information about MLPPP configuration procedures and commands, see the following documents:

• Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2.

In the Provisioning Multilink PPP chapter, the new limits for bundle and link parameters apply.

• Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00

Table 2 MLPPP Enhancement Summary

Feature Card Release 5.2.00 Release 5.3.00

Multiple fractional links Both 1 link only 6 T1 or 8 E1

Links per bundle MPSM-16-T1E1 4 8

MPSM-T3E3-155 6 8

Load balancing Both Equal bandwidth only Equal or unequal

OC-3/STM1 MPSM-T3E3-155 T3/E3 only T3/E3 and OC-3/STM1

Context IDs Both 1000 flows 2000 flows

PPP links per card MPSM-16-T1E1 16 64

MPSM-T3E3-155 168 (84 in CR) 256

MLPPP bundles per card MPSM-16-T1E1 16 64

MPSM-T3E3-155 84 128


OL-11771-03


MLPPP Upgrade Considerations

Consider the following MLPPP characteristic when upgrading to software Release 5.3:

• Different speed PPP links on the same MLPPP bundle are not allowed in software Release 5.3.

Software Releases 5.1 and 5.2 permit different speed links, so existing bundles may exist with links that have mismatched speeds. After you upgrade to Release 5.3, the dspppplinks command still shows the mismatched links, but the links are down and the system logs the following error:

EM-7-EM_EVENT emRoot transactAddPppLink EM Event: Id:448e, Line#825:64kbps ppp link 23 cannot be added to the bundle having 56kbps links

To restore PPP link operation, delete the mismatched links and add links of equal speeds to the bundle.

• 64 Kbps PPP links on lines with alternate mark inversion (AMI) line coding are not allowed in software Release 5.3.

Software Releases 5.1 and 5.2 permit 64 Kbps links on lines with AMI coding, so your system may be configured with these links. After you upgrade to Release 5.3, the dspppplinks command still shows the links, but the links are down and the system logs the following error:

EM-7-EM_EVENT emRoot transactAddPppLink EM Event: Id:448e, Line#860:64Kbps PPP link "LinkNum" not supported on lines

with AMI line coding

To restore PPP link operation, delete the 64 Kbps links, change the line coding to b8zs, and then add the links back into the bundle.

• The maximum value for normalized PVC bandwidth (normpvcbw) of MLPPP bundles changes from 176603 to 88301 cps in software Release 5.3. When you upgrade to software Release 5.3, bundles with PVC bandwidth that exceed 88301 cps are automatically reduced to 88301 cps.

• The default normalized PVC bandwidth (normpvcbw) for a bundle with an E1 link changes from 8600 bps to 9200 bps in software Release 5.3. The default value for a bundle with T1 links is unchanged, and remains 8600 bps. In software Release 5.3, when a bundle is added, the normpvcbw is set to 8600. If the first link added to the bundle is E1, normpvcbw is modified to 9200 bps.

Bundles added before upgrading to software Release 5.3 have a default value of 8600 cps. For bundles with E1 links, modify the normpvcbw value manually using the cnfmpbundleparams command.

Fractional T1/E1 Links for ATM ServicesThe initial release of the MPSM-16-T1E1 card supported ATM services, but for full T1/E1 lines only. This release expands the ATM service capabilities to support both full and fractional T1/E1 ports.

Fractional T1/E1 Configuration

The configuration procedures for ATM services do not change for fractional T1/E1 ports. When you add a fractional T1E1 port, you specify the range of DS0s to use. The addport command has arguments to specify a range of DS0s, and the dspport command shows DS0 ranges. For more information about command updates, see the “Changed MPSM Commands” section on page 62.


OL-11771-03


For more information about ATM configuration procedures and commands, see the following documents:

• Cisco ATM and Frame Relay Services (MPSM-T3E3-155 and MPSM-16-T1E1) Configuration Guide and Command Reference for MGX Switches, Release 5.2.


Fractional T1/E1 Configuration Limitations

Fractional T1/E1 configurations have the following configuration restrictions:

• Virtual ports on fractional T1/E1 lines are not supported.

• Connecting fractional T1/E1 interfaces with V.35 and X.21 is not supported.

• Partition bandwidths cannot be less than 100 percent of the port rate.

• Cicso Wide Area Network Manager (CWM) inband configuration upload over a low bandwidth link is not supported. Without sufficient bandwidth, CWM may time out and never synchronize.

Fractional T1/E1 configurations have the following functional limitations:

• Each physical interface can be configured with only one NxDS0 port.

• A physical interface can be configured with one NxDS0 port for ATM service, or one NxDS0 port for Frame Relay service, but not both.

• The number of timeslots of an existing NxDS0 port cannot be changed using the cnfport command. Therefore, you cannot dynamically add additional DS0 timeslots to increase bandwidth.

• Network clock distribution protocol (NCDP) cannot distinguish the type of line a NNI trunk is using. This information is transparent to NCDP. Therefore, selecting the NXDS0 port as a NCDP clock source is not blocked by default. Use the cnfncdpport command on the PXM card to block the NxDS0 port from being used as a NCDP clock source. By default for a NNI trunk, this is not blocked.

• Integrated local management interface (ILMI) using about 5 percent of the port bandwidth. This limits the number of connections that can be supported on either side for ILMI autoconfiguration or address registration to succeed.

• For PNNI and service specific connection-oriented protocol (SSCOP), call setup and mutual status exchange for each connection require about 20 cells per second in bandwidth. Connection reroute or connection setup on a NxDS0 trunk with insufficient bandwidth for the number of connections supported can fail if SSCOP times out.

• With PNNI signaling enabled, you must configure the minimum bandwidth that PNNI requires. Otherwise, PNNI trunks may not come up. Use the dsppnctlvc command to display the required PNNI bandwidth.

• Extended permanent virtual connections (XPVC) using NxDS0 user-to-network interface (UNI) are not supported.


OL-11771-03


Security EnhancementsRelease 5.3.00 introduces the following security enhancements:

• For the PXM45—Secure File Transfer (SFTP)

• for the RPM-XF—Secure Shell (SSH)

SFTP and SSH Features

Cisco MGX switches currently support the following remote access applications and protocols:

• Telnet, FTP, and SSH on PXM45 controllers

• Telnet and FTP on RPM-XF and RPM-PR cards

This release adds SFTP to the PXM45 card and SSH to the RPM-XF card. SFTP is an alternative to FTP that provides for secure (and authenticated) file transfer between a PXM card and a remote host.

For more information about managing Telnet and SSH features, see the following:


– Managing Telnet Access Features section

– Starting and Managing Secure (SSH) Access Sessions Between Switches section

• Release Notes for Cisco MGX Route Processor Module (RPM-XF) Cisco IOS Release 12.4(6)T for PXM45-based Switches, Release 5.3.00

– Secure Shell (SSH) section

SFTP Limitations

The SFTP feature has the following limitations:

• Maximum of 4 simultaneous sessions

• Sessions have an infinite timeout

• Must use forward slash (/) for path names

• The following SFTP commands are not supported:

– chown

– chmod

– chgrp

– ln

– rename, with absolute filenames

– Symlink


OL-11771-03


Disabling Telnet and FTP

By default, the PXM45 permits unsecured access from Telnet and FTP clients, as well as secure access from SSH and SFTP clients. Option 16 of the cnfndparm command, along with option 15, disables unsecured Telnet and FTP access from remote hosts while permitting secure SFTP and SSH sessions.

If you plan to use SFTP and SSH on the PXM45, you should consider disabling FTP and Telnet access to improve security. Telnet and FTP transfer all user ID, password, and session management information between the client and the PXM45 using clear text. Clear (or unencrypted) text can be read by network analysis and snooping tools.

Initializing SFTP

Upgrading PXM software is not sufficient to initialize and enable the SFTP feature. You must initialize the sshd_config file and reset the MGX chassis. Because resetting a chassis can interrupt traffic, you should initialize SFTP before upgrading software so you do not need to reset it later.

To initialize SFTP, perform the following steps:

Step 1 Initiate an FTP session with the PXM card.

Step 2 Change to the F:/SSHD directory.

Step 3 Get the sshd_conf file from the F:/SSHD directory.

Step 4 Append the line subsystem sftp sftp to the file.

Step 5 Put the sshd_conf file into the F:/SSHD directory.

Step 6 Proceed with the normal software upgrade procedure. Alternatively, enter the resetsys command to reset the chassis.

Note The resetsys command interrupts all traffic on the MGX chassis.

Remote IP Management Connection EnhancementsYou can manage a Cisco MGX 8850 node directly from an Ethernet or console port on the PXM, or you can configure a remote path to the PXM through a service module or route processor module. The following management paths are supported in earlier releases:

• AXSM or MPSM to PXM

• RPM-XF or RPM-PR to PXM

Option 15 Type yes to disable Telnet access to this switch. Type no to enable Telnet access.

Default: no (Telnet access is enabled)

Option 16 Type yes to disable unsecured Telnet or FTP access to this switch. Changing this option from no to yes automatically changes Option 15 to yes. Changing from yes to no has no affect on Option 15.

Default: no (Unsecured access is enabled)


OL-11771-03


Earlier releases supported intranode connections only, and you could only have one PVC between an RPM and PXM. Release 5.3.00 enhances the ATM0 feature to internode connections, where an RPM on one MGX switch connects to PXMs on other MGX switches using PNNI. And now you can manage multiple PXMs from a single RPM.

Management Connection Limitations

The IP addresses of hosts accessing the Cisco MGX 8850 node are stored in a RAM cache. Because this cache has a limit of 50 entries, only 50 IP hosts can actively access the node at one time. New IP hosts are blocked until the cache clears (as result of inactivity from some hosts) to make room for new entries.

Multiple RPMs can connect to the same PXM, but each RPM can have only one connection to the PXM. This is because the PXM has a single ATM0 address.

Note If you are connected to the MGX switch using the RPM and accidentally delete the SPVC, the connection drops. To restore RPM access, you must re-add the SPVC using the console port or Ethernet port.

Note The clrallcnf, clrcnf, or clrsmcnf commands clear management connections. To restore RPM access, you must reconfigure the RPM and PXM cards for IP connectivity using the console port or Ethernet port.

Configuring an RPM Management Connection

The following quick start procedure summarizes the RPM configuration procedure. This procedure assumes the RPM already has a switch partition configured for the management connection.

Command Action

Step 1 switch partition Create and configure a partition for switch 1, as necessary.

Step 2 interface sw1.<subif> point-to-point

Configure a point-to-point subinterface on switch 1.

Step 3 ip address <address> <mask> Assign an IP address to the switch subinterface. This IP address must be in the same subnet as the ATM0 port of the PXM card.

Step 4 pvc <vpi>/<vci>

ubr <rate>

Configure a PVC on the switch subinterface.

Note Specify 0 for the VPI.

Note In Release 5.3, the rate is configurable.

Step 5 switch connection vcc <vpi> <vci> master remote

Add a slave endpoint to the switch subinterface.

Step 6 show switch connection vcc <vpi> <vci>

Display the slave connection parameters, which include the NSAP address.


OL-11771-03


The following quick start procedure summarizes the PXM configuration procedure.

Management Configuration—Example

This example shows how to configure a management connection between an RPM-XF on one switch and the PXM on another switch. In this example, the RPM-XF switch partition and the PXM ATM0 interface are already available.

The following example shows how to configure the RPM-XF switch interface, add a slave connection, and display the NSAP address.

Router(config)#interface switch1.100 point-to-pointRouter(config-subif)#ip address 10.10.10.200 255.255.255.0Router(config-subif)#pvc 0/100Router(config-if-atm-vc)#ubr 1544Router(config-if-atm-vc)#switch connection vcc 0 100 master remoteRouter(config-if-swconn)#endRouter#show switch connection vcc 0 100----------------------------------------------------------Alarm state : No alarm Local Sub-Interface : 100Local VPI : 0Local VCI : 100Remote NSAP address : default Local NSAP address : 47.0091810001040000ABCD7777.000001011802.00Remote VPI : 0Remote VCI : 0

Command Action

Step 1 dspndparm Verify that the PXM is configured for ATM0 as a switch management interface.

Step 2 ipifconfig atm0 <address> <mask>

Assign an IP address to the ATM0 port, as necessary. This IP address must be in the same subnet as the switch interface on the RPM card.

Step 3 svcifconfig atm0 remote <nsap> pvc <vpi>.<vci>

Add a master connection endpoint. Use the NSAP address and VPI/VCI of the slave endpoint.

Step 4 dspsvcif Verify that the connection is up.

Step 5 routeshow Verify that the RPM IP address is displayed in the route table.


OL-11771-03


The following example shows how to configure the ATM0 interface of the PXM card, add a master connection to the RPM-XF, and verify that the connection is state is up. The NSAP address and VPI/VCI entered are the values previously displayed at the RPM-XF.

LA.8.PXM.a > ipifconfig atm0 10.10.10.144 netmask 255.255.255.0LA.8.PXM.a > svcifconfig atm0 remote 47.0091810001040000ABCD7777.000001011802.00 pvc 0.100LA.8.PXM.a > dspsvcifM8850_LA System Rev: 05.02 Apr. 25, 2006 16:36:38 PSTMGX8850 Node Alarm: NONEIP CONNECTIVITY SVC CACHE--------------------------------------------------------------------atm (unit number 0): Remote AESA: 47.0091.8100.0104.0000.abcd.7777.0000.0101.1802.00 SPVC VPI.VCI: 0.100 (PCR=3642 cps) Flags: (0x6) ATMARP,LLCENCAP State: (0x1) UP RxLCN: 1505 TxLCN: 1505 LCNindex: 766 LCNcallid: 0x80000001 Input Frames: 1 Output Frames: 1 Input Errors: 0 Output Errors: 0 Input ArpReq: 0 Output ArpReq: 0 Input ArpRply: 0 Output ArpRply: 0 Input InArpReq: 0 Output InArpReq: 0 Input InArpRply: 1 Output InArpRply: 0

Routing Enhancement for AXSM-XG CardsExtended link management interface (XLMI) and enhanced network-network interface (ENNI) are protocols that connect broadband packet exchange (BPX)-based AutoRoute networks to Cisco MGX 8850 (PXM45)-based PNNI networks. This release extends this capability to the following AXSM-XG cards:

• AXSM-16-155-XG

• AXSM-8-622-XG

For compatible back cards, see Table 9.

For more information about XLMI/ENNI configuration procedures and commands, see the XLMI Link Configuration Quickstart section in the following document:

• Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2


OL-11771-03


Platform EnhancementsThis release adds the following MGX platform enhancements.

• Database server/client enhancement—The server automatically copies database tables to the new directory for a release.

• Software FPGA upgrade on PXM45/C—Use this feature to upgrade hardware (Field Programmable Gate Array) FPGA images without introducing new hardware versions. This simplifies the process of adding or changing features and can reduce hardware costs for both Cisco and customers.

• PXM to MPSM QoS enhancement—Currently, traffic sent to the MPSM-T3E3-155 and MPSM-16-T1/E1 cards is managed by the class of service only. For example, the CBR traffic class is always given priority over the VBR.RT traffic class, even if VBR.RT connections are committed and data received is within the sustainable cell rate (SCR) limit.

Through this QoS enhancement, the PXM QE1210 is programmed using information from the MPSM so it can manage traffic dynamically based on the committed rate of the connections and interface policy.

Cisco MGX 8830/B EnhancementsThe Cisco MGX 8830/B is a 7-double-height horizontal slot chassis, where slots 1 and 2 are reserved for the PXM. The Cisco MGX 8830/B (PXM45/C) now supports the RPM-PR and RPM-XF cards.


OL-11771-03


RPM-PR Ethernet Back CardThe MGX-RJ45-5-ETH is a single-height back card for the RPM-PR that provides five RJ-45 connectors for Gigabit Ethernet, Fast Ethernet, or Ethernet lines. Figure 1 shows the MGX-RJ45-5-ETH faceplate.

Figure 1 MGX-RJ45-5-ETH Back Card

1 ENABLE LED

• Green—The back card is active.

• Off—The back card is not active.

3 Port 0 status LED

• Green

– Data present (flashing).

– The link is up.

2 Port 0 speed LED

• Orange—1000 Mbps.

• Green—100 Mbps.

• Off—10 Mbps

1495

37

PORT

1

ENBL

MGXRJ45

5-ETH

PORT

2

PORT

3

PORT

4

PORT

5

12

3


OL-11771-03


Table 3 lists the maximum cable length for each of the supported speeds on the MGX-RJ45-5-ETH card.

Features in Release 5.2.10Release 5.2.10 adds Unique Device Identifier (UDI) compliance for the Cisco MGX 8830/B chassis and backplane.

Features in Release 5.2.00Release 5.2.00 has the following features:

• MGX-VXSM-T3 Card

• AXSM-8-622-XG Card

• Graceful Upgrades to AXSM-XG Cards

• Multilink PPP on the MPSM-T3E3-155 Card

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

• Mobile PNNI Support

• Compression and Multiplexing Support for RPM-PR Cards

MGX-VXSM-T3 CardRelease 5.2.00 introduced a third VXSM card for the support of T3 lines. The card consists of a front card with six T3 ports and a half height back card with three T3 ports. The front card can be configured with either one back card or two back cards.

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

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

• Independent channelization of each line.

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

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

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

Table 3 MGX-RJ45-5-ETH Card Supported Speeds and Maximum Cable Lengths

Configuration Interface Speed Maximum Cable Length

10 Mbs Up to 100 meters




OL-11771-03


• Trap generation to CWM signals configuration changes and alarm status

• VSI support for PNNI and MPLS controllers

• Up to 128 total logical interfaces

• Up to 16 Classes of Service per logical interface

• Trunk and port interfaces on same card

• Virtual trunk support

• Resource Management

– Interface resource partitioning among PNNI and MPLS controllers

– Dynamic resource partitioning

– Ingress connection admission control (CAC) of logical ports based on maximum chassis slot bandwidth

• Connection Management

– Up to 128K connections (VCs + VPs)

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

– SVC/SVP, SPVC/SPVP, and LVC

– Symmetric and asymmetric connections

– VC merge for AAL 5 traffic

– Point to multipoint connections

• Traffic Management

– Enhanced CAC support

– Congestion management

– Per VC/VP traffic policing

– Per VC/VP traffic shaping

– ABR with VS/VD

• Operation, Administration, and Maintenance (OAM) support—Compliance with ITU-T I.610

• ILMI—Compliance with ATM Forum 4.0

• Statistics—Similar to AXSM-E

• Redundancy

– Card redundancy using hot standby

– APS backup with 1:1 and 1+1, inter-card and intracard, and facility protection with 1 front card and 2 back cards

• Online and offline diagnostics

• Feeder support

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

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

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


OL-11771-03


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

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

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

• The AXSM-XG does not support AutoRoute CoS queues

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

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

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

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

For more information about the upgrade procedure, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00.

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

• Support for MLPPP

• PPPmux on a MLPPP bundle basis

• Interworking between MLPPP and PPPoATM

• NxDS0 and DS1 PPP links

• Maximum of 84 PPP links per card

• Maximum of 84 MLPPP bundles per card

• Maximum of 6 PPP links per MLPPP bundle

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

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

• Support for three strict priority queues

• Support for the CDMA2000 and EV-DO

• 1:1 hot standby front card redundancy

• Operational load management


OL-11771-03


The MLPPP feature has the following restriction:

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

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

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

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

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

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

Compression and Multiplexing Support for RPM-PR CardsThe MGX-RPM-1FE-CP (one-port, Fast Ethernet-Co-processor) back card is a Cisco MGX 8850/RPM-PR back card that off-loads the following processes from the Route Processor Module (RPM-PR):

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

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

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

For more information, refer to:

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


OL-11771-03


Features in Release 5.1.20Release 5.1.20 supports Evolution-Data Optimized (EV-DO) traffic on the MPSM-16-T1E1. EV-DO is a high-speed data overlay for CDMA2000, where the Cisco MGX 8850 operates as the aggregation node:

• Multilink PPP Feature for CDMA2000 and EV-DO, page 33

Features in Release 5.1.00This section contains the descriptions of the following new features in Release 5.1.00:

• MPSM-16-T1E1 Card, page 30

• MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics, page 33

• Private Network Node Interface Current Route Feature, page 33

• PNNI Product Enhancements, page 35

• PXM1E OAM Enhancement, page 36

MPSM-16-T1E1 CardThe MPSM-16-T1E1 is a single-height front card that accommodates one single-height back card and fits into a slot in the upper or lower bay of the following chassis systems:

• Cisco MGX 8850 and Cisco MGX 8850/B switches

• Cisco MGX 8830 and Cisco MGX 8830/B switches

The MPSM-16-T1E1 front card supports 16 ports with T1/E1 capabilities, depending upon which back card is installed. Each line can be channelized or unchannelized.

Limitation: Consolidated Link Layer Management for Frame Relay is not supported in this release.

Operational Modes

The MPSM-16-T1E1 supports two software modes:

• ATM and Frame Relay services

• Multilink PPP services only

During initial card startup, boot into either one mode or the other.

Supported Features

This section lists the features that are supported on the MPSM-16-T1E1 card.

Supported Services

The following services are supported:

• Frame Relay

• ATM

• Inverse Multiplexing for ATM (IMA)


OL-11771-03


• Multilink PPP (MLPPP)

• Any Service Any Port

General Features

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

• Physical interfaces configurable as channelized or unchannelized ports for 16 T1 or E1 interfaces.

• Fault management and performance management for T1 and E1 interfaces.

• 1:1 hot standby card redundancy (Requires 1:1 redundancy back cards and Y-cable).

• 1:N cold standby card redundancy (Requires 1:N redundancy back cards and RCON connector).

• Standard Cisco MGX RAS features.

• Onboard BERT support for NxDS0 and T1/E1 interfaces.

• Any Service Any Port (ASAP).

• Optional software features enabled through feature licenses.

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

• Support for card and port service class templates.

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

• Support for FR-FR, FR-ATM, ATM-FR, ATM-VISM, and ATM-CE SPVC connection types, where one of the end-points resides on the MPSM-16-T1E1 card.

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

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

• Support for OAM fault management.

• Statistics collection and upload to Cisco Wan Manager (CWM).

• Configuration upload to CWM.

ATM Features

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

• Manages up to 16 T1/E1 worth of ATM traffic.

• T1 and E1 ATM interfaces.

• ATM trunking.

• VPCs and VCCs.

• Egress VC shaping.

• ABR VS/VD with support for external ABR segment.

• Integrated local management interface (ILMI) on all ATM interfaces.

• Maximum of 32 ATM UNI/NNI/VUNI/VNNI/EVUNI/EVNNI ports with signaling.

• Maximum of 2000 ATM connections.

• ATM traffic management features (includes ABR VS/VD).

• VCC/VPC shaping.


OL-11771-03


IMA Features

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

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

• Support for up to 16 IMA groups.

• Support for both T1 and E1 IMA links (T1 and E1 cannot be mixed in the same IMA group).

• Maximum of 8 links per IMA group.

• Differential delay supported is 275 ms for T1 and 220 ms for E1.

• Support for CTC and ITC clocking modes.

Frame Relay Features

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

• Supports the bandwidth of 16 T1/E1 lines.

• Ports can be added on T1/E1 lines or NxDS0 channels in T1/E1 lines.

• Maximum Frame Relay port bandwidth is 1.984 Mbps (E1 line with 31 time slots).

• Support for 56 Kbps ports.

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

• Maximum of 2000 Frame Relay connections.

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

• Ingress cut through mode of frame processing (No waiting for the complete frame to arrive. Frame processing and conversion to ATM cells starts as soon as header information is available).

• Maximum frame size supported is 4510 bytes.

• Support for 2-byte Frame Relay header.

• Ratio based egress servicing.

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

• LMI and Enhanced LMI on all Frame Relay interfaces.

• Frame Relay traffic management features.

MLPPP Features

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

• PPPmux on a MLPPP bundle basis.

• Interworking between PPP and PPPoATM.

• Maximum of 16 MLPPP bundles.

• Maximum of 4 PPP links per MLPPP bundle.

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

• NxDS0 and T1/E1 PPP links.

• 1 PPP link per physical line.

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

• Support for 4 strict priority queues.


OL-11771-03


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

• 1:N cold standby front card redundancy supported.

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

• Licensing of the supported features

Multilink PPP Feature for CDMA2000 and EV-DO

The MPSM-16-T1E1 implements Multilink PPP, which is a key protocol in a larger application defined by CDMA2000. In this application, the Cisco MGX 8850 (PXM45) aggregates traffic from several BTS site routers (MWR) and transfers that traffic to an IP network. The aggregation point in the Cisco MGX 8850 (PXM45) is the RPM-XF. Traffic from all of the BTS routers are transported over PPP links (typically on T1/E1 links) and brought into the Cisco MGX 8850 (PXM45) through an MPSM-16-T1E1 card. The MPSM-16-T1E1 transforms the PPP payload into AAL5 cells, which it sends to the RPM-XF using ciscoPPPoAAL5 encapsulation.

With growth in traffic in the CDMA2000 application, you might need to add additional T1/E1 links between the MWR and the MPSM-16-T1E1. The MLPPP feature simplifies the process of adding incremental bandwidth because it can aggregate capacity of individual T1/E1 lines. Because the IP payloads are small (typically voice) and the overhead associated with PPP (MLPPP) packets increases with smaller payloads, PPPMUX functionality is utilized on the MPSM-16-T1E1. In EV-DO, multiplexing is not used.

The connection between MPSM and RPM-XF is setup as a PVC connection. The bandwidth of this PVC depends on the number of operation PPP links on an MP bundle. RPM-XF terminates the PPPoAAL5 data and routes the IP traffic to the backbone IP network.

MPSM-155-T3E3 and MPSM-16-T1E1 Online DiagnosticsThe online diagnostic tests run on regular intervals for both on the active and standby state of the MPSM cards to check the health of the devices and data paths. The online diagnostics test the following devices and data paths:

• Data path from the CPU on the MPSM to the CBC slave loopback on the MPSM through Winpath 0

• Data path from the CPU on MPSM to the CBC master loopback on the PXM through Winpath 1

• Winpath memory access test (packet, parameter, host memory)

• Write/read memory access test for internal devices

• Validate front card NVRAM checksum

• Validate flash checksum

Private Network Node Interface Current Route FeatureThe Current Route feature provides the path information for active Point-to-Point (P2P) SPVCs/SPVPs master-end connections. The path information contains the lowest level physical node and egress trunk information of the path on which the connection is currently routed.

This feature uses the ATM standards based connTrace message to obtain the current route information. CWM uses the configuration upload file mechanism to request available path information of connections on a periodic or an on-demand basis.


OL-11771-03


This feature works in single peer group and multiple peer group networks. The current path can be used by the network administrators and planners to engineer the trunk use and to direct how connections should be routed.

Operational and Redundancy Limitations

The current route feature has the following operational limitations:

• Point-to-multipoint calls are not supported.

• Only SPVC/SPVP connections are supported. CWM does not manage SVC/SVP connections.

• Master ended connections have the current route information. Slave ended connections do not have this information.

• The configuration upload file contains a snapshot of the current route information at the time that the switch receives a configuration upload request from CWM. Therefore, the snapshot might not contain the latest information, and connection trace information that the switch receives after the file is created is not included in the file.

• If congestion occurs on a node, the connTrace message sent by the CLI and by the Current Route feature is dropped. The two connTrace messages are not distinguishable. This limitation also applies to connTrace ACK messages that are received on a congested node.

• After changing a node ID, disable and then re-enable the current route feature on each node in the network using the cnfndcurrte command.

This command flushes all existing current route information and starts collecting new information. After disabling the current route feature, wait at least 9 seconds (the time-out period for a connTrace message) before re-enabling it. This inhibits processing of stale conn-trace messages.

• The connection path information for a connection traversing more than 20 nodes is not stored in the current route path table. Therefore, such connections do not have current route information.

• The current route path does not include the destination termination port (normally slave endpoint UNI port). The destination port is set to zero in the current route path, which is similar to preferred route.

The current route feature has the following redundancy limitations:

• The current route feature provides redundancy. However, because the current route must not reduce routing performance, some connections might not have redundant current route information on the standby PXM.

For those connections that do not have redundant current route information at the time of a switchcc, their current route information is obtained through the normal scanning on the active card when the old standby becomes active.

• After a standby PXM card is inserted and reset, the active card sends the current route information to the standby card only after its state changes from Init to Standby. This avoids increasing the time it takes for the redundant card to come up to the Standby state, ready for switchcc.

The Standby state is not redundant until the current route update is completed. Therefore, a switchcc that occurs before all current route information is sent to the redundant card results in some connections not having current route information on the newly active card. The current route information for those connections is obtained during the normal current route scanning and processing.

• When inserting or resetting the standby PXM, enter the command dspndcurrte and verify that Bulk update is complete before performing a switchcc.


OL-11771-03


Feature Specifications

The current route feature has the following limitations:

• A maximum of 10K path entries per node are supported.

• A maximum of 5K node ID entries per node are supported.

• A maximum of 2K ports on PXM1E systems are supported when current route is enabled.

An attempt to enable the current route feature on a node which has more than 2K ports is not allowed and results in error. If the current route feature is enabled and more than 2K ports are subsequently added, this feature or other applications might not work properly.

• A maximum of 100K connections are supported PXM45/B systems when current route is enabled.

An attempt to enable current route on a node which has more than 100K connections results in error. If the current route feature is enabled and more than 100K connections are subsequently added, this feature or other applications might not work properly.

PNNI Product EnhancementsThe Link Selection enhancement adds functionality to parallel links to which link selection criteria is provisioned to minAW (minAWlinks). Activate this feature through the CLI. If these enhancements are not activated, the existing ‘link selection’ behavior is used.

Table 4 lists PNNI product enhancement requests incorporated in this release.

Table 4 PNNI Product Enhancements

PER ID Enhancement Description

PER 5672 SVCC-RCC connection configuration

This enhancement introduces a command (cnfpnni-svcc-rcc-param) to configure the connection parameters associated with SVCC-RCC connections at each level of the PNNI hierarchy.

PER 8281 Path bypass selection configuration

In a complex node multiple peer group topology, the path that has the highest available cell rate (AvCR) is advertised as the bypass. Typically this path has higher cost, so the calls routed over the pass bypass might always take the worst path. This enhancement adds an option to the cnfpnni-routing-policy command to specify the criteria for bypass path selection.

PER 8282 Administrative Weigh (AW) Pruning

Currently a trunk is included in the best path selection even if it has a single cell per second of AvCR. This enhancement introduces an AvCR threshold parameter to the cnfpnni-routing-policy command so that trunks with BW below the threshold are excluded from the best path search.


OL-11771-03


PXM1E OAM EnhancementThe PXM1E processes the following OAM loopback cells:

• End-to-end OAM loopback cells—Used for background connection continuity verification. These cells might be sent by a VISM card or router.

• Segment OAM loopback cells—Used for diagnostic testing between segment endpoints. These cells are sent for the following CLI commands: tstdelay, tstconsegep, and tstpndelay.

This release moves the task of extracting and injecting OAM loopback cells at the PXM1E from the Atlas to the QE1210. Unlike with Atlas, the QE1210 can distinguish between segment and end-to-end OAM loopback cells. The QE1210 extracts only the segment OAM loopback cells, while transparently passing the end-to-end OAM loopback cells.

Because the end-to-end OAM loopback cells no longer require software processing, the previous limitations for the OAM loopback cell rate on the PXM1E no longer apply. These cells are now processed in the QE1210 hardware and are limited only by the available line bandwidth.

Each PXM1E segment endpoint has a polling-induced queue extraction delay of up to 10 ms for a segment OAM loopback cell. This delay is not imposed on end-to-end cells or segment cells at nonsegment endpoints.

PER 8287 Consistent PNNI Link Selection

Allows application of the same link selection mechanism to connections of all service categories (ABR, UBR, CBR, and VBR) on minAW links.

Allows provisioning epsilon-equal AW parallel links among the minAW parallel links between two switches. The switch calculates the epsilon value based on user input.

If epsilon-equal AW parallel links exist between two switches along the selected shortest path, link selection applies. For epsilon-equal AW parallel links, the secondary link selection criteria is maxAvCR. If all links have the same AvCR, the connections are routed according to load balance criteria.

PER 8540 Preferred Route Enhancements

The cnfndidrtes command has a new parameter for indicating that the same node is being configured and that the preferred route status should not change. A connection that was on a preferred route before the change would not be groomed by route optimization.

PER 8660 Link Selection Enhancements for MPG

MPG (multipeer group) Pref Rt Conns

PER 8807 Routing Policy Enhancements

This enhancement adds a parameter value to the cnfpnni-routing-policy command that selects from equal administrative weight (AW) paths using the number of minimum hops. If multiple epsilon-equal AW paths with the same minimum-hops exist, a second load balance parameter specifies the tie break criteria.

Table 4 PNNI Product Enhancements (continued)

PER ID Enhancement Description


OL-11771-03

System Requirements

System RequirementsThis section describes software compatible with this release and lists the supported hardware.

Software/Firmware Compatibility MatrixTable 5 lists Cisco WAN or Cisco IOS Software products that are compatible with Release 5.4.30.

Table 5 Release 5.4.30 Compatibility Matrix

Switch or Component Compatible Software Version

Cisco MGX 8230 (PXM1)



MGX 1.3.18

MGX 1.3.16

MGX 1.3.14

MGX 1.3.12

Cisco MGX 8830/B (PXM45/C) MGX 5.4.30

MGX 5.4.10

MGX 5.4.00

MGX 5.3.20

MGX 5.3.00

MGX 5.2.10

Cisco MGX 8830 (PXM1E)

Cisco MGX 8830/B (PXM1E)

Cisco MGX 8850 (PXM1E and PXM45)

Cisco MGX 8850/B (PXM1E and PXM45)


MGX 5.4.30

MGX 5.4.10

MGX 5.4.00

MGX 5.3.20

MGX 5.3.00

MGX 5.2.10

BPX Switch Software Switch Software 9.4.12

BXM firmware MFZ

Cisco WAN Manager 15.4.00

15.3.00P2

15.3.00

15.1.50P2

Cisco MGX 8220 Shelf MGX 8220 5.0.20

Cisco SES PNNI 4.0.15

3.0.25


OL-11771-03

System Requirements

MGX and RPM Software Version Compatibility MatrixTable 6 lists the software that is compatible for use in a switch running Release 5.4.30 software.

Cisco IOS RPM-PR 12.4(14)T1

12.4(6)T5

12.4(6)T1

12.3(11)T8

Cisco IOS RPM-XF 12.4(15)T5

12.4(15)T1

12.4(6)T5

12.4(6)T1

12.3(11)T8

VISM-PR 3.3.30

3.3.25

3.3.20

VXSM 5.4.20.201

5.4.00

5.3.10

5.3.00

5.2.10

Table 5 Release 5.4.30 Compatibility Matrix (continued)

Switch or Component Compatible Software Version

Table 6 MGX and RPM Software Version Compatibility Matrix

Board Pair Boot Software Runtime Software

PXM45/B pxm45_005.004.030.200_bt.fw pxm45_005.004.030.200_mgx.fw

PXM45/C

PXM45/C MGX 8830/B chassis pxm45_005.004.030.200_bt.fw pxm45_005.004.030.200_m30.fw

PXM1E-4-155 MGX 8850 (PXM1E) chassis

pxm1e_005.004.030.200_bt.fw pxm1e_005.004.030.200_mgx.fw

PXM1E-8-155 MGX 8850 (PXM1E) chassis

PXM1E-8-T3E3 MGX 8850 (PXM1E) chassis

PXM1E-COMBO MGX 8850 (PXM1E) chassis

PXM1E-8-155


OL-11771-03

System Requirements

PXM1E-4-155 MGX 8830 chassis pxm1e_005.004.030.200_bt.fw pxm1e_005.004.030.200_m30.fw

PXM1E-8-T3E3 MGX 8830 chassis

PXM1E-8-155 MGX 8830 chassis

PXM1E-COMBO MGX 8830 chassis

AXSM-1-2488 axsm_005.004.030.200_bt.fw axsm_005.004.030.200.fw

AXSM-16-155

AXSM-4-622

AXSM-16-T3/E3

AXSM-1-2488/B

AXSM-16-155/B

AXSM-4-622/B

AXSM-16-T3/E3/B

AXSM-2-622-E axsme_005.004.030.200_bt.fw axsme_005.004.030.200.fw

AXSM-8-155-E

AXSM-16-T3E3-E

AXSM-32-T1E1-E

AXSM-16-155-XG axsmxg_005.004.031.200_bt.fw axsmxg_005.004.031.200.fw

AXSM-8-622-XG

AXSM-4-2488-XG

AXSM-1-9953-XG

MPSM-16-T1E1 mpsm16_t1e1_005.004.030.200_bt.fw mpsm16_t1e1_005.004.030.200.fw

MPSM-16-T1E1-PPP mpsm16t1e1ppp_005.004.030.200.fw

MPSM-T3E3-155 mpsm155_005.004.030.200_bt.fw mpsm155_005.004.030.200.fw

MPSM-T3E3-155-PPP mpsm155ppp_005.004.030.200.fw

MPSM-8-T1E1 mpsm_t1e1_030.004.030.200_bt.fw mpsm_t1e1_030.004.030.200.fw

MGX-SRME N/A (obtains from PXM) N/A (obtains from PXM)

MGX-SRME/B N/A (obtains from PXM) N/A (obtains from PXM)

SRM3T3/C N/A (obtains from PXM) N/A (obtains from PXM)

AX-CESM-8E1 cesm_8t1e1_CE8_BT_1.0.02.fw cesm_8t1e1_022.004.030.200.fw

AX-CESM-8T1

MGX-CESM-8T1/B

MGX-AUSM-8T1/B ausm_8t1e1_AU8_BT_1.0.02.fw ausm_8t1e1_022.004.030.200.fw

MGX-AUSM-8E1/B

Table 6 MGX and RPM Software Version Compatibility Matrix (continued)



OL-11771-03

System Requirements

SNMP MIB ReleaseThe SNMP MIB file for Release 5.4.30 is mgx8850rel5400mib.tar.

Note SNMP user guides are replaced by the online MIB tool athttp://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp

Supported HardwareThis section lists:

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

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

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

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

AX-FRSM-8T1 frsm_8t1e1_FR8_BT_1.0.06.fw frsm_8t1e1_022.004.030.200.fw

AX-FRSM-8E1

AX-FRSM-8T1-C

AX-FRSM-8E1-C

MGX-FRSM-HS2/B frsm_vhs_VHS_BT_1.0.07.fw frsm_vhs_022.004.030.200.fw

MGX-FRSM-2CT3

MGX-FRSM-2T3E3

MGX-RPM-PR-256 rpm-boot-mz.124-6.T5 rpm-js-mz.124-6.T5

MGX-RPM-PR-512

MGX-RPM-XF-512 rpmxf-boot-mz.124-15.T5 rpmxf-k9p12-mz.124-15.T5

(Crypto image)

rpmxf-p12-mz.124-15.T5

(non-Crypto image)

MGX-VXSM-155 vxsm_005.004.020.201_bt.fw vxsm_005.054.020.201.fw

(CALEA image)

vxsm_005.004.020.201.fw

(non-CALEA image)

MGX-VXSM-T3

MGX-VXSM-T1E1

MGX-VISM-PR-8T1 vism_8t1e1_VI8_BT_3.2.00.fw vism-8t1e1-003.053.030.200.fw

(CALEA image)

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

MGX-VISM-PR-8E1

Table 6 MGX and RPM Software Version Compatibility Matrix (continued)



OL-11771-03

System Requirements

Hardware in Release 5.4.30

Release 5.4.30 introduces no new hardware.



Release 5.3.20 did not introduce any new hardware.

Release 5.3.10 introduced the following PXM45/C hardware:

PXM-HDV—Back card with 2000-MB hard disk partition

Release 5.3.00 introduced the following RPM-PR back card:

MGX-RJ45-5-ETH—5-port Ethernet back card

Product IDs, Card Types, and APS Connectors

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

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

Front Card Type

Minimum 800 Part Number and Revision

Back Card Types

APSCon


MGX 8850 and 8850/BPXM45

MGX 8850 and 8850/BPXM1E

MGX 8830/BPXM45


MGX 8950PXM45

PXM45/C 800-20217-04-A0

PXM-HDV — 800-28566-01 x — x — x

PXM-HD — 800-05052-03-A0

PXM-UI-S3/B — 800-21557-01-A0

PXM45/B 800-09266-04-A0

PXM-HD — 800-05052-03-A0

x — — — x

PXM-UI-S3 — 800-05787-02-A0

PXM1E-8-155 800-21686-05-A0

SFP-8-155 Yes 800-21518-03-A0

— x — x —

SMFIR-1-155-SFP

Yes 10-1283-01-A0

SMFLR-1-155-SFP

Yes 10-1280-01-A0

MMF-1-155-SFP

Yes 10-1308-01-A0

PXM-UI-S3/B — 800-21557-01-A0


OL-11771-03

System Requirements

PXM1E-4-155 800-18588-03-A0

MMF-4-155/C Yes 1

800-07408-02-A0

— x — x —

SMFIR-4-155/C

Yes 1

800-07108-02-A0

SMFLR-4-155/C

Yes

1800-07409-02-A0

PXM-UI-S3/B — 800-21557-01-A0

PXM1E-8-T3E3 800-18590-03-A0

SMB-8-T3 — 800-05029-02-A0

— x — x —

SMB-8-E3 — 800-04093-02-A0

PXM-UI-S3/B — 800-21557-01-A0

PXM1E-16-T1E1 800-18658-04-A0

MCC-16-E1 — 800-19853-02-A0

— x — x —

RBBN-16-T1E1

— 800-21805-03-A0

PXM-UI-S3/B — 800-21557-01-A0

PXM1E-T3E3-155

Also referred to as

PXM1E-COMBO

800-18604-03-A0

MGX-T3E3-155

— 800-18698-02-A0

— x — x —

SMFIR-1-155-SFP

— 10-1283-01-A0

SMFLR-1-155-SFP

— 10-1280-01-A

MMF-1-155-SFP

— 10-1308-01-A0

PXM-UI-S3/B — 800-21557-01-A0

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

Table 7 MGX Chassis, Card, and APS Configurations Part 1 (continued)

Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45

XM-60 800-04706-06-A0

— — — — — — — x

MGX-APS-CON 800-05307-01-A0

— — — x — — — —

MGX-8850-APS-CON

800-20640-01-A0

— — — x x — — —

MGX-8830-APS-CON

800-05308-02 — — — — — x x —

MGX-8950-APS-CON

800-15308-01-A0

— — — — — — — x

MPSM-T3E3-155 800-23005-06-A0

SFP-2-155 Yes 800-23170-02-A0

x x x x —

BNC-3-T3E3 — 800-23142-04-A0

SMB-2-155-EL Yes 800-23171-03-A0

MPSM-8-T1E1 800-24473-07-A0

AX-RJ48-8T1 — 800-02286-01-A0

x x x x —

AX-R-RJ48-8T1

— 800-02288-01-A0

AX-RJ48-8E1 — 800-02408-01-A0

AX-R-RJ48-8E1

— 800-02409-01-A0

AX-SMB-8E1 — 800-02287-01-A0

AX-R-SMB-8E1

— 800-02410-01-A0

MPSM-16-T1E1 800-22339-08 RBBN-16-T1E1-1N

— 800-23091-03 x (/B chassis only)

x (/B chassis only)

x1 x1 —

MCC-16-E1-1N

— 800-23135-02

RED-16-T1E1 — 800-23092-04

MCC-16-E1 — 800-19853-03 x x x x —

RBBN-16-T1E1

— 800-21805-04


OL-11771-03

System Requirements

RCON-1TO5-8850 800-23094-03 — — — x (/B chassis only)

x (/B chassis only)

— —

RCON-1TO3-8850 800-23196-01 — — — x (/B chassis only)

x (/B chassis only)

— — —

RCON-1TO3-8830 800-23197-01 — — — — — x x —

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


Front Card Type


Back Card Types

APSCon

Minimum. 800 Part Number and Revision



MGX 8830/BPXM45


MGX 8950PXM45

AXSM-1-9953-XG 800-07365-06-A0

SMFSR-1-9953 — 800-08237-06-A0

— — — — x

SMFIR-1-9953 — 800-08246-06-A0

SMFLR-1-9953 — 800-08247-06-A0

AXSM-4-2488-XG 800-16987-04-A0

SMF-4-2488-SFP

— 800-19913-04-A0

— — — — x

SMFSR-1-2488-SFP

10-1421-03

SMFLR-1-2488-SFP

10-1742-01

AXSM-1-2488 800-05795-05-A0

SMFSR-1-2488 Yes 800-05490-05-A0

x — — — —

SMFLR-1-2488 Yes 800-06635-04-A0

SMFXLR-1-2488

Yes 800-05793-05-A0


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements

AXSM-1-2488/B 800-07983-02-A0

SMFSR-1-2488/B

Yes 800-07255-01-A0

x — — — x

SMFLR-1-2488/B

Yes 800-08847-01-A0

SMFXLR-1-2488/B

Yes 800-08849-01-A0

AXSM-8-622-XG 800-21445-06 SFP-4-622 Yes 800-22143-05 x — x — x1

AXSM-4-622 800-05774-09-B0

SMFIR-2-622

SMFLR-2-622

Yes 800-05383-01-A1

x — — — —

Yes 800-05385-01-A1

AXSM-4-622/B 800-07910-05-A0

SMFIR-2-622/B

Yes 800-07412-02-B0

x — — — x

SMFLR-2-622/B

Yes 800-07413-02-B0

AXSM-2-622-E 800-18521-02-A0

SMFIR-1-622/C

Yes 800-07410-02-A0

x — x — —

SMFLR-1-622/C

Yes 800-07411-02-A0

AXSM-16-155-XG 800-20821-06-A0

SFP-8-155 Yes 800-21518-03-A0

x — x — x1

SMFIR-1-155-SFP

10-1283-01-A0

SMFLR-1-155-SFP

10-1280-01-A0

MMF-1-155-SFP

10-1308-01-A0

MCC-8-155 Yes 800-22117-02-A0

AXSM-16-155 800-05776-06-A0

MMF-8-155-MT

Yes 800-04819-01-A1

x — — — —

SMFIR-8-155-LC

Yes 800-05342-01-A0

SMFLR-8-155-LC

Yes 800-05343-01-C0


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements

AXSM-16-155/B 800-07909-05-A0

MMF-8-155-MT/B

Yes 800-01720-02-A0

x — — — x

SMFIR-8-155-LC/B

Yes 800-07864-02-B0

SMFLR-8-155-LC/B

Yes 800-07865-02-B0

AXSM-8-155-E 800-18520-02-A0

SMB-4-155 Yes 800-07425-02-A0

x — — — —

MMF-4-155/C Yes 800-07408-02-A0

SMFIR-4-155/C

Yes 800-07108-02-A0

SMFLR-4-155/C

Yes 800-07409-02-A0

AXSM-16-T3E3 800-05778-08-A0

SMB-8-T3 — 800-05029-02-A0

x — — — —

SMB-8-E3 — 800-04093-02-A0

AXSM-16-T3E3/B 800-07911-05-A0

SMB-8-T3 — 800-05029-02-A0

x — — — x

SMB-8-E3 — 800-04093-02-A0

AXSM-16-T3E3-E 800-18519-02-A0

SMB-8-T3 — 800-05029-02-A0

x — x — —

SMB-8-E3 — 800-04093-02-A0

AXSM-32-T1E1-E 800-22229-01-A0

MCC-16-E1 — 800-19853-02-A0

x — — — —

RBBN-16-T1E1

— 800-21805-03-A0

MGX8950-EXTDR-CON

800-23813-03-A0

— — — — — — — x1

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


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45

MGX-SRME 800-14224-02-A0

MGX-SMFIR-1-155

Yes 1

800-14460-02-A0

x x — x —

MGX-STM1-EL-1

Yes 2

800-23175-03-A0

MGX-SRME/B 800-21629-03-A0

MGX-SMFIR-1-155

— 800-14460-02-A0

x x x x —

MGX-BNC-3T3-M

— 800-03148-02-A0

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


OL-11771-03

System Requirements

AX-CESM-8T1 800-02750-03-B0

AX-RJ48-8T1 — 800-02286-01-A0

x — — — —

AX-R-RJ48-8T1

— 800-02288-01-A0

MGX-CESM-8T1/B 800-08613-02-A0

AX-RJ48-8T1

AX-R-RJ48-8T1

— 800-02286-01-A0

x x — x —

— 800-02288-01-A0

MGX-VXSM-155 800-15121-06-A0

VXSM-BC-4-155

800-21428-06-A0

x — — — —

MGX-VXSM-T3 800-4074-02-A0

VXSM-BC-3T3 — 800-3095-03 x — — — —

MGX-VXSM-T1E1 800-24073-02-A0

VXSM-BC-24T1E1

800-23088-03-A0

x — — — —

MGX-VISM-PR-8T1

800-07990-02-A0

AX-RJ48-8T1 800-02286-01-A0

x x x x —

AX-R-RJ48-8T1

800-02288-01-A0

MGX-VISM-PR-8E1

800-07991-02-A0

AX-SMB-8E1 800-02287-01-A0

x x x x —

AX-R-SMB-8E1

800-02410-01-A0

AX-RJ48-8E1 800-02286-01-A0

AX-R-RJ48-8E1

800-02409-01-A0

1. APS connectors are not required in the Cisco MGX 8830 chassis.


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45

AX-FRSM-8E1 800-02438-04-A0

AX-SMB-8E1 — 800-02287-01-A0

x x — x —

AX-R-SM-8E1 — 800-02410-01-A0

AX-RJ48-8E1 — 800-02408-01-A0

AX-R-RJ48-8E1

— 800-02409-01-A0

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-T3E31 800-18731-02-A0

SMB-6-T3E3 — 800-08799-01-A0

x — — — —

MGX-FRSM-HS2/B

800-17066-01-A0

SCSI2-2HSSI/B2

— 800-05463-02-A0

800-05501-01-A0

— x — x —

MGX-12IN1-8S

— 800-18302-01-A0


OL-11771-03

System Requirements

MGX-RPM-PR-256

800-07178-02-A0

MGX-MMF-FE — 800-03202-02-A0

x x x x x

MGX-RJ45-FE — 800-02735-02-A0

MGX-RJ45-4E/B

— 800-12134-01-A0

MGX-RPM-1FE-CP

— 800-16090-05-D0

MGX-RJ45-5-ETH

— 800-27602-01-A0

MGX-RPM-PR-512

800-07656-02-A0

MGX-MMF-FE — 800-03202-02-A0

MGX-RJ45-FE — 800-02735-02-A0

MGX-RJ45-4E/B

— 800-12134-01-A0

MGX-RPM-1FE-CP

— 800-16090-05-D0

MGX-RJ45-5-ETH

— 800-27602-01-A0


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements

The following notes apply to Table 7 through Table 11:

• R- identifies a redundant card, for example AX-R-RJ48-8E1, AX-R-RJ48-8T1, and AX-R-SMB-8E1 cards.

• AXSM cards in the MGX 8850 (PXM45) switch can use either the MGX-8850-APS-CON or MGX-APS-CON.

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

• Cisco MGX 8950 does not support the AXSM/A or the AXSM-E cards. If these cards are present, Failed appears when the dspcds command is issued.

MGX-RPM-XF-512 800-09307-06-A0

MGX-XF-UI3 — 800-09492-01-A0

x — x — x

MGX-XF-UI/B — 800-24045-01-A0

MGX-1-GE — 800-18420-03-A0

MGX-2-GE — 800-20831-04-A0

MGX-1OC-12POS-IR

— 800-08359-05-A0

MGX-2OC-12POS-IR

— 800-21300-04-A0

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

— 30-1301-01-A0

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

— 30-1299-01-A0

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

— 10-1439-01-A0

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

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

3. Cannot be used in Cisco MGX 8850/B or Cisco MGX 8830/B chassis in slots where RCONs are installed. Use MGX-XF-UI/B instead.


Front Card Type


Back Card Types

APSCon




MGX 8830/BPXM45


MGX 8950PXM45


OL-11771-03

System Requirements

Table 12 summarizes the correct APS connector for each MGX chassis and front card.

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

Chassis TypeMGX-APS-CON800-05307-01

MGX-8850-APS-CON800-20640-01-A0

MGX-8830-APS-CON800-05308-02

MGX-8950-APS-CON800-15308-01-A0

MGX 8850 (PXM45) AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155-XG

MGX-SRME

MGX-SRME/B

MPSM-T3E3-1551

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

— —

MGX 8850 (PXM1E) — PXM1E-4-1552

PXM1E-8-155

MGX-SRME

MGX-SRME/B

MPSM-T3E3-1551

— —

MGX 8830 — — PXM1E-4-1552

PXM1E-8-155

MPSM-T3E3-1551

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

—

MGX 8830/B (PXM45)

— — AXSM-16-155-XG

AXSM-8-622-XG

AXSM-2-622-E

—

MGX 8950 — — — AXSM-16-155/B

AXSM-4-622/B

AXSM-1-2488/B

AXSM-16-155-XG


OL-11771-03

Service Class Template File Information

Service Class Template File InformationThis section contains Service Class Template (SCT) file information for Release 5.4.30.

PXM1E SCT FilesThe default SCTs provided are as follows:

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

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

The file names and checksums for the SCT files are as follows:

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

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

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

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

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

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

Notes:

1. PXM1E does not support CARD SCT.

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

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

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

AXSM and AXSM/B SCT FilesThe AXSM and AXSM/B SCTs have the following characteristics:

• SCT 2—Policing enabled, PNNI

• SCT 3—Policing disabled, PNNI

• SCT 4—Policing enabled, MPLS and PNNI

• SCT 5—Policing disabled, MPLS and PNNI

The file names and checksums for the SCT files are as follows:

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

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

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

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

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


OL-11771-03


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

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

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

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

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

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

AXSM-E SCT FilesThe AXSM-E SCTs have the following characteristics:

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

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

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

• PORT SCT 53—Policing disabled on PNNI and MPLS

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

• PORT SCT 55—Policing disabled on PNNI and MPLS

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

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

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

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

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

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

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

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

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

AXSM-XG SCT FilesThe AXSM-XG SCTs have the following characteristics:

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

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

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

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

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


OL-11771-03


The SCT file names and checksums are:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The SCT file names and checksums are:

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

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

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

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

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


OL-11771-03

New and Changed Commands

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

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

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

The MPSM-16-T1E1 SCT file names and checksums are:

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

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

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

New and Changed CommandsThis section contains the new and changed commands in Release 5.4.30, Release 5.4.10, Release 5.4.00, Release 5.3.20, and Release 5.3.00.

New Commands in Release 5.4.30The following commands are introduced in this release:

cnfvctrefresh

Enables or disables the VCT Refresh feature.

Service Context—ATM

Modules—AXSM

Enter the cnfvctrefresh command to enable or disable the VCT Refresh.

Syntax

cnfvctrefresh <VCT Refresh> [-reboot <Auto Reboot>]

Syntax Description

VCT Refresh Enables or disables the VCT Refresh. Valid values are:

enable: Enables VCT Refresh.

disable: Disables VCT Refresh.

Default: disable

reboot Enables or disables the Auto Reboot. Valid values are:

enable: Enables Auto Reboot.

disable: Disables Auto Reboot.

Default: enable


OL-11771-03


Attributes

Example

In the following example, the user enables the VCT Refresh feature:

Unknown.12.AXSM-XG[ATM].a > cnfvctrefresh enable

dspvctrefresh

Displays the VCT Refresh values.

Service Context—ATM

Modules—AXSM

Enter the dspvctrefresh command to display the VCT Refresh values.

Syntax

dspvctrefresh

Syntax Description

This command has no arguments or parameters.

Attributes

Example

In the following example, the user displays the VCT Refresh values:

Unknown.12.AXSM-XG[ATM].a > dspvctrefreshActive VCT Memory Refresh : enableAutomatic Card Reboot : enable

New Commands in Release 5.4.10The following commands are introduced in this release:

cnfcdbwupd

Enables or disables the BWUPD feature at card level.

Service Context—PPP

Modules— MPSM-T3E3-155

Log: no State: active Privilege: any



OL-11771-03


Enter the cnfcdbwupd command to disable or enable BWUPD feature. The command does not affect the existing IMA groups but affects the default behavior of newly added IMA groups that will be provisioned in the future. This command does not have any significance in E3 mode because MPSM-T3E3-155 does not support channelization in E3 mode.

Syntax

cnfcdbwupd <bwupd>

Syntax Description

Attributes

Example

In the following example, the user enables the BWUPD feature.

Unknown.12.MPSM155[ATM].a > cnfcdbwupd 1

dspcdbwupd

Displays the card level configuration.



Enter the dspcdbwupd command to display the card level configuration.

Syntax

dspcdbwupd

Syntax Description

This command takes no parameters.

Attributes

Example

In the following example, card level configuration is displayed.

Unknown.12.MPSM155[ATM].a > dspcdbwupd

bwupd Specifies whether BWUPD is enabled or not. Value 1 enables the BWUPD feature. Value 2 disables the BWUPD feature.

Note This is available only for T3 mode.




OL-11771-03


Default Bandwidth Update: Disable

cnfimagrpbwupd

Enables or disables the BWUPD feature on the port hosted by an IMA group.



Enter the cnfimagrpbwupd command to disable or enable BWUPD feature on the port hosted by an IMA group.

Syntax

cnfimagrpbwupd <group> <bwupd>

Syntax Description

Attributes

Example

In the following example, the user enables the BWUPD feature on the port hosted by the IMA group 2.

Unknown.12.MPSM155[ATM].a > cnfcdbwupd 2 1

dspimagrpbwupd

Displays the BWUPD feature configuration for an IMA group.



Enter the dspimagrpbwupd command to display the BWUPD feature configuration for an IMA group.

Syntax

dspimagrpbwupd <group>

Syntax Description

group IMA Group ID.

bwupd Specifies whether BWUPD is enabled or not. Value 1 enables the BWUPD feature. Value 2 disables the BWUPD feature.

Note This is available only for T3 mode


group IMA Group ID.


OL-11771-03


Attributes

Example

In the following example, the user displays the BWUPD feature configuration for an IMA group 2.

Unknown.12.MPSM155[ATM].a > dspimagrpbwupd 2

dspimagrpbwupd

Displays the BWUPD feature configuration for all IMA groups.



Enter the dspimagrpbwupd command to display the BWUPD feature configuration for an IMA group.

Syntax

dspimagrpbwupd

Syntax Description


Attributes

Example

In the following example, the user displays the BWUPD feature configuration for all IMA groups.

Unknown.12.MPSM155[ATM].a > dspimagrpbwupd 2

Note By default the BWUPD feature is enabled.

Changed Commands in Release 5.4.00This section lists the commands updated in Release 5.4.00 for the following cards:

• Changed MPSM Commands

• Changed PXM Commands

• Changed AXSM Commands




OL-11771-03


Changed MPSM Commands

MPSM16T1E1, MPSM155

• cnfpart—Syntax was missing, but now displays.

• cnfrscprtn—Syntax was missing, but now displays.

• cnfapsln—Syntax was missing, but now displays.

MPSM155

• addimaport—To avoid the confusion regarding the port rate to be multiple of 50, a check is introduced to put the port rate as multiple of 50 ONLY for Virtual Ports.

Changed PXM Commands

PXM1E




Changed AXSM Commands

AXSME, AXSM, AXSMXG




AXSMXG

• cnfpath—New error message reads:

Err: the specified STS Path Width is not supported

• addlnloop—Blocks loop when APS is present:

ERR: Cannot add Loop for APS configured Line

• addlapsln—Blocks the APS when line loop is present:

ERR: Cannot add APS for line in Loopback

Changed Commands in Release 5.3.20Release 5.3.20 contains the following changed commands for the MPSM Licensing feature changes:

• clrallcnf—No longer has the clrLicense argument.

• dspcdalms—No longer displays license alarms.

• dspndalms—No longer displays license alarms.

The following commands now accept a line number (bay.line) or path number for the bertifNum argument:


OL-11771-03


• addbert

• cnfbert

• delbert

• dspbert

• dspbertcap

• dspbertstats

• insbiterror

• startbert

• stopbert

Additionally, the dsplnalm and dsplnalms commands display the BERT status for a T3/E3 line.

The cnfln command has a new line type (dsx1E1CLEAR).

Changed Commands in Release 5.3.00This section lists the commands updated in Release 5.3.00 for the following cards:

• Changed MPSM Commands

• Changed PXM Commands

• Changed AXSM-XG Commands

Changed MPSM Commands

The following commands change in Release 5.3.00:

• addmpbundle, cnfmpbundle, delmpbundle, addpppmux, cnfpppmux, delpppmux, addcon, cnfcon, and delcon

– New bundleNumber/ifNum parameter range: 1 to 64 for T1/E1 or 1 to 128 for T3/E3

– New confirmation message for cnfmpbundle (CSCek31999):

M8830_SF.6.MPSM155PPP[FR].a > cnfmpbundle -bundle 1 -mrru 1500Warning: Bundle Config is being changed, traffic might be interrupted brieflyDo you want to proceed (Yes/No) ?

• addppplink, cnfppplink, and delppplink

– New link parameter range: 1 to 64 for T1/E1 or 1 to 256 for T3/E3

– Enhance online help for OC-3, T3/E3, and T1/E1 (CSCek31112)

– New restartTimer, cnfReqRetry, termReqRetry, echo, and maxFailure parameters for addppplink and cnfppplink (CSCeh29350). See addppplink, page 66, and cnfppplink, page 69.

– Remove ds0speed parameter from cnfppplink (CSCin97715). See cnfppplink, page 69.

• cnfmpbundleparams

– New normpvcbw parameter range: 0-88301 (CSCin99015).

– New normpvcbw parameter default: 9200 for E1.

• dspmpbundles


OL-11771-03


New WP identifier field for the MPSM-16-T1E1 (CSCin97715). See dspmpbundles, page 72

• dspmpbundlecnt and dspppplnkcnt

New statistics for the average bundle or link data rate in Kbps, called kbpsAIR (CSCin97715). See dspmpbundlecnt, page 79, and dspppplnkcnt, page 80.

• addport, dspport, and dspports

New ds0beg and ds0num parameters for adding for fractional T1/E1 ATM ports (CSCeg68904). See addport, page 63, dspport, page 73, and dspports, page 77.

• dsppathalmcnt

Display elapsed time for current statistics (CSCej89464). See dsppathalmcnt, page 71.

• dspmpbundleload, dspwinpathload, and dspwpbundles

Added these MPSM-T3E3-155 commands to the MPSM-16-T1E1 card for consistency.

addport

Add Port

Service Context—ATM and Frame Relay

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

Enter the addport command to create and configure a logical port on an active physical line or logical path.

On a BNC-3-T3 or BNC-3-E3 back card, you can add a port on a physical line, or on a path. On an SFP-2-155 and the SMB-2-155-EL OC-3 back card, you can add a port on a path only.

For the MPSM-16-T1E1, you can configure full T1/E1 ports or NxDS0 ports. With PNNI signaling enabled on NxDS0 ports, you must configure the minimum bandwidth that PNNI requires. Otherwise, PNNI trunks may not come up. Use the dsppnctlvc command to display the required PNNI bandwidth.

Before you can add a port to a line or path, you must configure and activate the line or path. You use the upln command to activate a line, or the uppath command to activate a path.

Note The MPSM-T3E3-155 card supports up to 128 ATM ports and 1000 Frame Relay ports. The maximum number of logical ports for the entire MPSM-T3E3-155 is 1000. For example, you can configure 872 Frame Relay ports and 128 ATM ports on one MPSM-T3E3-155 card.

Note If you are going to use card statistics, you must use cnfcdstat before you add logical ports with the addport command. You cannot configure card statistics after adding ports.

Note Frame Relay ports are not supported on STS-3 paths.

Syntax—ATM Service Context for MPSM-16-T1E1

addport <ifNum> <path_num> <guaranteedRate> <maxRate> <sctID> <ifType> [-vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>] [-ds0beg <ds0beg>] [-ds0num <ds0num>]


OL-11771-03


Syntax—ATM Service Context for MPSM-T3E3-155

addport <ifNum> <path_num> <guaranteedRate> <maxRate> <sctID> <ifType> [-vpi <vpi>] [-minvpi <minvpi>] [-maxvpi <maxvpi>]

Syntax Description—ATM Service Context

ifNum Specifies an interface number (port number) for the port you are adding.

• MPSM-16-T1E1 range: 4-499

• MPSM-T3E3-155 range: 4-1003

Note Port numbers 1 through 3 are reserved for broadband Frame Relay ports.

path_num Identifies the line or path on which to add an ATM port:

• DS1/E1 or DS3/E3 line: bay.line

• STS path: bay.line.sts

• DS3/E3/VT path:

– DS3 payload: bay.line.sts

– VT structured payload: bay.line.sts:tug3

• DS1/E1 path:

– DS3 line: bay.line:ds1

– DS3 payload: bay.line.sts:ds1

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

– VT structured payload: bay.line.sts:tug3.vtg.vt

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

Note Enter the dsplns or dsppaths -all command to display all available line or path identifiers on the card.

Note On a BNC-3-T3 or BNC-3-E3 back card, you can add a port on a physical line, or a path on the line. On an SFP-2-155 and the SMB-2-155-EL OC-3 back card, you can add a port on a path only.


OL-11771-03


guaranteedRate Specifies the guaranteed rate on a port in cells per second. The guaranteed rate can be either max cell rate of the interface, or a multiple of 50.

The total guaranteed rates cannot exceed the highest value in the following ranges:

• MPSM-T3E3-155 ranges:

– OC-3—50 to 353207 cps

– STS1—50 to 114113 cps

– DS3—50 to 96000(PLCP) or 104268(ADM)

– E3—50 to 80000

– E1—50 to 4528 cps

– DS1—50 to 3622 cps

• MPSM-T3E3-155 and MPSM-16-T1E1 ranges:

– E1—50 to 4528 cps

– DS1—50 to 3622 cps

Note For all interface types (UNI, NNI, VNNI, EVNNI, and EVUNI), the guaranteedRate must be the same as maxrate.

Note For fractional T1/E1, the maxRate and guaranteedRate must always equal (64 * 1024 * N) /(8 * 53), where N is equal to ds0num.

maxRate Specifies the maximum rate on a logical port in cells/second.

Note See guaranteedRate notes.

sctID The ID of a service class template (SCT) for the port. The range is 0–255. The SCT file must exist on the PXM disk. See cnfcdsct.

Note Currently, the system does not support certain parameters in the service class templates (SCTs). These parameters are (when applicable) PCR, SCR, and ICR. You can specify them through addcon, cnfcon, or Cisco WAN Manager.

ifType Specifies the port as one of the following types of interfaces:

• 1 = UNI (User-to-Network Interface)

• 2 = NNI (Network-to-Network Interface)

• 3 = VNNI (Virtual Network-to-Network Interface)

• 4 = VUNI (Virtual User-to-Network Interface)

• 5 = EVUNI (Enhanced Virtual User-to-Network Interface)

• 6 = EVNNI (Enhanced Virtual Network-to-Network Interface)

EVNNI and EVUNI permit a range of VPIs for a single interface, and this range of VPIs represents the virtual NNI or virtual UNI trunk. VNNI and VUNI allow only one VPI for a single interface, and that VPI represents the virtual NNI or virtual UNI trunk. Multiple VNNIs and EVNNIs can coexist on the same line.

-vpi Virtual Path Identifier for a VNNI or VUNI interface:

• VNNI range: 1-4095

• VUNI range: 1-255


OL-11771-03


Related Commands

cnfport, delport, dspport, dspports, dspportsct

Attributes

Example—ATM Service Context

In the following example, the user creates logical port 3 on line 3 of bay 1. The minimum and maximum cells per second is 96000 cps. The port SCT file ID is 4. The interface type is NNI (specified by the 2 at the end of the command input).

MGX8850.6.MPSM155[ATM].a > addport 3 1.3 96000 96000 4 2

In the following example, the user creates a fractional T1 port on line 5 of bay 1. The logical port number is 205, the minimum and maximum cells per second is 603 cps, the port SCT file ID is 0, and the interface type is NNI. This port has four DS0s, starting with the first DS0 of the T1 line.

M8850_SF.27.MPSM16T1E1[ATM].a > addport 205 1.5 603 603 0 1 -ds0beg 1 -ds0num 4

addppplink

Add a Link to an MLPPP Bundle


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

-minvpi The minimum VPI for an EVUNI or EVNNI interface:

• EVUNI range: 0-255

• EVNNI range: 0-4095

-maxvpi The maximum VPI for an EVUNI or EVNNI interface:

• EVUNI range: 0-255

• EVNNI range: 0-4095

-ds0beg Specifies the beginning DS0 number:

• T1 paths: 1-24

• E1MF and E1CRCMF paths: 2-16, 18-32 (17 is reserved)

• other E1 paths = 2-32

Note MPSM-16-T1E1 only.

-ds0num Specifies the number DS0 time slots that will follow the beginning DS0:

• T1 paths: 1-24

• E1MF and E1CRCMF paths: 1-30

• other E1 paths: 1-31

Note MPSM-16-T1E1 only.

Log: yes State: active Privilege: GROUP1


OL-11771-03


Enter the addppplink command to add a link to an existing MLPPP bundle. MPSM-16-T1E1 links are T1/E1 lines, and MPSM-T3E3-155 links are channelized T1/E1 paths.

Syntax

addppplink <link> <bay.line> <bundleNumber> [-mru <value>] [-lcpTimeout <msec>] [-restartTimer <msec>] [-cnfReqRetry <value>] [-termReqRetry<value>] [-echo <value>] [-maxFailure <value>] [-startDS0 <value>] [-numDS0 <value>] [-ds0speed <mode>] [-pfcTx <mode>] [-acfcTx <mode>] [-loopCheck <mode>]

Syntax Description

link A number for the PPP link.


• MPSM-T3E3-155 range: 1-84

bay.line The line or path number of the link.

• MPSM-16-T1E1 (DS1/E1 line):

– bay.line, where bay = 1, line = 1-16.

Note All links on a bundle must be in the same range of lines, either 1-8 or 9-16

• MPSM-T3E3-155 (DS1/E1 path):

– DS3 line: bay.line:ds1

– DS3 payload: bay.line.sts:ds1

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

– VT structured payload: 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 dsplns or dsppaths -all command to display all available lines or paths on the card.

bundleNumber The MLPPP bundle number to which you are adding a PPP link.


• MPSM-T3E3-155 range: 1-84

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.

-mru Maximum Receive Unit, in the range 64-1524.

Default:1500

-lcpTimeout Note The length of time to wait for an echo reply before bringing down LCP. The value is specified in msec, but is rounded down to the nearest 100 msec.

Range: 1000-4294967 msec

Default: 10000 msec


OL-11771-03


-restartTimer The link restart timer value.

Range: 1000-60000 msec

Default: 3000 msec

-cnfReqRetry The maximum number of configuration request retries.

Range: 1-255

Default: 10

-termReqRetry The maximum number of termination request retries.

Range: 1-255

Default: 2

-echo The maximum number of echo retries.

Range: 1-255

Default: 5

-maxFailure The maximum number of failures.

Range: 1-255

Default: 5

-startDS0 Specifies a starting DS0 for a fractional T1/E1 link, in the following ranges:

• T1 line or path: 1-24

• E1 line or path:

– E1 and CRC types: 2-32 (timeslot 0 reserved)

– MF or CRCMF types: 2-16, 18-32 (timeslots 0 and 16 reserved)

Note This parameter is required for a fractional T1/E1 link.

-numDS0 Specifies the number of DS0s for a fractional T1/E1 link, in the following ranges:

• T1 line or path: 1-24

• E1 line or path:

– E1 and CRC types: 1-31 (timeslot 0 reserved)

– MF or CRCMF types: 1-30 (timeslots 0 and 16 reserved)

Default: Maximum number of DS0s

Note A fractional T1/E1 link has a contiguous set of DS0s.

-ds0speed Specifies the speed of DS0 channels.

• 1 = 56K

• 2 = 64K (default)

-pfcTx Controls the compression of PF in PPP packets transmitted from this end.

• 1 = enable, PFC is performed if the far end is capable of receiving compressed PF.

• 2 = disable, PFC is not performed, even if the far end is capable of receiving compressed PF.

Default: 2


OL-11771-03


Attributes

Related Commands

cnfppplink, delppplink, dspppplink

Example

In the following example, the user adds a PPP link 5 and line 1.5 and bundle 5.

M8850_SF.27.MPSM16T1E1PPP[FR].a > addppplink 5 1.5 5

cnfppplink

Configure a PPP Link



Enter the cnfppplink command to change the configuration of a PPP link.

Syntax

cnfppplink -link <linkID> [-mru <value>] [-lcpTimeout <msec>] [-restartTimer <msec>] [-cnfReqRetry <value>] [-termReqRetry<value>] [-echo <value>] [-maxFailure <value>] [-pfcTx <mode>] [-acfcTx <mode>] [-loopCheck <mode>]

Syntax Description

-acfcTX Controls the compression of address/control fields in PPP packets transmitted from this end.

• 1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields.

• 2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.

Default: 2

-loopCheck Enables or disables loopback check. If loopback check is enabled, when the magic number in the incoming echo reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down the LCP session.

• 1 = enabled (default)

• 2 = disabled


-link Specifies the PPP link number.

Enter the dspppplinks command to display all PPP links on the card.

-mru The Maximum Receive Unit, in the range 64-1524


OL-11771-03


Attributes

Related Commands

addppplink, delppplink, dspppplink

-lcpTimeout The length of time to wait for a Echo Reply before bringing down LCP. The value is in msec, rounded down to the nearest 100 msec. Range 1000-4294967.

-restartTimer The link restart timer value.

Range: 1000-60000 msec

Default: 3000 msec

-cnfReqRetry The maximum number of configuration request retries.

Range: 1-255

Default: 10

-termReqRetry The maximum number of termination request retries.

Range: 1-255

Default: 2

-echo The maximum number of echo retries.

Range: 1-255

Default: 5

-maxFailure The maximum number of failures.

Range: 1-255

Default: 5

-pfcTx Controls the compression of PF in PPP packets transmitted from this end.

• 1 = enable, PFC is performed if the far end is capable of receiving compressed PF.

• 2= disable, PFC is not performed, even if far end is capable of receiving compressed PF.

-acfcTX Controls the compression of address/control fields in PPP packets transmitted from this end.

• 1 = enable, ACFC is performed if the far end is capable of receiving compressed address/control fields.

• 2 = disable, ACFC is not performed, even if far end is capable of receiving compressed address/control fields.

-loopCheck Controls loopback check. If loopback check is enabled, when the Magic Number in the incoming Echo Reply is the same as of this PPP link, then this PPP link assumes that the far end is in loopback and brings down its own LCP session.

• 1 = enable

• 2 = disable



OL-11771-03


Example

In the following example, the user configures PPP link 1 with an MRU of 1234 and enables acfcTx and pfcTx compression.

U4.5.MPSM16T1E1PPP[FR].a > cnfppplink -link 1 -mru 1234 -acfcTx 1 -pfcTx 1

dsppathalmcnt

Display Path Alarm Counters

Service Context—ATM and Frame Relay

Modules—MPSM-T3E3-155

Enter the dsppathalmcnt command to display the path alarm counters for the specified path for the current 15-minute interval and the current 24-hour interval. Optionally, you can display path alarm counters for a specific 15-minute interval only.

Syntax

dsppathalmcnt [path_filter] <path_num> [<intvl>]

Syntax Description

-path_filter Identifies the path type for which you want to display alarm counters.

Possible path_filter keywords are:

• -sts—Select STS paths in SONET networks, or AU paths in SDH networks.

• -vt—Select VT paths in SONET networks, or TU3 paths in SDH networks.

• -ds3—Select DS3 paths in SONET and SDH networks.

• -e3—Select E3 paths in SONET and SDH networks.

• -ds1—Select DS1 paths in SONET and SDH networks.

• -e1—Select E1 paths in SONET and SDH networks.

Note STS/STM paths and DS3 paths can have the same path number. If you enter the dsppathalmcnt command without the -path_filter option, and only STS/STM paths are configured on the card, the display shows the path alarm counters for the STS/STM path with the specified path number. If there are DS3 paths configured on the card as well as STS/STM paths, and you do not include the -path_filter option with the dsppathalmcnt command, the display shows the path alarm counters for the lowest-level path (the DS3 path). To avoid confusion, Cisco recommends that you specify a -path_filter when you display a path.

path_num The number of the path to display.

Note Use the dsppaths <path_filter> command to display the path numbers for available paths.

intvl The time interval to display (0–96). Interval 0 is the current 15-minute and 24-hour interval. Interval 1 is the most recent 15-minute interval. Interval 2 is the next most recent 15-minute interval, and so on. Interval 96 is the oldest 15-minute interval.


OL-11771-03


Related Commands

clrpathalmcnf

Attributes

Example

In the following example, the user displays the path alarm counters for the STS path 1.1.1, which displays the current interval statistics and the elapsed time of the current interval.

M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt -sts 1.1.1 Path Number : 1.1.1 Path Type : sts Path PM: Elapsed Time(in sec): 309 Num of AISs: 0 Num of RDIs: 0 Near End Far End CurrentESs : 0 CurrentESs : 0 CurrentSESs : 0 CurrentSESs : 0 CurrentCVs : 0 CurrentCVs : 0 CurrentUASs : 0 CurrentUASs : 0 Current24HrESs : 0 Current24HrESs : 0 Current24HrSESs: 0 Current24HrSESs: 0 Current24HrCVs : 0 Current24HrCVs : 0 Current24HrUASs: 0 Current24HrUASs: 0

In the following example, the user displays interval statistics for the same path.

M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt -sts 1.1.1 2 Path Type : sts Path Number : 1.1.1 Interval Number : 2 Path PM: -------- Near End Far End ESs : 0 ESs : 0 SESs : 0 SESs : 0 CVs : 0 CVs : 0 UASs : 0 UASs : 0

dspmpbundles

Display MLPPP Bundles



Enter the dspmpbundles command to display summary information about all MLPPP bundles.

Syntax

dspmpbundles

Log: no State: active, standby, init Privilege: ANYUSER


OL-11771-03


Syntax Description

None

Attributes

Related Commands

addmpbundle, cnfmpbundle, delmpbundle, dspmpbundle, dspwpbundles

Example

In the following example, the user displays all MLPPP bundles on an MPSM-16-T1E1 card:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundlesMLPPP Admin Oper Active Available Alarm MUX AutoBW WPBundle State State Links Bandwidth Cause Status Mode Id------------------------------------------------------------------------------- 1 Up Up 1 1536000 No Alarm Disable Enable 1 2 Up Up 1 1536000 No Alarm Disable Enable 2

In the following example, the user displays all MLPPP bundles on an the MPSM-T3E3-155 card:

M8850_SF.10.MPSM155PPP[FR].a > dspmpbundlesMLPPP Admin Oper Active Available Alarm MUX AutoBW WPBundle State State Links Bandwidth Cause Status Mode Id------------------------------------------------------------------------------- 1 Up Up 2 3072000 No Alarm Enable Enable 1 2 Up Up 2 3072000 No Alarm Enable Enable 2

dspport

Display Port

Service Context—ATM, Frame Relay, PPP


Enter the dspport command to display the configuration for a logical port. In the ATM CLI context, the ports represent ATM services or IMA groups. In the Frame Relay CLI context, the ports represent Frame Relay services, Multilink Frame Relay bundles, or Multilink PPP bundles.

The following qualifications apply to port displays:

• The operational state for standby cards is reported as N/A because the operational state of the standby card may not be the same as the active card.

• The total number of connections in the display includes control VCs. The types of control VCs are SSCOP, PNNI-RCC, and ILMI (if integrated local management interface is enabled on MPSM cards). To see the connection counts that do not include control VCs, use dsppnport.

• When a MPSM rebuilds, it provisions the card from the stored database on the PXM disk. If the SCT file associated with a specific port is missing or corrupted, the default SCT file is applied to that port. This is indicated in the dspport output by the string:

“0/0 =Def”



OL-11771-03


• The SCT ID in the display pertains to the port. For the card-level SCT ID, use dspcd on the current card.

Syntax

dspport <ifNum>

Syntax Description

Related Commands

addport, dnport, dspports

Attributes

Sample ATM Service Context

In the following MPSM-T3E3-155 example, the user displays the port configuration for ATM port 12.

mpsm_node.4.MPSM155[ATM].a > dspport 12 Interface Number : 12 Line/Path Number : 1.1.2 IMA Group Number : N/A Admin State : Up Operational State : Up Guaranteed bandwidth(cells/sec): 50 Number of partitions : 1 Maximum bandwidth(cells/sec) : 50 Number of SPVC : 1 ifType : UNI Number of SPVP : 0 VPI number (VNNI, VUNI) : 0 Number of SVC : 0 Number of Sig VC : 0 MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0 SCT Id : 0 =Def F4 to F5 Conversion : Disabled

In the following MPSM-16-T1E1 example, the user displays the port configuration for a fractional T1 ATM port with four DS0s.

M8850_SF.27.MPSM16T1E1[ATM].a > dspport 205 Interface Number : 205 Line/Path Number : 1.5 IMA Group Number : N/A Admin State : Up Operational State : Up Guaranteed bandwidth(cells/sec): 603 Number of partitions : 1 Maximum bandwidth(cells/sec) : 603 Number of SPVC : 0 ifType : UNI Number of SPVP : 0 VPI number (VNNI, VUNI) : 0 Number of SVC : 0 Number of Sig VC : 0 MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0 SCT Id : 0 =Def F4 to F5 Conversion : Disabled Time Slot : 1(4)

In the following MPSM-T3E3-155 example, the user displays the port configuration for IMA port 127.

ifNum Identifies the logical interface (port number) to display.

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

Log: no State: active, standby Privilege: ANYUSER


OL-11771-03


M8850_SF.9.MPSM155[ATM].a > dspport 127 Interface Number : 127 Line/Path Number : N/A IMA Group Number : 1 Admin State : Up Operational State : Up Guaranteed bandwidth(cells/sec): 3000 Number of partitions : 1 Maximum bandwidth(cells/sec) : 3000 Number of SPVC : 0 ifType : UNI Number of SPVP : 0 VPI number (VNNI, VUNI) : 0 Number of SVC : 0 Number of Sig VC : 0 MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0 SCT Id : 0 =Def F4 to F5 Conversion : Disabled

Sample Frame Relay Service Context

In the following example, the user displays the port configuration for Frame Relay port 2.

mpsm_node.5.MPSM155[FR].a > dspport 2 Interface Number : 2 Line Number : 1.1.1 DS0 Speed : unused DS0 Configuration Bit Map : N/A Admin State : Down Operational State : Down Port State : Inactive Port Signaling State : No Signaling Failure Interface Type : Frame Relay SCT Id : 0/0 =Def Frame Header Length : Two Bytes Flags Between Frames : 1 Equeue Service Ratio : 1 Port Speed : 44209 kbps Checksum type : crc16 Over-subscription : Disabled Over-subscribed : False Signaling Protocol Type : No Signaling Enhanced LMI : Disabled FRF 1.2 Support : Disabled Asynchronous Updates : Disabled T391 Link Integrity Timer : 10 secs

Type <CR> to continue, Q<CR> to stop: T392 Polling Verification Timer : 15 secs N391 Full Status Polling Counter : 6 N392 Error Threshold : 3 N393 Monitored Event Count : 4 FRF.12 Fragmentation : Disabled FRF.12 Fragment Size : 64 Bytes Port HDLC Frame Inversion : Disabled Number of Partitions : 1 Number of SPVC : 0

In the following example, the user displays the port configuration for Multilink Frame Relay port 4.

M8850_SF.9.MPSM155[FR].a > dspport 4 Interface Number : 4 Line Number : N/A MFR bundle Number : 1 DS0 Speed : unused DS0 Configuration Bit Map : N/A Admin State : Up Operational State : Up Port State : Active Port Signaling State : No Signaling Failure


OL-11771-03


Interface Type : Frame Relay SCT Id : 0/0 =Def Frame Header Length : Two Bytes Flags Between Frames : 1 Equeue Service Ratio : 1 Port Speed : 1532 kbps Checksum type : crc16 Over-subscription : Disabled Signaling Protocol Type : None Enhanced LMI : Disabled FRF 1.2 Support : Disabled Asynchronous Updates : Disabled T391 Link Integrity Timer : 10 secs

Type <CR> to continue, Q<CR> to stop: T392 Polling Verification Timer : 15 secs N391 Full Status Polling Counter : 6 N392 Error Threshold : 3 N393 Monitored Event Count : 4 FRF.12 Fragmentation : Disabled FRF.12 Fragment Size : 64 Bytes Port HDLC Frame Inversion : Disabled Number of Partitions : 1 Number of SPVC : 0

Sample PPP Service Context

In the following example, the user displays the port configuration for Multilink PPP port 5.

M8850_SF.25.MPSM16T1E1PPP[FR].a > dspport 5 Interface Number : 5 Line Number : N/A DS0 Speed : unused DS0 Configuration Bit Map : N/A Admin State : Up Operational State : Up Port State : Active Port Signaling State : No Signaling Failure Interface Type : Frame Forward SCT Id : 0/0 =Def Frame Header Length : Two Bytes Flags Between Frames : 1 Equeue Service Ratio : 1 Port Speed : 1536 kbps Checksum type : crc16 Over-subscription : Disabled Signaling Protocol Type : None Enhanced LMI : Disabled FRF 1.2 Support : Disabled Asynchronous Updates : Disabled T391 Link Integrity Timer : 10 secs T392 Polling Verification Timer : 15 secs

Type <CR> to continue, Q<CR> to stop: N391 Full Status Polling Counter : 6 N392 Error Threshold : 3 N393 Monitored Event Count : 4 FRF.12 Fragmentation : N/A FRF.12 Fragment Size : 64 Bytes Port HDLC Frame Inversion : Disabled Number of Partitions : 1 Number of SPVC : 0


OL-11771-03


dspports

Display Ports

Service Context—ATM, Frame Relay, PPP


Enter the dspports command to display general information about all logical ports on the card.

Enter the dspports command in the ATM CLI context to display the following information for all ATM ports on the current card:

Enter the dspports command in the Frame Relay CLI context to display the following information for all Frame Relay ports:

ifNum Identifies the logical interface (port).

Line/Path Identifies the path number associated with the port.

Admin State Indicates whether the administrative status of the port is up or down.

Oper State Indicates whether the port is up or down.

Guarntd Rate Indicates the minimum guaranteed rate for the port in cells per second.

Max Rate Indicates the maximum allowed rate for the port in cells per second.

SCT InUse Indicates the ID of the port-level SCT (see the addport command).

if Type Indicates the type of interface configured on the port.

VPI (VNNI, VUNI) The VPI number of the port (applies only where virtual NNIs are available).

VPI (EVUNI, EVNNI)

The minimum and maximum VPI configured for the port (applies only where virtual NNIs are available).

IMA GRP Identifies the port’s IMA group, if IMA groups are configured.

Note If the specified port is not configured for an IMA group, the IMA GRP field reports N/A.

DS0Start (Num) The first DS0 channel in an NxDS0 port, and the number of DS0s it contains.

ifNum The logical interface (port).

Line/Path The line or path number associated with the port.

Admin State Indicates whether the administrative status of the port is up or down.

Oper State Indicates whether the port is up or down.

ifType The type of interface configured on the port.

sctID Conf/InUse The ID of the port-level SCT (see the addport command).

DS0 Start (Num) The first DS0 channel in an NxDS0 port, and the number of DS0s it contains.

Port Speed Indicates the data rate of the port, in Kbps.

ESR Indicates the enqueue service ratio

Signaling Type Indicates the port signaling type, if any.

ELMI Status Indicates whether enhanced LMI state is enabled or disabled on the port.


OL-11771-03


Note The operational state for standby cards is reported as N/A because the operational state of the standby card may not be the same as the active card.

Syntax

dspports

Related Commands

addport, cnfport, delport, dspport

Attributes

Sample ATM Service Context

In the following MPSM-T3E3-155 example, the user displays the ATM ports, two of which are IMA groups.

M8850_SF.10.MPSM155[ATM].a > dspportsif Line/Path Admn Oper Guarntd Max SCT if VPI IMA DS0Num Num Stat Stat Rate Rate In Type -------------- GRP Start Use VNNI (EVNNI, (Num) VUNI EVUNI )---- ----------- ---- ---- -------- -------- --- ----- ---- MIN MAX --- ------ 10 N/A Up Up 7000 7000 0 UNI 0 0 0 1 N/A 20 N/A Up Up 7000 7000 0 UNI 0 0 0 2 N/A 113 1.1:3 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24) 123 1.2:3 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24)

In the following MPSM-16-T1E1 example, the user displays ATM ports, which include two IMA groups, two full T1 ATM ports, and two fractional T1 ATM ports with four DS0s each.

M8850_SF.27.MPSM16T1E1[ATM].a > dspportsif Line/Path Admn Oper Guarntd Max SCT if VPI IMA DS0Num Num Stat Stat Rate Rate In Type -------------- GRP Start Use VNNI (EVNNI, (Num) VUNI EVUNI )---- ----------- ---- ---- -------- -------- --- ----- ---- MIN MAX --- ------ 10 N/A Up Up 7000 7000 0 UNI 0 0 0 1 1(24) 20 N/A Up Up 7000 7000 0 UNI 0 0 0 2 1(24) 106 1.6 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24) 114 1.14 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24) 205 1.5 Up Up 603 603 0 UNI 0 0 0 N/A 1(4) 213 1.13 Up Up 603 603 0 UNI 0 0 0 N/A 1(4)

FRF 12 Fragmentation

Indicates whether FRF 12 Fragmentation is enabled or disabled on the port.

MLPPP Bundle Indicates the bundle with which the port is associated for MLPPP services.

Note Displayed only on cards that support MLPPP.

MFR Bundle Indicates the bundle with which the port is associated for MFR services.

Note Displayed only on cards that support MFR.



OL-11771-03


Sample Frame Relay Service Context

In the following example, the user displays the Frame Relay ports, one of which is in an MFR bundle.

M8850_SF.9.MPSM155[FR].a > dspportsESR: 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 Up FR 0 N/A 1532 1 None Off Off 1 11 1.1.0:1.1.1 Up Up FR 0 1(24) 1536 1 None Off Off N/A

Sample PPP Context

In the following example, the user displays the ports for MLPPP bundles.

M8850_SF.25.MPSM16T1E1PPP[FR].a > dspportsESR: Egress queue Service Ratio SCT DS0 Port E FRF If Line/Path Admn Oper if In Start Speed Signaling LMI 12 MLPPP Num Num Stat Stat Type Use (Num) kbps ESR Type St Frg Bundle ---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------ 5 N/A Up Up FFwd 0 N/A 1536 1 None Off N/A 5 13 N/A Up Up FFwd 0 N/A 1536 1 None Off N/A 13

dspmpbundlecnt

Display Statistics on an MLPPP Bundle



Enter the dspmpbundlecnt command to display MLPPP bundle statistics.

Syntax

dspmpbundlecnt <bundleNumber> <intvl>

Syntax Description

Attributes

bundleNumber Specifies the MLPPP bundle number for which t o display statistics.

Note Enter the dspmpbundles command to display all MLPPP bundles on the card.




OL-11771-03


Related Commands

dspmpbundle

Example

In the following example, the user displays statistics for interval 0 of MLPPP bundle 1 on an MPSM-16-T1E1:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspmpbundlecnt 1 0 MLPPP Bundle Number : 1 Interval Number : 0

Receive Packets : 2101305 Receive Bytes : 60955779 Receive Discard Bytes : 0 Receive MRRU Error Packets : 0 Receive Discard Packets : 0 Receive FCS Error Packets : 0 Receive kbpsAIR : 1509 Send Packets : 397 Send Bytes : 29390 Send kbpsAIR : 0

In the following example, the user displays statistics for interval 0 of MLPPP bundle 1 on an MPSM-T3E3-155:

M8850_SF.10.MPSM155PPP[FR].a > dspmpbundlecnt 1 0 MLPPP Bundle Number : 1 Interval Number : 0

Receive Packets : 2101305 Receive Bytes : 60955779 Receive Discard Bytes : 0 Receive MRRU Error Packets : 0 Receive Discard Packets : 0 Receive FCS Error Packets : 0 Receive kbpsAIR : 1509 Send Packets : 397 Send Bytes : 29390 Send kbpsAIR : 0

dspppplnkcnt

Display Statistics on a PPP Link



Enter the dspppplnkcnt command to display statistics on a PPP link.

Syntax

dspppplnkcnt <link> <intvl>]


OL-11771-03


Syntax Description

Attributes

Related Commands

clrppplnkcnt

Example

In the following example, the user displays statistics for interval 0 on PPP link 10 on an MPSM-16-T1E1:

M8850_SF.27.MPSM16T1E1PPP[FR].a > dspppplnkcnt 10 0 MLPPP Link Number : 10 Interval Number : 0

Receive Packets : 2291753 Receive Bytes : 66480391 Receive Discard Bytes : 0 Receive MRU Errors : 0 Receive Miscellaneous Errors : 0 Receive FCS Error Packets : 0 Receive kbpsAIR : 1498 Send Packets : 433 Send Bytes : 32054 Send kbpsAIR : 0

In the following example, the user displays statistics for interval 0 on PPP link 10 on an MPSM-T3E3-155:

M8850_SF.10.MPSM155PPP[FR].a > dspppplnkcnt 10 0 MLPPP Link Number : 10 Interval Number : 0

Receive Packets : 2291753 Receive Bytes : 66480391 Receive Discard Bytes : 0 Receive MRU Errors : 0 Receive Miscellaneous Errors : 0 Receive FCS Error Packets : 0 Receive kbpsAIR : 1498 Send Packets : 433 Send Bytes : 32054 Send kbpsAIR : 0

link Specifies the PPP link number for which to display statistics.

Note Enter the dspppplinks command to display all MLPPP links on the card.




OL-11771-03


Changed PXM Commands

This release adds a node configuration option that controls secure (SFTP and SSH) access to the PXM. This affects the following commands:

• cnfndparm

• dspndparms

cnfndparms—PXM45

Configure Node Parameters—PXM45

The cnfndparms command lets you configure a diverse set of node-level parameters.

Note Variations exist in the available parameters according to controller card and chassis. For the parameters on a PXM1E, see the next description of the cnfndparms command.

The parameters consist of an option number and a value or a yes/no choice. The configuration resides in nonvolatile RAM and thus survives a system reset or power cycle. Due to the wide range of options and the possible values assigned to these options, the sections that follow describe each option and later describe the values you can assign (a hexadecimal number, a yes or no entry, and so on).

To see the current configuration for these parameters, use the dspndparms command. For information on the alarms that might relate to the parameters, see the dspndalms and dspenvalms descriptions.

Maximum Card Resets

The first two options work together to prevent an endless loop of card resets. The first option specifies the number of seconds for counting resets. The second option is the number of resets.

• Option 1 lets you select the sliding window of time for counting the resets of the shelf management cards. The characteristics of the time period option are:

– The unit of measure is seconds.

– The number is a 16-bit decimal number with a range of 0–65535.

– A 0 means an infinite time period. The impact of an infinite time period is that only a specified count of resets can stop the resets.

– The default is 3600 seconds (1 hour).

• Option 2 lets you select the maximum number of resets of the shelf management card group for the configured time period. Its characteristics are:

– The number is an 8-bit decimal number with a range of 0–255. The meaning of a 0 for this parameter is an infinite number of resets—the resets can continue indefinitely.

– The default is three resets per time period.

Shutting Off Alarms for Absent Core Cards

This option lets you specify whether a redundant core card that is removed from the backplane causes an alarm. (The core cards are the PXMs and SRMs.) The option lets you turn off alarms until you reinstall the card.


OL-11771-03


Enable Expanded Memory for 250K Connections

This option lets you enable expanded memory on the PXM45 to support 250K connections. For you to enable expanded memory, a pair of PXM45/Bs or PXM45/Cs must reside in the system.

Caution This option cannot be disabled after it is enabled, even if you use the clrallcnf command.

Required Power Supply Module Bitmap

Through a bitmap mechanism, this option lets you specify the locations of required power supplies in an AC-powered system. If any one of the required supplies is removed, an alarm results. (For related information on alarms, see the dspndalms and dspenvalms descriptions.) Additional supplies can also exist in the power supply tray, but removing one of the additional supplies does not cause an alarm.

An AC power supply tray can hold up to six power supplies. A supply belongs to one of two groups of slots in the power supply tray: A1–A3 or B1–B3. Within the bitmap, an 8-bit hexadecimal number identifies a required supply. The A side of the tray is represented by the least significant hex value. The B side of the tray is represented by the most significant hex value. The map is the sum of the hexadecimal numbers. For example, the bitmap for requiring A1 and B1 is:

0x01 + 0x10 = 0x11

Required Fan Trays

This option lets you specify the required fan trays. The application of this setting is for alarm generation only and does not specify cooling requirements. For example, if you specify that the chassis must have two fan trays but one tray is missing, an alarm is generated. You can turn off fan tray alarms by specifying that no fan trays are required (even though at least one is required for cooling). The value is an 8-bit hexadecimal number.

Note An Cisco MGX 8850 or Cisco MGX 8950 chassis requires two fan trays for cooling regardless of the number you specify for alarm purposes with the cnfndparms command.

• 0x0 means no fan tray requirement. (The chassis must still have at least one fan tray for cooling.)

• 0x01 refers to the bottom fan tray.

• 0x02 refers to the top fan tray.

To require top and bottom fan trays, for example, enter a hexadecimal 3 for the option value:

0x01+0x02=0x03

Trap Manager Aging Timeout

This option lets you specify the number of hours that a trap manager can age before the switch deletes that trap manager’s registration. This setting is node-level and thus applies to all trap managers registered on the switch. The default of 0 means that the trap managers on the switch do not age. The only applicable trap managers for this parameter are Cisco WAN Manager (CWM) workstations.

The application of aging is a situation where:

• The IP address of the network management stations are likely to change.

• The workstations themselves are likely to be moved.

Non-CWM users or managers of a stable network manager environment should leave the setting at zero.


OL-11771-03


Primary IP Interface for Network Management

This option lets you specify a primary IP interface type for discovery by CWM. The primary IP interface is the first choice for CWM to use for network management. The main purpose of this option is to let you change from the default of an ATM interface to a LAN interface for use by CWM. The choice of LAN as the primary lets you use LAN interfaces to build an IP connectivity infrastructure for CWM. CWM discovers this interface type while it performs an ILMI MIB-walk or during a topology table retrieval.

The topology table contains the primary and secondary management interface information for all nodes in the network. CWM obtains this table from one of the nodes so that it does not have to perform an ILMI MIB walk to each node in the network.

Secondary IP Interface for Network Management

This option enables CWM to learn the secondary IP interface by doing a MIB-walk and reading the PNNI topology state element table. If the primary IP interface becomes unreachable, CWM uses the secondary IP interface. If you do not enable the secondary IP interface, the PNNI topology state elements (PTSEs) do not flood the secondary IP address.

The topology table contains the primary and secondary management interface information for all nodes in the network. CWM obtains this table from one of the nodes so that it does not have to perform an ILMI MIB-walk to each node in the network.

Automatic Setting of Cell Bus Clock Speed for RPM

This option lets you enable the automatic setting of cell bus clock speeds for the Route Processor Module-Premium (RPM-PR). If you enable this feature, the switch automatically adjusts the cell bus clock as needed when you insert or remove an RPM-PR at a particular cell bus. If this feature is enabled, for example, and two RPM-PRs are plugged into a cell bus, the clock speed is 42 MHz. If you remove one RPM-PR, the clock drops to 21 MHz.

The cell bus clock rates must be correct for the RPM-PR to do traffic shaping. If clock setting is not automatic, you must adjust the clock speeds by using the cnfcbclk command when needed. To see whether automatic or manual clock setting is enabled, use the dspcbclk command.

If you turn on this feature and one or more service modules are running at 42 MHz, the clock for all such cards immediately becomes 21 MHz, regardless of the number of cards in the switch.

Caution Enable this feature before using two MPSM-8-155s, two RPM-PRs, or one of each of these cards on the same cell bus. For example, slots 3 and 4 are on the same cell bus, and slots 5 and 6 are on the same cell bus.

Inband Node-to-Node IP Connectivity

This option lets you enable or disable inband, node-to-node IP connectivity, so that you can Telnet from the CLI of one switch to the CLI of another switch.

After you Telnet, an SVC is set up between the local node and the remote node. (The SVC is the transmission medium for all IP traffic between two nodes, yet the SVC and Telnet are independent of each other; the Telnet is just one kind of traffic.) If you disable this feature after the SVC is created and then proceed to transfer more IP data between nodes, the transfer of IP data is successful. In fact, it works without disruption until the SVC is torn down. The SVC is torn down when no IP traffic traverses the SVC for 15 minutes.


OL-11771-03


To exit the CLI of the remote switch—to break the connection and terminate the Telnet session—enter the exit or bye command (see the “Example” section on page 89).

This parameter is enabled by default after you run the clrallcnf command. On the other hand, if you upgrade from a software release that does not have this parameter, the default state is disabled.

PXM Switchover on Back Card Mismatch

When enabled, this option causes a switchover of redundant PXMs if the incorrect, field-replaceable back card (FRU) is inserted. The existence of various models of the PXM45, variations in the PXM1Es, and two models of the user interface (UI) back card have led to the creation of an option that lets you specify that if the incorrect combination is detected, the redundant pair switches over. Table 13 lists supported and disallowed combinations. Yes indicates a supported combination; No indicates a mismatch.

Disabling the High-Priority LCN for Interprocess Communication

This option lets you disable the high-priority LCN so that the applications exchanges all messages on the low-priority LCN.

The switch reserves two logical connection numbers (LCNs) for interprocess communication (IPC)—in this instance, the communication between applications on different cards:

• One LCN carries low-priority messages

• The other LCN carries high-priority (urgent) messages.

By default, both priorities of LCN are available, and the cards select the priority for messages as needed.

Disabling Telnet Access

To disable Telnet access to this switch, type yes when prompted. This option lets you disable Telnet access to the switch so that only the Secure Shell (SSH) utility can be used to access the switch from either a workstation or another Cisco MGX 88xx or Cisco MGX 8950 switch. Telnet is an unsecured access method because its communication uses clear text. SSH ensures secure communication by providing unique encryption for each session.

Disabling Unsecured Access

By default, the switch permits unsecured access from Telnet and FTP clients, and secure access from SSH and SFTP clients. To disable unsecured access from Telnet and FTP clients, set the Unsecured Access to Node Disabled option to yes.

Table 13 Supported and Mismatched PXM and UI Card Combinations

Controller PXM-UI-S3 PXM-UI-S3/B

PXM45/A Yes No

PXM45/B Yes No

PXM45/C No Yes

PXM1E with R7000 processor

Yes1

1. Supported, but we recommend that you avoid this combination.

Yes

PXM1E-8-OC-3 No Yes


OL-11771-03


Changing the Unsecured Access to Node Disabled option from:

• no to yes automatically changes the Telnet Access To Node Disabled option to yes.

• yes to no has no affect on the Telnet Access To Node Disabled option.

Option Values

This command requires various number formats for the support of its parameters:

• Boolean yes/no

• An 8-bit decimal has the range 0–255.

• A 16-bit decimal number has the range 0–65535.

• A 32-bit decimal number has the range 0–4294962795.

• An 8-bit hexadecimal number has the range 0–0xff.

• A 16-bit hexadecimal number has the range 0–0xffff.

• A 32-bit hexadecimal number has the range 0–0xffffffff.

Each option description states the type of number involved and the actual range for that option. Alternatively, the description states whether the choice is yes to enable or no to disable.

Syntax

cnfndparms <option_number> <option_value>

Syntax Description for PXM45

option number

This number selects the option.

Range: 1–15

Option 1 Option 1 is the number of seconds that the controller counts resets of the shelf management cards. A 0 means an infinite time period. The impact of an infinite time period is that only a specified count of resets can stop the resets.

• Range: 0–65535 seconds

• Default is 3600 seconds (1 hour)

Option 2 Option 2 is the maximum number of resets of the shelf management card group. See Option 1 for the period in which resets are counted. The meaning of a 0 for this parameter is an infinite number of resets—the resets can continue regardless of how many resets occur.

• Range 0–255 resets

• Default: 3 resets

Option 3 This option lets you enable or disable core card redundancy. Enter yes to enable or no to disable alarms on a missing, redundant core card. The default is enable, which means an alarm appears in the absence of a redundant core card.

Option 4 This option lets you enable or disable expanded memory on the PXM45/B or PXM45/C to support 250K connections. Enter yes to enable or no to disable. The default is no.

Note You cannot disable this option after it is enabled, even if you use the clrallcnf command.


OL-11771-03


Option 5 This option lets you specify the locations of required power supplies in an AC-powered system. The number is 8-bit hexadecimal:

• 0x0 (the default) means no specified power supply requirement related to this particular form of alarm generation (although the configuration must still meet the power requirements of the switch).

• 0x01: PSU A1 is required.



• 0x10: PSU B1 is required.



Option 6 This option lets you specify the location of one or more required fan trays. The number is 8-bit hexadecimal:

• 0 for no specific fan try requirement

• 0x01 for bottom fan tray required

• 0x02 for top fan tray required

Option 7 This option lets you specify the number of hours that a trap manager can age before the switch deletes that trap manager’s registration. This node-level setting applies to all registered trap managers. For details, see the “Trap Manager Aging Timeout” section on page 83.

Option 8 This option enables CWM to learn the primary IP interface by doing a MIB-walk and reading the PNNI topology state element table. Enter a number in the range 0–2:

• 0: The ATM0 interface is the primary.

• 1: No interface is used. This choice prevents ILMI node discovery.

• 2: The lnPci0 interface is the primary.

Default: ATM

Option 9 This option enables CWM to learn the secondary IP interface by doing a MIB-walk and reading the PNNI topology state element table. Enter a number in the range 0–2:

• 0: The ATM0 interface is the secondary.

• 1: No interface is used as the secondary.

• 2: The lnPci0 interface is the secondary.

• Default: lnPci0 (LAN)

Option 10 This option lets you enable the automatic setting of cell bus clock speed. In the current release, it applies to RPM-PR only. The choices are yes and no.

Default: yes

Option 11 This option lets you enable inband, node-to-node IP connectivity so you can Telnet between this CLI and other switches where this feature is enabled. Type yes to enable or no to disable.

Default: yes (enabled)

Option 12 Obsolete. Use dsprcons for Gang Card Status.


OL-11771-03


Related Commands

dspndparms, dspndalms, dspenvalms, cnfcbclk, dspcbclk

Attributes

Option 13 This option enables automatic switch-over when a FRU back card mismatch occurs. Type a 1 to enable or a 0 to disable this feature. This option applies to the combinations of controller card models and the user interface (UI) back card. Refer to the section, “PXM Switchover on Back Card Mismatch,” for information on the combinations.

Default: 0 (disabled).

Option 14 This option lets you disable the high-priority LCN for inter-process communication (IPC) between cards. Type yes or no:

• yes: the card-to-card, high-priority LCN is not used. This choice forces all IPC traffic between cards to share the same, low-priority LCN and prevents applications from sending urgent messages or critical data over a high-priority connection to applications on other cards.

• no: the card-to-card, high-priority LCN is used. This choice allows applications to choose the appropriate priority for carrying IPC traffic between cards. An application with a purpose for sending urgent or critical data selects the high priority LCN (if both cards support the high-priority LCN). Other messages take the low priority LCN as needed.

Default: No

Option 15 Type yes to disable Telnet access to this switch. Type no to enable Telnet access.

Default: no (Telnet access is enabled)

Option 16 Type yes to disable unsecured access to this switch, either Telnet or FTP. Changing this option from no to yes automatically changes Option 15 to yes. Changing from yes to no has no affect on Option 15.

Default: no (Unsecured access is enabled)

option value The option value can be a decimal or hexadecimal number or a yes or no entry. The following shows the possible ranges or values for each type of numeric option.

• 8-bit decimal: 0–255

• 16-bit decimal: 0–65535

• 32-bit decimal: 0–4294962795

• 8-bit hexadecimal: 0–0xff

• 16-bit hexadecimal: 0–0xffff

• 32-bit hexadecimal: 0–0xffffffff

Log: no State: active Privilege: SUPER_GP


OL-11771-03


Example

Specify 30 minutes (1800 seconds) for Card Reset Sliding Window. You can enter the option number and option value without prompting. The system subsequently uses the parameters and shows the result.

MGX8850.7.PXM.a > cnfndparms 1 1800NODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------

1 1800 16bit Decimal SHM Card Reset Sliding Window (secs)

Enable automatic setting of cell bus clock speed. Type the cnfndparms command without parameters to see all of the options, and then enter 10 and y at the subsequent prompt. This card is a PXM45. Afterwards, see if it is enabled by using the dspcbclk command.

M8850_SF.7.PXM.a > cnfndparmsM8850_SF System Rev: 05.02 Feb. 11, 2006 05:48:41 GMTMGX8850 Node Alarm: CRITICALNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs) 2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 No Boolean Core Redundancy Enabled 4 No Boolean Expanded Memory Enabled for 250K connections 5 0x0 8bit Hex Required Power Supply Module Bitmap 6 0x0 8bit Hex Required Fan Tray Unit Bitmap 7 0 8bit Decimal Trap Manager Aging timeout value(Hour(s)) 8 atm0 8bit Decimal Primary IP interface for Netmgmt 9 lnPci0 8bit Decimal Secondary IP interface for Netmgmt 10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled 11 Yes Boolean Inband Node-to-Node IP Connectivity Enabled 12 0 8bit DecimalObsolete. Use dsprcons for Gang Card Status 13 0 8bit Decimal Card Switchover on Back card FRU mismatch 14 No Boolean Card-to-Card High Priority LCN Disabled 15 No Boolean Telnet Access To Node Disabled 16 No Boolean Insecure Access(Telnet / Ftp) To Node Disabl

Enter option number (1-16): 10NODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled Enable/Disable Automatic Cellbus Clock Rate Setting. If option set to: Yes: Automatic Setting Enabled. This allows for automatic determination of cell bus clock rate depending on the insertion and removal of cards such as RPM in the shelf. No: Automatic Setting Disabled. This prevents automatic determination of cell bus clock rate. Manual manipulation must be performed using the cnfcbclk CLI command.

Enter value for option 10 (Y/N): YNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled


OL-11771-03


dspndparms

Display Node Parameters—PXM45, PXM1E

The dspndparms command displays the node parameters that were configured by use of the cnfndparms command. The node parameters in this case are a general set of diverse parameters. Refer to cnfndparms for a description of the parameters and their possible values.

Note The PXM45 has more node parameters than the PXM1E. For example, the PXM45 has expanded memory for 250K connections.

Syntax

dspndparms

Syntax Description


Related Commands

cnfndparms

Attributes

Example

Display the current node parameters on this Cisco MGX 8850 switch with a PXM1E card.

PXM1E_NY.7.PXM.a > dspndparmsPXM1E_NYSystem Rev: 05.03 Feb. 13, 2007 14:37:03 PSTMGX8850Node Alarm: MAJORNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 No Boolean Core Redundancy Enabled4 0x0 8bit Hex Required Power Supply Module Bitmap5 0x0 8bit Hex Required Fan Tray Unit Bitmap6 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))7 atm0 8bit Decimal Primary IP interface for Netmgmt8 lnPci0 8bit Decimal Secondary IP interface for Netmgmt9 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled10 Yes Boolean Inband Node-to-Node IP Connectivity Enabled11 0 8bit Decimal Obsolete. Use dsprcons for Gang Card Status12 0 8bit Decimal Card Switchover on Backcard FRU mismatch13 No Boolean Card-to-Card High Priority LCN Disabled14 No Boolean Telnet Access To Node Disabled15 No Boolean Insecure Access(Telnet / Ftp) To Node Disabl



OL-11771-03

MGX Release 5.4.30 Limitations, Restrictions, and Notes

Display the current node parameters on this Cisco MGX 8850 switch with a PXM45.

M8850_SF.7.PXM.a > dspndparmsM8850_SFSystem Rev: 05.03 Feb. 13, 2007 14:59:19 PSTMGX8850Node Alarm: MAJORNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 Yes Boolean Core Redundancy Enabled4 No Boolean Expanded Memory Enabled for 250K connections5 0x0 8bit Hex Required Power Supply Module Bitmap6 0x0 8bit Hex Required Fan Tray Unit Bitmap7 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))8 atm0 8bit Decimal Primary IP interface for Netmgmt9 lnPci0 8bit Decimal Secondary IP interface for Netmgmt10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled11 Yes Boolean Inband Node-to-Node IP Connectivity Enabled12 0 8bit Decimal Obsolete. Use dsprcons for Gang Card Status13 0 8bit Decimal Card Switchover on Backcard FRU mismatch14 No Boolean Card-to-Card High Priority LCN Disabled15 No Boolean Telnet Access To Node Disabled16 No Boolean Insecure Access(Telnet / Ftp) To Node Disabl

Changed AXSM-XG Commands

The addlmi command changed to permit XLMI configuration. It no longer returns an error message for that configuration. For more information, see Routing Enhancement for AXSM-XG Cards, page 23.

MGX Release 5.4.30 Limitations, Restrictions, and NotesThis section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.4.30.

Upgrade LimitationNone.

BERT LimitationIf you configure the BERT with an excess information rate (EIR) value of 2 (for 1 in 10), any configuration changes or BERT failure that could cause BERT to go out of sync will cause the BERT state to remain out of sync until you stop and restart BERT.

MGX Voltage Measurement LimitationVoltage sensing for the Cisco MGX 8850, Cisco MGX 8830, and Cisco MGX 8950 switches monitors the A1/B1 power circuits only. Therefore, if the A1/B1 power module is missing, the entire unit reports 0 volts for the A/B circuits, even though other power modules are present and working.


OL-11771-03


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

Bandwidth Limits

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

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

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

• Each half of the lower bay can support total OC-6 aggregate cell bus bandwidth.

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

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

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

Card Placement Guidelines

Placement of the MPSM-T3E3-155 is important because of the total card capacity. Other narrow band cards also use cell bus capacity, but they have smaller bandwidth requirements and place less load on the backplane.

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

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

• Install no more than 4 active MPSM-T3E3-155 cards in one Cisco MGX switch.

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


OL-11771-03


Bandwidth Oversubscription

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

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

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

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

PXM1E Switch LimitationsThe following notes apply to PXM1E based switches—Cisco MGX 8850 (PXM1E) and Cisco MGX 8830:

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

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

• MPLS controller is not supported on PXM1E.

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

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

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

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

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

The CBCs cannot load share to achieve OC-10 with one cell bus set at an OC-6 rate, and another cell bus set at an OC-4 rate. Traffic above the OC-6 rate is dropped. However, if only one CBC is used and the other CBC is not used, then the CBC can achieve an OC-10 rate.

On a Cisco 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 a Cisco MGX 8830, CBC0 supports slots 3, 5, 10, and 12 and CBC1 supports slots 4, 6, 11, and 13. Balance traffic by evenly distributing cell-based cards on the left and right sides of the chassis.


OL-11771-03


PXM1E Hardware Limitations

PXM1E hardware limitations are as follows:

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

• During hardware upgrade from PXM1E-4-155 to PXM1E-8-155, at the time when the inserted card types are different (one PXM1E-4-155 card set and one PXM1E- 8-155 card set), the standby trunk back card functionality is not available. Therefore, LED functionality is not available, and APS lines do not work on that back card. Modular optical transceiver (SFP-8-155) mismatches are not reported for that back card, and SFP-8-155 mismatches are not reported during hardware upgrades.

• Because the PXM1E-4-155 and PXM1E-8-155 back cards support LC and SC interfaces respectively, the following restriction applies when upgrading from PXM1E-4-155 to PXM1E-8-155 hardware:

After replacing the first PXM1E-4-155 card with the PXM1E-8-155 card set, update cabling for the PXM1E-8-155 interfaces with an LC-SC converter.

Similarly, after the second card set is replaced, perform the same update for the interfaces on the new card set. Otherwise, the upgrade is not graceful and becomes service affecting, until appropriate cables are installed.

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

• When MGX-8850-APS-CON is used, the Combo card and the PXM1E-4-155 card do not require a mini-backplane, but the PXM1E-8-155 does. Therefore, to support graceful upgrade to the PXM1E-8-155 card in the future, insert a mini-backplane with the PXM1E-4-155.

PXM1E Reserved Virtual Channel Identifiers

You cannot provision the following reserved VCIs:

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

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

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

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

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

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

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

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

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

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

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


OL-11771-03


PXM1E Point to Multipoint Support

Point-to-multipoint connections support new real-time and non-real-time applications, for example LAN emulation, distance-learning, live broadcasts, financial data delivery (stock market feeds), white board collaboration, video conferencing, data and file replication, and video on demand.

Multipoint enhances network efficiency because multiple streams of data can be replaced by a single transmission up to the multicast distribution point, typically an MGX with PXM45. Point-to-multipoint differs from broadcast because it replicates packets only to specific destination endpoints in the multicast distribution tree.

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

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

PXM1E Parity Errors

The PXM1E handles parity errors as follows:

• If the PXM1E card has a CBC CBH RAM parity error and all connections do not have traffic, then the PXM1E card fails to detect this parity error and does not switch over to the standby card. Also, all service module cards reset.

• The PXM1E standby card comes up even after a QE TS RAM parity error.

PXM1E Policing Accuracy

The PXM1E card has a policing accuracy limitation. The policing rate is defined as 50000000/PCR, so if the PCR is comparable to the OC-12 line rate (1412830), the policing rate parameter is a relative small number (50000000/1412830 = ~35.38996).

Because the PXM1E performs integer division, the decimal results are truncated and the policing parameter is not calculated accurately. Moreover, the policing rate parameter is stored as an exponent (5 bits) and mantissa (9 bits), which cannot represent a small number accurately. Therefore, a 100 percent accurate policing parameter cannot be configured for large PCR values.

To ensure that you obtain the rate that you have specified, the software configures policing at the next larger rate that the hardware supports. For example, if you program a connection with PCR = 1400000, the software programs the policing rate to be 1428571. For a worst-case scenario, if you configure a VBR2 connection with a PCR of 1400010 and the ingress user traffic is 1428570, there is no policing because the ATM policing rate is actually 1428571.


OL-11771-03


PXM45 and PXM1E System LimitationsThe following limitations apply to PXM45 and PXM1E systems:

• Because of granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured PCR rate when WFQ is enabled. For connections that have WFQ enabled, configure a PCR of 101 percent of the required rate. ABR has the same Qbin priority as UBR in the SCT tables. In this case ABR and UBR share excess bandwidth if WFQ is enabled.

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

– (overbooked MaxCR – overbooked ACR)/overbooked MaxCR. This occurs if you are interoperating with SES from Release 3.0.x and later.

– ACR = MaxCR – (trunk utilization/overbooking factor).

– overbooked ACR = ACR/overbooking factor.

– overbooked MaxCR = MaxCR/overbooking factor.

• The overbooked ACR is calculated differently for MGX and SES.

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

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

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

• The PXM45/A card is not supported in Release 5.0.00 and later.

• Disable complex node for physical nodes (the lowest level node) to decreases memory usage without decreasing functionality. Complex node should only be turned on for logical nodes.

• Simple Network Timing Protocol CWM MIB is not supported.

Maximum Threshold Accuracy

The PXM45 and PXM1E have a limitation with the accuracy of the maximum threshold. The Qbin threshold and VI rate are stored in the form of exponent and mantissa, and some accuracy is lost in expressing the real rate. In testing the thresholds, the lack of accuracy is compounded with both of the Qbin and VI rate (draining rate). Therefore, you cannot calculate an exact 100 percent correct discard rate.

To ensure that you obtain the rate that you have specified, the software configures Qbin depth at the next larger rate that the hardware supports. As a result, Int. Cell Gap (ICG) and Relative Service Delay (RSD) are truncated.

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

These notes apply to redundant cards.

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

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


OL-11771-03


SPVC Interoperability Limitations

SPVCs have the following interoperability limitations:

• NNI SPVC Addendum Version 1.0 is not supported.

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

• Terminating single-ended SPVCs on MGX switch with legacy service modules is not supported.

• Origination of single-ended SPVCs, with slavepers flag, from legacy service modules (FRSM, CESM, and RPM) is not supported.

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

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

• The tstdelay command is not available at the slave end of a single-ended SPVC for Cisco MGX 8850. For SES-PNNI, the command is available from the PXM even for the slave endpoint.

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

• If single-ended SPVCs originate from MGX switches, they can only be configured from the CLI and not from CWM.

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

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

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

• Override of SVC connections on a VPI because of an incoming SPVP request for that VPI is not supported. Only the following override options are supported:

– spvcoverridesvc

– spvcoverridesvp

– spvpoverridesvp

Service Card LimitationsThis section describes service card limitations.

AXSM-16-155-XG with MCC Back Card Limitations

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

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

From the CLI window on the side of APS added, the only way to find out if the remote APS has been added is through the Receive chanfield and modefield in dspapsln. The following display shows the APS status during configuration:


OL-11771-03


For GR253:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS (with MCC):


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

For ITU (or AnnexA):



After adding remote APS:



For AnnexB:



After adding remote APS:

Receive k2 chanfield—Working Section 1 or 2


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

The following notes apply to the AXSM-32-T1E1-E and PXM1E-16-T1E1 cards:

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

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

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

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

• Only 10 SVC calls per second is guaranteed.

• FDL support for Loopback code detection is not supported.

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

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

• IMA Autorestart (persistent RX IMA ID) feature is supported.

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

• ITC clocking mode on IMA is not supported.


OL-11771-03


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

• There is 5 ms fluctuation on IMA delay tolerance.

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

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

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

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

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

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

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

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

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

AXSM-E Card OAM Limitations

The following notes apply to AXSM-E OAM cells:

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

• The AXSM-E card can receive up to 1,500 segment OAM loopback cells per second for all connections operating in the normal mode (not loopback), assuming an even flow rate. Any excessive segment OAM loopback cells are dropped.

For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and each connection passes one segment OAM loopback cell per second, then only 1,500 of the connections can receive loopback cells at any given second. The additional 500 loop back cells are not received for that second.

General AXSM Card Limitations

If ER stamping is used, the rate interval does not provide sufficient accuracy to be completely effective. As a result, when an AXSM card has a PNNI link that is congested with mixed CBR/ABR traffic, cells are dropped. This condition only occurs when ER stamping is enabled and CI is disabled on an AXSM PNNI link where CBR/ABR traffic causes congestion on the link.

Use the CI/EFCI mechanism for rate feedback rather than the ER stamping mechanism, especially if CBR/ABR traffic is expected.

AXSM-XG Signal Level Limitation

The IR/LR/XLR SFP modules need a 10 db attenuator when connected with short cables. Otherwise, the signal overloads the receiver.


OL-11771-03


ATM Multicast Limitation

Configure an Cisco MGX 8950 with ATM multicast as follows:

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

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

A Cisco MGX 8950 system with a mix of AXSM-XG and AXSM/B cards is not recommended for the ATM multicast application because of limitations in the backplane serial buses. The workaround for Cisco MGX 8950 systems that must have a mix of AXSM-XG and AXSM/B cards is to configure the PNNI node as branching restricted.

cnfpnni -node 1 -branchingRestricted on.

Priority Bumping Limitation

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

AXSM Card APS Limitations

Thee APS feature has the following limitations:

• For AXSM APS, the back card of the active card must be present for correct APS operation.

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

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

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

MPSM Card Limitations

The MPSM cards have the following limitations:

• The MPSM-T3E3-155 card does not support the LMI Autosense feature.

• The MPSM-8T1-FRM and MPSM-8E1-FRM cards do not support the LMI Autosense feature.

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


OL-11771-03


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

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

• If you order MPSM cards with systems, the MPSM licenses can be shipped on the PXM card. For more information about MPSM licensing, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00.

MPSM-16-T1E1 Card PPP Limitation

On the RPM-XF, Rated Priority Queue is not supported; SAR based QoS is enabled instead. The traffic on priority queue can exceed the limit even if the class-based weighted fair (CBWF) queues are relatively free. RPM-XF supports absolute priority only, where the upper limit on the traffic is layered using the policing command.

CBSM Card Limitations

Cell Bus Service Modules (CBSM), formerly known as narrowband service modules, have the following limitations:

• When you enter the switchredcd command at the same time as a PXM switchover occurs, either through the switchcc/resetcd command at the PXM or because of a failure, the switchover can fail.

Conditions: switchredcd is entered at the PXM command line to perform CBSM Switchover, but the PXM switches over (manual or automatic) before the service module switchover is complete.

Symptom: Service module did not switch over after switchredcd.

If the PXM switches over before the CBSM switchover completes, the following can occur:

– The switchover might not be complete and the standby card is in an indeterminate state. The dspcd command from PXM still shows it as 'standby' and later switchover (because of active service module removal or reset) fails, causing loss of traffic. The switchredcd command also fails.

– The switchredcd from PXM again causes the failure because the standby service module is not able to allocate memory.

Workaround: Reset the standby service module card.

• Each CBSM has the following maximum number of connections:

– FRSM-8 = 1,000

– FRSM-2CT3 = 4,000

– FRSM-2T3 = 2,000

– FRSM-2E3 = 2,000

– CESM-8 = 248


OL-11771-03


IGX Feeder Limitation

After adding an IGX as a feeder to a SES/BPX or MGX node, the IGX has a default node number that might not be unique within the network. If the number is not unique, modify it to a unique node number by entering rnmnd <x>, where x is unique with respect to all other AutoRoute nodes. To find the other node numbers, enter dspnds +n. Failure to assign a unique number could cause the CWM Databroker to incorrectly form a hybrid connection database. The CWM interface might show the connection as incomplete.

Clock Source Limitations

Service modules have the following clock source limitations:

• The AUSM card supports one clock source only. Attempts to configure the secondary clock fail silently.

• The FRSM card does not support clock source configuration. Attempts to configure the clock source are not recorded in the database.

• When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. Recommitted means that the primary and secondary get requalified. The node temporarily uses the internal oscillator until the clock is requalified, and then locks onto the primary clock source again.

Clearing Card Configuration Notes

The clear service module configuration feature has the following behavior:

• Do not execute clrsmcnf on more than one card at a time.

• If a controller card switchover occurs before the clear service module configuration operation is complete, the clrsmcnf command must be re-entered to ensure that the configuration is completely cleared and to avoid incomplete cleanup.

• The clrsmcnf command might result in a discrepancy in the PNNI configuration. For example, some connections might be in the mismatch state.

• If the clrsmcnf command is entered with the <all> option to clear the software version for the slot as well, then cell bus service modules enter the boot/empty state and broadband service modules (for example, AXSM or MPSM-155-T3E3) enter the fail/active state.

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

PNNI LimitationsThis section describes limitations to PNNI links and routing.

Logical Link Limits

The number of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is enabled. The limit is essential to reduce the processing time for finding the bypasses between the logical links. A significant change in bandwidth in one of the links within the peer group triggers the bypass calculation. The bypasses are usually found from one logical link to another.


OL-11771-03


If there are n logical links, the calculation involves the finding n*n bypasses. If the number of logical links n is large, calculating the bypasses requires significant processing resources. The number of logical links can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.

Preferred Route Limitations

Preferred routes have the following limitations:

• Preferred routes are not supported for connections with endpoints on the RPM-PR.

• Upgrading from any Release 3.0.x is nongraceful. During the upgrade, the preferred route identifier information for each connection is lost, and the preferred route identifier must be reprovisioned on the service module cards.

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

• When a connection is routed on a route other than its preferred route and if the preferred route becomes available, the connection is not automatically routed back to its preferred route. You must deroute and reroute using configuration commands (optrte, rrtcon, dncon/upcon, and so on). QoS precedence over the preferred route does not apply to multipeer group networks (CSCdz40310).

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

• Preferred route status is supported in Release 5.0.00 and later. After an upgrade, manually reconfigure using commands like cnfcon. This step is necessary one time after the upgrade, and does not need to be repeated on subsequent upgrades.

Priority Route Limitations

Priority routing has the following limitations:

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

• The RPM does not support configuration of routing priority. The PXM assigns a priority of 8 to all RPM-mastered SPVCs.

• The addcon command on SES does not support routing priority; all added SPVCs are assigned a routing priority of 8. Use the cnfcon command to change the routing priority of the SPVCs.

• Changing the routing priority for DAX connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if only the endpoint parameters are changed, and routing priority is an end-point parameter. Also, because DAX connections are never derouted even when the UNI port stops responding and the rrtcon command does not support DAX connections, the routing priority change never gets reflected. The only way to reflect this change is to enter a dncon and then upcon. Because DAX connections are never derouted, the effect of this limitation is void.


OL-11771-03


• 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 travel along two different paths.

– Under congestion, releases can be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the congested interfaces. The calls that were not released could be higher priority calls.

• Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can occur after several failed attempts to route higher priority SPVCs. To prevent starvation of lower priority SPVCs after these failures, the software starts to route lower priority SPVCs and postpones higher priority SPVCs routing.

Persistent Topology Limitations

The persistent topology feature has the following limitations:

• In a mixed network of pre-Release 4.0.00 and 4.0.00 or later nodes, only the node name and the node ID are shown for a pre-Release 4.0.00 node in the topology database. 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 topology database. 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 topology database.

• To delete a node information entry from the topology database:

a. 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 1 hour.

b. Delete that node from the topology database. Perform this step because even if a node is removed from the topology database of all nodes in the peer group, its PTSEs remain stored in the other nodes until they are flushed from those nodes. This happens within 1 hour, but it is configurable as a PNNI timer value. If the node is deleted from the topology database within 1 hour, and the node performs a switchcc/reboot, then it is possible that the node information for the deleted node is added back into the topology database.

• When the node ID of a node is changed, the old node ID is added back into the topology database as a new node entry. In addition, the old node ID still is stored in the topology database 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 database of all the nodes in the peer group. Then, delete the information of the old node ID from the topology database.

• Some gateway nodes are not in sync in a peer group. This could occur 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 information for the deleted node does not appear 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, you must delete the node information from all of the nodes in that peer group including the non-gateway-node nodes. Otherwise, the node information for the deleted node remains in the non-gateway-node nodes. This could cause inconsistencies later if this node is configured to be a gateway node.


OL-11771-03


Fault Isolation and Trace LimitationsThis section describes fault isolation and trace limitations.

Serial Bus Path Fault Isolation Limitation

The Serial Bus Path Fault Isolation feature isolates errors on local cards only. However, when a common error occurs on the switching fabric card, this feature does not resolve the error. As a result, a problem on the PXM card or the XM-60 is reported by all cards that detect the symptoms of this problem.

Cell Bus Path Fault Isolation and Recovery Limitations

Cell bus path fault isolation has the following limitations:

• The isolation procedures can isolate the cell bus path in the serial bus service modules (for example, AXSM, AXSM/B, AXSM-E) and all communication with the standby controller card and the cell bus service modules (for example, FRSM, CESM). These procedures cannot isolate cell bus path failures involving the ATMizer SAR, which is used for all intercard communication except polling, between the active controller card and the serial bus based service modules.

• The isolation procedures can isolate the cell bus path failures to the active controller card only. This isolates the active controller card faults for the intercard communication over the cell bus from the active controller card to the service modules and the standby controller card. It does not isolate the fault if the active controller card fails to communicate with some cards and successfully communicates with the rest on the cell bus.

• At least two cards (two service modules or one service module and one standby PXM) must exist to isolate cell bus path failures to the active controller card.

• Only failures that are detected by periodic polling trigger the isolation procedures. Failures reported from other sources in the system about a service module or the standby controller card, due to the cell bus path failures, do not initiate the isolation procedures. Such failures reset the card for which the failure is reported, even while the active controller card is in the process of isolating the cell bus path failures triggered by the polling failures.

• No separate trap or alarm is generated for the active controller card cell bus path when the fault is isolated to the active controller card. Use the event logs to investigate events triggered by the card reset and switchover traps.

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

Path and Connection Trace Notes

The path and connection trace features have the following limitations:

• Path trace is not supported on the control port.

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

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

• Path and connection trace supports point to point connections.

• Path and connection trace supports MPG (multipeer group) and SPG (single-peer group).


OL-11771-03


CLI Access Level NotesConfiguration of CLI access levels has the following limitations:

• Not all CLI command access levels can be changed and a command cannot be changed to CISCO_GP group access level.

• Only the switch software can generate the access level binary file. This file has an authentication signature which must be validated before the file can be used. Any manual changes to the file make the file void.

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

• Command names are verified, but an invalid command name might be parsed and be added to the binary file. However, this invalid name is ignored later.

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

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

Disk Space Maintenance NotesThe firmware does not audit the disk space usage and remove unused files, so you must manually manage the disk space in C: and E: drives.

Manually delete unused saved configuration files, core files, and firmware files and the configuration files of the MGX-RPM-PR-256/512 and MGX-RPM-XF-512 cards. This avoids a shortage of disk space for storing event logs.

To remove files from the active controller card:

Step 1 Change to the directory that needs grooming.

CLI: cd <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


OL-11771-03

Installation and Upgrade Procedures

Non-native Controller Front Card and PXM-HD Card Notes

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

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

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

• The system keeps only the two most recent copies of the saved system configuration in the C:/CNF directory. You can use FTP to transfer all of the saved configuration files in C:/CNF to a local server for future reference. All files under C:/CNF are not replicated to the standby controller card under any circumstances.

Other Limitations and RestrictionsOther limitations and restrictions are as follows:

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

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

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

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

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

• Configuration information is not synchronized between PXMs during upgrades. You must reboot the standby PXM after it enters a stable state to synchronize changes made during the upgrade.

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

• The BPX does not support NCDP.

Installation and Upgrade ProceduresThis section defines the supported upgrade paths and the associated installation and upgrade procedures.


OL-11771-03


Supported Upgrade PathsTable 14 lists the supported upgrade paths.

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

Upgrade InformationThe upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00 contains the following procedures:

• Graceful PXM1E and PXM45 Boot Upgrades

• Nongraceful PXM1E and PXM45 Boot Upgrades

• Graceful PXM1E and PXM45 Runtime Software Upgrades

• Nongraceful PXM1E and PXM45 Runtime Software Upgrades

• Graceful Service Module Boot Upgrades

• Nongraceful Service Module Boot Upgrades

• Graceful Service Module Runtime Software Upgrades

• Nongraceful Service Module Runtime Software Upgrades

• Graceful RPM-PR and RPM-XF Boot Software Upgrades

• Graceful RPM-PR and RPM-XF Runtime Software Upgrades

• Nongraceful RPM-PR and RPM-XF Boot Software Upgrades

• Nongraceful RPM-PR and RPM-XF Runtime Software Upgrades

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

Table 14 Supported Upgrade Paths

Desired Software Supported Release

Release 5.4.30 5.4.10

5.4.00

5.2.10

5.3.00

5.3.10

5.3.20

Release 5.3.00 or 5.3.10 5.1.20 and later




OL-11771-03


Upgrading AXSM-XG CardsThe following notes apply to AXSM-XG card upgrades:

• Before you install AXSM-XG cards, use Table 15 to verify that the node is running a compatible software release.

Note Do not attempt to downgrade the AXSM-XG cards to releases earlier than supported.

• 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 virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header limitations.

For information about graceful upgrade of AXSM-XG cards, see the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00.

Upgrading the VISM-PR ImageIf you upgrade the VISM-PR image to Release 3.2.1x or later, and upgrade the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, do so in this order:

1. Upgrade the VISM-PR cards.

2. Upgrade the PXM1E or PXM45 cards in the same node.

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

Maintenance InformationThe upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.4.00 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.

Table 15 AXSM Card Compatible Software Releases

Card Software Release When First Supported

AXSM-1-9953-XG Release 4.0.00





OL-11771-03

Open Caveats

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

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

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

To perform online insertion or removal in privileged exec mode:

Step 1 Enter hw-module slot <slot> stop

Step 2 Perform online insertion or removal.

Step 3 Enter hw-module slot <slot> start

To perform online insertion or removal in configuration mode:

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

Step 2 Perform online insertion or removal.

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

Open CaveatsTable 16 shows the open Caveats in Release 5.4.30:

Table 16 Open Caveats in Release 5.4.30

Caveat ID Description

CSCek50447 Headline: IMA links fail while adding local or remote loopback.

Symptom: IMA links fail while adding local or remote loopback.

Condition: Add local or remote loopback on an IMA link using cnfpath on the corresponding path. The IMA link goes into failed state.

Workaround: Remove local or remote loopback and restart IMA group.

Hardware: MPSM155.


OL-11771-03

Resolved Caveats

Resolved CaveatsThis section contains the resolved caveats in the following releases:

• Release 5.4.30, page 112












CSCso75994 Headline: Errors logged when online diagnostics are enabled.

Symptom: Online diagnostics enabled on PXM or MPSM causes error logs to appear on PXM.

Condition: Enable online diagnostics on PXM or MPSM using cnfdiag command.

Workaround: None.

Hardware: MPSM155.

CSCsq25099 Headline: Optrte not running on all configured ports

Symptom: Optrte not running on all configured ports. Logs indicate some of the ports are kicking off optrte, however others do not appear to be running.

Condition: Ports configured for route optimization which have had their port on the SM, and the pnport downed on the PXM45 appear to be affected.

– Grooming configured on the port(s).

– Dnport on SM or dnpnport.

– Upport on SM or uppnport.

Workaround: There are two workaround for this issue:

1. Perform a switchcc.

2. Manually re-enable route optimization on the affected port(s). There is no need to disable optrte before re-enabling it.

Example: cnfrteopt <pnport> enable

Hardware: MPSM155.

Table 16 Open Caveats in Release 5.4.30 (continued)



OL-11771-03

Resolved Caveats


Release 5.4.30Table 18 shows the resolved caveats in Release 5.4.30.

Table 17 Resolved Caveats in Release 5.4.30


CSCso63651 AXSM-XG shows inaccurate CONN stats as huge numbers

CSCsq21932 Command dspimalnks -grp <grpNum> does not display all links in the grp

CSCso89727 Cannot modify vci range on a partition if there is SPVP on that port

CSCso66680 Unable to CC to MPSM card after executing IMA commands

CSCso30460 VSICORE: VsiErr:Conn Add to VSI DB Error log message coming in dsplog

CSCso75994 Errors are logged when online diagnostics enables

CSCso77632 Sempahores handling in MPSM 155

CSCso70794 cnfsnmp community string is not working when already having special char

CSCso77647 Not getting values in several dspchancnt counters

CSCso77588 dspimagrpalmcnt NE and FE failure counters out of sync

CSCso16959 The lmi operation resumes after resetting the card when the port is down

CSCso64160 Unable to execute cnfsnmp command due to illegal symbol after switchover

CSCso57801 Command dspsnmp shows no Community (ro) after runrev

CSCso55165 ICR limit is not specified in cnfabr command

CSCso05095 Command clrportcnt does not clear Rcv Frame Last Unknown DLCI

CSCso17012 Refreshing is not done properly after corrupting with different modes

CSCsj52098 cnfatmln fails due to S/W error

CSCso22572 SNMP walk aborts if RxLID in the IMA group is not in order

CSCso12225 Command dspload is not handling partition 0

CSCir01575 IMA group goes into startup state when one end conf to different ver

CSCso20051 Card resets on inducing VCT errors when card has one ended connections.

CSCsl32139 Command dspchassis shows incorrect value for Supports FEEDER functionality

CSCsk80285 AXSM: splitting the QE DB error threshold template

CSCek63549 Invalid ATM addresses seen in dsppnni-inducing-uplink

CSCso22693 After VCT refresh traffic stops flowing through connections

CSCso15099 Suspicious "commit failed" log messages are shown in dsplog

CSCso16751 Refresh complete log message is not coming in dsplog

CSCso15287 Suspicious CPU log messages are occurred in dsplog

CSCso20056 DAX connections cannot be made on two AXSM cards having same images

CSCir01571 Local loopback on an APS line getting reflected on disabled line

CSCsm45067 AXSM1/B QE48 VCT0 soft memory error


OL-11771-03

Resolved Caveats


CSCsj13099 Non-PGL node is showing up in the entire network as upnode

CSCsk90200 When a user changes the account password, it changed the password of another user

CSCsl72050 -alm option in dsppaths is not working properly

CSCsm87561 BRAM diag failure on PXM45

CSCir01322 MPSM16-FR: CLI shows up lines after executing dspchancnt cmd with -r & q

CSCsm26186 MPSM lose traffic on both direction

CSCsl26532 Bad PXM clock source from AXSM-XG if wrong cnfclksrc sequence

CSCsm59410 AXSME APS not behaving correctly for channel mismatch

CSCsj77551 OPNEXT OC192 Transponder fails when APS occurs

CSCsl79205 Incorrect no of FR ports in the output of dspln

CSCsk38474 AXSMXG OCP SFP not detected in AXSMXG

CSCsm32292 No response for dspchancnt/clrchancnt in AXSM

CSCsl09851 PAP login does not work

CSCsm73618 Several tasks are hanging on mutex semaphore

CSCin97455 The output of the command dsptech does not stop after pressing Q<CR>

CSCir01477 Block using the existing ip add for ipifconfig cli as telnet session hangs

CSCsk76056 Event CTC-4-CTC_INVALID_CD logged for PXM1E during upgrade.

CSCsm50673 Undetected VCT parity errors on standby AXSM causes outage after switchover

CSCsm34739 Memory errors reported

CSCsm39604 IMA related events causing memory leak

CSCsq31286 Cannot add or change SNMP passwords after restorecnf

CSCsq45009 PPP links go down with code fixes for online diags.

Table 17 Resolved Caveats in Release 5.4.30 (continued)




CSCeh91015 If QE errors are seen multiple times, add an action on QE Errors to reset PXM

CSCei47617 Line errors increasing on SRMEB T3 card while in loop

CSCej49510 scmMyCdMgmtPathOK() is not able to find problems in some situations

CSCek48987 Switchcc on PXM1E causes 1:N SMs to reset

CSCek54553 dspcdsct/dspportsct vcThr does not show correct result

CSCek55957 The Version fall back effect is not reflected after changing IMA version from 1.1 to 1.0

CSCek57255 Not able to clear SNMP contact and location text using the command cnfsnmp location/contact on MGX45


OL-11771-03

Resolved Caveats

CSCek57659 PXM1E node cannot synch up with secondary CWM

CSCek57680 On PXM1E node, the MPSM16-T1E1 card reports failed state

CSCek57978 SNMP associate frame MPSM PVC to preferred route fails

CSCek58022 RPM: Enhance debugging in IOS IPC code on PXM

CSCek58072 clrimalncnts does not work for MPSM16T1. Works on MPSMT3E3

CSCek58139 RPM-XF cannot access the drives X and C

CSCek58181 On PXM45/C with UI S3/B cards, the Ethernet interface locks up

CSCek58209 MPSM (16T1E1 and T3E3-155) do not display the VSI-Sig CosB in their SCTs

CSCek58333 Auto-restart state is not synched up on MPSM-16T1E1

CSCek58354 MPSM16 shows wrong RX TRL while synching up with 7200 CPE

CSCek58605 MPSM16-IMA dspimagrp is not showing the correct FE Tx clock mode

CSCek59557 The CAC failure on AXSM-B is reported as failure of MPSM card

CSCek59576 MPSM-155-T3E3 cards stuck in the init state after executing the resetcd of active MPSM card

CSCek60078 The zeroCIR connection feature on MPSM155 does not work. Traffic does not pass through the zerocir connection

CSCek60224 When active AUSM cards in MGX1E node were replaced, the connections and ports are lost

CSCek60419 After addrred the active MPSM cards does not de-register with PXM master agent

CSCek61039 Excessive delay on MPSM16-IMA links while enabling or disabling the local line loop

CSCek61149 Cell loss on VBR1-rt SPVC

CSCek61638 The PXM-1E is not checking SM feature on FRSM

CSCek61866 Statistics for AXSM-XG is not correct

CSCek61936 The MPSM16 dspimalnk shows wrong IMA link failure alarm

CSCek61938 The cnfcli access level does not work for some commands

CSCek61940 When scrambling is disabled on 7200, the MPSM16-IMA links do not recover automatically

CSCek62198 Changing the Agg token leads to an extra entry with link in attempt state in the dsppnni-link output

CSCek62310 Long latency in ABR connection when VSVD is on

CSCek62755 The trap 50008 from MGX1E does not match the MIB definition

CSCek63709 The display units of AXSM-OC12-XG SCT are not consistent with the CWM SCT manager units

CSCek63714 AXSM0C3-XG is flooded with alarms of Section Level defects

CSCek65566 The REI-L Line level defects are not captured in performance monitoring bins

CSCek65625 On AXSMXG, the LOF is not counted in the SEFS and SES performance monitoring bins

CSCek65662 The AXSMXG path level defects are not captured on performance monitoring bins

CSCek65940 SNMP interface should not support csConfigLoopbackType in path level

CSCek65950 Unable to modify RPM connection when VT is greater than 25




OL-11771-03

Resolved Caveats

CSCek66386 On MPSM-16-T1E1 card, the IMA Group is displaying wrong Auto Restart Sync state as Loopback Sync even though the Tx IMA ID is different on both sides of the IMA Group

CSCek67022 AXSMXG 0C3/OC12 line loop should not be allowed when APS is configured

CSCek67243 The cnfsnmp and snmp queries to RPM during the switchredcd fails

CSCek67471 The Command dumpalllogs should be removed from the list because it is not implemented

CSCek68183 Extra SVC seen on standby card, and card reboots with CAC fail error

CSCek70535 The AXSM-XG 0C-12 card fails and the APS switch message is vague

CSCek70866 dsplns shows major alarm when APS is configured

CSCek71275 PXM45/C with H2FPGA CAM shows Image Version as 2 in dspdevrev

CSCek71538 Core dump on cokega20 slot 9 AXSM_4OC12_B and dsperrhist shows ILMI Module critical Error

CSCek71688 An spvc provisioned with VPI/VCI 4095/65535 is not seen in dspcons

CSCin98875 The command cnfapsln does not show the -w option within the card

CSCir00569 The command dsphotstandby shows path DB mismatch errors

CSCir00684 The MPSM IMA alarms are not clearing even after correctly configuring the IMA groups

CSCir00710 The command dspportload is not showing the Ingress cell rate of CLP1 traffic

CSCir00849 The counters in dsplnalmcnt is not incrementing

CSCir00934 FR port provisioning with dsx1E1UNFRAMED allow2s 56kbps port speed

CSCir00958 The Clock mode is not reflected on remote end when changed through cnfimagrp

CSCir01063 IMA Group fails after configuring the autorestart feature

CSCir01068 When an ATM port is added on a line having dsx1AMI line coding, the line is goes into critical state

CSCir01109 Enhance the PPP link negotiation trace to print echo reply and option type when unsupported option is received.

CSCir01128 The command dspimalnks does not work with -grp option

CSCir01141 After MPSM155 upgrade to 5.3(0.200), IMA port connected to the CPE is not coming up

CSCir01153 The command dspimalnks displays huge value for Rel Delay

CSCir01207 Unable to add redundancy between AUSM with the same feature displayed

CSCir01269 Missing connection statistics for stat-ids 18,19,36 and 37

CSCir01433 On MPSM16, the IMA UNI and NNI ports does not show egress IMA traffic statistics

CSCir01434 MPSM155 cards reset due to PRM-PHPI communication failure

CSCir01473 The command syntax missing for cnfpart CLI in AXSM and XG cards

CSCir01511 dsppathalmcnt and snmpget on sonetMedium MIB broken

CSCir01541 The dsppath with wrong path format works fine on SDH path

CSCir01556 The dsppnni-bn-path and dsppnni-bypass always shows direct link

CSCir01609 CPRO error messages are seen for AXSMXG-OC12 and AXSMXG-OC3

CSCir01643 If no connection exist on the card, dspvsipart prints command failed




OL-11771-03

Resolved Caveats

CSCir01649 SCM connection statistics for XG are not correct as compared to CLI o/p

CSCir01743 Card goes into empty reserved after doing multiple resets

CSCir01758 Memory leak due to 2 PGL

CSCir01775 Alarm severity mismatch between AXSMXG and PXM

CSCir01792 Critical and major hardware errors do not cause AXSMXG to reset

CSCir01847 On AXSM-XG the alarm state of the line is clear but port state is down

CSCir01848 The command dsplns gives confusing display when secondary card is active

CSCir01894 The elapsed time does not increase after switchredcd

CSCir01913 Elapsed time counter shows unknown for dsplnalmcnt and dsppathalmcnt

CSCsi33863 The MPSM card resets after lots of switchcc in stress testing

CSCsi34078 Unexpected offline diag test for MPSM runs the next day

CSCsi34086 PXM resets with exception while configuring group with read view

CSCsi50439 On AXSM-16-155 XG, the command dspatmlayercnt does not show RX valid RM cells count

CSCsi72251 On AXSM-XG-0C3, the command tstdelay results in timeout on all connections

CSCsi78610 Path statistics showing huge value

CSCsi97844 snmpEngineID is not unique after upgrading to 5.4 image

CSCsj01602 Traps are not sent if boot IP is 0.0.0.0

CSCsj10384 ASXM-XG QMC Memory Threshold Setting

CSCsj18221 Switchcc or Runrev issued on MGX45 node resulted in secondary NBSM to change to blocked state

CSCsj30401 Connection provisioning will be rejected when the IMA group corresponding to an IMA port have all the links in alarm

CSCsj41333 The command dspimagrpsbwupd does not show proper display

CSCek69501 On an AXSME card, the option –len for the command cnfln DS3 does not work on DS3




OL-11771-03

Resolved Caveats

Release 5.4.00Table 19 shows the resolved caveats in Version .202 of Release 5.4.00.

Table 20 shows the resolved caveats in Versions .200 and .201 of Release 5.4.00.

Table 21 shows the resolved caveats in Release 5.4.00.

Table 19 Resolved Caveats in Version .202 of Release 5.4.00


CSCsi34086 PXM resets with exception when configuring group with read view.

CSCsi97844 snmpEngineID is 09 followed by all 0 on upgrade

CSCsj01602 traps are not sent if boot IP is 0.0.0.0

Table 20 Resolved Caveat in Versions .200 and .201 of Release 5.4.00


CSCek71275 PXM45/C with H2FPGA CAM shows as Version 2 in dspdevrev.



CSCek36145 MPSM8 in gives incorrect mismatch reason for incorrect back card

CSCek37677 dspmpbundlecnt discard field is incrementing without any act discard

CSCek40319 Notification should be sent when core redundancy is enabled/disabled

CSCek60078 MPSM155 zeroCIR connections have some issues

CSCek55957 Version fallback enabling using cnfimagroup is not reflected

CSCek58650 AXSM Protect Line Stuck in SF

CSCek59576 MPSMT3E3 cards in sl 5 and 6 stuck in init after resetcd on sl 5

CSCek60419 addred register standby MPSM card

CSCek62310 Cells stuck in VC_Q to cause long latency in ABR con with VSVD on

CSCek61989 ATM index not sent in case of traps

CSCek62198 Change in agg token results in an extra entry of H/z link in attempt

CSCek62755 Trap 50008 from MGX1E does not match MIB definition

CSCek61039 #13857 Excessive delay on IMA links when ena/disabling loc line loop

CSCek61149 Cell loss on VBR1-rt SPVC

CSCek61638 PXM-1E not checking SM feature on FRSM

CSCek61866 STATS for AXSM not correct

CSCek61936 MPSM16 dspimalnk shows wrong IMA link failure alarm

CSCek61940 MPSM16-IMA links not recovering automatically when scrambling enable

CSCek63714 AXSM0C3-XG is alarm flooding on Section Level Defects


OL-11771-03

Resolved Caveats


CSCek65625 AXSMXG LOF not counted in SEFS and SES

CSCir01141 After MPSM155 upgrade to 5.3(0.200) IMA port not up connected to CPE

CSCir01173 Trap 60633 contains ifType instead of mfrBundleIfIndex

CSCir01269 Missing connection stats for stat-ids 18,19,36 and 37

CSCir01354 Parallel swithovers on AUSM & FRSM 1:N red set

CSCir01520 Switchover denied for BULK mode

CSCir00203 Add CWM Support for new HDD (PXM_HDD_V)

CSCir00655 TIMER-ROLLOVER: Config upload may be influenced by ticks wrap around

CSCir00656 TIMER-ROLLOVER: wrong AIR values seen in dspchancnt and stats file

CSCir00657 TIMER-ROLLOVER: dspcduptime and dsprmrsrcs shows wrong card uptime

CSCir00658 TIMER-ROLLOVER: config copy resynch request is delayed

CSCir00661 TIMER-ROLLOVER: OAM processing continues after timer window is over

CSCir00685 mask value not seen after doing switchcc twice

CSCir00697 TIMER-ROLLOVER: pnni nbr counter not updated during rollover

CSCir00698 TIMER-ROLLOVER: PNNI PTSE processing improper during ticks rollover

CSCir00700 TIMER-ROLLOVER: PNNI hello processing improper during ticks rollover

CSCir00701 TIMER-ROLLOVER: PNNI timer processing delayed during ticks rollover

CSCir00702 TIMER-ROLLOVER: CPRO RAM disk write delayed during ticks rollover

CSCuk61119 Portscan on PXM reveals unused open ports

CSCir01068 line with AMI coding going into critical state with atm port added

CSCir01101 snmpwalk on AXSM cards shows ifOperStatus as UP always

CSCir01128 dspimalnks command does not work with -grp option

CSCir01153 dspimalnks display huge value for Rel Delay

CSCir01212 NEP: Hardware Mastership error on doing resetsys





CSCeb74271 HARD: NonFatalMajorError is not generated when VXWorks MemPart Exhaustion

CSCef52036 Line stats on Channelized T3/E3 line incorrect

CSCei07549 Enhancements to cnfatmlayer to allow configuring null cell parameter

CSCei47617 Line error increasing on SRME/B T3 while in loop

CSCek29124 Interoperability problems with connection trace


OL-11771-03

Resolved Caveats

CSCek29555 MPSM line alarms then port failure on softswitch then recovers

CSCek31881 Cannot execute addchanloop. Error in programming HW.

CSCek33616 ABR VPC connections not able to burst up to PCR

CSCek37837 delchanloop cause traffic route to incorrect slot

CSCek38109 After upgrading from 5.1 to 5.2 CBR conns go into conditional alarm state

CSCek38266 IMA group between MPSM155 and Nortel box does not come up

CSCek38904 UT08928: SSO feature enhancement for max config

CSCek39024 Set CLR_EFCI to zero on ingress

CSCek39539 Min CLR values for all service types set to 0 for ports on AXSM XG

CSCek39917 Mixed/bad clock config on an MPSM IMA port to stop passing traffic

CSCek42173 For SCT 5&6, ingress cells on OC3 port for PXM1E are flagged invalid

CSCek44492 CWM sync failed after slot 8 took over

CSCek45058 Upgrade from 5.2 to 5.3 on MPSM-PPP is causing the memblock corruption

CSCek41560 MGX PXM45 trap field in Hex instead of String

CSCek46566 MGX command cnfpasswd cannot change password using ssh

CSCek46752 Disk Partition space for partition D on PXM45

CSCek46987 Get many reported unknown values for ifAdminStatus

CSCek48985 AXSME switchredcd caused both cds to reset, fail

CSCek48987 PXM1E switchcc caused 1:N SMs to reset

CSCek49789 SWSW should block addapsln when AXSM-A/B line is in loopback

CSCek50066 PXM dspndparms opt 12 shows 0 when a gang card is in place

CSCek50387 ACI FIFO Full count increments rapidly sometimes

CSCek51244 PXM45/B rests due to software error reset.

CSCek51943 Standby PXM1E back card went to mismatch (APS was configured)

CSCek52818 PXM1-E dspdiagstatus shows cardstate unknown, and idle

CSCek53357 MPSM 16T1E1: subobj should be 20 for T1 line and 21 for E1 line

CSCek54333 MPSM-T3E3-155: dspimalnkbucketcnt incorrect after clearing

CSCek54514 AXSME custom SCT port sct showing as cisco sct

CSCek54550 dsperrhist does not display latest entry

CSCek54553 dspcdsct vc Thr does not show correct output

CSCek56614 Incorrect MIB Information with regard to trap sent

CSCek57659 PXM1E node cannot sync with secondary CWM

CSCek57680 MPSM16-T1E1 stuck in Failed state

CSCek57978 SNMP Associate frame MPSM PVC to pref route fails

CSCek58072 clrimalncnts does not work for MPSM16T1, works on MPSMT3E3

CSCek58181 Lock-up of Ethernet interface of PXM45/C with UI S3/B cards




OL-11771-03

Resolved Caveats


CSCek58333 Auto-restart state not synced up on MPSM-16T1E1

CSCek59557 CAC failure on AXSM-B, reported as MPSM card

CSCin89871 dspload is not showing used b/w when port is oversubscribed

CSCin98875 cnfapsln does not -w option

CSCin99001 MPSM 16T1E1 card in standby goes to failed after resetcd in 1:N red

CSCin99057 Default payload scrambling not adhering to the standards in MPSM

CSCin99058 verifydiskdb reports discrepancies btw primary and standby PXM

CSCin99359 UT08915: CONFIG_TIMER expd: lnkNum xxx logs on switched (SSO code)

CSCin99481 dspchancnt on XG-OC12 does not accept -r <interval> option

CSCin99532 Node lost inband connectivity with mbuf allocation failed log

CSCin99610 IMA group between PXM1E/AXSM-E and Nortel passport does not come up.

CSCin99721 Statistical alarms not declared in some situations

CSCir00016 Log LODS and LIF IMA events into PXM log.

CSCir00017 Display maximum observed delay on LODS links.

CSCir00134 MPSM unable to add sct number greater than 255

CSCir00149 PPP traps should have logical slotNum in OID entPhysicalParentRelPos

CSCir00222 MPSM sends 2 backcard insertion traps when it comes up.

CSCir00228 MPSM-IMA: Issue seen on dng dn and up IMA grp vth PNNI links and configs

CSCir00386 pppLinkStatus needs to be clarified for PROTO_DOWN condition

CSCir00592 Unable to add port after cnfautorestart

CSCir00684 MPSM IMA alarms are not clearing

CSCir00708 60561 and 60562 IMA related traps are not generated on MPSM16T1E1

CSCir00710 dspportload is not showing the ingress cell rate of CLP1 traffic

CSCir00849 The counters in dsplnalmcnt not getting incremented

CSCir00870 Secondary MPSM not taking over when primary is in active-f

CSCir00958 Clock mode not reflected on remote end when changed through cnfimagrp





CSCek30585 Trap parameter not matching ENTITY-MIB

CSCek35153 No traps generated when Lan cable is removed from Standby PXM45C

CSCek38785 Disk Partition space insufficient to support upgrade of 7 VXSMs


OL-11771-03

Resolved Caveats

Release 5.3.00Table 24 lists the resolved caveats in Release 5.3.00.

CSCek39067 The word backplane to be replaced by chassis in CLI show inventory

CSCek40639 Upgrade to 5.2 or greater causes AW parameter set to default

CSCek44255 Impedance mismatch on SRME-3 Y cable - CAB-BNC-Y/B

CSCek45997 PXM45 reroute timer triggered when interface was down

CSCek47955 PXM45C fails/resets when receiving ABR call setup w/PB and filters

CSCin98500 Enabling SM self test on Standby SMs and enhancing self-test

CSCir00215 PXM45/C fails after programming HDD model name





CSCeh20665 AXSM-XG NVRAM gets corrupted

CSCeh93023 Standby card reset for RAM sync error during line/path decommission

CSCei82475 CLP 0 discards on ABR connections when intvsvd is enabled

CSCej35237 Connection provisioning blocked in MPSM16 if line 1.1 has no port

CSCej37652 PXM1E back card went to mismatch after switchcc when APS was configured

CSCej42146 UBR.2 policing is not consistent across AXSM-A/B/E and AXSM-XG

CSCej43114 1:N switchover fail due to SNMP sub agent registration failure

CSCej46233 Buffer overflow error when addlnloop on a ds3 ln

CSCej48242 SES controller reset when multiple cnfcon issue through CLI

CSCej48854 Discrepancy between dspportcnt and dspcdcnt

CSCej48870 Switchredcd causes bundle mismatch and DiskDB mismatch error on MPSM

CSCej48888 dspcdcnt showing discards when online diag is enabled

CSCej49448 MER+:Invalid PTI-7 cells not incremented at MPSM-OC-3 dsp command

CSCej49460 log showing NVRAM Failed and Checksum errors for SRME

CSCej49510 scmMyCdMgmtPathOK() is not able to find problem in some situations

CSCej50880 MER+: AXSM-OC-3 not incrementing ingress invalid cell counter

CSCej71362 MIB table dsx3CurrentTable is not populated for AXSM-T3 card

CSCej72907 MIB tables for AXSM-OC-3 current line, path, SONET counters not populate

CSCej84077 connection trace is not standards compliant

CSCej88834 SSI-4-MEMBLKERROR messages are flooding the log file

CSCej89464 dsppathalmcnt -vt: Elapsed time is empty

CSCek01600 dsppathalmcnt:Elapsed time needs to be populated


OL-11771-03

Resolved Caveats

CSCek04078 card should print timestamp on console at boot time

CSCek04197 VISM remote SCR value needs be updated with local SCR value

CSCek05366 MIB walk looping in dsx3CurrentIndex

CSCek15048 Need to disable 64K mode for MPSM-8-FR with AMI coding

CSCek15086 Need to disable 64K mode for FRSM-8 with AMI coding

CSCek16312 SNMP ERROR THROWN FOR MPSM-16T1E1 CARD ENABLING IN SCM

CSCek16369 Need to disable 64kbps mode for AMI coding on MPSM-16

CSCek17853 PNNI and connections down after Resetsys on 1:N MPSM Setup

CSCek19998 Output of dspparts on MPSM is not aligned

CSCek22538 MPSM-T3E3-155 FR policer discarding CIR compliant traffic

CSCek23561 Addred should block 1:N MPSM-8T1E1 when both PRI and sec slot active

CSCek23624 Online Diagnostics fail to run on secondary slot of 1:N in Active State

CSCek23839 dspload CLI displays data of wrong partition in AXSM-A/B

CSCek24836 AXSM-XG switchredcd causes local loops to be lost

CSCek25166 VXSM upgd from R2.0MR > R2.5 w/o calls + nightly PXM image > 120 sec

CSCek25468 CTC-2-INTERNAL_EVENT and CTC-4-INVALID_TIMEOUT errors on Sec. Card.

CSCek26117 PXM45 should close 17185 socket port to avoid possible DoS Attack

CSCek26489 MPSM-OAM: high latency and OAM cell drops on MPSM155

CSCek26491 MPSM-OAM: Enhancement to OAM cells processing

CSCek26498 dspmpbundlecnt showing huge values after adding and deleting link

CSCek27990 cnfpath on MPSM-OC-3 should show 1 for bay and 1 & 2 for line

CSCek28155 SRME stats file includes peak value for bucket interval = 5 min

CSCek28316 CWM can not do conntrace more than 5 times

CSCek28933 remove redundant message with inconsistent info on CLI dspln ?

CSCek29029 While doing switchredcd LICE-4-ERRORWITHDATA messages getting logged

CSCek29587 Wrong bay and line value range on switchapsln

CSCek29989 SRM_3T3 going to Failed/Empty state after addlink to line 4 slot 13.

CSCek30340 SNMP get for axisImaGroupNumRxActLnks gives incorrect value

CSCek30374 dynamic bandwidth feature is not kicked in after runrev on pxm.

CSCek30597 snmpwalk on AXSM-4-2488-XG and AXSM-1-9953-XG loops at cssLOSs

CSCek31110 dumpconfigs does not provide dsplns or dspports on pxm1e

CSCek31112 addppplink shows help in T3E3 path ID format on OC-3 mode

CSCek31207 dspppplink output on E1 lines showing wrong value for physicallineid

CSCek31682 Humvee errors generated on dn/up ppplinks

CSCek31840 Inconsistencies between Switch CLI and SNMP for ATM port creation

CSCek32867 56 and 64 kbps speed ppp link should not be allowed on same bundle




OL-11771-03

Resolved Caveats

CSCek32869 PVC bw btw MPSM and XF is not correct when the ds0 speed is 56 kpbs

CSCek33223 AXSM, dsplcment -plcp errors increases when line configured as ADM

CSCek33812 Inconsistency of dspchancnt -r -max display for fr, atm mode in MPSM

CSCek33927 Loadrev to be blocked on card in FAILED state.

CSCek35302 Standby mpsm16t1e1 shows false PPP alarm

CSCek35892 Mismatch state not detected on PR on changing conn parmts on one end

CSCek35922 IPC buffers for traps are not available when we have max. config

CSCek36143 WIN11593: MPSM16:Performance when Mux enabled is less compared to Ph1

CSCek36821 Traffic does not pass from AXSM/B in 8950 after upgraded to 5.2

CSCek36879 switchcc causes active VISM calls to drop

CSCek37495 Default NormPvcBw for E1 links has to be modified

CSCek40639 Upgrade to 5.2 or greater causes AW parameter set to default

CSCin90687 Tx frame length editable to invalid values for IMA Release 1.0

CSCin97536 cnfilmi CLI does not display syntax of the command

CSCin97888 Cannot ccc to AXSM card

CSCin97891 Not able to transfer file on multiple sftp sessions

CSCin97895 SSH session does not timeout even after timer expires

CSCin97955 MPSM16T1E1 card reserved for RBBN-16T1E1 does not enter Mismatch

CSCin98000 SNMP query not working when Secondary RPM is active

CSCin98080 Fractional ports Operational State does not go down.

CSCin98407 Error in description of ciscoWanSpvcFailTrap (70009)

CSCin98539 Slips and dropped pings with AMI configured on MPSM

CSCin98544 STAT-4-ERROR error message logged while upgrading

CSCin98562 cnfpath on mpsm-oc3 card shows incomplete vales for STS option

CSCin98606 The ATM0 SPVC comes up very slowly after resetsys

CSCin98702 SNMP port open fails on Secondary card

CSCin98862 Clear SRM config even if redundancy is enabled

CSCin98897 dspsct shows WFQ_ENB value as NULL instead of n/a for card sct

CSCin98908 dsplog shows Invalid parameters pass in !! Max par=4

CSCin98957 dsplnalms command on AXSM-XG card gives invalid error message

CSCin99015 PVC PCR/SCR not updated on changing normpvc value

CSCin99018 DB2C-4-DBCLNT_RECVMSG errors logged while upgrading 5.2(10.32)A

CSCin99097 addapsln displays inconsistent help string

CSCin99163 Erroneous behavior on repeated execution of cnfcdmode on MPSM-T3E3

CSCin99183 SLT: dspspvcaddr does not display the addresses in sorted order

CSCin99212 SNMP subagent task gets suspended after a wrong value snmpset




OL-11771-03

Resolved Caveats

Release 5.2.10Table 25 lists the caveats that were resolved in Version .201 of Release 5.2.10.

Table 26 lists the resolved caveats in Release 5.2.10.

Table 25 Resolved Caveats in Version .201 of Release 5.2.10

Identifier Headline

CSCek30597 snmpwalk on AXSM-4-2488-XG and AXSM-1-9953-XG loops at cssLOSs

CSCek31375 UDI compliance of 8830/B chassis required


Identifier Headline

CSCed61774 First bulk mode line in temp LOS after SRM/SRME switchover

CSCed89128 MPSM8 Minor IMA alarm not reported on PXM with dspcds

CSCee06096 Unused MPSM FR/CES PAR interfaces shown up after resetsys

CSCee07604 Couple XBAR and HMM_ events clean-up

CSCee47346 MPSM-ATM does not send FRM, BRM until 1 cell of data is sent

CSCeh53982 The dsp feature allows disabling of IMA feature which is wrong info

CSCeh72899 Wrong OIDs populated for Xmt CLP0 and CLP1 cells

CSCeh77872 MPSM-155: Incorrect default SONET Tx path trace string

CSCeh85523 Display needs change. Err:failed to access or program HW.

CSCei21340 Configuration option is needed for alarm integration time in AXSMA/B

CSCei35633 Paths fail after switchredcd is issued on MPSM0C3

CSCei44706 dspload shows nonexistent partition info for AXSMB card

CSCei59862 ILMI goes down when traffic is stopped

CSCei61908 Slips and dropped pings with AMI configured on MPSM

CSCei75053 pnniport interface stuck in building VC for AXSMXG-OC-12 card

CSCej15496 AXSM-XG OC-3 FRUs not detected consistently

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

CSCej35237 Connection provisioning blocked in MPSM16 if line 1.1 has no port

CSCej37652 PXM1E back card went to mismatch after switchcc when APS was configured

CSCej42146 UBR.2 policing is not consistent across AXSM-A/B/E and AXSM-XG

CSCej46233 Buffer overflow error when addlnloop on a DS3 line

CSCej53700 LMI failure between MPSM -8t1e1 & Router due to LMI sequence no. mismatch

CSCej71362 MIB table dsx3CurrentTable is not populated for AXSM-T3 card

CSCej72907 MIB tables for AXSM-OC-3 current line, path, SONET counters not populated

CSCej82475 CLP 0 discards on ABR connections when intvsvd is enabled

CSCej84077 connection trace is not standards compliant


OL-11771-03

Resolved Caveats


CSCej89464 dsppathalmcnt -vt: Elapsed time is empty

CSCek01493 Connection goes into alarm for NNI-NNI interface

CSCek24836 AXSM-XG switchredcd causes local loops to be lost

CSCin91349 Version, h/w rev, and other info not shown in MIB in FRSM-2E3 card

CSCin94473 Invalid data exception while associating SCT file with card/port

CSCin96562 MER+: AXSMXG-OC192 is throwing EM-4-EM_ERROR while doings dsppaths

CSCin96877 MER+: IMA BW reduction does not result in reroute of CBR connection

CSCin97305 LMI failure between MPSM & Router due to LMI sequence no. mismatch

CSCin97474 SFM DB shows wrong file size on disk of the stat file


Identifier Headline


Identifier Headline

CSCeg29002 Stuck with free running clock on PXM1E.

CSCeg37735 CutW tasks can cause high CPU use resulting false alarm generation.

CSCeg47129 REG5.1 Resetsys cause the remote nodes (AXSM-XG OC-3) pnniport in down

CSCeg53512 REG5.1 Standby pxm gone to failed state after switchcc and saveallcnf

CSCeg59069 CCMA fails to transition to active

CSCeg68920 PXM reset when console receives external script containing %n

CSCeh00187 Avg CPU utilization goes up to 82% for OC-3 card running at 44 cps

CSCeh01295 Need to increase the VC/Cos/SG thresholds for SAR connections.

CSCeh02198 12-DT:Igress dest. slot bandwidth DB audit fails after up/dn port

CSCeh03624 2 sec additional latency for IPCP to converge

CSCeh05887 12-DT: SCT 500s files are corrupted

CSCeh11515 AXSM-XG does not discard Unassigned cells on SPVP with VPI = 0 (OC-3)

CSCeh12738 Mask off byte 127 of packet memory I2C

CSCeh13430 12-DT: All sscops stuck in reset; ipc msg allocate fail after xg reset

CSCeh18475 Connection down and rerouted after APS Pline removed (AnnexB only)

CSCeh23166 fail to detect SD = 9 when SD was set to 9 on APS line

CSCeh32190 AXSM-E OC-12 core dump upon delpart MPLS and PNNI partitions

CSCeh40420 SES: Coding Standard Bits in Call State IE are incorrectly set

CSCeh44896 Following a switchcc primary clock lock state shows free run on PXM1E

CSCeh62582 PXM1E combo fails E3 pulse mask


OL-11771-03

Resolved Caveats

CSCeh62878 HW Para: PXM1E combo fails E3 AIS response

CSCeh65399 12-DT: Redundant xg cards stuck in init after switchover

CSCeh71950 Upgrading FRSM HS2B DTE line cause line alarm.

CSCeh91015 Add an action on QE Errors to reset PXM if seem multiple times

CSCeh93732 SSI exception error on axsm-xg. It is in sunni core dump area.

CSCeh95399 Loop timing on AXSM-XG-OC-3 cause CV LOF on remote end

CSCei13826 Cannot switch from ausm to MPSM after adding mpsm as redundant card

CSCei14150 Conn goes into mismatch on MPSM after switchreds missing on PXM

CSCei14239 T3E3 IT: full throughput traffic caused redundancy switchred issues

CSCei16136 AXSM fails E3 AIS response

CSCei23845 MPSM stuck in failed state after resetcd script

CSCei23863 Traffic loss in both directions; IPCP is in acksent

CSCei29441 CLI blocks adding 1:1 redundancy on MPSM-T3 with RCON in quadrant

CSCei33337 Memory leaks after deactivating/activating a non-existent bundle

CSCei36072 AXSM-XG-OC-12: Coredump on the card

CSCei37771 dspcd on AXSM-XG shows negative #SVC after pulling FRUs.

CSCei38749 One end of MPSM line in LOF other end shows clear

CSCei40399 MPSM-16-T1E1—Config mismatch between PRM and PHPI fatal error during upgrade

CSCei44593 cnfpart failed with cannot modify LCN range due to configured conn

CSCei46236 IMA Groups and Links Disappeared After Running Scripts

CSCei50321 AXSM-XG Core Dumps After Performing switchred

CSCei52004 DaxCon between AXSM-XG <-> RPM-XF failed tstdelay/ping

CSCei55066 Mixed mode legacy cards redundancy with MPSM-8T1E1 should not be allowed

CSCei62648 126 terminated connections created on OC-48 PNNI trunk

CSCei70718 AXSM-XG failed to boot on software error

CSCei78895 Customer not able to provision on MPSM-T3E3-155 card via CWM

CSCei87684 dnport fails with software error in AXSM-XG

CSCej17823 PPP link flap during the PXM upgrade prevents graceful upgrade


CSCej62559 OSPF flaps observed after runrev with traffic going on the PPP links

CSCek23839 dspload CLI displays data of wrong partition in AXSM-A/B

CSCin84727 Bad release number was included in statistics file for VISM

CSCin86763 The config file sent from switch for AXSM-XG not having any sct associated

CSCin89927 Active and standby MPSM-155 core dumped after resetcd of standby

CSCin93775 SPVC connections in failed and getting winpath error


Identifier Headline


OL-11771-03

Resolved Caveats




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

CSCec48191 WatchDog timeout core dump is caused by SAR Queue Full.

CSCef66706 A maximum MRU of 1494 is achieved in the RPM-XF to MWR direction, when a MRU of 1524 is configured.

CSCef67225 Update frNIW in CISCO-WAN-FR-CONN-MIB file; Replace for MPSM-T3E3-155.

CSCef97365 REG5.1 Syncram invalid-unblock error found.

CSCeg03191 The mpsm-oc3 dumps the core after reset.

CSCeg25173 The mpsm-8-t1 dumps the core after reset.

CSCeg47129 REG5.1 Resetsys causes the remote nodes (AXSM-XG OC-3) pnniport into the down state.

CSCeg53512 REG5.1 Standby PXM went into failed state after switchcc and saveallcnf.

CSCeg57198 Core hot-dump on MPSM-16-T1E1 caused traffic to stop.

CSCeg60544 Fan tray trap discrepancy between MGX and MGX (PXM45).

CSCeg61656 BW update does not go through when RPM-XF subinterface is down.

CSCeg62874 When a bundle is administratively down and card is reset, the port changes to administratively up.

CSCeg65632 SAR Dispatcher hangs on mutex semaphore, which causes the card to reset.

CSCeg65663 Many SSI exceptions occur on a PXM1e node.

CSCeg69701 Database corruption after upgrading to 5.1.

CSCeg78661 AUSM trap 50918 is missing two varbinds.

CSCeg86507 phpi communication error on the mpsm-oc3/16.

CSCeg87717 PXM45/B system has a significant decrease in SPVC reroute rate performance.

CSCeg88649 ABR configuration is lost after standby reset.

CSCeh03411 Exception error on mpsm card causes card reset and coredump.

CSCeh06279 The tstdelay/tstcon tests failed on all connections.

CSCeh09518 AIS not generated when Port went down on AXSMXG

CSCeh10277 Stby XGoc12 in failed state; switchredcd caused synRamErrs.

CSCeh12738 Mask off byte 127 of packet memory I2C

CSCeh14484 ABR PCR is not getting copied to channel PCR in the MPSM-8T1-FRM card.

CSCeh15349 Entering the clrchancnt command after stopping traffic does not show traffic cleared.

CSCeh15410 WFQ cannot be disabled on ABR connections.

CSCeh16336 WFQ cannot be enabled on CBR/VBR connections.

CSCeh18931 lmiRootTask Addr exception occurs after switchred.

CSCeh19705 AXSM-XG NNI end points are not generating AIS after UNI end point is removed.


OL-11771-03

Resolved Caveats

CSCeh24125 OSPF goes down in single link mode with fragmentation enabled after bundle down/up.

CSCeh27127 Standby PXM45C stuck in Init-U/Active after entering loadrev command.

CSCeh29436 Policing drops CLP traffic on CBR.2 connection.

CSCeh29602 Some AXSMXG SCT files have inappropriate values for UBR.2 policing.

CSCeh30900 MPSM takes more than 4 minutes to boot after resetcd because of boot checksum issue.

CSCeh39575 MPLink trap is sent for Switch-side link after operUp, operDown events.

CSCeh46897 No RxAIS on AXSM-XG DS3 path when ominber is sending DS3 AIS to it.

CSCeh47620 Both primary and redundant MPSM cards are in the active state.

CSCeh48942 PPP links go down when protocol reject message is received for PPPmux.

CSCeh49968 pnports with ILMI are stuck in auto config after up/dnpnports.

CSCeh53471 workQPanic on MPSM155.

CSCeh58122 Incorrect speed for OC48 SONET path.

CSCeh63999 Traffic with packet size 1495 or more is dropped on MPSM-16-T1E1-PPP.

CSCeh64669 Need support for cds3RcvAIS count and cds3FEBE count.

CSCeh69278 Intermittent failure in IMA group setup between MPSM and AXSME.

CSCeh70562 Traffic in excess of PCR on UBR.2 connections egress as CLP1.

CSCeh72899 Wrong OIDs populated for Xmt CLP0 and CLP1 cells.

CSCeh78289 Hardware migration for NBSM to MPSM fails.

CSCeh80047 With 1:n redundancy group, primary MPSM stuck in boot when reset by second primary MPSM running a different version.

CSCeh96945 vc-merge fails to create tag vsi connections on AXSME.

CSCeh97670 Headline: MPSM-16-T1E1-PPP cards go to failed state after running resetcd script.

CSCei07636 PHPI communication error.

CSCei09787 Standby PXM stuck in backup boot after sysVersoinSet on active PXM.

CSCei67407 RPM-XF addred is blocked when RCON is present.


CSCej62559 OSPF flaps observed after runrev with traffic going on the PPP links

CSCin84104 FRSM-8P does not recognize SMB Line Connector Type after upgrade.

CSCin89087 Loadrev causes failure of active/primary MPSM-T3E3-155.

CSCin89618 MEMBLKERROR message while entering clrsmcnf command on MPSM-16-T1E1.




OL-11771-03

Resolved Caveats

Release 5.1.00Table 29 lists the caveats that were resolved in Release 5.1.

Table 29 Resolved Caveats in Release 5.1


CSCee31416 If card mode is different on stby MPSM-16, upln causes ram sync error

CSCee47465 CBSM-AXSMXG conn - after switchredcd - traffic stops

CSCee58638 Hardcoding of PXM slot for AXSM-MPSM155 conns: traffic loss on 8830

CSCee63424 Need support for NAK51-54 in PXM45 VSIS RM to clear dangler conns

CSCee80054 Sby PXM only - not disk from 8850 > 8830 goes into mismatch

CSCee85921 WIN5901: Link stuck in usable after particular error is removed

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

CSCee92300 Help message refers to obsolete/eng CLIs

CSCee94999 Remove PXM1E backup boot from PXM1E OAM Loopback feature compile

CSCee95294 WIN5984:MPSM16-EIT: some random pnni links fail when added by script

CSCee95371 IMA pnni-link deroute conns when switchred

CSCef02017 MPSM16-EIT: spi path add errors when one of the mpsm in 1:N reboot

CSCef08146 MPSM16-EIT:snmpget on Rcv & Tx Bytes return wrong values for FR Port

CSCef15811 MPSM16EIT:WIN6091 ima grp restart with NNI/ILMI causes card reset

CSCef15971 WIN6545 non supported DPS OAM cell stats handling

CSCef16682 WIN6545 invalid ATM cell with PTI=7 handling and stats update

CSCef20727 rmAllocLcn error during init stage

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

CSCef21961 tTnCmdTsk01 hogs CPU on pxm45b in sysBramEvtLogPrint()

CSCef22181 UT anomaly: Block addition of Slave connection on MLP Bundles on MPSM

CSCef22838 PXM45C-8830: Unable to reroute any service type conns except ubr

CSCef26657 Memory Leak under Congestion Scenario w/ Current Route

CSCef27840 MPSM16DT:Instruction Bound Exception caused the pxm1e to reset

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

CSCef28074 PHPI communication failure on MPSM after switchcc

CSCef28123 ABR has the same excessive priority as UBR

CSCef28241 PXM45C-8830: pnRedman SSI-3-EXCEPTION

CSCef28565 connection addition failing between MPSM16T1E1 and AXSM

CSCef30937 MPSM was failed after PXM switchcc stress testing

CSCef32181 XG ports in autoconfig for 30min, after upgrade

CSCef32407 MPSM16DT:mpsm16 card reset due to Bus Monitor Err on mpsm WINPATH

CSCef33722 MPSM16DT: 1:N RED failed to protect when the Primary card failure

CSCef35674 FECN is mapped to EFCI when setEFCIzero and NIW


OL-11771-03

Resolved Caveats

CSCef35743 WIN6354:MPSM16DT: dnimagrp on NE mpsm16 causes FE mpsm16 to reset

CSCef35755 Ping between MWR and XF goes through even after dncon on MPSM.

CSCef36378 WIN6313:OAM generated from IMA port has wrong CRC10

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

CSCef42054 Active PXM45 switched causing a core file

CSCef43182 MPSM16DT: ausmb card stuck when addimagrp w. out of range number

CSCef44587 EDP sometimes programmed to EPD0 sometimes to EPD1

CSCef45859 CLI dsppnni-path aw cbr caused exception

CSCef46693 switchcc fail due to outstanding database update

CSCef49455 MPSM16DT:Detected 1:N Red config mismatch, act/sdby reset on runrev

CSCef50757 Memory Leak after Repeatedly Downing Then Upping PNNI

CSCef51168 MPSM16DT: Active and Stdby reboot on switchredcd caused by snmpSA Task

CSCef51592 MPSM16DT: Byte Base Egress Service Ratio still work in Frame Base

CSCef52302 SNMPSA exception due to NULL pointer access

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

CSCef55251 mpsm card stay in failed state after setrev

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

CSCef58958 Telnet sessions are not being released gracefully

CSCef60038 Loopback tests on CBM via Win1 fails after 447 passes

CSCef62707 PXM45C-8830: dspconinfo, dspcons, dsppncons and others not working

CSCef63916 WIN6784: overrun issue upon dn/upppplink stress testing

CSCef64820 Mfg Diag only shows warning if master clock is not locked

CSCef65717 PXM45C-8830: Traffic loss around 1 sec with y-red on MPSM-OC-3

CSCef66764 IMA RX frame length field is not displaying in config gui

CSCef68719 clrsmcnf causes pnCCb crash and pxm45b resets

CSCef68743 56K link after reset has wrong comet programming

CSCef69457 Access level implementation for inTask commands

CSCef71060 IT: memory allocation/fragmentation issue after extended stress test

CSCef71163 MFRDT:M PSM8T1 all CLI rejected with wrong parsing and timeout on CC

CSCef72844 Missing SRM cards do not cause 1:N Red State to be Blocked

CSCef74066 DupFileList created while collecting stats on MPSM-16T1E1 cards

CSCef74998 Need to bring all links down before renegotiation for cnfmpbundle

CSCef77506 MPSM16DT:IMA nni lnk derouted all connections during switchcc

CSCef79081 MPSM16DT: mpsm standby card stuck init-state during runrev, coredump

CSCef79645 MPSM-Diag: Online diag fail to run on stdby 1:N MPSM-16

CSCef79647 Traffic stops completely on configuring ACFC/PFC on admin dn ppplink

Table 29 Resolved Caveats in Release 5.1 (continued)



OL-11771-03

Resolved Caveats

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

CSCef81959 Stby MPSM-T3E3-155 in failed state after loadrev

CSCef82452 dspchancnt is not working on MPSM-PPP

CSCef83027 MPSM16DT: loadrev on 1:N mpsm16 caused standby to Failed-U state

CSCef83728 Switchside PPP links go down after switchred on MPSM

CSCef83782 REG5.1 cutW1Task SSI-3-EXCEPTION

CSCef84575 MFRDT:WinPath Packet Bus Monitor error after link addition WIN6805

CSCef85133 snmpwalk on cimaLinkState gets into an infinite loop

CSCef88428 MPSM-Diag: Offline diag fail to start on 1:1 stdby MPSM

CSCef89132 if mru is nakd and then cnf to default (1500), links stays operDown

CSCef89191 IMA84 SDRAM refresh rate needs to be increased

CSCef90401 MPSM16DT:reset active 1:n red caused CBC-5-INVALID_ARG error

CSCef90982 ATM0: SSI-3-EXCEPTION HwMonitor while reloading RPM-PR

CSCef91392 MPSM-Diag: IMA-84 R/W test does not fail after fault insertion

CSCef92507 semaphore not defined, pxm45 in active-F

CSCef92669 not freeing connTrace msg. in congestion cond.

CSCef92922 REG5.1:AT Intermittently can not do cc 9 in reg-p3 node

CSCef93442 After switchred some of the switch side PPP links go down

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

CSCef93921 MRU cannot be changed on cnfppplink for transactCnfPppLink/Db failed

CSCef95524 MLP is not negotiating MRRU - PPP link stay inactive

CSCef96232 MPSM-PP is sending wrong endpoint discriminator on one of the links

CSCef97521 MPSM-16T1 Offline Diag test fails

CSCef97872 cannot addmux after delmux followed by dnmpbundle sometimes

CSCef97890 pnCcb memory leak on pxm45

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

CSCeg02154 PNNI: pnSptAwP task crash on SLT node

CSCeg02202 Current Route: current route tables are not getting populated

CSCeg02917 mfr configuration not visible in CWM

CSCeg03366 memory leak by pnSptAwP, pnSptCtdP and pnSptCdvP tasks

CSCeg04876 MPSM-OC-3:ds1 lns not shown on CWM,incorrect file sent by switch

CSCeg05676 nni link is in auto config after dn/uppnport on xg side

CSCeg05839 UPG5.1: pxm1e stuck in Empty/Reserve by remove/insert on 5.1(0.29)

CSCeg06814 MPSM-T3E3-155:Unable to upgd redundant cards

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

CSCeg09699 I2C driver support for winpath B1 chips




OL-11771-03

Resolved Caveats

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

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

CSCeg10741 dspchancnt rcv frames counter programming invalid.

CSCeg10810 frtt on MPSM FR should be in microseconds

CSCeg11715 MPSMOC-3 diagnostics enhancements

CSCeg12241 WIN 7309: lcp flaps on PPP links after downing one link

CSCeg12342 MPSM16PER: FrForwarding EGR is tagging BECN when INGR is congested

CSCeg13566 Memory leak issues on some SMs, cannot CC to them

CSCeg13614 MPSM 1:N Red: multiple mpsm-16-t1e1 cards in active-F

CSCeg15558 Endpoint Discriminator shown as Hex on MWR in MPSM-16-T1E1-ppp solution

CSCeg17056 dnbundle/dnppp, then upppp, upbundle, switch side PPP remains down

CSCeg17339 MPSM primary and secondary resets on doing a graceful upgrade

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

CSCeg17462 AUSM-8T1E1 cannot delete a port, error Connections existing on port

CSCeg17480 Missing MFR slave endpts data in config upld file for MPSM_8E1_FRM

CSCeg18618 Clear trap is not sent after selftest failure 60061 has been sent

CSCeg18974 MLPPP: ppplink trap 60272 having invalid value for lcp_pfc & lcp_acf

CSCeg21347 PPP link goes down on MWR while shown up on MPSM

CSCeg21470 Standby PXM45B stuck in INIT state due to ILMI addr ending w/ 0xff

CSCeg23877 UPG5.1:mpsm-155 went to Active-F-U-Active during runrev

CSCeg24814 PXM Diagnostics enhancements

CSCeg25020 CRC errors on the line when using AMI line coding

CSCeg28234 CS pkts seen with crtp+muxing ON MPSM for cUDP traffic

CSCeg28643 Need to free memory after generating trap

CSCeg29011 ppplink shows down on MPSM & up on MWR after switchred.

CSCeg29724 XM60 insertion causing active PXM45C to reset.

CSCeg29996 WIN 7310: dn and up 3 ppplinks result in long intermittent ping drop

CSCeg32485 MPSM 8T1E1 cannot have vci 32 to 34 included

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

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

CSCeg36788 Active mpsm8t1e1 comes up to standby after power cycle

CSCeg40360 MPSM E1 cards in lower bay crashed due to CTC exception

CSCeg42093 REG5.1: Switchredcd between LSM and MPSM8t1e1 is not allowing

CSCeg43495 MPSM in empty state after resetsys if core mask for PXM reset is enb

CSCeg46596 pnCcb crashed after rsetcd and dn/uppnport

CSCeg48573 REG5.1, 1:N switchredcd not rejected when SRME is not available




OL-11771-03

Resolved Caveats

Release 5.0.20Table 30 lists the caveats that were resolved in Release 5.0.20.

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

CSCeg52860 Workaround for ATMIzer SAR lockup

CSCeg55688 MPSM-16-T1E1 goes into ACTIVE-F state after switchcc

CSCeg57247 Compressed Packets are dropped on RPM-XF due to Corrupt PID

CSCeg66107 NEW_AXSMB_OC-12: No traffic flow after delapsln on 1:1 intracard APS

CSCeg66440 ssi exception error on axsm-xg:ilmi sync task dies

CSCin83809 MLPPP:Bundle gets added with wrong def value of cmpbendPointDiscrimC

CSCin85557 axisImaGroupVersion does not in the config upload file





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

CSCec81892 XGOC-3-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


OL-11771-03

Resolved Caveats

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




OL-11771-03

Resolved Caveats

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




OL-11771-03

Resolved Caveats

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 Cisco MGX 8850 and Cisco 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-OC-3

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




OL-11771-03

Resolved Caveats

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 up to 24 sec traffic loss

CSCef91992 The PTSE is dropped on receiving IG with type 36

CSCef92507 semaphore not defined, pxm45 in active-F

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

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

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

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

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

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

CSCeg09699 I2C driver support for winpath B1 chips

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

CSCeg11715 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




OL-11771-03

Resolved Caveats


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

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

CSCeg40316 WDDI sets tag to user_info field only for OAM channel

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

CSCeg52860 WatchDog timeout core dump caused by Sar Queue Full

CSCin59675 AUTO:UPC policing parameters are not properly displayed for AXSMXG

CSCin79215 Traps not getting generated for MFR link addition





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 MPSMOC-3: 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


OL-11771-03

Resolved Caveats

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 OC-3 winpath

CSCed73181 MPSM-155: Enabling frame-discard on master fails in h/w

CSCed73552 WIN 5048: traffic drop on FR/ATM conns after mcr reduced to 50

CSCed74374 REG5: RED Active AUSM card stuck in Boot State after Resetcd

CSCed74450 MPSM-155DT: MPSM configures as IMA trunk stuck in Active-F state

CSCed79636 cell discarding at egress when other 2000 connections in alarm

CSCed79767 dspchancnt does not work with -r and -max option on MPSM-155

CSCed81006 MPSM Etch 7 goes into idtmon with the oc3 crdmp feature change

CSCed81492 PNNI commands do not adhere to the 24 lines/page req

CSCed81568 MPSM-155-DT: switchover while rerouting results tVsiSync and tVsiSlave stuck

CSCed81573 Tracking code review for Vxworks prob w/ semaphore (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-OC-3 card went into Active -F state

CSCed84737 CLP failed to set to 0 on FR con when ChangeDEtoCLP map=setCLPzero




OL-11771-03

Resolved Caveats

CSCed85445 replace ssiRamIovCurMaxElementsGet with new SSI API (in all AXSM app

CSCed85997 SNMP timeouts on MPSM-OC-3 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 back card

CSCee00796 ILMI enabled UNI port goes down and up when connection are added

CSCee00828 RevB board takes a long time to download firmware

CSCee02189 MPSM-155-DT: tVsiSlave run away from CPU after dnports/resetcd/upports

CSCee02497 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




OL-11771-03

Resolved Caveats

CSCee09158 bootchange cmd on AXSM-E OC-12 w/o changes caused card reset

CSCee10237 Fail to automatically create CUT dir if accidentally 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 back cards generated multiple ApsModeMismatchClr traps

CSCee28318 SUNI driver needs to insert arbitrary pointer change to downstream

CSCee30064 connections deleted on AUSM switchredcd & PXM reset

CSCee30273 MPSM-155: IMA Grp Down w/Insff-link, but Port is Up, SPVCs are Up.

CSCee31377 MPSM OC-3 SIM card failed on upgrade

CSCee31972 UPG5+: XG EVNNI port stuck in down after runrev

CSCee32671 LMI sends incorrect message during timer retry

CSCee35169 AXSM Resets SNMP Subagent Software Exception

CSCee35248 REG5+: AXSME-32-T1E1 loses back card config after upgrade

CSCee35698 MPSM8-RAS: ATM ABR srcdest is not enabled correctly on channel

CSCee35820 MPSM8-RAS: softswitch should not check b/c if card in red bulk mode

CSCee38216 Card Reset is Setting Stats Ftp Status to ACTIVE. Should be INACTIVE

CSCee39204 No Action taken on Mutex semaphore hang for NON stdout semaphore

CSCee39665 cliRat task died during stdby card coming up

CSCee40457 Standby PXM reset/failed during upgrade

CSCee42145 Switch ASIC semaphore causes CLI freeze-AXSME




OL-11771-03

Resolved Caveats

CSCee42153 UPG5+: Mem leak from AXSM-XG lmiRootTask

CSCee43147 LMI data corruption if multiple LMI ports configured

CSCee43404 active PXM45B reset by SSI exception

CSCee44283 UPG5+: P2MP failed to commit to AXSM after upgrade

CSCee44466 LMI Control VC should use VSI service type signaling

CSCee44697 ILMI enable/disable not updated in rsc_part table on changing ILMI config.

CSCee44876 MPSM-155: Standby MPSM got reset 6 times overnight w/Cac Fails error

CSCee45538 Switch ASIC semaphore causes CLI freeze-AXSMXG

CSCee45542 Switch ASIC semaphore causes CLI freeze-PXM1E

CSCee45544 Switch ASIC semaphore causes CLI freeze-MPSMOC-3

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 OC-3 Stuck in Init state on Node with 4000 ports

CSCee66754 PXM45C: Single Bit ecc errors on resetting PXM intermittently.




OL-11771-03

Resolved Caveats

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




OL-11771-03

Resolved Caveats


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





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


OL-11771-03

Resolved Caveats

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 Error on cell bus caused card to enter failed state

CSCeb38659 resetsys on PXM45 causes AINI port to vc failure

CSCeb38985 MOC error caused ILMI failure on AXSM-XG card

CSCeb40265 xcnfln shows the clkfrquencythreshold 1-5. does not show what is meant

CSCeb40512 delred fail for LSM in 8830

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

CSCeb45254 SRMEB: Add/Del line loop cause APS failure

CSCeb51323 SRMEB: Stats manager caused Active PXM1E reset

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

CSCeb58227 conns are not derouted upon ilmi timeout when slp is enabled and dero

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

CSCeb59239 PM parameters on NBSMs are not accurate

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

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

CSCeb64000 switchover loss around 630 ms, >250 ms

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

CSCeb67843 Failed to add entry in QE48 Conn id table

CSCeb68706 observed message file already closed after runrev executed on frsm

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

CSCeb76581 CIT50: pnRedman suspended at provred_persis_link_addDel

CSCeb80000 conn does not deroute right away upon dnport with deroute delay on an

CSCeb83949 Policing of 80 char limit for dsppnportcac and dsppnportrsrc command

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

CSCec05854 Do NOT null out ifid for interfaces (back out CSCea32660)

CSCec08533 CESM T3E3 1:1 Redundancy is not functional

CSCec12108 Pnports of AXSM-XG card stay in building vc

CSCec12463 EVENT-CLEANUP: multiple ncdp fill in dsperrs log.

CSCec12609 CIT50: several VSI sev4 error logged from act and standby AXSM/B

CSCec14761 Software Error Reset PXM45

CSCec16762 Cannot cc on AXSM due to max sessions in hang

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

CSCec27723 Pnni signaling lcn reuse - pnni link cannot establish

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




OL-11771-03

Resolved Caveats

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

CSCec33505 Receive FIFO not held in reset during dnln.

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

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

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

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

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

CSCec42058 Statistical Alarm counters are not ok

CSCec42174 getting xbar alarm with offline diags enabled

CSCec42531 Err on switchcc outstanding database update

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

CSCec45604 Re-used port stay in alarm

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

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

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

CSCec51074 back card aps mux not set accordingly after switchred

CSCec51349 PXM1e reset after pumping high rate oam loopback

CSCec55245 Allowing to turn off rate control feature with ABR configured

CSCec55319 Mem leakage in procResponse: RespCalcC exhausting SSI SNMP partition

CSCec55976 vsiSlave Task suspended recovery action should be Fatal

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

CSCec59926 dump commands pause indefinitely with RPMs and may leak resources

CSCec62846 Failure on the data forwarding path was not detected

CSCec63239 VxWorks timer wrapped around

CSCec63535 AXSM-E: P2MP party in failed state after dnport/upport on leaf port

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

CSCec63713 AXSM reset with core dump

CSCec65160 dspload shows asymmetric bandwidth on AXSMs

CSCec66028 11010P4C: Trunk is shown into major alarm while there is no alarm on switch

CSCec66037 UBR.2 policing needs to tag all cells

CSCec66881 LSNT:AXSM Xtags does not come up

CSCec67719 HMM and QE48 falsely detects parity error when enabled

CSCec69262 PXM does not switch RPM-XF upon bkcd failures

CSCec69678 Popup: Cannot open input file ALARM:/SM_ALARM_1_13.CF errno = 0x388002

CSCec71316 DT: Connections do not get deprogrammed after dnport on AXSM-E card.

CSCec78432 FRSM-2T3 in a PXM1E chassis transmitting bogus a-bit alarm




OL-11771-03

Resolved Caveats

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 XGOC-3-DEV: SPI Errors due to continuous upilm/dnilmi on AXSM-XG-oc3

CSCec88175 The redundant RPM card did not cover for failed primary.

CSCed01505 threshold for SCM task hanging should be less

CSCed01523 need to fix node rebuild due to standby in init but scm thinks ready

CSCed01970 tDispatch task should give up CPU for other low priority tasks.

CSCed02565 ATLAS Non-Fatal and QE1210 Not-Fatal errors on yred AXSM pair

CSCed09164 Conn mastered at AUSM/FRSM with frm-based policing not prop to slave

CSCed09942 Minor issue on displaying card alarm state

CSCed14131 switchcc fail because standby PXM xbar is degraded

CSCed15676 Channel showing OK state with Controller Abit = 0

CSCed17323 Duplicate entries for conns in the STATS files

CSCed22720 Active PXM1E switched over after Standby Combo back card inserted

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

CSCed23150 AXSM VSIS changes wrong IpConn LCN on new cmd with same VP in VPC

CSCed24987 Config upload for AUSM-8T1 sends AUSM-8E1/B as FCDescr and BCState as invalid

CSCed25756 APS 1:1 intra-card, direction change results in mode mismatch error

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

CSCed30255 MAINT Connections not torn down in via node after dnpnport

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

CSCed30887 Login denial of service with [infinite login prompt] script

CSCed31789 vnni port alarm propagation not there when vpc is down

CSCed33148 pnportsig none port comes up with wrong vpi range max of 255

CSCed33156 Popup msg:Cannot write to C:/, errno 0x38800f

CSCed33292 StdAbr table in the config upload file

CSCed34580 After changing sct file multiple times, cnfport failed to change sct

CSCed35995 Traffic stopped running on 500 ABR cons on AXSM-XG OC-3

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




OL-11771-03

Resolved Caveats

CSCed41771 UPG5: XG-OC-3 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 OC-3 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 OC-3

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




OL-11771-03

Resolved Caveats

Known Route Processor Module or MPLS CaveatsFor information about caveats with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) for PXM45-based Switches, Release 5.4.00.

For information about caveats with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) for MGX Releases 1.3.16 and 5.4.00.

Known VXSM and VISM CaveatsFor information about caveats with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.10.

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

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.




OL-11771-03

Documentation Updates

Documentation UpdatesThis section provides updates for the following documents:

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

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

Cisco PNNI Network Planning Guide for MGX and SES Products UpdatesTable 33 describes the updates that resolve CSCei54818.

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

LMI Autosense is not supported on MPSM-8T1-FRM and MPSM-8E1-FRM cards. The LMI Autosense information in the following sections apply to the FRSM cards only:

• Chapter 2, “Adding Frame Relay Ports”

• Chapter 2, “Configuring Frame Relay Ports”

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

• addport

• cnfport

• xcnfport

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

Chapter Update

Chapter 2, Table 2.1, Note 3 Old note: PXM45, which is the first released version of the PXM45 card and is sometimes called PXM45A, is not supported on Release 5.1 switches.

Revised note: PXM45, which is the first released version of the PXM45 card and is sometimes called PXM45A, is not supported on Release 5.0 and onward.

Chapter 2, Table 2.1 New note: PXM45 does not support P2MP connections.


OL-11771-03

Documentation

DocumentationA Finding Cisco User Documentation Online ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.

AcronymsTable 34 lists acronyms that have been referenced in these release notes.

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

AMI alternate mark inversion [line coding]

APS Automatic Protection Switching

BPX Broadband packet exchange

BTS Base Transceiver Station

CAC connection admission control

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

ENNI Enhanced network-network interface

EV-DO Evolution-data optimized [traffic]

FGPA Field programmable gate array

FRU field-replaceable unit

GE Gigabit Ethernet

IAP Intercept Access Point

ILMA Integrated local management interface

IMA Inverse Multiplexing over ATM

IPC Interprocess communication

LANE Local Area Network Emulation

LCN logical connection number

LFI Link Fragmentation Interleaving

MFR Multilink Frame Relay


OL-11771-03

Acronyms

MLPPP/LFI Multilink PPP

MPSM Multiprotocol Service Module

MTI Multicast Tunnel Interface

NBSM Narrow band service module (traditional name for cell bus service modules in Release 4 and later)

NCDP Network clock distribution protocol

OAM Operation, administration, and maintenance

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

SCR Sustainable cell rate

SSCOP Service specific connection-oriented protocol

SFP Small Form Factor Pluggable Unit

SFTP Secure File Transfer

SM Service Module

SONET Synchronous Optical Network

SPVC Soft permanent virtual connection

SRM Service resource module

SSH Secure Shell

SVC Switched virtual circuit

UNI user-to-network interface

VCI virtual channel identifier

VISM Voice interworking service module

VPN Virtual Private Network

VRF VPN routing/forwarding

VSI Virtual switch interface

VXSM Voice switch service module

XF Express Forwarding

XLMI Extended link management interface

XPVC Extended permanent virtual circuit

Table 34 Acronyms Used in These Release Notes (continued)

Acronym Description


OL-11771-03

Obtaining Documentation, Obtaining Support, and Security Guidelines


For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo 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. (0805R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

© 2008 Cisco Systems, Inc. All rights reserved.


OL-11771-03

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html



OL-11771-03

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco ...

Documents

Transcript of Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco ...