Cisco MGX 8800 Series Switches

Table Of Contents

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

Table of Contents

Overview

About Release 5.1.00

Type of Release

Locating Software Updates

Features in Release 5.1.00

MPSM-16-T1E1

Supported Features

PPPMux and MLPPP on MPSM-16-T1E1

Current PNNI Route Requirement for Networks

New Limitations

Limitations

PNNI PERS

PXM1E QE OAM Enhancement

Online Diag for MPSM-155-T3E3 and MSPM-16-T1E1

IP Connectivity through RPM

Limitations

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

AXSM-16-155-XG with MCC Back Cards

MPSM Notes

MPSM-16-T1E1-PPP Limitation

PXM1E Parity Errors

Higher Level Logical Link Limits

Preferred Route

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

Cell Bus Service Modules (Formerly Known as Narrow Band Service Modules) and RPM-PR

IGX Feeder

Policing Accuracy for PXM1E

Maximum Threshold Accuracy for PXM45 and PXM1E

PXM1E-Based Switches

PXM1E Hardware Limitations

Reserved VCIs

Point to Multipoint Support on PXM1E

AXSM-E OAM

CLI Configurable Access

Controller Card Mastership Sanity Verification

Serial Bus Path Fault Isolation

Cell Bus Path Fault Isolation and Recovery

Disk Space Maintenance

Non-native Controller Front Card and PXM-HD Card

clrsmcnf Command

APS

Path and Connection Trace

Simple Network Timing Protocol (SNTP)

Priority Routing

SPVC Interoperability

Persistent Topology

Manual Clocking

AXSM Cards

AXSM-XG Hardware Limitation

ATM Multicast

Priority Bumping

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

Installation and Upgrade Procedures

Upgrade Information

Upgrading AXSM-XG Cards

Upgrading the VISM-PR Image

Maintenance Information

Anomalies in Release 5.1

Known Anomalies in Release 5.1

Resolved Anomalies in Release 5.1

Resolved Anomalies in Previous Releases

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

Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information

Acronyms

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

---

These release notes are part number OL-6478-01 Rev A0, January 25, 2005.

Table of Contents

Overview

These release notes contain the following sections:

•"About Release 5.1.00" section

•"Features in Release 5.1.00" section

•"System Requirements" section

•"Limitations, Restrictions, and Notes for Release 5.1" section

•"Installation and Upgrade Procedures" section

•"Anomalies in Release 5.1" section

•"Resolved Anomalies in Previous Releases" section

•"Documentation" section

•"Obtaining Documentation" section

•"Documentation Feedback" section

•"Cisco Product Security Overview" section

•"Obtaining Technical Assistance" section

•"Obtaining Additional Publications and Information" section

•"Acronyms" section

About Release 5.1.00

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

Type of Release

Release 5.1.00 is a software and hardware release for the following MGX switches:

•MGX 8830

•MGX 8850 (PXM1E and PXM45)

•MGX 8850/B (PXM1E and PXM45)

•MGX 8950

Locating Software Updates

Release 5.1.00 software is located at the following URL:

http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml

Features in Release 5.1.00

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

•"MPSM-16-T1E1" section

•"PPPMux and MLPPP on MPSM-16-T1E1" section

•"Current PNNI Route Requirement for Networks" section

•"PNNI PERS" section

•"PXM1E QE OAM Enhancement" section

•"Online Diag for MPSM-155-T3E3 and MSPM-16-T1E1" section

•"IP Connectivity through RPM" section

MPSM-16-T1E1

The MPSM-16-T1E1 is a single-height cell bus based card which is supported on the Cisco MGX 8850 (PXM1E and PXM45) and the Cisco MGX 8850/B (PXM1E and PXM45). This card uses a network processor for ATM and Frame Relay traffic management and supports 16 T1 or E1 lines. The card supports both Frame Relay and ATM services simultaneously.

The service module supports unchannelized and channelized T1/E1 interfaces with speeds ranging from T1/E1 down to a single DS0. A detailed list follows of various interfaces, features, and ATM and Frame Relay services supported by the MPSM-16-T1E1.

Limitation: CLLM is not supported in the first release of software. Hardware does have the capability to support this.

Supported Features

This section lists the features that are supported on the MPSM-16-T1E1 card.

Services

The following services are supported:

•Frame Relay

•ATM

•Inverse Multiplexing for ATM (IMA)

•Any Service Any Port

Physical Interface Characteristics

The MPSM-16-T1E1 card supported the following physical interface characteristics:

•Channelized or unchannelized

•16 T1

•16 E1

•Fault Management and Performance Management for T1 and E1

•BERT

Frame Relay Features

The following Frame Relay features are supported:

•Up to 16 E1 worth of Frame Relay traffic

•Support for n x DS0 and T1/E1 Frame Relay interfaces

•Up to 496 logical Frame Relay interfaces

•Up to 2000 user provisioned Frame Relay connections

•FR UNI/FR NNI/Frame Forwarding interfaces

•FRF.5 (NIW) and FRF.8.1 (SIW) standards

•LMI and Enhanced LMI on all Frame Relay interfaces

•Frame Relay traffic management

ATM Features

The following ATM features are supported:

•Up to 16 E1 worth of ATM traffic.

•T1 and E1 ATM interfaces

•Up to 2000 ATM connections

•VPCs and VCCs.

•Up to 32 ATM UNI/NNI/VUNI/VNNI/EVUNI/EVNNI interfaces with signaling.

•IMA version 1.0 and 1.1 with fallback and Auto Restart

•ILMI on all ATM interfaces.

•ATM traffic management features (includes ABR VS/VD)

•VCC/VPC Shaping

General Features

The following features are supported on the MPSM-16-T1E1 card:

•SPVCs, SVCs, SPVPs and PVPs

•Maximum of 2000 connections with any combination of Frame Relay and ATM connections

•FR-FR, FR-ATM, ATM-FR, ATM-VISM, ATM-CE SPVC connection types, where one of end-points resides on the MPSM-16-T1E1 card

•OAM Fault Management.

•Statistics collection and upload to Cisco Wan Manager (CWM)

•Configuration upload to CWM.

•1:1 hot standby redundancy and standard MGX RAS features

•1:N cold standby redundancy

•Connections provisioned on the MGX 8850 PNNI control plane using the MSF Switch architecture based Virtual Switch Interface (VSI)

•Provisioning XPVC endpoints

•Licensing of the supported features

PPPMux and MLPPP on MPSM-16-T1E1

The MPSM is a single height, cell bus based card in the MGX 8850 (PXM45) chassis. In this solution, the MPSM is physically connected to the MWR and uses Multilink Point-to-Point Protocol (MLPPP). Optionally, the MPSM can perform the Point-to-Point Protocol MUX (PPPMux) functionality. All NCP (other than pppMuxCP) and other routing protocols terminate on the RPM-XF.

MPSM is available in two software modes. In the MPSM-ASAP mode, the card is used in either ATM or Frame Relay or Frame Forwarding mode. With the MPSM-MLP mode, the MPSM supports the PPP, MLPPP, and PPPMux functionalities on the card.

MGX 8850 (PXM45) is used for aggregating traffic from several different BTS site routers (MWR) and transferring them over 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 card. MPSM transforms the PPP payload into AAL5 cells and transfers this over to RPM-XF using ciscoPPPoAAL5 encapsulation.

With growth in traffic, you might need to add additional T1/E1 links between the MWR and the MPSM. MPSM would need to perform the MLPPP operation to utilize the aggregate capacity of the individual T1/E1 lines. Also in this application, it is expected that the IP payloads are small (typically voice). Since the overhead associated with PPP (MLPPP) packets increases with smaller payloads, pppMux functionality is required on the MPSM.

The connection between MPSM and RPM-XF is setup as a PVC connection. The bandwidth of this PVC would depend on the number of operation PPP links on an MP bundle. RPM-XF terminates the PPPoAAL5 data and routes the IP traffic over to the backbone IP network.

Current PNNI Route Requirement for Networks

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 SPG and MPG 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.

New Limitations

P2MP calls are not supported. Only SPVC/SPVP connections are supported. CWM does not manage SVC/SVP connections.

A maximum of 10K paths are supported per node. Master ended connections have current route information. Slave ended connections do not have this information.

The configuration upload file contains only a snapshot of the current route information at the time a CWM configuration upload request is received on the switch. Therefore, the snapshot might not contain the latest information. Any connection trace information received 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 applies also to connTrace ACK messages that are received on a congested node.

When a node ID is changed, for each node in the network, disable and re-enable the current route feature using the new CLI command, cnfndcurrte.

This command flushes out all existing current route information and starts collecting new information. After disabling the feature, it is recommended that you wait for at least 9 seconds (time-out period for a connTrace message) before re-enabling it. This time-out period is to avoid processing 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, that connection does not have the 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.

Redundancy is provided with the current route feature. However, due to the requirement that the current route has no impact on routing performance, it is possible to have some connections that do 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.

When the standby PXM card is inserted and reset, the current route information starts to be sent from the active to the standby after the standby card state has changed from Init to Standby. This is designed to avoid significantly 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 bulk update is completed. Therefore, a switchcc that occurs before all current route information is sent to the redundant card (bulk update complete) 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/processing.

When inserting or resetting the standby PXM, use the command, dspndcurrte, to check the flag, Bulkupdate, to ensure that the bulk update is completed before performing a switchcc.

Limitations

This 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 when the feature is enabled are supported.

•An attempt to enable current route on a node which has more than 2K ports is not allowed and results in error.

•When current route is enabled and more than 2K ports are added, memory might not be enough for this feature as well as other applications. Therefore, the applications might not work properly.

•A maximum of 100K connections are supported on PXM45/B when the feature is enabled.

•An attempt to enable current route on a node which has more than 100K connections results in error.

•When current route is enabled and more than 100K connections are added, memory might not be enough for this feature as well as other applications. Therefore, they may not work properly.

PNNI PERS

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 PERs addressed in this release.

Table 1 PNNI PERS 

PER ID	Description
PER 5672	Configure SVCC-RCC
PER 8281	Path Bypass
PER 8282	AW Pruning
PER 8287	Consistent PNNI Link Selection Allow the same `link selection' mechanism being applied to connections of all service categories, i.e. ABR, UBR, CBR and VBR on `minAW links'. This is activated through CLI. Allow provisioning `minAW links' between two switches to be `epsilon-equal AW parallel links'. This is determined with a calculated `epsilon' value. Allow manual provisioning of `absolute' and `percentage' parameters through CLI. These parameters are used to calculate the `epsilon' value through a pre-determined algorithm. If `epsilon-equal AW parallel links' exist between two switches along the selected shortest path, `link selection' should apply. For `epsilon-equal AW parallel links', the secondary `link selection criteria' is maxAvCR. A connection routed to the link with maximum AvCR. If all links have the same AvCR, the connections are routed according to load balance.
PER 8540	Preferred Route Enhancements
PER 8660	Link Selection Enhancements for MPG Pref Rt Conns
PER 8807	cnfpnni - Routing Policy Enhancements

PXM1E QE OAM Enhancement

This feature moves the extraction and injection of OAM loopback cells on the PXM1E from the Atlas to the QE1210. Unlike the Atlas, the QE is able to distinguish between segment and end-to-end OAM loopback cells.

The QE is configured to extract only the segment OAM loopback cells and transparently pass the end-to-end OAM loopback cells. Thus, the end-to-end OAM loopback cells do not require software processing and do not impact CPU utilization.

The end-to-end OAM loopback cells are used for background connection continuity verification. These cells might be sent by a VISM card or router.

Segment OAM loopback cells are used for diagnostic testing between segment endpoints. These cells are sent for the following CLI commands: tstdelay, tstconsegep, and tstpndelay.

Limitations:

The previous limitations for the OAM loopback cell rate on the PXM1E no longer apply to end-to-end OAM loopback cells. These cells are now processed in the QE hardware and are only limited by the available line bandwidth.

A polling induced queue extraction delay of up to 10 ms for a segment OAM loopback cell exists at each PXM1E segment endpoint. This delay is not imposed on end-to-end cells or segment cells at non segment endpoints.

Online Diag for MPSM-155-T3E3 and MSPM-16-T1E1

The online diagnostic tests, when started, would run on regular intervals both on the active and standby state of the MPSM cards to check the health of the various devices and data paths. The online diagnostic tests the following devices and data paths:

•Data path from CPU on MPSM to CBC slave loopback on MPSM via Winpath 0

•Data path from CPU on MPSM to CBC master loopback on the PXM via Winpath 1

•Winpath memory access test (packet, parameter, host memory)

•Write/read test for the following devices on MPSM-155-T3E3:

–CBC

–SPECTRA

–LIMUX

–APOX

–TEMUX

–IMA84

–FRDM84

–SUNI4xJet

–MPC FPGA

–MIAC PLD

•Write/read test for the following devices on the MPSM-16-T1E1:

–MPCTL FPGA

–SLFP FPGA

–COMET Framer

•Validate front card NVRAM checksum

•Validate flash checksum

IP Connectivity through RPM

IP connectivity can be achieved, in addition to traditional Ethernet port, using one of the following methods:

•Through AXSM and MPSM cards using IP over ATM by setting up an SVC connection between the card and a router with ATM connection

•Through dynamically created PVC connections by PNNI for IP over ATM interface

Limitations

If the clrallcnf, clrcnf, or clrsmcnf commands are executed, the persistent data pertaining to the IP connectivity is lost. This will result in lost connectivity. You must reconfigure the RPM and PXM cards for IP connectivity again.

Access the cards through a console port or normal Ethernet port. If you are connected to the node via this connectivity, and attempt to delete the SPVC accidently, there is no protection against it. In this case, you must re-add the SPVC again via the console port or normal Ethernet port.

The IP addresses of hosts (workstations) accessing the MGX 8850 node are kept in a RAM cache. Since this cache can not expand beyond a limit, 50 such entries are allowed in the table. The implication is that if the table is full, and first 50 IP hosts are actively accessing the node, new IP hosts are blocked until cache clears (as result of inactivity from some hosts) to make room for new entries.

This solution is intended to manage only one MGX through RPM at this time. It does not address management of a network of nodes.

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

Table 2 Release 5.1.00 Compatibility Matrix 

Switch or Component	Compatible Software Version
MGX 8230 (PXM1) MGX 8250 (PXM1) MGX 8850 (PXM1)	MGX 1.3.11 MGX 1.3.10
MGX 8850 (PXM45) MGX 8850 (PXM1E) MGX 8950 (PXM45) MGX 8830 (PXM1E)	MGX 5.1.00 MGX 5.0.10 MGX 4.0.17 MGX 4.0.15
BPX Switch Software	Switch Software 9.4.10 BXM firmware MFZ
Cisco WAN Manager	CWM 15.1.00
MGX 8220 Shelf	MGX 8220 5.0.20
SES PNNI	4.0.15
VISM-PR	VISM 3.3.10 VISM 3.2.11 VISM 3.1.2
IOS RPM-PR	12.3(11)T3 12.3(7)T3 12.3(2)T7
IOS RPM-XF	12.3(11)T3 12.3(7)T3 12.3(2)T7

MGX and RPM Software Version Compatibility Matrix

Table 3 lists the software that is compatible for use in a switch running Release 5.1.00 software.

Table 3 MGX and RPM Software Version Compatibility Matrix 

Board Pair	Boot Software	MinimumBoot Code Version	Runtime Software	Latest FirmwareVersion
PXM45/B	pxm45_005.001.000.200_bt.fw	5.0.20	pxm45_005.001.000.200_mgx.fw	5.1.00
PXM45/C	pxm45_005.001.000.200_bt.fw	5.0.20	pxm45_005.001.000.200_mgx.fw	5.1.00
PXM1E-4-155 MGX 8850 (PXM1E) chassis	pxm1e_005.001.000.200_bt.fw	5.0.20	pxm1e_005.001.000.200_mgx.fw	5.1.00
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.000.200_bt.fw	5.0.20	pxm1e_005.001.000.200_m30.fw	5.1.00
PXM1E-8-T3E3 MGX 8830 chassis
PXM1E-COMBO MGX 8830 chassis
AXSM-1-2488	axsm_005.001.000.200_bt.fw	5.0.20	axsm_005.001.000.200.fw	5.1.00
AXSM-16-155
AXSM-4-622
AXSM-16-T3/E3
AXSM-1-2488/B	axsm_005.001.000.200_bt.fw	5.0.20	axsm_005.001.000.200.fw	5.1.00
AXSM-16-155/B
AXSM-4-622/B
AXSM-16- T3/E3/B
AXSM-2-622-E	axsme_005.001.000.200_bt.fw	5.0.20	axsme_005.001.000.200.fw	5.1.00
AXSM-8-155-E
AXSM-16-T3E3-E
AXSM-32-T1E1-E
AXSM-16-155-XG	axsmxg_005.001.000.200_bt.fw	5.0.20	axsmxg_005.001.000.200.fw	5.1.00
AXSM-4-2488-XG
AXSM-1-9953-XG
MPSM-16-T1E1	mpsm16t1e1_005.001.000.200_bt.fw	5.1.00	mpsm16t1e1_005.001.000.200.fw	5.1.00
MPSM-16-T1E1- PPP	mpsm16t1e1_005.001.000.200_bt.fw	5.1.00	mpsm16t1e1ppp_005.001.000.200.fw	5.1.00
MPSM-T3E3-155	mpsm155_005.001.000.200_bt.fw	5.0.20	mpsm155_005.001.000.200.fw	5.1.00
MPSM-8-T1E1	mpsm_t1e1_030.001.000.200_bt.fw	30.0.20	mpsm_t1e1_030.001.000.200.fw	30.1.00
MGX-SRME	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A
MGX-SRME/B	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A
SRM3T3/C	N/A (Obtains from PXM)	N/A	N/A (Obtains from PXM)	N/A
AX-CESM-8E1	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.001.000.200.fw	22.1.00
AX-CESM-8T1	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.001.000.200.fw	22.1.00
MGX-CESM- 8T1/B	cesm_8t1e1_CE8_BT_1.0.02.fw	1.0.02	cesm_8t1e1_022.001.000.200.fw	22.1.00
MGX-AUSM- 8T1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_022.001.000.200.fw	22.1.00
MGX-AUSM- 8E1/B	ausm_8t1e1_AU8_BT_1.0.02.fw	1.0.02	ausm_8t1e1_022.001.000.200.fw	22.1.00
AX-FRSM-8T1	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.001.000.200.fw	22.1.00
AX-FRSM-8E1	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.001.000.200.fw	22.1.00
AX-FRSM- 8T1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.001.000.200.fw	22.1.00
AX-FRSM- 8E1-C	frsm_8t1e1_FR8_BT_1.0.06.fw	1.0.06	frsm_8t1e1_022.001.000.200.fw	22.1.00
MGX-FRSM- HS2/B	frsm_vhs_VHS_BT_1.0.07.fw	1.0.07	frsm_vhs_022.001.000.200.fw	22.1.00
MGX-FRSM- 2CT3	frsm_vhs_VHS_BT_1.0.07.fw	1.0.07	frsm_vhs_022.001.000.200.fw	22.1.00
MGX-FRSM- 2T3E3	frsm_vhs_VHS_BT_1.0.07.fw	1.0.07	frsm_vhs_022.001.000.200.fw	22.1.00
MGX-RPM-PR-256	rpm-boot-mz.123-11.T3	12.3(7) T3	rpm-js-mz.123-11.T3	12.3(11)T3
MGX-RPM-PR-512	rpm-boot-mz.123-11.T3	12.3(7) T3	rpm-js-mz.123-11.T3	12.3(11)T3
MGX-RPM-XF-512	rpmxf-boot-mz.123-11.T3	12.3(7) T3	rpmxf-p12-mz.123-11.T3	12.3(11)T3
MGX-VISM-PR- 8T1	vism_8t1e1_VI8_BT_3.2.00.fw	3.2.0	vism-8t1e1-003.053.000.200.fw (CALEA image) vism-8t1e1-003.003.000.200.fw (non-CALEA image)	3.53.00 3.3.00
MGX-VISM-PR- 8E1	vism_8t1e1_VI8_BT_3.2.00.fw	3.2.0	vism-8t1e1-003.053.000.200.fw (CALEA image) vism-8t1e1-003.003.000.200.fw (non-CALEA image)	3.53.00 3.3.00

SNMP MIB Release

The SNMP MIB release for 5.1.00 is mgx8XXXrel5100mib.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 lists part number and revision compatibility for front and back cards in the MGX chassis. The table also lists whether an APS connector is required.

Table 5 presents a guide on which APS connector to use with which MGX chassis and front card.

In these tables:

•R- means that this is a redundant card, for AX-R-RJ48-8E1, AX-R-RJ48-8T1, and AX-R-SMB-8E1 cards.

•Either of these connectors work for the AXSM cards in the MGX 8850 (PXM45) switch: MGX-8850-APS-CON or MGX-APS-CON.

•The PXM45 card is not supported in Release 5.0.00 and higher. The PXM45/B and PXM45/C cards are supported.

•The SCSI2-2HSSI/B card has two different 800 part numbers, and both part numbers are valid.

•The PXM1E-COMBO card is also known as PXM1E-T3E3-155 card.

•MGX 8950 does not support the AXSM/A or the AXSM-E cards. If these cards are present, they will show up as "Failed" when the dspcds command is issued.

Table 4 MGX Chassis, Card, and APS Connector Configurations 

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 PXM1E	MGX 8950 PXM45
PXM45/C	800-20217-04-A0	PXM-HD	—	800-05052-03-A0	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
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	—
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	—
		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	—
		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	x	x	—
		MCC-16-E1-1N	—	800-23135-02
		RED-16-T1E1	—	800-23092-04
RCON-1TO5-8850	800-23094-03	—	—	—	x (only the /B chassis)	x (only the /B chassis)
RCON-1TO3- 8850	800-23196-01	—	—	—	x (only the /B chassis)	x (only the /B chassis)	—	—
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-2488- 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	—	—	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	—	—	—
		SMFLR-1-622/C	Yes	800-07411-02-A0
AXSM-16-155-XG	800-20821-06-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
AXSM-16-155	800-05776-06-A0	MMF-8-155-MT	Yes	800-04819-01-A1	x	—	—	—
		SMFIR-8-155- LC	Yes	800-05342-01-A0
		SMFLR-8-155- LC	Yes	800-05343-01-C0
AXSM-16-155/B	800-07909-05-A0	MMF-8-155- MT/B	Yes	800-01720-02-A0	x	—	—	x
		SMFIR-8-155- LC/B	Yes	800-07864-02-B0
		SMFLR-8-155- LC/B	Yes	800-07865-02-B0
AXSM-8-155-E	800-18520-02-A0	SMB-4-155	Yes	800-07425-02-A0	x	—	—	—
		MMF-4-155/C	Yes	800-07408-02-A0
		SMFIR-4-155/C	Yes	800-07108-02-A0
		SMFLR-4-155/C	Yes	800-07409-02-A0
AXSM-16-T3E3 AXSM-16-T3E3/B AXSM-16-T3E3-E	800-05778-08-A0 800-07911-05-A0 800-18519-02-A0	S