Table Of Contents
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.2.20
Table of Contents
Overview
About Release 5.2.20
Type of Release
Locating Software Updates
Features in Release 5.2.20
MPSM Licensing
Features in Release 5.2.10
Features in Release 5.2.00
MGX-VXSM-T3 Card
AXSM-8-622-XG Card
Graceful Upgrades to AXSM-XG Cards
Multilink PPP on the MPSM-T3E3-155 Card
PXM45/C Support in the MGX 8830/B Chassis
Mobile PNNI Support
Compression and Multiplexing Support for RPM-PR Cards
Service Class Template (SCT) File Information
PXM1E
AXSM and AXSM/B
AXSM-E
AXSM-XG
MPSM-T3E3-155
MPSM-16-T1E1
Features in Release 5.1.20
Features in Release 5.1.00
MPSM-16-T1E1 Card
Operational Modes
Supported Features
Multilink PPP Feature for CDMA2000 and EVDO
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
PNNI Current Route Feature
Operational and Redundancy Limitations
Feature Specifications
PNNI Product Enhancements
PXM1E OAM Enhancement
IP Management Connections through the RPM
System Requirements
Software/Firmware Compatibility Matrix
MGX and RPM Software Version Compatibility Matrix
SNMP MIB Release
Hardware Supported
Hardware in Release 5.2.20
Product IDs, Card Types, and APS Connectors
New and Changed Commands
Mobile PNNI
Graceful Upgrade
Online Insertion or Removal of the MGX-RPM-1FE-CP Back Card
Limitations, Restrictions, and Notes
MGX Chassis Bandwidth Limitations
Bandwidth Limits
Card Placement Guidelines
Bandwidth Oversubscription
PXM1E Switch Limitations
PXM1E Hardware Limitations
PXM1E Reserved VCIs
PXM1E Point to Multipoint Support
PXM1E Policing Accuracy
PXM45 and PXM1E System Limitations
Maximum Threshold Accuracy
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
Service Card Limitations
AXSM Channel Loopback Limitation
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
AXSM-E Card OAM Limitations
General AXSM Card Limitations
AXSM Card APS Limitations
MPSM Card Limitations
CBSM Card Limitations
IGX Feeder Limitation
Clock Source Limitations
Clearing Card Configuration Notes
PNNI Limitations
Logical Link Limits
Preferred Route Limitations
Priority Route Limitations
Persistent Topology Limitations
Fault Isolation and Trace Limitations
Serial Bus Path Fault Isolation Limitation
Cell Bus Path Fault Isolation and Recovery Limitations
Path and Connection Trace Notes
CLI Access Level Notes
Disk Space Maintenance Notes
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Upgrade Information
Upgrading AXSM-XG Cards
Upgrading the VISM-PR Image
Maintenance Information
Anomalies in Release 5.2.20
Known Anomalies in Release 5.2.20
Resolved Anomalies in Release 5.2.20
Resolved Anomalies in Previous Releases
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
Documentation Updates
Cisco PNNI Network Planning Guide for MGX and SES Products Updates
Cisco Frame Relay Services (FRSM/MPSM-8-T1E1) Configuration Guide and
Command Reference for MGX Switches, Release 5.2
Cisco MGX 8800/8900 Series Configuration Guide, Release 5.2 Updates
Appendix A: Downloading and Installing Software Upgrades
Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG
Supported Configurations
Limitations
Preparing to Upgrade
Converting Custom SCTs
Graceful Upgrade Procedure
Non-Graceful Upgrade Procedure
Documentation
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Product Alerts and Field Notices
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Acronyms
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Release 5.2.20
Part Number OL-11392-01 Revision B0, March 2007.
Table of Contents
Overview
These release notes contain the following sections:
•
About Release 5.2.20
•Features in Release 5.2.20
•Features in Release 5.2.10
•Features in Release 5.2.00
•Features in Release 5.1.20
•Features in Release 5.1.00
•System Requirements
•New and Changed Commands
•Limitations, Restrictions, and Notes
•Installation and Upgrade Procedures
•Anomalies in Release 5.2.20
•Resolved Anomalies in Previous Releases
•Documentation Updates
•Appendix A: Downloading and Installing Software Upgrades
•Documentation
•Obtaining Documentation
•Documentation Feedback
•Cisco Product Security Overview
•Product Alerts and Field Notices
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
•Acronyms
About Release 5.2.20
Version .201 of Release 5.2.20 is a patch release that does not introduce new features. The resolved anomalies for Version .201 are listed in Table 11.
These release notes describe the features, system requirements, and limitations that apply to Release 5.2.20 of the Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830 multiservice switches. These notes also contain Cisco support information.
Type of Release
Release 5.2.20 is a software release for the following Cisco MGX multiservice switches:
•MGX 8830 (PXM1E)
•MGX 8830/B (PXM1E and PXM45)
•MGX 8850 (PXM1E and PXM45)
•MGX 8850/B (PXM1E and PXM45)
•MGX 8950 (PXM45)
Locating Software Updates
Release 5.2.20 software is located at:
http://www.cisco.com/cgi-bin/tablebuild.pl/MGX8850-5220-hidden
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.2.20
This sections describes the features in Release 5.2.20.
MPSM Licensing
Release 5.2.20 enforces licenses through sales and support, rather than through software locks. Table 1 lists the MPSM licenses that are required for MPSM services and features. You must purchase licenses for the services and features that you plan to use on each MSPM card.
Note Before upgrading to Release 5.2.20, enter saveallcnf to preserve existing licensing information.
Table 1 Licensed Services for MPSM Cards
Card Type
|
License
|
Description
|
Software Release Support
|
5.0.20
|
5.1.20
|
5.2.00 and later
|
MPSM-8-T1E1
|
MPSM-RC-8-LIC
|
Rate Control—Enables either Standard ABR or Foresight features for Frame Relay connections.
|
x
|
x
|
x
|
MPSM-16-T1E1
|
MPSM-RC-16-LIC
|
Rate Control—Enables the Standard ABR feature for Frame Relay connections.
|
|
x
|
x
|
MPSM-MS-16-LIC
|
Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.
|
|
x
|
x
|
MPSM-ML-16-LIC
|
MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).
|
|
x
|
x
|
MPSM-PPP-16-LIC
|
MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).
|
|
x
|
x
|
MPSM-SR-16-LIC
|
1:N Redundancy
|
|
x
|
x
|
MPSM-T3E3-155
|
MPSM-CH-HS-LIC
|
Channelization—Enables channelization of the physical port into multiple DS0s for Frame Relay service and/or DS1s for ATM service.
|
x
|
x
|
x
|
MPSM-RC-HS-LIC
|
Rate Control—Enables the Standard ABR feature for Frame Relay connections.
|
x
|
x
|
x
|
MPSM-MS-HS-LIC
|
Multiservice (ASAP)—Enables simultaneous provisioning of both ATM and Frame Relay.
|
x
|
x
|
x
|
MPSM-ML-HS-LIC
|
MLFR and IMA—Enables the multilink features, Multilink FrameRelay (MFR) and Inverse Multiplexing for ATM (IMA).
|
x
|
x
|
x
|
MPSM-PPP-HS-LIC
|
MLPPP and PPPmux—Enables Multilink Point-to-Point Protocol (MLPPP), which includes PPP Multiplexing (PPPMux).
|
|
|
x
|
Release 5.2.20 removes the PXM commands that support software locks and license alarms, and changes the commands that display alarm information. The following commands are removed or changed:
•Removed PXM commands:
–cnflic
–dsplics
–dspliccds
–dspliccd
–dsplicnodeid
–dsplicalms
•Changed PXM commands:
–clrallcnf—No longer has the clrLicense argument
–dspndalms—No longer displays license alarms
–dspcdalms—No longer displays license alarms
The MIB for Release 5.2.20 does not change, but returned license information is no longer valid.
Features in Release 5.2.10
Version .201 of Release 5.2.10 adds UDI compliance for the Cisco MGX 8830/B chassis, and Version .202 changes the Cisco product identifier (PID) from MGX8830/B to MGX8830/B-CH. The UDI consists of the Cisco product identifier, version identifier (VID), and serial number (SN).
The show inventory command displays the PID, VID, and SN for each product in the chassis. The following example shows typical UDI information for the Cisco MGX 8830/B chassis:
M8830_SF.1.PXM.a > show inventory
NAME: "1" , DESCR: "Cisco MGX8830 Model B, 14 Slot chassis"
PID: MGX8830/B-CH, VID: , SN: -----
NAME: "" , DESCR: "Cisco MGX8830 Model B Backplane"
PID: MGX8830/B-CH, VID: V01, SN: SCA09380009
Features in Release 5.2.00
Release 5.2.00 has the following features:
•MGX-VXSM-T3 Card
•AXSM-8-622-XG Card
•Graceful Upgrades to AXSM-XG Cards
•Multilink PPP on the MPSM-T3E3-155 Card
•PXM45/C Support in the MGX 8830/B Chassis
•Mobile PNNI Support
•Compression and Multiplexing Support for RPM-PR Cards
•Service Class Template (SCT) File Information
MGX-VXSM-T3 Card
Release 5.2.00 introduces 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 a single 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 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
•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 intra-card, and facility protection with single front card and two 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 ms 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
In this release, 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 four 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 Upgrading an AXSM/A, AXSM/B, or AXSM-E to an AXSM-XG.
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 EVDO
•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 narrowband, 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 allowed to join a parent peer group of one of the fixed switches.
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
Service Class Template (SCT) File Information
This section contains SCT file information for Release 5.2.00.
PXM1E
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 filenames 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
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 filenames 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
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 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
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 filenames 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
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 filenames 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
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 filenames 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
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 EVDO
Features in Release 5.1.00
This section contains the descriptions of the following new features in Release 5.1.00:
•MPSM-16-T1E1 Card
•PNNI Current Route Feature
•PNNI Product Enhancements
•PXM1E OAM Enhancement
•IP Management Connections through the RPM
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
You boot into one mode or the other during initial card startup.
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. The MPSM-16-T1E1 cannot be the CE end point for ATM-CE connections because the MPSM-16-T1E1 does not support circuit emulation.
•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 Circuits (XPVC) endpoints. A 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:
•Handles 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.
•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 EVDO
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 via 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
PNNI Current Route Feature
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 new CLI command, cnfndcurrte.
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 conn-trace message) before re-enabling it. This inhibits processing of stale connTrace 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 the new 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 Bulkupdate is complete before performing a switchcc.
Feature Specifications
The current route feature has the following limits:
•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 new functionality to parallel links to which link selection criteria is provisioned to `minAW' (`minAWlinks'). This feature can be activated through the CLI. If these enhancements are not activated, the existing `link selection' behavior is used.
Table 2 lists the PNNI product enhancement requests incorporated in this release.
Table 2 PNNI Product Enhancements
PER ID
|
Description
|
PER 5672
|
SVCC-RCC connection configuration
This enhancement introduces a command (cnfpnni-svcc-rcc-param) to configure the connection parameters associated with SVCC-RCC connections at each level of the PNNI hierarchy.
|
PER 8281
|
Path bypass selection configuration
In a complex node multiple peer group topology, the path that has the highest available cell rate (AvCR) is advertised as the bypass. Typically this path has higher cost, so the calls routed over the pass bypass might always take the worst path. This enhancement adds an option to the cnfpnni-routing-policy command to specify the criteria for bypass path selection.
|
PER 8282
|
Administrative Weigh (AW) Pruning
Currently a trunk is included in the best path selection even if it has a single cell per second of AvCR. This enhancement introduces an AvCR threshold parameter to the cnfpnni-routing-policy command so that trunks with BW below the threshold are excluded from the best path search.
|
PER 8287
|
Consistent PNNI Link Selection
Allows application of the same link selection mechanism to connections of all service categories (ABR, UBR, CBR and VBR) on `minAW links'.
Allows provisioning `epsilon-equal AW parallel links' among the `minAW parallel links' between two switches. The switch calculates the `epsilon' value based on user inputs.
If `epsilon-equal AW parallel links' exist between two switches along the selected shortest path, `link selection' applies. For `epsilon-equal AW parallel links', the secondary `link selection criteria' is maxAvCR. If all links have the same AvCR, the connections are routed according to load balance criteria.
|
PER 8540
|
Preferred Route Enhancements
The cnfndidrtes command has a new parameter for indicating that the same node is being configured and that the preferred route status should not change. A connection that was on a preferred route before the change would not be groomed by route optimization.
|
PER 8660
|
Link Selection Enhancements for MPG (multi-peer group) Pref Rt Conns
|
PER 8807
|
Routing Policy Enhancements
This enhancement adds a parameter value to the cnfpnni-routing-policy command that selects from equal administrative weight (AW) paths using the number of minimum hops. If multiple epsilon-equal AW paths with the same minimum-hops exist, a second load balance parameter specifies the tiebreak criteria.
|
PXM1E OAM Enhancement
The PXM1E processes the following OAM loopback cells:
•End-to-end OAM loopback cells—Used for background connection continuity verification. These cells might be sent by a VISM card or router.
•Segment OAM loopback cells—Used for diagnostic testing between segment endpoints. These cells are sent for the following CLI commands: tstdelay, tstconsegep, and tstpndelay.
This release moves the task of extracting and injecting OAM loopback cells at the PXM1E from the Atlas to the QE1210. Unlike with Atlas, the QE1210 can distinguish between segment and end-to-end OAM loopback cells. The QE1210 extracts only the segment OAM loopback cells, while transparently passing the end-to-end OAM loopback cells.
Because the end-to-end OAM loopback cells no longer require software processing, the previous limitations for the OAM loopback cell rate on the PXM1E no longer apply. These cells are now processed in the QE1210 hardware and are limited only by the available line bandwidth.
Each PXM1E segment endpoint has a polling-induced queue extraction delay of up to 10 ms for a segment OAM loopback cell. This delay is not imposed on end-to-end cells or segment cells at nonsegment endpoints.
IP Management Connections through the RPM
You can manage the MGX 8850 node from the traditional Ethernet or console port, or you can set up one of the following connections:
•Through the AXSM or MPSM cards using an SVC to the PXM card
•Through the RPM card using a PVC to the PXM card
This release changes the PXM svcifconfig command to support management connections through the RPM card.
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.
Use this solution to manage only one MGX 8850 node through RPM, not an entire network of nodes.
Note If you are connected to the MGX node 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 If the clrallcnf, clrcnf, or clrsmcnf commands are executed, the persistent data pertaining to the IP connections is lost and connections are dropped. To restore RPM access, you must reconfigure the RPM and PXM cards for IP connectivity, using the console port or Ethernet port.
System Requirements
This section describes software compatible with this release and lists the supported hardware.
Software/Firmware Compatibility Matrix
Table 3 lists Cisco WAN or Cisco IOS software products that are compatible with Release 5.2.20.
Table 3 Release 5.2.20 Compatibility Matrix
Switch or Component
|
Compatible Software Version
|
MGX 8230 (PXM1)
MGX 8250 (PXM1)
MGX 8850 (PXM1)
|
MGX1.3.14
MGX 1.3.12
MGX 1.3.11
|
MGX 8830/B (PXM45/C)
|
MGX 5.2.20
MGX 5.2.10
MGX 5.2.00
|
MGX 8830 (PXM1E)
MGX 8830/B (PXM1E)
MGX 8850 (PXM1E and PXM45)
MGX 8850/B (PXM1E and PXM45)
MGX 8950 (PXM45)
|
MGX 5.2.20
MGX 5.2.10
MGX 5.2.00
|
BPX Switch Software
|
Switch Software 9.4.12
Switch Software 9.3.51
Switch Software 9.3.47
BXM firmware MFZ
|
Cisco WAN Manager
|
15.1.50
|
MGX 8220 Shelf
|
MGX 8220 5.0.20
|
