5.0.00 Release Notes for Cisco MGX 8880 Media Gateway [Cisco MGX 8880 Media Gateways]

Table Of Contents

Release Notes for Cisco MGX 8880 Software Version 5.0.00

Contents

About Release 5.0.00

Type of Release

Locating Software Updates

Service Class Template (SCT) File Information

AXSM/B

AXSM-E

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

SNMP MIB Release

Hardware Supported

Hardware in Release 5.0.00

MGX 8880 Product IDs and Card Types

Command Reference

Limitations, Restrictions, and Notes for 5.0.00

Higher Level Logical Link Limits

AXSM-32-T1E1-E

AXSM-E OAM

CLI Configurable Access

Serial Bus Path Fault Isolation

Disk Space Maintenance

clrsmcnf Command

APS

Path and Connection Trace

Priority Routing

SPVC Interop

Manual Clocking

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 Card

Caveats

Known MGX 8880 Media Gateway Anomalies

Known Route Processor Module or MPLS Anomalies

MGX-RPM-XF-512 and MGX-RPM-PR-512 Anomalies

Documentation

Documentation Notes for the April 2004 Product Releases

Related Documentation

Technical Manual Order of Use

Technical Manual Titles and Descriptions

Obtaining Documentation

Cisco.com

Ordering Documentation

Finding Documentation for Cisco MGX, BPX, SES, and CWM Products

Documentation Feedback

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 8880 Software Version 5.0.00

Contents

About Release 5.0.00

These release notes describes the system requirements, new features, and limitations that apply to Release 5.0.00 of the MGX 8880, Media Gateway. These notes also contain Cisco support information.

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

Type of Release

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

•MGX 8880

Locating Software Updates

This is the location for the MGX 8880 Media Gateway 5.0.00 software:

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

Service Class Template (SCT) File Information

This section contains SCT file information for Release 5.0.00.

AXSM/B

•SCT 2 - policing enabled, PNNI

•SCT 3 - policing disabled, PNNI

•SCT 4 - policing enabled, MPLS and PNNI

•SCT 5 - policing disabled, MPLS and PNNI

The check sum for the SCT files are as follows

•AXSM_SCT.PORT.2.V1: Check sum is = 0x78ccfb22= 2026699554

•AXSM_SCT.PORT.3.V1: Check sum is = 0x987919a7= 2558073255

•AXSM_SCT.PORT.4.V1: Check sum is = 0x775bfaa2= 2002516642

•AXSM_SCT.PORT.5.V1: Check sum is = 0xe84c696a= 3897321834

•AXSM_SCT.CARD.2.V1: Check sum is = 0x78ccfb22= 2026699554

•AXSM_SCT.CARD.3.V1: Check sum is = 0x987919a7= 2558073255

•AXSM_SCT.CARD.4.V1: Check sum is = 0x775bfaa2= 2002516642

•AXSM_SCT.CARD.5.V1: Check sum is = 0xe84c696a= 3897321834

A user can do dspsctchksum <filename> to confirm that the checksum of the Cisco-released SCT file and the file on the node match.

AXSM-E

These are the new AXSM-E SCT files:

•CARD and PORT SCT 4 - policing enabled for PNNI, disabled for MPLS

•CARD and PORT SCT 5 - policing enabled for PNNI, disabled for MPLS

•PORT SCT 6 - Policing disabled, used for PNNI ports.

•CARDand PORT SCT 52 - Policing enabled on PNNI, disabled on MPLS

•PORT SCT 53 - Policing disabled on PNNI and MPLS

•PORT SCT 54 - Policing enabled on PNNI, disabled on MPLS

•PORT SCT 55 - Policing disabled on PNNI and MPLS

The following are checksums for the new AXSM-E SCT file:

•AXSME_SCT.PORT.4.V1: Check sum is = 0x778eb096

•AXSME_SCT.CARD.4.V1: Check sum is = 0x778eb096

•AXSME_SCT.PORT.5.V1: Check sum is = 0x53c67945= 1405516101

•AXSME_SCT.CARD.5.V1: Check sum is = 0x53c67945= 1405516101

•AXSME_SCT.PORT.6.V1: Check sum is = 0xb69ce935= 3063736629

•AXSME_SCT.PORT.52.V1: Check sum is = 0x199550ec= 429215980

•AXSME_SCT.PORT.53.V1: Check sum is = 0xf6d53485= 4141167749

•AXSME_SCT.PORT.54.V1: Check sum is = 0x2a96b5b9= 714519993

•AXSME_SCT.PORT.55.V1: Check sum is = 0x5403c5ac= 1409533356

•AXSME_SCT.CARD.52.V1: Check sum is = 0xde496f2= 233084658

System Requirements

This section describes software compatible with this release, and lists the hardware supported in this release.

Software/Firmware Compatibility Matrix

Table 1 lists Cisco WAN or IOS products that are compatible with Release 5.0.00.

Table 1 MGX 5.0.00 Release Compatibility Matrix

Switch or Component

Compatible Software Version

MGX 8880 (PXM45/C)

MGX 5.0.00

VISM-PR

VISM 3.2.1

VISM 3.1.2

MGX 8880 (VXSM)

MGX 5.0.00

VXSM 5.0.00

IOS RPM-PR

12.3(2)T5

IOS RPM-XF

12.3(2)T5

MGX and RPM Software Version Compatibility Matrix

Table 2 lists the software that is compatible for use in a switch running Release 5.0.00 software.

Table 2 MGX and RPM Software Version Compatibility Matrix

Board Pair

Boot Software

Minimum

Boot Code

Version

Runtime Software

Latest

Firmware

Version

Minimum

Firmware

Version

PXM45/C

pxm45_005.000.000.200_bt.fw

5.0.00

pxm45_005.000.000.201_mgx.fw

5.0.00

5.0.00

AXSM-1-2488/B

axsm_005.000.000.200_bt.fw

5.0.00

axsm_005.000.000.201.fw

5.0.00

5.0.00

AXSM-16-155/B

AXSM-4-622/B

AXSM-16-T3/E3/B

AXSM-2-622-E

axsme_005.000.000.200_bt.fw

5.0.00

axsme_005.000.000.200.fw

5.0.00

5.0.00

AXSM-8-155-E

AXSM-16-T3E3-E

AXSM-32-T1E1-E

MGX-VXSM-155

MGX-VXSM-T1E1

vxsm_005.000.000.200_bt.fw

5.0.00

vxsm_005.000.000.200.fw

5.0.00

5.0.00

MGX-SRME/B

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

SRM-3T3/B

N/A (Obtains from PXM)

N/A

N/A (Obtains from PXM)

N/A

N/A

MGX-RPM-PR-512

rpm-boot-mz.123-2.T5

12.3(2)T5

rpm-js-mz.123-2.T5

12.3(2)T5

12.3(2)T5

MGX-RPM-XF-512

rpmxf-boot-mz.123-2.T5

12.3(2)T5

rpmxf-p12-mz.123-2.T5

12.3(2)T5

12.3(2)T5

MGX-VISM-PR-8T1

vism_8t1e1_VI8_BT_3.2.00.fw

3.2.0

vism_8t1e1_003.052.010.200.fw (CALEA image)

vism_8t1e1_003.002.010.200.fw (non-CALEA image)

3.52.10

3.2.10

3.52.10

3.2.10

MGX-VISM-PR-8E1

vism_8t1e1_VI8_BT_3.2.00.fw

3.2.0

vism_8t1e1_003.052.010.200.fw (CALEA image)

vism_8t1e1_003.002.010.200.fw (non-CALEA image)

3.52.10

3.2.10

3.52.10

3.2.10

Additional Notes

The following notes provide additional compatibility information for this release:

SNMP MIB Release

•The SNMP MIB release for 5.0.00 is mgx8XXXrel5000mib.tar.

Hardware Supported

This section lists:

•MGX 8880 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 8880

Hardware in Release 5.0.00

The following hardware is supported by the Release 5.0.00 software.

MGX 8880 Product IDs and Card Types

Table 3 lists Product IDs, minimum 800 part numbers, and the minimum revision levels for the MGX 8880.

Table 4 lists front and back card types, and whether the APS connector(s) is supported in Release 5.0.00.

Table 3 MGX 8880 Product IDs, 800 Part Numbers, and Their Minimum Revision Levels

Product ID

Minimum 800 Part Number

Minimum Revision

MGX-VXSM-155

800-15121-06

-A0

MGX-VXSM-T1E1

800-24073-02

-A0

VXSM-BC-4-155

800-21428-06

-A0

VXSM-BC-24T1E1

800-23088-03

-A0

AXSM-1-2488/B

800-07983-02

-A0

AXSM-16-155/B

800-07909-05

-A0

AXSM-16-T3E3/B

800-07911-05

-A0

AXSM-32-T1E1-E

800-22229-01

-A0

AXSM-4-622/B

800-07910-05

-A0

MGX-APS-CON

800-05307-01

-A0

MGX-MMF-FE

800-03202-02

-A0

MGX-SMFIR-1-155

800-14460-02

-A0

MGX-SRME/B

800-21629-03

-A0

MGX-BNC-3T3-M

800-23439-01

-A0

MGX-STM1-EL-1

800-23175-03

-A0

MGX-STM1-EL-1

800-14479-02

-A0

MGX-VISM-PR-8E1

800-07991-02

-A0

MGX-VISM-PR-8T1

800-07990-02

-A0

MMF-4-155/C

800-07408-02

-A0

MMF-8-155-MT/B

800-07120-02

-A0

PXM45/C

800-20217-04

-A0

PXM-HD

800-05052-03

-A0

PXM-UI-S3/B

800-21557-01

-A0

RBBN-16-T1E1

800-21805-03

-A0

SFP-8-155

800-21518-03

-A0

SMB-4-155

800-07425-02

-A0

SMB-6-T3E3

800-08799-01

-A0

SMB-8-E3

800-04093-02

-A0

SMB-8-T3

800-05029-02

-A0

SMF-4-2488-SFP

800-19913-04

-A0

SMFIR-2-622/B

800-07412-02

-B0

SMFIR-8-155-LC/B

800-07864-02

-B0

SMFLR-1-2488/B

800-08847-01

-A0

SMFLR-2-622/B

800-07413-02

-B0

SMFLR-8-155-LC/B

800-07865-02

-B0

SMFSR-1-2488/B

800-07255-01

-A0

SMFXLR-1-2488/B

800-08849-01

-A0

MGX-MMF-FE

800-03202-02

-A0

MGX-RJ45-4E/B

800-12134-01

-A0

MGX-RJ45-FE

800-02735-02

-A0

AX-SMB-8E1

800-02287-01

-A0

AX-R-SMB-8E1

800-02410-01

-A0

AX-RJ48-8T1

800-02286-01

-A0

AX-RJ48-8E1

800-02286-01

-A0

AX-R-RJ48-8T1

800-02288-01

-A0

AX-R-RJ48-8E1

800-02409-01

-A0

MGX-RPM-PR-256

800-07178-02

-A0

MGX-RPM-PR-512

800-07656-02

-A0

MGX-RPM-XF-512

800-09307-06

-A0

MGX-XF-UI

800-09492-01

-A0

MGX-2-GE

800-20831-04

-A0

MGX-2OC12POS-IR

800-21300-04

-A0

GLC-SX-MM (was MGX-GE-SX)

30-1301-01

-A0

GLC-LH-SM (was MGX-GE-LHLX)

30-1299-01

-A0

GLC-ZX-SM (was MGX-GE-ZX)

10-1439-01

-A0

Table 4 MGX 8880 Front and Back Card Types, and Whether APS Connector is Supported

Front Card Type

Back Card Types

Supports APS Connector
(MGX APS-CON or MGX-8880-APS-CON)

MGX-VXSM-155

VXSM-BC-4-155

Yes

MGX-VXSM-T1E1

VXSM-R-BC

No

VXSM-BC-24T1E1

No

PXM45/C

PXM-HD

—

PXM-UI-S3/B

—

AXSM-1-2488/B

SMFSR-1-2488/B

Yes

SMFLR-1-2488/B

Yes

SMFXLR-1-2488/B

Yes

AXSM-4-622/B

SMFIR-2-622/B

Yes

SMFLR-2-622/B

Yes

AXSM-16-155/B

SMB-4-155

Yes

MMF-8-155-MT/B

Yes

SMFIR-8-155-LC/B

Yes

SMFLR-8-155-LC/B

Yes

AXSM-16-T3E3/B

SMB-8-T3

—

AXSM-16-T3E3/B

SMB-8-E3

—

AXSM-32-T1E1-E

MCC-16-E1

—

RBBN-16-T1E1

—

MGX-VISM-PR-8T1

AX-RJ48-8T1

—

AX-R-RJ48-8T1

—

MGX-VISM-PR-8E1

AX-SMB-8E1

—

AX-R-SMB-8E1

—

AX-RJ48-8E1

—

AX-R-RJ48-8E1

—

MGX-SRME/B

MGX-BNC-3T3-M

No

MGX-STM1-EL-1

No

MGX-SMFIR-1-155

No

MGX-STM1-EL-1

No

MGX-RPM-PR-512

MGX-MMF-FE

—

MGX-RJ45-4E/B

—

MGX-RJ45-FE

—

MGX-RPM-XF-512

MGX-XF-UI

—

MGX-2-GE

—

MGX-2OC12POS-IR

—

GLC-LH-SM (was MGX-GE-LHLX¹)

—

GLC-SX-MM(was MGX-GE-SX1)

—

GLC-ZX-SM (was MGX-GE-ZX1)

—

Command Reference

Please refer to the following manuals for details about commands:

•The Cisco MGX 8850 (PXM45/PXM1E), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Command Reference, Release 5, part OL-4547-01, available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/cmdref/index.htm

•The Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5, part OL-4548-01, available online at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/8850px45/rel5/axsm/index.htm

•Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00

Limitations, Restrictions, and Notes for 5.0.00

This section includes information about limitations, restrictions, and notes pertaining to MGX Release 5.0.00.

•The VXSMs, when installed for the first time or after clearing the slot configuration, create default configuration. This creation of default configuration involves writing large amount of data to the hard disk in the node. So, when multiple VXSMs are installed simultaneously or the configuration of multiple VXSMs slots are cleared simultaneously, one or more VXSMs could fail to be installed. This results in following recommendations (refer to CSCed12646):

–install VXSMs using setrev command one at a time. Install another VXSM after the earlier one is installed completely and is Active.

–clear the VXSM slot configuration using clrsmcnf command (with no option where the slot primary software version is preserved) one at a time. Wait till the VXSM rebuilds after clearing the its slot configuration (without clearing the slot primary software version), before clearing the slot configuration of another VXSM slot.

Higher Level Logical Link Limits

•The numbers of logical links in the higher levels of the PNNI hierarchy is limited to 30 per level when the complex node configuration is turned on. The limit is essential to reduce the processing time involved in finding the bypasses between the logical links. Whenever there is a significant change in bandwidth in one of the links within the peer group, the bypass calculation is triggered and the bypasses are usually found from one logical link to another. So if there are n logical links, the calculation involves the finding n*n bypasses. So if the number of logical links n is large, a lot of processing time is used for calculating the bypasses. So the number of logical links per level has to be limited to 30. The number can be controlled by configuring the appropriate number of aggregation tokens for the outside links for that peer group.

AXSM-32-T1E1-E

•IMA version fall back is part of IMA group operation. If a group is configured with version 1.1 and it is connected to a far end group which is configured with version 1.0, this group will fall back to version 1.0.

•The IMA link LIF(Loss of IMA Frame) and LODS(Link Out of Delay Synchronization) defect integration times are configurable.

•ATM layer configuration for line and IMA ports takes an additional parameter, AIS enable. It is enabled by default.

•In T1 mode, payload scrambling is disabled by default and in E1 mode it is enabled by default on all lines and IMA groups.

•Only 10 SVC calls/sec is guaranteed

•FDL support for Loopback code detection is not supported

•Far End Line Performance counters are supported only for E1. They are not supported for the T1 interface.

•HMM support is not available for the IMA and the Framer devices. When there is switchover, it can take up to 3.5 seconds for the IMA groups to recover. Data is lost until the groups recover.

•IMA Auto-restart(persistent RX IMA ID) feature is supported.

•IMA group cannot have links from upper and lower bays together.

•ITC clocking mode on IMA is not supported.

•One way transmission delay of more than 500 msec on the T1/E1 IMA links is not supported

•There is 5ms fluctuation on IMA delay tolerance.

•While the IMA group accumulated delay is being removed with "clrimadelay", the following applies:

–Any changes to this IMA group configuration are temporarily blocked.

–Any changes in the FE IMA links in this group can cause the NE IMA group to restart.

•The VC and COSB thresholds are updated as and when the links are added/deleted from the IMA groups.

•The thresholds for the connections added when there are N links in the group can differ from connections added when there are (N+1) links in the IMA group.

•BERT is only supported on the T1 interfaces. It is not supported on E1 interfaces.

•The port number in the pnport(shelf.slot:subslot.port:subport) could be a random number. The user should not interpret this number as line or IMA group number. Refer to DDTS CSCdy08500

•PNNI requires SCR=453 cells/sec and PCR=969 cells/sec for the control connection.

•SSCOP requires of SCR=126 cells/sec and PCR= 2000 cells/sec.

AXSM-E OAM

•Any connection can receive E2E/OAM loopback cells up to the line rate (as long as the policing policy permits).

•If the connection is not in the loopback mode and is operating in the normal mode, then the AXSM-E card can receive up to 1,500 segment OAM loopback cells per second. Any excessive segment OAM loopback cell will dropped. This limitation applies for all the connections on a card.

•For example, if there is only one connection, then that connection can receive 1,500 segment OAM loopback cells per second. If there are 2,000 connections on an AXSM-E card and one segment OAM loopback cell per second is being pumped through on each connection, then there can only be up to 1,500 connections to receive loopback cells at any given second, and the additional 500 connections would not receive for that second.

•The limitation is 1,500 segment OAM loopback cells per card and not per connection, the 1,500 cps assumes an even flow rate.

CLI Configurable Access

The following notes pertain to how command access levels can be configured:

•Not all CLI commands are allowed to be changed and a command cannot be changed to CISCO_GP group access level.

•Only the switch software is allowed to generate the binary file. This file has an authentication signature which has to be validated before the file can be used. Any manual changes to the file would make the file void.

•If the binary file becomes corrupted, then the command access levels revert back to the default values during the card bring-up. To recover, repeat the installation process or retain a copy of the binary file and do cnfcli accesslevel install on that service module.

•Currently, command names are verified, but an invalid command name may be parsed and be added to the binary file. However, this invalid name would be ignored later.

•If replication to standby failed, the installation process failed.

•cnfcli accesslevel default restores all command access levels to default for the service module that this command is executed on. It does not remove the binary file and this change is not persistent. If it is executed on the active card of a redundancy pair, the standby card is not affected. When the card is reset and the binary file exists, it will configure from the binary file when it is brought up.

Serial Bus Path Fault Isolation

The Serial Bus Fault Isolation feature only addresses isolating errors on the local cards. However, when a common error occurs on the switching fabric card, this solution does not address this. As a result, if there is a problem on the PXM card, the fault is going to be reported against all cards that detected the symptoms of this problem.

Disk Space Maintenance

Because the firmware doesn't audit the disk space usage and remove unused files, the disk space in C: and E: drives should be manually monitored. Manually delete any unused saved configuration files, core files and firmware files and the configuration files of the MGX-RPM-PR-512 and MGX-RPM-XF-512 cards to avoid a shortage of disk space required to store event logs, configuration upload files in the C: drive and the configuration of MGX-RPM-PR-512 and MGX-RPM-XF-512 cards in the E: drive.

•The following steps are recommended to remove files on the system from the active controller card:

Step 1 Change to the directory that needs grooming.
CLI cc <directory_name> 
Step 2 List the directory to identify old files that can be removed and available disk space.
CLI ll 
Step 3 To remove any old files (you may also use wildcards in the filename):
CLI rm <complete_filename> 
Step 4 List the directory to see if the file has been removed and disk space is available:
CLI ll 
•Saving ConfigurationsThe system will keep only the two most recent copy of the saved system configuration under C:/CNF directory. Customer may use ftp protocol to ftp all the saved configuration under C:/CNF to their local server for future references. All files under C:/CNF will not replicated over to the standby controller card under any circumstances.

clrsmcnf Command

These notes pertain to the clrsmcnf command:

•Cisco does not recommend executing clrsmcnf on more than one card at a time

•For the clear service module configuration feature, if there is a controller card switchover before the clear service module configuration operation is complete, the clrsmcnf command needs to be re-issued to ensure that the configuration is completely cleared to avoid any incomplete cleanup.

•For the clear service module configuration feature, using the clrsmcnf command may result in discrepancy in the PNNI configuration. For example, some connections may be in the mis-match state.

•If the clrsmcnf command is given with the <all> option to clear the software version for the slot as well, then the card will go into the boot/empty state after the operation is complete.

•While using the clrsmcnf command, the card in the specified slot is not usable until the operation has successfully completed.

APS

These notes pertain to the APS feature:

•For AXSM APS, the backcard of the active card MUST be present for APS to function.

•AXSMs need the backcard of the active front card for the APS to work. This implies that AXSMs do not support the cross backcard removal, upper backcard of one AXSM and lower backcard of another AXSM.

•If you remove the upper backcard of the active front AXSM, it will trigger switching active card. At this point the APS is OK. However, if the lower backcard of the current active AXSM is removed at this time, it will not trigger switching active card since the standby card is missing one of the backcard. At this point the lower backcard APS does not work since the backcard of the active front card is missing.

•Port LED lights on AXSM-E front cards indicate the receive status of physical line connected to it only when the card is in active state. For a standby AXSM-E cards, the LEDs always remain green whether the lines are in LOS irrespective of which lines are Active (refer to anomaly CSCdv68576).

Path and Connection Trace

These notes pertain to the path and connection trace features:

•Path trace is not supported on the control port.

•Path trace will not have the accurate information when there is a crankback on the connect path.

•Path and Connection trace supports point to point connections.

•Path and Connection trace supports MPG (multi-peer group) and SPG (single-peer group).

Priority Routing

These notes pertain to the priority routing feature:

Prioritized reroute of SPVCs is not guaranteed, if the SPVCs originate on a signaling port. SPVCs may get routed out of order. In-order routing of SPVCs is guaranteed on non-signaling ports.

•RPM does not support configuration of routing priority. All RPM mastered SPVCs will be assigned a routing priority of 8 by the PXM.

•Changing the routing priority for dax connections, will not change the priority of the associated SVCs, this is because the SPVCs will not be derouted and rerouted if just the end-point parameters are changed, and routing priority is an end-point parameter. Also since dax connections are never derouted even when the UNI port goes down and rrtcon command is not supported for dax connections, the routing priority change will never get reflected. The only way for this to get reflected is to do a dncon and upcon. The very fact that dax connections are never derouted, the effect of this limitation is voided.

•Priority routing operates in a best effort manner for the following reasons:

–Two in-order RELEASEs can still arrive out of order at the Master node, if they take two different paths.

–Under congestion scenarios we can expect RELEASEs to be transmitted out-of-order. This is because we do not want to hold up the release of other calls if we are not able to send RELEASEs on one of the interfaces, as it is congested. The calls that we are unable to release could be higher priority calls.

–Lower priority SPVCs can be routed ahead of higher priority SPVCs. This can happen if we have attempted several times to route higher priority SPVCs, but failed. To prevent starvation of lower priority SPVCs, software will start to route lower priority SPVCs and software will get to the higher priority SPVCs at a later point in time.

SPVC Interop

These notes pertain to SPVC interoperability:

•NNI SPVC Addendum Version 1.0 is not supported.

•CC (Continuity Check) shall not be available at the slave end of a single-ended SPVC.

•Reporting AIS detection to CWM shall not be available at the slave end of a single-ended SPVC.

•The slave end of a single-ended SPVC shall not be visible to CWM.

•If Single-ended SPVCs are originated from MGX switches, they can only be configured via CLI and not from CWM in the current release.

•Single-end Provisioning will not be supported for DAX connections as no value addition is seen for Interoperability.

•SPVC Statistics shall not be available for the slave endpoint of a single-ended SPVC because this endpoint is non-persistent.

•When the persistent slave endpoint of an existing SPVC connection is deleted and the master endpoint is allowed to remain, the connection may get established as a single-ended spvc connection. In this case, CWM will show the connection as "Incomplete."

•Override of SVC connections on a VPI due to an incoming SPVP request for that VPI is not supported The following override options alone are supported:

–spvcoverridesvc

–spvcoverridesvp

–spvpoverridesvp.

Manual Clocking

These notes pertain to manual clocking:

•When resetcd is invoked, the primary and secondary (if configured) clock sources will be recommitted. However, the clock on which the node is latched on to will not be requalified. Only the backup clock will be qualified if present. Recommitted means that the primary and secondary will get requalified and the node will temporarily latch onto the internal oscillator, After the clock is requalified, the node will lock onto the primary clock source once again.

Other Limitations and Restrictions

•When configuring virtual interfaces (i.e. VUNI, VNNI, EVUNI, EVNNI), the physical interface must be of all one ATM header type, either UNI or NNI. Keep in mind that the signaling that is applied to a virtual port is independent of the actual virtual port ATM header. The only limit will be that the VPI value must be within the UNI ATM header limitations.

•If command clrchancnt is executed while a dspchancnt command is currently active then the data displayed will be incorrect. Restarting the dspchancnt after the previous one has completed will display correct data.

•clrsmcnf will not work for redundant service modules.

•clrsmcnf will not work if an upgrade is in progress.

•If RPM-XF is configured as a LSC (Label Switch Controller), execution of clrsmcnf command on those LSC slots will be rejected - as designed.

•Configuration information will not be synchronized between PXMs during upgrades. If there are any changes to the configuration during upgrades, the standby pxm needs to be rebooted. The standby PXM needs to be rebooted when it's in a stable state.

Clearing the Configuration on Redundant PXM45 Card

•Due to checks to prevent an inserted card from affecting the system, an additional step may be required when inserting two nonnative PXM45 cards in a shelf. Insert the first PXM45, use the clrallcnf command, and allow this to become active before inserting the second PXM45 .

•After a clrallcnf, the user needs to explicitly clean up stale SCT files (refer to anomaly CSCdw80282).

Caveats

This section provides information about known anomalies.

Known MGX 8880 Media Gateway Anomalies

For information about anomalies with the VXSM card, refer to Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00.

For information about anomalies in MGX Release 5.0.00 on other platforms, refer to Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00.

Known Route Processor Module or MPLS Anomalies

For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 .

MGX-RPM-XF-512 and MGX-RPM-PR-512 Anomalies

For information about anomalies with the MGX-RPM-XF-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00 .

For information about anomalies with the MGX-RPM-PR-512 card, refer to Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T5 for MGX Releases 1.3.00 and 5.0.00.

Documentation

A Guide to Cisco Multiservice Switch and Media Gateway Documentation ships with your product. That guide contains general information about how to locate Cisco MGX, BPX, SES, and CWM documentation online.

Documentation Notes for the April 2004 Product Releases

The April 2004 release includes new hardware or features for the following releases:

•Cisco MGX Release 5 for the MGX 8880 Media Gateway

•Cisco MGX Release 5 for these multiservice switches:

–Cisco MGX 8850 (PXM1E)

–Cisco MGX 8850 (PXM45)

–Cisco MGX 8950

–Cisco MGX 8830

•Cisco MGX Release 1.3, for these multiservice switches:

–Cisco MGX 8850 (PXM1)

–Cisco MGX 8230

–Cisco MGX 8250

•Cisco VXSM Release 5. The Voice Switch Service Module (VXSM) card is new for this release.

•Cisco WAN Manager Release 15. The Cisco WAN Manager (CWM) network management software is improved for this release. The previous release of CWM was 12. CWM Release 15 introduces a helpful new documentation feature: web-based online Help. To invoke online Help, press F1 on a PC, press the Help key on a UNIX workstation, or select Help from the main or popup menu.

Other components of multiservice WAN products, such as the Service Expansion Shelf (SES) and WAN switching software have no new features for the April 2004 release, therefore, their existing documentation was not updated.

Related Documentation

This section describes the technical manuals and release notes that support the April 2004 release of Cisco Multiservice Switch products.

Technical Manual Order of Use

Use the technical manuals listed here in the following order:

Step 1 Refer to the documents that ship with your product. Observe all safety precautions.

•Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES)—This document familiarizes you with safety precautions for your product.

•Guide to Cisco Multiservice Switch and Media Gateway Documentation—This document explains how to find documentation for MGX, BPX, and SES multiservice switches and media gateways as well as CWM network management software. These documents are available only online.

•Installation Warning Card—This document provides precautions about installing your cards. It explains such subjects as removing the shipping tab and inserting cards properly into the correct slots.

Step 2 Refer to the release notes for your product.

Step 3 If your network uses the CWM network management system, upgrade CWM. (If you are going to install CWM for the first time, do so after Step 4.) Upgrade instructions are included in the following documents:

•Cisco WAN Manager Installation Guide, Release 15

•Cisco WAN Manager User's Guide, Release 15

Step 4 If your network contains MGX and SES products, refer to this manual for planning information:

•Cisco PNNI Network Planning Guide for MGX and SES Products

Step 5 Refer to these manuals for information about installing cards and cables in the MGX chassis:

•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5 for installing cards and cables in these chassis.

•Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for installing cards and cables in the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.

Step 6 Refer to the manuals that help you configure your MGX switch and processor cards:

•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5 for these chassis.

•Cisco MGX 8xxx Edge Concentrator Installation and Configuration Guide for the Cisco MGX 8230, Cisco MGX 8250, or Cisco MGX 8850 (PXM1) chassis.

Step 7 Refer to the manual that supports the additional cards you intend to install in your switch. For example:

•The services books can help you establish ATM, Frame Relay, or circuit emulation services on your switch.

•The VISM book can help you set up your switch as a voice gateway, and the RPM book can help you implement IP on the switch.

Step 8 Additional books, such as command reference guides and error message books, can help with the daily operation and maintenance of your switch.

Note Manual titles may be different for earlier software releases. The titles shown in Table 5 are for the April 2004 release.

Technical Manual Titles and Descriptions

Table 5 lists the technical manuals and release notes that support the April 2004 multiservice switch product releases. Books and release notes in Table 5 are listed in order of use and include information about which multiservice switch or media gateway the document supports.

The books for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches were not updated for the April 2004 release, therefore, some information about configuring and using the new MPSM-8-T1E1 card in these switches is included in the following books:

•Cisco ATM Services (AUSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

•Cisco Frame Relay Services (FRSM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

•Cisco Circuit Emulation Services (CESM/MPSM) Configuration Guide and Command Reference for MGX Switches, Release 5

Information about how to install or upgrade to the MPSM-8-T1E1 card in Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) switches is in the Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00.

Note Refer to each product's release notes for the latest information on features, bug fixes, and more.

Terms

Two main types of ATM cards are used in MGX switches: AXSM and AUSM. AXSM stands for ATM Switching Service Module. AUSM stands for ATM UNI (User Network Interface) Service Module.

CWM stands for Cisco WAN Manager, our multiservice switch network management system.

Legacy service module refers to a previously introduced card. For this release, the term is used specifically for the CESM-8-T1E1, FRSM-8-T1E1, and AUSM-8-T1E1 cards, which can now be replaced by the new MPSM-8-T1E1 card.

MPSM stands for Multiprotocol Service Module.

RPM stands for Route Processor Module.

SES stands for Service Expansion Shelf.

VISM stands for Voice Interworking Service Module.

VXSM stands for Voice Switch Service Module.

Table 5 Technical Manuals and Release Notes for Cisco MGX and BPX Switches and Media Gateways (April 2004 Product Releases)

Document Title and Part Number

BPX with SES Rel. 4

MGX 8230 Rel. 1.3

MGX 8250 Rel. 1.3

MGX 8850 (PXM1) Rel. 1.3

MGX 8830
Rel. 5

MGX 8850 (PXM1E) Rel. 5

MGX 8850 (PXM45) Rel. 5

MGX 8950 Rel. 5

MGX 8880 Rel. 5.

Overview and Safety Documents

Guide to Cisco Multiservice Switch and Media Gateway Documentation

DOC-7814807=

x

x

x

x

x

x

x

x

x

Installation Warning Card

DOC-7812348=

x

x

x

x

x

x

x

x

x

Regulatory Compliance and Safety Information for Cisco Multiservice Switch and Media Gateway Products (MGX, BPX, and SES)

DOC-7814790=

—

x

x

x

x

x

x

x

x

Release Notes for the Cisco MGX 8880 Media Gateway, Release 5.0.00

OL-5190-01

—

—

—

—

—

—

—

—

x

Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.0.00

OL-4538-01

—

—

—

—

x

x

x

x

Release Notes for Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 (PXM1) Switches, Release 1.3.00

OL-4539-01

—

x

x

x

—

—

—

—

—

Release Notes for the Cisco Voice Switch Service Module (VXSM), Release 5.0.00

OL-4627-01

—

—

—

—

—

—

x

—

x

Release Notes for Cisco WAN Manager, Release 15.0.00

OL-4151-01

—

—

—

—

x

x

x

x

x

Release Notes for the Cisco Voice Interworking Service Module (VISM), Release 3.2.10

OL-4544-01

—

x

x

x

x

x

x

—

x

Release Notes for Cisco MGX Route Processor Module (RPM-XF) IOS Release 12.3(2)T5 for PXM45-based Switches, Release 5.0.00

OL-4536-01

—

—

—

—

—

—

x

x

x

Release Notes for Cisco MGX Route Processor Module (RPM-PR) IOS Release 12.3(2)T5 for MGX Releases 1.3.00 and 5.0.00

OL-4535-1

—

x

x

x

x

x

x

x

x

Cisco MGX 8230 Edge Concentrator Overview, Release 1.1.3¹

DOC-7812899=

—

x

—

—

—

—

—

—

—

Cisco MGX 8250 Edge Concentrator Overview, Release 1.1.3¹

DOC-7811576=

—

—

x

—

—

—

—

—

—

Cisco MGX 8850 Multiservice Switch Overview, Release 1.1.3¹

OL-1154-01

—

—

—

x

—

—

—

—

—

Hardware Installation Guides

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Hardware Installation Guide, Releases 2 Through 5

OL-4545-01

—

—

—

—

x

x

x

x

x

Cisco Service Expansion Shelf Hardware Installation Guide, Release 1¹

DOC-786122=

x

—

—

—

—

—

—

—

—

Planning and Configuration Guides

Cisco PNNI Network Planning Guide for MGX and SES Products

OL-3847-01

x

—

—

—

x

x

x

x

x

Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, Cisco MGX 8830, and Cisco MGX 8880 Configuration Guide, Release 5

OL-4546-01

—

—

—

—

Hierarchical Navigation

Cisco MGX 8880 Media Gateways

5.0.00 Release Notes for Cisco MGX 8880 Media Gateway

Downloads

Table Of Contents

Release Notes for Cisco MGX 8880 Software Version 5.0.00

Contents

About Release 5.0.00

Type of Release

Locating Software Updates

Service Class Template (SCT) File Information

AXSM/B

AXSM-E

System Requirements

Software/Firmware Compatibility Matrix

MGX and RPM Software Version Compatibility Matrix

Additional Notes

SNMP MIB Release

Hardware Supported

Hardware in Release 5.0.00

MGX 8880 Product IDs and Card Types

Command Reference

Limitations, Restrictions, and Notes for 5.0.00

Higher Level Logical Link Limits

AXSM-32-T1E1-E

AXSM-E OAM

CLI Configurable Access

Serial Bus Path Fault Isolation

Disk Space Maintenance

clrsmcnf Command

APS

Path and Connection Trace

Priority Routing

SPVC Interop

Manual Clocking

Other Limitations and Restrictions

Clearing the Configuration on Redundant PXM45 Card

Caveats

Known MGX 8880 Media Gateway Anomalies

Known Route Processor Module or MPLS Anomalies

MGX-RPM-XF-512 and MGX-RPM-PR-512 Anomalies

Documentation

Documentation Notes for the April 2004 Product Releases

Related Documentation

Technical Manual Order of Use

Technical Manual Titles and Descriptions

Terms