Cisco MGX 8880 Media Gateways

5.3.00 Release Notes for Cisco MGX 8880 Media Gateway

  • Viewing Options

  • PDF (380.4 KB)
  • Feedback
Release Notes for Cisco MGX 8880 Software Release 5.3.00

Table Of Contents

Release Notes for Cisco MGX 8880 Software Release 5.3.00

Table of Contents


Release 5.3.00 Description

Type of Release

Locating Software Updates

Release 5.3.00 Features and Enhancements

VXSM Enhancements

Security Enhancements

SFTP and SSH Features

Remote IP Management Connection Enhancements

Management Connection Limitations

Configuring an RPM Management Connection

Example Management Configuration

Platform Enhancements

RPM-PR Ethernet Backcard

AXSM-8-622-XG Service Module

Release 5.2.10 Features

Release 5.2.00 Features


System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Supported Hardware

Release 5.3.00 Hardware

MGX 8880 Product IDs and Card Types

Service Class Template Files



Limitations, Restrictions, and Notes for 5.3.00

Upgrading the VISM-PR Image

Higher Level Logical Link Limits

AXSM-32-T1E1-E Notes

AXSM-E Operation, Administration, and Maintenance Cells

Command Line Interface Access Levels

Disk Space Maintenance

Saving Configurations

Using the clrsmcnf Command

AXSM Card Automatic Protection Switching Limitations

Path and Connection Trace Features

Priority Routing Feature

Soft Permanent Virtual Connection Interoperability

Manual Clocking

Enabling Priority Bumping

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 Card

Known MGX 8880 Media Gateway Anomalies

Known Route Processor Module Anomalies


Obtaining Documentation

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


Release Notes for Cisco MGX 8880 Software Release 5.3.00

Part Number OL-8892-01 Revision B0, October 23, 2006

Table of Contents


These release notes contain the following sections:

"Release 5.3.00 Description" section

"Release 5.3.00 Features and Enhancements" section

"Release 5.2.10 Features" section

"Release 5.2.00 Features" section

"System Requirements" section

"Service Class Template Files" section

"Limitations, Restrictions, and Notes for 5.3.00" section

"Known MGX 8880 Media Gateway Anomalies" section

"Known Route Processor Module Anomalies" section

"Documentation" section

"Obtaining Documentation" section

"Documentation Feedback" section

"Cisco Product Security Overview" section

"Obtaining Technical Assistance" section

"Obtaining Additional Publications and Information" section

"Acronyms" section

Release 5.3.00 Description

These release notes describe the system requirements, new features, and limitations that apply to Release 5.3.00 of the Cisco MGX 8880 Media Gateway, and provide Cisco support information.

For information about new VXSM features, refer to the Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.00.

For information about new VISM-PR features, refer to the Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.25.

Type of Release

Release 5.3.00 is a software and hardware release for the MGX 8880 media gateway.

Locating Software Updates

Release 5.3.00 software is located at:

Route processor module (RPM) Cisco IOS software images are located at:

Release 5.3.00 Features and Enhancements

This release includes the following new features for the Cisco MGX 8880 platform:

VXSM Enhancements

Security Enhancements

Remote IP Management Connection Enhancements

Platform Enhancements

RPM-PR Ethernet Backcard

AXSM-8-622-XG Service Module

VXSM Enhancements

For information about VXSM enhancements, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.00.

Security Enhancements

This release introduces the following security enhancements:

PXM45—Secure File Transfer (SFTP)

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

SFTP and SSH Features

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

Telnet, FTP, and SSH on the PXM45 controllers

Telnet and FTP on the 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 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Configuration Guide, Release 5.1

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

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. A new option (16) of the cnfndparm command, along with an existing 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 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)

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 don't 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 an 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 prior releases:



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


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


Step 1 


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 


Verify that the connection is up.

Step 5 


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

Example Management Configuration

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 configures the RPM-XF switch interface, adds a slave connection, and displays the NSAP address.

Router(config)#interface switch1.100 point-to-point
Router(config-subif)#ip address
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#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 configures the atm0 interface of the PXM card, adds a master connection to the RPM-XF, and verifies 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 netmask
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
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

Platform Enhancements

This release adds the following MGX platform enhancements.

DB Server/Client enhancement

The server automatically copies database tables to the new directory for a release.

Software FPGA upgrade on PXM45/C

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

RPM-PR Ethernet Backcard

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



Green—The back card is active.

Off—The back card is not active.


Port 0 status LED

Green—Data present (flashing).

Orange—The link is up.


Port 0 speed LED

Green—1000 Mbps.

Orange—10 Mbps or 100 Mbps.


AXSM-8-622-XG Service Module

The AXSM-8-622-XG Service Module is supported on the MGX 8880 in Release 5.3.00.

The Cisco® 8-Port OC-12/STM-4 Channelized/Unchannelized ATM Switch Service Module is a line card for use in the Cisco MGX® 8800 Media Gateway in combination with the Cisco PXM-45 Processor Switch Module . This ATM switch service module has eight physical 622 Mbps interfaces that can be used to deliver high-density OC-12 or STM-4 trunking/User-Network Interface (UNI) or aggregation of sub-OC-12 traffic through port channelization.

Up to 12 Cisco 8-port OC-12/STM-4 ATM switch service modules can reside in the MGX 8880 to provide support for up to 96 OC-12c/STM-4 interfaces for service providers that require both high bandwidth and high network availability.

The AXSM-8-622-XG service module is used in conjunction with the SFP-4-622 back card. This card is a 4-port SFP back card for OC-12/STM-4 interfaces.

Key Features

Individual port channelization down to DS-3 and OC-3c/STM-1

Per-virtual path and per-virtual circuit traffic shaping and available-bit-rate (ABR) with virtual source and virtual destination

APS (1:1 and 1+1) port redundancy, plus APS 1+1 card redundancy

Up to four million cell buffers

Up to 16 classes of service (CoSs) that can be used to support IP or ATM services

Support for standards-based Private Network-Network Interface (PNNI), switched virtual circuit (SVC) and switched virtual path (SVP), soft permanent virtual connection (SPVC) and soft permanent virtual path (SPVP), and Multiprotocol Label Switching (MPLS) services

Release 5.2.10 Features

Maintenance Release 5.2.10 does not introduce new Cisco MGX 8880 features or enhancements.

Release 5.2.00 Features

Release 5.2.00 introduced the following hardware:

MGX-VXSM-T3 front card

VXSM-BC-3T3 back card


Cisco MGX 8880 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.

System Requirements

This section describes software compatible with Release 5.3.00, and lists the supported hardware.

Software/Firmware Compatibility Matrix

Table 1 lists Cisco WAN or Cisco IOS products that are compatible with Release 5.3.00.

Table 1 Release 5.3.00 Compatibility Matrix 

Switch or Component
Compatible Software Release

MGX 8880 (PXM45/C)

MGX 5.3.00


VXSM 5.3.00


VISM 3.3.25



(supported only with VISM-PR cards)



AXSM 5.3.00

MGX and RPM Software Version Compatibility Matrix

Table 2 lists the software that is compatible for use in a switch running Release 5.3.00 software.

Table 2 MGX and RPM Software Version Compatibility Matrix 

Board Pair
Boot Software
Runtime Software









(CALEA image)


(non-CALEA image)





(CALEA image)

vism-8t1e1- (non-CALEA image)


N/A (obtains from PXM)

N/A (obtains from PXM)


(supported only with VISM-PR cards)






(Crypto image)


(non-Crypto image)













SNMP MIB Release

The SNMP MIB release for Release 5.3.00 is mgx8XXXrel5300mib.tar.

Note SNMP user guides are replaced by the online MIB tool at URL

Supported Hardware

This section lists the MGX 8880 product IDs, 800 part numbers, and revision levels.

Release 5.3.00 Hardware

Release 5.3.00 introduces the following RPM-PR backcard:

MGX-RJ45-5-ETH—Five-port Ethernet backcard

MGX 8880 Product IDs and Card Types

Table 3 lists product IDs, minimum 800 part numbers, and the minimum revision levels for the MGX 8880.

Table 3 MGX Chassis, Card, and Automatic Protection Switching Configurations 

Front Card Type
Min. 800 Part Number and Revision
Back Card Types
Min. 800 Part Number and Revision

PXM45/C (processor switch module)




































































(was MGX-GE-SX1)


(was MGX-GE-ZX1)



(supported only with VISM-PR cards)






























































Service Class Template Files

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


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


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

Limitations, Restrictions, and Notes for 5.3.00

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

Due to granularity limitations in the AXSM-E hardware, cell traffic does not reach the configured peak cell rate (PCR) rate when weighted fair queuing (WFQ) is enabled. You must configure connections that have WFQ enabled with a PCR of 101 percent of the actual required rate. Available bit rate (ABR) has the same Qbin priority as the unspecified bit rate (UBR) in the SCT tables. In this case, ABR and UBR share excess bandwidth if WFQ is enabled.

The VXSM cards, when installed for the first time or after clearing the slot configuration, create a default configuration. The creation of a default configuration involves writing large amount of data to the hard disk in the node.

When multiple VXSM cards are installed simultaneously or the configuration of multiple VXSM slots are cleared simultaneously, one or more VXSM cards could fail to be installed. This potential failure results in following recommendations (refer to CSCed12646):

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

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

Upgrading the VISM-PR Image

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

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

Higher Level Logical Link Limits

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

If there are n logical links, the calculation involves finding n*n bypasses.

If the number of logical links n is large, a lot of processing time is used to calculate the bypasses. Limit the number of logical links per level to 30. To control the number, configure the appropriate number of aggregation tokens for the outside links for that peer group.

AXSM-32-T1E1-E Notes

The following notes apply:

Inverse multiplexing over ATM (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: Alarm Indication Signal (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 switched virtual circuit (SVC) calls per second are guaranteed.

Facilities Data Link (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.

Hidden Markov Method (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.

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

Independent Transmit Clock (ITC) clocking mode on IMA is not supported.

1-way transmission delay of more than 500 milliseconds (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 using the clrimadelay command, 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 Virtual Circuit (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.

Bit error rate testing (BERT) is only supported on 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 CSCdy08500.

Private Network-to-Network Interface (PNNI) requires:

Sustainable cell rate (SCR) = 453 cells per second and

Peak cell rate (PCR) = 969 cells per second for the control connection

Service-Specific Connection-Oriented Protocol (SSCOP) requires an SCR = 126 cells per second and PCR = 2000 cells per second.

AXSM-E Operation, Administration, and Maintenance Cells

The following notes apply to AXSM-E operation, administration, and maintenance (OAM) cells:

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

If the connection is not in the loopback mode and is operating in the normal mode, then the AXSM-E card can receive up to 1,500 segment OAM loopback cells per second. Any excessive segment OAM loopback cells are dropped. This limitation applies for all the connections on a card.

For example, if only one connection exists, that connection can receive 1,500 segment OAM loopback cells per second. If 2,000 connections exist on an AXSM-E card, and one segment OAM loopback cell per second is being channeled through on each connection, then there can only be up to 1,500 connections to receive loopback cells at any given second. The additional 500 connections are not received for that second.

The limitation is 1,500 segment OAM loopback cells per card and not per connection. The 1,500 cps assumes an even flow rate.

Command Line Interface Access Levels

The following notes pertain to configuring command access levels:

Not all command line interface (CLI) commands are changeable, and a command cannot be changed to CISCO_GP group access level.

Only the switch software is allowed to generate the binary file. This binary file has an authentication signature which has to be validated before the binary 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 execute a cnfcli accesslevel install command on that service module.

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

If replication to standby failed, the installation process failed.

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

Disk Space Maintenance

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

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

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

Step 1 Change to the directory that needs grooming.

CLI cc <directory_name> 

Step 2 List the directory to identify old files that can be removed and available disk space.

CLI ll 

Step 3 Remove any old files (you may also use wild cards in the filename).

CLI rm <complete_filename> 

Step 4 List the directory to see if the file was removed and disk space is available.

CLI ll 

Saving Configurations

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

Using the clrsmcnf Command

These notes pertain to the clrsmcnf command:

We do not recommend executing clrsmcnf on more than one card at a time

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

For the clear service module configuration feature, using the clrsmcnf command might result in discrepancy in the PNNI configuration. For example, some connections might be in the mismatch state.

If the clrsmcnf command is given with the <all> option to clear the software version for the slot as well, then the card enters the boot/empty state after the operation is complete.

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

While using the clrsmcnf command, the card in the specified slot is not usable until the operation is successfully completed.

AXSM Card Automatic Protection Switching Limitations

These notes pertain to the Automatic Protection Switching (APS) feature:

For AXSM APS, the back card of the active card must be present for APS to function.

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

If you remove the upper back card of the active front AXSM, it triggers switching active card. The APS is OK. However, if the lower back card of the current active AXSM is removed at this time, it does not trigger switching the active card because the standby card is missing one of the back cards. The lower backcard APS does not work because the back card of the active front card is missing.

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

Path and Connection Trace Features

These notes pertain to the path and connection trace features:

Path trace is not supported on the control port.

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

Path and connection trace support point to point connections.

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

Priority Routing Feature

These notes pertain to the priority routing feature:

Prioritized reroute of soft permanent virtual connection (SPVCs) is not guaranteed if the SPVCs originate on a signaling port. SPVCs might get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports.

RPM does not support configuration of routing priority. All RPM mastered SPVCs are assigned a routing priority of 8 by the PXM.

Changing the routing priority for DAX connections does not change the priority of the associated SVCs. The SPVCs are not derouted and rerouted if just the endpoint parameters are changed, and routing priority is an endpoint parameter. Also, because DAX connections are never derouted even if the user-network interface (UNI) port stops responding and the rrtcon command is not supported for DAX connections, the routing priority change is never reflected. The only way for the routing priority change to be reflected is to execute the dncon and upcon commands. Because DAX connections are never derouted, the effect of this limitation is voided.

Priority routing operates in a best effort manner for the following reasons:

Two in-order releases can still arrive out of order at the master node if they take two different paths.

Under congestion scenarios releases can be expected to be transmitted out-of-order. This is because releases of other calls must not be held up if you are not able to send releases on one of the interfaces because it is congested. The calls that were not released could be higher priority calls.

Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can happen if you have repeatedly failed to route higher priority SPVCs. To prevent starvation of lower priority SPVCs, the software starts to route lower priority SPVCs. The software eventually addresses the higher priority SPVCs later.

Soft Permanent Virtual Connection Interoperability

These notes pertain to SPVC interoperability:

Network-to-Network Interface (NNI) SPVC Addendum Version 1.0 is not supported.

CC (Continuity Check) is not available at the slave end of a single-end SPVC.

Reporting AIS detection to Cisco Wide Area Network Manager (CWM) is not available at the slave end of a single-end SPVC.

The slave end of a single-end SPVC is not visible to CWM.

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

Single-end provisioning is not supported for DAX connections.

SPVC statistics are not available for the slave endpoint of a single-end SPVC because this endpoint is nonpersistent.

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

Override of SVC connections on a virtual path identifier (VPI) due to an incoming SPVP request for that VPI is not supported. The following override options are supported only:




Manual Clocking

When resetcd is invoked, the primary and secondary (if configured) clock sources are recommitted. However, the clock to which the node is latched is not requalified. Only the backup clock is qualified if present. Recommitted means that the primary and secondary are requalified, and the node temporarily latches onto the internal oscillator. After the clock is requalified, the node locks onto the primary clock source once again.

Enabling Priority Bumping

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

Other Limitations and Restrictions

Other limitations and restrictions are as follows:

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

If command clrchancnt is executed while a dspchancnt command is currently active, the displayed data is incorrect. To display correct data, restart the dspchancnt after the previous one is complete.

The clrsmcnf command does not work:

For redundant service modules.

If an upgrade is in progress.

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

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

Clearing the Configuration on Redundant PXM45 Card

These notes apply to redundant cards.

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

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

Known MGX 8880 Media Gateway Anomalies

For information about anomalies in MGX Release 5.3.00 on other platforms, refer to the Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.3.00.

For information about anomalies with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.00.

For information about anomalies with the VISM card, refer to Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.25.

Known Route Processor Module Anomalies

For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.4(6)T1 for PXM45-based Switches, Release 5.3.00.

For information about anomalies with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.4(6)T1 for MGX Releases 1.3.14 and 5.3.00.


A Guide to Cisco Multiservice Switch Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, broadband and packet exchange (BPX), service expansion shelf (SES), and CWM documentation online.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

You can access the most current Cisco documentation at this URL:

You can access the Cisco website at this URL:

You can access international Cisco websites at this URL:

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

Ordering Documentation

Registered users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

Nonregistered users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only —

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies —

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532

Tip Use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.

Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

Access to all tools on the Cisco Technical Support & Documentation website requires a user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

or view the digital edition at this URL:

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

World-class networking training is available from Cisco. You can view current offerings at this URL:


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


Table 4 Acronyms Used in These Release Notes 



Alarm Indication Signal


ATM Switch Service Module. In these release notes, AXSM-A refers to the original AXSM card (A did not appear on the card), and AXSM/B refers to the newer AXSM/B card (B does appear on the card).


Available bit rate


Automatic Protection Switching


Bit error rate testing


broadband and packet exchange


Communications Assistance for Law Enforcement Act/ Lawful Intercept


Command Line Interface


Class of service


Cisco Wide Area Network Manager


Facilities Data Link


Gigabit Ethernet


Hidden Markov Method


Inverse Multiplexing over ATM


Independent Transmit Clock mode


Link Fragmentation Interleaving


Loss of Signal


Label switch controller


Multilink Frame Relay


Multilink PPP


multiple peer group


Multiprotocol service module


Multicast Tunnel Interface


Network-to-Network Interface


Operation, Administration, and Maintenance




Peak cell rate


Provider Edge


Product Enhancement Request


Private Network-to-Network Interface


Packet over SONET


Point-to-Point Protocol


Processor Switch Module


Route Processor Module


sustainable cell rate


service class template


Service-Specific Connection-Oriented Protocol


Service Expansion Shelf


Service Module


Synchronous optical network


Soft permanent virtual connection


Service resource module


Switched virtual circuit


unspecified bit rate


user-network interface


Virtual Circuit


Voice interworking service module


Virtual path identifier


Virtual private network


VPN routing/forwarding


Voice switch service module


weighted fair queuing


Express forwarding