Table Of Contents
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.3.10
Non-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
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
Fractional T1/E1 Links for ATM Services
Fractional T1/E1 Configuration
Fractional T1/E1 Configuration Limitations
Remote IP Management Connection Enhancements
Management Connection Limitations
Configuring an RPM Management Connection
Management Configuration—Example
Routing Enhancement for AXSM-XG Cards
Graceful Upgrades to AXSM-XG Cards
Multilink PPP on the MPSM-T3E3-155 Card
PXM45/C Support in the MGX 8830/B Chassis
Compression and Multiplexing Support for RPM-PR Cards
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
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
Product IDs, Card Types, and APS Connectors
Service Class Template File Information
MGX Release 5.3.10 Limitations, Restrictions, and Notes
MGX Voltage Measurement Limitation
MGX Chassis Bandwidth Limitations
PXM1E Reserved Virtual Channel Identifiers
PXM1E Point to Multipoint Support
PXM45 and PXM1E System Limitations
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
Clearing Card Configuration Notes
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
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card
Known Anomalies in Release 5.3.10
Resolved Anomalies in Release 5.3.10
Status Changed Anomalies in Release 5.3.10
Resolved Anomalies in Previous Releases
Resolved Anomalies in Release 5.3.00
Resolved Anomalies in Release 5.2.10
Resolved Anomalies in Release 5.2.00
Resolved Anomalies in Release 5.1.20
Resolved Anomalies in Release 5.1
Resolved Anomalies in Release 5.0.20
Resolved Anomalies in Release 5.0.10
Resolved Anomalies in Release 5.0.00
Known Route Processor Module or MPLS Anomalies
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.3.10
Part Number OL-11147-01 Revision C1, May 2008
Table of Contents
Overview
These release notes contain the following sections:
•
Service Class Template File Information
•
MGX Release 5.3.10 Limitations, Restrictions, and Notes
•
Resolved Anomalies in Previous Releases
•
Cisco Product Security Overview
•
Product Alerts and Field Notices
•
Obtaining Technical Assistance
•
Obtaining Additional Publications and Information
About Release 5.3.10
Version .201 of Release 5.3.10 is a patch release that does not introduce new features. The resolved anomalies for Version .201 are listed in Table 16.
These release notes describe the system requirements, new features, and limitations that apply to Release 5.3.10. These notes also contain Cisco support information. Release 5.3.10 is a software and hardware release for the following Cisco multiservice switches (MGXs):
•
MGX 8830 (Processor Switch Module, or PXM1E)
•
MGX8830/B (PXM1E and PXM45)
•
MGX 8850 (PXM1E and PXM45)
•
MGX 8850/B (PXM1E and PXM45)
•
MGX 8950 (PXM45)
Locating Software Updates
Release 5.3.10 software is located at:
http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml
Route Processor Module (RPM) Cisco IOS software images are located at:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
Features in Release 5.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 an 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
•
Remote IP Management Connection Enhancements
•
Routing Enhancement for AXSM-XG Cards
Multilink Point-to-Point Protocol Enhancements for CDMA2000 and EV-DO
CDMA2000 applications can use the 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 1 compares the features of Release 5.2 to Release 5.3:
MLPPP Configuration
The MLPPP features in Release 5.3 do not change the MLPPP configuration procedures and command syntax; only the valid ranges for links and bundles change (see Table 1). 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 Configuration Guide, Release 5.2
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 transactAddPppLinkEM Event: Id:448e, Line#825:64kbps ppp link 23 cannot be added to the bundlehaving 56kbps linksTo 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 transactAddPppLinkEM Event: Id:448e, Line#860:64Kbps PPP link "LinkNum" not supported on lineswith AMI line codingTo 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 88301cps 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 Configuration Guide, Release 5.2
Fractional T1/E1 Configuration Limitations
Fractional T1/E1 configurations have the following configuration restrictions:
•
Virtual ports on fractional T1/E1 lines are not supported.
•
Connecting fractional T1/E1 interfaces with V.35 and X.21 is not supported.
•
Partition bandwidths cannot be less than 100 percent of the port rate.
•
Cicso Wide Area Network Manager (CWM) inband configuration upload over a low bandwidth link is not supported. Without sufficient bandwidth, CWM may time out and never synchronize.
Fractional T1/E1 configurations have the following functional limitations:
•
Each physical interface can be configured with only one NxDS0 port.
•
A physical interface can be configured with one NxDS0 port for ATM service, or one NxDS0 port for Frame Relay service, but not both.
•
The number of timeslots of an existing NxDS0 port cannot be changed using the cnfport command. Therefore, you cannot dynamically add additional DS0 timeslots to increase bandwidth.
•
Network clock distribution protocol (NCDP) cannot distinguish the type of line a NNI trunk is using. This information is transparent to NCDP. Therefore, selecting the NXDS0 port as a NCDP clock source is not blocked by default. Use the cnfncdpport command on the PXM card to block the NxDS0 port from being used as a NCDP clock source. By default for a NNI trunk, this is not blocked.
•
Integrated local management interface (ILMI) using about 5 percent of the port bandwidth. This limits the number of connections that can be supported on either side for ILMI autoconfiguration or address registration to succeed.
•
For PNNI and service specific connection-oriented protocol (SSCOP), call setup and mutual status exchange for each connection require about 20 cells per second in bandwidth. Connection reroute or connection setup on a NxDS0 trunk with insufficient bandwidth for the number of connections supported can fail if SSCOP times out.
•
With PNNI signaling enabled, you must configure the minimum bandwidth that PNNI requires. Otherwise, PNNI trunks may not come up. Use the dsppnctlvc command to display the required PNNI bandwidth.
•
Extended permanent virtual connections (XPVC) using NxDS0 user-to-network interface (UNI) are not supported.
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 Configuration Guide, Release 5.2
–
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.
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 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 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 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.
The following quick start procedure summarizes the PXM configuration procedure.
Management Configuration—Example
This example shows how to configure a management connection between an RPM-XF on one switch and the PXM on another switch. In this example, the RPM-XF switch partition and the PXM ATM0 interface are already available.
The following example shows how to configure the RPM-XF switch interface, add a slave connection, and display the NSAP address.
Router(config)#interface switch1.100 point-to-pointRouter(config-subif)#ip address 10.10.10.200 255.255.255.0Router(config-subif)#pvc 0/100Router(config-if-atm-vc)#ubr 1544Router(config-if-atm-vc)#switch connection vcc 0 100 master remoteRouter(config-if-swconn)#endRouter#show switch connection vcc 0 100----------------------------------------------------------Alarm state : No alarmLocal Sub-Interface : 100Local VPI : 0Local VCI : 100Remote NSAP address : defaultLocal NSAP address : 47.0091810001040000ABCD7777.000001011802.00Remote VPI : 0Remote VCI : 0The following example shows how to configure the ATM0 interface of the PXM card, add a master connection to the RPM-XF, and verify that the connection is state is up. The NSAP address and VPI/VCI entered are the values previously displayed at the RPM-XF.
LA.8.PXM.a > ipifconfig atm0 10.10.10.144 netmask 255.255.255.0LA.8.PXM.a > svcifconfig atm0 remote 47.0091810001040000ABCD7777.000001011802.00 pvc 0.100LA.8.PXM.a > dspsvcifM8850_LA System Rev: 05.02 Apr. 25, 2006 16:36:38 PSTMGX8850 Node Alarm: NONEIP CONNECTIVITY SVC CACHE--------------------------------------------------------------------atm (unit number 0):Remote AESA: 47.0091.8100.0104.0000.abcd.7777.0000.0101.1802.00SPVC VPI.VCI: 0.100 (PCR=3642 cps)Flags: (0x6) ATMARP,LLCENCAPState: (0x1) UPRxLCN: 1505 TxLCN: 1505LCNindex: 766 LCNcallid: 0x80000001Input Frames: 1 Output Frames: 1Input Errors: 0 Output Errors: 0Input ArpReq: 0 Output ArpReq: 0Input ArpRply: 0 Output ArpRply: 0Input InArpReq: 0 Output InArpReq: 0Input InArpRply: 1 Output InArpRply: 0Routing 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 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 8.
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.
MGX 8830/B Enhancements
The MGX 8830/B is a 7-double-height horizontal slot chassis, where slots 1 and 2 are reserved for the PXM. The 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
![]()
Table 2 lists the maximum cable length for each of the supported speeds on the MGX-RJ45-5-ETH card.
Table 2 MGX-RJ45-5-ETH Card Supported Speeds and Maximum Cable Lengths
Configuration Interface Speed Maximum Cable Length10 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:
•
Graceful Upgrades to AXSM-XG Cards
•
Multilink PPP on the MPSM-T3E3-155 Card
•
PXM45/C Support in the MGX 8830/B Chassis
•
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 MGX 8850, MGX 8830, and MGX 8950 chassis
•
Maximum bandwidth is 2.4 Gbps when installed in a MGX 8850 or MGX 8830 chassis
•
Maximum bandwidth is full card bandwidth when installed in 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 an 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 an 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 Configuration Guide, Release 5.2.
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 MGX 8830/B Chassis
A PXM45/C controller in an MGX8830/B chassis provides support for a selection of narrowband and broadband interfaces in an 8-slot chassis. The PXM45/C controller's 45Gbps 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 an MGX8850/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 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-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
•
Private Network Node Interface Current Route Feature
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:
•
MGX 8850 and MGX 8850/B switches
•
MGX 8830 and 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 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 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 MGX 8850 (PXM45) aggregates traffic from several BTS site routers (MWR) and transfers that traffic to an IP network. The aggregation point in the 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 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 3 lists PNNI product enhancement requests incorporated in this release.
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 4 lists Cisco WAN or Cisco IOS software products that are compatible with Release 5.3.10.
MGX and RPM Software Version Compatibility Matrix
Table 5 lists the software that is compatible for use in a switch running Release 5.3.10 software.
SNMP MIB Release
The SNMP MIB file for Release 5.3.10 is mgx8850rel5310mib.tar.
![]()
Note
SNMP user guides are replaced by the online MIB tool at:
http://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp
Supported Hardware
This section lists:
•
MGX 8850 (PXM45) Product IDs, 800 part numbers, and revision levels
•
MGX 8850 (PXM1E) Product IDs, 800 part numbers, and revision levels
•
MGX 8830 Product IDs, 800 part numbers, and revision levels
•
MGX 8950 Product IDs, 800 part numbers, and revision levels
Hardware in Release 5.3.10
Release 5.3.10 introduces 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 6 MGX Chassis, Card, and APS Configurations Part 1
Front Card Type Minimum 800 Part Number and Revision Back Card Types APSCon Minimum 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830 and 8830/BPXM1E MGX 8950PXM45PXM45/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-
SFPYes
10-1283-01-A0
SMFLR-1-155-
SFPYes
10-1280-01-A0
MMF-1-155-
SFPYes
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 7 MGX Chassis, Card, and APS Configurations Part 2
Front Card Type Minimum 800 Part Number and Revision Back Card Types APSCon Minimum 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830 and 8830/BPXM1E MGX 8950PXM45XM-60
800-04706-06-A0
—
—
—
—
—
—
—
x
MGX-APS-CON
800-05307-01-A0
—
—
—
x
—
—
—
—
MGX-8850-APS-
CON800-20640-01-A0
—
—
—
x
x
—
—
—
MGX-8830-APS-
CON800-05308-02
—
—
—
—
—
x
x
—
MGX-8950-APS-
CON800-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 MGX 8830/B chassis must use the RED-16-T1E1 back card for 1:N redundancy.
Table 8 MGX Chassis, Card, and APS Configurations Part 3
Front Card Type Minimum 800 Part Number and Revision Back Card Types APSCon Minimum. 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830 and 8830/BPXM1E MGX 8950PXM45AXSM-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-
2488Yes
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/BYes
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-
SFP10-1283-01-A0
SMFLR-1-155-
SFP10-1280-01-A0
MMF-1-155-
SFP10-1308-01-A0
MCC-8-155
Yes
800-22117-02-A0
AXSM-16-155
800-05776-06-A0
MMF-8-155-MT
Yes
800-04819-01-A1
x
—
—
—
—
SMFIR-8-155-
LCYes
800-05342-01-A0
SMFLR-8-155-
LCYes
800-05343-01-C0
AXSM-16-155/B
800-07909-05-A0
MMF-8-155-
MT/BYes
800-01720-02-A0
x
—
—
—
x
SMFIR-8-155-
LC/BYes
800-07864-02-B0
SMFLR-8-155-
LC/BYes
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-CON800-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 9 MGX Chassis, Card, and APS Configurations Part 4
Front Card Type Minimum 800 Part Number and Revision Back Card Types APSCon Minimum 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830 and 8830/BPXM1E MGX 8950PXM45MGX-SRME
800-14224-02-A0
MGX-SMFIR-1-155
Yes 1
800-14460-02-A0
x
x
—
x
—
MGX-STM1-
EL-1Yes 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/B800-04809-01-A0
AX-RJ48-8T1
—
800-02286-01-A0
—
x
—
x
—
AX-R-RJ48-8T1
—
800-02288-01-A0
MGX-AUSM-
8E1/B800-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-
A0VXSM-BC-3T3
—
800-3095-03
x
—
—
—
—
MGX-VXSM-T1E1
800-24073-02-A0
VXSM-BC-24T1E1
800-23088-03-A0
x
—
—
—
—
MGX-VISM-PR-
8T1800-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-
8E1800-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 10 MGX Chassis, Card, and APS Configurations Part 5
Front Card Type Minimum 800 Part Number and Revision Back Card Types APSCon Minimum 800 Part Number and Revision MGX 8850 and 8850/BPXM45 MGX 8850 and 8850/BPXM1E MGX 8830/BPXM45 MGX 8830 and 8830/BPXM1E MGX 8950PXM45AX-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-
2T3E3800-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/B800-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-
256800-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-
512800-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 MGX 8850/B or MGX 8830/B chassis in slots where RCONs are installed. Use MGX-XF-UI/B instead.
The following notes apply to Table 6 through Table 10:
•
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.
•
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 11 summarizes the correct APS connector for each MGX chassis and front card.
Table 11 APS Connectors Required for Each Chassis and Type of Front Card
Chassis Type MGX-APS-CON800-05307-01 MGX-8850-APS-CON800-20640-01-A0 MGX-8830-APS-CON800-05308-02 MGX-8950-APS-CON800-15308-01-A0MGX 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.3.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 MGX 8850 (PXM1E) and 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 Configuration Guide, Release 5.2 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
Release 5.3.10 does not add or change commands. This sections lists the commands updated in Release 5.3.00 for the following cards:
Changed MPSM Commands
The following commands change in Release 5.3.00:
•
addmpbundle, cnfmpbundle, delmpbundle, addpppmux, cnfpppmux, delpppmux, addcon, cnfcon, and delcon
–
New bundleNumber/ifNum parameter range: 1 to 64 for T1/E1 or 1 to 128 for T3/E3
–
New confirmation message for cnfmpbundle (CSCek31999):
M8830_SF.6.MPSM155PPP[FR].a > cnfmpbundle -bundle 1 -mrru 1500Warning: Bundle Config is being changed, traffic might be interrupted brieflyDo you want to proceed (Yes/No) ?•
addppplink, cnfppplink, and delppplink
–
New link parameter range: 1 to 64 for T1/E1 or 1 to 256 for T3/E3
–
Enhance online help for OC-3, T3/E3, and T1/E1 (CSCek31112)
–
New restartTimer, cnfReqRetry, termReqRetry, echo, and maxFailure parameters for addppplink and cnfppplink (CSCeh29350). See addppplink, 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
Related Commands
cnfport, delport, dspport, dspports, dspportsct
Attributes
Example—ATM Service Context
In the following example, the user creates logical port 3 on line 3 of bay 1. The minimum and maximum cells per second is 96000 cps. The port SCT file ID is 4. The interface type is NNI (specified by the 2 at the end of the command input).
MGX8850.6.MPSM155[ATM].a > addport 3 1.3 96000 96000 4 2
In the following example, the user creates a fractional T1 port on line 5 of bay 1. The logical port number is 205, the minimum and maximum cells per second is 603 cps, the port SCT file ID is 0, and the interface type is NNI. This port has four DS0s, starting with the first DS0 of the T1 line.
M8850_SF.27.MPSM16T1E1[ATM].a > addport 205 1.5 603 603 0 1 -ds0beg 1 -ds0num 4addppplink
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
Attributes
Related Commands
cnfppplink, delppplink, dspppplink
Example
In the following example, the user adds a PPP link 5 and line 1.5 and bundle 5.
M8850_SF.27.MPSM16T1E1PPP[FR].a > addppplink 5 1.5 5cnfppplink
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
Attributes
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 1dsppathalmcnt
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
Related Commands
clrpathalmcnf
Attributes
Example
In the following example, the user displays the path alarm counters for the STS path 1.1.1, which displays the current interval statistics and the elapsed time of the current interval.
M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt -sts 1.1.1Path Number : 1.1.1Path Type : stsPath PM:Elapsed Time(in sec): 309Num of AISs: 0Num of RDIs: 0Near End Far EndCurrentESs : 0 CurrentESs : 0CurrentSESs : 0 CurrentSESs : 0CurrentCVs : 0 CurrentCVs : 0CurrentUASs : 0 CurrentUASs : 0Current24HrESs : 0 Current24HrESs : 0Current24HrSESs: 0 Current24HrSESs: 0Current24HrCVs : 0 Current24HrCVs : 0Current24HrUASs: 0 Current24HrUASs: 0In the following example, the user displays interval statistics for the same path.
M8850_SF.9.MPSM155PPP[FR].a > dsppathalmcnt -sts 1.1.1 2Path Type : stsPath Number : 1.1.1Interval Number : 2Path PM:--------Near End Far EndESs : 0 ESs : 0SESs : 0 SESs : 0CVs : 0 CVs : 0UASs : 0 UASs : 0dspmpbundles
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
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 WPBundle State State Links Bandwidth Cause Status Mode Id-------------------------------------------------------------------------------1 Up Up 1 1536000 No Alarm Disable Enable 12 Up Up 1 1536000 No Alarm Disable Enable 2In the following example, the user displays all MLPPP bundles on an the MPSM-T3E3-155 card:
M8850_SF.10.MPSM155PPP[FR].a > dspmpbundlesMLPPP Admin Oper Active Available Alarm MUX AutoBW WPBundle State State Links Bandwidth Cause Status Mode Id-------------------------------------------------------------------------------1 Up Up 2 3072000 No Alarm Enable Enable 12 Up Up 2 3072000 No Alarm Enable Enable 2dspport
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
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 12Interface Number : 12Line/Path Number : 1.1.2 IMA Group Number : N/AAdmin State : Up Operational State : UpGuaranteed bandwidth(cells/sec): 50 Number of partitions : 1Maximum bandwidth(cells/sec) : 50 Number of SPVC : 1ifType : UNI Number of SPVP : 0VPI number (VNNI, VUNI) : 0 Number of SVC : 0Number of Sig VC : 0MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0SCT Id : 0 =DefF4 to F5 Conversion : DisabledIn 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 205Interface Number : 205Line/Path Number : 1.5 IMA Group Number : N/AAdmin State : Up Operational State : UpGuaranteed bandwidth(cells/sec): 603 Number of partitions : 1Maximum bandwidth(cells/sec) : 603 Number of SPVC : 0ifType : UNI Number of SPVP : 0VPI number (VNNI, VUNI) : 0 Number of SVC : 0Number of Sig VC : 0MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0SCT Id : 0 =DefF4 to F5 Conversion : DisabledTime 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 127Interface Number : 127Line/Path Number : N/A IMA Group Number : 1Admin State : Up Operational State : UpGuaranteed bandwidth(cells/sec): 3000 Number of partitions : 1Maximum bandwidth(cells/sec) : 3000 Number of SPVC : 0ifType : UNI Number of SPVP : 0VPI number (VNNI, VUNI) : 0 Number of SVC : 0Number of Sig VC : 0MIN VPI (EVNNI, EVUNI) : 0 MAX VPI (EVNNI, EVUNI): 0SCT Id : 0 =DefF4 to F5 Conversion : DisabledSample 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 2Interface Number : 2Line Number : 1.1.1DS0 Speed : unusedDS0 Configuration Bit Map : N/AAdmin State : DownOperational State : DownPort State : InactivePort Signaling State : No Signaling FailureInterface Type : Frame RelaySCT Id : 0/0 =DefFrame Header Length : Two BytesFlags Between Frames : 1Equeue Service Ratio : 1Port Speed : 44209 kbpsChecksum type : crc16Over-subscription : DisabledOver-subscribed : FalseSignaling Protocol Type : No SignalingEnhanced LMI : DisabledFRF 1.2 Support : DisabledAsynchronous Updates : DisabledT391 Link Integrity Timer : 10 secsType <CR> to continue, Q<CR> to stop:T392 Polling Verification Timer : 15 secsN391 Full Status Polling Counter : 6N392 Error Threshold : 3N393 Monitored Event Count : 4FRF.12 Fragmentation : DisabledFRF.12 Fragment Size : 64 BytesPort HDLC Frame Inversion : DisabledNumber of Partitions : 1Number of SPVC : 0In 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 : 4Line Number : N/AMFR bundle Number : 1DS0 Speed : unusedDS0 Configuration Bit Map : N/AAdmin State : UpOperational State : UpPort State : ActivePort Signaling State : No Signaling FailureInterface Type : Frame RelaySCT Id : 0/0 =DefFrame Header Length : Two BytesFlags Between Frames : 1Equeue Service Ratio : 1Port Speed : 1532 kbpsChecksum type : crc16Over-subscription : DisabledSignaling Protocol Type : NoneEnhanced LMI : DisabledFRF 1.2 Support : DisabledAsynchronous Updates : DisabledT391 Link Integrity Timer : 10 secsType <CR> to continue, Q<CR> to stop:T392 Polling Verification Timer : 15 secsN391 Full Status Polling Counter : 6N392 Error Threshold : 3N393 Monitored Event Count : 4FRF.12 Fragmentation : DisabledFRF.12 Fragment Size : 64 BytesPort HDLC Frame Inversion : DisabledNumber of Partitions : 1Number of SPVC : 0Sample 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 5Interface Number : 5Line Number : N/ADS0 Speed : unusedDS0 Configuration Bit Map : N/AAdmin State : UpOperational State : UpPort State : ActivePort Signaling State : No Signaling FailureInterface Type : Frame ForwardSCT Id : 0/0 =DefFrame Header Length : Two BytesFlags Between Frames : 1Equeue Service Ratio : 1Port Speed : 1536 kbpsChecksum type : crc16Over-subscription : DisabledSignaling Protocol Type : NoneEnhanced LMI : DisabledFRF 1.2 Support : DisabledAsynchronous Updates : DisabledT391 Link Integrity Timer : 10 secsT392 Polling Verification Timer : 15 secsType <CR> to continue, Q<CR> to stop:N391 Full Status Polling Counter : 6N392 Error Threshold : 3N393 Monitored Event Count : 4FRF.12 Fragmentation : N/AFRF.12 Fragment Size : 64 BytesPort HDLC Frame Inversion : DisabledNumber of Partitions : 1Number of SPVC : 0dspports
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:
Enter the dspports command in the Frame Relay CLI context to display the following information for all Frame Relay ports:
![]()
Note
The operational state for standby cards is reported as N/A because the operational state of the standby card may not be the same as the active card.
Syntax
dspports
Related Commands
addport, cnfport, delport, dspport
Attributes
Sample ATM Service Context
In the following MPSM-T3E3-155 example, the user displays the ATM ports, two of which are IMA groups.
M8850_SF.10.MPSM155[ATM].a > dspportsif Line/Path Admn Oper Guarntd Max SCT if VPI IMA DS0Num Num Stat Stat Rate Rate In Type -------------- GRP StartUse VNNI (EVNNI, (Num)VUNI EVUNI )---- ----------- ---- ---- -------- -------- --- ----- ---- MIN MAX --- ------10 N/A Up Up 7000 7000 0 UNI 0 0 0 1 N/A20 N/A Up Up 7000 7000 0 UNI 0 0 0 2 N/A113 1.1:3 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24)123 1.2:3 Up Up 3622 3622 0 UNI 0 0 0 N/A 1(24)In the following MPSM-16-T1E1 example, the user displays ATM ports, which include two IMA groups, two full T1 ATM ports, and two fractional T1 ATM ports with four DS0s each.
M8850_SF.27.MPSM16T1E1[ATM].a > dspportsif Line/Path Admn Oper Guarntd Max SCT if VPI IMA DS0Num Num Stat Stat Rate Rate In Type -------------- GRP StartUse 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 > dspportsESR: Egress queue Service RatioSCT DS0 Port E FRFIf Line/Path Admn Oper if In Start Speed Signaling LMI 12 MFRNum 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 111 1.1.0:1.1.1 Up Up FR 0 1(24) 1536 1 None Off Off N/ASample 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
Attributes
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 0MLPPP Bundle Number : 1Interval Number : 0Receive Packets : 2101305Receive Bytes : 60955779Receive Discard Bytes : 0Receive MRRU Error Packets : 0Receive Discard Packets : 0Receive FCS Error Packets : 0Receive kbpsAIR : 1509Send Packets : 397Send Bytes : 29390Send kbpsAIR : 0In 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 0MLPPP Bundle Number : 1Interval Number : 0Receive Packets : 2101305Receive Bytes : 60955779Receive Discard Bytes : 0Receive MRRU Error Packets : 0Receive Discard Packets : 0Receive FCS Error Packets : 0Receive kbpsAIR : 1509Send Packets : 397Send Bytes : 29390Send kbpsAIR : 0dspppplnkcnt
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
Attributes
Related Commands
clrppplnkcnt
Example
In the following example, the user displays statistics for interval 0 on PPP link 10 on an MPSM-16-T1E1:
M8850_SF.27.MPSM16T1E1PPP[FR].a > dspppplnkcnt 10 0MLPPP Link Number : 10Interval Number : 0Receive Packets : 2291753Receive Bytes : 66480391Receive Discard Bytes : 0Receive MRU Errors : 0Receive Miscellaneous Errors : 0Receive FCS Error Packets : 0Receive kbpsAIR : 1498Send Packets : 433Send Bytes : 32054Send kbpsAIR : 0In 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 0MLPPP Link Number : 10Interval Number : 0Receive Packets : 2291753Receive Bytes : 66480391Receive Discard Bytes : 0Receive MRU Errors : 0Receive Miscellaneous Errors : 0Receive FCS Error Packets : 0Receive kbpsAIR : 1498Send Packets : 433Send Bytes : 32054Send kbpsAIR : 0Changed 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.
![]()
CautionThis 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 MGX 8850 or 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.
![]()
CautionEnable 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 12 lists supported and disallowed combinations. Yes indicates a supported combination; No indicates a mismatch.
Table 12 Supported and Mismatched PXM and UI Card Combinations
Controller PXM-UI-S3 PXM-UI-S3/BPXM45/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 MGX 88xx or 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
This option is reserved for future use. 0 No Gang, 1 Left, 2 Right, 3 Both Gang Present
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
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 OPTIONSOpt# Value Type Description---- ----- ---- -----------1 1800 16bit Decimal SHM Card Reset Sliding Window (secs)
Enable automatic setting of cell bus clock speed. Type the cnfndparms command without parameters to see all of the options, and then enter 10 and y at the subsequent prompt. This card is a PXM45. Afterwards, see if it is enabled by using the dspcbclk command.
M8850_SF.7.PXM.a > cnfndparmsM8850_SF System Rev: 05.02 Feb. 11, 2006 05:48:41 GMTMGX8850 Node Alarm: CRITICALNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 No Boolean Core Redundancy Enabled4 No Boolean Expanded Memory Enabled for 250K connections5 0x0 8bit Hex Required Power Supply Module Bitmap6 0x0 8bit Hex Required Fan Tray Unit Bitmap7 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))8 atm0 8bit Decimal Primary IP interface for Netmgmt9 lnPci0 8bit Decimal Secondary IP interface for Netmgmt10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled11 Yes Boolean Inband Node-to-Node IP Connectivity Enabled12 0 8bit Decimal 0 No Gang, 1 Left, 2 Right, 3 Both Present13 0 8bit Decimal Card Switchover on Back card FRU mismatch14 No Boolean Card-to-Card High Priority LCN Disabled15 No Boolean Telnet Access To Node Disabled16 No Boolean Insecure Access(Telnet / Ftp) To Node DisablEnter option number (1-16): 10NODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------10 Yes Boolean Auto Setting of Cellbus Clock Rate EnabledEnable/Disable Automatic Cellbus Clock Rate Setting. If option set to:Yes: Automatic Setting Enabled. This allows for automaticdetermination of cell bus clock rate depending on theinsertion and removal of cards such as RPM in the shelf.No: Automatic Setting Disabled. This prevents automaticdetermination of cell bus clock rate. Manual manipulationmust be performed using the cnfcbclk CLI command.Enter value for option 10 (Y/N): YNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------10 Yes Boolean Auto Setting of Cellbus Clock Rate Enableddspndparms
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
Example
Display the current node parameters on this MGX 8850 switch with a PXM1E.
PXM1E-IMA-230.7.PXM.a > dspndparms
PXM1E-IMA-230 System Rev: 04.00 May. 12, 2003 09:37:43 GMTMGX8850 Node Alarm: CRITICALNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 Yes Boolean Core Redundancy Enabled4 0x0 8bit Hex Required Power Supply Module Bitmap5 0x0 8bit Hex Required Fan Tray Unit Bitmap6 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))7 atm0 8bit Decimal Primary IP interface for Netmgmt8 lnPci0 8bit Decimal Secondary IP interface for Netmgmt9 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled10 Yes Boolean Inband Node-to-Node IP Connectivity Enabled11 0 8bit Decimal 0 No Gang, 1 Left, 2 Right, 3 Both Present12 0 8bit Decimal Card Switchover on Back card FRU mismatch13 No Boolean Card-to-Card High Priority LCN DisabledDisplay the current node parameters on this MGX 8850 switch with a PXM45.
M8850_SF.7.PXM.a > dspndparmsM8850_SF System Rev: 05.02 Feb. 11, 2006 05:50:00 GMTMGX8850 Node Alarm: CRITICALNODE CONFIGURATION OPTIONSOpt# Value Type Description---- ----- ---- -----------1 3600 16bit Decimal SHM Card Reset Sliding Window (secs)2 3 8bit Decimal SHM Max Card Resets Per Window (0 = infinite)3 No Boolean Core Redundancy Enabled4 No Boolean Expanded Memory Enabled for 250K connections5 0x0 8bit Hex Required Power Supply Module Bitmap6 0x0 8bit Hex Required Fan Tray Unit Bitmap7 0 8bit Decimal Trap Manager Aging timeout value(Hour(s))8 atm0 8bit Decimal Primary IP interface for Netmgmt9 lnPci0 8bit Decimal Secondary IP interface for Netmgmt10 Yes Boolean Auto Setting of Cellbus Clock Rate Enabled11 Yes Boolean Inband Node-to-Node IP Connectivity Enabled12 0 8bit Decimal 0 No Gang, 1 Left, 2 Right, 3 Both Present13 0 8bit Decimal Card Switchover on Back card FRU mismatch14 No Boolean Card-to-Card High Priority LCN Disabled15 No Boolean Telnet Access To Node Disabled16 No Boolean Insecure Access(Telnet / Ftp) To Node DisablChanged 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.3.10 Limitations, Restrictions, and Notes
This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.3.10.
MGX Voltage Measurement Limitation
Voltage sensing for the MGX 8850, MGX 8830, and MGX 8950 switches monitors the A1/B1 power circuits only. Therefore, if the A1/B1 power module is missing, the entire unit reports 0 volts for the A/B circuits, even though other power modules are present and working.
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 anomaly CSCei02096.
Bandwidth Limits
An 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—MGX 8850 (PXM1E) and MGX 8830:
•
Y-red is not supported on the MCC electrical back card.
•
For inter-card APS to work on the PXM1E-8-155, and one front card is missing or not available, both 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 an MGX 8850, the CBCs are split between the left and right side of the chassis: CBC0 supports slots 1-6 and 17-22 and CBC1 supports slots 9-14 and 25-30. On an MGX 8830, CBC0 supports slots 3, 5, 10, and 12 and CBC1 supports slots 4, 6, 11, and 13. Balance 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 a MGX with PXM45. Point-to-multipoint differs from broadcast because it replicates packets only to specific destination endpoints in the multicast distribution tree.
The MGX 8830 (PXM1E) and MGX 8850 (PXM1E) can be used in conjunction with an MGX (PXM45) in a network to support point-to-multipoint connections. The PXM45 hardware performs cell replication to multiple destination endpoints. The MGX with PXM1E functions as the originating node or as 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 anomaly 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 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 anomaly 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 MGX 8950 with ATM multicast as follows:
•
MGX 8950 system loaded with AXSM/Bs without AXSM-XG cards in the system.
•
MGX 8950 system loaded with all AXSM-XG based cards without AXSM/Bs in the system.
An 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 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 Configuration Guide, Release 5.2.
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.
cc <directory_name>
Step 2
List the directory to identify old files that can be removed and available disk space.
ll
Step 3
Remove any old files (you may also use wild cards in the filename).
rm <complete_filename>
Step 4
List the directory to see if the file has been removed and disk space is available.
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 installatin and upgrade procedures.
Supported Upgrade Paths
Table 13 lists the supported upgrade paths.
Table 13 Supported Upgrade Paths
Desired Software Supported ReleaseRelease 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 Configuration Guide, Release 5.2.
Upgrade Information
The upgrade appendix in the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 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 14 to verify that the node is running a compatible software release.
![]()
Note
Do not attempt to downgrade the AXSM-XG cards to releases earlier than supported.
•
When configuring virtual interfaces (for example, VUNI, VNNI, EVUNI, or EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. The signaling that is applied to a virtual port is independent of the virtual port ATM header. The only limit is that the VPI value must be within the UNI ATM header limitations.
For information about graceful upgrade of AXSM-XG cards, see the Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2.
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 Configuration Guide, Release 5.2 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
Anomalies in Release 5.3.10
This section contains the known, resolved, and changed status anomalies in Release 5.3.10.
Known Anomalies in Release 5.3.10
Table 15 shows the known anomalies in Release 5.3.10:
Resolved Anomalies in Release 5.3.10
Table 16 lists the anomalies that are resolved in Version .201 of Release 5.3.10.
Table 16 Resolved Anomalies in Version .201 of Release 5.3.10
Identifier HeadlineCSCek71275
PXM45/C with H2FPGA CAM shows as Version 2 in dspdevrev.
Table 17 shows the resolved anomalies in Release 5.3.10:
Status Changed Anomalies in Release 5.3.10
Table 18 shows the status changed anomalies in Release 5.3.10:
Resolved Anomalies in Previous Releases
This section contains the resolved anomalies in the following releases:
•
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
Resolved Anomalies in Release 5.3.00
Table 19 lists the resolved anomalies in Release 5.3.00.
Resolved Anomalies in Release 5.2.10
Table 20 lists the anomalies that are resolved in Version .201 of Release 5.2.10.
Table 21 lists the resolved anomalies in Release 5.2.10.
Resolved Anomalies in Release 5.2.00
Table 22 lists the resolved anomalies in Release 5.2.00.
Resolved Anomalies in Release 5.1.20
Table 23 lists the resolved anomalies in Release 5.1.20.
Resolved Anomalies in Release 5.1
Table 24 lists the anomalies that are resolved in Release 5.1.
Resolved Anomalies in Release 5.0.20
Table 25 lists the anomalies that are resolved in Release 5.0.20.
Resolved Anomalies in Release 5.0.10
Table 26 lists the anomalies that are resolved in Release 5.0.10.
Resolved Anomalies in Release 5.0.00
Table 27 lists the anomalies that are resolved in Release 5.0.00.
Known Route Processor Module or MPLS Anomalies
For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.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.
Known VXSM and VISM Anomalies
For information about anomalies with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.3.10.
For information about anomalies with the VISM card, refer to Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.3.30.
Documentation Updates
This section provides updates for the following documents:
•
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Table 28 describes the updates that resolve CSCei54818.
Cisco Frame Relay Services (FRSM/MPSM-8-T1E1) Configuration Guide and
Command Reference for MGX Switches, Release 5.2LMI Autosense is not supported on MPSM-8T1-FRM and MPSM-8E1-FRM cards. The LMI Autosense information in the following sections apply to the FRSM cards only:
•
Chapter 2, "Adding Frame Relay Ports"
•
Chapter 2, "Configuring Frame Relay Ports"
The LMI Autosense options in the following commands apply to the FRSM card only:
•
addport
•
cnfport
•
xcnfport
Documentation
A Finding Cisco User Documentation Online ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. This section explains the product documentation resources that Cisco offers.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
The Product Documentation DVD is a library of technical product documentation on a portable medium. The DVD enables you to access installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the HTML documentation and some of the PDF files found on the Cisco website at this URL:
http://www.cisco.com/univercd/home/home.htm
The Product Documentation DVD is created monthly and is released in the middle of the month. DVDs are available singly or by subscription. Registered Cisco.com users can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
Ordering Documentation
You must be a registered Cisco.com user to access Cisco Marketplace. Registered users may order Cisco documentation at the Product Documentation Store at this URL:
http://www.cisco.com/go/marketplace/docstore
If you do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Documentation Feedback
You can provide feedback about Cisco technical documentation on the Cisco Technical Support & Documentation site area by entering your comments in the feedback form available in every online document.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you will find information about how to do the following:
•
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:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:
•
For emergencies only — security-alert@cisco.com
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 — psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
•
1 877 228-7302
•
1 408 525-6532
![]()
Tip
We encourage you to 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 encryption key 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:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
If you do not have or use PGP, contact PSIRT to find other means of encrypting the data before sending any sensitive material.
Product Alerts and Field Notices
Modifications to or updates about Cisco products are announced in Cisco Product Alerts and Cisco Field Notices. You can receive Cisco Product Alerts and Cisco Field Notices by using the Product Alert Tool on Cisco.com. This tool enables you to create a profile and choose those products for which you want to receive information.
To access the Product Alert Tool, you must be a registered Cisco.com user. (To register as a Cisco.com user, go to this URL: http://tools.cisco.com/RPF/register/register.do) Registered users can access the tool at this URL: http://tools.cisco.com/Support/PAT/do/ViewMyProfiles.do?local=en
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com 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:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
![]()
Note
Use the Cisco Product Identification Tool to locate your product serial number before submitting a request for service online or by phone. You can access this tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link, clicking the All Tools (A-Z) tab, and then choosing Cisco Product Identification Tool from the alphabetical list. This 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.
![]()
Tip
Displaying and Searching on Cisco.com
If you suspect that the browser is not refreshing a web page, force the browser to update the web page by holding down the Ctrl key while pressing F5.
To find technical information, narrow your search to look in technical documentation, not the entire Cisco.com website. On the Cisco.com home page, click the Advanced Search link under the Search box and then click the Technical Support & Documentation.radio button.
To provide feedback about the Cisco.com website or a particular technical document, click Contacts & Feedback at the top of any Cisco.com web page.
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:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco 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 2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—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 channel product 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:
http://www.cisco.com/go/marketplace/
•
Cisco Press publishes a wide range of general networking, training, and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
•
Packet magazine is the magazine for Cisco networking professionals. 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 subscribe to Packet magazine 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:
http://www.cisco.com/en/US/products/index.html
•
Networking Professionals Connection is an interactive website where networking professionals share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
•
"What's New in Cisco Documentation" is an online publication that provides information about the latest documentation releases for Cisco products. Updated monthly, this online publication is organized by product category to direct you quickly to the documentation for your products. You can view the latest release of "What's New in Cisco Documentation" at this URL:
http://www.cisco.com/univercd/cc/td/doc/abtunicd/136957.htm
•
World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0805R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.