Home | Skip to Content | Skip to Search | Skip to Navigation | Skip to Footer |
Worldwide [change] |Register |About Cisco
Guest

Hierarchical Navigation

Cisco MGX 8800 Series Switches

4.0.12 Release Notes for MGX 8950, MGX 8850 (PXM45), MGX 8850 (PXM1E), and MGX 8830

Downloads

Table Of Contents

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

Contents

About Release 4.0.12

Type of Release

Locating Software Updates

New Features and Enhancements in Release 4.0.12

Point-to-Multipoint Support on AXSM-E

AXSM-A/B Multicast Support

Crossbar handling of requests from broadband service modules:

Broadband Service module request generation:

Limitations in AXSM-A involving multicast traffic:

Limitations of both AXSM-A and AXSM/B

Frame Discard Feature

New Features and Enhancements in Release 4.0.11

Features and Enhancements in Previous Release 4.0.10

LMI AutoSense

addport

xcnfport

cnfport

dspport

Resource Monitoring

Platforms

Add Channel Loopback on AXSM-E (PER 3854)

Platforms

Service Module Core Hot Dump

Platforms

Active PXM Freeze Detection and Recovery (PER 7869)

Platforms

Improved SCM Polling Diagnostics on Active and StandBy PXM

Platforms

Cell Bus Service Module on PXM-45 (Expanded from MGX 4.0.00 Release)

Platform

AXSM/B as Feeder Uplink on MGX 8950

Platforms

Features and Enhancements in Previous Release 4.0.00

Closed User Groups

Platforms

References

Preferred Routes for PNNI Multipeer Group Networks

Platforms

References

Point-to-Multipoint SVC/SPVC Support

Platforms

References

Increased Number of Signaling Interfaces

Platforms

PXM1E-Related Hardware (the PXM1E-8-155 card)

Redundancy Support

Automatic Protection Switching Support

Modular Transceiver Support in the New 8-port OC3/STM1 Back Card

UNI connection support in PXM1E-16-T1E1

ATM Routing in PXM1E

Connection Management

Cell Bus Service Module Support

Virtual Trunks Support in PXM1E

Virtual UNI Support in PXM1E

Feeder Trunk support in PXM1E

PXM1E Diagnostics

AXSM-E as Upstream to Feeder Nodes

Platform

Cell Bus Service Modules on PXM45

Platform

AXSM-32-T1E1-E UNI with IMA

Platforms

PXM45/C

Platforms

AXSM-1-9953-XG

Platforms

AXSM-4-2488-XG

Platforms

Enhancements

Service Class Template (SCT) File Information

PXM1E

AXSM and AXSM/B

AXSM-E

AXSM-4-2488-XG

FRSM-12-T3E3

System Requirements

Software/Firmware Certified Releases

MGX and RPM Software Version Compatibility Matrix

Hardware Supported

New Hardware in Release 4.0.12

New Hardware in Release 4.0.11

New Hardware in Release 4.0.10

New Hardware in Previous Release 4.0.00

APS Connectors

MGX 8850 (PXM45) Product IDs and Card Types

MGX 8850 (PXM1E) Product IDs and Card Types

MGX 8830 Product IDs and card types

MGX 8950 Product IDs and card types

New and Changed Commands

Limitations, Restrictions, and Notes for 4.0.12

Limitations

Upgrading to 4.0.10

Higher Level Logical Link Limits

CLI Upgrade

Preferred Route

PXM45/C

192 Signaling Interfaces

Closed User Group (CUG)

Point to Multipoint SVC/SPVC Support

AXSM-32-T1E1-E/PXM1E-16-T1E1

Cell Bus Service Modules (formerly know as Narrow Band Service Module) and RPM-PR

AXSM-E as Upstream to Feeder Nodes

IGX Feeder

Policing Accuracy for PXM1E

Maximum Threshold Accuracy for PXM45 and PXM1E

PXM1E-Based Switches

AXSM-E OAM

CLI Configurable Access

Controller Card Mastership Sanity Verification

Serial Bus Path Fault Isolation

Cell Bus Path Fault Isolation and Recovery

FRSM-12-T3E3

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 Interop

Preferred Route

Persistent Topology

Manual Clocking

AXSM Cards

AXSM-XG Hardware Limitation

ATM Multicast

RPM-PR and RPM-XF Limitations

Restrictions

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

AXSM Model B Restrictions

Formatting Disks

Saving Configurations

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 and PXM1E Cards

Limitations and Restrictions for 2.1.x

General Limitations, Restrictions, and Notes

Limitations for rteopt via parallel links

Important Notes

APS Management Information

Preparing for Intercard APS

Managing Intercard APS Lines

Troubleshooting APS Lines

Installation and Upgrade Procedures

Upgrade Information

Maintenance Information

Upgrade Limitations

Frame Discard

Documentation

Changes to this Document

Notes

Related Documentation

Cisco WAN Manager Release 12

Cisco MGX 8850 (PXM45) Multiservice Switch Release 4

Cisco MGX 8850 (PXM1E) Multiservice Switch Release 4

Cisco MGX 8950 Multiservice Service Release 4

SES PNNI Release 4

Cisco MGX 8830 Multiservice Switch Release 4

Cisco WAN Switching Software Release 9.4

MGX 8850 (PXM1) Edge Concentrator Release 1.2.20

MGX 8250 Edge Concentrator Release 1.2.20

MGX 8230 Edge Concentrator Release 1.2.20

How to Find Multiservice Switch Customer Documents Online

If the Part Number is Known

If the Part Number is Not Known

Ordering Documentation

Documentation on the World Wide Web

Documentation CD-ROM

Documentation Feedback

Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Caveats

MGX 8850, MGX 8830, and MGX 8950 4.0.12 Anomalies

Known Anomalies in Release 4.0.12

Anomalies Resolved in Release 4.0.12

Anomaly Status Change from Previous Release

MGX 8850, MGX 8830, and MGX 8950 4.0.11 Anomalies

Anomalies Resolved in Release 4.0.11

MGX 8850, MGX 8830, and MGX 8950 4.0.10 Anomalies

Anomalies Resolved in Release 4.0.10

Known Route Processor Module or MPLS Anomalies

MGX-RPM-XF-512 Anomalies

Acronyms


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

Contents

About Release 4.0.12

These release notes describes the system requirements, new features, and limitations that apply to Release 4.0.12 of the MGX 8850, MGX 8950, and MGX 8830 multiservice switches. These notes also contain Cisco support information.

These release notes complement the technical manuals listed in the "Related Documentation" section.

Note Release notes for MGX 8950, Release 4.0.12, are combined with these release notes. A new section that describes how these release notes change with each revision appears in the "Changes to this Document" section.

Type of Release

Release 4.0.12 is a software release for the following MGX switches:

•MGX 8830 PNNI routing switch

•MGX 8850 (PXM1E)

•MGX 8850 (PXM45)

•MGX 8950

Locating Software Updates

This is the location for the MGX 8850(PXM45/PXM1E), MGX 8830, and MGX 8950 4.0.12 software:

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

New Features and Enhancements in Release 4.0.12

Point-to-Multipoint Support on AXSM-E

Multicast support on AXSM-E provides a non-branching multicast (single leaf) support in the egress direction. In egress direction, the leaf connection can be a "via" connection or a terminating connection.

This multicast connection cannot branch into multiple leaves in the egress direction on the AXSM-E card. Also, it cannot branch on any other AXSM-E in the node. In addition, the leaf connection on AXSM-E should be the first leaf on that multicast connection. Otherwise it will remain in "fail" state until it is the only remaining leaf on the node for that multicast connection.

AXSM-A/B Multicast Support

Crossbar handling of requests from broadband service modules:

The crossbar is configured for `Unicast preferred' implying that it will honor requests from the service modules in the following order (for a specific destination slot):

•"Unicast Primary w/ speedup" (not supported on AXSM-A)

•"Multicast Primary w/ speedup" (not supported on AXSM-A)

•"Unicast Primary" (supported on AXSM-A/B)

•"Multicast Primary" (supported on AXSM-A/B)

•"Unicast Secondary" (supported on AXSM-A/B)

Broadband Service module request generation:

The service modules can generate two types of requests (primary and secondary) for unicast traffic based on the number of switch planes and number of cells in the input queue. And the service modules can generate one "Unicast Primary" and multiple "Unicast secondary" requests at any point of time (every S-Tick).

AXSM-A cards:

•Does not support priority (speedup) requests towards crossbar for neither unicast/multicast.

•Is configured for unicast preferred - gives preference to unicast traffic over multicast traffic

•All multicast requests are primary requests. Unicast requests can be both primary as well as secondary

AXSM-B cards:

•Support priority (speedup) requests towards crossbar for both unicast and multicast.

•Is configured for unicast preferred - gives preference to unicast traffic over multicast traffic.

•All multicast requests are primary requests. Unicast requests can be both primary as well as secondary

Limitations in AXSM-A involving multicast traffic:

For example, suppose the source card has 8 cells in the queue for the same destination and switch is made of 4 switch planes, the source card will generate one "Unicast Primary" and 3 "Unicast secondary" requests. For multicast traffic there is no secondary request, all multicast requests are primary only. There could be a scenario where multiple source cards are trying to send both "Unicast" and "multicast" traffic to the same (congested) destination. In that case one source card's "Multicast primary" request can win over the other source cards "Unicast secondary requests". Traffic from only one source card to the same destination will not be an issue as the card gives priority to unicast traffic. 

Example 1

Card A is sending OC48 CBR unicast traffic to Card B.

Card C is sending OC24 UBR multicasttraffic to Card B.

Result: Card A will see some ingress discards. But the same behavior is true for unicast

to unicast traffic as well. (AXSM-A only)


Example 2

Card A is sending OC24 CBR multicast traffic to Card B.

Card C is sending OC48 UBR unicast traffic to Card B.

Card D is sending OC48 UBR unicast traffic to Card B.

Result: Card A will see some ingress discards. Same can happen on unicast as well.

(AXSM-A only).

Limitations of both AXSM-A and AXSM/B

Both AXSM-A/B have 32-cell queue in egress replication engine. This queue can easily over-run if the multicast traffic fed to this is bursty in nature. Bursty traffic could originate either from one source or from multiple separate multicast sessions.

Frame Discard Feature

New developments have occurred in the CLI for the Frame Discard feature in connection provisioning. Starting with releases 3.0.23 and 4.0.10, two types of frame discard became available. For a detailed explanation, see the addcon or cnfcon description in either the Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and Cisco MGX 8950 Command Reference (Release 3 or 4) or the Cisco ATM Services (AXSM) Software Configuration Guide and Command Reference for MGX Switches (Release 3 or 4). Also see the Note in the Installation and Upgrade section of these release notes.

New Features and Enhancements in Release 4.0.11

None.

Features and Enhancements in Previous Release 4.0.10

The new features in Release 4.0.10 are listed in Table 1.

Table 1 New Features in Release 4.0.10

New Release 4.0.10 Feature
MGX 8850 PXM45(A)
MGX 8850 PXM45/B
MGX 8850
PXM45/C
MGX 8950
MGX 8850 (PXM1E)
MGX 8830

LMI AutoSense

YES

YES

YES

NA

YES

YES

Resource Monitoring

YES

YES

YES

YES

YES

YES

Add Channel Loopback on AXSM-E

YES

YES

YES

NA

NA

NA

Service Module Hot Core Dump

YES1 (

YES1

YES1

YES

NO

NO

Active PXM Freeze Detection and Recovery

YES

YES

YES

YES

NO

NO

Improved SCM Polling Diagnostics on Active and Standby PXM

YES

YES

YES

YES

YES

YES

MGX-FRSM-HS2/B

NA

YES

YES

NO

YES

YES

MGX-FRSM-2T3E3

NO

YES

YES

NO

YES

YES

AXSM/B Feeder Support

YES

YES

YES

YES2

NA

NA

1 Except for Cell Bus Service Module

2 Already supported on MGX 8850 (PXM45) and new on MGX 8950


LMI AutoSense

The LMI AutoSense feature on the Frame Relay Cards on MGX switches enables a frame relay port to detect the LMI type supported by the frame relay CPE (customer premise equipment). This autosensing feature avoids the need to configure the LMI type on each frame relay port.on the FRSM-8T1/E1 and FRSM-VHS (2CT3, 2T3, 2E3, 2HS2B) cards on PXM1/(PXM45A/B/C)/PXM1E platforms.

The LMI AutoSense feature is supported for Frame Relay and FUNI port types. It is not applicable for Frame Forwarding port types. The detected LMI types will be of the following UNI types:

•AnnexD-UNI

•AnnexA-UNI

•StrataLMI

The LMI AutoSense feature is not supported on NNI interfaces.

The LMI AutoSense feature is configurable at a per port level.

A new MIB variable portLmiSigConfMethod has been added to the existing frPortCnfSigLMIGrpTable MIB table.

The addport, cnfport, xcnfport and dspport CLI commands have been modified to configure/display the new portLmiSigConfMethod MIB variable.

addport

One more parameter lmi_autosense will be added to the addport CLI, which can be optionally specified by the user while adding the port. By default the value will be set to Manual(1).

If the user wants to configure the port for LMI AutoSense, the user needs to set the lmi_autosense parameter value to AutoSense(2) while adding the port using addport.

The addport command syntax for the cards will thus be modified to as shown below

FRSM-8P and FRSM-2CT3.

Syntax:

addport "port_num line_num ds0_speed begin_slot num_slot port_type [lmi_autosense]"

where lmi_autosense can be configured for either mode Manual(1) or AutoSense(2)

FRSM-2T3, FRSM-2E3, FRSM-HS2B.

Syntax:

addport "port_num line_num port_type [lmi_autosense]"

xcnfport

One more parameter "-lmias" has been added to the xcnfport CLI, which can be specified while either adding the port or modifying the port using xcnfport. By default the value is set to Manual(1).

To configure the port for LMI autosense set the "-lmias" parameter value to AutoSense(2) while adding/modifying the port using xcnfport. At the same time, set the port signalling protocol type to noSignalling using the "-sig" option.

The xcnfport command syntax for the cards has been modified as shown below.

Syntax:

xcnfport "-pt <PortNum> -ln <PortLineNum> -en <PortEnable> -rat <PortEqueueServiceRatio> -flag <PortFlagsBetweenFrames> -asy <AsynchMsg> -t391 <T391Timer> -t392 <T392Timer> -n391 <N391Counter> -n392 <N392Counter> -n393 <N393Counter> -enhancedLmi <enhancedLmi> -pta <portAdmin> -svcen <portSvcStatus> -svcuse <portSvcInUse> -pbe <portBertEnable> -m32eqth <EgressQueueThreshold> -lmias <lmi autosense>"

where -lmias <lmi_autosense> can be set to either 1 for Manual or 2 for Autosense.

cnfport

One more parameter lmi_autosense has been added to the cnfport CLI, which can be specified while modifying the port. By default the value is set to Manual(1).

To configure the port for LMI autosense, set the lmi_autosense parameter value to AutoSense(2) and lmiSig to noSignalling while using cnfport.

The cnfport command syntax for the cards has been modified to as shown below:

Syntax:

cnfport "portNum lmiSig asyn ELMI T391 T392 N391 N392 N393 [lmi_autosense]"

where [lmi_autosense] can be set to either 1 for Manual or 2 for AutoSense.

dspport

The existing CLI dspport will be enhanced to display the value of the new MIB variable. The display of this new variable portLmiSigConfMethod will be added between the display of PortSpeed and SignallingProtocolType.

Example: 

node.1.4.VHSHS2.a > dspport 1

    SlotNum:                      		4

    PortLineNum:                  		1

    PortNum:                      		1

    PortRowStatus:                		Add

    PortDs0Speed:                 		notUsed

    PortDs0ConfigBitMap(1stDS0):  		0xffffff(1)

    PortEqueueServiceRatio:       		n/a

    PortFlagsBetweenFrames:       		0

    PortSpeed:                    		51840 kbps

    portLmiSigConfMethod:         				Manual

    SignallingProtocolType:       		NoSignalling

    AsynchronousMsgs:             		UPD_UFS disabled

    T391LineIntegrityTimer:       		10 sec

    T392PollingVerificationTimer: 		15 sec

    N391FullStatusPollingCounter: 		6

    N392ErrorThreshold:           		3

    N393MonitoredEventCount:      		4

    EnhancedLmi:                  		Off

    PortState:                    		FailedDuetoLineFailure

    PortSignallingState:          		No Signalling Failure

    CLLMEnableStatus:             		Disable

    CLLMxmtStatusTimer:           		40 ms

    portType:                     		frameRelay

    portEnhancedSIW:              		Disable

    PortIngrPercentUtil:          		0

    PortEgrPercentUtil:           		0

    PortOversubscribed:           		False

    PortSvcStatus:                		Disable

    PortSvcInUse:                 		Not In-Use

    PortSvcShareLcn:              		Card-based

    PortSvcLcnLow:                		0

    PortSvcLcnHigh:               		0

    PortSvcDlciLow:               		0

    PortSvcDlciHigh:              		0

    PortNumNextAvailable:         		2

Resource Monitoring

The feature Resource Monitoring periodically checks the switch resources and takes appropriate actions when either there is a resource shortage or recovery happens. The resources monitored are:

•Memory (all SSI partitions and VxWorks(TM) partition)

•Hard Disk space

•IPC buffers

•CPU

•SSI Sync Timers

•SSI File Descriptors

•VxWorks file descriptors

•System up time

The action includes:

•Alarm

•Trap

•Log

The following are new CLIs for the feature:

•cnfrmrsrc: Configure resource monitoring behavior

•dsprmrsrc: display particular resource information in detail

•dsprmrsrcs: display all the resources in summary

•dsprmalms: display resource related alarms

The following are modification on existing CLI:

•dspcdalm: add resource monitoring category

Platforms

The feature is supported on:

•MGX 8850 (PXM1E, PXM45, AXSM, AXSM-E, FRSM12)

•MGX 8950 (PXM45, AXSM/B, AXSM-XG)

•MGX8830 (PXM1E)

Add Channel Loopback on AXSM-E (PER 3854)

Currently, the addchanloop CLI command on the AXSM-E card offers the local and remote loop option. This would make it consistent with the addchanloop command on the AXSM/B Card.

The local (egress) loop option of addchanloop has been added on the AXSM-E. Special handling is involved where the SABRE chip handles the egress loopback instead of the ATLAS chip.

dspchancnt is supported on the loopback connection.

Limitations:

• OAM and RM cells cannot be looped back, only data cells can be looped.

• All OAM functions will not work on the loopback connections.

• The QE is disabled in the egress direction when the sabre is looped back, so there will be discards at the egress QE; the data cells are actually being looped back through SABRE.

• During the loopback, special loopback LCNs are used. The normal connection LCN will be disabled at that time.

• There are 8 loopback LCNs per card, so only 8 connections can be looped back at a time.This includes ingress and egress loopbacks.

• The users cannot enable remote and local channel loopback at the same time on the same channel.

Platforms

The feature is supported on:

•MGX 8850(AXSM-E)

Service Module Core Hot Dump

In order to ease debugging of either memory leak or memory corruption on service module (SM) cards, core hot dump feature provides the functionality of initiating core hot dump through CLI command of "core hot-dump <file.zip>" on SM. The feature is available on the following service modules:

•AXSM

•AXSM-E

• AXSM-XG

•FRSM12

CBSM (Cell Bus Service Module) is not supported by this feature. Only one SM slot can execute core hot dump at one time. The core hot dump will not cause SM card to reset. The feature can be executed on active and standby SM cards. Each SM slot performing core hot dump will have a core hot dump zip file saved on the active PXM hard disk "C:/" directory. The user can ftp the zipped core file to a their workstation and use a GDB debugger to analyze the core file to analyze the problems. At the PXM CLI prompt, the user can check SM core hot dump status by using the CLI command "core dump-status". The CLI shows slots that are in the process of core hot dump.

Platforms

The feature is supported on:

•MGX 8850 (AXSM/B, AXSM-E, FRSM12)

•MGX8950 (AXSM/B, AXSM-XG)

Active PXM Freeze Detection and Recovery (PER 7869)

The standby PXM monitors the SCM polls coming from the Active PXM. If the standby PXM detects a missing Poll, it waits for configurable maximum consecutive missing polls (Default 13 polls: 19.5 Seconds) and then takes over the mastership and resets the Active PXM.

To ensure the Standby PXM does not reset the Active in case of local SCM path failure, the Active PXM detects the missing Poll responses. It resets the standby PXM (or any Service Module) in configurable consecutive missing poll responses(10 Polls: 15 Seconds recommended).

This feature is not enabled by default on PXM cards. The feature has to be enabled on the Active PXM and the values for MaximumPoll counts from Active and Standby must be configured also.The default value for the standby PXM maximum missing poll before it declares active frozen is 13 counts(19.5 sec) and the default value for the Active PXM maximum poll retries is 9 polls(+1 failure before retries).

Platforms

The feature is supported on:

•MGX 8850(PXM45)

•MGX 8950

Improved SCM Polling Diagnostics on Active and StandBy PXM

The feature is an enhancement in SCM for improving the debugging ability for SCM Poll / RPM heartbeat failures. SCM has a mechanism of monitoring card's health by sending Poll messages (Additionally Heartbeat in RPM). SCM declares a card dead after a certain number of responses are not received and reports the error to Shelf Manager which in turn will reset the Service Module. Currently, there is no debugging information either logged or stored once the card resets. The feature has the capability of storing more information in case of card failure for easier debugging. The possible cause of an SCM Poll/Heartbeat failure could be Failure in the communication path, Failure of the channel on which the Poll/Heartbeat is sent, and Failure on the Service Module. A new mechanism introduced in SCM collects the relevant data for improving failure analysis. A minimum number of failure of Poll/Heartbeat threshold (50% of Maximum Poll Retry limit) would be used to trigger the collection of data from SAR, QE and CBC on the PXM side.

Platforms

The feature is supported on:

•MGX8850(PXM45, PXM1E)

•MGX8950

•MGX8830

Cell Bus Service Module on PXM-45 (Expanded from MGX 4.0.00 Release)

MGX-FRSM-2T3E3 and MGX-FRSM-HS2/B have been added to the list of Cell Bus Service Modules supported on the PXM45/B and PXM45/C.

Platform

The feature is supported on:

•MGX 8850 (PXM45/B, PXM45/C)

AXSM/B as Feeder Uplink on MGX 8950

Previously supported only on the MGX 8850-PXM45, the feeder upstream capability will now be supported on the MGX 8950 as well. This feature enables PXM-1 feeder nodes to be directly connected to the AXSM/B cards on MGX 8950 nodes.

Platforms

The feature is supported on:

•MGX 8950

Features and Enhancements in Previous Release 4.0.00

Note Cell bus service modules (CBSMs) were formerly called narrow band service modules (NBSMs). As the MGX product line has grown, the narrow band distinction is no longer appropriate. CBSMs use the MGX cell bus for customer traffic instead of the serial bus used by cards such as AXSM and FRSM-12-T3E3.

Refer to the "Acronyms" section for definitions of acronyms used in these release notes.

Release 4.0.00 contains the following new features:

Table 2 lists which switch supports which new feature.

Table 2 MGX Release 4.0.00 Feature Support by Switch 

New Release 4.0.00 Feature
MGX 8850 PXM45(A)
MGX 8850 PXM45/B
MGX 8850
PXM45/C
MGX 8950
MGX 8850 (PXM1E)
MGX 8830

Closed User Groups (CUG)

YES*

YES

YES

YES

YES

YES

Preferred routes for PNNI Multipeer Group Networks

YES

YES

YES

YES

YES

YES

Point to Multipoint SVC/SPVC support (P2MP)

NO

YES

YES

YES

YES

YES

Increased number of Signaling Interfaces

NO

YES

YES

YES

N/A

N/A

Virtual trunks support in PXM1E

NO

NO

NO

NO

YES

YES

Virtual UNI support in PXM1E

N/A

N/A

N/A

NO

YES

YES

PXM1E as Upstream to Feeder Nodes

N/A

N/A

N/A

NO

YES

YES

AXSM-E Upstream to Feeder Nodes

NO

YES

YES

NO

NO

NO

Cell Bus on PXM451

NO

YES

YES

NO

NO

NO

Additional Narrow Band on PXM1E

N/A

N/A

N/A

NO

YES

YES

AXSM-32-T1E1-E UNI with IMA

NO

YES

YES

NO

N/A

N/A

PXM1E-16-T1E1 UNI with IMA

N/A

N/A

N/A

NO

YES

YES

PXM1E-8-155

N/A

N/A

N/A

N/A

YES

YES

PXM45/C

NO

NO

YES

YES

NO

NO

AXSM-1-9953-XG

NO

NO

NO

YES

NO

NO

AXSM-4-2488-XG

NO

NO

NO

YES

NO

NO

1 Please refer to the CBSM matrix (Table 2) for details.

1 * Closed User Groups is support on PXM45(A) in Release 4.0.10.


Closed User Groups

The Closed User Groups (CUG) supplementary service enables network users to form groups, to and from which access is restricted. A network user may be associated with one CUG, multiple CUGs, or no CUG. Members of a specific CUG can communicate typically among themselves, but in general not with network users outside of the CUG. Specific network users can have additional restrictions preventing them from originating calls to, or receiving calls from, network users of the same CUG (Outgoing Calls Blocked or Incoming Calls Blocked). In addition, a network user can be further restricted in originating calls to, or receiving calls from, network users outside of any CUG membership defined for the network user (Outgoing Access or Incoming Access.).

The feature is based on the ITU-T Q.2955.1 recommendation.

Platforms

The feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

References

ITU-T Q.2955.1

Preferred Routes for PNNI Multipeer Group Networks

Preferred routing of connections provides the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route is one which will follow the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route is one which will follow only the configured path; if the configured path is not available, the connection will remain unrouted.

Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8850 (PXM1E)

•MGX 8830

•MGX 8950

References

PNNI 1.1

Point-to-Multipoint SVC/SPVC Support

The SVC/SPVC point-to-multipoint (P2MP) feature offers the ability for one root SVC/SPVC connection to establish a simple tree topology to one or more leaf connections. The data traffic is uni-directional from root multicast to all leaves, i.e., what is sent from the root data channel is received by all leaves. From the root, leaves can be added to the connection using SETUP/ADD_PARTY signaling messages. Point-to-multipoint is a mandatory feature described in UNI 3.0, UNI3.1 and UNI4.0 specs. The implementation is compliant with in Q2971.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•AXSM/B on MGX 8950

•AXSM/B on MGX 8850 (PXM45)

Note AXSM/B support is limited due to the capability of the hardware. P2MP connections and throughput are limited.

References

UNI 3.0, UNI3.1, UNI4.0, Q2971

Increased Number of Signaling Interfaces

Support for up to 192 PNNI routing/signaling interfaces on MGX 8850 (PXM45/B and PXM45/C). Prior to this release, the platform supports only 99 signaling interfaces. The features enables increased signaling interfaces for interconnecting with other switches or DSLAMs.

Platforms

This feature is supported on:

•MGX 8850 (PXM45)

•MGX 8950

PXM1E-Related Hardware (the PXM1E-8-155 card)

•8-port OC3/STM1and MCC-8-155

•Continues to support existing PXM1 features

•PXM1E 8-port OC3/STM1 will require the UI-S3/B back card

•PXM1E-8-155, new 8-port OC3/STM1 back card with the SFP and MCC-8-155 support.

Redundancy Support

The PXM1E PNNI Controller offers redundancy, offer hitless operation, and Y-Redundancy (1:1) will be supported in PXM1E for the 155 interface.

Service Modules will have 1:N redundancy and 1:1 redundancy as supported by the individual service modules

Automatic Protection Switching Support

Automatic Protection Switching (APS) 1:1 and1+1 for both the Bellcore GR-253 and ITU-T G.783 Annex-A and Annex-B standards will be supported for the OC3 and STM1 interfaces. The MGX-8850-APS-CON plane is required for APS functionality.

Modular Transceiver Support in the New 8-port OC3/STM1 Back Card

The PXM1E will support a single universal back card capable of supporting single-mode and multi-mode fiber connectors for the different reaches in OC3 and STM1.

External field-replaceable transceivers for SMF-IR, SMF-LR and MMF, purchased by the customer, will be supported.

UNI connection support in PXM1E-16-T1E1

In a previous software release (3.0.10), the PXM1E-16-T1E1 card provided support for IMA trunking. In the MGX 4.0.00 release, the same card will support both native ATM UNI and IMA UNI endpoints. Sixteen T1/E1 ports can be mixed and matched for either native UNI or NNI ports and IMA UNI or NNI ports.

ATM Routing in PXM1E

The PXM1E-based switches support the ATM Forum standard PNNI routing/signaling based on the same baseline used for MGX 8850 (PXM45) and BPX/SES systems. It can be a peer to the PXM45-based switches in the single peer group and participate in multipeer groups.

Connection Management

Supports different types of connections—SVC, SVP, S-PVC, and S-PVP. UNI 3.X/4.0 signaling and ILMI are used to setup SVCs and SVPs.

PXM1E will support 13,500 local switching connections and 27,000 routed connections.

Cell Bus Service Module Support

A cell bus service module is an MGX service module that uses the MGX cell bus to transport customer traffic between that service module and other services modules or PXM uplinks. Traditionally, the CBSMs were called narrow band service modules (NBSMs).

For a summary of service modules supported in MGX 8830 and MGX 8850 (PXM1E), please refer to Table 2.

Virtual Trunks Support in PXM1E

Virtual trunks will be supported in the PXM1E ports. A maximum of 31 (physical and virtual) trunks can be supported in a PXM1E card. The feature will be supported in 4-port OC3/STM1, 8-port T3/E3, 8-port OC3/STM1, 16- port T1/E1 and the combo PXM1E cards. SVC, SPVC and SPVP connections can be routed over the virtual trunks.Virtual trunks can originate and terminate between PXM1E, AXSM/A, AXSM/B, AXSM-XG and AXSM-E cards.

Virtual UNI Support in PXM1E

A new port type called Virtual UNI (VUNI) and Enhanced Virtual UNI(EVUNI) is defined in addition to the already defined port types UNI, NNI, VNNI (Virtual Trunk). This feature benefits both the MPLS and PNNI control plane.

Feeder Trunk support in PXM1E

PXM1E ports can accept feeder trunks in any port. IGX 8400, MGX 8230, MGX 8250 and MGX 8850 (PXM1) can be added as feeders to MGX 8830 and MGX 8850 (PXM1E).

PXM1E Diagnostics

Both HMM and online diagnostics report alarms in the Hardware Alarm category under the card alarms.

•HMM reports alarms for all devices when error thresholds are crossed. Further information can be obtained via the CLI dspdeverr <device>. This CLI will have to be issued for each device to ensure that all relevant errors have been observed. The alarm raised by the specific instance of the device (for example, QE1210 - 0 or 1) will also be available in the dspdeverr CLI.

•The CLI dspdiagerr online indicates whether there is error reported by online diagnostics. Further information regarding the error can be obtained from the event logs via a filter using CLI dsplog -mod PXMD.

POST test results printed to the console immediately after execution may display failures. These may be due to tests being attempted for devices not present on the particular PXM1E-board (such as the second ATM policing device on the PXM1E-4-155). The tests are based purely on device offsets and can display spurious results. To confirm/rule-out real and relevant tests, please use the following examples:

Example 1 PXM1E-4-155: ATM policing device 2 and framers 2 and 4 do not exist: Following shows all relevant test cases passed. Although framers 2 and 4 show passed below, those two cases must be ignored. 

         Power On Self Test Results

Test Name                 Result     Description

BRAM Checksum             PASS

QE Ram                    PASS

CBC Ram                   PASS

Ethernet Reg              PASS

PCI-IDE Reg               PASS

Clock Mux                 PASS

Framer 1 Access           PASS

Framer 2 Access           PASS

Framer 3 Access           PASS

Framer 4 Access           PASS

ATLAS 1 Ram               PASS

ATLAS 2 Ram               FAIL       Ingress SRAM: Pattern Not Matched

Hard Disk Access          PASS

Example 2 PXM1E-8-T3E3: ATM policing device 2 and framers 3 and 4 do not exist: Following shows all relevant test cases passed. 

         Power On Self Test Results

Test Name                 Result     Description

BRAM Checksum             PASS

QE Ram                    PASS

CBC Ram                   PASS

Ethernet Reg              PASS

PCI-IDE Reg               PASS

Clock Mux                 PASS

Framer 1 Access           PASS

Framer 2 Access           PASS

Framer 3 Access           FAIL       Framer 3 Access 1 Fail

Framer 4 Access           FAIL       Framer 4 Access 1 Fail

ATLAS 1 Ram               PASS

ATLAS 2 Ram               FAIL       Ingress SRAM: Pattern Not Matched

Hard Disk Access          PASS

Example 3 PXM1E-T3E3-155: Following shows all relevant test cases passed. 

         Power On Self Test Results

Test Name                 Result     Description

BRAM Checksum             PASS

QE Ram                    PASS

CBC Ram                   PASS

Ethernet Reg              PASS

PCI-IDE Reg               PASS

Clock Mux                 PASS

Framer 1 Access           PASS

Framer 2 Access           PASS

Framer 3 Access           PASS

Framer 4 Access           PASS

ATLAS 1 Ram               PASS

ATLAS 2 Ram               PASS

Hard Disk Access          PASS

Example 4 PXM1E-8-155: Following shows all relevant test cases passed. For the 8OC3, the ethernet controller test is not done, since the controller is part of the system controller which is not tested in this release. 

         Power On Self Test Results

Test Name                 Result     Description

BRAM Checksum             PASS

QE Ram                    PASS

CBC Ram                   PASS

Ethernet Reg              NOT_DONE   Ethernet Controller Test Not Required.

PCI-IDE Reg               PASS

Clock Mux                 PASS

Framer 1 Access           PASS

Framer 2 Access           PASS

Framer 3 Access           PASS

Framer 4 Access           PASS

ATLAS 1 Ram               PASS

ATLAS 2 Ram               PASS

Hard Disk Access          PASS

Example 5 PXM1E-16-T1E1: ATM policing device 2 and framers 1,2,3 and 4 do not exist: Following shows all relevant test cases passed. 

         Power On Self Test Results

Test Name                 Result     Description

BRAM Checksum             PASS

QE Ram                    PASS

CBC Ram                   PASS

Ethernet Reg              PASS

PCI-IDE Reg               PASS

Clock Mux                 PASS

Framer 1 Access           FAIL       Framer 1 Access 1 Fail

Framer 2 Access           FAIL       Framer 2 Access 1 Fail

Framer 3 Access           FAIL       Framer 3 Access 1 Fail

Framer 4 Access           FAIL       Framer 4 Access 1 Fail

ATLAS 1 Ram               PASS

ATLAS 2 Ram               FAIL       Ingress SRAM: Pattern Not Matched

Hard Disk Access          PASS

AXSM-E as Upstream to Feeder Nodes

Previously supported only with AXSM and AXSM/B cards, the feeder upstream capability will now be supported using the AXSM-E card as well. This feature enables PXM1 and IGX 8400 feeder nodes to be directly connected to the AXSM-E cards on the PXM45 nodes.

Platform

•MGX 8850 (PXM45)

Cell Bus Service Modules on PXM45

This feature allows key Cell Bus Service Modules to be supported on the MGX 8850 (PXM45). Where necessary, these cards can be used in conjunction with the SRME or SRM-3T3/C Service Resource Module for distribution and redundancy purposes. Please see Table 2 for details.

Platform

•MGX 8850 (PXM45)

Note Support for these Service Modules is already available on all PXM1 and PXM1E platforms.

Table 3 Cell Bus Service Modules (CBSMs) Supported in Release 4.0.00, 4.0.10, 4.0.11, and 4.0.12 

 
MGX 8850
MGX 8830
MGX 8950
Cell Bus Service Modules
PXM45(A)
PXM45/B
PXM45/C
PXM1E
PXM1E
PXM45B/C

MGX-AUSM-8T1/B

NO

NO

NO

YES

YES

NO

MGX-AUSM-8E1/B

NO

NO

NO

YES

YES

NO

AX-CESM-8T1

NO

YES1

YES 1

NO

NO

NO

MGX-CESM-8T1/B

NO

YES

YES

YES

YES

NO

AX-CESM-8E1

NO

YES

YES

YES

YES

NO

AX-FRSM-8T1 and AX-FRSM-8E1

NO

YES

YES

YES

YES

NO

AX-FRSM-8T1-C and AX-FRSM-8E1-C

NO

YES

YES

YES

YES

NO

MGX-FRSM-2CT3

NO

YES

YES

YES

YES

NO

MGX-FRSM-2T3E3

NO

YES

YES2

YES

YES

NO

AX-FRSM-HS1

NO

NO

NO

NO

NO

NO

AX-FRSM-HS2

NO

NO

NO

NO

NO

NO

MGX-FRSM-HS2/B

NA

YES

YES2

YES

YES

NO

MGX-SRME

YES3

YES

YES

YES

YES

NO

MGX-SRM-3T3/C

NO

YES

YES

YES

YES

NO

MGX-VISM-8T1 and MGX-VISM-8E1 *

YES

YES

YES

NO

NO

NO

MGX-VISM-PR-8T1 and MGX-VISM-PR-8E1 *

YES

YES

YES

YES

YES

NO

1 For better performance, we encourage you to use MGX-CESM-8T1/B on nodes with PXM45/B and PXM45/C processor/ controller cards

2 New and supported in release 4.0.10

3 APS is not supported for SRME on PXM45(A).


AXSM-32-T1E1-E UNI with IMA

This feature allows the AXSM-32-T1E1-E to support the IMA capability on a UNI, VUNI, and EVUNI interface. This is in addition to the IMA trunking feature already supported in a previous release.

Platforms

•MGX 8850 (PXM45)

PXM45/C

The PXM45/C is a combination ATM switching fabric/processor card. The switching fabric provides 45 Gbps of non-blocking switching capacity, while the processor provides the control plane that delivers ATM networking software, diagnostics, and performance monitoring.

Platforms

•MGX 8850 (PXM45)

•MGX 8950

AXSM-1-9953-XG

The AXSM-1-9953-XG ATM Switch Service Module is a high-density, double-height Service Module for use in the Cisco MGX 8950 Next Generation Multiservice Switch in combination with the high-capacity PXM45 processor switching module and the XM-60 switching module, to deliver OC-192c/STM-64 trunk connectivity.

Up to 12 AXSM-XG service modules can be accommodated in the Cisco MGX 8950.

Platforms

•MGX 8950

AXSM-4-2488-XG

The AXSM-4-2488-XG ATM Switch Service Module is a Quad OC-48/STM-16, double-height service module for use in the Cisco MGX 8950 Next Generation Multiservice Switch. Used in combination with the high-capacity PXM45 processor and the XM-60 switching module it delivers high density connectivity of 4 interfaces of OC-48/STM-16, either in a clear-channel format or as channelized to OC-12/STM-4, OC-3/STM-1, and DS-3.

Up to 12 AXSM-4-2488-XG service modules can reside in the Cisco MGX 8950, to provide up to 48 OC-48/STM-16 interfaces to support service providers that require both high bandwidth and highest network availability. When used in the channelized mode, each service module can carry alternatively up to 64 DS-3 channels, 64 OC-3/STM-1 channels, 16 OC-12/STM-4 channels, or any combination of these 3 types adding up to 64 channels.

Platforms

•MGX 8950

Enhancements

The product enhancement requests (PERs) in Table 4 were introduced in Release 4.0.00.

Table 4 Product Enhancement Requests in Release 4.0.00 

Enhancement Number or Description
Purpose

AUSM CAC based on SCR
1822

This enhancement is for the PXM and the AUSM 8T1E1 cards.As part of this feature an option is provided to the customer per card to select the CAC feature. The option available is SCR based CAC or PCR based.

Scaling to 1 to 2 million connections
1820

The purpose of this enhancement is to introduce several concepts:

1. Global Transaction ID that will be maintained per SM. (AXSM/AXSM-E/AXSM-XG/PXM1E/SES). This will be used by the CWM to check if its db is in sync with that of the switch.

2. Static Connection File will be pre-created by the switch depending that are rules dependent. This will eliminate the need for CWM to wait for file creation and can be directly FTP'ed from the switch.

3. Incremental File that will only contain data necessary for CWM to sync up. CWM will specify the Transaction ID that it is in sync with and the switch will only provide connection data from the same Transaction ID. This will eliminate returning back data that is not needed by CWM.

Persistent Topology
2291

Purpose of this feature is to enable the CWM to maintain a persistent topology information of the entire network. One or more nodes will be designated as gateway nodes. Whenever CWM needs info about the network, it will query gateway nodes to collect the necessary information.

Preferred Route including MPG
2489, 3383

Preferred routing of connections provide the network operator a means of bypassing the PNNI route selection, and configuring a specific path through the network which a connection will follow. Preferred routes can be configured as either Preferred or Directed routes. A Preferred route follows the configured path if available, but will revert to a PNNI-selected route if the preferred route is not available. A Directed route follows only the configured path; if the configured path is not available, the connection remains unrouted.

Preferred routes can be specified for SPVCs from source switch to the destination switch end-to-end using CLI or SNMP. The end-to-end preferred route for connections can span across multiple peer groups. The implementation is based on PNNI 1.1 specification.

Display Hot Standby for AXSME and AXSM-XG
2834

When the CLI command is given on a Standby AXSM or AXSME, for the verification of the persistent information, it reads the information from the Active PXM disk and compares with the configuration in its RAM. First, the number of records for each type of configuration will be compared. Then, the record data itself will be compared for each existing record. It displays any discrepancies on the terminal. In the case of non-persistent information, the Standby AXSM or AXSME obtains the non-persistent information from its active peer and compares it with what it has in its RAM. It displays any discrepancies on the terminal.

Additional CBSM Stats
2965

Additional CBSM stats for FRSM Port/PVC and AUSM.

Reroute speed increase using PXM45/C
3726

Doubling connection reroutes-per-second rate on MGX.

Larger Stat Counters via AXSM-XG
3727

AXSM-XG supports 64 bit stats.

Narrow Band Service Modules on PXM45
3733

Narrowband Service Module support on MGX 8850 PXM45.