Guest

Cisco MGX 8800 Series Switches

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

  • Viewing Options

  • PDF (1.8 MB)
  • Feedback
Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Software Release 5.5.10

Table Of Contents

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

Contents

About This Release

Locating Software Updates

New Features

Resetting MPSM Cards When PPP Links Go Down

Limitations

Displaying a Banner Message Before the Login Prompt

SSH and SFTP

Telnet and FTP

Limitations

SFTP Support on NBSM Cards

Persistent Support for RPM DPC

Enabling Data-path Checking on Standby RPMs

Traps and Alarms

Features in Release 5.5.00

Configuring the J1 Byte TxTrace Option on AXSM-XG Cards

Support for Daylight Saving

SNMP Support

Limitations

Disabling SSHV1, FTP, and Telnet on MGX

SNMP Support

Limitations

Power Supply Enhancement

SNMP and STATS Support for Card Uptime

MIBs Used

SNMP Support for resetcd, switchcc, and switchredcd

MIBs Used

Limitations

Grouping MGX Commands

Command for Grouping the Output of Existing Commands

Limitations

Grouping MPSM Commands

Command for Displaying Configuration Information

Command for Displaying Statistics Information

MultiVC Access to PXM Through Nonredundant RPM-XF

Limitations

Hardware and Resource Monitoring on MPSM-155 Cards

Hardware Monitoring

Resource Monitoring

Commands for Hardware and Resource Monitoring

Traps for Hardware and Resource Monitoring

Detecting Parity Error on a Standby AXSM

Refreshing the AXSM Virtual Connection Table

Limitations

Adding Additional VXSM Cards

Support for Back Card Status Message

Support for TACACS Challenge Messages

Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C

Features in Release 5.4.00

Bidirectional Forwarding Detection Version 1

DSCP Marking on RPM-XF Management Interface

Limitations

Flash MIB Support

SNMPv3

Trap Squelch Feature

Limitations

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

Features in Release 5.3.20

MPSM Licensing Changes

Support for Clear Channel E1 Lines

Support for BERT Tests on Clear Channel T3/E3 Lines

Features in Release 5.3.10

Enhanced VXSM Card Support

Non-Redundant Upgrade Procedure

Redundant Upgrade Procedure

Cisco MGX 8800 Series Operating and Storage Environment

Guidance for Operating and Storage Environments

Operating Environment Specifications

Non-operating and Storage Environment Specifications

Features in Release 5.3.00

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

Summary of MLPPP Changes

MLPPP Configuration

MLPPP Upgrade Considerations

Fractional T1/E1 Links for ATM Services

Fractional T1/E1 Configuration

Fractional T1/E1 Configuration Limitations

Security Enhancements

SFTP and SSH Features

Remote IP Management Connection Enhancements

Management Connection Limitations

Configuring an RPM Management Connection

Management Configuration—Example

Routing Enhancement for AXSM-XG Cards

Platform Enhancements

Cisco MGX 8830/B Enhancements

RPM-PR Ethernet Back Card

Features in Release 5.2.10

Features in Release 5.2.00

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

Features in Release 5.1.20

Features in Release 5.1.00

MPSM-16-T1E1 Card

Operational Modes

Supported Features

Multilink PPP Feature for CDMA2000 and EV-DO

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics

Private Network Node Interface Current Route Feature

Operational and Redundancy Limitations

Feature Specifications

PNNI Product Enhancements

PXM1E OAM Enhancement

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Supported Hardware

Hardware in Release 5.5.10

Product IDs, Card Types, and APS Connectors

Service Class Template File Information

PXM1E SCT Files

AXSM and AXSM/B SCT Files

AXSM-E SCT Files

AXSM-XG SCT Files

MPSM-T3E3-155 SCT Files

MPSM-16-T1E1 SCT Files

New and Changed Commands

New Commands in Release 5.5.10

cnfcdresetppp

cnfloginbanner

cnfstdbyrpmdpc

dspcdresetppp

dsploginbanner

dspstdbyrpmdpc

New Commands in Release 5.5.00

cnfdaylightsetting

cnfmultivc

cnftxtraceopt

cnfvctrefresh

delprevdbs

dspbundleconfiginfo

dspbundlestatsinfo

dspdaylightsetting

dspdeverr

dspdeverrhist

dspmultivc

dsptxtraceopt

dspvctrefresh

showtech

Changed Commands in Release 5.5.00

cnfndparms

cnfrmrsrc

dspcds

dsprmrsrc

dsprmrsrcs

Changed Commands in Release 5.4.00

Changed MPSM Commands

Changed PXM Commands

Changed AXSM Commands

Changed Commands in Release 5.3.20

Changed Commands in Release 5.3.00

Changed MPSM Commands

addport

addppplink

cnfppplink

dsppathalmcnt

dspmpbundles

dspport

dspports

dspmpbundlecnt

dspppplnkcnt

Changed PXM Commands

cnfndparms—PXM45

dspndparms

Changed AXSM-XG Commands

MGX Release 5.5.10 Limitations, Restrictions, and Notes

Upgrade Limitation

BERT Limitation

MGX Chassis Bandwidth Limitations

Bandwidth Limits

Card Placement Guidelines

Bandwidth Oversubscription

PXM1E Switch Limitations

PXM1E Hardware Limitations

PXM1E Reserved Virtual Channel Identifiers

PXM1E Point to Multipoint Support

PXM1E Parity Errors

PXM1E Policing Accuracy

PXM45 and PXM1E System Limitations

Maximum Threshold Accuracy

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

SPVC Interoperability Limitations

Service Card Limitations

AXSM-16-155-XG with MCC Back Card Limitations

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

AXSM-E Card OAM Limitations

General AXSM Card Limitations

AXSM Card APS Limitations

MPSM Card Limitations

CBSM Card Limitations

IGX Feeder Limitation

Clock Source Limitations

Clearing Card Configuration Notes

PNNI Limitations

Logical Link Limits

Preferred Route Limitations

Priority Route Limitations

Persistent Topology Limitations

Fault Isolation and Trace Limitations

Serial Bus Path Fault Isolation Limitation

Cell Bus Path Fault Isolation and Recovery Limitations

Path and Connection Trace Notes

CLI Access Level Notes

Disk Space Maintenance Notes

Non-native Controller Front Card and PXM-HD Card Notes

Other Limitations and Restrictions

Installation and Upgrade Procedures

Supported Upgrade Paths

Upgrade Information

Upgrading AXSM-XG Cards

Upgrading the VISM-PR Image

Maintenance Information

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

Open Caveats

Resolved Caveats

Release 5.5.10

Release 5.5.00

Release 5.4.00

Release 5.3.20

Release 5.3.10

Release 5.3.00

Release 5.2.10

Release 5.2.00

Release 5.1.20

Release 5.1.00

Release 5.0.20

Release 5.0.10

Release 5.0.00

Known Route Processor Module or MPLS Caveats

Known VXSM and VISM Caveats

Documentation Updates

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

Documentation

Acronyms

Obtaining Documentation, Obtaining Support, and Security Guidelines


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


Revised: June 29, 2009, OL-13646-02

Contents

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

About This Release

Locating Software Updates

New Features

Resetting MPSM Cards When PPP Links Go Down

Displaying a Banner Message Before the Login Prompt

SFTP Support on NBSM Cards

Persistent Support for RPM DPC

Features in Release 5.5.00

Configuring the J1 Byte TxTrace Option on AXSM-XG Cards

Support for Daylight Saving

Disabling SSHV1, FTP, and Telnet on MGX

Power Supply Enhancement

SNMP and STATS Support for Card Uptime

SNMP Support for resetcd, switchcc, and switchredcd

Grouping MGX Commands

Grouping MPSM Commands

MultiVC Access to PXM Through Nonredundant RPM-XF

Hardware and Resource Monitoring on MPSM-155 Cards

Detecting Parity Error on a Standby AXSM

Refreshing the AXSM Virtual Connection Table

Adding Additional VXSM Cards

Support for Back Card Status Message

Support for TACACS Challenge Messages

Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C

Features in Release 5.4.00

Bidirectional Forwarding Detection Version 1

DSCP Marking on RPM-XF Management Interface

Flash MIB Support

SNMPv3

Trap Squelch Feature

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

Features in Release 5.3.20

MPSM Licensing Changes

Support for Clear Channel E1 Lines

Support for BERT Tests on Clear Channel T3/E3 Lines

Features in Release 5.3.10

Enhanced VXSM Card Support

Non-Redundant Upgrade Procedure

Redundant Upgrade Procedure

Cisco MGX 8800 Series Operating and Storage Environment

Guidance for Operating and Storage Environments

Operating Environment Specifications

Non-operating and Storage Environment Specifications

Features in Release 5.3.00

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

Summary of MLPPP Changes

MLPPP Configuration

MLPPP Upgrade Considerations

Fractional T1/E1 Links for ATM Services

Fractional T1/E1 Configuration

Fractional T1/E1 Configuration Limitations

Security Enhancements

SFTP and SSH Features

Remote IP Management Connection Enhancements

Management Connection Limitations

Configuring an RPM Management Connection

Management Configuration—Example

Routing Enhancement for AXSM-XG Cards

Platform Enhancements

Cisco MGX 8830/B Enhancements

RPM-PR Ethernet Back Card

Features in Release 5.2.10

Features in Release 5.2.00

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

Features in Release 5.1.20

Features in Release 5.1.00

MPSM-16-T1E1 Card

Operational Modes

Supported Features

Multilink PPP Feature for CDMA2000 and EV-DO

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics

Private Network Node Interface Current Route Feature

Operational and Redundancy Limitations

Feature Specifications

PNNI Product Enhancements

PXM1E OAM Enhancement

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Supported Hardware

Hardware in Release 5.5.10

Product IDs, Card Types, and APS Connectors

Service Class Template File Information

PXM1E SCT Files

AXSM and AXSM/B SCT Files

AXSM-E SCT Files

AXSM-XG SCT Files

MPSM-T3E3-155 SCT Files

MPSM-16-T1E1 SCT Files

New and Changed Commands

New Commands in Release 5.5.10

New Commands in Release 5.5.00

Changed Commands in Release 5.5.00

Changed Commands in Release 5.4.00

Changed MPSM Commands

Changed PXM Commands

Changed AXSM Commands

Changed Commands in Release 5.3.20

Changed Commands in Release 5.3.00

Changed MPSM Commands

Changed PXM Commands

Changed AXSM-XG Commands

MGX Release 5.5.10 Limitations, Restrictions, and Notes

Upgrade Limitation

BERT Limitation

MGX Chassis Bandwidth Limitations

MGX Chassis Bandwidth Limitations

Bandwidth Limits

Card Placement Guidelines

Bandwidth Oversubscription

PXM1E Switch Limitations

PXM1E Hardware Limitations

PXM1E Reserved Virtual Channel Identifiers

PXM1E Point to Multipoint Support

PXM1E Parity Errors

PXM1E Policing Accuracy

PXM45 and PXM1E System Limitations

Maximum Threshold Accuracy

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

SPVC Interoperability Limitations

Service Card Limitations

AXSM-16-155-XG with MCC Back Card Limitations

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

AXSM-E Card OAM Limitations

General AXSM Card Limitations

AXSM Card APS Limitations

MPSM Card Limitations

CBSM Card Limitations

IGX Feeder Limitation

Clock Source Limitations

Clearing Card Configuration Notes

PNNI Limitations

Logical Link Limits

Preferred Route Limitations

Priority Route Limitations

Persistent Topology Limitations

Fault Isolation and Trace Limitations

Serial Bus Path Fault Isolation Limitation

Cell Bus Path Fault Isolation and Recovery Limitations

Path and Connection Trace Notes

CLI Access Level Notes

Disk Space Maintenance Notes

Non-native Controller Front Card and PXM-HD Card Notes

Other Limitations and Restrictions

Installation and Upgrade Procedures

Supported Upgrade Paths

Upgrade Information

Upgrading AXSM-XG Cards

Upgrading the VISM-PR Image

Maintenance Information

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

Supported Upgrade Paths

Open Caveats

Resolved Caveats

Release 5.5.10

Release 5.5.00

Release 5.4.00

Release 5.3.20

Release 5.3.10

Release 5.3.00

Release 5.2.10

Release 5.2.00

Release 5.1.20

Release 5.1.00

Release 5.0.20

Release 5.0.10

Release 5.0.00

Documentation Updates

Documentation

Acronyms

Obtaining Documentation, Obtaining Support, and Security Guidelines

About This Release

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

Release 5.5.10 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)

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 Updates

Release 5.5.10 software is located at:

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

New Features

Release 5.5.10 includes the following new features for the Cisco MGX platforms:

Resetting MPSM Cards When PPP Links Go Down

Displaying a Banner Message Before the Login Prompt

SFTP Support on NBSM Cards

Persistent Support for RPM DPC

Resetting MPSM Cards When PPP Links Go Down

MPSM cards support PPP mode as one of the deployable solutions. In rare cases, all the PPP links go down operationally even though their Admin state and Lower layer status is UP. Usually, the operational state of the PPP links goes down when either the Lower layer or the Admin state is down.

In Release 5.5.10, this feature resolves the issue by resetting the MPSM card. This enhancement enables the system to monitor the events received from the Admin and Lower layer. When all the PPP links are down and their corresponding Lower layer is UP, the system sends a trap, and an event is logged on the PXM. Also, the system triggers a configurable timer. When the timer expires, the card reset is triggered. If any of these PPP links recover to the operational UP state before the timer expires, then the timer is canceled and no reset action is taken.

You can enable this feature by using the command cnfcdresetppp. By default, this feature is enabled. The default value of the timer is three seconds. For more information about the commands, refer to the section New and Changed Commands.


Note You have to disable this feature if you are doing any administration or maintenance activity on a MPSM links or peer node.


Limitations

This enhancement enables the system to detect only the link failures, not the reasons for failure. The links might also go down due to administrative activity.

This enhancement does not resolve the outage problems completely. The switchover happens only if all the PPP links go down. The new active card may face the same problem even after the card resets.

Displaying a Banner Message Before the Login Prompt

In Release 5.5.10, enhancements are made to display a banner message before the login prompt when a user logs in to MGX through Telnet, FTP, SSH, or SFTP. You can configure the path of the banner file. The procedure to configure the path differs for SSH, SFTP, Telnet, and FTP.

SSH and SFTP

For SSH and SFTP sessions, you have to update the sshd_config file with the path of the banner file. To update the path:


Step 1 Copy the file sshd_config to your local directory.

Step 2 Append the following line in the config file using any text editor:

banner "path of bannerfile"

Step 3 Copy the updated config file from your local directory to the active PXM.

Step 4 Put the banner file in the specified path.

Step 5 Reset the standalone PXM. Execute the switchcc command twice if you have both the active and standby card on your MGX node.

Telnet and FTP

A new command, cnfloginbanner, is added to specify the path of the banner file. MGX reads the banner file from the specified path and sends it to the Telnet or FTP client. If no banner file exists in the specified path, then the system creates a banner file with empty content. You have to update this file with the login message. For more information about the commands, refer to the section New and Changed Commands.

Limitations

Login banner needs to be configured in F:/SSHD directory, or any directory which sync between active and standby PXM. Otherwise, login banner will be lost after doing a swithcc or resetting of the active PXM card.

SFTP Support on NBSM Cards

Before Release 5.5.10, when the NMS sent an IOCTL request to the PXM for the configuration file, alarm file, and statistic file from the NBSM, the PXM returned the same value (-1). In Release 5.5.10, when the NMS sends an IOCTL request to the PXM for the configuration file, alarm file, and statistic file, the PXM returns the actual size of the file.

Persistent Support for RPM DPC

Before Release 5.5.10, the data-path check (DPC) running on an RPM-XF card detects the health of the data path and sends the results to the PXM45 through alarms and logs, but does not send any information to diagnostic module on the PXM. Because of this, no traps are sent to the NMS for data-path check failure, and the PXM45 does not take any recovery action when a standby RPM-XF card fails.

In Release 5.5.10, enhancements are made to report the data-path failure on an RPM-XF card. The PXM45 sends traps to the NMS when data-path check failure occurs on an RPM-XF card.

Enabling Data-path Checking on Standby RPMs

When data-path check failure occurs, the PXM45 takes the following actions:

1. Puts the standby RPM-XF card in the failed state and blocks the redundancy switchover

2. Puts the active and standalone cards in the Active-F state

When the failure is cleared, you have to restore the active and standby cards. To restore the cards, run the following commands on the PXM:

resetcd -f slot no for the active card

resetcd slotno for standby card

A new command, cnfstdbyrpmdpc, is added for enabling the data-path check feature on standby RPM-XF cards. The command dspstdbyrpmdpc displays the status of data-path check on standby RPM-XF cards.

Traps and Alarms

The following traps are sent to the NMS:

cwModuleSelfTestFail

When diagnostics on an RPM-XF card fail.

cwModuleFailed

When the PXM45 puts the standby RPM-XF card in the failed state.


No new alarms are added for this feature. The following existing alarms are used:

ZAM alarm for diagnostic failure.

Data-path check failure alarm (changes from line level to card level)

Alarms that are sent when the PXM45/PXM1E puts the card in failed state.

Features in Release 5.5.00

Release 5.5.00 includes the following new features for the Cisco MGX platforms:

Configuring the J1 Byte TxTrace Option on AXSM-XG Cards

Support for Daylight Saving

Disabling SSHV1, FTP, and Telnet on MGX

Power Supply Enhancement

SNMP and STATS Support for Card Uptime

SNMP Support for resetcd, switchcc, and switchredcd

Grouping MGX Commands

Grouping MPSM Commands

MultiVC Access to PXM Through Nonredundant RPM-XF

Hardware and Resource Monitoring on MPSM-155 Cards

Detecting Parity Error on a Standby AXSM

Refreshing the AXSM Virtual Connection Table

Adding Additional VXSM Cards

Support for Back Card Status Message

Support for TACACS Challenge Messages

Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C

Configuring the J1 Byte TxTrace Option on AXSM-XG Cards

The default value of the J1 byte (STS path trace string in SONET frames) inserted by AXSM-XG card is 62NULL+CR+LF. That is, the default value consists of 62 NULL ASCII characters, followed by a <CR>, and then a <LF> ASCII character, thus making the total length of the J1 byte 64 characters. For AXSM-A/B/E cards, the default J1 byte inserted in a SONET frame is 64 NULL ASCII characters. Some of the switches in the network require the J1 byte sent from the peer to be 64 NULL ASCII characters. Due to this mismatch in the J1 byte, the interoperability fails on the AXSM-XG cards with these switches. You can resolve this issue by setting the default value of J1 byte to 64 NULL ASCII characters during hardware upgrade from AXSM-A/B/E to AXSM-XG card.

To enable J1 byte TxTrace, set the value to 1. In the following example, the user enables the J1 byte TxTrace:

Unknown.12.AXSM-XG[ATM].a > cnftxtraceopt 1

For more information about the commands, refer to the section New and Changed Commands

Note The parameter modified using the command cnftxtraceopt is at card level, and all line and path will follow the same configuration. You cannot configure TxTrace option for individual line or path.


Support for Daylight Saving

Prior to Release 5.5.00, the feature Daylight Saving was not available on the Cisco MGX 88xx switch controller, even though it was available on RPM cards. Due to this, when the daylight saving starts, the time shown in the logs was different for the RPM and MGX 88xx switch controller. Also, the time shown by the switch controller card was different from the wall clock time.

In Release 5.5.00, CLI and SNMP support is provided to configure daylight saving time on MGX 88xx switch controller.

The following commands are introduced to configure and display the daylight saving settings:

cnfdaylightsetting

dspdaylightsetting

For more information about the commands, refer to the section New and Changed Commands.

SNMP Support

CISCO-SYSTEM-MIB is used to enable the Daylight Saving feature. A trap is sent to indicate the timezone change. The following objects are reused:

csySummerTimeStatus

csySummerTimeRecurringStart

csySummerTimeRecurringEnd

csyClockDateAndTime

Limitations

If there is a node in a different time zone with the Daylight Saving feature disabled, correlating the events between those nodes becomes difficult.

If an application has an event scheduled in the future, and the event time and the scheduled change in time zone are the same, then the application may not get enough time to reschedule that event. In that case, the application will not run. The following applications fall under this category:

Diag

optRoute

Disabling SSHV1, FTP, and Telnet on MGX

The MGX switch can be accessed using Telnet, FTP, Secure Shell Protocol Version 1(SSHV1), Secure Shell Protocol Version 2 (SSHV2), and Secure File Transfer Protocol (SFTP). Prior to release 5.5.00, there was no option to disable the feature SSHV1 through CLI and SNMP.

In Release 5.5.00, options are provided to disable the SSHV1 using the CLI and SNMP. Also, FTP and Telnet can be disabled using SNMP. After you disable these protocols, MGX does not allow new sessions. The old session continues to run.

The following commands are updated to include the node-wide parameters for disabling SSHV1:

cnfndparms

dspndparms

For more information about the commands, refer to the section New and Changed Commands.

SNMP Support

One new MIB FTP-SERVER-MIB is introduced for FTP. For Telnet, the scalar ctsTelnetActivation, which is part of MIB CISCO-TELNET-SERVER-CAPABILITY is used. For SSHV1, the scalar cssServiceActivation which is part of the MIB CISCO-SECURE-SHELL-MIB is used.

These MIB elements are part of the configuration upload. MGX sends traps when SSHV1, FTP, and Telnet are enabled or disabled.

Limitations

If you disable SSHV1, the system disables Telnet access, as well.

If SSHV1 is enabled, the system enables only SSHV1. You have to enable the Telnet session separately.

Power Supply Enhancement

Prior to Release 5.5.00, the command dspenvalms displays the voltage level as "Below Normal" if the power supply unit (PSU) in slot one is missing even though PSUs are present in other slots. In Release 5.5.00, the command dspenvalms displays the voltage level as "Indeterminate" if one slot is missing and PSUs are present in other slots.

The following example displays the command output:

Saras.8.PXM.a > dspenvalms

Saras                            System Rev: 05.03   May. 16, 2007 18:02:08 GMT
MGX8850                                              Node Alarm: MAJOR
ENVIRONMENTAL ALARM STATE INFO   ^Notification Disabled    *Alarm Detected
   Alarm Type      Unit   Threshold      DataType   Value       State
----------------  ---- --------------   -------- ---------- -------------
Temperature             <= 50            Celsius   32       Normal

Power Supply       A1   none             None      none     Missing
Power Supply       A2   none             None      none     Missing
Power Supply       A3   none             None      none     Normal
DC Voltage         A    42  to 58        VoltsDC   0    Indeterminate   

Power Supply       B1   none             None      none     Missing
Power Supply       B2   none             None      none     Normal
Power Supply       B3   none             None      none     Missing
DC Voltage         B    42  to 58        VoltsDC   0    Indeterminate

SNMP and STATS Support for Card Uptime

SNMP and STATS support are provided to the command dspcduptime. The command dspcduptime displays the time elapsed since the last reboot of a card. The following cards support SNMP:

AXSMXG

MPSM-16-T1E1

MPSM-T3E3-155

PXM1E

PXM45

RPM-PR

RPM-XF

VISM

VXSM

The following cards support STATS:

AXSMXG

MPSM-16-T1E1

MPSM-T3E3-155

PXM1E

PXM45

VXSM

MIBs Used

CISCO-ENTITY-FRU-CONTROL-MIB is used for supporting this feature.

SNMP Support for resetcd, switchcc, and switchredcd

In Release 5.5.00, Cisco MGX 88xx and MGX 89xx support SNMP for the following commands:

resetcd

switchcc

switchredcd

SNMP support enables you to execute the commands through NMS Manager.

MIBs Used

For the resetcd command, the shelfTable in BASIS-SHELF-MIB.my is used. For switchredcd and switchcc commands, the CISCO-ENTITY-REDUNDANCY-MIB.my and CISCO-ENTITY-REDUNDANCY-TC-MIB.my are used. The tables used in the CISCO-ENTITY-REDUNDANCY-MIB.my are:

ceRedunCommandTable

ceRedunGroupTypesTable

ceRedunMbrConfigTable

ceRedunGroupTable

Limitations

The option clear history in the resetcd command is not supported. Using the command resetcd -f, you cannot clear the failure history of the card through SNMP.

Access to ceRedunGroupTable and ceRedunMbrConfigTable is read-only.

Grouping MGX Commands

In Release 5.5.00, a new command is added to group the output of a series of commands. The command showtech displays all the configuration and run-time status information. The command helps a user to avoid the time spent on executing each command one by one. Also, the detailed output of the command helps a user to debug the problems easily. This command is available only on PXM, MPSM-155-PPP, and 16T1E1-PPP.

Command for Grouping the Output of Existing Commands

The command showtech groups the output of a series of commands. On a PXM45, the command displays the output of the following commands:

dspcdalms

dspcderrs

dspcds

dspchassis

dspclkalms

dspclksrcs

dspcons -state fail

dspcontrollers

dspdeverrhist (for all devices XBARCORE,DISK,CBC,HUMVEE,QE1210)

dspdisk

dspenvalms

dsperrhist -<slot #> (for all slots with cards)

dsphwalms

dspipif

dspndalms

dsppnni-node

dspprf <t> < m | n | q | r>

dspprfhist

dspred

dsprevs

dsprmalms

dspswalms

ipcMblkShow

logConsoleShow

ssiMemTaskStatShow

On an MPSM, the command displays the output of the following commands:

dspcd

dspchancnt <connection> <interval> (for every connection)

dspcons

dsplns

dspmpbundles

dspmpbundle <bundle> (for every bundle)

dsppaths -all

dspppplinks

dspppplink <link> (for every link)

dsprmalms

dsptotals

logConsoleShow

For more information about the command, refer to the section New and Changed Commands.

Limitations

This command is available only on PXM45 and MPSM-16T1E1PPP. The cards should not be in the failed state.

Grouping MPSM Commands

In Release 5.5.00, new commands are added to group the output of a series of commands. These commands help a user to collect the configuration information by executing a single command. The advantages of this feature are:

Reduces the time taken to collect the information by correlating multiple outputs

Ensures accuracy, thoroughness, and consistency of diagnostic data collection

Command for Displaying Configuration Information

The command dspbundleconfiginfo displays the configuration information related to the following:

Bundle

Links related to the bundle

Connection related to the bundle

Mux related to the bundle

The following commands are used for displaying the output:

dspcon

dspmpbundle

dspppplink

dsppppmux

Command for Displaying Statistics Information

The command dspbundlestatsinfo displays the statistics information related to the following:

Bundle

Links related to the bundle

Connection related to the bundle

Mux related to the bundle

The following commands are used for displaying the output:

dspchancnt

dspmpbundlecnt

dspppplinkcnt

dsppppmuxcnt


Note This command is available only on MPSM-155-PPP and MPSM-16t1e1-PPP.


For more information about the commands, refer to the section New and Changed Commands.

MultiVC Access to PXM Through Nonredundant RPM-XF

In Release 5.5.00, controlled access to the PXM is enabled. For enabling this feature, in-band connectivity through RPM is used. In-band connectivity through RPM requires establishment of SVC between atm0 interface on the PXM and slave endpoints on RPM. RPM routes packets received on the PVC through its Fast Ethernet (FE) interface to the external IP world. You can configure an access control list (ACL) on this FE interface for controlled access to the PXM.

For configuration information, refer to Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.00.

Limitations

The following limitations apply:

The feature works only if the atm0 interface is configured as default.

PXM will dump all the IP packets to RPM even if a destination does not exist.

All the RPMs and the managed PXM should be in the same chassis.

IP address of the FEs of all RPMs used for controlled access to a PXM should be in the same subnet.

On resetting the RPM card, the IP cache entries are not deleted for the SVC connections (which are used for IP connectivity) and will be down till RPM boots up. Therefore, the default VC is not used for these IP entries till aging of the entry happens or connection comes up.

Hardware and Resource Monitoring on MPSM-155 Cards

Hardware Monitoring

Hardware Monitoring Module (HMM) monitors the hardware devices on a card and detects the device error conditions. HMM reports the error type to the PXM. Depending on the availability of a redundant card and the severity of the error conditions, PXM determines the corrective action. For instance, if an active card of a redundant pair reports a major error, PXM initiates a card switchover. However, in the absence of a standby card, the active card is put in the failed state. HMM runs on both active and standby cards. HMM functionality is split into two parts:

Monitoring infrastructure

Monitoring individual devices

The following hardware devices are monitored on an MPSM-155 card:

APOX FPGA

CBC-155 FPGA

SUNI-IMA-84

Winpath Network Processor


Note HMM is already supported on PXM45, PXM1E, AXSM, AXSM-E, and ASXM-XG cards.


Resource Monitoring

Resource monitoring (RM) monitors various system resources such as memory, CPU, IPC buffers, hard disk, timers, and so on. In Release 5.5.00, a new resource, Winpath Ingress/Egress buffer, is added for MPSM-PPP mode.

Commands for Hardware and Resource Monitoring

The following commands are introduced in this release for hardware monitoring:

dspdeverr

dspdeverrhist

No new commands are added for Resource Monitoring. The output of the existing commands are updated with the Winpath resources. You can use the following commands for resource monitoring:

cnfrmrsrc

dsprmrsrc

dsprmrsrcs

For more information about the commands, refer to the section New and Changed Commands.

Traps for Hardware and Resource Monitoring

The Hardware Error Report trap is raised by HMM under the following conditions:

When a device error count exceeds the major set threshold

When a device error count exceeds the critical set threshold

When a device error count decreases below the critical clear threshold

When a device error count decreases below the major clear threshold

No new traps are added. The existing trap, cwHardwareErrorReport, is used for sending traps.

The RM raises the Resource Update Report trap when a change of state is detected for a resource. The existing trap, cwModuleOsRsrcUpdate, is used for reporting the state of change.

Detecting Parity Error on a Standby AXSM

On 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.5.00, the probability of dual AXSM failure is reduced by actively 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 Table

On 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 redundant card, the slot either fails or resets when the number of errors crosses the threshold value.

In Release 5.5.00 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 of the card and prevents the outage. The VCT refresh cycle time for 128K connections is close to 12 minutes. A new command cnfvctrefresh is added to enable this feature. For more information about the commands introduced, refer to the section New and Changed Commands.


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.

Point-to-multipoint connections are not refreshed.

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

Adding Additional VXSM Cards

You can add additional VXSM cards to a Cisco MGX 8850 chassis as primary cards. Adding of additional cards may result in insufficient disk space. To create the required disk space, previous versions of database on the existing slots must be deleted. A new command delprevdbs is added to enable users to delete the previous versions of the database.

This command can be executed on the following card types: PXM45, PXM1E, AXSM, AXSME, AXSMXG, VXSM, MPSM T3E3, and MPSM 16T1E1.


Note When the delprevdbs command is run on the PXM card, it deletes the unused databases of both shelf manager and disk database. But on a service module card, only the disk databases are deleted.


Support for Back Card Status Message

Prior to Release 5.5.00, the dspcds command displays the status of front card and only one back card available. The status of other cards was not available and the user has to run dspcds command to see the status of all the back cards for a slot. In Release 5.5.00, an option all is added to the dspcds command to display the status of all back cards. This command is supported only on PXM45 and PXM1E.

The following example displays the output of the command:

n210.7.PXM.a > dspcds all

n210 System Rev: 05.05 Nov. 02, 2008 22:22:42 GMT

Chassis Serial No: SAA03320190 Chassis Rev: B0 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Redundant Redundancy

Slot Card State Type Slot Type

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

01 Failed/Active/Empty AXSM_16OC3_B NA NO REDUNDANCY

02 Empty --- --- ---

03 Empty --- --- ---

04 Empty --- --- ---

05 Empty --- --- ---

06 Failed/Empty/Empty AXSM_16OC3 NA NO REDUNDANCY

07 Active-U/Active/Active PXM45C 08 PRIMARY SLOT

08 Empty Resvd-U/Empty Resvd/Empty --- 07 SECONDARY SLOT

09 Active/Active FRSM_2T3 NA NO REDUNDANCY

10 Active/Active MPSM-T3E3-155-PPP NA NO REDUNDANCY

11 Failed/Active/Empty AXSM-8-622-XG NA NO REDUNDANCY

12 Empty --- --- ---

13 Active/Empty/Active RPM_XF NA NO REDUNDANCY

14 Failed/Empty/Empty AXSME_2OC12 NA NO REDUNDANCY

15 Empty --- --- ---

Type <CR> to continue, Q<CR> to stop:

n210 System Rev: 05.05 Nov. 02, 2008 22:22:42 GMT

Chassis Serial No: SAA03320190 Chassis Rev: B0 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Redundant Redundancy

Slot Card State Type Slot Type

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

16 Empty --- --- ---

18 Empty --- --- ---

19 Empty --- --- ---

20 Empty --- --- ---

21 Empty --- --- ---

25 Active/Active MPSM-T3E3-155 NA NO REDUNDANCY

26 Active/Active MPSM-T3E3-155 NA NO REDUNDANCY

28 Empty --- --- ---

31 Empty --- --- ---

32 Empty --- --- ---

Support for TACACS Challenge Messages

The TACACS challenge messages inform a user that the password has expired when the user tries to login through SSH. For more information about configuration, see the guide Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Support for AXSM-16-T3E3/B Card in 8830/B Chassis with PXM45C

With this release, support for the AXSM-16-T3E3/B cards in the MGX 8830/B chassis is added.

Features in Release 5.4.00

Release 5.4.00 includes the following new features for the Cisco MGX platforms:

Bidirectional Forwarding Detection Version 1

DSCP Marking on RPM-XF Management Interface

Flash MIB Support

SNMPv3

Trap Squelch Feature

Bidirectional Forwarding Detection Version 1

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

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

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

Flash MIB Support

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

SNMPv3

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

The large number of traps a large system 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 following limitations apply:

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 PXM45C

With 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.20

Release 5.3.20 has the following new and changed features:

MPSM Licensing Changes

Support for Clear Channel E1 Lines

Support for BERT Tests on Clear Channel T3/E3 Lines

MPSM Licensing Changes

Release 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.20
5.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


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 Lines

Release 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 9
M8850_SF.27.MPSM16T1E1[FR].a > addport 11 1.10 1 0
M8850_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 Lines

Release 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

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

Release 5.3.10 includes the following new features and warnings.

Enhanced VXSM Card Support

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

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 Environment

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

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

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

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

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:

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


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.

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

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 Services

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

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.

Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10

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.

Security Enhancements

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

Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10

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

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.

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)


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 Enhancements

You 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

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.

The following quick start procedure summarizes the PXM configuration procedure.

 
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.

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-point
Router(config-subif)#ip address 10.10.10.200 255.255.255.0
Router(config-subif)#pvc 0/100
Router(config-if-atm-vc)#ubr 1544
Router(config-if-atm-vc)#switch connection vcc 0 100 master remote
Router(config-if-swconn)#end
Router#show switch connection vcc 0 100
----------------------------------------------------------
Alarm state           : No alarm 
Local Sub-Interface   : 100
Local VPI             : 0
Local VCI             : 100
Remote NSAP address   : default                                    
Local NSAP address    : 47.0091810001040000ABCD7777.000001011802.00
Remote VPI            : 0
Remote VCI            : 0

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.0
LA.8.PXM.a > svcifconfig atm0 remote 47.0091810001040000ABCD7777.000001011802.00 pvc 0.100
LA.8.PXM.a > dspsvcif
M8850_LA                         System Rev: 05.02   Apr. 25, 2006 16:36:38 PST
MGX8850                                              Node Alarm: NONE
IP 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 Cards

Extended 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

Platform Enhancements

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

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

RPM-PR Ethernet Back Card

The 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

 

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

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

100 Mbs

Up to 100 meters

1000 Mbs

Up to 50 meters


Features in Release 5.2.10

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

Features in Release 5.2.00

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

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

The 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

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.

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 Cards

You 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.5.10.

Multilink PPP on the MPSM-T3E3-155 Card

This 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

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 Chassis

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

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

The 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

Features in Release 5.1.20

Release 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

Features in Release 5.1.00

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

MPSM-16-T1E1 Card

MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics

Private Network Node Interface Current Route Feature

PNNI Product Enhancements

PXM1E OAM Enhancement

MPSM-16-T1E1 Card

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

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.

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.

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 Diagnostics

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

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

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.

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 Enhancements

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

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.


PXM1E OAM Enhancement

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

System Requirements

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

Software/Firmware Compatibility Matrix

Table 5 lists Cisco WAN or Cisco IOS Software products that are compatible with Release 5.5.10.

Table 5 Release 5.5.10 Compatibility Matrix 

Switch or Component
Compatible Software Version

Cisco MGX 8230 (PXM1)

Cisco MGX 8250 (PXM1)

Cisco MGX 8850 (PXM1)

MGX 1.3.18

MGX 1.3.16

MGX 1.3.14

Cisco MGX 8830/B (PXM45/C)

MGX 5.5.10

MGX 5.5.00

MGX 5.4.30

MGX 5.4.10

MGX 5.3.20

MGX 5.3.10

Cisco MGX 8830 (PXM1E)

Cisco MGX 8830/B (PXM1E)

Cisco MGX 8850 (PXM1E and PXM45)

Cisco MGX 8850/B (PXM1E and PXM45)

Cisco MGX 8950 (PXM45)

MGX 5.5.10

MGX 5.5.00

MGX 5.4.30

MGX 5.4.10

MGX 5.3.20

MGX 5.3.10

BPX Switch Software

Switch Software 9.4.12

BXM firmware MFZ

Cisco WAN Manager

16.0.00

Cisco MGX 8220 Shelf

MGX 8220 5.0.20

Cisco SES PNNI

4.0.15

3.0.25

Cisco IOS RPM-PR

12.4(15)T9

12.4(15)T7

12.4(15)T1

12.4(6)T10

Cisco IOS RPM-XF

12.4(15)T9

12.4(15)T7

12.4(15)T1

12.4(6)T10

VISM-PR

3.3.35.203

3.3.35

3.3.30

3.3.25

3.3.20

VXSM

5.5.10

5.5.00

5.4.20

5.4.00

5.3.30

5.3.10


MGX and RPM Software Version Compatibility Matrix

Table 6 lists the software that is compatible for use in a switch running Release 5.5.10 software.

Table 6 MGX and RPM Software Version Compatibility Matrix 

Board Pair
Boot Software
Runtime Software

PXM45/B

pxm45_005.005.010.200_bt.fw

pxm45_005.005.010.200_mgx.fw

PXM45/C

PXM45/C MGX 8830/B chassis

pxm45_005.005.010.200_bt.fw

pxm45_005.005.010.200_m30.fw

PXM1E-4-155 MGX 8850 (PXM1E) chassis

pxm1e_005.005.010.200_bt.fw

pxm1e_005.005.010.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

PXM1E-4-155 MGX 8830 chassis

pxm1e_005.005.010.200_bt.fw

pxm1e_005.005.010.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.005.010.200_bt.fw

axsm_005.005.010.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.005.010.200_bt.fw

axsme_005.005.010.200.fw

AXSM-8-155-E

AXSM-16-T3E3-E

AXSM-32-T1E1-E

AXSM-16-155-XG

axsmxg_005.005.011.200_bt.fw

axsmxg_005.005.011.200.fw

AXSM-8-622-XG

AXSM-4-2488-XG

AXSM-1-9953-XG

MPSM-16-T1E1

mpsm16t1e1_005.005.010.200_bt.fw

mpsm16t1e1_005.005.010.200.fw

MPSM-16-T1E1-PPP

mpsm16t1e1ppp_005.005.010.200.fw

MPSM-T3E3-155

mpsm155_005.005.010.200_bt.fw

mpsm155_005.005.010.200.fw

MPSM-T3E3-155-PPP

mpsm155ppp_005.005.010.200.fw

MPSM-8-T1E1

mpsmt1e1_030.005.010.200_bt.fw

mpsmt1e1_030.005.010.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.005.010.200.fw

AX-CESM-8T1

MGX-CESM-8T1/B

MGX-AUSM-8T1/B

ausm_8t1e1_AU8_BT_1.0.02.fw

ausm_8t1e1_022.005.010.200.fw

MGX-AUSM-8E1/B

AX-FRSM-8T1

frsm_8t1e1_FR8_BT_1.0.06.fw

frsm_8t1e1_022.005.010.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.005.010.200.fw

MGX-FRSM-2CT3

MGX-FRSM-2T3E3

MGX-RPM-PR-256

rpm-boot-mz.124-15.T9

rpm-js-mz.124-15.T9

MGX-RPM-PR-512

MGX-RPM-XF-512

rpmxf-boot-mz.124-15.T9

rpmxf-k9p12-mz.124-15.T9

(Crypto image)

rpmxf-p12-mz.124-15.T9

(non-Crypto image)

MGX-VXSM-155

vxsm_005.005.010.200_bt.fw

vxsm_005.055.010.200.fw

(CALEA image)

vxsm_005.005.010.200.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.035.203.fw

(CALEA image)

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

MGX-VISM-PR-8E1


SNMP MIB Release

The SNMP MIB file for Release 5.5.10 is mgx8850rel5510mib.tar.

Supported Hardware

This 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

Hardware in Release 5.5.10

Release 5.5.10 introduces no new hardware:

Release 5.5.00 introduces no 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
APS
Con
Minimum 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830 and 8830/B
PXM1E
MGX 8950
PXM45

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

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 1

800-07409-02-A0

PXM-UI-S3/B

800-21557-01-A0

PXM1E-8-T3E3

800-18590-03-A0

SMB-8-T3

800-05029-02-A0

x

x

SMB-8-E3

800-04093-02-A0

PXM-UI-S3/B

800-21557-01-A0

PXM1E-16-T1E1

800-18658-04-A0

MCC-16-E1

800-19853-02-A0

x

x

RBBN-16-T1E1

800-21805-03-A0

PXM-UI-S3/B

800-21557-01-A0

PXM1E-T3E3-155

Also referred to as

PXM1E-COMBO

800-18604-03-A0

MGX-T3E3-155

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 8 MGX Chassis, Card, and APS Configurations Part 2 

Front Card Type
Minimum 800 Part Number and Revision
Back Card Types
APS
Con
Minimum 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830 and 8830/B
PXM1E
MGX 8950
PXM45

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

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.


Table 9 MGX Chassis, Card, and APS Configurations Part 3 

Front Card Type
Minimum 800 Part Number and Revision
Back Card Types
APS
Con
Minimum. 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830 and 8830/B
PXM1E
MGX 8950
PXM45

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

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

AXSM-16-155

800-05776-06-A0

MMF-8-155-MT

Yes

800-04819-01-A1

x

SMFIR-8-155-
LC

Yes

800-05342-01-A0

SMFLR-8-155-
LC

Yes

800-05343-01-C0

AXSM-16-155/B

800-07909-05-A0

MMF-8-155-
MT/B

Yes

800-01720-02-A0

x

x

SMFIR-8-155-
LC/B

Yes

800-07864-02-B0

SMFLR-8-155-
LC/B

Yes

800-07865-02-B0

AXSM-8-155-E

800-18520-02-A0

SMB-4-155

Yes

800-07425-02-A0

x

MMF-4-155/C

Yes

800-07408-02-A0

SMFIR-4-155/C

Yes

800-07108-02-A0

SMFLR-4-155/C

Yes

800-07409-02-A0

AXSM-16-T3E3

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.


Table 10 MGX Chassis, Card, and APS Configurations Part 4 

Front Card Type
Minimum 800 Part Number and Revision
Back Card Types
APS
Con
Minimum 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830 and 8830/B
PXM1E
MGX 8950
PXM45

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

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.


Table 11 MGX Chassis, Card, and APS Configurations Part 5 

Front Card Type
Minimum 800 Part Number and Revision
Back Card Types
APS
Con
Minimum 800 Part Number and Revision
MGX 8850 and 8850/B
PXM45
MGX 8850 and 8850/B
PXM1E
MGX 8830/B
PXM45
MGX 8830 and 8830/B
PXM1E
MGX 8950
PXM45

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

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

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-12
POS-IR

800-08359-05-A0

MGX-2OC-12
POS-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.


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.

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 Type
MGX-APS-CON
800-05307-01
MGX-8850-APS-CON
800-20640-01-A0
MGX-8830-APS-CON
800-05308-02
MGX-8950-APS-CON
800-15308-01-A0

MGX 8850 (PXM45)

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155

AXSM-16-155/B

AXSM-4-622

AXSM-4-622/B

AXSM-1-2488

AXSM-1-2488/B

AXSM-16-155-E

AXSM-2-622-E

AXSM-16-155-XG

MGX-SRME

MGX-SRME/B

MPSM-T3E3-1551

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

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

1 Required only if running in OC-3 mode.

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


Service Class Template File Information

This section contains Service Class Template (SCT) file information for Release 5.5.10.

PXM1E SCT Files

The 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.5.10 explains how to upgrade a SCT file to a new minor version.

AXSM and AXSM/B SCT Files

The 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

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 Files

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

The 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

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 Files

The 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

MPSM-16-T1E1 SCT Files

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

This section contains the new and changed commands in Release 5.5.10, Release 5.5.00, Release 5.4.00, Release 5.3.20, and Release 5.3.00.

New Commands in Release 5.5.10

The following commands are introduced in this release:

cnfcdresetppp

Enables or disables the MPSM card reset when all PPP links go down.

Service Context—PPP

Modules— MPSM155, MPSM16T1E1

Enter the cnfcdresetppp command to enable or disable the MPSM card reset.

Syntax

cnfcdresetppp <auto restart> <timer>

Syntax Description

auto restart

Causes the MPSM card to restart automatically. Valid values are:

1: Enables auto restart. The default value is 1.

2: Disables auto restart.

timer

Seconds in which the timer expires. The valid range is 3 to 86400. The default value is 3 seconds.


Attributes

Log: no

State: active

Privilege: any


Related Commands

dspcdresetppp

Example

In the following example, the user enables auto restart:

n201.6.MPSM155PPP[FR].a > cnfcdresetppp 1 20

cnfloginbanner

Configures the path of the banner file.

Service Context—NA

Modules— PXM45, PXM1E

Enter the cnfloginbanner command to configure the path of the banner file.

Syntax

cnfloginbanner <loginmethod> <path>

Syntax Description

loginmethod

Method used for authentication during the login (for example FTP and Telnet.)

path

Path of the banner file. The value can be a string with a maximum of 42 characters. The maximum size of the banner file can be 1024 bytes.


Attributes

Log: no

State: active

Privilege: any


Related Commands

dsploginbanner

Example

In the following example, the user sets the banner path file:

Unknown.7.PXM.a > cnfloginbanner telnet F:SSHD/telnet_banner

path F:SSHD/telnet_banner added to local database

cnfstdbyrpmdpc

Enables or disables data-path checking on standby RPM-XF cards.

Service Context—ATM

Modules— PXM45, PXM1E

Enter the cnfstdbyrpmdpc command to enable or disable data-path check on RPM-XF.

Syntax

cnfstdbyrpmdpc <slot> <onEnb> [<interval> <retry>]

Syntax Description

slot

Slot of the standby RPM-XF card.

onEnb

Enables or disables the data-path checking. Values are:

enable: Enables data-path checking.

disable: Disables data-path checking. The default value is disable.

interval

Interval between two successive DPC packets. The valid range is 1 to 600 seconds

retry

Number of attempts. The valid range is 1 to 60.


Attributes

Log: no

State: active

Privilege: any


Related Commands

dspstdbyrpmdpc

Example

In the following example, the user enables data-path checking on a standby RPM-XF card:

Unknown.7.PXM.a > cnfstdbyrpmdpc 10 enable

cnfstdbyrpmdpc: Do you want to proceed (Yes/No)? y
Interval value is 6
Retry Value is 5

dspcdresetppp

Displays the autorestart details.

Service Context—PPP

Modules— MPSM155, MPSM16T1E1

Enter the dspcdresetppp command to display the autorestart details.

Syntax

dspcdresetppp

Syntax Description

This command has no arguments.

Attributes

Log: no

State: active

Privilege: any


Related Commands

cnfcdresetppp

Example

In the following example, the user displays the autorestart details:

n201.6.MPSM155PPP[FR].a > dspcdresetppp

AutoRestart:Enabled
Timer : 3

dsploginbanner

Displays the banner path details.

Service Context—NA

Modules— PXM45, PXM1E

Enter the dsploginbanner command to display the banner path details.

Syntax

dsploginbanner

Syntax Description

This command has no arguments.

Attributes

Log: no

State: active

Privilege: any


Related Commands

cnfloginbanner

Example

In the following example, the user displays the path of the banner file:

Unknown.7.PXM.a > dsploginbanner 
Local database information
    loginmethod           path
    -------------------------

    telnet                F:SSHD/telnet_banner
    ftp                   F:SSHD/ftp_banner

dspstdbyrpmdpc

Displays the status of data-path checking on standby RPM-XF cards.

Service Context—ATM

Modules— PXM45, PXM1E

Enter the dspstdbyrpmdpc command to display the status of data-path checking.

Syntax

dspstdbyrpmdpc <slot>

Syntax Description

slot

Slot of the standby RPM-XF card.


Attributes

Log: no

State: active

Privilege: any


Related Commands

cnfstdbyrpmdpc

Example

In the following example, the user displays the status of data-path checking on an RPM-XF card:

Unknown.7.PXM.a > dspstdbyrpmdpc 10
DPC feature is disabled for STANDBY RPM-XF slot 10
Interval Value =  6
Retry Value = 5

New Commands in Release 5.5.00

The following commands are introduced in this release:

cnfdaylightsetting

Enables Daylight Saving on MGX 88xx switch controller.

Modules—MGX 88xx

The cnfdaylightsetting command helps you to configure the daylight saving on a Cisco MGX 88xx switch controller.

Syntax

cnfdaylightsetting <status> [Start] [StdTmZn] [End] [SumTmZn]

Syntax Description

status

Status of the Daylight Saving on the card. You can either enable or disable the Daylight Saving feature. Valid values are enable and disable.

Default: disable

Start

Specifies the start date of the Daylight Saving time. The date should be entered in the following format: which-day-mon-hhmm.

Valid values for which are: 1st, 2nd, 3rd, 4th, 5th, last

Valid values for day are: Sun, Mon, Tue, Wed, Thu, Fri, Sat

Valid values for mon are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec

The time should be in the standard time format.

StdTmZn

The standard time zone. Valid values are:

GMT, EST, CST, MST, PST, -12, -11, -10, ... 10, 11, 12

End

Specifies the end date of the Daylight Saving. The date should be entered in the following format: which-day-mon-hhmm.

Valid values for which are: 1st, 2nd, 3rd, 4th, 5th, last

Valid values for day are: Sun, Mon, Tue, Wed, Thu, Fri, Sat

Valid values for mon are: Jan, Feb, Mar, Apr, May, Jun, Jul, Aug, Sep, Oct, Nov, Dec

The time should be in the standard time format.

SumTmZn

The summer time zone. Valid values are:

EDT, CDT, MDT, PDT, -12, -11, -10, ...10, 11, 12


Attributes

Log: yes

State: active

Privilege: any


Example

In the following example, the user enables the Daylight Saving feature:

M8850_SF.7.PXM.a > cnfdaylightsetting enable 1st-Sun-Nov-1230 GMT 1st-Mon-Dec-1230 EDT

cnfmultivc

Enables or disables Multi-VC access to the PXM.

Service Context—ATM

Modules— PXM

The cnfmultivc command either enables or disables Multi-VC access to the PXM.

Syntax

cnfmultivc <enable|disable>

Syntax Description

enable

Enables Multi-VC access to the PXM.

disable

Disables Multi-VC access to the PXM.


Attributes

Log: yes

State: active

Privilege: any


Example

The following example shows how to enable Multi-VC Access: 

M8830_SF.1.PXM.a > cnfmultivc enable
Multi VC feature is enabled

cnftxtraceopt

Enables or disables the J1 byte Configuration on XG cards.

Service Context—ATM

Modules— XG

Enter the cnftxtraceopt command to disable or enable the J1 byte TxTrace configuration.

Syntax

cnftxtraceopt <0/1>

Syntax Description

0/1

0: Disables the TxTrace option.

1: Enables the TxTrace option.


Attributes

Log: yes

State: active

Privilege: any


Example

In the following example, the user enables the J1 byte TxTrace feature:

Unknown.12.AXSM-XG[ATM].a > cnftxtraceopt 1

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


Attributes

Log: yes

State: active

Privilege: any


Example

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

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

delprevdbs

Delete previous databases.

Modules— PXM

Enter the delprevdbs command to delete previous databases.

Syntax

delprevdbs <slot-id>

Syntax Description

slot-id

This parameter displays the slot number of the card.


Attributes

Log: yes

State: active

Privilege: group1


Example

The following example deletes all the pervious versions of databases in the slot:

M8850_NY.7.PXM.a > delprevdbs 2

The SHM and Disk DB other than the current revision will be cleared for
the specified slot. Once started, this command should 
not be aborted as doing that can leave the shelf in 
an indeterminate state.
For this reason, this command cannot be aborted 
using ctrl-C or by using any other command

delprevdbs: Do you want to proceed (Yes/No)? 

dspbundleconfiginfo

Displays the configuration information related to a bundle.

Service Context— PPP

Modules— MPSM

Enter the dspbundleconfiginfo command to display the output of the commands.

Syntax

dspbundleconfiginfo <bundle number>

Syntax Description

bundle number

The bundle number.


Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM:

admin.MPSM155PPP[FR].a > dspbundleconfiginfo 1

--------------------------------dspBundleInfo----------------------------

Bundle Number : 1

Admin State : Up

Oper State : Down

Alarm Cause : No Link

MRRU : 1524

SeqNumFormat : 24 bit

Fragmentation : Disable

EndpointDiscrimClass : Locally Assigned

EndpointDiscriminator : Kadamba.22.1

LinksConfigured : 2

LinksActive : 0

RemoteMRRU : 0

RemoteEndpDiscrimClass : Null

RemoteEndpDiscriminator:

Configured Bandwidth : 3072000

Available Bandwidth : 0

--------------------------------dspPppLinkInfo----------------------------

PPP Link ID : 1

AdminStatus : Up

OperState : Down

Fail Reason : LowerLayerDown

BundleID : 1

PhysicalLineID : 1.1:1

DS1LinkStartDS0 : 1

DS1LinkNumDS0 : 24

DS1Link56KbpsMode : Disable

MRU : 1500

LcpTimeout : 10000

LcpLoopCheck : Enable

RemoteMRU : 0

PFCReceive : Enable

ACFCReceive : Enable

PFCTransmit : Disable

ACFCTransmit : Disable

PFCTransmitOper : Disable

ACFCTransmitOper : Disable

LinkDescriptor : LineSide

RestartTimer : 3000

MaxConfigReqRetry : 10

Type <CR> to continue, Q<CR> to stop:

MaxTerminateReqRetry : 2

LcpMaxEchoReqRetry : 5

MaxFailures : 5

--------------------------------------dspPppMuxInfo---------------------------------------

Mux Bundle Number : 1

Mux Protocol Status : ProtocolDown

MuxEnable State : Enable

MuxOperStatus : OperDown

DeMuxEnable State : Enable

DeMuxOperStatus : OperDown

DeMuxPID : 33

DeMuxRemotePID : 33

MuxTimer : 600

MuxMaxSubFrameLength : 64

MuxMaxSubFrameCount : 15

MuxMaxFrameLength : 256

----------------------------------dspConnInfo---------------------------------------------

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

Local : NSAP Address vpi vci

(M) 47009181000000000005230003000001051FFF00 54 1000

Remote : NSAP Address vpi vci

(S) 4700918100000000000523000300000101180200 0 133

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

Port Number : 1 DLCI : 1000

Conn. Type : frForward Chan Service Type: nrtVBR

Conn Service Type : vbr3nrt Egress Queue Type: lowPriority

Admn Status : UP Oper Status : OK

Slave Persist : YES Max Cost : 2147483647

CIR (bps) : 1536000 BC (bytes) : 10300

BE (bytes) : 10300 FECN Config : setEFCIzero

ChanDEtoCLPmap : setCLPzero ChanCLPtoDEmap : ignoreCLP

IngrPercentUtil : 100 EgrPercentUtil : 100

EgrSrvRate (bps) : 1536000 ZeroCirEir (bps) : N/A

DE Tagging : DISABLED IgnoreIncomingDE : DISABLED

Pref Rte Id : 0 Directed Route : NO

Upload : 0000375c Routing Priority : 8

OAM CC Config : DISABLED Statistics : ENABLED

Local Loopback : DISABLED UPC : ENABLED

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

Type <CR> to continue, Q<CR> to stop:

Local PCR (cps) : 8600 Remote PCR (cps) : 8600

Local SCR (cps) : 8600 Remote SCR (cps) : 8600

Local MCR (cps) : N/A Remote MCR (cps) : N/A

: Remote MBS (cps) : 1024

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

Xmt Abit State : A equal 1 Rcv Abit State : OFF

Xmt ATM State : Not Sending Rcv ATM State : Not Recving

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

E-AIS/RDI CONDITIONED CCFAIL IfFail Mismatch LMI-ABIT

NO NO NO NO NO NO

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

dspbundlestatsinfo

Displays the statistics information related to a bundle.

Service Context— PPP

Modules— MPSM

Enter the dspbundlestatsinfo command to display the output of the commands.

Syntax

dspbundlestatsinfo <bundle number> <interval>

Syntax Description

bundle number

The bundle number.

interval

The interval between the start of one transmission and the start of the next transmission.


Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM:

admin.MPSM155PPP[FR].a > dspbundlestatsinfo 2 3
---------------dspBundleCntInfo                    ---------------
  MLPPP Bundle Number          : 2         
  Interval Number              : 3         

  Receive Packets              :          0
  Receive Bytes                :          0
  Receive Discard Bytes        :          0
  Receive MRRU Error Packets   :          0
  Receive Discard Packets      :          0
  Receive kbpsAIR              :          0
  Send Packets                 :          0
  Send Bytes                   :          0
  Send kbpsAIR                 :          0


---------------dspPppMuxCntInfo                    ---------------
  MLPPP MUX Number          : 2         
  Interval Number           : 3         

  Receive Subframes         :          0
  Receive Packet            :          0
  Receive Error Packets     :          0
  Send Sub Frames           :          0
  Send Packets              :          0
  Send Non-Mux Packets      :          0


---------------dspPppLinkInfo                    ---------------

---------------dspPppLinkCntInfo 						 		 	 	 	 	---------------
  MLPPP Link Number            : 2         
  Interval Number              : 3         

  Receive Packets              :          0
  Receive Bytes                :          0
  Receive Discard Bytes        :          0
  Receive MRU Errors           :          0
  Receive Miscellaneous Errors :          0
  Receive kbpsAIR              :          0
  Send Packets                 :          0
  Send Bytes                   :          0
  Send kbpsAIR                 :          0


---------------dspChanCntInfo                    ---------------
------------------------------------------------------------------------------
Port Number               :          2  DLCI                      :       1000
Up Time (seconds)         :          0
------------------------------------------------------------------------------
           Ingress chan stat
-----------------------------------------------
Rcv Frames                     : 93                  
Rcv Frames Discard             : 0                   
           Egress chan stat
-----------------------------------------------
Xmt Frames                     : 650726              
Xmt Frames Discard             : 0                   

Type <CR> to continue, Q<CR> to stop: 
Xmt Frames CRC Error           : 0 

dspdaylightsetting

Displays daylight saving settings.

Service Context—PPP

Modules— MGX88XX

Enter the dspdaylightsetting command to display the daylight saving settings.

Syntax

dspdaylightsetting

Syntax Description

This command has no arguments or keywords.

Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user displays the daylight saving settings:

M8850_SF.7.PXM.a > dspdaylightsetting
Daylight Saving is disabled.

dspdeverr

Displays the errors detected by a device. It also displays the hardware alarm raised by a device.

Service Context—ATM

Modules— MPSM

Enter the dspdeverr command to display the errors detected by a device.

Syntax

dspdeverr <device name>

Syntax Description

device name

The name of the hardware device. For instance, APOX, CBC155, IMA84, and WinPath.


Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM card:

admin.MPSM155PPP[FR].a > dspdeverr APOX
CURRENT ERROR COUNT FOR DEVICE APOX   (Alarm : None )
----------------------------------------------------------------
Error Type
-----------
APPI Ingress Parity Err 
APPI Ingress Protocol Err
PPL3 Ingress Header Parity Err
PPL3 Ingress Payload Parity Err
...
Total Errors
------------
0
0
0
0
 

dspdeverrhist

Displays the errors reported by the device since the last reset of the card or clearing the device errors.

Service Context—FR

Modules—MPSM

Enter the dspdeverrhist command to display the errors reported by the device since the last reset of the card or clearing the device errors.

Syntax

dspdeverrhist <device name>

Syntax Description

device name

The name of the hardware device. For instance, APOX, CBC155, IMA84, or WinPath.


Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM card:

admin.MPSM155PPP[FR].a > dspdeverr APOX
CURRENT ERROR COUNT FOR DEVICE APOX   (Alarm : None )
----------------------------------------------------------------
Error Type
-----------
APPI Ingress Parity Err
APPI Ingress Protocol Err
PPL3 Ingress Header Parity Err
PPL3 Ingress Payload Parity Err
...
Total Errors
------------
0
0
0
0
 

dspmultivc

Displays whether the Multi-VC access is on or off.

Service Context—ATM

Modules— PXM

The dspmultivc command displays whether Multi-VC access is on or off.

Syntax

dspmultivc

Syntax Description

This command has no arguments or keywords.

Attributes

Log: no

State: active

Privilege: any


Example

The following example shows how to display the status of the Multi-VC access feature: 

M8830_SF.1.PXM.a > dspmultivc
Multi VC feature is disabled

dsptxtraceopt

Displays the J1 byte Configuration on XG cards.

Service Context—ATM

Modules— XG

Enter the dsptxtraceopt command to display the J1 byte TxTrace configuration.

Syntax

dsptxtraceopt

Syntax Description

This command takes no arguments.

Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user displays the J1 byte TxTrace configuration:

Unknown.12.AXSM-XG[ATM].a > dsptxtraceopt
Tx Trace Option is set to TRUE

These commands do not apply to the following cards:

XG OC48

XG OC 192

The following error is displayed if these commands are applied:

Err: Command is not applicable for this card type

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

Log: no

State: active

Privilege: any


Example

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

Unknown.12.AXSM-XG[ATM].a > dspvctrefresh
Active VCT Memory Refresh : enable
Automatic Card Reboot : enable

showtech

Displays the output of a series of commands.

Modules— PXM, MPSM

Enter the showtech command to display the output of the commands.

Syntax

showtech

Syntax Description

This command has no arguments or keywords.

Attributes

Log: yes

State: active

Privilege: super group


Example

In the following example, the user executes the command on a PXM:

POP2-3.8.PXM.a > showtech

This command will take time to complete.

showtech: Do you want to proceed (Yes/No)? y

********************************** show cards **********************************

Unknown System Rev: 05.04 Jul. 18, 2008 10:34:09 GMT

Chassis Serial No: 12345 Chassis Rev: 80 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Alarm Redundant Redundancy

Slot Card State Type Status Slot Type

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

01 Failed/Empty AXSM-32-T1E1-E MINOR NA NO REDUNDANCY

02 Empty --- --- --- ---

03 Empty --- --- --- ---

04 Empty --- --- --- ---

05 Empty --- --- --- ---

06 Empty --- --- --- ---

07 Active/Active PXM45 MAJOR 08 PRIMARY SLOT

08 Empty Resvd/Empty --- MAJOR 07 SECONDARY SLOT

09 Empty --- --- --- ---

10 Active/Active AXSM_16OC3 CRITICAL NA NO REDUNDANCY

11 Active/Active AXSM_4OC12_B CRITICAL NA NO REDUNDANCY

12 Empty --- --- --- ---

13 Active/Active MPSM-T3E3-155-PPP CRITICAL NA NO REDUNDANCY

14 Active/Active MPSM-T3E3-155-PPP NONE NA NO REDUNDANCY

15 Empty --- --- --- ---

Type <CR> to continue, Q<CR> to stop:

Unknown System Rev: 05.04 Jul. 18, 2008 10:34:09 GMT

Chassis Serial No: 12345 Chassis Rev: 80 GMT Offset: 0

Node Alarm: CRITICAL

Card Front/Back Card Alarm Redundant Redundancy

Slot Card State Type Status Slot Type

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

16 Empty --- --- --- ---

21 Empty --- --- --- ---

29 Boot/Empty FRSM_HS2 NONE NA NO REDUNDANCY

30 Failed/Empty MPSM-T3E3-155 MINOR NA NO REDUNDANCY

31 Empty --- --- --- ---

32 Empty --- --- --- ---

******************************* show node alarms *******************************

Node Alarm Summary

Alarm Type Critical Major Minor

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

Clock Alarms 0 1 0

Switching Alarms 3 0 0

Environment Alarms 0 0 0

Card Alarms 756 184 4

******************************* show clock alarms ******************************

Unknown System Rev: 05.04 Jul. 18, 2008 10:34:10 GMT

MGX8850 Node Alarm: CRITICAL

Clock Manager Alarm Summary

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

NETWORK CLOCK ALARM : STANDBY CLOCK NOT READY - NO CLOCK REDUNDANCY : MAJOR

Critical Major Minor

000 001 000

...

In the following example, the user executes the command on an MPSM:

POP2-3.20.MPSM155PPP[FR].a > showtech

This command will take time to complete.

Do you want to process (Yes/No)? y

---------------------------show card info-----------------------

Front Card Back Card

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

Card Type: MPSM-T3E3-155-PPP ---

State: Active Absent

Serial Number: SAD080605DT ---

Boot FW Rev: 5.3(20.200) ---

SW Rev: 5.4(218.1)D ---

HW Rev: 02 ---

Orderable Part#: 800-22339-04 000-00000-00

PCA Part#: 73-8597-05 00-0000-00

CLEI Code: 0 ---

Reset Reason: Reset from PXM

Card Summary:

Card SCT Id: 0

Features Enabled: FRAME RELAY

#Max ATM Conns #ATM Ports #ATM Partitions #ATM SPVCs #ATM SPVPs #ATM SVCs

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

0 0 0 0 0 0

#Max FR Conns #FR Ports #FR Partitions #FR SPVCs

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

128 0 0 0

#IMA Groups #IMA Links #MP Bundles #PPP Links

Type <CR> to continue, Q<CR> to stop:

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

0 0 0 0

FC Operation Mode: CARD_OPER_MODE_NONE

First Available Port Number: 4

------------------------show interfaces----------------------

Interfaces Total Max Admin Up Available Alarm

Physical Lines 0 0 0 0

Sonet STS/SDH-AU 0 0 0 0

Sonet/SDH-TU 0 0 0 0

DS3 0 0 0 0

E3 0 0 0 0

DS1 0 0 0 0

E1 0 0 0 0

MP Bundles 128 0 128 0

PPP Links 256 0 256 0

winpath Total Max Configured

MpBundles on WP 1 96 0

MpBundles on WP 2 96 0

Confg BW on WP 1 2016 DS0s 0 DS0s

Confg BW on WP 2 2016 DS0s 0 DS0s

Interfaces Total Max Configured Available Alarm

FR Ports 128 0 128 0

FR Connections 128 0 128* 0

Signaling connections are not included here.

------------------show resource monitoring alarms---------------

ID Name Critical Major Minor

0 Static Memory 0 0 0

1 Dynamic Memory 0 0 0

2 Stats Memory 0 0 0

3 SNMP Memory 0 0 0

4 IPC Small Buffer 0 0 0

5 IPC Medium Buffer 0 0 0

6 IPC Large Buffer 0 0 0

7 IPC Huge Buffer 0 0 0

8 IPC MBlk Buffer 0 0 0

9 CPU Free 0 0 0

10 System Memory 0 0 0

11 Timer 0 0 0

12 FD(File Descriptor) 0 0 0

13 VxWorks FD 0 0 0

14 System Uptime 0 0 0

TOTAL: 0 0 0

......

Changed Commands in Release 5.5.00

Release 5.5.00 contains the following changed commands:

cnfndparms

cnfrmrsrc

dspcds

dsprmrsrc

dsprmrsrcs

cnfndparms

Configures the node-wide parameters.

The cnfndparms command configures the node-wide parameters. A new option 17 is added to enable or disable SSHV1.

Syntax

cnfndparms [1-17]

Syntax Description

17

Enables or disables SSHV1. Valid values are:

Yes: SSHV1 access to this node is disabled. Use SSHV2 to remotely log in to the node.

No: SSHV1 access to this node is enabled. Telnet access depends on what is configured for the Telnet option in the node parameters.


Attributes

Log: yes

State: active

Privilege: SUPER_GP


Example

The following example shows how to enable SSHV1:

M8850_SF.7.PXM.a > cnfndparms

M8850_SF                         System Rev: 05.04   Oct. 26, 2007 00:41:36 PST
MGX8850                                              Node Alarm: MINOR
NODE CONFIGURATION OPTIONS
Opt#  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 Decimal   Obsolete, Use dsprcons for Gang Card Status  
13    0           8bit Decimal   Card Switchover on Backcard 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 Disable
17    Yes         Boolean        SSH V1 & Telnet Access To Node Disabled      


Enter option number (1-17): 17
NODE CONFIGURATION OPTIONS
Opt#  Value       Type           Description
----  -----       ----           -----------
17    Yes         Boolean        SSH V1 & Telnet Access To Node Disabled      
Enable/Disable SSHV1 & Telnet access to this node. If option set to:
    Yes:    SSH V1/Telnet access to this node is disabled.  This
            forces all incoming SSHV1/Telnet connections to be rejected by
            the node.  Use SSHV2 to remotely log in to the node 
     No:    SSH V1 access to this node is enabled. Telnet access depends on 
            what is configured for Telnet option in the Node parameters 
            Incoming SSH V1 connections will be accepted by the node.
            Use of other protocols such as SSHV2 and FTP/SFTP are still 
            supported for remotely logging into a terminal session  or transfer
            files to/from the node.

Enter value for option 17 (Y/N): yes
NODE CONFIGURATION OPTIONS
Opt#  Value       Type           Description
----  -----       ----           -----------
17    Yes         Boolean        SSH V1 & Telnet Access To Node Disabled

Note By default, access to SSHV1, FTP, and Telnet are enabled.


cnfrmrsrc

Configures the resource monitoring attributes.

In this release, a new resource Winpath is added.

Syntax

cnfrmrsrc <rsrcid> [-poll] [-loth] [-medth] [-hith]

Syntax Description

rsrcid

The resource index. The resource index ranges from 0 to 18.

poll

The polling interval in seconds. The interval ranges from 5 to 86400 seconds.

loth

Low threshold.

medth

Medium threshold.

hith

High threshold.


Attributes

Log: yes

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM card:

admin.MPSM155PPP[FR].a > cnfrmrsrc 15 -poll 50
========================[Resource Information]======================
Resource Name     : Winpath Ingress Buffer 0 	Maximum size          : 12160      
Resource State    : OK                     												Cur size (Byte)       :     
IgnoreMedium      : No                   												Low WaterMark         : 
Threshold Type    : value                												Poll interval (sec)   : 50        
Low threshold %   : 7.0                    												Low threshold value   : 10944
Medium threshold %: 8.0                 												Medium threshold value: 9728 
High threshold %  : 9.0                     												High threshold value  : 8512

==================[Action Information]=================
            Send         Alarm  Severity       Alarm
            Trap        Critical Major  Minor   Clear
Low Action: yes/major   no       yes     no      no       
Med Action: yes/major   no       no      yes     no       
Ok Action : yes/info    no       no      no      yes      

================[Statistics Information]===============
Total polls   : 3364          Failed polls       : 0       
Ok to low     : 0             Low to ok          : 0       
Ok to med     : 0             Med to ok          : 0        
Med to low    : 0        
Traps sent OK : 0             Traps sent failures: 0        
==================[Other Information]==================
Largest Free Size :               Hi priority alloc: 127
Low priority alloc: 2             Alloc failures   : 0 

dspcds

Display Cards—PXM45, PXM1E

In this release, the command dspcds is updated to display the status of the front cards and corresponding back cards.

Syntax

dspcds

Syntax Description

This command has no arguments or keywords.

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


Example

Display the cards in the current MGX 8850 switch.

M8850_SF.7.PXM.a > dspcds
M8850_SF                         System Rev: 05.04   Nov. 21, 2007 00:24:34 PST
Chassis Serial No:   SCA062300GF Chassis Rev: B0     GMT Offset: -8
                                                     Node Alarm: CRITICAL
Card Front/Back         Card              Alarm      Redundant   Redundancy 
Slot Card State         Type              Status     Slot        Type   
---  ----------         --------          --------   -------     -----  

01   Active/Active      RPM_XF            NONE       02          PRIMARY SLOT
02   Standby/Active     RPM_XF            CRITICAL   00          SECONDARY SLOT
03   Standby/Active     AXSME_8OC3        NONE       04          SECONDARY SLOT
04   Active/Active      AXSME_8OC3        NONE       03          PRIMARY SLOT
05   Active/Active      AXSM_4OC12_B      NONE       NA          NO REDUNDANCY
06   Active/Active      AXSM-32-T1E1-E    NONE       NA          NO REDUNDANCY
07   Active/Active      PXM45B            NONE       08          PRIMARY SLOT
08   Empty Resvd/Empty  ---               NONE       07          SECONDARY SLOT
09   Active/Active      MPSM-T3E3-155-PPP NONE       NA          NO REDUNDANCY
10   Active/Active      MPSM-T3E3-155     NONE       NA          NO REDUNDANCY
11   Empty              ---               ---        ---         ---    
12   Active/Active      FRSM_8T1          NONE       NA          NO REDUNDANCY
13   Active/Active      FRSM_8E1          NONE       NA          NO REDUNDANCY
14   Active/Active      FRSM_2CT3         NONE       NA          NO REDUNDANCY
15   Active/Active      SRME_OC3          NONE       16          PRIMARY SLOT
16   Empty              ---               ---        ---         ---    
25   Active/Active      MPSM-16-T1E1      NONE       NA          NO REDUNDANCY
26   Active/Active      CESM_8T1/B        NONE       NA          NO REDUNDANCY
27   Active/Active      MPSM-16-T1E1      NONE       NA          NO REDUNDANCY
28   Active/Active      MPSM-8T1-FRM      MINOR      NA          NO REDUNDANCY
29   Active/Active      MPSM_8E1_ATM      NONE       NA          NO REDUNDANCY
30   Active/Active      CESM_8E1          NONE       NA          NO REDUNDANCY
31   Active/Active      SRM_3T3           NONE       32          PRIMARY SLOT
32   Empty              ---               ---        ---         ---    

dsprmrsrc

Displays the details of the utilization of a particular resource.

In this release, a new resource Winpath is added.

Syntax

dsprmrsrc <rsrcid>

Syntax Description

rsrcid

The resource index. The resource index ranges from 0 to 18.


Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM card:

admin.MPSM155PPP[FR].a > dsprmrsrc 15
========================[Resource Information]======================
Resource Name     : Winpath Ingress Buffer 0 Maximum size : 12160         
Resource State    : OK 	 										Cur size (Byte):                    
IgnoreMedium      : No 		 									Low WaterMark :                    
Threshold Type    : value 											Poll interval (sec) : 30              
Low threshold %   : 7.0 											Low threshold value   : 10944   
Medium threshold %: 8.0 											Medium threshold value: 9728 
High threshold %  : 9.0 											High threshold value  : 8512     
==================[Action Information]=================
            Send         Alarm  Severity       Alarm
            Trap        Critical Major  Minor   Clear
Low Action: yes/major   no       yes     no      no       
Med Action: yes/major   no       no      yes     no       
Ok Action : yes/info    no       no      no      yes      

================[Statistics Information]===============
Total polls   : 3364          Failed polls       : 0       
Ok to low     : 0             Low to ok          : 0       
Ok to med     : 0             Med to ok          : 0        
Med to low    : 0        
Traps sent OK : 0             Traps sent failures: 0        
==================[Other Information]==================
Largest Free Size :               Hi priority alloc: 127
Low priority alloc: 2             Alloc failures   : 0 

dsprmrsrcs

Displays the resource utilization on a service module. Memory and buffer statistics are monitored continuously and current status is displayed.

In this release, a new resource Winpath is added.

Syntax

dsprmrsrcs

Syntax Description

This command has no arguments or keywords.

Attributes

Log: no

State: active

Privilege: any


Example

In the following example, the user executes the command on an MPSM card:

admin.MPSM155PPP[FR].a > dsprmrsrcs

Id     Name           State     Max     Current    Low    Medium    High  Enable
================================================================================
0  Static Memory        OK   73261056  22788224 6153840  6282045  7179480   ON 
1  Dynamic Memory       OK   19980288  19074128 2397600  2597400  2797200   ON 
2  Stats Memory         OK   39960576  39960576 479520   519480   559440    OFF
3  SNMP Memory          OK   13320192  13304352 799200   865800   932400    ON 
4  IPC Small Buffer     OK   4128      4126     1237     1340     1443      ON 
5  IPC Medium Buffer    OK   1400      1400     420      455      490       ON 
6  IPC Large Buffer     OK   1200      1200     360      390      420       ON 
7  IPC Huge Buffer      OK   856       856      255      276      298       ON 
8  IPC MBlk Buffer      OK   10084     10082    1209     1310     1411      ON 
9  CPU Free             OK   100       86       5        7        10        ON 
10 System Memory        OK   62452384  7550848  6245200  7494240  9367800   ON 
11 Timer                OK   1000      944      50       60       80        ON 
12 FD(File Descriptor)  OK   100       99       5        6        8         ON 
13 VxWorks FD           OK   500       500      25       32       40        ON 
14 System Uptime        OK   --        1        460      440      --        ON 
15 Winpath Ingres Buf0  OK   12160     12125    1216     2432     3648      ON 
16 Winpath Ingres Buf1  OK   12160     12128    1216     2432     3648      ON 
17 Winpath Egress Buf0  OK   16840     13032    1684     3368     5052      ON 
18 Winpath Egress Buf1  OK   16840     13519    1684     3368     5052      ON

Changed Commands in Release 5.4.00

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

Changed MPSM Commands

Changed PXM Commands

Changed AXSM Commands

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

cnfpart—Syntax was missing, but now displays.

cnfrscprtn—Syntax was missing, but now displays.

cnfapsln—Syntax was missing, but now displays.

Changed AXSM Commands

AXSME, AXSM, AXSMXG

cnfpart—Syntax was missing, but now displays.

cnfrscprtn—Syntax was missing, but now displays.

cnfapsln—Syntax was missing, but now displays.

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

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

clrallcnfNo longer has the clrLicense argument.

dspcdalmsNo longer displays license alarms.

dspndalmsNo longer displays license alarms.

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

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

This 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 1500
Warning: Bundle Config is being changed, traffic might be interrupted briefly
Do 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, and cnfppplink.

Remove ds0speed parameter from cnfppplink (CSCin97715). See cnfppplink.

cnfmpbundleparams

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

New normpvcbw parameter default: 9200 for E1.

dspmpbundles

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

dspmpbundlecnt and dspppplnkcnt

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

addport, dspport, and dspports

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

dsppathalmcnt

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

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

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.

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

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


Related Commands

cnfport, delport, dspport, dspports, dspportsct

Attributes

Log: yes

State: active

Privilege: GROUP1


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

Service Context—PPP

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

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-16-T1E1 range: 1-16

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-16-T1E1 range: 1-16

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

-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

-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


Attributes

Log: yes

State: active

Privilege: GROUP1


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

Service Context—PPP

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

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

-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

-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


Attributes

Log: yes

State: active

Privilege: GROUP1


Related Commands

addppplink, delppplink, dspppplink

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.


Related Commands

clrpathalmcnf

Attributes

Log: no

State: active, standby, init

Privilege: ANYUSER


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

Service Context—PPP

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

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

Syntax

dspmpbundles

Syntax Description

None

Attributes

Log: no

State: active

Privilege: any


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 > dspmpbundles
MLPPP    Admin  Oper    Active  Available       Alarm      MUX      AutoBW   WP
Bundle   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 > dspmpbundles
MLPPP   Admin  Oper    Active  Available       Alarm      MUX      AutoBW   WP
Bundle  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

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

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"

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

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.


Related Commands

addport, dnport, dspports

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


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.

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

dspports

Display Ports

Service Context—ATM, Frame Relay, PPP

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

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:

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.


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

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.

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.



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

Log: no

State: active, standby

Privilege: ANYUSER


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 > dspports
if  Line/Path  Admn Oper   Guarntd   Max    SCT  if      VPI         IMA DS0
Num 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 > dspports
if  Line/Path  Admn Oper   Guarntd   Max    SCT  if      VPI         IMA DS0
Num 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)

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 > dspports
ESR: Egress queue Service Ratio                                                
                                SCT DS0    Port                 E   FRF        
If   Line/Path   Admn Oper if   In  Start  Speed      Signaling LMI 12   MFR   
Num  Num         Stat Stat Type Use (Num)  kbps   ESR Type      St  Frg Bundle   
---- ----------- ---- ---- ---- --- ------ ------ --- --------- --- --- ------ 
   4         N/A   Up   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 > dspports

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

Service Context—PPP

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

Enter the dspmpbundlecnt command to display MLPPP bundle statistics.

Syntax

dspmpbundlecnt <bundleNumber> <intvl>

Syntax Description

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.

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.


Attributes

Log: no

State: active

Privilege: any


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

Service Context—PPP

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

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

Syntax

dspppplnkcnt <link> <intvl>]

Syntax Description

link

Specifies the PPP link number for which to display statistics.

Note Enter the dspppplinks command to display all MLPPP links on the card.

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.


Attributes

Log: no

State: active

Privilege: any


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

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.

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.

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.

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

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.

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

Yes

PXM1E-8-OC-3

No

Yes

1 Supported, but we recommend that you avoid this combination.


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.

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.

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.

0x02: PSU A2 is required.

0x04: PSU A3 is required.

0x10: PSU B1 is required.

0x20: PSU B2 is required.

0x40: PSU B3 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.

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.

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


Related Commands

dspndparms, dspndalms, dspenvalms, cnfcbclk, dspcbclk

Attributes

Log: no

State: active

Privilege: SUPER_GP


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 1800
NODE CONFIGURATION OPTIONS
Opt#  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 > cnfndparms
M8850_SF                         System Rev: 05.02   Feb. 11, 2006 05:48:41 GMT
MGX8850                                              Node Alarm: CRITICAL
NODE CONFIGURATION OPTIONS
Opt#  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 Decimal	Obsolete. 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): 10
NODE CONFIGURATION OPTIONS
Opt#  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): Y
NODE CONFIGURATION OPTIONS
Opt#  Value       Type           Description
----  -----       ----           -----------
10    Yes         Boolean        Auto Setting of Cellbus Clock Rate Enabled

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

This command takes no parameters.

Related Commands

cnfndparms

Attributes

Log: no

State: active, standby

Privilege: ANYUSER


Example

Display the current node parameters on this Cisco MGX 8850 switch with a PXM1E card.

PXM1E_NY.7.PXM.a > dspndparms
PXM1E_NY	System Rev: 05.03   Feb. 13, 2007 14:37:03 PST
MGX8850	Node Alarm: MAJOR
NODE CONFIGURATION OPTIONS
Opt#  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     0x0         8bit Hex									Required Power Supply Module Bitmap
5     0x0         8bit Hex									Required Fan Tray Unit Bitmap
6     0           8bit Decimal									Trap Manager Aging timeout value(Hour(s))
7     atm0        8bit Decimal									Primary IP interface for Netmgmt
8     lnPci0      8bit Decimal									Secondary IP interface for Netmgmt
9     Yes         Boolean									Auto Setting of Cellbus Clock Rate Enabled
10    Yes         Boolean									Inband Node-to-Node IP Connectivity Enabled
11    0           8bit Decimal									Obsolete. Use dsprcons for Gang Card Status
12    0           8bit Decimal									Card Switchover on Backcard FRU mismatch
13    No          Boolean									Card-to-Card High Priority LCN Disabled
14    No          Boolean									Telnet Access To Node Disabled
15    No          Boolean									Insecure Access(Telnet / Ftp)  To Node Disabl

Display the current node parameters on this Cisco MGX 8850 switch with a PXM45.

M8850_SF.7.PXM.a > dspndparms
M8850_SF	System Rev: 05.03   Feb. 13, 2007 14:59:19 PST
MGX8850	Node Alarm: MAJOR
NODE CONFIGURATION OPTIONS
Opt#  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 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 Decimal									Obsolete. Use dsprcons for Gang Card Status
13    0           8bit Decimal									Card Switchover on Backcard 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

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.

MGX Release 5.5.10 Limitations, Restrictions, and Notes

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

Upgrade Limitation

None.

BERT Limitation

If 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 Chassis Bandwidth Limitations

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

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 Limitations

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

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.

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.

PXM45 and PXM1E System Limitations

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

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 Limitations

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

For GR253:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS (with MCC):

Receive k2 chanfield—Null Channel

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

For ITU (or AnnexA):

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

For AnnexB:

Receive k2 chanfield—Null Channel

Receive k2 modefield—Undefined

After adding remote APS:

Receive k2 chanfield—Working Section 1 or 2

Receive k2 modefield—Undefined

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.

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.

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.

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

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

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 Limitations

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

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.

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.

Fault Isolation and Trace Limitations

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

CLI Access Level Notes

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

The 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


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 Restrictions

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

This section defines the supported upgrade paths and the associated installation and upgrade procedures.

Supported Upgrade Paths

Table 14 lists the supported upgrade paths.

Table 14 Supported Upgrade Paths

Desired Software
Supported Release

Release 5.5.10

5.4.30, 5.5.00

Release 5.3.00 or 5.3.10

5.1.20 and later

Release 5.2.00 or 5.2.10

4.0.17 and later

Release 5.1.00 or 5.1.20

4.0.17 and later


For information on the following installation and upgrade procedures, refer to the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10.

Upgrade Information

The upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10 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

Upgrading AXSM-XG Cards

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

Table 15 AXSM Card Compatible Software Releases

Card
Software Release When First Supported

AXSM-1-9953-XG

Release 4.0.00

AXSM-4-2488-XG

Release 4.0.00

AXSM-16-155-XG

Release 5.0.00

AXSM-8-622-XG

Release 5.2.00



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

Upgrading the VISM-PR Image

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

The upgrade appendix in the Cisco MGX 8800/8900 Series Software Configuration Guide Release 5.5.10 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.

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

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

Table 16 shows the open Caveats in Release 5.5.10:

Table 16 Open Caveats in Release 5.5.10 

Caveat ID
Description

CSCsz23658

Headline: IMA group goes down when vfb/restart/switching is done on an MPSM16T1E1 card.

Symptom: IMA group goes down when version fallback is disabled on MPSM16T1E1.

Workaround: Always keep the version fallback enabled on the card. Even if you do not require a version fall back to happen, still keep the version fall back parameter enabled. By default, this parameter is enabled at group level.

Hardware: MPSM16T1E1.


Resolved Caveats

This section contains the resolved caveats in the following releases:

Release 5.5.10

Release 5.5.00

Release 5.4.00

Release 5.3.20

Release 5.3.10

Release 5.3.00

Release 5.2.10

Release 5.2.00

Release 5.1.20

Release 5.1.00

Release 5.0.20

Release 5.0.10

Release 5.0.00

Release 5.5.10

Table 18 shows the resolved caveats in Release 5.5.10.

Table 17 Resolved Caveats in Release 5.5.10 

Caveat ID
Description

CSCsz81705

Login banner is not displayed after switchcc in PXM45C redundancy.

CSCsz79333

FTP to node hangs when the path of the login banner is 80 characters long.

CSCsz77179

In dpscdsct command, the -units option with value cellbyte is not working.

CSCsz71612

dsperrhist command displays wrong reason for vxworks memory getting exhausted.

CSCsz67310

ILMI is configurable for VPI 4095 for UNI port on AXSM-XG card.

CSCsz67207

Wrong counters on inducing multiple errors to fail diag test.

CSCsz45431

TRL for IMA group observed as 0.0 on MCC-16E1 back card.

CSCsz60350

dspmpbundlecnt command displays junk value for "Receive Discard Packets"

CSCsz66790

SNMP community of 32 characters is not reflecting in RPM.

CSCsz61986

Configured resource monitoring thresholds may be inaccurate.

CSCsx66708

Connections are not coming up after multiple reset of stand alone PXM.

CSCsz57674

AXSM-XG: link failure due to loss of ILMI messaging.

CSCsz58373

Size of the alarm file for NBSMs on PXM is one byte more than it on CWM with FTP.

CSCsz55265

Error induced with Ondiag disabled comes in effect after Ondiag enabled.

CSCsz34772

Resource monitoring threshold configuration is broken for System Memory.

CSCsz32642

The output of dspcds and dspred do not match for 1:N redundant RPM-XF and SMs.

CSCsz13512

No event get logged for FTP banner size greater than 1K.

CSCsz25588

Missing Quit Statement in the Online Diag Failure Check using shellcon.

CSCsz23357

Online Diag Failure Check using shellcon.

CSCsy92803

Operationally down bundle not getting operationally up after the switchover of MPSMT3E3/T1E1.

CSCsz11684

Last character of ftp banner login getting truncated.

CSCsz09731

PXM45 CPU utilization is high due to pnccb task; MPSM NAK reason code change needed.

CSCsz15266

Resource monitoring on MPSM-T3 is always in MED state for system memory.

CSCsz11448

dspfdrs command shows wrong output for remote port.

CSCsy92829

dspchancnt command displays junk value for Rcv Frames.

CSCsy95071

dspsct and dspportsct commands are not working properly for AXSM-XG.

CSCsy23038

Active line got switched on when Lockout at Local end in APS annexB.

CSCsy42789

MPSM-T3E3-155ppp does not reset when Far end is already down.

CSCsy43014

Upgrade of MPSM-T3E3-155(ASAP) to MR cause IMA NNI port down.

CSCsy73775

dnmpbundles on one node, continuously resets the card on other node.

CSCsx77697

Group running secs not getting reset to 0 after performing restartimagrp.

CSCsy17197

Wrong switch and switch request is happening for APS annexB.

CSCsy23054

mpBundleConfigInfoShow <BundleNo> command displays non-existing bundle.

CSCsy35074

AXSM-XG ILMI lost connectivity.

CSCsy26071

For error APOX_WINP1_EGR_PARITY_ERR, dsperrhist command on PXM displays APOX Win.

CSCsy47690

MPSM-16T1E1-ppp card gets reset by Admin down of mpbundle.

CSCsy54353

Wrong value set for reset flag on up/dnmpbundle.

CSCsy33846

Optional parameter as per the syntax is not optional in cnfcdresetppp command.

CSCsy06422

Upgraded side MPSM-T3E3-155 card gets RESET by Admin down of mpbundle.

CSCsy16631

Introducing IMA84_HMM_HCS_ER introduces IMA84_HMM_SBIEX_UND_ERR also.

CSCsw33724

MPSM PPP event logged when cell bus capacity exceeds OC3.

CSCsx49663

Upgrade of mpsm155ppp to MR image boot both cards.

CSCsx78247

Wrong information is displayed after switching the lines on PXM1E-4-155.

CSCsy23069

Syntax for switchapsln is not correct for MPSM-T3E3-155 for APS.

CSCsx53080

Counters are not accurate for the dspchancnt output.

CSCsx96046

Size of the file observed on CWM is always one byte more than it observed on PXM.

CSCsx96561

Wrong log message displayed for stats file in dsplog output on MGX node.

CSCsx80132

AXSM-XG: SCT values shifted.

CSCsw87633

Banner Login: Unable to do FTP.

CSCsw80912

The value of the expected Rxid changes to -1 on changing the differential delay /vfb parameter.

CSCsx20868

MPSM resets due to 'Task Monitor Fatal'.

CSCsx19607

cnfvctrefresh command does not handle the "reboot" parameter properly.

CSCsx11949

Wrong information is displayed after switching the lines on MPSM card.

CSCsw87987

PNNI trunk flapping caused multiple PVCs to go down.

CSCsw85036

MPSM PPP reset timer is not working properly.

CSCsv90150

MPSM threshold on IMA Accumulation Delay is required.

CSCsw76770

Extra characters while doing telnet and ftp.

CSCsw88248

Offline diag issue with AXSM-4-622/B and y-cables.

CSCsu99551

CLP bits not marked on DE Tagged/Marked frames.

CSCsu74486

Route entry does not get cleared in IPcache during VC failure.

CSCsl56936

cnfpathalm gives error while configuring some parameters.

CSCsw85042

MPSM reset feature is not working for default value.

CSCsv39665

sftp support of config upload for NBSM card.

CSCsw85029

DPC failure reporting of standby RPM-XF to PXM NOK.

CSCsw78786

Help string of cnfvctrefresh command should show autoreboot as optional.

CSCsw35591

MPSM cards are going out of sync in CWM.

CSCsv61747

PPP autoreset feature is triggered on doing Admin down for all ppp links.

CSCsw51381

Wrong information is displayed after switching the lines on near end when Lockout option is selected.

CSCsw45740

All PPP links going down on MPSMppp card.

CSCsw18764

Add CLIs on PXM to enable and disable the data path check on standby RPM-XF.

CSCsw18768

Display a banner before login prompt.

CSCsw37369

showtech command is checking paths on mpsm16t1e1[PPP] card.

CSCsw41969

Optional parameter in cnfsnmp command are not optional.

CSCsw18279

delapsln command not working when the AXSM-B line is in loopback.


Release 5.5.00

Table 18 shows the resolved caveats in Release 5.5.00.

Table 18 Resolved Caveats in Release 5.5.00 

Caveat ID
Description

CSCsm59432

Change node-index option to node number in dsppnni-path command.

CSCsm33833

MGX MPSM CLI and ShellConn Clubbing.

CSCsm26186

MPSM lose traffic on both direction.

CSCsl79205

Incorrect number of FR ports in the output of dspln.

CSCsl67520

dsppart is showing minvci=32 while addcon is taking only vci value >=35.

CSCsl47411

Trace message from AXSM-XG shows improper output.

CSCsl19397

MLPPP bundles discard frames when adding new sites due to buffer lockup.

CSCsl11569

VXSM failed while upgrading to renamed software version file.

CSCsk90200

When a user changes account password, the password of another user changes.

CSCsk84042

switchover should be blocked when the red bus is engaged.

CSCsk76056

Event CTC-4-CTC_INVALID_CD logged for PXM1E during upgrade.

CSCsk74221

PXM45 accepts invalid subnet mask using command ipifconfig.

CSCsk67665

Wrong port value is thrown in the error message of dspchanloop.

CSCsk54350

delprevdbs should be allowed only for reserved card.

CSCsk46256

delpart with invalid arguments throws unwanted arguments along with Err.

CSCsk42664

MultiVC feature checkin.

CSCsk27094

CD(change directory) not successful in SFTP login.

CSCsk19024

delprevdbs and verifydiskdb command are executed simultaneously.

CSCsk11538

delprevdbs command is not accepted on MPSM-T3E3 card.

CSCsk11530

Channel loop back gets deleted on AXSM-XG when port is brought down.

CSCsk11574

Not able to configure TxTrace on a SONET path when the width is 1.

CSCsk09681

delprevdbs command should be blocked while upgrade is in progress.

CSCsj95321

Using released memory in snmpMA. Less IPC buffer size than actual msg.

CSCsj89965

SFTP to PXM45 times out.

CSCsj89434

cnfdalightsetting command throwing error when Tue is given for a day.

CSCsj89442

Summertimezone shows incorrect value after configuring the daylightsetting.

CSCsj86013

Minor alarm with ADM line type between 7200 router and AXSM16T3E3B.

CSCsj77551

OPNEXT OC192 Transponder fails when APS occurs.

CSCsj75926

XG OC12 allows different line types on the same backcard after upgrade.

CSCsj59952

Telnet access to the node disabled after loading 5.4(196.1)A.

CSCsj28768

XBAR values need to be changed in cnfxbarmgmt for 8830 chassis.

CSCsj25032

To checkin SSH v1 disabling feature.

CSCsj13099

Non-PGL node is showing up in the entire network as the upnode.

CSCsj01186

loadrev/runrev/commitrev going through fine without the default syntax.

CSCsi90199

TONEPLANS directory should not be replicated. It causes delay in standby.

CSCsi53538

dspsct 0 displays incorrect values, especially a series of zeroes.

CSCsi54779

Support of challenge messages for SSH.

CSCsi51712

sftp of config files unsupported.

CSCsi45305

dspcds does not indicate missing back-cards from each bay.

CSCsi34086

PXM resets with exception when configuring a group with read view.

CSCir01937

The output of the command dspndparms does not show the last few characters of the last line.

CSCir01797

Wrong syntax is displayed for the command dspv3trapmgr.

CSCek70706

VSI default value is not constant.

CSCir01741

The command clrpathalm gives error message twice.

CSCir01733

The command cnftrapsqlchlist accepts illegal values and update the sqlchlist.

CSCir01707

When a state change occurs for any resource, invalid values are seen in RMON logs.

CSCir01664

The return message of the command dspload needs to be changed.

CSCek69500

Aged trap managers are not deleted from snmpTargetAddrTable.

CSCir01620

snmpOutNoSuchNames values do not get updated on the node. On CWM, it is getting updated.

CSCir01617

The command delpart executed with invalid arguments throws unwanted arguments along with Err.

CSCir01588

cNotifCtrlTableSize is allowed to set, which should be blocked.

CSCir01568

The command cnftrapsqlch accepts threshold and interval values for manual squelch.

CSCir01535

Mismatch between the syntax and description of the command cnfatmln.

CSCir01477

The telnet session hangs while executing the command ipifconfig.

CSCir01479

The command cnfifip has to be made obsolete.

CSCir01347

NCDP is shown as the default clocking in the command cnfncdp.

CSCir01322

MPSM16-FR: The command shows up lines after executing dspchancnt with -r & q.

CSCir01314

Wrong message is displayed while adding redundancy between RPM-PR and RPM-XF.

CSCek65057

snmpwalk on dsx3IntervalTable on MPSM card is looping.

CSCek63518

RPM-XF stays in boot after executing the command restoreallcnf.

CSCek63549

Invalid ATM addresses seen when running dsppnni-inducing-uplink.

CSCek61943

Number of nodes shown in the dsppnni-node-count and dsptech are inconsistent.

CSCek50447

DC voltage reading is 0 if either A1 or B1 is not present.

CSCek48234

VXSM 1:N SHM support - Enhancement.

CSCin98555

SHMA-4-API_SEND_ERR messages were logged while executing resetsys.

CSCin97455

The output of the command dsptech does not stop after pressing Q<CR>.

CSCin95998

The command verifydiskdb status accepts extra junk characters.

CSCeh57638

An error message should be generated when adding partial pref routes.

CSCeg39571

PXM45 should automatically change to daylight saving time.

CSCin84632

The commands dspsvcif,dsppvcif, and dspipifcache should accept only one argument.

CSCdv44368

DLS: Upport displays the addport usage statement.

CSCei41126

AXSMXG-OC12 cnflnalm syntax should show severity range of None.

CSCek18492

AAL2:Dspports heading mis-aligned; unreadable.

CSCek22835

cnfdiag gives incorrect/incomplete error message.

CSCek69501

AXSME cnfln -len option for DS3 (E3 line type) does not work properly.

CSCin94909

Inconsistent alignment for dspnni-intf.

CSCir01161

Warning message thrown with error message while adding ppp link on downed line.

CSCir01575

IMA group goes into startup state when one end conf to different ver.

CSCsj35834

MIBs correction during Neptune bundle release.

CSCsj61931

SNMP and STATS support for card uptime in MGX8850.

CSCsj91601

Discrepancy in the counters of dsplnalmcnt and dsppathalmcnt.

CSCsl26532

Bad PXM clock source from AXSM-XG if wrong cnfclksrc sequence.

CSCsl56936

cnfpathalm gives error while configuring some parameters.

CSCsl72465

Redundant table is not updated correctly and snmpwalk on it fails.

CSCsm32147

Implement equivalent of show-tech for MPSM-PPP.

CSCsm33738

Implement equivalent of show-tech for PXM.

CSCsm84988

AXSME logs OAM_CONN_UPOamErrLog OAM error.

CSCsm87561

BRAM diag failure on PXM45.

CSCso05095

clrportcnt does not clear Rcv Frame Last Unknown DLCI.

CSCso12225

dspload command is not handling partition 0.

CSCso15099

Suspicious "commit failed" log messages are shown in dsplog.

CSCso15287

Suspicious CPU log messages are shown in dsplog.

CSCso16751

Refresh complete log message is not showing in dsplog.

CSCso16959

The lmi operation resumes after resetting the card when the port is down.

CSCso17012

Refreshing is not doing properly, after corrupting with different modes.

CSCso20051

Card resets on inducing VCT Errors when card has one ended connections.

CSCso20056

DAX connections cannot be made on two AXSM cards having same images.

CSCso22396

Error message not displayed when the same path is added again.

CSCso22572

SNMP walk aborts if RxLID in the IMA group is not in order.

CSCso22693

After VCT refresh traffic stops flowing through connections.

CSCso30460

VSICORE: VsiErr:Conn Add to VSI DB Error log message coming in dsplog.

CSCso50080

In dspbundlestatsinfo chancnt are not getting updated with traffic.

CSCso50093

mpBundleConfigInfoShow does not receive -1 as an argument. Card resets.

CSCso50101

dspbundleconfiginfo is not displaying error message when there is no PPP link.

CSCso55165

ICR limit is not specified in cnfabr command.

CSCso57801

dspsnmp shows no Community (ro) after runrev.

CSCso63651

AXSMXG shows inaccurate CONN stats as huge numbers.

CSCso64160

cnfsnmp do not work after giving special characters as an input.

CSCso64226

IMA links failing on adding local/remote loopback.

CSCso66680

Unable to CC to MPSM card after doing IMA commands.

CSCso70794

cnfsnmp community string is not working when database is already corrupt.

CSCso70819

Card reset when cnfsnmp community string is >255 chars.

CSCso75994

Errors logged when online diagnostics are enabled.

CSCso77588

dspimagrpalmcnt NE and FE failure counters out of sync.

CSCso77632

Semaphores handling in MPSM 155.

CSCso77647

Not getting values in several dspchancnt counters.

CSCso87311

Resource monitoring of Winpath Buffers.

CSCso89727

Cannot modify vci and vpi range on a partition if there is SPVP on that port.

CSCsq02520

Wrong initialization of Error thresh time for APOX.

CSCsq02648

HMMErrorDb not getting initialized correctly for APOX.

CSCsq02675

Critical error Trap is not getting generated for APOX.

CSCsq03002

HMM PollHandler not working for APOX_INTERNAL_ERROR_3_STATUS err group.

CSCsq03510

Errors cleared in register not polled when present in monitor list.

CSCsq03523

Error severity not decreasing when error is cleared.

CSCsq03549

Poll handler functionality not working correctly for 10th bit.

CSCsq03581

Critical threshold reach for minor APOX_GEN_INGRESS_ERR injected.

CSCsq03601

Card resets when APOX_WINP1_INGRESS_INTERF minor error injected.

CSCsq03638

Discrepancy value of error counter for APOX_HMM_APPI_INGRESS_PAR.

CSCsq11525

Error counters not getting updated for APOX_GEN_EGRESS_ERR.

CSCsq21932

dspimalnks -grp <grpNum> does not display all links in the grp.

CSCsq25099

Optrte not running on configured ports.

CSCsq31286

Cannot add or change snmp passwords after restorecnf.

CSCsq44721

Problem in integration of CBC and IMA errors in FIT.

CSCsq45009

PPP links go down on full load.

CSCsq45097

Output of shellconn ipcMblkShow is not matching the same in showtech.

CSCsq49436

Cannot ftp MPSM boot fw to PXM1E card.

CSCsq52398

snmp community is not set to default after upgrade in redundant setup.

CSCsq52827

Subheadings displayed in output of command showtech are of different length.

CSCsq57827

To disable and enable the HMM feature through shellconn.

CSCsq63072

Adding NVRAM login facility for CBC HMM.

CSCsq65341

No error message displayed when there exists no bundle and no ppplinks.

CSCsq65533

dsperrhist not working as per FS and problem in q handling in PXM showtech.

CSCsq67925

showtech in MPSM does not show some CLIs when pressed "q".

CSCsq68051

Wrong Set Threshold for APOX_HMM_INTERNAL_FIFO_UNDRRUN_ERR.

CSCsq68715

Discrepancy in value of Register Bit MAsk.

CSCsq70995

Display for command headline for bundles, ppplinks and dspchancnt is not proper.

CSCsq75986

AXSM-B inconsistency between RAM and DISK data.

CSCsq77973

Command dspbundlestatsinfo is accepted with invalid time interval.

CSCsq81252

Trap display string at trap manager is not displayed properly.

CSCsq83578

Not able to gracefully upgrade AXSM image to 5.4(231.1)A from 5.4(28.12)A.

CSCsq88423

MPSM-HMM: No Trap on clearing the Major alarm.

CSCsq93574

HMM is reporting non-fatal error multiple times when injecting APOX_HMM_.

CSCsr00845

showtech gives no output after showing the failed connections.

CSCsr03985

Inst Bound Exception observed when executing command addsnmpgroup.

CSCsr06049

showtech command shows "login:"

CSCsr06584

MPSM-16T3E3-155 card resets while adding ppp links on 5.4(231.2)A ppp.

CSCsr10357

CISCO-MGX8800-TRAPS-MIB does not compile and may contain errors.

CSCsr17603

Increasing Minor Major Critical HMM Threshold values for MPSM155.

CSCsr24707

Unable to upgrade hardware from AXSM-B to AXSM-XG.

CSCsr36648

After cnfcon changes are not reflected in mpBundleConfigInfoShow output.

CSCsr42851

Enhance PXM to handle DPC clear trap sent from RPM-XF.

CSCsr42858

DPC failure for RPM-XF needs to be reported to SHM always.

CSCsr43120

No SII traps seen on MD.

CSCsr45342

Lots of debug message appears for the error when we induce HMM error.

CSCsr45380

dspbertstat counter not incrementing after changing the eir.

CSCsr50574

Enhance PXM to handle RPM online diagnostic report

CSCsr51287

Resetting or clearing Line Card causes PXM to switch.

CSCsr53812

IMA Version Fallback: Display issue.

CSCsr55660

Minor trap should be there for minor alm.

CSCsr67779

On resetting PXM, daylightsaving settings are enabled.

CSCsr70259

SEFS counters do not increment when configured for E1 operation.

CSCsr71022

No traps received upon removal of PXM-UI card.

CSCsr80424

MPSM command prompt suspended for few minutes while ccing to same card.

CSCsr88715

SNMP error reported on MGX instead of SNMP server.

CSCsu01671

Output of spcd slotno is not displaying inserted back card type for both rpm-pr and rpm-xf.

CSCsu01683

SSI-4-STRTOOLONG is logged after resetting MPSM card.

CSCsu24282

SSI-3-EXCEPTION observed and ssh session hung when trying to ssh node.

CSCsu25955

Compilation error in AXIPOPMIBS.

CSCsu33195

dsptrapmgr shows empty table and could not add new trap manager also.

CSCsu35342

Undesired response on MGX when connection is added on AXSM-E card.

CSCsu41511

Addport not accepting rate 50 which should be acceptable.

CSCsu47317

Wrong remote port value in dspfdrs output.

CSCsu47454

showtech command does not display PXM configuration properly on 8830 chassis.

CSCsu49606

PXM-1E will not support showtech command.

CSCsu51673

daylightsaving settings not working.

CSCsu56569

SSI-4-STKCHK error observed while configuring snmp user.

CSCsu59602

While adding dax/SPVC connections on AXSME, connections went to ALARM state.

CSCsu61950

daylightsaving settings get enabled after upgrade.

CSCsu62518

VXSM unable to come up after PXM resetsys.

CSCsu62542

MGX High CPU due to memory block failure on PXM.

CSCsu67314

On upgrade to 5.5, ssh to node fails.


Release 5.4.00

Table 19 shows the resolved caveats in Version .202 of Release 5.4.00.

Table 19 Resolved Caveats in Version .202 of Release 5.4.00 

Caveat ID
Description

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 shows the resolved caveats in Versions .200 and .201 of Release 5.4.00.

Table 20 Resolved Caveat in Versions .200 and .201 of Release 5.4.00 

Caveat ID
Description

CSCek71275

PXM45/C with H2FPGA CAM shows as Version 2 in dspdevrev.


Table 21 shows the resolved caveats in Release 5.4.00.

Table 21 Resolved Caveats in Release 5.4.00 

Caveat ID
Description

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

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


Release 5.3.20

Table 22 shows the resolved caveats in Release 5.3.20.

Table 22 Resolved Caveats in Release 5.3.20 

Caveat ID
Description

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

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

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


Release 5.3.10

Table 23 shows the resolved caveats in Release 5.3.10.

Table 23 Resolved Caveats in Release 5.3.10 

Caveat ID
Description

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

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


Release 5.3.00

Table 24 lists the resolved caveats in Release 5.3.00.

Table 24 Resolved Caveats in Release 5.3.00 

Caveat ID
Description

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

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

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


Release 5.2.10

Table 25 lists the caveats that were resolved in Version .201 of 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


Table 26 lists the resolved caveats in Release 5.2.10.

Table 26 Resolved Caveats in Release 5.2.10 

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

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


Release 5.2.00

Table 27 lists the resolved caveats in Release 5.2.00.

Table 27 Resolved Caveats in Release 5.2.00 

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

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

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


Release 5.1.20

Table 28 lists the resolved caveats in Release 5.1.20.

Table 28 Resolved Caveats in Release 5.1.20 

Caveat ID
Description

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