Table Of Contents
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.1.20
Table of Contents
Overview
About Release 5.1.20
Locating Software Updates
Features in Release 5.1.20
Features in Release 5.1.00
MPSM-16-T1E1 Card
Operational Modes
Supported Features
Multilink PPP Feature for CDMA2000 and EV-DO
MPSM-155-T3E3 and MPSM-16-T1E1 Online Diagnostics
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.1.00
Product IDs, Card Types, and APS Connectors
Limitations, Restrictions, and Notes for Release 5.1.20
PXM1E Switch Limitations
PXM1E Hardware Limitations
PXM1E Reserved VCIs
PXM1E Point to Multipoint Support
PXM1E Parity Errors
PXM1E Policing Accuracy
PXM45 and PXM1E System Limitations
Maximum Threshold Accuracy
Clearing the Configuration on Redundant PXM45 and PXM1E Cards
SPVC Interoperability Limitations
Service Card Limitations
AXSM-16-155-XG with MCC Back Card Limitations
AXSM-32-T1E1-E and PXM1E-16-T1E1 Card Limitations
AXSM-E Card OAM Limitations
General AXSM Card Limitations
AXSM Card APS Limitations
MPSM Card Limitations
CBSM Card Limitations
IGX Feeder Limitation
Clock Source Limitations
Clearing Card Configuration Notes
PNNI Limitations
Logical Link Limits
Preferred Route Limitations
Priority Route Limitations
Persistent Topology Limitations
Fault Isolation and Trace Limitations
Serial Bus Path Fault Isolation Limitation
Cell Bus Path Fault Isolation and Recovery Limitations
Path and Connection Trace Notes
CLI Access Level Notes
Disk Space Maintenance Notes
Non-native Controller Front Card and PXM-HD Card Notes
Other Limitations and Restrictions
Installation and Upgrade Procedures
Upgrade Information
Upgrading AXSM-XG Cards
Upgrading the VISM-PR Image
Maintenance Information
Anomalies in Release 5.1.20
Known Anomalies in Release 5.1.20
Resolved Anomalies in Release 5.1.20
Status Changed Anomalies
Resolved Anomalies in Previous Releases
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
Documentation
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Acronyms
Release Notes for Cisco MGX 8850, Cisco MGX 8950, and Cisco MGX 8830, Software Version 5.1.20
These release notes are Part Number OL-7277-01 Rev I0, March 2007
Table of Contents
Overview
These release notes contain the following sections:
•
About Release 5.1.20
•Features in Release 5.1.20
•System Requirements
•Limitations, Restrictions, and Notes for Release 5.1.20
•Installation and Upgrade Procedures
•Anomalies in Release 5.1.20
•Resolved Anomalies in Previous Releases
•Documentation
•Obtaining Documentation
•Documentation Feedback
•Cisco Product Security Overview
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
•Acronyms
About Release 5.1.20
Version .202 of Release 5.1.20 is a patch release that does not introduce new features. The resolved anomalies for Version .202 are listed in Table 10.
The following versions of MPSM software on Cisco.com have been updated to include resolved anomaly CSCeh12738:
•MPSM-16-T1E1—From .200 to .202
•MPSM-16-T1E1-PPP—From .201 to .202
•MPSM-T3E3-155—From .200 to .202
See Table 11 in the "Resolved Anomalies in Release 5.1.20" section.
The MPSM-16-T1E1-PPP software on Cisco.com was updated from version .200 to version .201 to include resolved anomalies CSCej17823 and CSCej62559. See Table 12 in the "Resolved Anomalies in Release 5.1.20" section.
The PXM45/PXM1E software on Cisco.com was updated from version .200 to version .201 to include the resolved anomaly CSCei67407. See Table 13 in the "Resolved Anomalies in Release 5.1.20" section.
These release notes describe the system requirements, new features, and limitations that apply to Release 5.1.20. These notes also contain Cisco support information. Release 5.1.20 is a software and hardware release for the following Cisco MGX switches:
•MGX 8830 (PXM1E)
•MGX 8830/B (PXM45)
•MGX 8850 (PXM1E and PXM45)
•MGX 8850/B (PXM1E and PXM45)
•MGX 8950 (PXM45)
Locating Software Updates
Release 5.1.20 software is located at the following URL:
http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml
RPM IOS images are located at the following URL:
http://www.cisco.com/kobayashi/sw-center/sw-ios.shtml
Features in Release 5.1.20
This release 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-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
•Any Service Any Port
General Features
The MPSM-16-T1E1 card supports the following general features:
•Physical interfaces which are configured 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
•SPVCs, SVCs, SPVPs, and PVPs
•Card and port service class templates
•Maximum of 2000 connections (any combination of Frame Relay and ATM connections)
•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 Virtual Switch Interface (VSI)
•Provisioning XPVC endpoints
•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:
•IMA Version 1.0 and 1.1 with fallback and auto restart support
•Up to 16 IMA groups
•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
•CTC and ITC clocking modes supported
Frame Relay Features
The MPSM-16-T1E1 card supports the following Frame Relay features:
•Handles up to 16 T1/E1 worth of Frame Relay traffic
•Ports 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 timeslots)
•56 Kbps ports
•Total of 496 Frame Relay logical ports (16 x 31 timeslots in E1)
•Maximum of 2000 Frame Relay connections
•FR UNI, FR NNI, and Frame Forwarding interfaces
•Ingress cut through mode of frame processing (Waiting is not required 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
•Two-byte Frame Relay header
•Ratio based egress servicing
•FRF.5 (NIW) and FRF.8.1 (SIW) standards
•LMI and Enhanced LMI on all Frame Relay interfaces
•Frame Relay traffic management features
PPP Features
The MPSM-16-T1E1 card supports the following Mulitlink PPP (MLPPP) features:
•PPP and MLPPP
•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
•Four strict priority queues
•CDMA2000® applications with the MWR 1900 and the RPM-XF
•1:N cold standby front card redundancy
•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 utilized.
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 via 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 utilizes 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 usage 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 connTrace 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 preserves.
Table 1 lists the PNNI product enhancement requests incorporated in this release.
Table 1 PNNI Product Enhancement Requests Incorporated
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 multi-peer group (MPG) 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 non segment 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 2 lists Cisco WAN or IOS products that are compatible with Release 5.1.20.
Table 2 Release 5.1.20 Compatibility Matrix
Switch or Component
|
Compatible Software Version
|
MGX 8230 (PXM1)
MGX 8250 (PXM1)
MGX 8850 (PXM1)
|
MGX 1.3.12
MGX 1.3.11
|
MGX 8830 (PXM1E)
MGX8830/B (PXM45)
MGX 8850 (PXM1E and PXM45)
MGX 8850/B (PXM1E and PXM45)
MGX 8950 (PXM45)
|
MGX 5.1.20
MGX 5.0.20
MGX 4.0.17
|
BPX Switch Software
|
Switch Software 9.4.12
Switch Software 9.3.47
BXM firmware MFZ
|
Cisco WAN Manager
|
15.1.50
|
MGX 8220 Shelf
|
MGX 8220 5.0.20
|
|
SES PNNI
|
4.0.15
3.0.25
|
IOS RPM-PR
|
12.3(11)T6
12.3.(11)T4
12.3(7)T10
|
IOS RPM-XF
|
12.3(11)T6
12.3.(11)T4
12.3(7)T10
|
MGX and RPM Software Version Compatibility Matrix
Table 3 lists the software that is compatible for use in a switch running Release 5.1.20 software.
Table 3 MGX and RPM Software Version Compatibility Matrix
Board Pair
|
Boot Software
|
Runtime Software
|
PXM45/B
|
pxm45_005.001.020.201_bt.fw
|
pxm45_005.001.020.202_mgx.fw
|
PXM45/C
|
pxm45_005.001.020.201_bt.fw
|
pxm45_005.001.020.202_mgx.fw
|
PXM45/C MGX 8830/B chassis
|
pxm45_005.001.020.201_bt.fw
|
pxm45_005.001.020.202_m30.fw
|
PXM1E-4-155 MGX 8850 (PXM1E) chassis
|
pxm1e_005.001.020.201_bt.fw
|
pxm1e_005.001.020.201_mgx.fw
|
PXM1E-8-155 MGX 8850 (PXM1E) chassis
|
PXM1E-8-T3E3 MGX 8850 (PXM1E) chassis
|
PXM1E-COMBO MGX 8850 (PXM1E) chassis
|
|
PXM1E-8-155
|
PXM1E-4-155 MGX 8830 chassis
|
pxm1e_005.001.020.201_bt.fw
|
pxm1e_005.001.020.201_m30.fw
|
PXM1E-8-T3E3 MGX 8830 chassis
|
PXM1E-COMBO MGX 8830 chassis
|
|
AXSM-1-2488
|
axsm_005.001.020.200_bt.fw
|
axsm_005.001.020.200.fw
|
AXSM-16-155
|
AXSM-4-622
|
AXSM-16-T3/E3
|
AXSM-1-2488/B
|
axsm_005.001.020.200_bt.fw
|
axsm_005.001.020.200.fw
|
AXSM-16-155/B
|
AXSM-4-622/B
|
AXSM-16-T3/E3/B
|
|
AXSM-2-622-E
|
axsme_005.001.020.200_bt.fw
|
axsme_005.001.020.200.fw
|
AXSM-8-155-E
|
AXSM-16-T3E3-E
|
AXSM-32-T1E1-E
|
AXSM-16-155-XG
|
axsmxg_005.001.020.200_bt.fw
|
axsmxg_005.001.020.200.fw
|
AXSM-4-2488-XG
|
AXSM-1-9953-XG
|
MPSM-16-T1E1
|
mpsm16t1e1_005.001.020.200_bt.fw
|
mpsm16t1e1_005.001.020.202.fw
|
MPSM-16-T1E1-PPP
|
mpsm16t1e1_005.001.020.200.fw
|
mpsm16t1e1ppp_005.001.020.202.fw
|
MPSM-T3E3-155
|
mpsm155_005.001.020.200_bt.fw
|
mpsm155_005.001.020.202.fw
|
MPSM-8-T1E1
|
mpsm_t1e1_030.001.020.200_bt.fw
|
mpsm_t1e1_030.001.020.200.fw
|
MGX-SRME
|
N/A (Obtains from PXM)
|
N/A (Obtains from PXM)
|
MGX-SRME/B
|
N/A (Obtains from PXM)
|
N/A (Obtains from PXM)
|
SRM3T3/C
|
N/A (Obtains from PXM)
|
N/A (Obtains from PXM)
|
AX-CESM-8E1
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
cesm_8t1e1_022.001.020.200.fw
|
AX-CESM-8T1
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
cesm_8t1e1_022.001.020.200.fw
|
MGX-CESM-8T1/B
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
cesm_8t1e1_022.001.020.200.fw
|
MGX-AUSM-8T1/B
|
ausm_8t1e1_AU8_BT_1.0.02.fw
|
ausm_8t1e1_022.001.020.200.fw
|
MGX-AUSM-8E1/B
|
ausm_8t1e1_AU8_BT_1.0.02.fw
|
ausm_8t1e1_022.001.020.200.fw
|
AX-FRSM-8T1
|
frsm_8t1e1_FR8_BT_1.0.06.fw
|
frsm_8t1e1_022.001.020.200.fw
|
AX-FRSM-8E1
|
frsm_8t1e1_FR8_BT_1.0.06.fw
|
frsm_8t1e1_022.001.020.200.fw
|
AX-FRSM-8T1-C
|
frsm_8t1e1_FR8_BT_1.0.06.fw
|
frsm_8t1e1_022.001.020.200.fw
|
AX-FRSM-8E1-C
|
frsm_8t1e1_FR8_BT_1.0.06.fw
|
frsm_8t1e1_022.001.020.200.fw
|
MGX-FRSM-HS2/B
|
frsm_vhs_VHS_BT_1.0.07.fw
|
frsm_vhs_022.001.020.200.fw
|
MGX-FRSM-2CT3
|
frsm_vhs_VHS_BT_1.0.07.fw
|
frsm_vhs_022.001.020.200.fw
|
MGX-FRSM-2T3E3
|
frsm_vhs_VHS_BT_1.0.07.fw
|
frsm_vhs_022.001.020.200.fw
|
MGX-RPM-PR-256
|
rpm-boot-mz.123-11.T6
|
rpm-js-mz.123-11.T6
|
MGX-RPM-PR-512
|
rpm-boot-mz.123-11.T6
|
rpm-js-mz.123-11.T6
|
MGX-RPM-XF-512
|
rpmxf-boot-mz.123-11.T6
|
rpmxf-p12-mz.123-11.T6
|
SNMP MIB Release
The SNMP MIB release for 5.1.20 is mgx8850rel5120mib.tar.
Note SNMP manuals are replaced by the online MIB tool at URL http://tools.cisco.com/ITDIT/MIBS/jsp/index.jsp
Hardware Supported
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
This section also lists front and back card types, and whether APS connectors are supported for
•MGX 8850 (PXM45)
•MGX 8850 (PXM1E)
•MGX 8830
•MGX 8950
Hardware in Release 5.1.00
The following new hardware is introduced in Release 5.1.00.
•MGX 8850/B (PXM1E, PXM45/B, and PXM45/C)
•MPSM-16-T1E1
•RBBN-16-T1E1-1N
•MCC-16-E1-1N
•RED-16-T1E1
•RCON-1TO3-8850B
Product IDs, Card Types, and APS Connectors
Table 4-Table 7 list part number and revision compatibility for front and back cards in the MGX chassis. The tables also list whether an APS connector is required.
Table 4 MGX Chassis, Card, and APS Configurations Part 1
Front Card Type
|
Min. 800 Part Number and Revision
|
Back Card Types
|
APS
Con
|
Min. 800 Part Number and Revision
|
MGX 8850 and 8850/B
PXM45
|
MGX 8850 and 8850/B
PXM1E
|
MGX 8830/B
PXM45
|
MGX 8830
PXM1E
|
MGX 8950
PXM45
|
PXM45/C
|
800-20217-04-A0
|
PXM-HD
|
—
|
800-05052-03-A0
|
x
|
—
|
x
|
—
|
x
|
| |
|
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
SMFIR-1-155-
SFP
SMFLR-1-155-
SFP
MMF-1-155-
SFP
|
Yes
|
800-21518-03-A0
10-1283-01-A0
10-1280-01-A0
10-1308-01-A0
|
—
|
x
|
—
|
x
|
—
|
| |
|
MCC-8-155
|
Yes
|
800-22117-02-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
SMFIR-1-155-
SFP
SMFLR-1-155-
SFP
MMF-1-155-
SFP
|
—
|
800-18698-02-A0
10-1283-01-A0
10-1280-01-A0
10-1308-01-A0
|
—
|
x
|
—
|
x
|
—
|
| |
|
PXM-UI-S3/B
|
—
|
800-21557-01-A0
|
|
|
|
|
|
Table 5 MGX Chassis, Card, and APS Configurations Part 2
Front Card Type
|
Min. 800 Part Number and Revision
|
Back Card Types
|
APS
Con
|
Min. 800 Part Number and Revision
|
MGX 8850 and 8850/B
PXM45
|
MGX 8850 and 8850/B
PXM1E
|
MGX 8830/B
PXM45
|
MGX 8830
PXM1E
|
MGX 8950
PXM45
|
XM-60
|
800-04706-06-A0
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
x
|
MGX-APS-CON
|
800-05307-01-A0
|
—
|
—
|
—
|
x
|
—
|
—
|
—
|
—
|
MGX-8850-APS-
CON
|
800-20640-01-A0
|
—
|
—
|
—
|
x
|
x
|
—
|
—
|
—
|
MGX-8830-APS-
CON
|
800-05308-02
|
—
|
—
|
—
|
—
|
—
|
x
|
x
|
—
|
MGX-8950-APS-
CON
|
800-15308-01-A0
|
—
|
—
|
—
|
—
|
—
|
—
|
—
|
x
|
MGX8950-EXTD-CON
|
800-23813-03-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)
|
x
|
x
|
—
|
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)
|
x
|
—
|
—
|
Table 6 MGX Chassis, Card, and APS Configurations Part 3
Front Card Type
|
Min. 800 Part Number and Revision
|
Back Card Types
|
APS
Con
|
Min. 800 Part Number and Revision
|
MGX 8850 and 8850/B
PXM45
|
MGX 8850 and 8850/B
PXM1E
|
MGX 8830/B
PXM45
|
MGX 8830
PXM1E
|
MGX 8950
PXM45
|
AXSM-1-9953-XG
|
800-07365-06-A0
|
SMFSR-1-9953
|
—
|
800-08237-06-A0
|
—
|
—
|
—
|
—
|
x
|
| |
|
SMFIR-1-9953
|
—
|
800-08246-06-A0
|
|
|
|
|
|
| |
|
SMFLR-1-9953
|
—
|
800-08247-06-A0
|
|
|
|
|
|
AXSM-4-2488-XG
|
800-16987-04-A0
|
SMF-4-2488-
SFP
SMFSR-1-2488-SFP
SMFLR-1-248-
SFP
|
—
|
800-19913-04-A0
10-1421-03
10-1742-01
|
—
|
—
|
—
|
—
|
x
|
AXSM-1-2488
|
800-05795-05-A0
|
SMFSR-1-2488
|
Yes
|
800-05490-05-A0
|
x
|
—
|
—
|
—
|
—
|
| |
|
SMFLR-1-2488
|
Yes
|
800-06635-04-A0
|
|
|
|
|
|
| |
|
SMFXLR-1-
2488
|
Yes
|
800-05793-05-A0
|
|
|
|
|
|
AXSM-1-2488/B
|
800-07983-02-A0
|
SMFSR-1-2488/B
|
Yes
|
800-07255-01-A0
|
x
|
—
|
—
|
—
|
x
|
| |
|
SMFLR-1-2488/B
|
Yes
|
800-08847-01-A0
|
|
|
|
|
|
| |
|
SMFXLR-1-
2488/B
|
Yes
|
800-08849-01-A0
|
|
|
|
|
|
AXSM-4-622
|
800-05774-09-B0
|
SMFIR-2-622
|
Yes
|
800-05383-01-A1
|
x
|
—
|
—
|
—
|
—
|
| |
|
SMFLR-2-622
|
Yes
|
800-05385-01-A1
|
|
|
|
|
|
AXSM-4-622/B
|
800-07910-05-A0
|
SMFIR-2-622/B
|
Yes
|
800-07412-02-B0
|
x
|
—
|
|
