Table Of Contents

9.4.12 Version Software Release Notes Cisco WAN Switching System Software

Table of Contents

About the 9.4.12 Release

Software Release 9.4.12 Files

New Features in Release 9.4.12

New Features in Release 9.4.10

Configuration Support for Pseudo AIS on BXM

Load Balancing on Equal Cost Paths

Real Time Statistics from SNMP Using an SNMP GET

ATM Discard VCQ Full Counter Statistics on BXM Endpoints

New Features in Release 9.4.00

IGX as an AAL5 Feeder

VSI Service Class Template Configuration

TFTP Interval and SNMP Channel Statistics Configuration

URM IOS CLI

Line Rate PCR

CPU Idle Time from SNMP

BCC SAR Failure

Auto Switchyred on UXM

IGX and BPX Connection Scaling

Continuous Alarm on Invalid Login Attempts

Revising Access Levels for Configuration Commands

Special Installation and Upgrade Requirements

General Upgrade Procedure

Revision Interoperability Supported

Version Compatibility Notes

Control Card Requirements

Control Card Boot Firmware Requirements

Control Card Compatibility Requirements

Control Card Physical Card Upgrade Procedure

Limitations for Release 9.4.12

Compatibility Matrix

Compatibility Notes

MGX 8220 Firmware Compatibility

MGX 8850 1.1/1.2 Firmware Compatibility

MGX 8230 1.1/1.2 Firmware Compatibility and
MGX 8250 1.1/1.2 Firmware Compatibility

BPX 8600 Firmware Compatibility

IGX 8400 Firmware Compatibility

MGX 8220 5.0 Hardware Compatibility

BPX 8600 Hardware Compatibility

IGX 8400 Hardware Compatibility

Anomalies in Release 9.4.12

Known Anomalies in Release 9.4.12

Resolved Anomalies in Release 9.4.12

Anomalies in Release 9.4.10

Known Anomalies in Release 9.4.10

Resolved Anomalies in Release 9.4.10

Anomaly Status Change from Previous Releases

Additional Deliverables

SNMP MIB

Default Values

Cisco BPX 8600 Nodes

Cisco IGX 8400 Nodes

Appendix A—BXM Firmware MFZ Release Notes

About the Firmware MFZ

Front Cards

Front Card for APS Compatibility

Back Cards

New Features Supported in BXM Firmware MFZ

New Features Supported in BXM Firmware MFY

New Features Supported in BXM Firmware MFX

New Features Supported in BXM Firmware MFW

New Features Supported in BXM Firmware MFV

New Features Supported in BXM Firmware MFU

New Features Supported in BXM Firmware MFT

New Features Supported in BXM Firmware MFR

New Features Supported in BXM Firmware MFP

New Features Supported in BXM Firmware MFN

New Features Supported in BXM Firmware MFM

New Features Supported in BXM Firmware MFK

New Features Supported in BXM Firmware MFJ

New Features Supported in BXM Firmware MFH

New Features Supported in BXM Firmware MFF

New Features Supported in BXM Firmware MFE

New Features Supported in BXM Firmware MFD

New Features Supported in BXM Firmware MFC

New Features Supported in BXM Firmware MFB

New Features Supported in BXM Firmware MFA

New Features Supported in BXM Firmware MEC

New Features Supported in BXM Firmware MEB

New Features Supported in BXM Firmware MEA

New Features Supported in BXM Firmware MDA

Special Installation/Upgrade Requirements

Features Obsoleted

Notes, Cautions, and Clarifications

Anomalies Fixed in MFZ

Known Anomalies in MFY

Anomalies Fixed in MFY

Known Anomalies in MFX

Anomalies Fixed in MFX

Anomalies Fixed in MFW

Anomalies Fixed in MFV

Anomalies Fixed in MFU

Anomaly Fixed in MFT

Anomalies Fixed in MFR

Anomalies Fixed in MFP

Anomalies Fixed in MFN

Anomalies Fixed in MFM

Anomalies Fixed in MFL

Anomalies Fixed in MFK

Anomalies Fixed in MFJ

Anomalies Fixed in MFH

Anomalies Fixed in MFF

Anomalies Fixed in MFE

Anomalies Fixed in MFD

Anomalies Fixed in MFC

Anomalies Fixed in MFB

Anomalies Fixed in MFA

Anomalies Fixed in MEC

Logic to Calculate Actual Cell Transmission Rate in a BXM card (CSCdm94372)

Anomalies Fixed in MEB

Anomalies Fixed in MEA

Firmware Filenames and Sizes

Appendix B—UXM Model C ACK Firmware Release Notes

Introduction

New Feature

Obsolete Features

Compatibility

Anomalies Fixed in ACK

Upgrade Instructions

Anomalies Fixed in ACH

Boot Code Requirements

Unsupported Configurations or Applications

Notes and Cautions

Firmware Filenames and File Sizes

Appendix C—UXM Model B Firmware ABU Release

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in ABU

Upgrade Instructions

Boot Code Requirements

Unsupported Configuration or Applications

Firmware Filenames and Sizes

Notes and Cautions

Appendix D—UXM Model B Firmware ABV Release

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in ABV

Upgrade Instructions

Boot Code Requirements

Unsupported Configuration or Applications

Firmware Filenames and Sizes

Notes and Cautions

Appendix E—URM Model B Firmware XBC Release Notes

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in XBC

Upgrade Instructions

Boot Code Requirements

Unsupported Configurations or Applications

Firmware Filenames and Sizes

Notes and Cautions

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

9.4.12 Version Software Release Notes Cisco WAN Switching System Software

---

These release notes are part number OL-7563-01 Rev. A0, April 19, 2005.

Table of Contents

About the 9.4.12 Release

The 9.4.12 software release supports the Cisco WAN switching products: Cisco BPX 8600 series and Cisco IGX 8400 series.

Throughout this document, unless otherwise stated, all references to BXM also include BXM-E. References to UXM also include UXM-E.

Software Release 9.4.12 Files

This maintenance release includes all features supported up to Release 9.4.12.

Table 1 Release 9.4.12 BPX Files

File Name(s)	File Size
9412B.000-9412B.026	65536
9412B.026	5829
9412B.img	784

Table 2 Release 9.4.12 IGX Files

File Name	File Size
9412G.000-9412G.028	65536
9412G.029	17272
9412G.img	784

New Features in Release 9.4.12

None.

New Features in Release 9.4.10

This section describes the following new features included in Release 9.4.10:

• "Configuration Support for Pseudo AIS on BXM" section

• "Load Balancing on Equal Cost Paths" section

• "Real Time Statistics from SNMP Using an SNMP GET" section

• "ATM Discard VCQ Full Counter Statistics on BXM Endpoints" section

Configuration Support for Pseudo AIS on BXM

This feature allows users to configure (enable/disable) pseudo AIS alarm generation on BXM OC3/OC12 trunks when error rates exceed 1 in 10^-3.

Under normal conditions, when the error rate exceeds 1 in 10^-3, the SWSW declares the trunks to be in Major Alarm (Statistical). However, the connections on the trunks remain routed over those erroneous trunks. Traffic can be potentially impacted on those routed connections.

To reduce the risk of user traffic running on erroneous links, BXM can be configured to generate a pseudo PATH AIS alarm in such higher error conditions on BXM OC3/OC12 links and send it back to SWSW to put trunks in fail mode. Under this path AIS trunk failure condition, the SWSW reroutes the connections on the erroneous trunks, thereby making a statistical alarm to mimic the behavior of a regular trunk alarm.

The modifications in SWSW allows the BXM firmware to declare a "fake path AIS", which is configurable from the SWSW CLI command interface. If you do not need the pseudo AIS alarm, you can turn off this feature.

This feature adds a new configuration entry in the current cnfnodeparm command screen. A new configuration parameter is added to cnfnodeparm command to support the display and configuration of fake AIS alarm.

To enable this feature use the following syntax:

cnfnodeparm 61 Y

To disable this feature, use the following syntax:

cnfnodeparm 61 N

The default is disable.

Any changes in this parameter trigger the SWSW to send the appropriate configuration messages (enable or disable) to all BXM cards in the node. See the "Default Values" section for a screen shot of the cnfnodeparm command.

Limitation

This feature requires BXM firmware revision MFY or higher.

Load Balancing on Equal Cost Paths

This feature provides the capability to balance the load on parallel equal cost paths across two nodes. Load balancing is controlled by a debug flag (on/off switch).

This feature is done by extending the Dijkstra's algorithm that is used to find the shortest path based on the trunk cost. The algorithm is used to find out the shortest path to a destination based on the lowest cost path, but the algorithm does not indicate what to do in case the paths are of equal cost.

On equal cost paths the load balance should be the same. The implementation of a tie break for loads on equal cost paths is based on the following three tie breaks, acting one after the other in case the earlier tie break fails:

1. Open space on the trunks

2. Available LCNs

3. GW LCNs.

Currently, when a parallel equal cost path exists, all of the connections added tend to take the trunk with the lowest logical ID irrespective of the load on that trunk. This feature corrects this behavior.

Real Time Statistics from SNMP Using an SNMP GET

The feature adds the ability to obtain real-time statistics from the cards through SNMP Get operation.

No changes occur with the switch when the statistics are queried through SNMP Walk operation. Using the GET operation improves statistics retrieval performance.

ATM Discard VCQ Full Counter Statistics on BXM Endpoints

This feature implements collection of SNMP statistics for the Receive VCQ Full cell discard for connection endpoints on the BXM card.

Previously, the MIB object "atmDiscardVcqFulls", which provides the VCQ Full discard value, was implemented for connection endpoints on ASI. This feature extends the capability to BXM endpoints. and supports statistics for all types of BXM service modules.

New Features in Release 9.4.00

This section describes the following new features included in Release 9.4.00:

• "IGX as an AAL5 Feeder" section

• "VSI Service Class Template Configuration" section

• "TFTP Interval and SNMP Channel Statistics Configuration" section

• "URM IOS CLI" section

• "Line Rate PCR" section

• "CPU Idle Time from SNMP" section

• "BCC SAR Failure" section

• "Auto Switchyred on UXM" section

• "IGX and BPX Connection Scaling" section

• "Continuous Alarm on Invalid Login Attempts" section

• "Revising Access Levels for Configuration Commands" section

IGX as an AAL5 Feeder

This feature allows the IGX to act as an AAL5 feeder to the PXM45-based Cisco MGX 8850, the PXM1E-based Cisco MGX 8850, and the Cisco MGX 8830 or the BPX+SES switches.

In prior releases, the IGX could only be a feeder to the BPX (or another IGX). The two nodes communicate by using Annex G LMI over a proprietary Auto Route Networking Channel.

This new IGX AAL5 feeder support is added by encapsulating the LMI messages in ATM AAL5 cells on the UXM feeder trunk that is connected to an AXSM, AXSM-E, PXM1E, or BXM card.

See the "SNMP MIB" section for more information on the SNMP interface changes for this feature.

Additional Capabilities

The dsplmistats command includes the LMI Node Status statistics.

The following commands have been added to configure and display the LMI timers:

•cnffdrlmiparms

•dspfdrlmiparms

See the following example:

Last Command: cnffdrlmiparms 10 10 10 5 5




T393 Status Enquiry Timer: 10

T394 Update Status Timer: 10

T396 Polling Timer: 10

N394 Max Status Enquiry Retry: 5

N395 Max Update Status Retry: 5




Last Command: dspfdrlmiparms

Next Command:




rmfdrrsrc

The following new SuperUser command has been added:

rmfdrrsrc

Use this command to remove a feeder that is in LMI communication failure because the routing node is no longer attached. If the routing hub deletes an IGX feeder while other connection exist on the feeder, the feeder becomes dangling.

To cleanup a dangling IGX feeder:

---

Step 1 Delete all existing connections on the IGX feeder

Step 2 Issue the new command rmfdrrsrc.

---

Syntax

rmfdrrsrc <slot.port>

Parameters

Parameter	Description
slot.port	Slot and port numbers corresponding to the feeder trunk interface.

Attributes

Privilege	Jobs	Log	Node	Help	History	Lock	HiPri
SuperUser	No	Yes	BPX, IGX	Yes	Yes	Yes	No

Limitations on the IGX AAL5 Feeder Feature

This feature has the following limitations:

1. The IGX AAL5 feeder trunk (to the PXM45-based Cisco MGX 8850, the PXM1E-based Cisco MGX 8850, and Cisco MGX 8830 or the BPX+SES) is only supported on UXM or UXM-E cards.

2. The control VCs for LMI and IP connectivity use VPI/VCI of 3/31 and VPI/VCI of 3/8 respectively. These values are not user configurable.

3. XPVCs and XPVPs remain unsupported on the IGX, whether it is a feeder or a routing node.

4. The URM card remains unsupported on the IGX AAL5 feeder.

5. The UXM IMA back card with the BNC connectors is not supported on the IGX AAL5 feeder.

VSI Service Class Template Configuration

Cell loss ratio (CLR) is a new configurable parameter in the QBIN template. The value of CLR from the template is used as default for CAC calculations, if a value of zero is specified for CLR in the connection request.

CLR is negotiated by PNNI for SVCs but not for SPVCs. For SPVCs, the value of CLR from the template is used, rather than assuming a CLR of zero for CAC calculations.

This enhancements also make the existing "Discard Selection" parameter in the QBIN template configurable on an interface.

In a Multi-VC TAGCOS solution 8 IP TOS (Type of Service) values are queued into 4 classes. Each class is assigned a Qbin. To differentiate between two different TOS in the same Qbin, cells belonging to one of the TOS are marked with a CLP = 1. For this scheme to work, which means to provide a higher QOS to the TOS with greater precedence or priority, the discard method used at the Qbin should be CLP Hysteresis, and not EPD.

Previously, there was no way of changing the Discard Selection mechanism used at the Qbin. The Discard Selection at the Qbin is now configurable, allowing you to choose whether EPD or CLP Hysteresis should be used as the discard algorithm at the Qbin.

The configuration of CAC treatment in the VC descriptor template has been made more user friendly by displaying the available CAC options on the screen. Input error checking has been added to ensure that you select a valid CAC treatment for the selected Service Class.

Affected CLI command - cnfqbin

CLR (Cell Loss Ratio) parameter

The cnfqbin command has been modified to allow configuration of CLR parameter.

Syntax:

cnfqbin <Interface> <Qbin> .........<CLR>

Parameters:

Parameter	Description
<Interface>	Interface on which CLR needs to be configured.
<Qbin>	Qbin number for CLR configuration.
<CLR>	Value range is 1-15.The configured number indicates the negative power to which the base 10 is raised to obtain the value for CLR. For example, a value of 8 would indicate a CLR = 1/108.

Attributes:

Privilege	Jobs	Log	Node	Help	History	Lock	HiPri
1-6	Yes	Yes	BPX/IGX	Yes	Yes	Yes	No

Discard Selection parameter

The cnfqbin command has been modified to allow configuration of the Frame Discard Select parameter of the Qbin template. You can now choose between PPD or EPD.

Syntax:

cnfqbin <Interface> <Qbin> ........ <Frame Discard Select>

Parameters:

Parameter	Description
<Interface>	Specifies interface on which Frame Discard Select need to be configured.
<Qbin>	Qbin number for Frame Discard Select configuration.
<Frame Discard Select>	Discard schemes. •PPD •EPD

Attributes:

Privilege	Jobs	Log	Node	Help	History	Lock	HiPri
1-6	Yes	Yes	BPX/IGX	Yes	Yes	Yes	No

Example:

NODE TN Cisco BPX 8620 9.4.00 Date/Time Not Set




Qbin Database 4.2 on BXM qbin 10 (Configured by ATMF_tagcos_1 Template)

(EPD Enabled on this qbin)




Qbin State: Enabled

Discard Threshold: 24000 cells

EPD Threshold: 95%

High CLP Threshold: 100%

EFCI Threshold: 100%

Cell Loss Ratio : 8

Frame Discard Select : EPD




This Command: cnfqbin 4.2 10 e n 24000 95 100 100




Cell Loss Ratio [8] :




Affected CLI Command - cnfqbint

Cell Loss Ratio:

A new parameter is displayed on the cnfqbint command. This parameter takes values from 1-15.The configured number indicates the negative power to which the base 10 is raised to obtain the value for CLR. For example a value of 8 would indicate a CLR = 1/10⁸.

cnfqbint <tmplt_id> <Qbin> <parm_index> <parm_val>

Frame Discard Select:

The cnfqbint command now has an additional option for selecting between EPD and PPD through a new field "Frame Discard Select" in the display.

cnfqbint <tmplt_id> <Qbin> <parm_index> <parm_val>

Example

NODE TN Cisco BPX 8620 9.4.00 Date/Time Not Set




Service Template: 1 Qbin: 10




1 Discard Threshold: 300000 (micro secs)

2 CLP Low/EPD Threshold: 95 (% of Discard Threshold)

3 CLP High Threshold: 100 (% of Discard Threshold)

4 EFCI Threshold: 100 (% of Discard Threshold)

5 Frame Discard Select: PPD

6 Vc Shaping: Enabled

7 Cell Loss Ratio 8

This Command: cnfqbint 1 10




Enter index for parameter to modify:




TFTP Interval and SNMP Channel Statistics Configuration

In previous releases, TFTP Interval Statistics for connections were configured on a node basis. When a particular channel statistic type was enabled, all connections which supported the enabled statistic attempted to collect it. On a node with a large number of terminated connections, huge amounts of resources are used to collect, format and store the statistics. The TFTP Statistics operation leads to an unnecessary overhead if statistics are needed for only a small subset of terminated connections.

SNMP or Counter Channel Statistics are automatically enabled whenever a connection is added from or to a node. SNMP Statistics collection also leads to unnecessary overhead if the user does not require these statistics for all connections.

This feature allows you to configure individual connections to enable or disable TFTP channel interval Statistics or SNMP Channel Statistics or both. TFTP and SNMP Statistics will only be collected for those connections that have collection of the respective statistics enabled.This leads to an improvement in performance. In order to achieve this performance improvement, you have to disable both SNMP and TFTP statistics on each connection for which statistics collection is not required.

The default settings for this feature are TFTP Channel Interval Statistics collection enabled and SNMP Channel Statistics collection disabled. (As seen by the new command, dspstatcon screen.)

See the "SNMP MIB" section for more information on the SNMP interface changes for this feature.

URM IOS CLI

This feature in IGX Switches allows you to access the IOS CLI of the URM embedded router from the IGX CLI without having to be locally attached to the console, auxiliary or Ethernet port of the URM.

In previous releases, a physical cable was required to connect to the console router port. Therefore, it required that you were physically on site to access the router, or if there are more than one router in the same IGX shelf, then it would require physical moving of the cable from router to router or multiple connections to individual router ports.

With this feature, you can access the router remotely and perform maintenance on the router without having to be physically on site, as there is no physical cable to move.

---

Note Only one session per node can be active at a time.

---

Line Rate PCR

This feature provides the capability to configure a VSI partition to advertise either VI Rate or VSI Max Bandwidth to the controller. Depending on this the PNNI connections on that VSI partition can have a PCR up to the VI Rate or the VSI Max Bandwidth.

AutoRoute allowed the connections to have a PCR up to the VI Rate in releases prior to 9.4. In prior releases, as connections were migrated from AutoRoute to PNNI, since the PNNI connections could have a PCR only up to the VSI Max Bandwidth, the connections would need to have the PCR adjusted to meet the PNNI restrictions. With this feature the PNNI connections can retain their PCR setting upon migration.

CPU Idle Time from SNMP

This feature introduces a new SNMP MIB object which returns the CPU idle time calculated by the profiler. This object will give the idle time as displayed in the "dspprf" screen. The way the profiler works is that it has discrete time interval (configurable using "cnfprfparm"). When that time interval expires, it sums the values and takes the average. Using the above timeline, the profiler, if set to 20 seconds, would take the values for 1 through 20, compute their average and then display that value, non-changing for the next 20 seconds. Until at time t=40, it would take the values for 21 through 40, compute their average and then display the value, non-changing for the next 20 seconds. Until at time t=60, it would take the values for 41-60, compute their average and then display the value, non-changing for the next 20 seconds. CPU idle time is accessible via SNMP interface through the MIB object "shelfCnfgAverageIdle".

See the "SNMP MIB" section for more information on the SNMP interface changes for this feature.

BCC SAR Failure

This feature, which can be enabled or disabled by a debug flag on/off3, provides the capability to automatically do a switchover on a SAR failure of the BCC. The modifications in the switch software flag the BCC failures on an Active or Standby cards as MAJOR alarms and do an automatic switchover as necessary when this feature is enabled. See the "Default Values" section for a screen shot of the on3 command.

The BCC switchover will only occur if the node has a healthy card in standby state that is ready to take over. The switchover recovery will not occur if the standby is in a failed state (or even SAR failed), or in download or update phase, instead the node will undergo a hitless rebuild. If the standby is in an upgraded state, then the SAR failure will trigger a hitless rebuild as opposed to a switchcc. The same will be the case, if the standby is not ready to takeover the control, either because of a failure or because of an ongoing update. The failure on the card will be cleared, if the BCC undergoes a hitless rebuild and an event will be logged to reflect this. If the switchover occurs to a healthy standby, the original active's failure will not be cleared so that the user will have a chance to examine the failure reason later.

Auto Switchyred on UXM

This feature, which can be enabled or disabled by a debug flag on/off3, provides the capability to automatically do a switchyred up on receiving a Loss of Cell on a UXM-OC3 interface, if a y-redundant pair is available. This feature also adds the capability to support the switchyred command on the IGX platform, for both UXM as well as legacy cards, similar to the switchyred command currently available on the BPX platform. See the "Default Values" section for a screen shot of the on3 command.

IGX and BPX Connection Scaling

This feature speeds up the CWM sync-up time when there are more number of connections in a network. This feature provides a debug flag(on/off3) from the switch CLI to enable or disable the sending of the slave endpoint connection updates to the CWM.The improvement in the CWM sync-up time can be achieved if the slave end point connection updates debug flag is set to disabled. See the "Default Values" section for a screen shot of the on3 command.

Continuous Alarm on Invalid Login Attempts

Currently if generation of MAJOR alarm on invalid log in attempts is enabled (by putting the value for cnfsysparm 22 to 3 or more) switch software generates a MAJOR alarm on (say) 3 consecutive invalid login attempts and generates a 20005 trap. This trap will not be sent again until the alarm has been investigated and cleared by using the CLI command "clrloginalm". See the "Default Values" section for a screen shot of the cnfsysparm command.

This feature provides support to generate this trap for each block of consecutive invalid login attempts whether the command clrloginalm is executed or not.

Revising Access Levels for Configuration Commands

The access levels are raised for the following commands:

•cnfsnmp (IGX/BPX)—from ANYUSER to SUPER User

•cnfqbin (BPX)—from ANYUSER to SUPER User

•cnfportfunc (IGX)—from ANYUSER to SUPER User [command is new on the BPX]

•cnfabrparm (BPX)—from GROUP5 to SUPER User

Special Installation and Upgrade Requirements

This section contains the installation procedures and upgrade requirements.

General Upgrade Procedure

---

Note Consult a Support Representative before performing any software upgrade.

---

The earliest release supported for a graceful upgrade is 9.3.33.

Before upgrading the switch software, make sure the cards have the minimum firmware revision per the compatibility matrix.

Procedure for Adding New BCC Cards as a Part of Upgrading to Release 9.4

If new BCC cards are to be installed as part of the upgrade to Release 9.4, then the physical card upgrade procedure described below must be completed as a separate activity from the Switch software upgrade.

•If upgrading to BCC-4 cards on BPX 8600 nodes, perform the software upgrade, followed by the BCC-4 physical card upgrade.

If BCC-4 is already installed, then upgrade as normal.

•If any other type of BCC cards are being physically upgraded, complete the physical upgrade of the cards first, followed by the software upgrade.

Revision Interoperability Supported

The Revision Interoperability feature allows a mixed/ heterogeneous network of 9.3.30, 9.4.00, 9.4.10, or 9.4.12 nodes to coexist and interoperate. This capability allows users to upgrade their networks from 9.3 to 9.4 in multiple steps.

---

Note It is not recommended that users operate in this state for extended periods of time.

---

Normal network maintenance and operations such as provisioning, trunk reroutes, card insertions and removals, and normal network alarming, are supported in the mixed revision network. Normal alarms can be received while upgrading a node to Release 9.4.

Version Compatibility Notes

For a complete list of firmware revisions supported, see the "Compatibility Matrix" section.

This release supports:

•NTM firmware version NEK and NFK or later. For 2048 kbps support and trunk encryptor synchronization, use NJA and NKA or later.

•UXM firmware

–For MPLS VC merge and trunk loopback features, ACK or later

–For MPLS/VSI feature, UXM model ACB or later

–If not using MPLS/VSI feature, UXM model ABH or later

•BXM firmware

–Model MFN or later

–For MPLS VC merge, trunk VC traffic shaping, and VT oversubscription features, MFV or later.

•UFM firmware for ELMI-based topology discovery feature

–For UFM-C model B, version ZBD, and UFM-U model B, version YBC

–For UFM-C model A, version ZAT, and UFM-U model A, version YAL

•URM Model A XAA, or later

•URM Model B XBA or later

---

Note VNS interworking is not supported in Release 9.3.30 and later.

---

Control Card Requirements

All BPX processor cards must be configured with a minimum of 64 MB of RAM, and NPMs must be configured with a minimum of 32 MB of RAM. NPMs require at least 1 MB of BRAM. VSI on IGX requires NPMs with at least 4 MB of BRAM. To verify the BRAM size on IGX 8400 nodes, use the dspcd command.

Control Card Boot Firmware Requirements

As specified below, the correct version of CC boot firmware must be installed on the cards prior to a software upgrade to Release 9.4.

BCC Type	Firmware
BCC-3-64	H.D.M
BCC-4V	H.H.M
BCC-4V/B	H.H.M

NPM Type	Firmware
NPM-32	R.B.S
NPM-64	R.C.S
NPM-32B	R.E.S
NPM-64B	R.F.S

With the new version of NPM boot code (RxS), upgrading does not require physical card resetting with the following steps:

---

Step 1 Burn the boot code on the active NPM(1).

Step 2 Execute the switchcc command. Wait until the NPM(1) becomes standby.

NPM(2) is now active.

Step 3 Execute the resetcd command to reset the standby (resetcd 1 h). Wait until the reset card NPM(1) becomes standby.

Step 4 Burn the boot code on the active NPM(2).

Step 5 Execute the switchcc command. Wait until the NPM(2) becomes standby.

NPM(1) is now active.

Step 6 Execute the resetcd command to reset the standby (resetcd 2 h). Wait until the reset card NPM(2) becomes standby.

---

Control Card Compatibility Requirements

Each redundant pair of BCC cards in a given BPX 8600 node must be of identical type and memory configuration. For example, if the active card is a BCC-3-64, then the standby card must be the same. BCC-3 cards with 64 MB of RAM cannot be mixed with BCC-4 cards.

Each redundant pair of NPM cards in a given IGX 8400 node must be of identical type and memory configuration. For example, if the active card is an NPM-32, then the standby card must be the same. NPM cards with 32 MB of RAM cannot be mixed with NPM cards with 64 MB of RAM. Also, NPM-64 cards cannot be mixed with NPM-64B cards.

These requirements apply to all software upgrade procedures. These requirements do not apply to the physical card upgrade procedure, as described below.

Control Card Physical Card Upgrade Procedure

When performing a control card (CC) upgrade, the following procedure must be used on all BCC and/or NPM processors:

---

Step 1 Remove the current standby CC front and back cards. (Removal of back card only applies to BCC.)

Step 2 Replace with new CC front and back cards that are identical to the current active CC. (Replacement of back card only applies to BCC.)

---

Note After Step 2, the node contains a mix of an old type CC and the new type CC. This condition is permitted only while the standby updates to the new CC are in progress, which takes less than one hour. The time during which this mixture of CC types exists must be kept to a minimum by immediately replacing the second old type CC with the matching one of the new type.

---

Step 3 Wait for the standby updates on the newly installed standby CC to complete.

Step 4 Issue a switchcc command to utilize the newly installed CC.

Step 5 Verify that the network is stable.

Step 6 Remove the current standby CC front and backcard. (Remove back card only applies to BCC.)

Step 7 Replace with new CC front and back cards that are identical to the current active CC. (Replace back card only applies to BCC.)

Step 8 Wait for the standby updates on the newly installed standby CC to complete.

The CC physical upgrade is now complete.

Step 9 With the secondary card in the standby state, cause a switchover using the switchcc command. This command tests that the hardware is working correctly.

---

To take advantage of the dual SIU when upgrading to the BCC-4, the BPX 8600 node must have a new backplane that has dual traces incorporating with the BCC-4.

The dspbpnv command can be issued to verify if the node has the new backplane or the old backplane. The following table details the bit fields for the BCC backplane NOVRAM format. The display of word 2 describes the backplane type.

16 Bit Word	Byte # (hex)	Contents
0	0,1	Hardware revision
1	2,3	Backplane Type (usually 0x65=101 decimal)
2	4,5	Backplane version (0x0000:old 0x0001:new)
3	6,7	Backplane serial number in ASCII - MSB
4	8,9	Backplane serial number in ASCII - MSB
5	A,B	Backplane serial number in LSB
6	C,D	Board FAB number, in ASCII - MSB
7	E,F	Board FAB number, in ASCII - LSB
8	10,11	Board FAB number, in ASCII - LSB
9	12,13	Board FAB number, in ASCII - LSB
A	14,15	Board FAB number, in ASCII - LSB
B	16,17	Board FAB number, in LSB
C	18,19	Unused
D	1A,1B	Unused
E	1C,1D	Unused
F	1E,1F	Checksum bytes - NOT SUPPORTED

The cnfbpnv command can be used to configure the backplane if backplane is enabled.

Limitations for Release 9.4.12

When an IGX is added as a feeder to a SES/BPX or MGX node, it will have a default node number. This node number may not be unique within the network. If it is not unique then it needs to be modified to a unique node number by issuing the CLI command "rnmnd <x>" where x should be unique with respect to all other auto-route nodes. To find the other node numbers, use the CLI command "dspnds +n". Failing to do so, CWM Databroker may have incorrectly formed hybrid connection database, and the CWMGUI may show the connection as incomplete.

Compatibility Matrix

This section contains compatibility information for Release 9.4.12.

Compatibility Notes

For a complete list of firmware revisions supported, see the Compatibility Matrix document, which is included in this release package.

MGX 8220 Firmware Compatibility

Table 3 lists the Cisco MGX 8220 firmware.

Table 3 Cisco MGX 8220 Firmware 

		System 5.0		System 4.1
PCB Description	CW2000 Name	Latest F/W	Min F/W	Latest F/W	Min F/W
ASC F/W	ASC	5.0.18 5.0.19	5.0.17	4.1.11	4.1.00
ASC Boot	ASC	1.0.03	1.0.01	1.0.03	4.0.04
ASC/2 FW	ASC	5.0.18	5.0.17	4.1.11	4.1.00
ASC/2 Boot	ASC	1.0.03	1.0.01	1.0.03	4.0.04
ASC/2F FW	ASC	5.0.18	5.0.17	4.1.11	4.1.05
ASC/2F Boot	ASC	1.0.03	1.0.01	1.0.03	1.0.01
BNM-T3	BNM-T3	n/a	n/a	n/a	n/a
BNM-E3	BNM-E3	n/a	n/a	n/a	n/a
BNM-155	BNM-155	n/a	n/a	n/a	n/a
FRSM-4T1	FRSM-4T1	4.0.22	4.0.19	4.0.23	4.0.13
FRSM-4E1	FRSM-4E1	4.0.22	4.0.19	4.0.23	4.0.13
FRSM-4T1-C	FRSM-4T1-C	4.0.22	4.0.19	4.0.23	4.0.13
FRSM-4E1-C	FRSM-4E1-C	4.0.22	4.0.19	4.0.23	4.0.13
FRSM Boot	FRSM-4T1	4.0.00	4.0.00	4.0.00	4.0.00
FRSM Boot	FRSM-4E1	4.0.00	4.0.00	4.0.00	4.0.00
FRSM Boot	FRSM-4T1-C	4.0.00	4.0.00	4.0.00	4.0.00
FRSM Boot	FRSM-4E1-C	4.0.00	4.0.00	4.0.00	4.0.00
SRM T1E1 (B)	SRM-T1E1	n/a	n/a	n/a	n/a
SRM 3T3	SRM-3T3	n/a	n/a	n/a	n/a
CESM-4T1	CESM-4T1	4.0.17	4.0.15	4.0.17	4.0.11
CESM-4E1	CESM-4E1	4.0.17	4.0.15	4.0.17	4.0.11
CESM Boot	CESM-4T1	4.0.01	4.0.01	4.0.01	4.0.00
CESM Boot	CESM-4E1	4.0.01	4.0.01	4.0.01	4.0.00
CESM-8T1	CESM-8T1	5.0.14	4.1.05	4.1.09	4.1.00
CESM-8E1	CESM-8E1	5.0.14	4.1.05	4.1.09	4.1.00
CESM-8 Boot	CESM-8T1	1.0.01	1.0.01	1.0.01	4.1.00
CESM-8 Boot	CESM-8E1	1.0.01	1.0.01	1.0.01	4.1.00
AUSM-4T1	AUSM-4T1	4.0.21	4.0.19	4.0.21	4.0.13
AUSM-4E1	AUSM-4E1	4.0.21	4.0.19	4.0.21	4.0.13
AUSM Boot	AUSM-4T1	4.0.00	4.0.00	4.0.00	4.0.00
AUSM Boot	AUSM-4E1	4.0.00	4.0.00	4.0.00	4.0.00
FRSM-8T1	FRSM-8T1	5.0.15	5.0.10	4.0.24	4.0.13
FRSM-8E1	FRSM-8E1	5.0.15	5.0.10	4.0.24	4.0.13
FRSM-8T1 Boot	FRSM-8T1	1.0.02	1.0.01	1.0.02	4.0.01
FRSM-8E1 Boot	FRSM-8E1	1.0.02	1.0.01	1.0.02	4.0.01
AUSM-8T1	AUSM-8T1	5.0.14	5.0.10	4.0.24	4.0.14
AUSM-8E1	AUSM-8E1	5.0.14	5.0.10	4.0.24	4.0.14
AUSMB-8T1	AUSMB-8T1	5.0.14	5.0.10	4.0.24	4.0.19
AUSMB-8E1	AUSMB-8E1	5.0.14	5.0.10	4.0.24	4.0.19
AUSM-8T1E1 Boot	AUSM-8T1	1.0.02	1.0.01	1.0.02	4.0.01
AUSM-8T1E1 Boot	AUSM-8E1	1.0.02	1.0.01	1.0.02	4.0.01
AUSM-8T1E1 Boot	AUSMB-8T1	1.0.02	1.0.01	1.0.02	4.0.01
AUSM-8T1E1 Boot	AUSMB-8E1	1.0.02	1.0.01	1.0.02	4.0.01
FRSM-HS1	FRSM-HS1	5.0.14	4.0.16	4.0.20	4.0.11
FRSM-HS1/B	FRSM-HS1/B	5.0.14	4.0.16	4.0.20	4.0.11
FRSM-HS1 Boot	FRSM-HS1	1.0.01	1.0.01	1.0.01	4.0.00
FRSM-HS1 Boot	FRSM-HS1/B	1.0.01	1.0.01	1.0.01	4.0.00
FRSM-HS2	FRSM-HS2	5.0.13	5.0.10	n/s	n/s
FRSM-HS2 Boot	FRSM-HS2	1.0.01	1.0.01	n/s	n/s
IMATM	IMATM-T3T1	n/s	n/s	4.0.22	4.0.13
IMATM	IMATM-E3E1	n/s	n/s	4.0.22	4.0.13
IMATM	IMATMB-T1	5.0.14	5.0.10	4.0.22	4.0.13
IMATM	IMATMB-E1	5.0.14	5.0.10	4.0.22	4.0.13
IMATM Boot	IMATM-T3T1	n/s	n/s	1.0.02	4.0.01
IMATM Boot	IMATM-E3E1	n/s	n/s	1.0.02	4.0.01
IMATM Boot	IMATMB-T1	1.0.02	1.0.01	1.0.02	4.0.01
IMATM Boot	IMATMB-E1	1.0.02	1.0.01	1.0.02	4.0.01

MGX 8850 1.1/1.2 Firmware Compatibility

Table 4 lists the Cisco MGX 8850 Release 1.1/1.2 firmware.

Table 4 Cisco MGX 8850 Release 1.1/1.2 Firmware 

PCB Description	CW2000 Name	Latest F/W	Min F/W
PXM1	PXM-1	1.2.21	1.1.40
PXM1-2-T3E3	PXM1-2T3E3	1.2.21	1.1.40
PXM1-4-155	PXM1-4OC3	1.2.21	1.1.40
PXM1-1-622	PXM1-OC12	1.2.21	1.1.40
MGX-SRM-3T3/B	SRM-3T3	n/a	n/a
MGX-SRM-3T3/C	SRM-3T3	n/a	n/a
AX-CESM-8E1	CESM-8E1	10.2.21	10.0.21
AX-CESM-8T1	CESM-8T1	10.2.21	10.0.21
MGX-AUSM-8E1/B	AUSMB-8E1	10.2.21	10.0.21
MGX-AUSM-8T1/B	AUSMB-8T1	10.2.21	10.0.21
MGX-CESM-T3	CESM-T3	10.2.21	10.0.21
MGX-CESM-E3	CESM-E3	10.2.21	10.0.21
AX-FRSM-8E1/E1-C	FRSM-8E1	10.2.21	10.0.21
AX-FRSM-8T1/T1-C	FRSM-8T1	10.2.21	10.0.21
MGX-FRSM-HS2	FRSM-HS2	10.2.21	10.0.22
MGX-FRSM-2CT3	FRSM-2CT3	10.2.21	10.0.22
MGX-FRSM-2T3E3	FRSM-2T3	10.2.21	10.0.22
MGX-FRSM-2T3E3	FRSM-2E3	10.2.21	10.0.22
MGX-FRSM-HS1/B	FRSM-HS1/B	10.2.21	10.0.21
MGX-VISM-8T1	VISM-8T1	2.0.(1)	1.5.05
MGX-VISM-8E1	VISM-8E1	2.0.(1)	1.5.05
MGX-RPM-128M/B	RPM	12.2(15)T2	12.2(4)T
MGX-RPM-PR	RPM	12.2(15)T2	12.2(4)T
CWM	—	12.0.00 P1.1	12.0.00

MGX 8230 1.1/1.2 Firmware Compatibility and
MGX 8250 1.1/1.2 Firmware Compatibility

Table 5 lists the MGX 8230 and MGX 8250 firmware.

Table 5 Cisco MGX 8230/8250 Release 1.1/1.2 Firmware 

PCB Description	CW2000 Name	Latest F/W	Min F/W
PXM1	PXM-1	1.2.21	1.1.40
PXM1-2-T3E3	PXM1-2T3E3	1.2.21	1.1.40
PXM1-4-155	PXM1-4OC3	1.2.21	1.1.40
PXM1-1-622	PXM1-OC12	1.2.21	1.1.40
MGX-SRM-3T3/C	SRM-3T3	n/a	n/a
AX-CESM-8E1	CESM-8E1	10.2.21	10.0.21
AX-CESM-8T1	CESM-8T1	10.2.21	10.0.21
MGX-AUSM-8E1/B	AUSMB-8E1	10.2.21	10.0.21
MGX-AUSM-8T1/B	AUSMB-8T1	10.2.21	10.0.21
MGX-CESM-T3	CESM-T3	10.2.21	10.0.21
MGX-CESM-E3	CESM-E3	10.2.21	10.0.21
AX-FRSM-8E1/E1-C	FRSM-8E1	10.2.21	10.0.21
AX-FRSM-8T1/T1-C	FRSM-8T1	10.2.21	10.0.21
MGX-FRSM-HS2	FRSM-HS2	10.2.21	10.0.22
MGX-FRSM-2CT3	FRSM-2CT3	10.2.21	10.0.22
MGX-FRSM-2T3E3	FRSM-2T3	10.2.21	10.0.22
MGX-FRSM-2T3E3	FRSM-2E3	10.2.21	10.0.22
MGX-FRSM-HS1/B	FRSM-HS1/B	10.2.21	10.0.21
MGX-VISM-8T1	VISM-8T1	3.1.(1)	1.5.05
MGX-VISM-8E1	VISM-8E1	3.1.(1)	1.5.05
MGX-RPM-128M/B	RPM	12.2(15)T2	12.2(4)T
MGX-RPM-PR	RPM	12.2(15)T2	12.2(4)T
CWM	—	12.0.00 P1.1	12.0.00

BPX 8600 Firmware Compatibility

Table 6 lists the BPX firmware.

Table 6 Cisco BPX Firmware 

PCB Description	dspcds Name	Card Name in FW Image	Model	Latest F/W	Min F/W
BCC-3-64 boot	BCC-3	BCC	D	HDM	HDM
BCC4 boot	BCC-4	BCC	E	HEM	HEM
BCC4-128 boot	BCC-4	BCC	H	HHM	HHM
ASI 2T3/2E3	ASI-T3	ASI	B	n/s	n/s
ASI 2T3/2E3	ASI-E3	ASI	B	n/s	n/s
ASI 2T3/2E3	ASI-T3	ASI	C	UCF	UCF
ASI 2T3/2E3	ASI-E3	ASI	C	UCF	UCF
ASI-155	ASI-155	ASI-155	B	n/s	n/s
ASI-155-E	ASI155E	ASI-155	D	n/s	n/s
ASI-155-E	ASI155E	ASI-155	E	WEC	WEC
ASI-155	ASI-155	ASI-155	H	WHC	WHC
ASM	ASM	—	A	GAC	GAC
BXM-BME	BME	BME	K	N/S	N/S
BXM-T3-8/12	BXM-T3	BXM	F	MFY	MFW
BXM-E3-8/12	BXM-E3	BXM	F	MFY	MFW
BXM-155-4/8	BXM-155	BXM	F	MFY	MFW
BXM-622/622-2	BXM-622	BXM	F	MFY	MFW
BXM-T3-8E/12E/12EX	BXM-T3	BXM	F	MFY	MFW
BXM-E3-8E/12E/12EX	BXM-E3	BXM	F	MFY	MFW
BXM-155-4D/8D/4DX/8DX	BXM-155	BXM	F	MFY	MFW
BXM-622-2D/DX/2DX	BXM-622	BXM	F	MFY	MFW
BNI-3T3/3E3	BNI-T3	BNI	C	TCM	TCM
BNI-3T3/3E3	BNI-E3	BNI	C	TCM	TCM
BNI-155	BNI-155	BNI-155	B	VBR	VBR
BNI-155-E	BNI155E	BNI-155	D	VDR	VDR

IGX 8400 Firmware Compatibility

Table 7 lists the IGX firmware.

Table 7 Cisco IGX Firmware 

PCB Description	dspcds Name	Card Name in Firmware Image	Model	Latest F/W	Min F/W
NPM 32 boot	NPM	NPM	B	RBS	RBS
NPM 64 boot	NPM	NPM|NPM-64	C	RCS	RCS
NPM-B 32 boot	NPM	NPM|NPM-32B	E	RES	RES
NPM-B 64 boot	NPM	NPM|NPM-64B	F	RFS	RFS
IGX-NTM	NTM	NTM	E	NJA	NEK
IGX-NTM (B)	NTM	NTM	F	NKA	NFK
IGX-UXM	UXM	UXM	B	ABT	ABJ
IGX-UXM	UXM	UXM	C	ACK	ACH
IGX-UXME	UXM	UXM	B	ABT	ABJ
IGX-UXME	UXM	UXM	C	ACK	ACH
IGX-HDM	HDM	HDM	C	SCF	SCF
IGX-LDM	LDM	LDM	C	LCC	LCC
IGX-CVM-DS0A	CVM	CVM	A	DAF	DAF
IGX-CVM	CVM	CVM	B	DBF	DBF
IGX-CVM-TT	CVM	CVM	C	DCA	DCA
IGX-FRM	FRM	FRM	D	FDZ	FDZ
IGX-FRM-31	FRM	FRM-31	E	FEZ	FEZ
IGX-FRM-2	FRM	FRM-2	F	FFD	FFD
FRM(B)	FRM	FRM	H	FHB	FHB
IGX-FRM	FRM	FRM	J	FJB	FJB
IGX-FRM-31	FRM	FRM-31	K	FKB	FKA
IGX-UFM-4C/8C	UFM	UFM-C	A	ZAT	ZAN
IGX-UFM-4C/8C	UFM	UFM-C	B	ZBD	ZBA
IGX-UFM-U	UFMU	UFM-U	A	YAL	YAJ
IGX-UFM-U	UFMU	UFM-U	B	YBC	YBA
IGX-URM	URM	URM	A	XAB	XAA
IGX-URM	URM	URM	B	XBC	XBB
IGX-UVM	UVM	UVM	D	DDF	DDF
IGX-UVM1	UVM	UVM	E	DEF	DEE

1 IGX-UVM model E supersedes models A, B, and C firmware. A, B, and C are obsolete and should not be used.

MGX 8220 5.0 Hardware Compatibility

Table 8 lists the Cisco MGX 8220 hardware.

Table 8 Cisco MGX 8220 Hardware 

Card Type	Hardware Revisions	Image Type
ASC	AH, AJ, AK, AL, AM, AN, AP, AR	ASC
ASC/B	AN	ASC
ASC2	BA, BB, BC, BD, BE, BF	ASC
ASC2F	BA, BB, BC, BD, BE, BF	ASC
BNM-T3	AJ, BA, BB, BC, BD	ASC
BNM-T3/B	BE, BF	ASC
BNM-E3	AA, AB, AC	ASC
BNM-E3/B	AD, AE	ASC
BNM-155	AA, AB, AC, AD, AE, AF, AH	ASC
SRM-T1E1	AB, AC, BA, BB, BC	ASC
SRM-T1E1/B	BD	ASC
SRM-3T3, SRM-3T3/B, SRM-3T3/C	BA, BB, BC, BD, BE, BF	ASC
FRSM-4T1E1	AJ, BK, BL, BM, BN, BP, BQ, CA, CB, CC, CE	ASC
FRSM-8T1E1	AA, AB, AC	FRSM
FRSM-HS1	AA, AB, AC, AD, AE, AH, AJ	FRSM-8T1E1
FRSM-HS1/B	AA	FRSM-HS1
FRSM-HS2	800-029099-03 AO, 800-02909-04 AO	FRSM-HS2
CESM-RT1E1	AA, BA, BB, BC	CESM
AUSM-4T1E1	AA, AB, AC, BA, BB, BC, BD	AUSM
AUSM-8T1E1	AA, AB, AC, AD, AE, AF	AUSM-8T1E1
AUSM-8T1E1/B	AA	AUSM-8T1E1
IMATM-8T1E1	AA, AB, AC, AD, AE, AF, AG	IMATM8
IMATM-8T1E1/B	AA, AB, AC, AD, AE, AF	IMATM8
CESM-8T1E1	AA, AB, AC	CESM-8T1E1

BPX 8600 Hardware Compatibility

Table 9 lists the Cisco BPX hardware.

Table 9 Cisco BPX Hardware 

Card Type	Part Numbers	Latest H/W	Min. H/W
Controller Cards
BPX-BCC-64M	800-04008-04	A	A
BPX-BCC-BC	73-211380-00	D	A
BPX-BCC-3-64M	73-3720-02	R	J
BCC-3BC	800-02916-01	E	A
BPX-BCC4V	800-03580-06	E	C
BPX-BCC-4V/B	800-06483-02	C	A
ASI-2T3	73-216330-00	F	A
ASI-2E3	73-216330-01	F	A
ASI-155E	73-214250-00	H	F
ASI-155E	73-218100-02	J	A
Alarm Group
BPX-ASM	800-04009-01	C	A
BPX-ASM-BC	73-211910-00	C	A
ASM-LM	800-211910-10	B	A
Broadband Switch Group
BPX-BME	800-02855-04	B	A
BPX-BXM-T3-8	800-02777-07	J	B
BPX-BXM-T3-8E	800-03933-02	A	A
BPX-BXM-E3-8	800-02779-07	J	B
BPX-BXM-E3-8E	800-03928-02	A	A
BPX-BXM-T3-12	800-02776-07	J	B
BPX-BXM-T3-12E	800-03931-02	A	A
BPX-BXM-T3-12EX	800-03934-02	A	A
BPX-BXM-E3-12	800-02778-07	J	B
BPX-BXM-E3-12E	800-03929-02	A	A
BPX-BXM-E3-12EX	800-03930-02	A	A
BPX-T3/E3-BC	73-2759-02	A	A
BPX-BXM-155-8	800-02664-07	J	B (C for APS)
BPX-MMF-155-8-BC	800-03255-01	B	A
BPX-SMF-155-8-BC	800-03257-01	B	A
BPX-SMFLR-155-8-BC	800-02593-01	B	A
BPX-BXM-155-4	800-02666-07	J	B (C for APS)
BPX-BXM-E-155-4D	800-03094-02	A	A
BPX-BXM-E-155-8D	800-03092-02	A	A
BPX-BXM-E-155-4DX	800-03093-02	A	A
BPX-BXM-E-155-8DX	800-03091-02	A	A
BPX-MMF-155-4-BC	800-03256-02	B	A
BPX-SMF-155-4-BC	800-03258-01	B	A
BPX-SMFLR-155-4-BC	800-02594-02	B	A
BPX-BXM-622	800-02646-10	M	D (E for APS)
BPX-BXM-622-2	800-02638-10	M	D (E for APS)
BPX-BXM-E-622-2D	800-03150-02	A	A
BPX-BXM-E-622-DX	800-03151-02	A	A
BPX-BXM-E-622-2DX	800-03149-02	A	A
BPX-622-2-BC	73-2884-01	D	A
BPX-SMF-622-BC	800-03249-01	C	A
BPX-SMF-622-2-BC	800-03251-01	C	A
BPX-SMFLR-622-BC	800-03250-01	C	A
BPX-SMFLR-622-2-BC	800-03252-01	D	A
BPX-XLR-622	800-02738-01	C	A
BPX-XLR-622-2	800-02739-01	C	A
BPX-BME-OC12	73-2469-07	F	A
RDNT-SMF-155-4R	800-03677-01	J	A
RDNT-SMF-155-8R	800-03679-01	K	A
RDNT-LR-155-8R	800-03678-01	J	A
RDNT-LR-622-2R	800-03676-01	F	A
RDNT-SMF-622R	800-03675-01	F	A
RDNT-SMF-622-2R	800-03674-01	J	A
BPX-STM1-EL-4	800-03716-02	A	A
BNI-3-T3/C	800-02858-02	A	A
BNI-3-E3/C	800-02859-02	A	A
BNI-155E	73-218100-01	K	A
BNI-2-155/B	73-4133-01	L	L
BPX-T3/E3	800-03058-02	E	A
BPX-E3-BC	73-213070-01	E	A
BPX-MMF-2-BC	73-214290-00	D	A
BPX-SMF-2-BC	73-216270-00	D	A
BPX-SMFLR-2-BC	73-216270-01	D	A
SMF-LM-OC3	800-216270-10	C	A
SMF-LM-OC3-LR	800-216270-11	C	A
MMF-LM-OC3	800-214290-10	B	A
LM-3T3	800-213070-10	D	A
LM-3E3	800-213070-11	D	A

IGX 8400 Hardware Compatibility

Table 10 lists the IGX hardware.

Table 10 Cisco IGX Hardware 

Card Type	Part Numbers	Latest H/W	Min. H/W	Comments
Controller Cards
IGX-NPM-32	73-2894-01	W	A	—
IGX-NPM-64	73-2895-01	W	A	—
IGX-NPM-32B	73-2554-04	L	A	—
IGX-NPM-64B	73-2363-02	C	A	—
IGX-SCM	73-3341-01	Y	A	Revision X or later for nodes with UXM IMA trunks
Alarm Group
IGX-ARM	73-218230-00	B	A	—
BC-512011	73-212360-00	D	A	—
Trunk Group
IGX-NTM	73-2296-04	E	A	—
BC-6271A-TI	73-207380-00	M	A	—
BC-6171A-E1	73-207370-01	P	A	—
BC-6083A-SR	73-208540-00	J	A	—
BC-550150-Y1	73-210820-01	D	A	—
ACM1	73-2921-03	W	A	—
BC-571110A-T3	73-2879-01	L	A	—
BC-571210A-E3	73-2679-01	K	A	—
BC-571310A-E2	73-215940-00	D	A	—
BC-571410A-HSSI	73-216370-00	A	A	—
IGX-UXM	73-2511-03	D	A	—
IGX-UXM-E	—	A	A	—
BC-UAI-4-155-SMF	73-2703-03	D	A	—
BC-UAI-4-155-MMF	73-2705-03	D	A	—
BC-UAI-2-155-SMF	73-2699-03	C	A	—
BC-UAI-2SMFXLR	—	A	A	—
BC-UAI-4SMFXLR	—	A	A	—
BC-UAI-6-T3	73-2952-02	A	A	—
BC-UAI-3-T3	73-2954-02	A	A	—
BC-UAI-6-E3	73-2953-02	A	A	—
BC-UAI-3-E3	73-2955-02	A	A	—
BC-UAI-8-E1-BNC	73-2932-02	C	A	—
BC-UAI-4-E1-BNC	73-3061-01	C	A	—
BC-UAI-8-T1-DB15	73-2941-02	C	A	—
BC-UAI-8-E1-DB15	73-2942-02	C	A	—
BC-UAI-4-T1-DB15	73-3059-01	C	A	—
BC-UAI-4-E1-DB15	73-3060-01	C	A	—
BC-UAI-4-STM1E	73-3364-02	A	A	—
Port Group
IGX-URM	800-06260-06	A	A	—
BC-2FE2V	800-06257-03	A	A	—
ACM1A	73-2930-03	W	A	—
IGX-HDM	73-2853-02	F	A	*Show SDP H/W Rev, DM=SDP+ACM2
ACM2	73-2922-03	T	A	—
BC-5082A-V35	73-2450-01	K	A	—
BC-5083A-RS449	73-204850-00	V	A	—
BC-5084B-RS232	73-2723-01	W	A	—
IGX-LDM	73-207250-00	K	A	*Show LDP H/W Rev, LDM=LDP+ACM1A
BC-5286A-RS232	73-207180-01	L	A	LDI-4RS232
BC-5287A-RS232	73-207180-00	L	A	LDI-8RS232
IGX-CVM-DSOA	73-3002-02	D	A*	*Show CDP H/W Rev, CVM=CDP+ACM1A
IGX-CVM-T1EC	73-3003-03	E	A*	*Show CDP H/W Rev, CVM=CDP+ACM1A
IGX-CVM-E1EC	73-209660-00	H*	A*	*Show CDP H/W Rev, CVM=CDP+ACM1A
IGX-CVM-TT	—	—	—	—
BC-6271A-TI	73-207380-00	M	A	—
BC-6171A-E1	73-207370-01	P	A	—
BC-550100-J1	73-210820-00	C	A	—
IGX-FRM	73-2517-03	N	A	—
IGX-FRM-31	73-2517-03	N	A	—
IGX-FRM-2	73-2519-01	M*	A*	*Show FRP H/W Rev, FRM-2=FRP+ACM1A
BC-6251B-V35	73-3253-01	M	A	FRI-4V.35-2
BC-6254A-X21	73-211440-00	H	A	FRI-X.21
BC-6355A-X21	73-214120-01	C	A	FRI-2X21
IGX-UFM-4C	73-2531-05	N	A	Needs a minimum of ZAS/ZBC Firmware
IGX-UFM-8C	73-2531-05	N	A	Needs a minimum of ZAS/ZBC Firmware
BC-UFI-8T1-DB15	73-2444-02	D	A	—
BC-UFI-8E1-DB15	73-2445-02	D	A	—
BC-UFI-8E1-BNC	73-2449-02	D	A	—
IGX-UFM-U	73-2349-04	D	A	—
BC-UFI-12V35	73-2711-01	D	A	—
BC-UFI-12X21	73-2712-01	D	A	—
BC-UFI-4HSSI	73-2693-01	C	A	—
IGX-UVM	73-2361-04	K	A	—
BC-UVI-2E1EC	73-2420-01	B	A	—
BC-UVI-2T1EC	73-2373-01	C	A	—
BC-UVI-2S1EC	73-2374-01	A	A	—

Anomalies in Release 9.4.12

This section describes the known and resolved anomalies in Release 9.4.12.

Known Anomalies in Release 9.4.12

Table 11 lists the known anomalies in Release 9.4.12 as of April 11, 2005.

Table 11 Known Anomalies in Release 9.4.12 

Bug ID	Description
CSCdv33406	Headline: BXM-155 with APS: Automatic loop release by switchyred command. Symptom: While the APS(1+1) and the loop clock was configured to the BXM cards, the loop clock seemed to be released automatically on the execution of switchyred command. Condition: APS 1+1 setup is present and switchyred is executed. Workaround: Manually set the loop clock to no once, and then set back to YES again.
CSCdx33468	Headline: dspcons shows connections but dspcon shows "connection does not exist". Symptom: dspcons shows all connections but dspcon shows "connection does not exist". Conditions: The network has the following software configuration: SWSW is 9.3.10 BXM FW is MFR Workaround: None.
CSCee35937	Headline: Frame Relay connection failed to route. Symptom: Frame Relay connection failed to route. Conditions: The connection going over the trunk was taken out for testing. When the trunks restored, the connection not routed over the trunk. It is in a failed state. Workaround: Issue a switchcc.
CSCeg08706	Headline: Maximum PVC LCNs not increasable using cnfrsrc giving an error. Symptom: When issuing the command cnfrsrc on a port to increase the maximum PVC LCNs, an error is received not allowing the action. Here is an example of the error: PVC Channels (3000) cannot exceed (148) The port group will be fine and dspchuse shows available PVC. Conditions: This problem is seen in a BPX node when they were configuring Maximum PVC LCNs value using cnfrsrc. This is particularly seen when VSI partitions on two port group. BXM card were enabled and disabled. Workaround: These are the possible workarounds: 1. Re-enable the disabled partitions to their previous values. 2. Reset the BXM card using resetcd slot <h> to recalculate the VSI LCN boundary. 3. Delete all of the VSI partitions on the card, and then re-add them. 4. Trigger a full rebuild using: resetcd <active-cc-slot> h Further Problem Description: Either switchcc or hitless rebuild will not provide workaround to this problem. As CSCsdm06886 DDTS fix, switchcc as a workaround has been removed and as CSCdt45926 DDTS fix, hitless rebuild workaround has been removed.
CSCeg38815	Headline: High BPX CPU during line alarms/BPX/SES configurations. Symptom: High CPU use during line failures. The problem has been produced and the thstats and rhstats have been captured. dspprf shows the hish usage: iSmpl 0 1 2 3 4 5 6 7 8 9 10 11 Tick 0 -19 -39 -60 -80 -100 -120 -140 -159 -180 -199 -220 IDLE 8.2 6.7 7.6 4.3 8.3 11.1 10.3 10.8 8.4 3.2 2.6 0.0 RSRC 28.0 29.0 25.8 27.5 27.6 27.5 30.0 25.5 29.1 26.4 31.4 23.1 CBUS 2.2 2.3 2.1 2.2 2.2 2.2 2.3 2.0 2.2 1.9 2.3 1.9 NETW 3.4 3.5 4.0 2.9 3.9 3.2 3.5 3.4 3.5 3.1 3.2 4.6 TRNS 52.8 55.2 53.5 58.5 53.1 51.3 49.2 53.6 50.9 58.7 50.4 60.1 FAIL 1.7 0.9 1.4 0.9 1.2 1.5 1.4 1.4 1.9 2.4 4.2 2.8 SNMP 0.1 0.1 0.1 0.7 0.1 0.1 0.1 0.1 0.1 1.0 2.2 2.4 PROT 0.7 0.4 0.6 0.4 0.5 0.3 0.5 0.4 0.5 0.4 0.5 2.7 TXIO 0.1 0.0 0.0 0.0 0.0 0.1 0.0 0.0 0.0 0.0 0.0 0.0 ILMI 0.2 0.3 0.2 0.2 0.3 0.2 0.3 0.3 0.2 0.2 0.2 0.2 SUMM 2.3 1.5 4.7 2.2 2.7 2.6 2.6 2.5 2.8 2.6 3.3 1.8 This Command: dspprfhist Conditions: Failure in a port. Node has more than 15k connections and the connections are mainly DAX connections with no rerouting involved. Workaround: None.
CSCeh06593	Headline: BCC aborting with Swerr 1M2 and 3M1 when running dspphyslnstat commands. Symptom: Running a Perl script to parse the BPX response from dspphyslnstathist and dspphyslnstatcnf results in a BCC abort 1M2 and 3M1 with associated 422, 502, 503, 532, 589, 923, swerrs 121 being seen. Aborts are very intermittent, and entering the commands directly via CLI shows no issue. Conditions: BPX network is running 9.2.34 with Perl script parsing dspphyslnstat outputs every hour. Workaround: Disable script.

Resolved Anomalies in Release 9.4.12

Table 12 lists the resolved anomalies in Release 9.4.12 as of April 11, 2005.

Table 12 Resolved Anomalies in Release 9.4.12 

Bug ID	Description
CSCdm38743	Addcon in a addjob does not let you configure PCR(0+1)
CSCdp26838	SWERR 2058 logged on standby NPM, dspstatparms shows more statistics on standby NPM
CSCdt07203	Hitless rebuilds logged on a failed switchcc can fill hitless log
CSCdu15686	Diagnostics PortTest V35/X21
CSCdx93228	Error message 2004 on the switch
CSCdy49484	Active BCC taking software error 992 continuously
CSCdy54959	SW Error 551 clears only on reseating of the BCC card
CSCea41956	Standby BCC status became cleared in the cause of SWLOG 586
CSCea55566	dsptrkerrs reporting large amounts of COMM FAIL on trunks after switchcc
CSCea58058	addcon for an SIW conn does not work in a job from the Frame Relay side
CSCeb31595	One end of connection failed with one way PVC
CSCeb41182	Pass Sync not propagating correctly on trunk add
CSCeb48398	Toggling payload scrambling on a VT not implemented correctly
CSCeb69548	Loop in a UFM port could be deleted but stays in the connections
CSCeb87464	UXM E3 is flagging minor alarms for BIP-8s incorrectly
CSCec24228	cnftrk fails on port with multiple virtual trunks
CSCec27023	SWSW gives ICS related error message with 56k addcon on HDM
CSCec30644	IGX UXM IMA trunk not allocating correct DS0s when map changed
CSCec53390	Physical UBUs are incrementing on standby UFM after background diag test
CSCed21795	IGX/BPX QIR timeout value in cnffstparm
CSCed24965	Statistics 46 and 47 not collected for IMA line/port
CSCed41679	BXME—Upgrading LCNs to 60K fails
CSCed45736	Suddenly, all BXM and Standby BCC are removed
CSCed88906	Each 57 minutes a PNNI trunk goes down and up
CSCee03234	BPX rebuild due to UP failure on active BCC card
CSCee21672	Incorrect output for fpRteTrkRcvCap MIB
CSCee34625	TCP RST vulnerability unexpectedly close telnet session
CSCee39134	Loopback appears, cannot delete it
CSCef08257	BXM OC-3 HCS correctable error count missing in SNMP
CSCef19669	Active NPM keep on resetting and standby is stuck at downloading with 1M3 error
CSCef25628	Disable background test for FR cards when the tst dc allocated outside reserved
CSCef29422	Lost user commands after upgrade
CSCeg37046	BPX BXM corrupts VCCs > 4095 in VPC
CSCeg45987	Connections become incomplete after coldstart followed by warmstart
CSCin78524	User cannot set the value 32 in cnfsysparm 7 on IGX node

Anomalies in Release 9.4.10

This section describes the known and resolved anomalies in Release 9.4.10.

Known Anomalies in Release 9.4.10

Table 13 lists the known anomalies for Release 9.4.10.

Table 13 Known Anomalies in Release 9.4.10 

Bug ID	Description
CSCdk22430	Headline: Word 15 of bpnv checksum is not recalculate Symptom: Checksum word 15 of backplane nvram is not recalculated when words 0-14 are updated using cnfbpnv. Conditions: Observed with BPX 9.1.01. Workaround: No workaround is available at this time.
CSCdk62225	Headline: SWSW DSPPWR is incorrect for a DC Power Self Symptom: DSPPWR is incorrect for a DC Power Self Conditions: None Workaround: None
CSCdk63665	Headline: VAD parameters revert to default after upgrade to 8.4.30 Symptom: When upgrading from 8.1.72 the VAD parameters revert to the default values. Conditions: While upgrading Workaround: Need to manually enter values after upgrade
CSCdk65076	Headline: non fatal card errors when BXM-T3 is put in Symptom: Non fatal card errors when BXM-T3 was inserted Conditions: None Workaround: None
CSCdk90900	Headline: CWM: Connection Mgr makes the UXM go into alarm and resets when modifying connections Symptom: The UXM card on an IGX goes into alarm and resets if the connection was added using CLI and then modified using the Connection Manager. Conditions: Cisco WAN Manager 9.1.05 Patch 4 UXM in IGX SWSW 9.1.07 Workaround: The work around is to add connection using the Connection Manager and modify it using the CLI.
CSCdm00298	Headline: Abstract: Cannot Add/Modify ATM-ATM PVCs with PCR104268 through CWM Symptom: After line config change cant configure ATM-ATM PVC with PCR=104268 through CWM. Conditions: After changing the line conf. cell framing from PLCP to HEC on BXM-T3 line. Workaround: Should work via CLI, not dependent on robust message update.
CSCdm05505	Headline: post upgrade 8259-9106 ASI fail selftest w Self Test Timeout Occurred Symptom: Standby fail self-test following upgrade from 8259 to 9106 Conditions: None Workaround: Disable self-test
CSCdm22426	Headline: Commands which lock UI - dspbob - will cause jobs to fail without notice Symptom: While using jobs to down or up the connection based on a jobtrigger, the job will fail if dspbob is executed while the control signal toggle. Conditions: Observed with IGX 8.2.56. Workaround: Retrigger the job after dspbob.
CSCdm38743	Headline: Addcon in a addjob for CBR connection does not let you configure PCR(0+1) Symptom: While configuring an addcon in an addjob, no error message is display indicating that the line need to be up first. The error message appear if the addcon is done from the CLI. Condition: None Workaround: None
CSCdm40952	Headline: Two PVCs rerouted during switchcc in BPX network] Symptom: On a switchcc, the node will try to reroute some working connections not on their preferred route (dsprrst will show non-zero values). The reroute attempt will not be successful and the connections will continue to use their working path. Conditions: This will happen only when preferred routes are set up for the connections and these connections are not routed on their preferred routes. Workaround: If all connections are on their preferred route, this problem will not happen. To ensure that all connections are on their preferred route, execute "cnfpref * +" on that node - this will create a preferred route (same as the current route) for ALL the connections (including those which did not have preferred routes).
CSCdm71136	Headline: BDB Packet drop alarms are not forwarded by the SNMP Agent Symptom: Minor and major alarms for BDB packet drops on trunks are not forwarded to the remote network manager using the trap forwarding facility by the SNMP proxy agent. Conditions: Observed with IGX SWSW 9.1.12 and CWM 9.1.08. Workaround: No workaround available at this time.
CSCdm76279	Headline: Cisco View no Data for FR-RealTimeCounters on IGX Symptom: When Using CiscoView to view the FR-RealTimeCounter SpreadSheet only the first two columns are displayed correctly, the remaining columns are displayed as 1's. Conditions: All conditions are normal. Workaround: None
CSCdp26838	Headline: SWERR 2058 logged on standby NPM, dspstatparms shows more stats on stby NPM Symptom: Software errors 2058 are logged continuously on the standby NPM. If there is a switchcc, the errors will continue to be logged continuously on the active NPM. The node's event log shows "Standby NPM <slot> Update Completed" without an immediately preceding "NPM <slot> Removed" event logged. The dspstatparms display on the NPM logging the 2058 errors has a higher statistics count than the NPM which is not logging the errors. Conditions: An IGX running software release 9.1.xx. There may be a defect or an excessive number of standby CC updates which is causing the standby CC update queue to be flushed. The flushing of the standby CC update queue causes the standby CC to be completely updated without resetting the card. Due to this defect, the complete updating of the standby CC without a preceding reset may cause excess TFTP statistics to be enabled on the standby CC. If there enough excess TFTP statistics enabled, the TFTP memory will be depleted and software errors 2058 (BAD_TFTP_MEM_OUT - TFTP memory full) will be logged. Workaround: The excess statistics on the standby NPM can be removed by resetting the standby NPM. This will also stop the logging of the software error 2058s. If there is a higher statistics count on the active CC after the standby CC is updated, there may also be excess statistics on the active CC. These can be removed with a switchcc. See CSCdm12055, CSCdp07967, and CSCdm64863 for workarounds and corrections to defects that can cause the "Standby NPM <slot> Update Completed" event which precipitates the excess TFTP statistics.
CSCdp33698	Headline: CVM-TT(CVM model C): Got Agent Error: No Such Name when added voice connection Symptom: Connections of CVM-TT (CVM FW Model C) can not be created by Connection Manager. Conditions: CWM: 9.1.06, 9.1.07, 9.1.09 IGX: 9.1.xx Workaround: None
CSCdp44912	Headline: Upgrade 9.1.04 to 9.1.16 causes UXM Y-red cards to go into mismatch Symptom: Upgrade from IGX 9.1.04 to 9.1.16 causes UXM Y-red card to go into mismatch. Conditions: Same as above. Workaround: delyred can be performed to avoid this condition. Further Problem Description: Problem isolated "VC shaping" upgrade mechanism.
CSCdp48861	Headline: Polling for voice conn and line stats results in high TRNS RT usage Symptom: The customer may notice slow UI response, or a difficulty logging into the node using the normal VT session. The dspprfhist shows high RT usage in the TRNS process. The thstats shows high RT usage by state machine 55 (0x33). Conditions: This is due to statistics updates for voice connections. It may be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs). Workaround: The command off1 17 can be performed. This will stop the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats. If statistics must be collected, limit the number of statistics. Frame Relay statistics are collected at 5 minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1 minute intervals, but the following statistics are reported at 3 second intervals: 1. Seconds V.25 Modem On 2. Seconds DSI Enabled 3. Seconds Off-Hook 4. Seconds In Service
CSCdp61249	Headline: Bus errors logged at a high rate, filling the nodes event log Symptom: Event log fills with multiple bus error entries every minute. This may displace other entries which are of interest from the event log. Conditions: The IGX node has a bus error. Workaround: Correcting the bus error condition will stop the reporting of the errors to the event log.
CSCdp98648	Headline: CWM 92 equipment MGR does not support BXM enhance card type. Symptom: Equipment MGR cannot tell the difference between BXM legacy or enhance. Conditions: BPX nodes containing both legacy BXMs and Enhanced BXMs. Workaround: Log into the BPX node and do dspcd XX and determine from number of channel support. The enhanced version of the BXM card has 61K channels, and the BXM card has less than 61K channels.
CSCdr05291	Headline: Problems deleting feeder trunks via SNMP Symptom: switchIfService must be specified to delete feeder trunks, but not routing trunks. Conditions: This requirement confuses CiscoView users. Workaround: Use the CLI commands to delete feeder trunks.
CSCdr01353	Headline: AIS (BLU) from IMATM trunk causes comm break Symptom: BPXs with BXMs connected by AXIS IMATM can comm break following an IMA group failure even though other paths exist to the remote node. The comm break will clear quickly but can delay rerouting of conns to the remote node up to a minute. Conditions: A failure in 1 direction of the IMA T1's, producing AIS (BLU) alarm on BXM trunks, causes a comm break. A failure in both directions simultaneously causes the expected reroutes (and comm fail) in a timely manner. Workaround: Restrict CC traffic on these trunks.
CSCdr15925	Headline: A bit advertised may be incorrect after switchcc Symptom: A-bit may be advertised to CPE as active when it should be inactive after a switchcc/runrev. dspcons -fabit on switch shows A-bit is failed. Conditions: Switch has NNI connection(s) with A-bit failed, and there is a CC switch over. Workaround: The correct status will be sent if the connections is downed and upped (dncon/upcon). A reset of the endpoint card (FRM or UFM) will also cause the correct status to be sent.
CSCdr25278	Headline: Loss of Signal not properly indicated per UNI 3.1 Symptom: The SUT and EMS are not indicating LOS as per UNI 3.1. Conditions: None. Workaround: None.
CSCdr45021	Headline: BETA: Request to generate an alarm when an SES trunk use default SCT 1 Symptom: SCT 1 is default SCT reserved for MPLS. When an SES trunk is provisioned, if the default SCT is not changed to SCT 3, trunk will fail to come up. Conditions: A warning message in configuration screen to indicate that the default is SCT 1 for MPLS and should be changed to SCT 3 for SES will be useful. Workaround: Make sure that SES uplink uses SCT 3 as service class template.
CSCdt07203	Headline: Hitless rebuilds logged on a failed switchcc can fill hitless log Symptom: The hitless rebuild log filled up due to repeated failed switchccs. Conditions: A bad standby BCC is required. The node must be running at least 9.2. Workaround: Clear the hitless log with the command "dsphitless c" or switchcc less often so that the hitless rebuild log entries get a chance to age out of the log.
CSCdv33406	Headline: BXM-155 w/ APS: Automatic loop release by switchyred command. Symptom: While the APS(1+1) and the loop clock was configured to the BXM cards, the loop clock seemed to be released automatically on the execution of switchyred command. Condition: APS 1+1 setup is present and switchyred is executed. Workaround: Manually set the loop clock to no once, and then set back to YES again.
CSCdw04934	Headline: CLI switchyred command, took approximately 40 to 70 seconds to complete Symptom: switchyred sometimes took 40 to 70 seconds to complete. Conditions: Network with following software configuration: 9.3.3d MF02 Workaround: None Further Problem Description: After loading MF02, switchyred is taking 40 to 70 seconds to complete.
CSCdw07614	Headline: Date and time changed after runrev command was issued Symptom: Date and time changed during upgrade Conditions: 9.3.3b and 9.3.3d MF01 Workaround: none. Further Problem Description: date/time changed after runrev command issued on two different nodes. This was noticed doing dsplog, it showed the date and time changed then changed back.
CSCdx33468	Headline: dspcons shows connections but dspcon shows "connection does not exist". Symptom: dspcons shows all connections but dspcon shows "connection does not exist". Conditions: The network has the following software configuration: SWSW is 9.3.10 BXM FW is MFR Workaround: None.
CSCdx37714	Headline: After Runrev IGX hangs when performing Ungraceful upgrade. Symptom: When performing runrev on an IGX node with only one Processor (Ungraceful Upgrade), the node can hang in boot mode until a terminal is connected to the control port. This has been found on NPM32, NPM32B and NPM64 using latest rev S firmware for each of the Build models per card. Once a terminal is connected the screen will display "Transition to online in progress" and will recover with the new SWSW rev. In the node log you will often see the NPM has restarted due to either a watchdog or software abort, as opposed to Restarting due to Primary revision change. Conditions: Single NPM node with no connectivity via control port either by local or terminal server. Nodes can be heavily loaded or have no configuration on them other than name/number/date etc. Workaround: 1. The first workaround is already known and that is to have a terminal connected via the control port. (Not suitable in your scenario). This is the reason the problem has not been reported/documented before as discussions with other engineers and on our internal forums show that there are no examples of Single Processor IGX's having no connectivity via the control port. The Cisco Labs all have the Control Ports connected to a Terminal Server and customer examples of single node upgrades have had engineers onsite. 2. You can also recover the nodes remotely by using an Engineering command called "setimage". Use this command to set the SWSW level for use in code patches. Once the required upgrade SWSW level is set and the runrev command is issued, the node will again remain in boot mode but now can be connected via the Ethernet Port and the Setrev command can be issued to force the node to rebuild with the correct revision. 3. If you connect the AUX port to the Control Port using two standard 25pin D types and a terminal cable this also has the effect of making the node rebuild correctly with the New SWSW revision. If you wire the control port to the below specification you ensure the node rebuilds and comes back online with the new rev. Tests showed that inserting wires into the below pinout either before a runrev or after when the node is in boot will have the same effect. TX 2 ------------- 8 CD RTS 4 ----------5 CTS DSR 6 ---------20 DTR Pin Outs of the interface can be found at below URL: http://www.cisco.com/univercd/cc/td/doc/product/wanbu/igx8400/8_5/ic85/igxicbl. htm#xtocid483424 4 A further method of ensuring the nodes recover after a SWSW upgrade is to have a redundant NPM card. No nodes failed when node was configured in a redundant mode. After the above tests the same two card types were used in a single node and upgrades through 9.2.33, 9.2.38, 9.3.24 and 9.3.36 were performed without problems being encountered. 5. The best option found so far to get around this problem is to disable DTR in the cnfterm for the control port. This has also been found to recover the node after the runrev has been issued.
CSCdx84899	Headline: Software Errors 105/100 appeared with SES 1.1.75.103 attached Symptom: Software errors 100/105 appeared on the BPX with SES version 1.1.75.103. Conditions: Software error with the following software version configuration: SWSW 9.3.36 SES version 1.1.75.103 BXM FW MFR Workaround: None
CSCdx85868	Headline: delallsvcrsrc cause APS errors to be sent to CWM Symptom: After upgrading to 9.3.36 the customer had to issue the command delallsvcrsrc. When this was issued they saw messages for APS being generated in the CWM logs. 1022207183 62 Thu May 23 22:26:23 2002 node1 - Port Id 9.10, state clear on n ode node1 in network XYZ is modified.; .1.3.6.1.4.1.351.1.0.20067 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - Port Id 9.11, state clear on n ode node1 in network XYZ is modified.; .1.3.6.1.4.1.351.1.0.20067 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - APS Activated on network XYZ node1 Line 11.5, Working line: 11.5, Protection line: 12.5.; .1.3.6.1.4.1.351.1.0.20101 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - APS Activated on network XYZ node node1 Line 3.2, Working line: 3.2, Protection line: 4.2.; .1.3.6.1.4.1.351.1.0.20101 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - APS Activated on network XYZ node1 Line 11.1, Working line: 11.1, Protection line: 12.1.; .1.3.6.1.4.1.351.1.0.20101 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - APS Activated on network XYZ node1 Line 11.2, Working line: 11.2, Protection line: 12.2.; .1.3.6.1.4.1.351.1.0.20101 0 1022207183 62 Thu May 23 22:26:23 2002 node1 - APS Activated on network XYZ node1 Line 3.1, Working line: 3.1, Protection line: 4.1.; .1.3.6.1.4.1.351.1.0.20101 0 Conditions: The BPX was running 9.3.36 and the effecting command was delallsvcrsrc command. Workaround: None
CSCdx93228	Headline: Error message 2004 on the switch Symptom: Concord's Network Health tool gets SNMP errors from the IGX's SNMP agent. Conditions: With SWSW 9.1.12. Workaround: None. Further Problem Description: error message 2004
CSCdy79353	Headline: Spare bandwidth not fairly allocated between AutoRoute and MPLS traffic Symptom: Spare bandwidth is not fairly allocated between AutoRoute and MPLS traffic. MPLS traffic will have access to all of the spare bandwidth limiting autoroute traffic to its static load. Conditions: AutoRoute with MPLS overlay Workaround: Customer installed MPLS only trunks Further Problem Description: PER 7127 has been raised
CSCdz87003	Headline: Test Delay Granularity not accurate Symptom: UXM testdelay granularity Conditions: No special environment. Workaround: No workaround
CSCea00485	Headline: Upgrade from 9.2.34 to 9.3.24 APS lines show on their PROT incorrectly Symptom: Upgrading BPX network from 9.2.34 to 9.3.24 all APS configured BXM 155 DX cards showed to be on their PROT lines after the upgrade. No errors were recorded in either the node or CWM logs, and there was no indication of any switch taking place. Attempts to switch from PROT to WORK had no effect at changing the display, neither did issuing a switchcc. The only way to clear the condition was to switchapsln W-P and then switchapsln P-W using the force option. This suggests the problem is cosmetic only as no user traffic was effected when in the original state. Problem was only found during audit after network upgrade. Conditions: None Workaround: Workaround is to switchapsln W-P force, then switchapsln P-W force. Display should then read correctly.
CSCea33846	Headline: The point of Slot7 to 7 and 8 on Cross Point is NOT tested by tstber. Symptom: From 9.2.35, the following two points on Cross Point is NOT tested by tstber. Active BCC -> Active BCC Active BCC -> Standby BCC Conditions: None Workaround: 'tstber m' command. Example: tstber m 7 8 0 2 1 20 n m:Manual 7:Primary Slot 8:Secondary Slot 0:Destination Port 2:Qbin Number 1:destination Channel 20:BFrams to send n:Stop on errors The point of Slot 7 to 8 is tested by this command.
CSCea41956	Headline: Standby BCC status became Cleared in the cause of SWLOG 586. Symptom: Standby BCC status became 'Cleared' in the cause of SWLOG 586. Conditions: This symptom occurred BPX/IGX has NOT experienced switchcc or power cycle for 1243days. Workaround: resetcd <Standby BCC Slot #> h and switchcc before the symptom occur.
CSCea54762	Headline: AIS not reported by BPX dspcon, until dspchstats is executed Symptom: AIS not reported by BPX via dspcon command. If dspchstats command is issued on the connection, then dspcon will show the correct AIS state. Conditions: BPX running switch software 9.3.36. BXM firmware is MFT. Workaround: Issue dspchstats command prior to dspcon command.
CSCea55566	Headline: dsptrkerrs reporting large amounts of COMM FAIL on trunks after switchcc Symptom: After a switchcc on an IGX, most if not all trunks reporting large amounts of COMM FAILs using the dsptrkerrs command. The log does not indicate any COMM Breaks however. Conditions: IGX node is running 9.2.41 SWSW under normal load and condition is reporting large amounts of COMM FAILs after a switchcc is issued. Please note the errors only seem to occur during the instant the switchcc is in progress. The errors do not continue to increment once the switch is complete. Workaround: None at this time. Further Problem Description: None, see information above under the "Conditions" heading.
CSCea76950	Headline: Node Abort, following swerr 100, 502, 589 and 504. Symptom: Following a swerr 100, the node ran into memory management problems with led to an abort. This was indicated by swerr 502, 589 and 504 in quick succession. The abort was 1000003. A basic debug of the errors indicate that the swerr 100 was that the message does match command, i.e is invalid. Error 589 has Allocated memory block with string... 1000003 abort has Fault address of FACE Conditions: There are no specific conditions known to be required at this time. Network running normally with average loading and no reported maintenance or outage activity. Workaround: There appears to be a memory management error while handling the response mismatch error condition. If you can identify and avoid the mismatch error condition you can avoid the defect in handling the error condition.
CSCea87668	Headline: cnfrsrc allows configuring BW under the reserved value Symptom: After creating asymmetric connections cnfrsrc allows to configure AutoRoute bandwidth under the ingress needed traffic. Conditions: create an asymmetric connection in the port that has less egress bandwidth change the autoroute bandwidth to the egress bandwidth and the systems allows it and this is wrong because the ingress bandwidth is over this value. Workaround: Make external calculations and adjust the autoroute bandwidth to this
CSCeb08097	Headline: Deleting ATFXFST connection does not remove FCES from the configuration Symptom: If a ATFXFST is created from a UXM to a UFM and then FCES enabled the connection will start to transmit RM cells. If the connection is deleted and readded but FCES is left disabled (default setting) the connection automatically starts transmitting RM cells. Conditions: The network conditions are normal. The network only consists of IGX's running 9.2.41 switch software. It have also been tested with 9.3.45 the problem is the same. Workaround: The problem can be avoided by disabling FCES prior to deleting the connection. This ensures the connection is programmed correctly.
CSCeb22327	Headline: SWERR 1012 when reset standby and switchcc Symptom: Reset standby bcc and switchcc caused swerr 1012 dspchuse on the slot shows a negative value for the number of available chans. Conditions: SWSW: 9.3.40 BXM FW: M.F.T Workaround: None.
CSCeb22555	Headline: OAM AIS/RDI alarms do not clear in BPX network due to BFRAME header corruption Symptom: PVC failure causes AIS and RDI to be reported either side of BXM NNI. When failure clears not all PVC's recover from this alarm and stay in this state. Conditions: PVC failure causing AIS and RDI alarms to be triggered either side of BXM NNI. Heavily loaded network running 9.2.34 Workaround: None
CSCeb29615	Headline: Connections doesn't get programmed correctly if upcon command is issued. Symptom: PVC experience one-way traffic and rsh command indicate ingress QE threshold is set to 0. Conditions: The problem may occur if customer issue an upcon command COS 0 follow by a dncon COS 0, or CM state machine is disable. Workaround: RRTCON on master end.
CSCeb31595	Headline: One end of connection failed with one way PVC Symptom: Connection Ok on master end, but Failed on slave end. Conditions: Route concurrency level configured greater than 1 (cnfcmparm 29). Maybe seen after the connection reroutes. Reroute throttling may be a factor (cnfrrcpu). Workaround: Down/up or reroute connection to clear failure. Set route concurrency level to 1 to avoid failure.
CSCeb40932	Headline: UXM card did not switch to a redundant card even after the HW failure Symptom: Trunk 15.1 and 15.2 were in loss of signal Red. Customer had to do resetcd to switch to redundant card to 16. Conditions: SWSW 9.2.38, UXM OC3 card running BER FW revision Workaround: Perform resetcd
CSCeb41182	Headline: Pass Sync not propagating correctly on trunk add Symptom: When a UXM-T1 card has one trunk already configured on it, and we add another trunk, if the PASS SYNC value is different on each trunk end, the value does not propagate from the adding end to the terminating end as it should. Normally, if we have PASS SYNC YES on one trunk end and PASS SYNC NO on the other end, when we add the trunk, the adding end will dictate the value on the opposite end. This does occur with the first trunk on the card, but does not occur when additional trunks are added. Conditions: Occurs only when there is already a trunk in service on the card. Workaround: Either ensure that the trunk configuration matches on each end before adding the trunk, or manually configure one end with the desired PASS SYNC value, forcing a change on the other end.
CSCeb44498	Headline: Watchdog Timeout and 3M Abort. Symptom: Watchdog Timeout occurred on several nodes in the same network. The software log contains the following entries. 1. Error 3000000 01000432 3039E8D6 RSRC 9.3.11 05/30/03 20:03:02 2. Error 513 00000000 303A36FA CBUS 9.3.11 05/30/03 20:03:02 3. Er ror 502 301EBF18 303A38F6 CBUS 9.3.11 05/30/03 20:03:02 4. Error 589 00000005 303A39FA CBUS 9.3.11 05/30/03 20:03:02 5. Error 513 00000000 303A36FA CBUS 9.3.11 05/30/03 20:03:02 6. Error 502 301EBF18 303A38F6 CBUS 9.3.11 05/30/03 20:03:02 7. Error 589 00000005 303A39FA CBUS 9.3.11 05/30/03 20:03:02 8. Error 513 00000000 303A36FA CBUS 9.3.11 05/30/03 20:03:02 9. Error 502 301EBF18 303A38F6 CBUS 9.3.11 05/30/03 20:03:02 10. Error 589 00 000005 303A39FA CBUS 9.3.11 05/30/03 20:03:02 11. Error 513 0000 0000 303A36FA CBUS 9.3.11 05/30/03 20:03:02 12. Error 502 301EBF 18 303A38F6 CBUS 9.3.11 05/30/03 20:03:02 Conditions: System conditions are normal no event occurs immediately prior to the Watchdog Timeout taking place. Workaround: None
CSCeb48398	Headline: Toggling Payload Scrambling on a VT not implemented correctly Symptom: Toggling Payload scrambling on a VT from Yes to No has no affect. Subsequent toggling back to yes, actually disables it. From then on you are at the reverse of the displayed value. Conditions: This problem is observed when cnftrk is used to change the Payload Scrambling parameter on the Virtual Trunk and it is not the first virtual trunk on that physical interface. Workaround: Issue cnftrk twice with exactly the same value to correctly set the Payload Scrambling Value.
CSCeb50717	Headline: BCC4 switchover with swerr 52 Symptom: BPX BCC4 switchover, and it made 20 minutes for the switchover time. Conditions: SW error 52 was logged on Active BCC, after auto switching to Standby BCC that BCC also got SW error 52 Workaround: None

Resolved Anomalies in Release 9.4.10

Table 14 lists the resolved anomalies for Release 9.4.10.

Table 14 Resolved Anomalies in Release 9.4.10 

Bug ID	Description
CSCdu21342	RAS: add LMI/ILMI debug tools to display LMI/ILMI data structures
CSCdw37288	Enhance code to notify user of obsolete FTM card
CSCdw44810	event log for runrev initiated from remote node says loadrev
CSCdx92352	Changing peak for already enabled TFTP stats does not work
CSCdy17099	uninitialized variables used in gt_nxt_bndl_con()
CSCdy22026	memmap shows wrong value for space left in case of memory overflow
CSCdy35192	Minor alarm does not clear on CWM GUI BPX icon unless you log into the node
CSCdy50994	30 and 923 when cnftrkict/dsptrkict run on NTM slot that does not have a trunk up
CSCdz48325	auto yred switch occurs on LOS alarm.
CSCea04404	HEC line displays t3/636 rather than t3/690 - bandwidth limited
CSCea22154	upln on BXM-155 logs swerr 5105, inconsistent databases warning on dnln
CSCea32473	l and t options of dspconcnts wrongly show lns and trks alarms as masked.
CSCea36542	VCI=0 on overlapping resources created via sw cli not added in cwm db
CSCea50919	BPX, slotFrontCHCount snmp does not respond correctly to BXM-E
CSCea60732	failcd does not accept (self test) and (BUS) for stbybcc from ACTV cli
CSCea62029	SNMP for Data Connection returns fail for UVM card (connection addition)
CSCea71630	Runjob to configure trunk failing for UXM trunks
CSCea92940	conn stats are displayed as enabled/disabled on command cnfstatcon * * e/d
CSCeb02540	SNMP get query does not trigger a poll for any object in atmTrunkStatsTable
CSCeb04143	SNMP get for conns. cause polling even when corr. snmpstats are disabled
CSCeb34045	Under certain conditions, IGX may send incorrect ABIT alarm towards feeder
CSCin21585	atmEndPointIBS range is 0-24000, unable to set IBS to 0
CSCin32081	Enum missing for STS-12c sonetIfFrame in strata.mib
CSCin34650	cnfrsrc cli does not refresh properly
CSCin36369	swerr 534 on BPX node when dspconcnts t is don
CSCin36370	swerr 105 on powering off and powering on IGX node
CSCin36622	igx sends circuit line robust message with wrong logical port value
CSCin40238	Protocol by card field does not refresh on cnftrk
CSCin40978	PROJ: Incorporate SNMP stats for VCQ Full discards for BXM (PER5915)
CSCin43274	dncon/upcon with COS option should be accessed from SUPERGRP or higher levels
CSCin43311	If the conn type changed in cnfatmcls then prev conn types defaults are loaded
CSCin46239	dspconcnts p does not work properly on igx and igx feeders
CSCin47418	SWerr 514 and 589 on issuing dsprtrlog
CSCin47670	failcd options 2 and 3 do not work for active and stby BCC
CSCin48202	3M abort on dspch execution repeatedly

Anomaly Status Change from Previous Releases

Table 15 lists the anomalies that changed status as a result of the release of Release 9.4.10.

Table 15 Anomaly Status Change from Previous Releases 

Bug ID	Description
CSCdk83372	TFTP Download of Software abort with no status message. Duplicated to CSCdt52981, which was resolved in 9.3.30
CSCdx52484	CBR traffic got dropped on BPX side on ENNI link when there is congestion. Transferred to the BXM firmware known anomalies list.
CSCdx79141	chan allocation inconsistency between BXM and SES, Closed
CSCdy51972	switchyred on BXM while SES has chan alms gets alms stuck. Transferred to the BXM firmware known anomalies list.
CSCdz02751	UNKNOWN OAM Cell Rx, Unreproducible
CSCdz08271	Rx Port errors on ASI when line is upped but port is not, Junked
CSCdz36965	BXM fail after firmware burn. Transferred to the BXM firmware known anomalies list.
CSCea54019	Switchcc from BCC-3 to BCC-4 triggers comfailure on feeder trks, Closed
CSCea56662	addcon returns Other end QIR out of range for this end card. Duplicated to CSCin43311, which was resolved in 9.4.10
CSCea56907	inter card connection between two BXMs is not programmed correctly, Unreproducible
CSCea80645	Huge time drift for stats reset during high CPU usage, Closed

Additional Deliverables

SNMP MIB

The SNMP IGX/BPX switch SNMP MIB is being provided with the delivery of Release 9.4 Switch Software. The MIB is in standard ASN.1 format and is located in the ASCII text files agent.m, ilmi.m, ilmi_ctl.m, ilmiaddr.m, switch.m, swtraps.m, and errors.m which are included in the same directory as the Switch Software images. These files may be compiled with most standards-based MIB compilers.

Switch MIB changes of Release 9.4.00

atmTrunks

New object

atmTrkAal5FdrTrk

A new MIB variable atmTrkAal5FdrTrk has been added to the atmTrunks table.

atmTrunks OBJECT-TYPE

SYNTAX SEQUENCE OF AtmTrkEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "A list of atmTrk interfaces"

--DEFAULT test-function test_atmrtetrktable

--DEFAULT next-function next_atmrtetrktable

--DEFAULT get-function get_atmrtetrktable_%t

::= { trunkServiceObjects 2 }

atmTrkEntry OBJECT-TYPE

SYNTAX AtmTrkEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "A interface entry"

INDEX { switchIfIndex }

::= { atmTrunks 1 }

AtmTrkEntry ::=

SEQUENCE {

....

atmTrkVTPathFailReason INTEGER,

atmTrkHcfShift INTEGER,

atmTrkMaxXmitRate INTEGER,

atmTrkAal5FdrTrk INTEGER

}

atmTrkAal5FdrTrk OBJECT-TYPE

SYNTAX INTEGER {

notApplicable(1)

enable(2),

disable(3)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Indicates if the trunk should be used as an AAL5 feeder trunk. If enabled, the LMI messages will be encapsulated in the standard ATM AAL5 cells. If disabled, the LMI messages will be encapsulated in the proprietary AutouRoute networking messages. This object is applicable for UXM feeder trunks on the IGX feeders only. The default value is disable(3). For UXM feeder trunks on the IGX routing nodes or any ATM routing trunks, notApplicable(1) will be returned."

--DEFAULT view-mask IGX_VIEW

:= {atmTrkEntry 71}

Modified objects

atmTrkType

A new read-only enum trkTypeAal5(12) has been added to the MIB variable atmTrkType in the atmTrunks table.




atmTrkType OBJECT-TYPE

SYNTAX INTEGER {

trkTypePHY(1),

trkTypeCBR(2),

trkTypeVBR(3),

trkTypeABR(4),

trkTypeIPXAF(5),

trkTypeAXISAF(6),

trkTypeESPAF(7),

trkTypeIGXAF(8),

trkTypeVSIAF(9),

trkTypePARAF(10),

trkTypeRTVBR(11),

trkTypeAal5(12)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION " The type of this trunk. The values of trkTypeCBR(2),

trkTypeVBR(3), and trkTypeABR(4), and trkTypeRTVBR are

writable for virtual trunks only. The trkTypePHY(1) value

is returned for a get-request on a physical trunk. Other

values are returned for a get-request on a feeder trunk."

::= { atmTrkEntry 9 }




Changed object

atmTrkOeNdType




A new enum ndTypeMGXH(10) has been added to the MIB variable atmTrkOeNdType in the atmTrunksTable.

atmTrkOeNdType OBJECT-TYPE

SYNTAX INTEGER {

]ndTypeOther(1),

ndTypeIPX(2),

ndTypeBPX(3),

ndTypeIPXAF(4),

ndTypeAXIS(5),

ndTypeIGX(6),

ndTypeIGXAF(7),

ndTypeESP(8),

ndTypePAR(9),

ndTypeMGXHub(10),

ndType8450(16)

}

ACCESS read-only

STATUS mandatory

DESCRIPTION " The type of node or shelf at the other end of this

trunk. Enumeration ndType8450 is obsolete."

::= { atmTrkEntry 13 }

shelfCnfgObjects

New objects

shelfCnfgTftpChanStats

shelfCnfgSnmpChanStats




Two new scalar objects (shelfCnfgTftpChanStats and shelfCnfgSnmpChanStats) have been introduced to enable or disable TFTP and SNMP statistics on ALL connections on a node.

shelfCnfgStatMaster OBJECT-TYPE

SYNTAX IpAddress

ACCESS read-only

STATUS mandatory

DESCRIPTION "This object provides the network manager the

IP address of the master statistics collection

management workstation."

--DEFAULT get-function get_shelfcnfg_%t

::= { shelfCnfgObjects 1 }

................................

................................

shelfCnfgTftpChanStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2),

NoChange(3)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect TFTP

statistics for all connections on node. If the user value is 'enable' then any configured

TFTP channel statistics will be enabled all connections. If the user value

is 'disable' then connections will ignore the TFTP channel statistics

configuration. The value of `NoChange' is always returned for a GET operation"

--DEFAULT test-function test_shelfcnfg

--DEFAULT get-function get_shelfcnfg_%t

::= { shelfCnfgObjects 40}

shelfCnfgSnmpChanStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2),

NoChange(3)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect SNMP

statistics for all connections on node. If the user value is 'enable' then

SNMP channel statistics will be enabled for all connections. If the user value

is 'disable' then connections will ignore the SNMP channel statistics

configuration. The value of `NoChange' is always returned for a GET operation "

--DEFAULT test-function test_shelfcnfg

--DEFAULT get-function get_shelfcnfg_%t

::= { shelfCnfgObjects 41}





shelfCnfgProfilerIdle OBJECT-TYPE

SYNTAX INTEGER

ACCESS read-only

STATUS mandatory

DESCRIPTION "The CPU idle time (in %). This system-wide object, which is maintained at all time after boot, is the idle time of the switch to be used to see how busy the switch is. This is calculated every interval set by the CLI command 'cnfprfparm'. This idle time is the same IDLE value displayed in 'dspprf' screen for the current interval"

--DEFAULT get-function get_shelfcnfg_%t

::= { shelfCnfgObjects 42 }

AtmEndptTable

New objects

Two new objects, atmEndptTftpStats and atmEndptSnmpStats, have been added to the atmEndptTable. These objects allow you to enable or disable TFTP and SNMP statistics on ATM connections.

atmEndptTable OBJECT-TYPE

SYNTAX SEQUENCE OF AtmEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "The ATM End-Point table. This table

is used to model a PVC end-point. This table

contains the traffic parameters for ATM end-point."

::= { switchConnection 8 }




atmEndptEntry OBJECT-TYPE

SYNTAX AtmEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "An entry in the ATM End-point table."

INDEX { atmEndptIndex }

::= { atmEndptTable 1 }





AtmEndptEntry ::=

SEQUENCE {

atmEndptIndex INTEGER,

atmEndptDesc DisplayString,

............

............

atmEndptTftpStats INTEGER

atmEndptSnmpStats INTEGER

}

atmEndptTftpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect TFTP

statistics for the connection. If the user value is 'enable' then any configured

TFTP channel statistics will be enabled for the connection. If the user value

is 'disable' then the connection will ignore the TFTP channel statistics

configuration. "

::= { atmEndptEntry 94 }





atmEndptSnmpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect SNMP

statistics for the connection. If the user value is 'enable' then

SNMP channel statistics will be enabled for the connection. If the user

value is 'disable' then the connection will ignore the SNMP channel

statistics configuration.

::= { atmEndptEntry 95 }

AtmQbinTable

New object

atmQbinClr




atmQbinTable OBJECT-TYPE

SYNTAX SEQUENCE OF AtmQbinEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "The ATM Port or Trunk Qbin Configuration table."

--DEFAULT test-function test_atmqbintable

--DEFAULT next-function next_atmqbintable

--DEFAULT get-function get_atmqbintable_%t

--DEFAULT view-mask BPX_VIEW | IGX_VIEW

::= { rsrcServiceObjects 2 }




atmQbinEntry OBJECT-TYPE

SYNTAX AtmQbinEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "An entry in the ATM Ports or Trunks Qbin Configuration table."

INDEX { switchIfIndex, atmQbinId }

::= { atmQbinTable 1 }




AtmQbinEntry ::=




SEQUENCE {

atmQbinId INTEGER,

atmQbinAdminStatus INTEGER,

atmQbinOperStatus INTEGER,

atmQbinMinBw INTEGER,

atmQbinDepth INTEGER,

atmQbinLoClp INTEGER,

atmQbinHiClp INTEGER,

atmQbinEfci INTEGER,

atmQbinTmpltCnfg INTEGER,

atmQbinVcShaping INTEGER,

atmQbinEpd INTEGER,

atmQbinClr INTEGER

}

...................................

atmQbinEpd OBJECT-TYPE

SYNTAX INTEGER {

EPD(1),

PPD(2) (CLP Hysterisis)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION

"Indicates whether Early Packet Discard (EPD) or Partial Packet Discard is enabled on this qbin."

::= { atmQbinEntry 11 }






atmQbinClr OBJECT-TYPE

SYNTAX INTEGER ( 1- 15)

ACCESS read-write

STATUS mandatory

DESCRIPTION "Indicates a number for Cell Loss Ratio (1 through 15). The configured number is the negative power to which the base 10 will be raised to obtain the value for CLR. For example a value of 8 would indicate a CLR = 1/10^8.

"

::= { atmQbinEntry 12 }




frEndptTable

New objects

Two new objects, frEndptTftpStats and frEndptSnmpStats, have been added to the frEndptTable. These objects allow you to enable or disable TFTP and SNMP statistics on Frame relay connections.

frEndptTable OBJECT-TYPE

SYNTAX SEQUENCE OF FrEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "The Frame Relay End-Point Configuration table.

This table is used to model a Frame Relay end-point.

The table contains the configuration parameters

required to create and configure a Frame Relay end-point."

--DEFAULT test-function test_frendpttable

--DEFAULT next-function next_frendpttable

--DEFAULT get-function get_frendpttable_%t

--DEFAULT view-mask IPX_VIEW

::= { switchConnection 5 }




frEndptEntry OBJECT-TYPE

SYNTAX FrEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "An entry in the Frame Relay End-point Configuration table."

INDEX { frEndptIndex }

::= { frEndptTable 1 }

FrEndptEntry ::=

SEQUENCE {

frEndptIndex INTEGER,

frEndptDesc DisplayString,

..................................................

..................................................

frEndptTftpStats INTEGER,

frEndptSnmpStats INTEGER

}

frEndptTftpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect TFTP statistics for the connection. If the user value is 'enable' then any configured TFTP channel statistics will be enabled for the connection. If the user value is 'disable' then the connection will ignore the TFTP channel statistics configuration. "

::= { frEndptEntry 48 }

frEndptSnmpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect SNMP statistics for the connection. If the user value is 'enable' then SNMP channel statistics will be enabled for the connection. If the user value is 'disable' then the connection will ignore the SNMP channel statistics configuration. "

::= { frEndptEntry 49 }




voiceEndptTable

New objects

Two new objects, voiceEndptTftpStats and voiceEndptSnmpStats, have been added to the voiceEndptTable. These objects allow you to enable or disable TFTP and SNMP statistics on voice connections.

voiceEndptTable OBJECT-TYPE

SYNTAX SEQUENCE OF VoiceEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "The voice channel connection table has Channel Connection

information. This table contains parameters which are

used to create a Voice connection and configure the channel."




--DEFAULT test-function test_voendpttable

--DEFAULT next-function next_voendpttable

--DEFAULT get-function get_voendpttable_%t

--DEFAULT view-mask IPX_VIEW

::= { switchConnection 13 }




voiceEndptEntry OBJECT-TYPE

SYNTAX VoiceEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "An entry in the voice Endpoint Channel Connection table."

INDEX { voiceEndptIndex }

::= { voiceEndptTable 1 }




VoiceEndptEntry ::=

SEQUENCE {

voiceEndptIndex INTEGER,

voiceOtherEndptIndex INTEGER,

......................................................

......................................................

voiceEndptTftpStats INTEGER,

voiceEndptSnmpStats INTEGER

}




voiceEndptTftpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect TFTP

statistics for the connection. If the user value is 'enable' then any configured

TFTP channel statistics will be enabled for the connection. If the user value

is 'disable' then the connection will ignore the TFTP channel statistics

configuration. "

::= { voiceEndptEntry 30 }

voiceEndptSnmpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect SNMP

statistics for the connection. If the user value is 'enable' then

SNMP channel statistics will be enabled for the connection. If the user value

is 'disable' then the connection will ignore the SNMP channel statistics

configuration. "

::= { voiceEndptEntry 31 }

dataEndptTable

New objects

Two new objects, dataEndptTftpStats and dataEndptSnmpStats, have been added to the dataEndptTable. These objects allow you to enable or disable TFTP and SNMP statistics on data connections.

dataEndptTable OBJECT-TYPE

SYNTAX SEQUENCE OF DataEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "The data End-Point table."

--DEFAULT test-function test_dataendpttable

--DEFAULT next-function next_dataendpttable

--DEFAULT get-function get_dataendpttable_%t

--DEFAULT view-mask IPX_VIEW

::= { switchConnection 17 }




dataEndptEntry OBJECT-TYPE

SYNTAX DataEndptEntry

ACCESS not-accessible

STATUS mandatory

DESCRIPTION "An entry in the data End-point table."

INDEX { dataEndptIndex }

::= { dataEndptTable 1 }

DataEndptEntry ::=

SEQUENCE {

dataEndptIndex INTEGER,

dataOtherEndptIndex INTEGER,

..................................................................

dataEndptTftpStats INTEGER,

dataEndptSnmpStats INTEGER

}




dataEndptTftpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect TFTP

statistics for the connection. If the user value is 'enable' then any configured

TFTP channel statistics will be enabled for the connection. If the user value

is 'disable' then the connection will ignore the TFTP channel statistics

configuration. "

::= { dataEndptEntry 29 }

dataEndptTftpStats OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "Specifies whether the user would like to collect SNMP

statistics for the connection. If the user value is 'enable' then

SNMP channel statistics will be enabled for the connection. If the user value

is 'disable' then the connection will ignore the SNMP channel statistics

configuration. "

::= { dataEndptEntry 30 }





rsrcPartiVsiBwOverbooking OBJECT-TYPE

SYNTAX INTEGER {

enable(1),

disable(2)

}

ACCESS read-write

STATUS mandatory

DESCRIPTION "This object is used to indicate what bandwidth a partition should advertise to a controller. If Enabled a partition advertises VI Rate and PNNI connections on that VSI partition can have a PCR up to the VI Rate. If disabled the partition advertises the VSI Max bandwidth and PNNI connections on that VSI partition can have a PCR up to the VSI Max bandwidth. The default is disabled."

--DEFAULT view-mask BPX_VIEW

::= { rsrcPartiEntry 14 }

Default Values

This section contains default values for the Cisco BPX and Cisco IGX nodes.

Cisco BPX 8600 Nodes

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




System-Wide Parameters




1 Max Time Stamped Packet Age (msec) ................................ 32

2 Allow CPU Starvation of Fail Handler .............................. No

7 Max Network Queuing Delay for HDM/LDM NTS Data connections (msec).. 32

9 Max Network Queuing Delay for CVM/UVM VAD connections (msec)....... 64

11 Max Network Queuing Delay for CVM/UVM non-VAD connections (msec)... 64

13 Enable Discard Eligibility......................................... No

14 Use Frame Relay Standard Parameters Bc and Be...................... No

22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm.. 0

23 Enable Connection Deroute Delay feature............................ No

24 Interval Statistics polling rate for ATM VCs....................... 5

25 Interval Statistics polling rate for ports on IGX nodes............ 5

26 Max Num of Nodes doing Simultaneous TFTP Configuration Save/Restore 2




This Command: cnfsysparm




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




1 Update Initial Delay [ 5000] (D) 16 Stats Memory (x 100KB) [   132] (D)

2 Update Per-Node Delay [30000] (D) 17 Standby Update Timer [    10] (D)

3 Comm-Break Test Delay [30000] (D) 18 Stby Updts Per Pass [   150] (D)

4 Comm-Break Test Offset [ 10] (D) 19 BusFail Monitor Window [    12] (D)

5 Network Timeout Period [ 1700] (D) 20 BusFail PollErr Thrhld [     0] (D)

6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [    60] (D)

7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [    50] (D)

8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [   560] (D)

9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [   280] (D)

10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [    56] (D)

11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [  7680] (D)

12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [   256] (D)

13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [     Y] (Y/N)

14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [     1] (D)

15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [    10] (D)

31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [   100] (D)

32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[  1000] (D)

33 Job Lock Timeout [ 60] (D) 48 Send Abit early [     N] (Y/N)

34 Max Via LCONs [50000] (D) 49 Abit Tmr Multiplier M [     0] (D)

35 Max Blind Segment Size [ 3570] (D) 50 Abit Tmr Granularity N [     3] (D)

36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [     N] (Y/N)

37 Max Mem on Stby Q (%) [ 33] (D) 52 CommBrk Hop Weight [    25] (D)

38 Stat Config Proc Cnt [ 1000] (D) 53 CB Fail Penalty Hops [     2] (D)

39 Stat Config Proc Delay [ 2000] (D) 54 Auto BXM upgrade [     Y] (Y/N)

40 Enable Degraded Mode [ Y] (Y/N) 55 LCN reprgrm batch cnt [   100] (D)

41 Trk Cell Rtng Restrict [ Y] (Y/N) 56 Dnld LanIP or NwIP [     Nw](Lan/Nw)

42 Enable Feeder Alert [ N] (Y/N) 57 IP Relay gateway node [     0] (D)

43 Reroute on Comm Fail [ N] (Y/N) 58 Max LAN Window (sec) [    60] (D)

44 Auto Switch on Degrade [ Y] (Y/N) 59 Max LAN Packets/Window [ 18000] (D)

45 Max Degraded Aborts [ 100] (D) 60 Extended Cline Object [     N] (Y/N)

                                        61 BXM Fake AIS Alarm [  N] (Y/N)




This Command: cnfnodeparm

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Index Status Function




1 Enabled Automatic TRK Loopback Test on Local/Remote Alarms

2 Enabled User Command Logging

3 Enabled Automatic Card Reset on Hardware Error

4 Enabled Card Error Record Wraparound

5 Disabled Card Test After Failure

6 Disabled Download From Remote Cisco StrataView Plus

7 Disabled Logging of conn events in local event log

8 Disabled Logging of conn events in Cisco StrataView Plus event log

9 Disabled Force Download From a Specific IP address





This Command: cnffunc





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Index Status Function




1 Disabled Configuration Save/Restore

2 Enabled ForeSight

3 Disabled Multiple VTs (1 session enabled)

4 Disabled Virtual Trunks

5 Enabled ABR standard with VSVD

6 Disabled Priority Bumping

7 Disabled Virtual Ports






This Command: cnfswfunc





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -

Type Freq Enable Inc Thresh Timeout Enable Inc Thresh

---- ----- -------- ------- ------- ------- -------- ------- -------

BCC 1600 Enabled 100 300 800 N/A 100 300

ASM 300 Disabled 100 300 60 N/A 100 300

BNI-T3 300 Enabled 100 300 150 N/A 100 300

BNI-E3 300 Enabled 100 300 150 N/A 100 300

ASI-E3 900 Enabled 100 300 800 Enabled 100 300

ASI-T3 900 Enabled 100 300 800 Enabled 100 300

ASI-155 900 Enabled 100 300 800 Enabled 100 300

BNI-155 300 Enabled 100 300 150 N/A 100 300

BXM 4000 Enabled 100 300 3000 Enabled 100 300






This Command: cnftstparm

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




8 Maximum Routing Bundle [ 90] (D)

9 Reroute Timer [ 3] (secs)

10 Reset Timer on Line Fail [ Yes]

11 Max Down/Up Per Pass [ 50] (D)

12 Down/Up Timer [30000] (msecs)

13 Max Route Errs per cycle [ 50] (D)

14 Time between Rrt cycles [ 5] (mins)

15 Max. Rrt Err cycles [ 10] (D)

16 Routing pause timer [ 0] (msecs)

17 Max msgs sent per update [ 10] (D)

18 Send SVC urgent msg [ No]

19 Max SVC Retry [ 0] (D)

20 Wait for TBL Updates [ 70] (100 msecs)

21 Max Derouting Bndl (0=all)[ 500] (D)

22 Enable Cost-Based Routing [ No]

23 Enable Route Cache Usage [ No]

24 Use Delay for Routing [ No]

25 # of reroute groups used [ 50] (D)

26 Starting size of RR grps [ 0] (CLU)

27 Increment between RR grps [ 100] (CLU)

28 CM updates app timeout [ 5] (10 secs)

29 Route concurrency level [ 1] (D)





This Command: cnfcmparm





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




1 Rmt Blk Freq (msec) [ 100] 16 FW Dnld Msgs/Block(dec) [ 4]

2 Rmt Blk Size (hex) [ 400] 17 Flash Write TO(msec) [ 16000]

3 Lcl Blk Freq (msec) [ 100] 18 Flash Erase TO(msec) [ 100]

4 Lcl Blk Size (hex) [ 400] 19 Erase Verify TO(msec) [ 16000]

5 Image Req Freq (msec) [ 10000] 20 Standby Flash TO(sec) [ 300]

6 Dnld Req Freq (msec) [ 10000] 21 Lcl Flash Init TO(msec) [ 1000]

7 Session Timeout (msec) [ 30000] 22 Flsh Write Blk Sz (hex) [ 10000]

8 Request Hop Limit (dec) [ 1] 23 Flsh Verfy Blk Sz (hex) [ 400]

9 Crc Throttle Freq (dec) [ 5000] 24 Chips Per Write/Erase [ 1]

10 Crc Block Size (hex) [ 400]

11 Rev Change Wait(dec) [ 0]

12 CCs Switch Wait(dec) [ 1000]

13 Lcl Response TO(msec) [ 5000]

14 Rmt Response TO(msec) [ 20000]

15 FW Dnld Block TO(msec) [ 50]





This Command: cnfdlparm





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




1. Logout Time ........... 120 minutes

2. VT Logout Time ........ 4 minutes

3. Prompt Time ........... 60 seconds

4. Command Time .......... 3 minutes

5. UID Privilege Level ... 6

6. Input Character Echo .. Enabled

7. Screen Update Time .... 10 seconds





This Command: cnfuiparm




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




1 Priority Bumping Enabled [ NO]

2 Priority Bumping Bundle [ 50] (D)

3 Priority Bumping Bands:

Band 1 [ 2] (D)

Band 2 [ 4] (D)

Band 3 [ 6] (D)

Band 4 [ 8] (D)

Band 5 [ 10] (D)

Band 6 [ 12] (D)

Band 7 [ 14] (D)





This Command: cnfbmpparm





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Function Number Status Function Number Status

Background Upcard 1 Enabled Conn Stat Sampling 15 Enabled

Background Updates 2 Disabled Neighbor Update Errs 16 Disabled

Standby Terminal 3 Enabled

Memory Protection 4 Enabled

Comm Break 5 Enabled

Comm Fail Test 6 Enabled

CRC Test 7 Enabled

Bus Fail Detection 8 Enabled

Line Diag 9 Enabled

Clock Restoral 10 Enabled

Cm_Rerouting 11 Enabled

Clock Routing 12 Enabled

Dynamic BW Allocation 13 Enabled

Modem Polling 14 Enabled

This Command: on1





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Function Number Status Function Number Status

Line Stat Sampling 1 Enabled Robust Alarm Updates 15 Enabled

Statistical Alarm 2 Enabled Realtime Counters 16 Enabled

Job Ready Checker 3 Enabled LAN Interface 17 Enabled

Configuration Backup 4 Enabled Update Standby Stats 18 Enabled

Standby Update 5 Enabled Telnet Access 19 Enabled

Downloader 6 Enabled Junction ID 20 Enabled

Cm Updates 7 Enabled Mult SV+/Routing Node 21 Disabled

Topo/Stat Updates 8 Enabled Simulated Fdr Trks 22 Disabled

Card Statistical Alms 9 Enabled Deroute Delay 23 Enabled

Card Stat Sampling 10 Enabled Auto Renum Fail Recov 24 Enabled

Address Validation 11 Enabled Card Simulation Tool 25 Disabled

ASM Stats Polling 12 Enabled

Port Stat Sampling 13 Enabled

Robust Updates 14 Enabled

Last Command: on2





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




Function Number Status

Trace Msg Sent 1 Disabled

Multi-DB Stby Updates 2 Enabled

Trace Conv Msg 3 Disabled

Region memory init 4 Disabled

VT Clk Switch Evt Log 5 Disabled

Load Bal on EqCost Rt 6 Disabled

Slve Endpt CWM Update 7 Disabled

Htls Rbld on SAR Fail 8 Enabled

Stat Poll on SNMP GET 9 Disabled

This Command: on3

BNI-T3

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 3.2 Config T3 [96000 cps] BNI-T3 slot: 3

Transmit Rate: 96000 VPC Conns disabled: --

Protocol By The Card: -- Line framing: PLCP

Hdr Type NNI: -- coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type:

Connection Channels: 1771 length: 0-225 ft.

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: No

F4 AIS Detection: -- Frame Scramble: --

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 3.2





Next Command:




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 3.2 Parameters

1 Q Depth - rt-VBR [ 242] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 8878] (Dec)

4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 3.2




Which parameter do you wish to change:

BNI-E3

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 10.2 Config E3 [80000 cps] BNI-E3 slot: 10

Transmit Rate: 80000 VPC Conns disabled: --

Protocol By The Card: -- Line framing: --

Hdr Type NNI: -- coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type:

Connection Channels: 1771 length: 0-225 ft.

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: Yes

F4 AIS Detection: -- Frame Scramble: --

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 10.2





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 10.2 Parameters

1 Q Depth - rt-VBR [ 202] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 8978] (Dec)

4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 10.2

BNI-155/155E

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 1.1 Config OC3 [353207cps] BNI-155 slot: 11

Transmit Rate: 353208 VPC Conns disabled: --

Protocol By The Card: -- Line framing: STS-3C

Hdr Type NNI: -- coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type: --

Connection Channels: 16050 length: --

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: Yes

F4 AIS Detection: -- Frame Scramble: Yes

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 1.1




Next Command:




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 1.1 Parameters

1 Q Depth - rt-VBR [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [15463] (Dec)

4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)

8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 1.1




Which parameter do you wish to change:




BXM-T3

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 5.6 Config T3 [96000 cps] BXM slot: 5

Transmit Rate: 96000 VPC Conns disabled: No

Protocol By The Card: No Line framing: PLCP

Hdr Type NNI: Yes coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type: --

Connection Channels: 256 length: 0-225 ft.

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: No

F4 AIS Detection: -- Frame Scramble: --

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 5.6





Next Command:




MAJOR ALARM





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 5.6 Parameters

1 Q Depth - rt-VBR [ 242] (Dec) 15 Q Depth - CBR [ 400] (Dec)

2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [10000] (Dec)

4 Q Depth - BData A [ 8000] (Dec) 18 Low CLP - CBR [ 60] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 80] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 5.6





Which parameter do you wish to change:

BXM-E3

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 3.1 Config E3 [80000 cps] BXM slot: 3

Transmit Rate: 80000 VPC Conns disabled: No

Protocol By The Card: No Line framing: --

Hdr Type NNI: Yes coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type: --

Connection Channels: 256 length: 0-225 ft.

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: Yes

F4 AIS Detection: -- Frame Scramble: --

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 3.1





Next Command:




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 3.1 Parameters

1 Q Depth - rt-VBR [ 202] (Dec) 15 Q Depth - CBR [ 400] (Dec)

2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [10000] (Dec)

4 Q Depth - BData A [ 8000] (Dec) 18 Low CLP - CBR [ 60] (%)

5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 80] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)

8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

Last Command: cnftrkparm 3.1





Next Command:




BXM-155

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 5.2 Config OC3 [353207cps] BXM slot: 5

Transmit Rate: 353208 VPC Conns disabled: No

Protocol By The Card: No Line framing: STS-3C

Hdr Type NNI: Yes coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type: --

Connection Channels: 256 length: --

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: Yes

F4 AIS Detection: -- Frame Scramble: Yes

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 5.2





Next Command:




sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 5.2 Parameters

1 Q Depth - rt-VBR [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)

2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [20000] (Dec)

4 Q Depth - BData A [10000] (Dec) 18 Low CLP - CBR [ 60] (%)

5 Q Depth - BData B [10000] (Dec) 19 High CLP - CBR [ 80] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)

8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 5.2

BXM-622

sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 11.1 Config OC12 [1412679cps] BXM slot: 11

Transmit Rate: 1412830 VPC Conns disabled: No

Protocol By The Card: No Line framing: STS-12C

Hdr Type NNI: Yes coding: --

Statistical Reserve: 5000 cps recv impedance: --

Idle code: 7F hex cable type: --

Connection Channels: 256 length: --

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Pass sync: Yes

Restrict CC traffic: No Loop clock: No

Link type: Terrestrial HCS Masking: Yes

Routing Cost: 10 Payload Scramble: Yes

F4 AIS Detection: -- Frame Scramble: Yes

Vtrk Type / VPI: -- / --

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 11.1





Next Command:





sw-node TRM Cisco BPX 8620 9.4.12 Apr. 4 2005 15:40 GMT




TRK 11.1 Parameters

1 Q Depth - rt-VBR [ 3533] (Dec) 15 Q Depth - CBR [ 1200] (Dec)

2 Q Depth - Non-TS [ 5297] (Dec) 16 Q Depth - nrt-VBR [10000] (Dec)

3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [40000] (Dec)

4 Q Depth - BData A [40000] (Dec) 18 Low CLP - CBR [ 60] (%)

5 Q Depth - BData B [40000] (Dec) 19 High CLP - CBR [ 80] (%)

6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)

7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)

8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)

9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)

10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)

11 High CLP - BData A [ 100] (%)

12 Low CLP - BData B [ 25] (%)

13 High CLP - BData B [ 75] (%)

14 EFCN - BData B [ 30] (Dec)

This Command: cnftrkparm 11.1





Which parameter do you wish to change:




Cisco IGX 8400 Nodes

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




System-Wide Parameters




1 Max Time Stamped Packet Age (msec) ................................ 32

2 Allow CPU Starvation of Fail Handler .............................. No

7 Max Network Queuing Delay for HDM/LDM NTS Data connections (msec).. 30

9 Max Network Queuing Delay for CVM/UVM VAD connections (msec)....... 64

11 Max Network Queuing Delay for CVM/UVM non-VAD connections (msec)... 64

13 Enable Discard Eligibility......................................... No

14 Use Frame Relay Standard Parameters Bc and Be...................... No

22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm.. 0

23 Enable Connection Deroute Delay feature ........................... No

24 Interval Statstics polling rate for ATM/Frame Relay VCs............ 5

25 Interval Statistics polling rate for ports......................... 5

26 Max Num of Nodes doing Simultaneous TFTP Configuration Save/Restore 4




This Command: cnfsysparm





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




1 Update Initial Delay [ 5000] (D) 16 CC Redundancy Cnfged [ Y] (Y/N)

2 Update Per-Node Delay [30000] (D) 17 MT3 Pass Through Relay [ Y] (Y/N)

3 Comm-Break Test Delay [30000] (D) 18 Nw Pkt Tx Rate (pps) [ 500] (D)

4 Comm-Break Test Offset [ 10] (D) 19 Stats Memory (x 100KB) [ 130] (D)

5 Network Timeout Period [ 1700] (D) 20 Standby Update Timer [ 10] (D)

6 Network Inter-p Period [ 4000] (D) 21 Stby Updts Per Pass [ 150] (D)

7 NW Sliding Window Size [ 1] (D) 22 Gateway ID Timer [ 30] (D)

8 Num Normal Timeouts [ 7] (D) 23 GLCON Alloc Timer [ 30] (D)

9 Num Inter-p Timeouts [ 3] (D) 24 Comm Fail Delay [ 60] (D)

10 Num Satellite Timeouts [ 6] (D) 25 Nw Hdlr Timer (msec) [ 100] (D)

11 Num Blind Timeouts [ 4] (D) 26 CBUS Delay (msec) [ 20] (D)

12 Num CB Msg Timeouts [ 2] (D) 27 SNMP Event logging [ Y] (Y/N)

13 Comm Fail Interval [10000] (D) 28 TFTP Grant Delay (sec) [ 1] (D)

14 Comm Fail Multiplier [ 3] (D) 29 TFTP ACK Timeout (sec) [ 10] (D)

15 Temperature Threshold [ 50] (D) 30 TFTP Write Retries [ 3] (D)

31 FRP Link Status Alarm [ Y] (Y/N) 46 Modem polling timer [ 1] (D)

32 Job Lock Timeout [ 60] (D) 47 Verify CBA for non-FRP [ N] (Y/N)

33 Max Via LCONs [20000] (D) 48 Send Abit early [ N] (Y/N)

34 Max Blind Segment Size [ 3570] (D) 49 Abit Tmr Multiplier M [ 0] (D)

35 Max XmtMemBlks per NIB [ 3000] (D) 50 Abit Tmr Granularity N [ 3] (D)

36 Max Mem on Stby Q (%) [ 33] (D) 51 CommBrk Hop Weight [ 25] (D)

37 Trk Cell Rtng Restrict [ Y] (Y/N) 52 CB Fail Penalty Hops [ 2] (D)

38 Stat Config Proc Cnt [ 1000] (D) 53 Dnld LanIP or NwIP [ Lan](Lan/Nw)

39 Stat Config Proc Delay [ 2000] (D) 54 IP Relay gateway node [ 0] (D)

40 Enable Degraded Mode [ Y] (Y/N) 55 Max LAN Window (sec) [ 60] (D)

41 Enable Rrt on Comm Fail[ N] (Y/N) 56 Max LAN Packets/Window [18000] (D)

42 Auto Switch on Degrade [ Y] (Y/N) 57 Default Redundant Lane [ N] (Y/N)

43 Max Degraded Aborts [ 100] (D)

44 Max Htls Rebuild Count [ 100] (D)

45 Htls Counter Reset Time[ 1000] (D)

This Command: cnfnodeparm





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




Index Status Function




1 Enabled Automatic CLN/PLN Loopback Test on Local/Remote Alarms

2 Enabled FDP Loopback button

3 Enabled User Command Logging

4 Enabled Automatic Card Reset on Hardware Error

5 Enabled TXR Model D Download

6 Enabled Card Error Record Wraparound

7 Disabled Card Test After Failure

8 Disabled Download From Remote CWM

9 Disabled Logging of conn events in local event log

10 Disabled Logging of conn events in CWM event log

11 Disabled Logging SVC Connection Events

12 Disabled Force Download From a Specific IP address

13 Disabled CDP WinkStart Signalling

14 Enabled Logging of Bus Diagnostic Events in local event log

15 Enabled Automatic Card Reset after Burnfw for CBI cards

16 Disabled Logging of router state events in CWM event log

This Command: cnffunc





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




Index Status Function




1 Disabled Repetitive Pattern Suppression

3 Enabled Frame Relay

4 Disabled Configuration Save/Restore

5 Disabled ForeSight

6 Disabled Frame Relay Network-to-Network Interface

7 Disabled Multiple VTs (1 session enabled)

8 Disabled Interface Shelf

9 Enabled Virtual Trunks

10 Disabled ABR standard with VSVD





This Command: cnfswfunc




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT

Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -

Type Freq Enable Inc Thresh Timeout Enable Inc Thresh

---- ----- -------- ------- ------- ------- -------- ------- -------

PSM 300 Enabled 100 300 31 N/A 100 300

HDM 300 Enabled 100 300 80 Enabled 100 300

LDM 300 Enabled 100 300 80 Enabled 100 300

NTM 300 Enabled 100 300 31 N/A 100 300

FRM 300 Enabled 100 300 80 Enabled 100 300

MT3 300 Enabled 100 300 50 N/A 100 300

CVM 300 Enabled 100 300 300 N/A 100 300

NPM 180 Enabled 100 300 120 N/A 100 300

ARM 300 Enabled 100 300 60 N/A 100 300

BTM 300 Enabled 100 300 120 N/A 100 300

FTM 300 Enabled 100 300 80 Disabled 100 300

UFM 300 Enabled 100 300 80 Enabled 100 300

UFMU 300 Enabled 100 300 80 Enabled 100 300

ALM 300 Enabled 100 300 120 N/A 100 300

UVM 300 Disabled 100 300 60 N/A 100 300

UXM 300 Enabled 100 300 800 Enabled 100 300

URM 300 Enabled 100 300 800 Enabled 100 300

This Command: cnftstparm

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




8 Maximum Routing Bundle [ 90] (D)

9 Reroute Timer [ 3] (secs)

10 Reset Timer on Line Fail [ Yes]

11 Max Down/Up Per Pass [ 50] (D)

12 Down/Up Timer [30000] (msecs)

13 Max Route Errs per cycle [ 200] (D)

14 Time between Rrt cycles [ 5] (mins)

15 Max. Rrt Err cycles [ 1] (D)

16 Routing pause timer [ 0] (msecs)

17 Max msgs sent per update [ 10] (D)

18 Send SVC urgent msg [ Yes]

19 Max SVC Retry [ 0] (D)

20 Wait for TBL Updates [ 70] (100 msecs)

21 Max Derouting Bndl (0=all)[ 500] (D)

22 Enable Cost-Based Routing [ No]

23 Enable Route Cache Usage [ No]

24 Use Delay for Routing [ No]

25 # of reroute groups used [ 50] (D)

26 Starting size of RR grps [ 0] (CLU)

27 Increment between RR grps [ 100] (CLU)

28 CM updates app timeout [ 5] (10 secs)

29 Route concurrency level [ 1] (D)






This Command: cnfcmparm





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




1 Rmt Blk Freq (msec) [ 100] 16 FW Dnld Msgs/Block(dec) [ 4]

2 Rmt Blk Size (hex) [ 400] 17 Flash Write TO(msec) [ 16000]

3 Lcl Blk Freq (msec) [ 100] 18 Flash Erase TO(msec) [ 100]

4 Lcl Blk Size (hex) [ 400] 19 Erase Verify TO(msec) [ 16000]

5 Image Req Freq (msec) [ 10000] 20 Standby Flash TO(sec) [ 300]

6 Dnld Req Freq (msec) [ 10000] 21 Lcl Flash Init TO(msec) [ 1000]

7 Session Timeout (msec) [ 30000] 22 Flsh Write Blk Sz (hex) [ 10000]

8 Request Hop Limit (dec) [ 1] 23 Flsh Verfy Blk Sz (hex) [ 400]

9 Crc Throttle Freq (dec) [ 5000] 24 Chips Per Write/Erase [ 1]

10 Crc Block Size (hex) [ 400]

11 Rev Change Wait(dec) [ 0]

12 CCs Switch Wait(dec) [ 1000]

13 Lcl Response TO(msec) [ 5000]

14 Rmt Response TO(msec) [ 30000]

15 FW Dnld Block TO(msec) [ 50]

This Command: cnfdlparm





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




1. Logout Time ........... 20 minutes

2. VT Logout Time ........ 4 minutes

3. Prompt Time ........... 60 seconds

4. Command Time .......... 3 minutes

5. UID Privilege Level ... 6

6. Input Character Echo .. Enabled

7. Screen Update Time .... 10 seconds





This Command: cnfuiparm




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




1 Priority Bumping Enabled [ NO]

2 Priority Bumping Bundle [ 50] (D)

3 Priority Bumping Bands:

Band 1 [ 2] (D)

Band 2 [ 4] (D)

Band 3 [ 6] (D)

Band 4 [ 8] (D)

Band 5 [ 10] (D)

Band 6 [ 12] (D)

Band 7 [ 14] (D)






This Command: cnfbmpparm





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




Function Number Status Function Number Status

Background Upcard 1 Enabled Dynamic BW Allocation 15 Enabled

Background Updates 2 Disabled Modem Polling 16 Enabled

Standby Terminal 3 Disabled Conn Stat Sampling 17 Enabled

Memory Protection 4 Enabled FastPAD Test 18 Enabled

Comm Break 5 Enabled Neighbor Update Errs 19 Disabled

Comm Fail Test 6 Enabled SVC Del Bgnd Updates 20 Disabled

BRAM Memory Protect 7 Enabled

CRC Test 8 Enabled

CDT Clock Test 9 Enabled

Bus Fail Detection 10 Enabled

Line Diag 11 Enabled

Clock Restoral 12 Enabled

Cm_Rerouting 13 Enabled

Clock Routing 14 Enabled

This Command: on1





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




Function Number Status Function Number Status

Line Stat Sampling 1 Enabled LAN Interface 15 Enabled

Statistical Alarm 2 Enabled Update Standby Stats 16 Enabled

Job Ready Checker 3 Enabled EIA Monitoring 17 Enabled

Configuration Backup 4 Enabled Telnet Access 18 Enabled

Standby Update 5 Enabled Junction ID 19 Enabled

Downloader 6 Enabled Mult SV+/Routing Node 20 Enabled

Cm Updates 7 Enabled Feeder with NW Trunks 21 Disabled

Power Supply Monitor 8 Enabled Multiple Fdr Trunks 22 Disabled

Topo/Stat Updates 9 Enabled Simulated Fdr Trks 23 Disabled

CDP/CIP Sig. Polling 10 Enabled Auto Renum Fail Recov 24 Enabled

Port Stat Sampling 11 Enabled IGX - ACM Selftest 25 Enabled

Robust Updates 12 Enabled Card Simulation Tool 26 Enabled

Robust Alarm Updates 13 Enabled Major Alarm on NNI 27 Disabled

Realtime Counters 14 Enabled Deroute Delay 28 Enabled

This Command: on2





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




Function Number Status

Trace Msg Sent 1 Disabled

Multi-DB Stby Updates 2 Enabled

AIT/BTM/ALM 32h Ext2 3 Enabled

Card Synchronization 4 Disabled

Loop Access Dev Init 5 Disabled

Auto allocate UXM UBU 6 Disabled

Trace Conv Msg 7 Disabled

Automatic Cbus Diags 8 Disabled

Region memory init 9 Disabled

VT Clk Switch Evt Log 10 Disabled

Load Bal on EqCost Rt 11 Disabled

Slve Endpt CWM Update 12 Disabled

Auto Swtchyred on LOC 13 Disabled

Stat Poll on SNMP Get 14 Disabled




This Command: on3

UXM-T3

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.3 Config T3/636 [96000 cps] UXM slot:5

Transmit Trunk Rate: 96000 cps Payload Scramble: No

Rcv Trunk Rate: 96000 cps Connection Channels: 256

Pass sync: Yes Gateway Channels: 200

Loop clock: No Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Statistical Reserve: 5000 cps Incremental CDV: 0

Header Type: NNI Deroute delay time: 0 seconds

VPI Address: 1 VC Shaping: No

Routing Cost: 10 VPC Conns disabled: No

Idle code: 7F hex AAL5 Feeder Trunk: Yes

Restrict PCC traffic: No

Link type: Terrestrial

Line framing: PLCP

Line cable length: 0-225 ft.

HCS Masking: Yes

Last Command: dsptrkcnf 5.3





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.3 Parameters:

1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 532] 15 BDataA [10000] 29 rt-VBR [ 532] 32 BDataA [10000]

13 Non TS [ 795] 16 BDataB [10000] 30 Non TS [ 795] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 5.3

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.3 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]









This Command: cnftrkparm 5.3





Which parameter do you wish to change:

UXM-T1-IMA (1 physical line up)

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.1 Config T1/24 [3622 cps] UXM slot:9

IMA Group Member(s): 1 Line coding: B8ZS

Retained links: 1 Line cable type: ABAM

Transmit Trunk Rate: 3622 cps Line cable length: 0-131 ft.

Rcv Trunk Rate: 3622 cps HCS Masking: Yes

Pass sync: Yes Payload Scramble: No

Loop clock: No Connection Channels: 256

Statistical Reserve: 1000 cps Gateway Channels: 200

Header Type: NNI Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

VPI Address: 1 Incremental CDV: 0

Routing Cost: 10 IMA Protocol Option: Disabled

Idle code: 7F hex IMA Max. Diff. Dly: 200 msec.

Restrict PCC traffic: No IMA Clock Mode: CTC

Link type: Terrestrial Deroute delay time: 0 seconds

Line framing: ESF VC Shaping: No

TRK 9.1 Config T1/24 [3622 cps] UXM slot:9

VPC Conns disabled: No

Last Command: dsptrkcnf 9.1

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.1 Parameters:

1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 22] 15 BDataA [10000] 29 rt-VBR [ 21] 32 BDataA [10000]

13 Non TS [ 30] 16 BDataB [10000] 30 Non TS [ 28] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 9.1




Continue?




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.1 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]









This Command: cnftrkparm 9.1




Which parameter do you wish to change:







UXM-T1-IMA (4 physical lines up)

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.2(4) Config T1/95 [14339 cps] UXM slot:9

IMA Group Member(s): 2-5 Line coding: B8ZS

Retained links: 4 Line cable type: ABAM

Transmit Trunk Rate: 14339 cps Line cable length: 0-131 ft.

Rcv Trunk Rate: 14339 cps HCS Masking: Yes

Pass sync: Yes Payload Scramble: No

Loop clock: No Connection Channels: 256

Statistical Reserve: 1000 cps Gateway Channels: 200

Header Type: NNI Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

VPI Address: 1 Incremental CDV: 0

Routing Cost: 10 IMA Protocol Option: Enabled

Idle code: 7F hex IMA Max. Diff. Dly: 200 msec.

Restrict PCC traffic: No IMA Clock Mode: CTC

Link type: Terrestrial Deroute delay time: 0 seconds

Line framing: ESF VC Shaping: No

This Command: dsptrkcnf 9.2





Continue?




CD MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.2(4) Config T1/95 [14339 cps] UXM slot:9

VPC Conns disabled: No

Last Command: dsptrkcnf 9.2





Next Command:

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.2(4) Parameters:

1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 81] 15 BDataA [10000] 29 rt-VBR [ 80] 32 BDataA [10000]

13 Non TS [ 118] 16 BDataB [10000] 30 Non TS [ 117] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 9.2





Continue?




CD MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 9.2(4) Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]









This Command: cnftrkparm 9.2





Which parameter do you wish to change:

UXM-E1-IMA (1 physical line up)

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.1 Config E1/30 [4528 cps] UXM slot:13

Line DS-0 map: 1-15,17-31 Line coding: HDB3

IMA Group Member(s): 1 Line CRC: Yes

Retained links: 1 Line recv impedance: 120 ohm

Transmit Trunk Rate: 4528 cps HCS Masking: Yes

Rcv Trunk Rate: 4528 cps Payload Scramble: Yes

Pass sync: Yes Connection Channels: 256

Loop clock: No Gateway Channels: 200

Statistical Reserve: 1000 cps Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Header Type: NNI Incremental CDV: 0

VPI Address: 1 IMA Protocol Option: Disabled

Routing Cost: 10 IMA Max. Diff. Dly: 200 msec.

Idle code: 54 hex IMA Clock Mode: CTC

Restrict PCC traffic: No Deroute delay time: 0 seconds

Link type: Terrestrial VC Shaping: No

This Command: dsptrkcnf 13.1





Continue?




CD MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.1 Config E1/30 [4528 cps] UXM slot:13

VPC Conns disabled: No

Last Command: dsptrkcnf 13.1





Next Command:




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.1 Parameters:

1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 27] 15 BDataA [10000] 29 rt-VBR [ 26] 32 BDataA [10000]

13 Non TS [ 37] 16 BDataB [10000] 30 Non TS [ 36] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 13.1





Continue?




CD MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.1 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]









This Command: cnftrkparm 13.1





Which parameter do you wish to change:

UXM-E1-IMA (4 physical lines up)

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.5(4) Config E1/119 [17962 cps] UXM slot:13

Line DS-0 map: 1-15,17-31 Line coding: HDB3

IMA Group Member(s): 5-8 Line CRC: Yes

Retained links: 4 Line recv impedance: 120 ohm

Transmit Trunk Rate: 17962 cps HCS Masking: Yes

Rcv Trunk Rate: 17962 cps Payload Scramble: Yes

Pass sync: Yes Connection Channels: 256

Loop clock: No Gateway Channels: 200

Statistical Reserve: 1000 cps Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Header Type: NNI Incremental CDV: 0

VPI Address: 1 IMA Protocol Option: Enabled

Routing Cost: 10 IMA Max. Diff. Dly: 200 msec.

Idle code: 54 hex IMA Clock Mode: CTC

Restrict PCC traffic: No Deroute delay time: 0 seconds

Link type: Terrestrial VC Shaping: No

This Command: dsptrkcnf 13.5





Continue?




CD MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.5(4) Config E1/119 [17962 cps] UXM slot:13

VPC Conns disabled: No

Last Command: dsptrkcnf 13.5





Next Command:




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.5(4) Parameters:

1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 101] 15 BDataA [10000] 29 rt-VBR [ 100] 32 BDataA [10000]

13 Non TS [ 148] 16 BDataB [10000] 30 Non TS [ 147] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 13.5





Continue?




MAJOR ALARM





sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 13.5(4) Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]






This Command: cnftrkparm 13.5




Which parameter do you wish to change:





UXM-E3

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.1 Config E3/530 [80000 cps] UXM slot:5

Transmit Trunk Rate: 80000 cps Payload Scramble: Yes

Rcv Trunk Rate: 80000 cps Connection Channels: 2500

Pass sync: Yes Gateway Channels: 200

Loop clock: No Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Statistical Reserve: 5000 cps Incremental CDV: 0

Header Type: NNI Deroute delay time: 0 seconds

VPI Address: 1 VC Shaping: No

Routing Cost: 10 VPC Conns disabled: No

Idle code: 7F hex AAL5 Feeder Trunk: Yes

Restrict PCC traffic: No

Link type: Terrestrial

Line framing: HEC

Line cable length: 0-225 ft.

HCS Masking: Yes

Last Command: dsptrkcnf 5.1




Next Command:




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.1 Parameters:

1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 444] 15 BDataA [10000] 29 rt-VBR [ 444] 32 BDataA [10000]

13 Non TS [ 641] 16 BDataB [10000] 30 Non TS [ 641] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 5.1




Continue?




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 5.1 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]




This Command: cnftrkparm 5.1




Which parameter do you wish to change:

UXM-OC3

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 10.1 Config OC3 [353207cps] UXM slot:10

Transmit Trunk Rate: 353208 cps Connection Channels: 256

Rcv Trunk Rate: 353207 cps Gateway Channels: 200

Pass sync: Yes Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR

Loop clock: No Incremental CDV: 0

Statistical Reserve: 5000 cps Frame Scramble: Yes

Header Type: NNI Deroute delay time: 0 seconds

VPI Address: 1 VC Shaping: No

Routing Cost: 10 VPC Conns disabled: No

Idle code: 7F hex AAL5 Feeder Trunk: Yes

Restrict PCC traffic: No

Link type: Terrestrial

Line framing: STS-3C

HCS Masking: Yes

Payload Scramble: Yes

Last Command: dsptrkcnf 10.1





Next Command:




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 10.1 Parameters:

1 Yel Alm-In/Out (D) [ 2500/ 10000] 18 Red Alm-In/Out (D) [ 2500/ 10000]

2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]

4 Gateway Efficiency (D) [ 2.0]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]

9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ 1952] 15 BDataA [10000] 29 rt-VBR [ 1952] 32 BDataA [10000]

13 Non TS [ 2925] 16 BDataB [10000] 30 Non TS [ 2925] 33 BDataB [10000]

14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]

This Command: cnftrkparm 10.1




Continue?




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 10.1 Parameters:

Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)

35 CBR [ 600] 38 CBR [ 600]

36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]

37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]

Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)

41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]

42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]

43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]




This Command: cnftrkparm 10.1





Which parameter do you wish to change:

NTM-T1

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 4 Config T1/24 [8000 pps] NTM slot:4

Line DS-0 map: 0-23 Deroute delay time: 0 seconds

Pass sync: Yes

Loop clock: No

Statistical Reserve: 1000 pps

Routing Cost: 10

Idle code: 7F hex

Restrict PCC traffic: No

Link type: Terrestrial

Line framing: D4

Line coding: B8ZS

Line cable type: ABAM

Line cable length: 0-133 ft.

Traffic: V,TS,NTS,FR,FST

Incremental CDV: 0

Last Command: dsptrkcnf 4





Next Command:




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 4 Parameters:

1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]

2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 22] 32 BDataA [ 600]

13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 30] 33 BDataB [ 600]

14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2648] 34 HighPri[ 100]

This Command: cnftrkparm 4





Which parameter do you wish to change:




NTM-E1

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 15 Config E1/32 [10666 pps] NTM slot:15

Line DS-0 map: 0-31

Pass sync: Yes

Loop clock: No

Statistical Reserve: 1000 pps

Routing Cost: 10

Idle code: 54 hex

Restrict PCC traffic: No

Link type: Terrestrial

Line coding: HDB3

Line CRC: No

Line recv impedance: 75 ohm + gnd

Traffic: V,TS,NTS,FR,FST

Incremental CDV: 0

Deroute delay time: 0 seconds

Last Command: dsptrkcnf 15





Next Command:






sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT




TRK 15 Parameters:

1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]

2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 28] 32 BDataA [ 600]

13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 40] 33 BDataB [ 600]

14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2632] 34 HighPri[ 100]

This Command: cnftrkparm 15





Which parameter do you wish to change:




NTM-SR

sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT

TRK 7 Config SR/30 [10000 pps] NTM slot:7

Subrate interface: X.21

Subrate data rate: 1920 kbps

Pass sync: No

Loop clock: Yes

Statistical Reserve: 1000 pps

Routing Cost: 10

Restrict PCC traffic: No

Link type: Terrestrial

Traffic: V,TS,NTS,FR,FST

Deroute delay time: 0 seconds

This Command: dsptrkcnf 7




sw-node TRM Cisco IGX 8430 9.4.12 Apr. 4 2005 16:50 GMT

TRK 7 Parameters:

1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]

2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]

3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]

4 Gateway Efficiency (D) [ N/A]

5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)

6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]

7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]

Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)

8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]

9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]

Receive Queue Depth (D) Transmit Queue Depth (D)

12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 27] 32 BDataA [ 600]

13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 37] 33 BDataB [ 600]

14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2636] 34 HighPri[ 100]

This Command: cnftrkparm 7

Appendix A—BXM Firmware MFZ Release Notes

This section contains information about the BXM firmware MFZ.

About the Firmware MFZ

BXM firmware version MFZ supports all existing interfaces and models of BXM hardware. The tables in this section outline various levels of hardware revisions supported for BXM firmware version MFZ.

Front Cards

Table 16 lists the front cards that support MFZ firmware.

Table 16 Front Cards Supported by MFZ Firmware 

Model Number	Description	FW model	HW Rev	FW Rev
BXM-155-4	4 port OC3 Line Module (Front Card)	F	B	MFZ
BXM-155-8	8 port OC3 Line Module (Front Card)	F	B	MFZ
BXM-622	1 port OC12 Line Module (Front Card)	F	D	MFZ
BXM-622-2	2 port OC12 Line Module (Front Card)	F	D	MFZ
BXM-T3-8	8 port T3 Line Module (Front Card)	F	B	MFZ
BXM-T3-12	12 port T3 Line Module (Front Card)	F	B	MFZ
BXM-E3-8	8 port E3 Line Module (Front Card)	F	B	MFZ
BXM-E3-12	12 port E3 Line Module (Front Card)	F	B	MFZ
BXM-155-8DX	8 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-8D	8 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-4DX	4 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-4D	4 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-622-2DX	2 port OC12 Line Module (Front Card)	F	A0	MFZ
BXM-622-2D	2 port OC12 Line Module (Front Card)	F	A0	MFZ
BXM-622-DX	1 port OC12 Line Module (Front Card)	F	A0	MFZ
BXM-T3-12EX	12 port T3 Line Module (Front Card)	F	A0	MFZ
BXM-T3-12E	12 port T3 Line Module (Front Card)	F	A0	MFZ
BXM-T3-8E	8 port T3 Line Module (Front Card)	F	A0	MFZ
BXM-E3-12EX	12 port E3 Line Module (Front Card)	F	A0	MFZ
BXM-E3-12E	12 port E3 Line Module (Front Card)	F	A0	MFZ
BXM-E3-8E	8 port E3 Line Module (Front Card)	F	A0	MFZ

Front Card for APS Compatibility

Table 17 lists the front cards that support APS with MFZ firmware.

Table 17 Front Cards Supporting APS with MFZ Firmware 

Model Number	Description	FW model	HW Rev	FW Rev
BXM-155-4	4 port OC3 Line Module (Front Card)	F	C	MFZ
BXM-155-8	8 port OC3 Line Module (Front Card)	F	C	MFZ
BXM-622	1 port OC12 Line Module (Front Card)	F	E	MFZ
BXM-622-2	2 port OC12 Line Module (Front Card)	F	E	MFZ
BXM-155-8DX	8 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-8D	8 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-4DX	4 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-155-4D	4 port OC3 Line Module (Front Card)	F	A0	MFZ
BXM-622-2DX	2 port OC12 Line Module (Front Card)	F	A0	MFZ
BXM-622-2D	2 port OC12 Line Module (Front Card)	F	A0	MFZ
BXM-622-DX	1 port OC12 Line Module (Front Card)	F	A0	MFZ

Back Cards

Table 18 lists the back cards that are supported by MFZ firmware.

Table 18 Back Cards Supported by MFZ Firmware 

Model Number	Description	HW Rev	FW Rev
MMF-155-4	4 port multi-mode fiber back card	A	na
MMF-155-8	8 port multi-mode fiber back card	A	na
SMF-155-4	4 port single-mode fiber intermediate-reach back card	A	na
SMF-155-8	8 port single-mode fiber intermediate-reach back card	A	na
SMFMR-155-4	4 port single-mode fiber long-reach back card	A	na
SMFMR-155-8	4 port single-mode fiber long-reach back card	A	na
SMF-622	1 port intermediate-reach OC12 back card	A	na
SMF-622-2	2 port intermediate-reach OC12 back card	A	na
SMFMR-622	1 port long-reach OC12 back card	A	na
SMFMR-622-2	2 port long-reach OC12 back card	A	na
XLR-622	1 port extra long-reach OC12 back card	A	na
XLR-622-2	2 port extra long-reach OC12 back card	A	na
BPX-T3/E3-12	12 port T3/E3 back card	A	na
BPX-T3/E3-8	8 port T3/E3 back card	A	na
RDNT-LR-622-2	2 port long-reach OC12 redundant back card	A	na
RDNT-SM-622-2	2 port intermediate reach OC12 redundant back cards	A	na
RDNT-SM-622	1 port intermediate reach OC12 redundant back cards	A	na
RDNT-LR-155-8	8 port long-reach OC3 redundant back cards	A	na
RDNT-SM-155-4	4 port intermediate-reach OC3 redundant back cards	A	na
RDNT-SM-155-8	8 port intermediate-reach OC3 redundant back cards	A	na

New Features Supported in BXM Firmware MFZ

Bug fixes only.

New Features Supported in BXM Firmware MFY

Bug fixes only.

New Features Supported in BXM Firmware MFX

•VSI bandwidth overbooking—CSCdy72578.

•ECAC support added on the BXM for VSI connections—CSCdw83279.

New Features Supported in BXM Firmware MFW

Bug fixes only.

New Features Supported in BXM Firmware MFV

VC merge support added.

New Features Supported in BXM Firmware MFU

•Virtual trunk oversubscription.

•VC shaping.

New Features Supported in BXM Firmware MFT

Bug fix only. This image includes a fix for the bug CSCdw54957.

New Features Supported in BXM Firmware MFR

Bug fix only.

New Features Supported in BXM Firmware MFP

Configurable number of ILMI traps.

New Features Supported in BXM Firmware MFN

•F4-F5 Mapping on ports and F4 AIS detection on virtual trunks.

•Support for E2E tstpingoam.

•Support for O.151 OAM standard.

New Features Supported in BXM Firmware MFM

Bug fix only.

New Features Supported in BXM Firmware MFK

LCN CAC with policing parameters set by PNNI controller. (See the "Notes, Cautions, and Clarifications" section).

New Features Supported in BXM Firmware MFJ

Bug fix only.

New Features Supported in BXM Firmware MFH

•Dynamic partitioning feature is supported on the BXM card by default. Remote shell feature through the BCC CLI provides a mechanism to turn off this feature.

•SPVC feeder support.

New Features Supported in BXM Firmware MFF

Use of separate qbin to guarantee bandwidth resources for the control channels of VSI controllers.

New Features Supported in BXM Firmware MFE

Bug fix only.

---

Note Support for APS 1:1 added for VSI.

---

New Features Supported in BXM Firmware MFD

Bug fix only.

New Features Supported in BXM Firmware MFC

•Support for SES (PNNI controller).

•BootCore enhancement to support multi-vendor flash-SIMMs.

•A 1 msec granularity for tstdelay measurement.

New Features Supported in BXM Firmware MFB

•Multiple VSI (2.2) partition feature. Three partitions are supported.

•Hitless connection density upgrade for BXM.

•SCR and PCR policing at less than 50 CPS for T3/E3 BXMs.

•Control traffic shaping.

New Features Supported in BXM Firmware MFA

Multiple VSI (2.2) partition feature (two partitions).

---

Note First release in MF branch of firmware.

---

New Features Supported in BXM Firmware MEC

No new features in Release MEC.

New Features Supported in BXM Firmware MEB

No new features in Release MEB.

New Features Supported in BXM Firmware MEA

•VSI version 2.2 (single partition).

•ITUT Annex B and configurable signal degrade (SD) and signal failure (SF) thresholds for SONET linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).

Table 19 lists the current default thresholds.

Table 19 SD and SF Default Thresholds 

BIP count	Condition
10-4	SF detected
10-5	SD detected & SF clear
10-6	SD clear & SF clear

New Features Supported in BXM Firmware MDA

•Virtual trunking.

•BXM multi-level channel statistics.

•SONET linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).

•Card based LMI and ILMI.

•Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. See the "Special Installation/Upgrade Requirements" section.

Special Installation/Upgrade Requirements

This section contains additional installation and upgrade requirements.

BXM-622DX Upgrade Issue

The issue in this section applies only to the BXM-622DX (enhanced single port OC12) card.

Firmware revisions MFE through MFL have incorrect queue sizes. When you upgrade from lower revisions, mismatches can occur. And, the card might not recover.

This problem has been corrected in MFM. Therefore, use MFM or higher revisions when you upgrade.

A similar problem exists in Model E firmware for revisions MEJ and MEK. You must upgrade to Model F firmware, using MFM or higher.

APS Issues

Upgrading from MEK and lower firmware to MFZ when feeder trunks are utilized with APS while the BPX node does not have APS requires the following procedure:

---

Step 1 Change the PXM1-based MGX feeder to use APS1+1 unidirectional AND disable K1K2 processing (might need to delete and then add back APS).

On the BPX temporarily configure to use unidirectional mode.

Step 2 After PXM1-based MGX dspapsln shows both lines OK, delete the APS line on the BPX.

Step 3 Proceed to upgrade the BXM cards as if Y-red.

Step 4 After both cards are MFZ, add back the APS on the BPX.

Step 5 Reconfigure both PXM1-based MGX and BPX to use the appropriate APS configurations.

---

BXM cards with MCB/MDA firmware or later can be smoothly migrated to the MFA or above version of firmware by using Y-cable redundancy.

To upgrade a BXM card pair in Y-red configuration, complete the following steps:

---

Step 1 Upgrade the standby card with the MFA or above firmware version.

Wait for all of the configuration to be downloaded to the card.

Step 2 Do a switchyred to switch to the card with firmware MFA or above version.

Step 3 Burn the other card with the desired version MFA or above firmware.

Follow the standard firmware upgrade procedure for downloading and burning the firmware to the cards.

Step 4 If BCC SWSW version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Stats, go directly to MFC or above versions from MCC.

---

For APS (1+1) MEx or MFA image versions are not to be treated as compatible with MFZ (minus MFA) image versions. During an upgrade procedure from MEx or MFA image to MFZ (minus MFA) image, both cards must be upgraded to the MFZ (minus MFA) image with minimal interval between them. Any intra-MFZ (minus MFA) or intra-MEx upgrades are fine.

The incompatibility is due to APS intercard messages from one end not being recognized by the other end. See bug CSCdu67053 for the symptoms caused by this incompatibility.

Channel Statistics Issues

While upgrading from firmware, on OC3, 1 port OC12 BXM cards, if stats level on BXM is greater than 1, use one of the following upgrade procedures listed below.

Upgrade From Firmware Revision MEA or Higher

---

Step 1 Upgrade SWSW to 9.2.30 or higher.

Step 2 Upgrade the firmware to MFZ.

---

Upgrade From Firmware Revisions Lower Than MEA.

This procedure avoids card mismatch.

---

Step 1 Upgrade firmware to MEC.

Step 2 Upgrade the SWSW to 9.2.30 or higher revision.

Step 3 Upgrade the firmware to MFZ.

A firmware burn must not be interrupted. A card reset in the middle of burn firmware results in the BXM being maintained in the core state (identified by blinking yellow LED) or failed state (identified by a solid red LED). In this case the dspcds screen reports the card as FAILED. This state can be recovered by reburning the firmware into the card.

---

Features Obsoleted

The following features have been obsoleted:

1. VSI 1.0 is obsoleted by VSI 2.2 in the MDA release and higher.

2. From versions MFJ to MFN channel statistics level 0 is no longer supported for BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models. In MFN and higher conditional support for statistics level 0 is revoked. See the "Notes, Cautions, and Clarifications" section for more details.

3. In all other models channel statistics level 0 is supported by all firmware versions (BXM-155-8DX, BXM-155-8D, BXM-155-4DX, BXM-155-4D, BXM-622-2DX, BXM-622-2D, BXM-622-DX, BXM-T3-12EX, BXM-T3-12E, BXM-T3-8E, BXM-E3-12EX, BXM-E3-12E, BXM-E3-8E).

Notes, Cautions, and Clarifications

1. BXM Model F firmware is intended for use with 9.3 switch software. BXM Model F firmware can be used to upgrade BXM cards during the upgrade process from SWSW Release 9.2 to 9.3. BXM Model F firmware has not been tested for compatibility with SWSW Releases 8.4, 8.5, and 9.1. BXM Model F firmware is compatible with IOS version 12.05t2 or greater for MPLS.

2. MFE is a not on Cisco.com because it is an SES specific release.

3. Protection Switching based on BER on BXM might not comply to standards. The GR-253 and ITU-T G.783 requires that switching be completed within 60 msec from the time the error starts. BXM is unable to detect BER threshold crossing until the next poll, which occurs every 250 msec. Thus, switching time can be up to 250 msec under certain circumstances.

4. In APS 1+1 default configuration, both back card LEDs show green when primary card is active and selection is from PROT line. When primary card is active and it is selecting from PROT, PROT backcard should be green, since it is carrying traffic. WORK backcard should also be green since that is the physical path for the primary (and active) card to pass traffic. Backcard LED green means the backcard is directly or indirectly carrying traffic, and pulling the backcard causes traffic disruption (CSCdm53430).

5. In APS 1+1 default configuration and a manual W->P is on and a switchyred is issued, a manual W->P event is logged. By default, on switchyred the new active card comes up in "clear" state. But in this case since there is a manual W->P on, the APS line switches to PROT and the switching is logged (CSCdm53404).

6. In APS 1+1 default configuration if the selected line is PROT and last user request is clear and a switchyred is issued, line switches to WORK. If the last user request is "clear", full automatic APS switching is in effect with the working line being active by default. When there is no last user switch request to switch to any particular line, the working line becomes active (CSCdm53420).

7. When APS Annex B is added to local end which has the secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If the secondary card is active, do a switchyred to make the primary card active. Then, add APS Annex B (CSCdm46359).

8. MFK and higher versions support LCN CAC for Class of Services. The controller reserves some LCNs for control VC as default. These reserved LCNs cannot be used by any Class of Service in MFZ. If all the LCNs for the partition have been used in a version earlier than MFK, after the MFZ version is updated in the switch, some connections might not be added. These connections try to use LCNs reserved for control VC which is not allowed.

Configure more LCNs for the partition to make sure enough LCNs exist for all the connections.

9. The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.

10. APS 1:1 is not supported for VSI in versions before MFE (CSCdp42996). APS 1:1 must not be configured on ports intended to be used by PNNI or MPLS as after switchover traffic flow is stalled on the protection line for releases before MFE. However, in MFE and higher, this problem is fixed.

11. Total bandwidth allocated to all VSI partitions on a BXM must not be more that OC12 rate, 1412832 cps. BCC SWSW allows users to configure more than the OC12 rate, which all of the PNNI connection commit requests are NACKed by BXM.

12. In firmware versions prior to MFF signaling bandwidth for an SES controller was not guaranteed. In MFF and above the signaling qbin feature has been added (with SWSW 9.3.10 and higher and SES image 1.0.10 and higher) to guarantee signaling bandwidth.

13. Statistics level 0 for legacy BXM cards was obsoleted in Model F releases until MFN. However, in version MFP and higher conditional support statistics level 0 for legacy cards is revoked. Statistics level 0 is not supported if VSI configurations exist on the card.

If a card was configured with statistics level 0 with VSI enabled in a previous release of firmware (Model C or E), upgrading to MFP or above revisions causes a mismatch on legacy cards.

To avoid impacting VSI operations, reconfigure the card to statistics level 1 or above before upgrading.

---

Note BXME (enhanced cards) support all statistics levels unconditionally with all valid configurations, models, and releases.

---

14. Starting with MFP through this release of MFZ, excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) are now reported to Switch Software as red alarms. This feature is not configurable, and might cause failed connections and rerouted trunks in configurations where APS is not enabled, alternate trunk routes do not exist or on UNI ports. This feature is not active when APS is configured and enabled.

Because this feature is not configurable at this point in time customers who do not want this behavior should not upgrade to MFP through MFZ but rather wait for a subsequent SWSW/BXM fw release where this feature can be turned on and off (default is off) via CLI command.

Anomalies Fixed in MFZ

Table 20 lists that anomalies that are fixed in MFZ.

Table 20 Anomalies Fixed in MFZ 

Bug ID	Description	Apply to SES
CSCec33060	Symptom: dspchstats on atfxfst connections shows CLP0 discards. These cell are not user cells since user traffic is not affected. These cells are traffic management cells. Conditions: Run the dspchstats command on an ATFXFST connection on a BXM. Workaround: Unknown.	No
CSCee45765	Symptom: XLMI/LMI protocol remains in down state. Conditions: When a switchover is done on an AXSM or remote end, XLMI/LMI on the BXM side might go down due to missing ACKs from the remote end. These ACKs are the responses to the UPDATE STATUS message BXM has been sending. XLMI/LMI might stay in down state. Workaround: Unknown. XLMI/LMI might recover if on the AXSM side you execute dnlmi /uplmi or any event to trigger UPDATE STATUS message sent to the BXM. Note dnlmi and uplmi do not affect traffic.	No
CSCeb54474	Symptom: Backcard LED on standby APS card shows green when it is not carrying active APS line (active traffic). Conditions: Down the line, and up line again. Workaround: None.	No
CSCeb32926	Symptom: SF/SD BER APS alarm does not clear. Conditions: 1. Introduce SF/SD BER error on the standby card. 2. Remove the standby backcard. 3. Remove the source of SF/SD BER error. 4. Reinsert the backcard. SF/SD BER alarm is stuck doing dspapsln. Workaround: 1. Reintroduce the SF/SD BER error (do not remove backcard), and clear the source of BER error. 2. Do a forced switchapsln (option 3).	No

Known Anomalies in MFY

No known anomalies exist in the BXM firmware MFY.

Anomalies Fixed in MFY

Table 21 lists that anomalies that are fixed in MFY.

Table 21 Anomalies Fixed in MFY 

Bug ID	Description
CSCea08808	Symptom: In a BPX/SES PNNI scenario, SVC/SPVC connections do not route over PNNI virtual interface (VNNI, virtual trunk) when using different VPIs in both ends of the Virtual Path Connection. Connections fail with cause code #35: Last Fail Cause: requested VPCI/VCI not available. Conditions: The scenario is similar to the following: BXM_VNNI-----VPI1-----VPC_Cloud-----VPI2----BXM_VNNI where VPI1 is different than VPI2 Workaround: Disable ILMI auto configuration using the command from the SES Controller. With auto-configuration disabled, the ILMI slave does not start ATM layer parameter-negotiations while ports come up. Instead, the ILMI slave uses the local configuration parameters. The default state for auto-configuration is enabled. Further Problem Description: If this problem is present, the command, dsppnport, shows a minSvccVpi greater than maxSvccVpi, and a minSvccVci greater than maxSvccVci in the end with higher VPI value. This can be seen in the following example: nodename.7.PXM.a > dsppnport 1:1.4:14 Port: 1:1.4:14 Logical ID: 16848910 IF status: up Admin Status: up UCSM: enable SVC Routing Pri: 8 Auto-config: enable Addrs-reg: enable IF-side: network IF-type: nni UniType: private Version: pnni10 PassAlongCapab: n/a Input filter: 0 Output filter: 0 minSvccVpi: 11 maxSvccVpi: 10 <===== minSvccVci: 35 maxSvccVci: 65535 minSvpcVpi: 11 maxSvpcVpi: 10 <===== MFY resolves this issue. MFY is not compatible to previous images for this particular feature. Both sides have to be MFY or later.
CSCea85590	Symptom: In an XPVC network, BXM at the edge of the AR network connects to an AXSM card in the SPVC network. The NodeStatus message that the BXM sends to AXSM, contains a field of Fdr_slot. This field is where the physical slot number is sent, while the logical slot number is needed for the consistency by the CWM. Conditions: This symptom occurs when running the XLMI/LMI protocol. Workaround: None.
CSCeb21297	Symptom: Pseudo AIS on path BIP-8 errors on BXM cards with SONET interfaces is not a configurable feature. Conditions: This symptoms occurs always. Workaround: None. This DDTS makes configurable the customer-specific behavior where AIS-P is triggered from UAS. In previous releases starting with MFP, this was always ON. Now the default is OFF, and it must be turned ON via command, cnfndparm 61, using SWSW 9.4.00 or higher. For a more detailed description, see SWSW 9.4 Release Notes.

Known Anomalies in MFX

Table 22 lists the known anomalies in MFX.

Table 22 Known Anomalies in MFX 

Bug ID	Description	Apply to SES
CSCdx52484	Symptom: CBR traffic got dropped on ENNI link on BPX side where there is congestion. Condition: resetcd of BXM can solve the problem. Workaround: Unknown.	No
CSCdx79141	Symptom: Channel allocation inconsistency between BPX and SES. Condition: Have only 1 part. first (Max. lcn > Min.), add conns. > min. Add more parts such that sum (Mins) >Max (max). Workaround: None.	Yes

Anomalies Fixed in MFX

Table 23 lists the anomalies that are fixed in MFX.

Table 23 Anomalies Fixed in MFX 

Bug ID	Description
CSCdw76023	Symptom: For APS 1:1 intracard configuration, dspapsln command keeps showing false and misleading alarm "APS missing card." Conditions: APS 1:1 intracard setup using R (redundant) designated backcard. Workaround: Do not use an R designated backcard when configuring APS 1:1 intracard setup. Use the normal backcard. It is just a false alarm. All APS functionality should still be working correctly.
CSCdw95063	Symptom: "dspapsln" doesn't show "card missing" on standby even though the standby card has been removed. "dspapsln" shows OK even though standby BXM card is removed to cause a switchover to the newly active card. Conditions: Remove the active BXM to cause the switchover to the newly active card in an APS 1+1 configuration setup. Workaround: Insert back the standby BXM card.
CSCdx28781	Symptom: When bit errors happen on a line, all the connections provisioned on the line fail. Conditions: MFM onwards (There is a code change went into firmware image MFM, which puts the line into Path AIS as long as UAS-P condition persists. This change is good for trunks as alternate routes could be chosen. But on lines, especially when they are error prone, there is no choice but to keep using the line, application might slow down but at least connection does not get failed). Workaround: Use images before MFM or replace the buggy physical cable.
CSCdx40378	Symptom: When sending F5 OAM end to end flows through a DACS SPVC, only the "egress" counters of dspconstats increment. This true for F5 end to end AIS, or F5 end to end loopback. Conditions: This affects OAM cell counting on all SPVC connections. It occurs with firmware MFW or lower revision. Workaround: None.
CSCdx50089	Symptom: ILMI did not update its neighbor IP address and IfName to be "N/A", when its physical link on which it was running went down. dspnebdisc would show the previous neighbor IP address and IfName in this situation. Conditions: The physical link on which ILMI was running went down. Workaround: Reset the card will clear the old information.
CSCdx72292	Symptom: Commit connection request is failed due to NAK from BXM, while still a lot of available bandwidth at partition level. Conditions: Single/multiple partitions on a interface enabled. 1. The bandwidth common pool of this interface is zero. 2. At least in one partition, sum of (cos_min_bw) > part_min_bw, due to the round up when applying the policy parameters -minbw to get cos_min_bw. Workaround: Configuring the multiple partitions gives at least 20 cells in common pool. The work around for CSCdv03058 applies to this problem. See CSCdv03058 for detail workaround explanation.
CSCdy16927	Symptom: BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred. Conditions: SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder ** 1. The connection segment in the BPX/SES network is down. 2. The corresponding segment in the SPVC feeder is in Abit alarm. 3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "**" tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the downed VSI connection in the BPX/SES network. Workaround: None.
CSCdy57435	Symptom: Fatal PRFD Pending error has been seen at BXM card. (SIMBA errors excess its threshold). Conditions: Most likely, it happens during FW/SW upgrade. Workaround: None.
CSCdy75277	Symptom: A pnport stuck is in down state after being added and configured. Conditions: Add and configure pnport on a freshly added trunk/port. Delete all the configuration and down all interfaces, then newly add and configure the pnport from scratch. Workaround: Unknown.
CSCdy80205	Symptom: When physical interface in alarm (LOS), dsppnport shows the operating status as up in SES. Conditions: When SES is running 3.0(10.0) or later, even if the physical interface is in alarm (LOS), if ILMI is enabled, with out configuring signaling type (NNI or UNI) in SES, the operating status of interface is shown as UP. This issue occurs with BXM Image MFW or prior. Workaround: Configure signaling type in SES.
CSCdy89521	Symptom: The AAL5 Feeder attached to the BPX routing hub becomes unreachable after a delshelf command was issued on the BPX, even though there are no existing connections on either the feeder or the BPX. Conditions: BXM runs the LMI protocol. Workaround: None
CSCdz49797	Symptom: Doing a switchyred on BXM causes AXSM connection to go into Abit/AIS alarm. Conditions: A switchyred on BXM card running XPVC in a mixed MGX 8220 BPX MGX (PXM1) MGX (PXM45) network can go into alarm, and then the alarm will not clear. Typically a transition outside of the PNNI network (a switchyred on the BPX in this case) can cause the ingress port to generate an AIS alarm, which it sends into the PNNI network and is received by CPE at the other end. Because the AIS is incorrect, there's never any indication to the ingress port that it should clear the alarm. Workaround: Executing dncon/upcon on the AXSM end which is generating switch side Tx AIS (if that is the master connection) If the problem is on the slave end need to delete and re-add the connection
CSCin33357	Symptom: After burn MFW image, the BXM enhanced card went to resetting. Conditions: BXME card with statistics level 0 and VSI connections. Workaround: Do not use statistics level 0 for BXME card.
CSCdz60041	Symptom: BPX may not be able to recover clock from the line with PLCP framing configuration. Conditions: BPX may experience clock recovery issues when recovering clock from the line connected to other vendor equipment. Workaround: None

Anomalies Fixed in MFW

Table 24 lists that anomalies that are fixed in MFW.

Table 24 Anomalies Fixed in MFW 

Bug ID	Description
CSCdw80712	Symptom: 1:1 APS allows manual/forced switchapsln P->WLine. Conditions: 1. 1:1 APS with Bi-Dir configured; remote is AXSM/B. 2. Manual switchaps W->PLine from AXSM/B. 3. Forced switchaps P->WLine from BXM. Workaround: None.
CSCdx45385	Symptom: BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn). Conditions: 1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level. 2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated. Workaround: Add a con or down a con to trigger the update.
CSCdx55794	Symptom: BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4. Conditions: 1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX. 2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI. Workaround: None.
CSCdx56537	Symptom: Setting cnftrkparm 9 2500/15000 causes trunk failure. Conditions: BXM running MFU firmware. Found in lab environment but likely to also be found in a live network if these trunk parameter values are used and the trunk passes over another medium such as a TDAX or SDH backbone. Workaround: Set cnftrkparm 9 2500/10000 which is the default for STM1. Do not use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.
CSCdx59080	Symptom: Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a "Looped Back" state when the BXM is reset by command "resetcd ? h". Conditions: BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk. Workaround: Issue cnftrk and change none of the parameters by stepping through them.
CSCdy01870	Symptom: SIMBA reset card errors logged due to PRFD Pending Errors Conditions: BXM image MEE and SWSW image 9.3.00 Workaround: None.
CSCdy01951	Symptom: Unnecessary alarms are triggered when BXM sends slot errors to SWSW. Conditions: The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed. Workaround: None.
CSCdy05515	Symptom: Current BXM firmware only support a few statistics counters. In order to enhance customer operation and maintenance capability, a few new statistic counters have been added. The detail description about the new created statistics and associated CLI commands and MIBs can be found in the latest VSI document. See DDTS case CSCdy05597 (SES and MIBs). Conditions: All previous FW do not support the new connection statistics. Workaround: Not applicable.
CSCdy13987	Symptom: Newly added routed SPVC carries counter values of previously deleted SPVC. Conditions: Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values. Workaround: Problem is fixed in MFW (MF20).

Anomalies Fixed in MFV

Table 25 lists the anomalies that are fixed in MFV.

Table 25 Anomalies Fixed in MFV 

Bug ID	Description
CSCdr55738	Symptom: Switchyred on APS 1+1 trunks is taking longer than 250 msec. Conditions: Performed switchyred on APS 1+1 with SWSW 9.3.10 and BXM FW MF17. Workaround: Unknown.
CSCds20584	Symptom: BW change by cnftrk command does not change ER stamping BW. Conditions: When the AR ABR STD connection is programmed and the bw of trunk is changed by the cnftrk command. The changed BW does not take effect. Workaround: Manually reset the card.
CSCdu09831	Symptom: APS fails when working backcard (active or standby) is removed from chassis when working front card is active. Conditions: The working front card has to be the active card when working backcard is removed. This occurs when APS 1+1 ITUT non-revertive bi-directional configuration SWSW 9.2.34BXM fw MFJ. Workaround: In operational situations always have the protecting front card and protecting backcard as active. Any failures will then switch ok and either backcard can be swapped while protecting front card is active.
CSCdv86732	Symptom: Incorrect values for Path Unavailable Seconds statistics are displayed under dspplyslnstathist. The displayed counts maybe higher than expected. For example, over a 900 second period, 910 Path UAS counts may be displayed. While Path UAS stats are referred to specifically, other duration statistic counts could be affected as well. Conditions: The problem occurs under the following conditions: •BXM line or trunk •The line or trunk is in major alarm (e.g. LOS, AIS, YEL) •Statistics are collected on the line or trunk to report the duration of the alarm condition (e.g. UAS). •The automatic trunk/line loopback test is disabled using the cnffunc command. Workaround: None.
CSCdw06552	Symptom: Conns should stop passing traffic when dnpnport on UNI port on SES. Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node. Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX 8850 (PXM45) node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic. When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells. Workaround: Unknown.
CSCdw21798	Symptoms: Forced switchapsln when secondary section has failed is accepted. Conditions: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1. Workaround: Unknown.
CSCdw51601	Symptom: dspportstats on BXM shows Rx as Zero even the port has traffic passes in both directions. Conditions: Not every single port has this problem. However we found multiple cards in the customer network have this issue. All the problem ports are T3 ports. Workaround: None.
CSCdw81944	Symptom: APS switch options 4,5,6 should not be allowed on AnnexB protocol. Conditions: Upon switchapsln options 4, 5, 6. Workaround: Unknown.
CSCdw83849	Symptom: APS 1+1 configured between AXSM/B and BXM running ITU-AnnexB protocol: APS Lockout request (on BXM) doesn't keep selector position. Conditions: APS Setup: MGX 8850 (AXSM/B) ----> BPX (BXM) APS 1+1, AnnexB Trigger: 1. On AXSM/B, apply APS force switch from Working section 1 (WS1) to WS2. 2. On BXM, apply lockout request, selector switches to WS1 which is incorrect. Lockout should indeed freeze selector position to WS2 in this scenario. Workaround: Unknown.
CSCdw94327	Symptom: With 1:1 configuration; either WL or PL in LOS, BPX always sends RDI-P to AXSM/B. Conditions: 1. Configured Intra 1:1 APS. Forced switchaps W->PLine for both APS lines. Active on Plines. 2. Removed the WL-Rx from remote ends. Active stayed on PLines, both lines in Minor alarms. Remote node receives RDI-P on the failed line. Workaround: Unknown.
CSCdx05529	Symptom: Removing cable on protection line followed by switchyred card on remote node cause remote Yel major alarm on the trunk. Conditions: It only happened with ITUT protocol with APS 1+1 mode Workaround: Unknown.
CSCdx29896	Symptom: VrmRetLcnResources CD error logged on BXM. Conditions: Run AutoRoute/MPLS/PNNI on BPX network. Three partitions (2 MPLS, 1 PNNI) are on an interface with a VC Merge Parent connection. Workaround: Unknown.
CSCdx32780	Symptom: Card went to Failed state during normal operation with card error: rt_task.c 1258 Task low on real time, SRCID = 4. Conditions: This symptom occurs with SWSW 9.3.36 SPVC connections and BXM FW MFU. Workaround: Unknown.
CSCdx49312	Symptom: SES cannot add PVC with PCR = linerate. Conditions: With old SES image and BXM image, SES does not allow adding connections, and CLI rejects. Workaround: Use BXM MFV and related SES image (1.1.79).
CSCdx52531	Symptom: APS standby CD to active but no response to BCC after reset active BXM. Conditions: Enable VSI partition for MPLS and with APS configuration on BXM on BPX. Workaround: Manually reset BXM.
CSCdx69563	Symptom: Continuous 105 and CD errors logged on BXM cause SPVC down on SES. Conditions: Configure 100K SPVC on BPX with SES. Workaround: Unknown.
CSCdx73291	Symptom: Fatal card error happened on BXM card in slot 9 after doing a full hitless rebuild on node. The card error should be a Non Fatal card error. Conditions: A full hitless node rebuild was done on a node with many connections. This problem is related to a temporary HDLC queue overflow and should not be a fatal error. Workaround: Unknown.
CSCin03340	Symptom: BXM sends ILMI trap with incorrect number of PVCs Conditions: The SWSW 9.3.40 feature—configurable number of changes per ILMI trap—needs support from the FW when ILMI is run by the card. Workaround: Unknown.

Anomalies Fixed in MFU

Table 26 lists that anomalies that are fixed in MFU.

Table 26 Anomalies Fixed in MFU 

Bug ID	Description
CSCdt90381	Symptom: A small outage (approximately 10 msec) occurs on VPCs terminating/originating on BXM. Conditions: This will occur only during hitless rebuild. Workaround: None.
CSCdu21825	Symptom: The WINGZ shows the RX Network stat as zero even when data flows through the network. Conditions: This occurs only on a BPX-SES Network. Workaround: The data at the CLI shows the correct statistics, For right now the CLI data can be used instead of WINGZ.Or Use MFU or later image.
CSCdu71237	Symptom: BXM card did not automatically switch to standby card Conditions: This symptom occurs when Non Fatal Error "0xc000002" occurred on BXM trunk card, and the traffic worsened. Workaround: None.
CSCdv31049	Symptom: BXM sets K1 Tx to Force Switch instead of Reverse Request even though remote had already been sending a Force Switch. BXM, however, maintains the correct line. Conditions: Remote end already had a Force Switch to Working line in effect, and local BXM receives a user command to do a Force Switch to the Protection line. Workaround: Clear the BXM Force switch command.
CSCdv89925	Symptom: ACR is only 10 when VC shaping is enabled for UBR con Conditions: Trunk VC Shaping feature on BXM card is configured between two nodes. UBR connections are routed between the nodes. Workaround: None.
CSCdv77996	Symptom: dspapsln reports wrong info w.r.t. APS when one of the yred cards is out. Conditions: This bug fix is available in firmware release MFR, but SWSW bug fix should be there in order to have the complete solution. SWSW bug: CSCdw35862 9.3.30 MJ01 Further Problem Description: When one card of APS pair is removed, then reset dspapsln shows lines as ok. Should show card failed or missing.
CSCdw06552	Symptom: Connections should stop passing traffic when dnpnport on UNI port on SES. Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node. Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX Release 2 node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic. When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells. Workaround: None. Note This is a partial fix and relies on a SES DDTS CSCdv48496 for resolution.
CSCdw21798	Symptoms: Forced switch when secondary section has failed is accepted. Conditions: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1. Work around: None.
CSCdw25074	Symptom: When inserting 1E-03 errors into the whole frame of STM-4 trunk 3.1 (errors inserted in the direction A to B) BPX A becomes unreachable i.e. cannot telnet to BPX A. VT to A from another BPX times out and there's an HPOV event stating that the link is down to A. The other nodes in the network remain reachable. BPX node log shows that the BCC has a suspected failure (Which indicates corruption of the BCC self test)a few minutes after inserting the errors into the trunk at B. Removing the errors from the trunk results in BPX becoming reachable. Same problem seen with the other BCC active. This is consistently reproducible. If reroutes on another trunk (e.g. trk 1.1) are taking place when the errors are being inserted into trk 3.1, the connections (which are pref 'd' onto trk 1.1) remain derouted until the errors are removed from trk 3.1. Conditions: Errors inserted at 10 -3 in one direction from A to B cause A to go unreachable. Found in lab environment running 9.2.38 with MFN firmware on 155 and 622 optical card types. Workaround: DNTRK to force a reroute.
CSCdw53395	Symptoms: Traffic disrupted in the via node. No AIS is propagated to other master end if slave end port is down. Conditions: This symptom mostly occurs when MGX 8850 (PXM45) is connected to SES. Workaround: None.
CSCdw54957	Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX (PXM45). Conditions: This symptom occurs in 9.3.3i MFR. Workaround: None. Further Problem Description: When there is a congestion on MGX egress port, MGX 8850 (PXM45) sets EFCI=1 for all SPVCs/XPVCs on that port to the downstream.
CSCdw62999	Symptom: BPX sends a wrong value for K1. Conditions: This symptom occurs in APS interop testing between BPX and AXSM/B OC-3. Workaround: None.
CSCdw63238	Symptom: BXM sends RDI trap to SES which does a dnpnport Conditions: Config is BXM UNI with aps 1+1, SW 9.3.35, FW MFR, SES SW 1.1.71. Workaround: None.
CSCdw75999	Symptom: Dspconstats on an SES CLI for an SPVC connection shows that clp0 discards and clp1 discard counts are interchanged. Conditions: This symptom occurs in SES 1.0(14), BXM FW MFR. Discards, due to the policing action, are reported incorrectly in dspconstats command. Discards due to congestion are reported correctly. Workaround: None. Update BXM FW to MFU or later.
CSCdw88723	Symptom: Say BXM1 is a BME card. BXM2 is normal BXM card running fw image MFC-MFT. Multicast root connection runs from BXM2 to BXM1 and fans out to other connections at BXM1 port 2. We will see high number of ingress cell discards on the root connection at BXM2. Conditions: This symptom occurs with BXM2 running f/w image between MFC to MFT. Workaround: None. Use firmware image MFU or later on BXM2.

Anomaly Fixed in MFT

Table 27 lists the anomaly that is fixed in MFT.

Table 27 Anomaly Fixed in MFT 

Bug ID	Description
CSCdw54957	Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX (PXM45). Conditions: This symptom occurs in SWSW: 9.3.3i, BXM FW: MFR. When there is a congestion on MGX egress port, MGX (PXM45) sets EFCI = 1 for all SPVCs/XPVCs on that port to the downstream. Workaround: None.

Anomalies Fixed in MFR

Table 28 lists the anomalies that are fixed in MFR.

Table 28 Anomalies Fixed in MFR 

Bug ID	Description
CSCdv90721	Symptom: The prevalent symptom is Tx BIP 16 and B-Frame Parity slot errors on BXM-622 or BXM-155 cards. Occasional SIU Phase and Rx BIP 16 errors may also occur on BXM-622 and BXM-155 cards depending on the severity of the problem. Conditions: This symptom can occur with any version of BXM firmware on BXM-622 or BXM-155 cards. The aggregate cell transfer rate of the BXM card is 1,412,832 cells/second so the problem can occur on BXM-622 or BXM-155 cards even if the load on each line is well below line rate. The problem occurs during oversubscription when multiple high speed cards have traffic destined for a particular card through the switching fabric. Workaround: To solve the BCC-4 software error 742 problem, upgrade switch software to 9.1.22, 9.2.31, 9.3.00 or later.
CSCdw16362	Symptom: The BXM card changed the state from active to empty for a particular slot and failed to communicate with the BCC. Conditions: Switch Software was upgraded for the particular BXM and statistics were enabled before the current state. Now the particular slot is in empty state although both front and back cards are present for the slot. This loop happened because of SPVC statistics task. It happens when new spvc_config_stats command comes in the VSI message with more than currently configured stat ids. Due to this the data base will be updated. During this update some flag was not set properly and it leads to a loop. Workaround: A workaround is not known other than the physical removal of the card. Or, use MFR or later images.
CSCdm50659	Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms. Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable. Workaround: Lowering the alarm threshold for MAJOR and MINORHCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR. These thresholds are as low as they can be set currently.
CSCdt82384	Symptom: APS trunk built on bxm-155-4d. sf and sd thresholds set to 5 and UNI-direction non-revertive switching with cnfapsln. Random logic errors inserted into the working pair of the trunk to observe protection switch at sf threshold. Good switch at 1 in 103 and 105 but when 1 in 104 inserted trunk goes unstable repeatedly switching from working to protection and vice versa. Trunk continues to toggle until errors removed. Conditions: This symptom occurs with BXM-155 enhanced cards using APS card cage and injecting 104 error rate into one of the working lines. Workaround: None.

Anomalies Fixed in MFP

Table 29 lists the anomalies that are fixed in MFP.

Table 29 Anomalies Fixed in MFP 

Bug ID	Description
CSCds47753	Symptoms: Card error will happen in standby "VrmDekConnEndPoint Try to delete". Conditions: When standby syncs up with active, it tries to delete a not existing connection. Workaround: The card error indicates that there is a invalid try of deleting a non-existing connection. It should not create any problem in existing or new connection.
CSCds75845	Symptom: There is no ER stamping cell generated from BPX in SES environment. Although, CI is set to be off and ER is on by using cnfabrparam, CI cells are still observed where there is congestion. Conditions: This symptom occurs when the connection is routed by PNNI (created by using SES controller). Workaround: None.
CSCdt55356	Symptom: After configured status of all NNI links to down at SES node svcmgx, then configured all links up. while the 100k SPVC connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by itself. Condition: MGX nodes p2spvc4 and p2spvc3 (via node) both have standalone PXM45-B card. Initially 100K SPVC connections have been established between p2spvc4 and SES node svcmgx endpoints. Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.
CSCdu21842	Symptom: ILMI does not report correct status of the ATM PVCs when Protocol by card is enabled. Conditions: When a BPX is connected to a router through a BXM card and ILMI Protocol is run by the card. Workaround: None.
CSCdu04976	Symptom: Around 200 SPVCs stuck in Rx AIS after resetting BCC. Conditions: Resetting the BCC during resync with a SES controller causes this problem as the AIS bit-map is cleared. PXM: 1.1(50.100)A1 BXM: MF15 SWSW: 9.3.3E Workaround: Unknown.
CSCdu29758	Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value. Conditions: The first couple of loopback cells received have incorrect VCI values. BXM = MFJ, BPX 9.2.31 BXMa-BPX == BPX-BXMb<-> ADTECH (OAM F4Loopback) Workaround: None.
CSCdu63175	Symptom: LOF and Bert_SD alarm uncleared on BXM. Conditions: This symptom occurs with 1+1 APS with bi-direction on BPX and MGX. Workaround: Perform a switchcdred/switchyred on BXM.
CSCdu89263	Symptom: When running XLMI on a BXM port which is connected to an AXSM ENNI port, BXM XLMI sending slot 0 and incorrect port number in the node status msg.BXM XLMI is configured with polling disabled. Conditions: Run XLMI and disable the polling. Workaround: Enable the polling, then disable it.
CSCdv18519	Symptom: In reading MF* BXM MFM fw release notes, it was discovered the Stats collection level 0 is no longer supported in MFM and beyond. Stats level 0 supports 32k cons stats level 1 16k connections. Conditions: This symptom occurs in 9.3.3V. MF21. Workaround: See MFM release notes Stat level 0 no longer supported on Legacy BXM cards.
CSCdv21924	Symptom: By running XLMI, when the NodeStatus message did not get ack back, it would retry every T396 (polling timer), instead of using the correct T393 timer. Conditions: This symptom occurs when XLMI is configured and link/line is down. XLMI NodeStatus retry mechanism kicks in. But a wrong timer T396 was used for retrying interval. Workaround: It does not cause any service interrupting or deteriorating and it won't show up under normal operating condition. If a specific NodeStatus retry interval is really needed, one can configure T396 to that value temporarily before the fix is in.
CSCdv21999	Symptom: BXM sends a port failure VSI message to the controller after switchyred. Conditions: This symptom occurs under yred configuration and running LMI on PNNI port on this card. Switchyred so the standby card become active and the port on standby card from failure state to OK. Workaround: None.
CSCdv32466	Symptom: A ENNI port is still showing as failed after switchyred when it becomes OK. Conditions: Yred and APS 1+1 are configured. XLMI is running on the ENNI port. On the previous active card, the port was in a fail state. When the failure got recovered very quick during the switchyred, BXM missed the OK report to BCC, so BCC still shows this port as fail state. SW and FW version: 9.3.30 MF25 Workaround: None.
CSCdv43448	Symptom: The command dsppnports shows the port in "LostConnectivity" state. Condition: Disable ILMI on BPX using cnfvsiif. Workaround: Reset the card. This problem happens only in MFN. Or, use firmware image newer than MFN.
CSCdv52437	Symptom: Comm Failure after Working line experiences Remote Yellow. Conditions: APS 1+1 bidirectional mode GR-253 and ITU After remote experiences LOS on Protection line, the local active Working line will have a Remote Yellow alarm. This alarm eventually causes a Communications failure, and traffic will be rerouted. Workaround: Use unidirectional mode.
CSCdv57400	Symptom: Customer removes commands under ATM interface or tears vc down and up again the router will send two traps to the BXM VSI port but only looks like it is re-acting to the first trap hence the remote router will receive AIS and then transmit RDI. The connection will never come out of this state unless the remote end from the SES is bounced. Conditions: You must be attached to a PNNI VSI port on the BXM. Workaround: 1. Switch ILMI off on the port. 2. Disable oam-manage on the routers.
CSCdv58157	Symptom: On BXM switchover, the VSI ABR VP falls to MCR. Conditions: This symptom occurs with BXM FW up to MFN (MF30). Standby BXM should collect this VP ABR connection during initial data transfer phase. Standby BXM is inserted later than active card or is reset after connection provisioning. Check with 'rsh slot# sabre GetSabreParams sabre# lcn#' and look for 'Path con' field. Switchover to stdby in this case will cause the problem. Workaround: Reassert/resync all the connections. Use firmware later than MFN.
CSCdv62493	Symptom: BXM does not send Node status counters to BCC. Conditions: XLMI is running on card. Workaround: None. This is an enhancement.
CSCdv66806	Symptom: Dax connection does not get rerouted if added when slave interface is down; and later when slave interface is brought back up. Conditions: This is applicable only for dax connections on SES - not on MGX (PXM45). Workaround: Delete and re-add the dax conn when the slave interface is up. It will get routed.
CSCdv86166	Symptom: A feeder trk shows UNREACHABLE after switchyred, while it was actually up and running without any communication problem. Conditions: When running FDR-LMI in a yred pair, the FDR trunk was in a fail state. After switchyred, the FDR trunk changed its state to be OK, however, dspnode still shows this FDR trk was in the unreachable state. Workaround: This is not service impacting, although the FDR trunk shows as unreachable. To get the correct state, reset the card.

Anomalies Fixed in MFN

Table 30 lists the anomalies that are fixed in MFN.

Table 30 Anomalies Fixed in MFN 

Bug ID	Description
CSCds08461	Symptoms: Incorrect operations (SF_LOW sent) after detecting mode mismatch. Conditions: BXM is configured as APS 1+1 Bidirectional mode, and is attached to a node configured as 1+1 Unidirectional. Workaround: Manual administrative intervention to synchronize both nodes to the appropriate mode.
CSCds53524	Symptom: SWLOG error 109 on BPX. Conditions: This symptom occurs with SWSW 9.3.10, Cards: BXM 155 while adding connections between BPX nodes found a swlog 109. Workaround: A workaround is under investigation.
CSCds78285	Symptom: Connections in failed or BuildingVC state. Conditions: CAC policy was not downloaded to some of the BXMs. Workaround: None.
CSCds91102	Symptom: BXM card interfaces went into provisioning state. Conditions: BXM card was reset and PXM did a resync. Workaround: None.
CSCdt35547	Symptom: Cell drops at a CBR connection when a CBR connection and an ABR connection are congested at an ENNI trunk Conditions: This symptom occurs when congestion exists at an ENNI trunk in a AR/PNNI hybrid network. Workaround: None.
CSCdt38471	Symptoms: The available BXM TCB buffer went down to zero and the card got stuck. Conditions: This happened in the 100k SPVC devtest setup. The problem can be reproduced by performing switchyred on two BXM redundancy cards. Workaround: The reasons to cause TCB buffer leakage were found. Furthermore, the holes in the firmware code have been sealed. The fix will be included in the firmware releases MFM or later.
CSCdt41728	Symptoms: Card error VrmRetLcnResources was observed. Conditions: This bug is reproduced in 100K network when port 1.2 of orses7, which is connected to Adtech is seeing temporary LOS. This happened when Adtech is power cycling. Also 1.2 is the end point of 6666 routed SPVCs. Workaround: None.
CSCdt53756	Symptom: SES had huge CDV value compared to MGX 8850 PXM45. Conditions: This symptom always occurs. Workaround: None.
CSCdt55356	Symptom: After configured status of all NNI links to dwon at SES node svcmgx, then configured all links up while the 100k SPVP connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by themselves. Conditions: MGX nodes p2spvc4 and p2spvc3 (via node) both have standalone PXM45-B card. Initially 100K SPVC connections have been established between p2spvc4 and SES node svcmgx endpoints. Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.
CSCdt68427	Symptom: After dellp is done traffic is not right when VP connection and cnfln VC shaping enable. Conditions: A dellp was done on a VP with VC shaping enabled. Workaround: None.
CSCdu08104	Symptom: AR connections do not pass traffic or some links be in comm fail condition. Conditions: The intermediate devtest release for VC-merge project had a problem. On downloading this image would some time bring down the trunk. Workarounds: There are no known workarounds.
CSCdu12049	Symptom: BXM Card switches on Nortel exercising to test APS Link. This happens every time test is completed. Conditions: BXM card is not reacting to K1 bits correctly. Workaround: There are no known workarounds.
CSCdu20728	Symptom: One end of the trunk experiences unbalanced Rx/Tx high priority cells in dspqbinstats. Any CBR traffic on the trunk will not be seen in the CBR QBIN stats. Conditions: Unknown. Workaround: None yet.
CSCdu22039	Symptom: F4 F5 Code mapping modifications. Conditions: None. Workaround: None.
CSCdu23725	Symptom: Attempt to configure the booking factor on a UNI port failed. Error message: ERROR: Switch Response returned Failure Conditions: The conditions for the error are unknown since the CAC feature on the UNI port hasn't been studied before and there were many activities such as addcon, cable failure prior the problem detected. Workaround: Unknown.
CSCdu26023	Symptom: When PNNI and MPLS partitions are configured in a interface with no common pool of bandwidth, only one of the partition will be working fine and the other partition will not come up. Conditions: When PNNI and MPLS is configured in an interface with no common pool of bandwidth, due to the rounding up of the bandwidth for each service type in PNNI by policy parameters, the total bandwidth of a partition, resulted from adding bandwidths of all service types, will go beyond the max bandwidth of both partitions. Because of this, only the first partition will succeed and the other partition will be rejected by CAC. Workaround: Provide at least 20 cells of common pool using cnfrsrc command.
CSCdu29758	Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value. Conditions: This condition occurs with BXM=MFJ, BPX 9.2.31. Setup BXMa-BPX==BPX-BXMb<-> ADTECH (OAM F4Loopback). Workaround: None.
CSCdu44350	Symptom: Although equipment is NOT connected to PROT Line, Standby Line Alarm Status is OK on dspapsln. This symptom appears when CDERR is logged at timing of addapsln. Conditions: Standby line is not connected to equipment. Workaround: None.
CSCdu48766	Symptom: VI programming on enhanced cards is improper. Conditions: Virtual trunks were dropping all cells. Workaround: None.
CSCdu50129	Symptom: While CWM coldstart then down two links with 32K connections at orses2 nodes. CWM can not sync up with orses2 node any more and stuck in mode 2. Condition: There are 50K SPVC DAX connections at node orses2. Workaround: CWM needs to coldstart again.
CSCdu59151	Symptoms: APS commands switchapsln F/M on PXM fails. Condition: BXM running image MF20 with APS configured as ITU-T Annex A and the remote node is any box that strictly adheres to G.783 Annex A, specifically regarding not sending "mode" bits. Workaround: Do not use image MF20 for ITUT Annex A.
CSCdu59240	Symptom: Alarms on 1:1 APS BPX side uncleared after 1:1 APS back to Bi-dir on MGX side. Conditions: This symptom occurs with 1:1 APS with bi-dir on BPX and 1:1 APS with uni-dir on MGX. Workaround: Unknown.
CSCdu62336	Symptom: Code clean-up. Conditions: None. Workaround: Unknown.
CSCdu67053	Symptom: When BXM OC-3 card was downgraded from M.F.21 to M.E.K continuous card errors were being logged. Condition: M.E.K. FW was burned on the standby card that was configured for Y-Red and had APS 1+1 lines configured with traffic. Workaround: Use matching firmware versions on YRED pair.
CSCdu75130	Symptom: Active card in the y-red pair continuously making the connections. Resource usage in active and standby card differs. Conditions: 1. Active card up & running 2. Intracard connections between two interfaces on the same BXM. 3. Booking factor less that 100% on above interfaces. 4. Standby card is inserted at this time. Workaround: Resetting both the active and standby cards at the same time.
CSCdu82229	Symptom: ILMI polling when "Protocol by Card" is configured to "Yes" is inconsistent and unpredictable. Conditions: When ILMI is running on card and its peer is running version 3.0/3.1, the polling interval timer was set with wrong value, which was the 1/5 of the configured polling interval. For correct behavior, refer to SCM note of this bug. Workaround: Use OAM instead of ILMI.
CSCdu87060	Symptom: pnport on SES goes into building vc state. Condition: Change the signaling VPI using cnfpnportsig. Workaround: Reset the BXM card.
CSCdu88418	Symptom: 1. After SWSW upgrade from 9.2.34 -> 9.3.3W, BXME OC-12 card with APS 1+1 setup logged swsw err. 105 and card errs. 2. This problem have been observed several times before. Conditions: This event happened after SWSW upgrade. Workaround: Need DE input.
CSCdv08977	Symptom: Unable add PNNI VSI connections on a y-red BXM pair when upgraded from BXM to BXM-E. Standby card not in SYNC with active card. Policy parameters for the first interface/partition on the active card missing. Conditions: This symptom occurs with BXM Firmware MFN and before. Any SWSW supporting hot upgrade on BXM. Upgrade procedure is followed to upgrade a y-red pair of BXM from BXM to BXM-E cards. Note that the policy parameters for the first interface/partition on the active card are messed up. If this interface has booking factor less than 100% then above defect will surface. Workaround: Reset both the BXM cards after upgrade. Or, use MFN or later BXM FW before upgrade and on enhanced cards.
CSCdv17853	Symptom: Fix compiler warnings. Condition: None. Workaround: None.
CSCdv18775	Symptom: BXM card err. ilmi_task.c 323 pIlmiWd: SoItcSend Failed (currsize 500). Conditions: 1. This problem occurs after burning BXM FW MF21 -> MJ04. 2. It occurs after switchyred. 3. It occurs after rerouting of connections. Workaround: Need a fix from BXM FW DEs.
CSCdv30471	Symptoms: Active and Standby card do not sync up in terms on number of connections. VSI yred pair. Conditions: FW image prior to MFN. When VSI partition 3 is used by controller. Workaround: Do not use partition 3.
CSCdv30755	Symptom: Traffic discontinuity on SPVC connections on consecutive switch-yreds on BXMs. Condition: To begin with, BXM with UNI interfaces should have de-routed connections which are later routed properly. This can happen during initial provisioning of the SPVCs or on re-routing the connections after trunks (NNI) go down and up. Two or more consecutive switchovers on the BXMs hosting UNI interfaces (persistent endpoints of SPVCs). Workarounds: 1. Reroute/resync all the connections and reset the standby card once active card has all connections. 2. Do no do BXM switchovers more than once. 3. Reset standby card before doing the first switchover.

Anomalies Fixed in MFM

Table 31 lists the anomalies that are fixed in MFM.

Table 31 Anomalies Fixed in MFM 

Bug ID	Description
CSCdr16007	Symptom: ILMI trap atmfVccChange returns invalid agent-addr (48.48.48.48), while the correct one shall be (0.0.0.0). "ERROR Invalid agent-addr". Conditions: The error happens during adding or deleting connections. Workaround: None.
CSCdr44694	Symptom: ILMI trap atmfVccChange returns incomplete information. "variable-bindings (none)". Conditions: The error happens during adding or deleting connections. Workaround: None.
CSCds06835	Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk. Conditions: CC traffic is passed across virtual trunks. Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.
CSCds74110	Symptom: The second leaky bucket doesn't adhere to the leaky bucket algorithm. When testing a VBR connection on a BXM-E3 you can burst over the expected value for the connection. Conditions: A connection can exceed his calculated burst size for a VBR connection. Workaround: There is no workaround.
CSCds75477	Symptom: When a delay of over 200 ms is introduced to a trunk with a Addtech tester, 75% of the time the tstdelay result gives a reading lower than the actual RTD. The expected reading would be over 400 ms but instead it is 150 ms. Conditions: The tstdelay test reports inaccurate results. Workaround: None.
CSCdt21547	Symptom: There is no command available to clear SPVC statistics on SES controller. Conditions: SPVC statistics cannot be cleared via SES Workaround: None.
CSCdt36060	Symptom: The tstdelay command intermittently fails. Conditions: Tstdelay intermittently failed when BPX is configured as a segment endpoint for VCC and VPC established between a MGX abd BPX Workaround: None.
CSCdt43471	Symptom: 1. Card errors of "Non Fatal Error id: 0x12000003" 2. Unknown VPI/VCI in dsptrkstats and dspportstats Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs. Workaround: None.
CSCdt44670	Symptoms: The available BXM TCB buffer went down to zero and the card got stuck. Conditions: This happened in the 100k SPVC setup. The problem can be reproduced by performing "switchyred" on two BXM redundancy cards. Workaround: None.
CSCdt45820	Symptom: 1. Card errors of "Non Fatal Error id: 0x12000003" 2. Unknown VPI/VCI in dsptrkstats and dspportstats Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs. Workaround: None.
CSCdt45966	Symptom: Resync process starts and SPVC connections are re-asserted on BXM switch over. Condition: Intra-slave (DACS) SPVC connections are conditioned (AIS/Abit generation) due to external factors. Workaround: None.
CSCdt46282	Symptom: On SPVC connection CDVT programmed is not observed when testing. Conditions: When user tries to set up the CDVT value to less than 10 ms due to a bug in the firmware BXM uses the value 250 ms. Workaround: Use values above 10 ms.
CSCdt48062	Symptom: Ports remain in "provisioning" state on SES. Condition: Enable /disable the partitions on BXM interfaces (specially on engineering BXM images after MFJ between MF08 to MF12). Workaround: Do not re-enable the partition after disabling it. BXM need to be reset if re-enabled configuration has to take effect.
CSCdt58185	Symptom: The CESM-E8 dropped cells after 1/2 hrs. (Seeing the clock synchronization problem. Conditions: This symptom occurs when selecting a clock from the trunk or passing the sync along the trunk. BXM-OC3-D or DX (enhanced) card did not behave properly. Workaround: Use any other type of BXM card except for the BXM-OC3 enhanced.
CSCdt78404	Symptom: 70K SPVCs stuck in Rx side AIS after resetsys/switchcc on PXM overnight. Conditions: SPVCs stuck in AIS state. Workaround: Reset BXM card.
CSCdt75817	Symptom: Asymmetric ABRSTD connections using VSVD will not ramp up ACR to higher than the lower PCR setting. Conditions: It happens when an asymmetric ABR connection is added or modified. Workaround: The problem was identified as incorrect programming SABRE chip and has been fixed in MFM or later FW.
CSCdt80542	Symptom: BXM does guarantee at least MCR value on ABR connection on a congested port. Condition: Traffic was pumped on a congested port having ABR connectiions. Workaround: Unknown.
CSCdt88482	Symptom: The available TX cell rate is lot smaller than available RX cell rate. The available TX cell rate for signalling is a huge negative number Condition: 100K SPVC connections have been established between MGX and BPX nodes. Workaround: Reset BXM card.

Anomalies Fixed in MFL

Table 32 lists the anomalies that are fixed in MFL.

Table 32 Anomalies Fixed in MFL 

Bug ID	Description
CSCds15145	Symptom: Max BW could be configured as less than Min. Conditions: This might happen as the policy parameter might not be checked for the consistency. Workaround: Do not configure Max below min.
CSCds06835	Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk. Conditions: CC traffic is passed across virtual trunks. Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.
CSCds75221	Symptom: When Issuing the command "dspconstats" for ABR or UBR connection it does not report the CLP0 and CLP1 correctly. Conditions: Statistics for ABR and UBR are not updated. Workaround: None.
CSCdt38554	Symptom: After executing resetsys on the node (svcmgxpxm45) pxm1 cards. There are two ports stuck in building vc. Conditions: The node (svcmgxpxm45) has 100k routed SPVC connections. Workaround: Unknown.
CSCdt45966	Symptom: Checksum calculation is not correct in BXM. Conditions: Connection conditioning occurred via bulk set command. Workaround: Uppnport/dnpnport on UNI and NNI port, and do switchyred to kick resync.
CSCdt48062	Symptom: Port gets stuck in building VC state. Conditions: This symptom occurs with connection admission control. Workaround: Establish connections of various service type and bandwidth requirements.

Anomalies Fixed in MFK

Table 33 lists the anomalies that are fixed in MFK.

Table 33 Anomalies Fixed in MFK 

Bug ID	Description
CSCdt21322	Symptom: BXM load info returned to controller is wrong when maxbw set to 0. Conditions: Reproducible. Workaround: None.
CSCdp16050	Symptom: maxvc functionality for CAC not working. Conditions: Reproducible. Workaround: None.
CSCdt04632	Symptoms: For a VSI partition, the reporting available number of LCN is greater than the maximum number of LCN configured for that partition. Conditions: This symptom occurs when the port group unused LCN is less than the maximum LCN configured for the partition, and the unused LCN for the port group plus the LCN that still left from the reserved (min-curr) is greater than the maximum of the partition. Workaround: None.
CSCds85653	Symptom: BXM card error of "cb_if.c 1588 CbCoreTxEvent(): Failed core_cbmsg_put: return. Conditions: This symptom occurs continually doing switchcc with large amounts of AR/SPVC connections. Workaround: Reset BXM card.
CSCds76142	Symptom: BXM card shows standby-failed status. Condition: Download firmware on standby card. Workaround: Reset BXM card.
CSCds65105	Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than'To Port'. Conditions: This symptom occurs with DAX connection from BXM-622 port 1-2 on the same node with ADTECH generating traffic. Workaround: None.
CSCdr19696	Symptom: User never gets to know when the line is out of SD/SF condition.Both the APS lines always show in OK state in dspapsln. Conditions: APS Line switches to standby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition. Workaround: Use rsh command to get all the APS line status.

Anomalies Fixed in MFJ

Table 34 lists the anomalies that are fixed in MFJ.

Table 34 Anomalies Fixed in MFJ 

Bug ID	Description
CSCds61912	Symptom: After downloading new firmware(MF30), card in failed state. Conditions: This symptom occurs when downloading MF30 firmware release. Workaround: Do not use MF30 which is a development release between MFH and MFJ.
CSCds11506	Symptom: Minimum guaranteed cell rate shows a cell less than configured. Conditions: Set minimum BW to say 3333334 and policy BW% to 5859. Workaround: Increase the minBW by few cells.
CSCdr19696	Symptom: User never gets to know when the line is out of SD/SF condition. Both the APS lines always show in OK state in dspapsln. Conditions: APS Line switches to standby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition. Workaround: Use rsh command to get all the APS line's status.
CSCds32845	Symptom: Connection commits rejected with reason no resources even when resources are actually available. Conditions: Enable/disable a virtual trunk. Workaround: Reset the BXM after disabling a VT on any interface on the card.
CSCds37237	Symptom: When upgrade BXM firmware image to BXM MFH from images between BXM MFC-BXM MFF, if the network migration flag was enabled in a card before the upgrading, then after burning the new image to the card, the network migration flag becomes disabled mistakenly. Conditions: The problem only happens to the card whose previous image is BXM MFC-BXM MFF, and the network migration flag was enabled before upgrading, and BXM MFH has to be the new image. Workaround: Upgrading to image BXM MFH+ (not including BXM MFH), will not have any problem. Network migration flag is always enabled, and no user command available any more to disable it. Only for the situation you need to upgrade image to BXM MFH and your card's previous images is BXM MFC-BXM MFF, you may see the problem. The workaround is, issue either the "rsh <slot> cdcfg network dis" command before the upgrading, or "rsh <slot> cdcfg network ena" after the upgrading, to enable the network migration flag on BXM MFH.
CSCds59710	Symptom: Loss of traffic on a VPC connection added with VPI = 0. Conditions: This symptom occurs with SWSW: 9.3.10. BXM FW: MFF The port on which the VPC connection has been added has a VSI Controller attached to it and the Controller is usingVPI = 0 and VCI = x for its signaling channel. Workaround: If a VPC connection exists with VPI = 0, on the port to which a Controller is to be added, configure the signaling channel on the controller side to use a VPI other than 0.
CSCds63578	Symptom: SW errors 105 logged on BXM while adding VSI connections. Subsequent card errors saying CB_TASK restarted. Conditions: This error sometimes happens when a VSI partition is enabled/disabled many times. Workaround: Reset the BXM.
CSCds65105	Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'. Conditions: This symptom occurs with DAX connection from BXM-622 port 1-2 on the same node with ADTECH generate traffic. Workaround: None.
CSCds67854	Symptom: SPVC cannot be routed over the virtual trunk even when enough bandwidth and LCN are available. Routed connections discard some traffic. Conditions: Route connections of different service types over the virtual trunks. Workaround: None.
CSCds04137	Symptom: Channels remain mismatch after lockout is cleared Conditions: In ITU-T Annex B protocol for APS, when a condition causes a switch to occur while a lockout request is present, the channel change will not resynchronize even after the lockout is cleared. Workaround: No
CSCds53645	Symptom: ABR connections (PNNI) not programmed properly for redundant slave. Conditions: This symptom occurs with switchyred. When connection is added, redundant card is not there and inserted at later stage. When connection is added, there is no redundant configuration; addyred at later stage. Workaround: None.

Anomalies Fixed in MFH

Table 35 lists the anomaly that is fixed in MFH.

Table 35 Anomaly Fixed in MFH 

Bug ID

Description

CSCds14495

Symptom: Dynamic Partitioning and SPVC AIS generation would not work on a card until a rsh command is issued to enable the network migration flag and reset the card. Conditions: When a card comes up and has never enabled the network migration flag for life time.This network migration flag is used for enabling dynamic partitioning and SPVC AIS, status report generations. By default, the flag is disabled. Workaround: Use the "rsh <slot> cdcfg netmig en/dis" command to enable/disable the flag, then reset the card once in a lifetime.

Anomalies Fixed in MFF

Table 36 lists the anomalies that are fixed in MFF.

Table 36 Anomalies Fixed in MFF 

Bug ID	Description
CSCds08448	Symptom: ERS (explicit rate stamping) is working only first virtual trunk and NOT for subsequent VTs (standard ABR). Conditions: When ERS is enabled on a card basis using "cnfabrparm", the mapping is done on a port-by-port basis. The port_vi is used but for virtual trunks, this mapping does not hold true. Need to change the mapping to the physical port. Workaround: On any physical port, just set up one virtual trunks. Or a physical trunk. Multiple VTs on the same physical port will cause a problem.
CSCdr79610	Symptom: Change booking factor for a class of service, get rejected. Conditions: When there are some connections established, and some of the class of service have used bandwidth exceeding their reserved, change booking factor for any class of the service may get rejected. This is because it fails the check which should only be called when cos_min_bw in the policy parameters is changed. This check should not be called when booking factor is changed. Workaround: Disable that partition, change the booking factor, then enable the partition again. Or keep the used_bw for all cos under the cos_min_bw, you will be able to change booking factor freely.
CSCdr76334	Symptom: Connect OC3 port on BXM with 7200 router, connect 2 OC3 ports back to back. Enable ILMI on router, and ILMI, protocol on card cnfrsrc VSI part 1 disable NebDiscovery on ports.when running cnfnodeparm 56 0|1 and With VSI disabled, peer info is transmitted to peer. delcntrl, and cnfrsrc deleting VSI partition, fails to disable Peer information as well. Conditions: ilmi_enable_from_contrl bit was not cleared when delctrlr, or VSI partition deleted, thus VSI code kept issuing get requests and responding to peer information. In AR/VSI hybrid networks, and for backward compatibility either BXMs without NebDisc, or swsw versions. Topo traps are not sent to downreved SWSW versions, and are controllable by SW software for versions including the feature. Code was added to properly support disabling of VSI functionality using delctrlr or cnfrsrc at Bcc in addition to existing dnpnport at the VSI controller. Support for backreved cards added, and corrections to logic in ILMI FSM state machine to properly send TopoTrap to BCC. Workaround: None
CSCdr79936	Symptom: Statistics files not generated/missing on some 15 minutes intervals. Conditions: System time is changed at 15 minutes boundaries. Workaround: Minimize system time and card config changes.
CSCdr83144	Symptom: Card error of "N. Fatal from 0x17: 0x25120075 0x809b5f90 0x367e 0x1." Conditions: This symptom occurs with switchyred, switchcc or reset PXM when there are SPVC connections with statistics enabled. Workaround: None.
CSCds11484	Symptom: Available cell rate reported by BXM is incorrect. Conditions: Sum of the minimum bandwidths of all the interfaces on a BXM reaches OC12. Workaround: Reduce minimum BW on all interfaces by half.
CSCdr89217	Symptom: Software Error Log of 9098 Conditions: This symptom occurs with cnfrsrc of partition 3 using MEB firmware. Workaround: None.
CSCdr89966	Symptom: Card Error of 0x41030006. Conditions: PXM controller is upgraded/re-booted. Workaround: None.
CSCdp89085	Symptoms: The total call count becomes negative on the BXM interface. However, this problem has not been reproducible. Conditions: If this problem happens, the following card error is displayed: 'vsi_rsrc_pfns.c 483 VrmRetLcnResources 3, 16316' Workaround: A related bug CSCdr86894 which reported an incorrect number of total call counts, has been found to be the result of an uninitialized variable in vsi_rsrc_conn_pfns.c: VrmRsrcClrRCMP(). The debugging information embedded in this function may be helpful in verifying the negative call count problem if it is reproduced.

Anomalies Fixed in MFE

Table 37 lists the anomalies that are fixed in MFE.

Table 37 Anomalies Fixed in MFE 

Bug ID	Description
CSCdp05098	Symptom: Cell discards occur for ABRFST/ABRSTD connections when the traffic burst is greater than the MBS. Conditions: This occurs when the traffic burst size is fixed to 140000 cells at 70000 cps. The connections are configured with PCR=72000/72000, MBS=1000/1000 and ICR 7200/7200. This is the expected behavior since the configured MBS < the actual burst size. Workaround: Increase the MBS and ICR using cnfcon.
CSCdr59731	Symptom: Port 11.1 is connected to 11.2 and ILMI are up and running on both ports. Enable neighbor discovery on 11.1, then 11.2. The 0x71 responses/traps from BXM fw is not predictable. At least two variations are observed: 1. Port 11.2 has it's neighbor's info but port 11.1 does not. 2. Both port 11.1 and 11.2 only know the IP addresses of their neighbors. The Neighbor's IFName are missing. Problem was observed in MF17, but code changes in more recent builds had already repaired the problem. Conditions: When ILMI session restarts, remnants of IfName, IpAddr from previous session left. Clr/reset IfName, IpAddr in MIB, on ILMI session restart In FMSStart, pIlmiProcessFsmStart () calls a new function IlmiClrPeerAndSendTopoTrap (pcb_ptr->session_id).
CSCdr79936	Symptom: Statistics files not generated/missing on some 15 minutes intervals. Conditions: This symptom occurs when system time is changed at 15 minutes boundaries. Workaround: Minimize system time and card configuration changes.
CSCdm16800	Symptom: Card error 0xc000007 appears in the card error log. Conditions: This error indicates that an unknown type of cell which is not expected has arrived in the egress QE. Workaround: Engineering has done in-depth investigation into this case. We are convinced the problem does not affect user traffic or the node in any other way. Therefore, the symptom will not be reported as a card error. The fix has been incorporated into MEE firmware.
CSCdp22930	Symptom: N/A Conditions: Cbus rd/wr operations set up in the PUUMBA chip when performing cbus rcv/xmit. Workaround: None.
CSCdp74680	Symptom: Even if the interface is in LOS, the SPVCs do not generate ingress AIS into the network. Conditions: Connection is added after the interface goes into LOS. Workaround: None.
CSCdr44250	Symptom: Private image did not allow as many OAM cells to flow as public image. Conditions: This occurred by undoing a hardware fix in a private image. Workaround: This was never introduced into the Public view and no workaround is required.
CSCdr45986	Symptoms: Standby and active block checksum value do not match and resync happens on switchover. Conditions: Active card has many SPVC connections derouted it happens. Workaround: None.
CSCdr71473	Symptom: Unreachable BXM, sw errors and cd errors on the BPX. Conditions: LMI is enabled when controller either slow to respond or unreachable. Workaround: Disable LMI.
CSCdp97307	Symptoms: Executed "rsh <slot> vsi cm VsiIs " without parameter. The card will crash. Conditions: Always. Workaround: Pull out the card and reinsert.
CSCdr86894	Symptoms: Many ports have VC failure because BXM has no resource to build the SVC. Conditions: Intermittent. Workaround: Reset BXM card.
CSCdr57712	Symptom: Multi partition fails to report all virtual trunks. Conditions: This symptom occurs in case of virtual trunks with different partition. Workaround: Reset the BXM card.
CSCdr77238	Symptom: Switch General Info does not contain bulk set capability bit. With newer images of PXM bulk set will not work with BXM images prior to MFD. Conditions: PXM images later than 07/06/2000 contain logic to identify the bulk set capability of the slave. BXM images prior to 07/06/2000 will not have this bit set because it is newly introduced parameter in VSI spec. Workaround: No workaround. Need to upgrade to MFD.

Anomalies Fixed in MFD

Table 38 lists the anomalies that are fixed in MFD.

Table 38 Anomalies Fixed in MFD 

Bug ID	Description
CSCdr29278	Symptom: Originally the card used to get frozen not responding to any request from the controller, as the TCB database was corrupted. But it has been protected now. But whenever a null pointer is being inserted into the TCB list a card error is being flagged. It is a harmless card error (not service affecting) Conditions: The cause is unknown. Workaround: None.
CSCdp63445	Symptom: ABR and UBR connections loose traffic when VC shaping is turned on. Conditions: Enabling of VC shaping on port terminating ABR and UBR connections. Workaround: Leave VC shaping disabled.
CSCdr30454	Symptom: Connections (LCNs) can not satisfied because of insufficient memory Conditions: Channel stat level is set to 0 Workaround: Use chan stat level (cnfcdparm) 1, 2 or 3.
CSCdr14247	Symptom: The correct state of an SPVC is not reflected in connection bulk traps for large number of connections (> 1000). Sometimes Connection states keep toggling between AIS and CLR state when the connections are actually in AIS state Conditions: AIS cells generated by the RCMP on different connections arrive too close to each other in the same second. This sudden burst of cells overwhelm the Class of service buffers (QBINs) in the Egress direction and get discarded. This causes remote end of the trunk to detect a loss of AIS cells and declare connection a CLR. Workaround: None.
CSCdr40204	Symptom: Service rate for VBR traffic when WFQ is enabled is at SCR (instead of PCR) even when there is no congestion for enhanced cards (1210 QE and Sabre) Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level. Workaround: None. Has been fixed.
CSCdr42885	Symptom: All the ports on a BXM slave go into provisioning state. Conditions: Controller looses communication with the BXM. This happens when AAL5 driver in the BXM malfunctions and does not free the message buffers of the application processes (ILMI, VSI, and so forth). Eventually BXM runs out of message buffers. Workaround: Reset the BXM card.
CSCdr49056	Symptom: Invalid Part id in SPVC stats after controller is added. Condition: This problem happens when SFM receives the VSI message before adding the controller. This is possible to happen when there is a delay between 52 and 61 message. Since 52 add the control vc it will receive the frame and give it SFM task. But SFM does not have any information for that partition and will report the error saying that invalid partition. Since this is possible to happen as per design, the card is removed now. Workaround: None.
CSCdr40234	Symptom: Service rate for UBR traffic when WFQ is enabled much lower than PCR even when there is no congestion for enhanced cards (1210 QE & Sabre) Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level. Workaround: None. Has been fixed.
CSCdr49060	Symptom: When doing a cnfcon for ABR connection, service rate drops to MCR rate even when there is no congestion. This is when WFQ is enabled and the inherent VSVD is not used. Conditions: There are a certain parameters associated with WFQ that are required in order for WFQ to work. However, for ABR connections, when a cnfcon is done, once it is detected that VSVD is not enabled, the structure (Sabre rate RAM) which holds all these parameters is cleared out. This would cause WFQ not to operate properly. Workaround: No need. Fix is done.
CSCdr43012	Symptom: All the ports on a BXM slave go into provisioning state. Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck. Workaround: Reset the BXM card.
CSCdr52195	Symptom: All the ports on a BXM slave go into provisioning state. Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck. Workaround: Reset the BXM card.
CSCdr36963	Symptom: When PNNI controller goes down then comes up, it couldn't establish its control call to the BXM partition, thus VC failure is displayed in PNNI controller for that partition. Conditions: This problem only happens under the following conditions: 1. The policy parameters for the partition have been configured as nonzero at some of the class of service. The reserved minimum bandwidth of some class of service are nonzero. 2. Delete/disable that partition. BXM suppose to release all resources. However, it only released resources at partition level, but leave the reserved resources at CoS level unchanged. As result, when this partition is enabled again, the internal CAC calculation at partition level became negative. That caused the first control call setup request fail. Workaround: Reset the BXM card will clear the VC failure.
CSCdr33867	Symptom: Connect OC3 port on BXM with 7200 router, enable ILMI on router, and ILMI, protocol on card and Neighbor Discover, Object 0x31, Peer's IfName is not null terminated. Conditions: Some peer.ifName's are null terminated. Some names are not a PDU containing valid nonzero length peer.ifName does not always include '\0'; and is stored accordingly in the MIB. added a test if peer.ifName is non-zero in length, and isn't null terminated, concatenate the '\0'char and bump peer.ifNameLen++ count Added logic CbIlmiStatsReport, ilmi_proc.c pIlmiFsmGetResponseEventAtS3, pIlmiFsmGetResponseEventAtS9, ilmi_fsm_evt.c to ensure TopoTrap, and ILMIStats report are correctly formatted. Workaround: None.
CSCdp48306	Symptom: On NNI side, when cross connect is established with VPI>1000 (0x3e8) the first nibble is getting chopped off and traffic is flowing on VPI 0xe8 due to bad programming of connection. Conditions: This happens if on NNI side VPI > 0xff. Workaround: None.
CSCdr51875	Symptom: Virtual Trunking causing Unreachability Conditions: At least two virtual trunks share a common port at one node, but their remote endpoints terminate on different nodes. The virtual trunks are used to carry networking (rt_op) traffic. The simplest example follows below: node_A ---- vtrk ----  /---- vtrk ---- node_C   /   / node_B (vtrks share common port) With this topology, "node_A" sees "node_C" as unreachable and vice-versa; however, "node_A" communicates to "node_B", and "node_B" communicates to "node_C". Workaround: Customers who are already using VT wraparound should continue to do so under 9.2.3x until the fix is available. BXM virtual trunking (no VT wraparound) can still be implemented using software release 9.2.2x. If virtual trunks are not yet in use, the VT wraparound solution can be implemented in release 9.2.3x.
CSCdr57805	Symptom: Card errors show up indicating "CB_TASK is ready" Conditions: CB_TASK gets busy processing VSI messages and this causes root task to incorrectly assume that CB_TASK is not in a sane state. Actually a firmware change incorrectly reduced the polling interval by the root task such that it was polling the states of tasks sooner than it is supposed to. Workaround: None. Ignore these card errors as these are benign.
CSCdr56931	Symptom: After resetsys on PXM or bouncing the feeder/control port or reset of BXM card, some virtual trunks go into vc failure/building vc state. Conditions: Resetting PXM or pulling out the cable connecting the BXM feeder port to the controller or resetting the BXM cause the interface set policy parameters to be sent to the BXM. This cause ingress BW to be recomputed. CB_TASK passes VI numbers 0 to 31 to the CAC module which expects the range 0 to 15. This caused the problem by overindexing the CAC structures. Workaround: None.
CSCdr59241	Symptom: Building VC status on UNI ports after repeated enabling/disabling of partition with the control port Conditions: Controller does not send policy parameters for control port upon enabling of partition. When disabling partition, CoS max bandwidth was zeroed out. With no policy parameters from which to obtain the new values, COS max bandwidth is stuck at zero; thus not allowing ant control to be established. Workaround: Older PXM image does send policy parameters even for the partition with the control port. Control port does not require policy parameters to be sent from controller. Default it to the max bandwidth configured for the partition.
CSCdr51970	Symptom: Change CAC policy parameters will cause the available BW for some CoS to be negative. Conditions: Current implementation does not validate the CAC policy parameter change. It will always take the value. However, in some cases, improper policy parameters change will cause the avail_bw at CoS level go negative. In this particular scenario, the current used bandwidth of a CoS is equal to its reserved minimum bandwidth.Then the user changed the policy parameter to make this CoS min_bw to smaller number. Now current_used_bw for this CoS is greater than its reserved, and it has to obtained bw from the common pool to maintain its currently used bw. However, the user changed the policy parameter again, to increase the reserved bw for another CoS, which caused the common pool to be zero.Therefore, by normal calculation, the previous CoS avail_bw becomes to negative. Decreasing cos_min_bw to be less than it is currently used_bw is an invalid operation and should get rejected, otherwise it will mess up the CAC. Workaround: Delete some connections to release bandwidth before decreasing CoS minimum bandwidth.
CSCdr66273	Symptom: The encoding is in the reverse of the expected value by UNI4.0 spec. Conditions: This symptom occurs with STD ABR connections. Workaround: No workaround.

Anomalies Fixed in MFC

Table 39 lists the anomalies that are fixed in MFC.

Table 39 Anomalies Fixed in MFC 

Bug ID	Description
CSCdp63445	Symptom: ABR and UBR connections loose traffic when VC shaping is turned on. Conditions: Enable VC shaping on port terminating ABR and UBR connections. Workaround: Leave VC shaping disabled.
CSCdr11396	Symptom: Data transfer has affected while running OAM loopback. Conditions: All user data is dropped when send in 960 cps of OAM. Workaround: None.
CSCdp11511	Symptom: BPX treats segment OAM loopback different from end-to-end OAM loopback cells. Conditions: None. Workaround: None.
CSCdr13208	Symptom: BXM CD errors while running OAM cells. Conditions: 1. One PVC has 2880 cps of data and 960 cps of OAM cells. 2. Another PVC has 2880 cps of data and 960 cps of OAM cells. Workaround: None.
CSCdr13196	Symptom: BPX reports SWERR 105. Conditions: SWERR105 is logged while running OAM loopback test. Workaround: Reset the BXM card.
CSCdr13182	Symptom: tstdelay/tstcon/tstconseg for all PVCs on that card will fail. Conditions: User sends in >= 960 cps of OAM loopback cells. Workaround: None.
CSCdr13151	Symptom: dspportstats always show Tx port = 0. Conditions: Send in >= 960 cps of OAM loopback cells. Workaround: None.

Anomalies Fixed in MFB

Table 40 lists the anomalies that are fixed in MFB.

Table 40 Anomalies Fixed in MFB 

Bug ID	Description
CSCdm52254	Symptom: Random BIP-8 errors show up on T3 when running in direct map (HEC) mode. There is no such thing as a BIP-8 error in the direct map mode. But this counter should report 0 in this mode. Conditions: This is totally random due to the fact that an uninitialized (don't care) counter variable is accumulated in every poll period. This counter is not even read from hardware in the HEC mode. Workaround: Ignore BIP-8 errors when the T3 trunks are configured in the HEC mode.
CSCdm62817	Symptom: tstconseg command sometimes does not work. Conditions: Execute tstconseg multiple times with high loop count (10). Workaround: None
CSCdm84853	Symptom: BW reported via interface load info is erroneous. Conditions: Forward & Backward BW for VSI connections is different. Workaround: None.
CSCdm92931	Symptom: APS line switchover occurs upon card removal when lockout is set. Conditions: None. Workaround: Upgrade to MEF or newer version of firmware.
CSCdp20848	Symptom: SF switchover does not occur after dncd/upcd execution on Annex B 1+1 APS. Conditions: When the dncd command is executed, SWSW sends 0x27 CBUS message. The handler for this message was putting the lines in loopback and shutting down the laser. Also it was changing the line state in SoCdDown() to DOWN state. This caused subsequent upcd (0x05/0x04) message to re-initialize the lines disabling the S/UNI interrupts in the process. Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp24224	Symptom: WTR does not occur after LOS recovery on protection line Conditions: The meaning of primary and secondary channels were changed immediately upon switchover instead of waiting for the expiry of WTR. This caused the clearing of the failure to be accounted against the secondary channel and thus there was no WTR. Fixed by introducing a Preparation switch mode where-in the current active channel will remain as the secondary until a WTR occurs or a primary section mismatch pre-empts that state. At the expiry of WTR, the preparation switch mode is complete and the current active channel becomes the primary. Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp25130	Symptom: APS Non-revertive bidirectional feature. Conditions: Resolved. Workaround: None.
CSCdp25220	Symptom: Avail Buffer on BXM = 0 on LVC flapping for xtag interfaces Conditions: This is same as CSCdp58969. During this condition AAL5 driver doesn't release the transmission buffer. Workaround: Upgrade to/MEF or newer versions of firmware.
CSCdp28931	Symptom: No RDI-P generated when loss of Cell Delineation occurs. Conditions: The cell header so Loss of Cell Delineation occurs. The SONET "PATH RDI" indication is not transmitted as outlined in the UNI 3.1 specification. Workaround: None.
CSCdp32646	Symptom: WTR Timer does not work and reversion occurs during SF switchover. Conditions: Added a preparation switch mode where the current active channel is the secondary channel. At the expiry of WTR, the secondary channel is changed to the become the primary channel. Workaround: Upgrade to MEF or newer version of firmware.
CSCdp35156	Symptom: BPX APS reverts back to the working line before WTR time has expired Conditions: TR was being pre-empted by a spurious SD condition. Fixed by setting the right thresholds for SF/SD based on BER. Workaround: Upgrade to MEF or newer version of firmware.
CSCdp38148	Symptom: Resetcd slot 11 on BPX causes local APS switching. Conditions: Re-impose the selector and bridge states on both ACTIVE and STANDBY cards after Y-red switchover, re-discover the line states and re-execute and external requests.Also include a STABILITY timer before the line state is processed. Workaround: Upgrade to MEF or newer version of firmware.
CSCdp39723	Symptom: APS not functioning in 9.2.21 with FW ME18@sprintf for Bidirectional w/Nonrevertive Conditions: Reversion was happening due to spurious SF/SD events.Fixed by setting the right values for SF/SD thresholds. Workaround: Upgrade to MEF or newer version of firmware
CSCdp46399	Symptom: Need a documentation explains how to setup port groups for FW MEF (me26). Conditions: None. Workaround: No known workaround.
CSCdp49640	Symptom: When FCES feature enable on BXM NNI data transfer stops. Conditions: The ABR parameters like NRM, CRM, FRTT, MCR, ICR were not getting programmed when the FCES is turned on using the cnfcon command. Adding the connection with the FCES enabled behaved properly. Workaround: None.
CSCdp49749	Symptom: Node unreachable after resetting two nodes in the network. Conditions: When com bus message 0x52 is sent down to BXM, we were not handling the case when message says activate the LCN, but delete the VPI and VCI pair specified in the command. Workaround: None. Upgrade to MFB.
CSCdp57596	Symptom: CB_TASK on BXM goes into deadlock state causing VSI session to be lost. Conditions: This happens when both Ingress and Egress qe semaphore is taken by IDLE_TASK and it never released in an error condition. Workaround: None. Upgrade to MEF or newer versions of firmware.
CSCdp58969	Symptom: cb_get.c CB_VPC_STATUS_POLL SoItcSend Failed upon VSI Failure Conditions: When VSI receives and transmits lot of VSI message AAL5 drive, it will get into deadlock problem if it had missed a DMA interrupt. Workaround: None. Upgrade to MEF or newer version of firmware
CSCdp59328	Symptom: EPD bit was not set for interslave control vc. Conditions: This symptom occurs when VSI get congestion (same as CSCdp58969). Workaround: None. Upgrade to/MEF or newer versions of firmware.
CSCdp59727	Symptom: Addlnlocrmt causes node unreachable. Conditions: None. Workaround: Reset the BXM card.
CSCdp59729	Symptom: addlnlocrmt causes node unreachable. Conditions: addlnlocrmtlp causes node unreachable even though there are other parallel trunks. Workaround: No known workaround.
CSCdp60696	Symptom: Both lines fail when only one line in alarm. Conditions: After the standby card comes out of reset, its S/UNI states are not reliable for a period of 1.5 seconds and the S/UNI reports LOS clear on the WORK line. This gets conveyed to the active card and then the Manual switch gets priority and becomes the current local request. This causes a switch back to WORK. When the active card's S/UNI monitors the WORK line, it discovers that the line is in LOS and immediately switches back. The oscillations continue and the line goes into LOCKOUT due to excessive switching. In the Lockout mode only the WORK line is active and thus the defect. Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp62213	Symptom: Switching from bi-dir to uni-dir mode APS generates APS architecture mismatch error Conditions: When APS pair is configured from bi-dir mode to uni-dir mode the other side indicates APS architecture mismatch error, and then the other side is also configured from bi-dir mode to uni-dir mode, the APS architecture mismatch error does not clear. Workaround: Delete APS and then add APS again - it defaults to uni-dir.
CSCdp65320	Symptom: Need a trap when BPX puts APS in lockout. Conditions: Send the traps in the right sequence. First send the Lockout trap and then the failed to switch trap if there is a switch attempt while lockout is in effect. Workaround: None.Upgrade to MEF or newer version of firmware
CSCdp67673	Symptom: dspapsln does not show ARCH_MIS any more. Conditions: dspapsln does not show ARCH_MIS when caused for the second time on the same trunk. Workaround: No known workaround.
CSCdp79156	Symptom: TDP signaling cross connect VSI request rejected by BXM. Conditions: If BPX is configured with trunks and virtual trunks the virtual trunks are initialized properly with qbin size. Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp84386	Symptom: Connectivity w/BXM lost due to missing DMA completion interrupts. Conditions: AAl5 driver will be in deadlock and never transmits and receives. Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp86147	Symptom: The removal of Rx cable of APS trunk leading to loss of Frm and Prot Sw Byt Fail. Conditions: While removing the Rx cable of APS working line (configured to trunk), working line goes to Loss of Frm and dsptrks shows the trunk in alarm. After connecting cable back the APS Alarm status shows "Prot Sw Byt FAIL". Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp89972	Symptom: Node rebuild caused 3 BXM cards failed. Conditions: Moved the allocation and initialization of the Connection database to the SoCoEnterStandby function instead of in the 0x50 handler (SoCdUp). Workaround: None.Upgrade to MEF or newer version of firmware.
CSCdp92916	Symptom: Commands executed on standby card affect APS line. Conditions: Series of commands executed in standby card affects APS line. Workaround: None.Upgrade to MEF or newer version of firmware.

Anomalies Fixed in MFA

Table 41 lists the anomalies that are fixed in MFA.

Table 41 Anomalies Fixed in MFA 

Bug ID	Description
CSCdk42527	Symptom: Rx Queue becomes full after LOS on the feeder trunk. Conditions: This symptom occurs after LOS condition on the feeder trunk. Workaround: Reset the feeder trunk.
CSCdk80483	Symptom: TX cell loss counts in dsptrkerrs increase continuously. Conditions: This symptom occurs when there is trunk configured. Workaround: None.
CSCdk81384	Symptom: BXM slot errors keeps on incrementing on a BCC3 node, but the reading of 'EAP ARFD' should only be interpreted when using the dual receiver feature on a BCC4 node. Conditions: BXM slot has errors on a BCC3 node. Workaround: None.
CSCdm04312	Symptom: The problem is a false failure is declared against the SIMBA Multicast Record RAM. Conditions: The problem occurs when Self Test is activated against a Y-Redundant pair of BME Cards (BXM-622 cards loaded with the multicast BME firmware) that have more than 1000 connections programmed through them. Workaround: Disable Self Test via the cnftstparm command.
CSCdm09295	Symptom: Reconfig of FCES from enable to disable does not work, as a result traffic burst is restricted to MCR. Conditions: This symptom occurs every time changing an existing connection from FCES enable to disable. Workaround: Delete the connection and add back a new one with FCES disable.
CSCdm09882	Symptom: Log non fatal message related to the RCMP errors. Conditions: It is mainly seen in the heat chamber. Workaround: Please make sure the TEST FREQUENCY and TIMEOUT variables under cnftstparm for BXM are set to 4000/3700 level.
CSCdm16505	Symptom: AIS not sent on VP ABRFST/ABRSTD connection. Conditions: This symptom occurs when LOS on trunk between 2 nodes. Workaround: None.
CSCdm31923	Symptom: AIS/YEL alarm does not go away even after the alarm is clear from the other end. Conditions: It happens on the E3 when the LOOP TIME parameter is set to YES in the trunk or line configuration. Workaround: None.
CSCdm39186	Symptom: Card fatal error occurred when running in standby mode under the heat condition. As a result, the card reset periodically. Conditions: Card is running in standby mode under heat condition. Workaround: None.
CSCdm50659	Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms. Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path far end unavailable. Workaround: Lowering the alarm threshold for MAJOR and MINOR HCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR. These thresholds are as low as they can be set currently.
CSCdm52585	Symptom: DspVsiPartInfo shows very large Available LCN field. Conditions: The sum of min-lcns is greater than the max (max lcns) on a port group. Workaround: None.
CSCdm53420	Symptom: switchyred causes APS line to switch when last user request is clear. Conditions: This symptom occurs with APS 1+1 configuration. The protection line was active and the "last user switch request" was clear. When a switchyred was performed, APS line switched to working line active Workaround: None.
CSCdm61493	Symptom: When BIP8 errors are received on an E3 line or trunk at a rate of 10E-3, the line or trunk will not declare any alarm. Conditions: High rates of BIP8 errors are received. Workaround: None.
CSCdm73220	Symptom: Trunks or Virtual Trunks does not allow traffic going through. Conditions: This symptom occurs with SWSW 9.1 with ME level of firmware. Trunks or VTs configured on BXM/BXM-E. Workaround: None.
CSCdm81534	Symptom: ICR of abrfst on BXM-155 falls down to MCR after resetcd. Conditions: Change the ICR after resetcd before start sending traffic. Workaround: None.
CSCdm92916	Symptom: Operational commands (dncd, resetcd, remove) on standby card impact active APS line. When active line is PROT line and a switchover of cards occur, WORK line becomes active line on the newly active cards. Conditions: APS 1+1 Annex B and PROT are active line. switchyred or resetcd on the active card causes line to switchover from PROT to WORK. Workaround: None.
CSCdm92931	Symptom: APS line switchover occurs upon card removal/insertion when lockout is set Conditions: When Lockout is set, removing/inserting the card makes it happen.
CSCdm93274	Symptom: OC3 back card LED is wrong after reset/pull cards. Conditions: Multiple APS lines exist on a card and perform switchyred when Working line is active and Secondary card is active. Workaround: None.
CSCdp11025	Symptom: Use the "dspapsln" to get the screen to display apsln status.When the working line is taken out the LOS appears on the working line. When the protection line is taken out both the working and protection display LOS. When the protection line is put back in the LOS/Alarms on the protection should clear. They do not. Conditions: Physically remove and add the rx or both rx and tx lines as follows: 1. Remove the working line. 2. Remove the protection line. 3. Add the protection line back. Workaround: None.
CSCdp17741	Symptom: 2-portgroup card reports 1 port group at the channel stats level 2 and 3. Conditions: When channel stats level 2 or 3 are configured on BXM-622-2 port and BXM-155 reports only one port group. Workaround: Auto Route connections are not affected by this. But for VSI connections there is no work around.
CSCdp18840	Symptom: The CBR.2 Calls do not pass traffic above 50 Cells/second. Conditions: VSI controller establishes CBR.2 connection and it does not fill in the PCR field. Workaround: Fill the PCR value also with the CR value.
CSCdp22930	Symptoms: Intlock missing for rd/wr operation Workaround: Reassert intLock on commbus ISR to prevent SCC access from getting interrupted.
CSCdp31325	Symptom: UBR cells are policed unnecessarily below PCR. Conditions: Always. Workaround: None.
CSCdp32853	Symptom: The BXM enhanced cards keep getting reset and card errors are logged and node may go into degraded mode, when command "addapsln slot1.port1 slot2.port2 1" is issued. Conditions: This symptom occurs with BXM enhanced OC3 cards with 4 port and FW rel earlier that M.E.22/M.F.09. Workaround: 1. Do not addapsln on second port onwards for BXM-E OC3 4 port card. OR 2. Replace the BXM-E 4 port card with 8 ports card.
CSCdp33894	Symptom: Standby APS line shows status as Path AIS upon switchyred or on APS switchover on LOS. Conditions: switchyred on APS, the prot. line report Path AIS. Workaround: None. Upgrade to ME26/MED or later versions of BXM firmware.
CSCdp36155	Symptom: BXM-E OC3/OC12 does not show supporting APS HW 1+1 in dspcd command and otherwise also. Condition: This symptom occurs with BXM-E OC3/ OC12 card with HW rev < 'C'. Workaround: None.
CSCdp36324	Symptom: Last user request affects switching on BPX. Conditions: None. Workaround: None.

Anomalies Fixed in MEC

Table 42 lists the anomalies that are fixed in MEC.

Table 42 Anomalies Fixed in MEC 

Bug ID	Description
CSCdm66131	Symptom: After addapsln trunk goes to LOS. Conditions: Both ends have secondary card active, add APS 1+1 to one end, then add APS to the other end, the trunk sometimes goes into LOS. Workaround: None.
CSCdm64366	Symptom: APS 1+1 manual switch sometimes does not work after a while after several manual switch and auto switch. Conditions: Secondary card is active and several manual switch and auto switches are performed. Workaround: None.
CSCdm62809	Symptom: APS 1+1 bidirectional non-revertive switches back to working line when line condition clears on working. Condition: APS 1+1 configured in bi-direction non-revertive mode. Working line is in LOS, current active line is protection, clear LOS on working line. Workaround: None.
CSCdm69974	Symptom: Card errors (0x25170076) occur when only one virtual trunk is configured in a physical port. Conditions: Once this card error occurs, illegal pointer access has been made. These errors might result in a card error, "databus error" or network traffic getting hurdled because of inconsistency in swsw/fw databases. Workaround: To avoid this situation, configure at least two virtual trunks on any physical port that you have VTs on. When preforming the configuration, configure the VTs one directly after the other.
CSCdm65813	Symptom: APS switches back to working line incorrectly. Conditions: Switch sequence W->P, P->W and then W->P, then cause LOS on WORK line and put the cable back, APS switches to Working line. Workaround: None.
CSCdm77212	Symptom: When addshelf command is executed, it comes back with a communication breakdown. Conditions: Channel level stats is set to 0 so that BXM reports wrong maximum channels. Workaround: For previous releases the statistics level for OC3 card should not be 0 level.
CSCdm74316	Symptom: Re-adding VSI shelf does not work until a resetcd is executed on the LSC control port. Conditions: Load information on an interface is 4 bytes more that MAX_VSI_MSG. The message gets dropped on BXM, so VSI controller is in discovery state forever. Workaround: None.
CSCdm75722	Symptom: No control VC after BXM is reset. Conditions: When resync request comes down from the VSI controller with 19 checksum blocks, the length check done on BXM does not include padding. Workaround: None.
CSCdm74968	Symptom: 0B card error causing BXM to reset. Conditions: Over night jobs are running on controller cards. Workaround: None.
CSCdp02190	Symptom: tstdelay timed out when going through BNI trunk. Conditions: More that 12 VTs on an interface causes wrong port-vi mapping while considering STI_SHIFT/NO_SHIFT from 13 th VT/port onwards. Workaround: None.
CSCdm78335	Symptom: dspvsistatus rarely shows the VSI programming status as Done. Conditions: Primary and secondary ports have two different VPI ranges. Workaround: None.
CSCdm26752	Symptom: Card errors continuously logged with "SoItcSend failed" message. Conditions: RAS oam_lpbk is on and switchyred is executed several times in a job. Workaround: None.
CSCdm93839	Symptom: Card resets on receiving OAM loopback cells at high rate. Conditions: oamlpbk is enabled with high OAM traffic on large number of connections. Workaround: None.
CSCdm52254	Symptom: BIP-8 code errs occurs on routing trunks. Conditions: T3 card used in HEC mode can randomly have this problem. Workaround: None.
CSCdm44183	Symptom: BXM-155 4DX was not able to recover after resetting the card. Conditions: Traffic is sent at a rate >= 383 cps on a terminated connection on BXM-E card and then card is reset. Workaround: None.
CSCdm90997	Symptom: BXM-E trunk and port stats are always zero in TX direction. Conditions: Port terminated on BXM-E card or trunk passing through BXM-E card. Workaround: None.
CSCdm80991	Symptom: Unable to add 3 segment connections using CM GUI. Conditions: Feeder is connected to BXM card of BPX routing node and for BXM trunk configuration, ILMI/LMI protocol is enabled as CARD based. Workaround: None.
CSCdm82688	Symptom: Traffic Shaping problems with VT with and without rap around solution. Conditions: Large deviations in CDV values. Workaround: None.
CSCdm94372 (See explanation below.)	Symptom: Trunks sometimes drop CBR traffic. Conditions: If a trunk is configured to full line rate on BXM cards, then traffic is dropped. Workaround: None.
CSCdp00063	Symptom: Node unreachability is experienced on VTs (virtual trunks). Conditions: Multiple VTs are configured on a trunk interface of the BXM/BXM-E. Workaround: Configure only one VT per trunk interface.

Logic to Calculate Actual Cell Transmission Rate in a BXM card (CSCdm94372)

if (configured cell rate == full line cell rate) then

transmitted cell rate = full line cell rate

else

transmitted cell rate = from equation below or from table 1

For example:

If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is then 98,013 CPS any traffic sent over 98,013 CPS would be discarded.

Only rates in the table or computed from the equation should be used. Otherwise, cell loss may be experienced.

1464865	56552	28832	19348	14559	11670	9738	8355
733860	54458	28278	19097	14416	11579	9674	8308
489558	52513	27744	18852	14277	11488	9611	8261
367288	50703	27231	18614	14139	11399	9549	8215
293888	49013	26736	18381	14005	11311	9487	8169
244938	47432	26258	18154	13872	11225	9426	8124
209966	45950	25798	17933	13743	11140	9366	8079
183733	44558	25353	17717	13616	11056	9307	8035
163327	43247	24923	17506	13491	10974	9248	7992
147001	42012	24508	17300	13368	10892	9190	7948
133642	40845	24106	17099	13248	10812	9133	7906
122509	39741	23717	16902	13129	10733	9077	7863
113088	38695	23341	16710	13013	10656	9021	7822
105012	37703	22976	16522	12899	10579	8966	7780
98013	36761	22623	16339	12787	10503	8912	7739
91889	35864	22280	16159	12677	10429	8858	7699
86485	35010	21947	15983	12568	10355	8805	7659
81681	34196	21625	15812	12462	10283	8753	7619
77383	33419	21311	15643	12357	10212	8701	7580
73515	32676	21007	15479	12254	10141	8650	7541
70014	31966	20711	15318	12153	10072	8599	7502
66833	31286	20423	15160	12053	10003	8549	7464
63927	30634	20143	15005	11955	9936	8500	7427
61264	30009	19871	14853	11859	9869	8451	7389
58814	29409	19606	14705	11764	9803	8403	7352

Anomalies Fixed in MEB

Table 43 lists the anomalies that are fixed in MEB.

Table 43 Anomalies Fixed in MEB 

Bug ID	Description
CSCdm50469	Symptom: Software error 105 and mallet card errors happened continuously. Conditions: When jobs that cause reroutes of connections (for example, switchcc, hitless rebuild) are run for a long time, sometimes BXM card freezes with mallet card errors and software error 105. Workaround: None.
CSCdm50723	Symptom: After deleting APS, switchyred causes temporary LOS when the other end still has APS. Conditions: One end has APS 1+1, other end was added with APS 1+1 and line is up between the two ends. Then APS is deleted from one end. The primary card is active on non APS end. On switchyred on the non APS end there is a temporary LOS. If APS was never added to one end, then switchyred does not result in temporary LOS. Workaround: Instead of deleting APS first and then doing a switchyred, do a switchyred first and then delete APS. This does not result in temporary LOS.
CSCdm63038	Symptom: BXM card fails with breakpoint error. Conditions: When tx cell rate of a trunk is reduced to zero, BXM card fails with break point error (division by zero). Workaround: None.

Anomalies Fixed in MEA

Table 44 lists the anomalies that are fixed in MEA.

Table 44 Anomalies Fixed in MEA 

Bug ID	Description
CSCdm09882	Symptom: Log non fatal message related to RCMP errors. Conditions: It is mainly seen in the heat chamber. Workaround: None.
CSCdm18186	Symptom: AIS status could be randomly be displayed in dspcon Conditions: When the connection AIS signal is constantly changing, the dspcon/dspchstats OAM status will not be accurate for all the connections on the card. Workaround: None.
CSCdm26380	Symptom: Software error 9098 occurred during switchyred BXM Conditions: This problem occurs on cards with the APS channels halved option set and then doing a cnfrsrc on a port that belongs to the second port group. Note that this fix will cause a card mismatch on active cards with channel halved option turned on. Workaround: None.
CSCdm31923	Symptom: AIS/YEL alarm does not go away even after the alarm is clear from the other end. Conditions: It happens on the E3 when the LOOP TIME parameter is set to YES in the trunk or line configuration. Workaround: None.
CSCdm37519	Symptom: Trunks go to Communication Fail after burning firmware. Conditions: MC10 is burnt into BXM-OC12 with trunks. Workaround: None.
CSCdm37709	Symptom: APS line fails to clear channel mismatch after lockout. Conditions: This symptom occurs with bi-direction APS 1+1. Local end has locked out of protection set. Then WORK cable is pulled out on local end to cause LOS. Lockout is then cleared and then the WORK cable is put back. This causes a channel mismatch on the far end and the mismatch never clears. Workaround: None.
CSCdm38647	Symptom: This bug has been fixed in MEA such that the firmware reports the correct number of port groups. The side effect of this fix is that the Switch Software could mismatch the BXM card. If there is a card mismatch then down all the lines/trunks on the card and up them again. Conditions: When the user loads the MEA firmware on the BXM card running MDA with APS halved channeled enabled, then the card will come up in mismatched state. Workaround: None.
CSCdm46658	Symptom: switchapsln command does not work for APS AnnexB line. Conditions: Annex B configuration if hitless rebuild is done when active line is PROT, then switchapsln does not work after hitless rebuild. Workaround: None.

Firmware Filenames and Sizes

Table 45 contains the firmware file information.

Table 45 Firmware Files 

Filename	Size
BXMMFZ.000	65536
BXMMFZ.001	65536
BXMMFZ.002	65536
BXMMFZ.003	65536
BXMMFZ.004	65536
BXMMFZ.005	65536
BXMMFZ.006	65536
BXMMFZ.007	65536
BXMMFZ.008	65536
BXMMFZ.009	65536
BXMMFZ.010	65536
BXMMFZ.011	65536
BXMMFZ.012	65536
BXMMFZ.013	65536
BXMMFZ.014	65536
BXMMFZ.015	65536
BXMMFZ.016	65536
BXMMFZ.017	65536
BXMMFZ.018	65536
BXMMFZ.019	65536
BXMMFZ.020	65536
BXMMFZ.021	65536
BXMMFZ.022	65536
BXMMFZ.023	65536
BXMMFZ.024	65536
BXMMFZ.025	48064
BXMMFZ.026	14
BXMMFZ.027	2
BXMMFZ.IMG	784
BXMMFZ.img	784

Appendix B—UXM Model C ACK Firmware Release Notes

This section contains information about UXM Model C firmware.

Introduction

ACK is a firmware maintenance release for UXM cards on the IGX. The firmware is the same for UXM and UXM-E cards.

New Feature

This section contains the new feature in ACK.

Cell Bus Parity Diagnostic—CSCdy86516

This feature allows SWSW to detect parity errors on lanes 2-4 of the backplane. Lane 1 errors are detected by the NPM.

A dummy connection is added between two UXM cards in the node and is used to send a test packet from one end of the connection to the other. By observing the parity errors count before the packet is sent and after the packet is received, you can determine whether there are parity errors on the backplane.

Obsolete Features

None.

Compatibility

1. Software

ACK firmware is compatible with Switch Software Release 9.3.10 or later.

2. Hardware

ACK firmware is compatible with all UXM and UXM-E model hardware.

Anomalies Fixed in ACK

Table 46 lists the anomalies that are fixed in firmware ACK.

Table 46 Anomalies Fixed in ACK 

Bug ID	Description
CSCdx76898	Symptom: Software error 9098 was logged after switchyred was issued multiple times. Conditions: This error shows that a VSI Y-red error occurred while switching over to the hot standby card. Workaround: Use dncd or resetcd on the active card for Y-red switchover.
CSCea29189	Symptom: SWERR: 9098 was logged when VSI partitions were configured using cnfrsrc after multiple Y-red switchover. Conditions: Software error 9098 keeps occurring while configuring VSI partitions using cnfrsrc command. Workaround: Use dncd or resetcd on the active card for Y-red switch over. Then, configure VSI partitions using cnfrsrc.
CSCed92177	Symptom: Traffic on the cell bus through the UXME trunk had doubled. The statistics on the connection of the UXME port were normal, but at the other end of the connection the traffic had doubled. Tracing the connection showed that the UXME was introducing the extra traffic. This problem was found as a result of the y-redundancy being configured on the cards when the line was put in local remote loopback state. If y-redundancy is removed, this problem does not occur. Conditions: This symptom only appears to affect T3 and OC3 cards. The T1/E1 cards did not exhibit double traffic. Workaround: Disable y-redundancy, and no further increased traffic issues exist.

Upgrade Instructions

To upgrade the firmware to ACK, complete the following steps:

---

Step 1 Upgrade the UXM boot code to boot revision 10.

Step 2 Upgrade the firmware to ACK.

Step 3 Reset the card.

---

Anomalies Fixed in ACH

Table 47 lists the anomalies that are fixed in ACH.

Table 47 Anomalies Fixed in ACH 

Bug ID	Description
CSCdu89369	Symptom: SWERR9000/C311 logged when disable VSI partition on IMA-T1 VT on IGX. Conditions: When a VSI partition is enabled/disabled on a T1-IMA Virtual trunk SwSw Error9000 is logged. Workaround: Not a service affecting bug.
CSCdv19468	Symptom: Loopback on Physical Interface not working on E3, T3 and OC3. Conditions: Loop back on Physical interface is not effective on ports and trunks as the traffic is seen leaked to other end CPE. This bug is found as part of Diagnostic Loopback feature implemented on UXM trunks which is enabled in 9.3.40 SWSW Release. Workaround: Issue resetcd.
CSCdv38499	Symptom: Traffic is being LEAKED to the remote end when loop back is present. Conditions: Local loopback on UXM ports will result in traffic leaked to cell bus. Local remote loopback on UXM ports will result in traffic leaked to cell bus from remote end. This bug is found and resolved as part of the Diagnostic Loopback feature implementation which is enabled in 9.3.40 SWSW Release. Workaround: Issue resetcd on UXM.
CSCdw14895	Symptom: Adding DS3 trunk from Y-RED side results addtrk failure with message in 'loop back ' detected. Conditions: This bug was introduced due to CSCdv38499 which has broken addtrk on Y-Red pair. Workaround: Issue addtrk from remote end if no Y-Red exists on remote end. Alternatively, physically pullout the Standby and perform addtrk.
CSCdt14885	Symptom: UXM card resets, we see swerr 103 and or cderrs 0B 29 00 A9 01 0D 17. Conditions: UXM card resets with either 103 SWSW error or 0B h/w error or both on an active UXM which has been Up for 320 days. This bug is due to Gateway Timer Counter overflow which is found to occur every 320 days since card is up. This bug exists in all previous versions of firmware under Model-C UXM as well as UXM-E hardware. Workaround: Reset UXM card in a maintenance window before 320 days of uptime.

Boot Code Requirements

Boot Code revision boot_10 is needed for the ACK release.

Unsupported Configurations or Applications

None.

Notes and Cautions

1. Switch Software Release 9.3.10 or later is compatible with the following versions of IOS and 7200 port adapter hardware:

IOS 12.1(3)T and later

PA-A1 (non enhanced) flavors of T3, E3, and OC3 ATM adapters

---

Note PA-A3 adapters are not supported for multi-VC mode as of 9/2000.

---

2. Changing the VPI range on a UXM interface partition is not causing the Xtagatm interface configuration on the controller to be updated.

This issue is recently discovered in 12.1(3)T.

When the slave ATM switch reports a VPI range change through an "IFC GET CNFG TRAP" the LSC does the following:

a. If the VPI range is reduced, the XTAG interface is toggled down and back up to force LDP/TDP to be reset. The LDP negotiates label ranges (VPI, VCI ranges) only when the session is established. The information displayed through a "show tag int detailed" command should be correct in this case.

---

Note The above does not apply to the BPX where the VPI or VCI range cannot be SHRUNK using the cnfrsrc command unless the interface is in the disabled state.

---

b. If the VPI range is increased, the information is updated in the VSI master but the information is NOT propagated to the XTAG. The LSC ignores the increased range instead of resetting the LDP session which forces VCs to be torn down. The VPI range from the "show tag int detailed" command can be interpreted as the LOCAL range that LDP/TDP used when setting up the session that is active. Changes at the ATM switch level are not reflected in the LSC unless the change explicitly causes the LDP session to be re-established.

3. Only one Xtag interface corresponding to a partition on a UXM interface that has multiple-partitions comes up. Other Xtag interface based on different partitions on the same UXM interface is not coming up.

Turn on "debug VSI errors."

The following errors display the messages: VPI/VCI in use or VCI in use. Overloading of the 0/32 tag-control PVC has occurred.

a. Example 1: Node tagigx4 dspctrlrs for tagigx4, shows two controllers, one each for partition 1 and partition 2.

node TN Cisco IGX 8430 9.3.10   Aug. 3 2000 11:05 PDT




VSI Controller Information




CtrlrId PartId ControlVC Intfc Type CtrlrIP

VPI VCIRange

1 1      0 40-70       3.3 MPLS 6.6.6.6

2 2      0 40-70       19.3 MPLS 66.66.66.66




b. Example 2: dsprsrc for 7.1, shows partitions 1, 2 and 3 on trunk 7.1

Trunk : 7.1

Maximum PVC LCNS: 256 Maximum PVC Bandwidth: 65000

(Statistical Reserve: 5000)

State                 MinLCN MaxLCN StartVPI EndVPI MinBW MaxBW

Partition 1: E 30 100 50 75 1000 10000

Partition 2: E 10 100 90 150 1000 10000

Partition 3: E 10 100 180 240 1000 5000




c. Xtagatm interface configuration for partitions 1 and 2 on Trunk 7.1

Make sure that only Xtag ATM interface uses the default tag-control-vc of 0/32. All other Xtag ATM interfaces on the same UXM interface should use non-default tag-control-vcs using the "tag-switching atm control-vc" command.

The following example shows xtagatm71 configuration on the LSC connected to 3.3 using default tag-control-vc of 0/32

Current configuration:

!

interface XTagATM71

ip unnumbered Loopback0

no ip mroute-cache

extended-port ATM2/0 vsi 0x00070100

tag-switching ip

end




The following example shows xtagatm71 configuration on an LSC connected to 19.3 using configured tag-control-vc of 90/32

Current configuration:

!

interface XTagATM71

ip unnumbered Loopback1

no ip directed-broadcast

no ip route-cache cef

extended-port ATM5/0 vsi 0x00070100

tag-switching atm control-vc 90 32

tag-switching ip

end




4. The URL for open and resolved caveats for IOS release image 12.1.(3)T can be found at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/121cavs/121tcavs.htm

5. An MPLS LSC on a T3 port cannot see the IGX.

When configuring a Cisco MPLS LSC on T3 interfaces, make sure the payload scrambling option on the UXM T3 line matches the config on the LSC. The default for the LSC is OFF, and the default for the UXM is ON since the lines come UP and CLEAR.

The following examples show T3 UXM configurations:

a. dsplncnf 12.6

node VT Cisco IGX 8430 9.3.1Z Aug. 3 2000 10:14 PDT




LN 12.6 Config T3/636 UXM slot:12

Loop clock: No

Line framing: PLCP Idle code: 7F hex

HCS Masking: Yes

Payload Scramble: No

VC Shaping: No

b. dspctrlrs

node VT Cisco IGX 8430 9.3.1Z Aug. 3 2000 10:14 PDT




VSI Controller Information




CtrlrId PartId ControlVC Intfc Type CtrlrIP

                    VPI VCIRange

1 1   0 40-70 12.6 MPLS 7.7.7.7

2 2   0 40-70 12.1 MPLS 99.99.99.99




Controller 1 on node tagigx3 is connected to 12.6. If the IP address in the CtrlrIP column is correct, you know that the LSC is being seen by the IGX and vice-versa. Otherwise a 0.0.0.0 displays.

6. The complete list of the FAQs (Frequently Asked Questions) that assist in troubleshooting VSI/MPLS problems on IGX can be found at the following URL:

http://wwwin-eng.cisco.com/Eng/WAN/IGX/WWW/VSI/igxvsifaq.htm

Firmware Filenames and File Sizes

Table 48 lists the firmware file information for the UXM Model C.

Table 48 UXM Filenames and Sizes 

Filename(s)	Size (bytes)
ACK.000 to ACK.024	65536
ACK.025	5346
ACK.img	784
AC09.000	56624
AC09.img	784

Appendix C—UXM Model B Firmware ABU Release

This section contains information about UXM Model B firmware.

Introduction

UXM ABU is Model-B firmware release for UXM card on IGX. Firmware is the same for UXM and UXM-E cards.

New Features

This section contains the new features in ABU.

RCMP Parity Policing

CSCdz03296 implementation of policing RCMP parity errors on UXM.

This feature allows the UXM card to continue to be in service under a low rate of parity errors while informing the user of parity event. The card resets if the error rate exceeds a threshold rate.

Obsolete Features

None.

Compatibility

1. Software:

ABU is compatible with Switch Software Releases 9.1, 9.2, and 9.3.

2. Hardware:

ABU is compatible with all models of URM and UXM-E hardware.

3. Previous versions of UXM firmware:

On IMA trunks this version is not compatible with UXMs Model B firmware versions ABA to ABD.

On IMA trunks Model B firmware (AB*) is not compatible with model A (AA*) because model B is Standards compliant and model A is not. Therefore, IMA trunks must be upgraded together.

Anomalies Fixed in ABU

Table 49 lists the anomalies that are fixed in firmware ABU.

Table 49 Anomalies Fixed in ABU 

Bug ID	Description
CSCdu66836	Switchyred fails an IMA trunk momentarily and then clears failure.
CSCdx41404	IMA protocol OK keeps on being recorded.
CSCdx44466	T3 trunks go into looped Back state at the same time.
CSCdy02463	Dropping cells on IMA port after upgrade to ABS firmware.
CSCdy20922	End-to-end OAM cell not received on the remote CPE.
CSCdy54168	UXM/UXM-E-T1 fails loop back test on line interfaces upon loss of cell alarm.

Upgrade Instructions

Update boot code to boot_09 before upgrading to ABU.

Boot Code Requirements

Boot code revision boot_09 is needed for the ABU release.

Unsupported Configuration or Applications

None.

Firmware Filenames and Sizes

Table 50 lists the ABU filenames and sizes.

Table 50 ABU Files 

Filenames	Size (bytes)
ABU.000-ABU.017	65536
ABU.018	60251
ABU.img	784

Notes and Cautions

None.

Appendix D—UXM Model B Firmware ABV Release

This section contains information about UXM Model B firmware.

Introduction

UXM ABV is Model-B firmware release for UXM cards on IGX. Firmware is the same for UXM and UXM-E cards.

New Features

This section contains the new features in ABV.

Cell Bus Parity Diagnostic

CSCdy86516 implementation of cell bus parity diagnostic.

This feature allows detection of parity errors on lanes 2-4 of the backplane.

Lane 1 errors are detected by the NPM. A dummy connection is added between two UXM cards in the node. This connection is used to send a test packet from one end to the other end.

Parity errors on the backplane can be determined by observing the parity error count before the packet is sent and after the packet is received.

Obsolete Features

None.

Compatibility

1. Software:

ABV is compatible with Switch Software Releases 9.1, 9.2, and 9.3.

2. Hardware:

ABV is compatible with all models of URM and UXM-E hardware.

3. Previous versions of UXM firmware:

On IMA trunks this version is not compatible with UXMs Model B firmware versions ABA to ABD.

On IMA trunks Model B firmware (AB*) is not compatible with model A (AA*) because Model B is Standards compliant and model A is not. Therefore, IMA trunks must be upgraded together.

Anomalies Fixed in ABV

Table 51 lists the anomalies that are fixed in firmware ABV.

Table 51 Anomalies Fixed in ABV 

Bug ID	Description
CSCdy29096	Cell drop on IMA 30 channel 7 E1 and 8 E1
CSCdy88772	Communication failure after upgrading UXM to A.B.T firmware
CSCdz48550	addloclp causes alarm or continuity problems on ATM connections
CSCeb08097	Deleting ATFXFST connection does not remove FCES from the configuration
CSCed92177	Double traffic on UXM-E trunk in Y-Redundancy
CSCin33540	addlnlocrmtlp does not work properly
CSCin34772	Loopback feature not working

Upgrade Instructions

Update boot code to boot_09 before upgrading to ABV.

Boot Code Requirements

Boot code revision boot_09 is needed for the ABV release.

Unsupported Configuration or Applications

None.

Firmware Filenames and Sizes

Table 52 lists the ABV filenames and sizes.

Table 52 ABV Files 

Filenames	Size (bytes)
ABV.000-ABV.017	65536
ABV.018	63765
ABV.img	784

Notes and Cautions

None.

Appendix E—URM Model B Firmware XBC Release Notes

This section contains information about the URM Model B firmware XBC.

Introduction

URM XBC is Model-B firmware release for URM card on IGX. The URM is an IOS-based routing module for the IGX. This release is an upgrade from XBB.

New Features

This section contains new features in XBC.

RCMP Parity Policing

CSCin32112—Implementation of Policing RCMP parity errors on URM.

This feature allows URM card to continue to be in service under low rate of parity errors while informing the user of parity event. The card will be reset if the error rate exceeds a threshold rate.

URM IOS CLI

This feature improves the management of the URM by allowing access to the IOS CLI running on the URM via the IGX CLI. This feature will also enhance Serviceability by further enabling remote recovery of the URM beyond the RRC feature introduced in 9.3.30 software.

This feature allows users to access the IOS CLI of the URM embedded router from the IGX CLI, so that users can access the router without having to be physically connected to the IOS Console port on the URM backcard

Obsolete Features

None.

Compatibility

1. Software

XBC firmware is compatible with Switch Software Release 9.3.47.

2. Hardware

XBC firmware is compatible with URM hardware.

Anomalies Fixed in XBC

Table 53 lists the anomalies that are fixed in firmware XBC.

Table 53 Anomalies Fixed in XBC 

Bug ID	Description
CSCdz48550	addloclp causes alarm or continuity problems on ATM connection.
CSCin15267	DUART hangs up when there is heavy interrupts (Rx and Tx) from both the channels simultaneously.
CSCin21211	For all rsh commands, Lines were truncated beyond 80 characters.
CSCin21212	"-MORE" is attached to the end of the "dsprtrlog" response even though there is no more data to view.
CSCin39677	After changing the Max and Min LCNs of VSI partition using cnfrsrc, SWerr:5050 was logged when "cba_verify" command was executed.

Upgrade Instructions

No special upgrade instructions in upgrading the URM Admin firmware from XBB to XBC.

Boot Code Requirements

Boot Code revision boot_2 is needed for the XBC release.

Unsupported Configurations or Applications

The 0/1023 is a special VC used by URM for IPC between Admin Processor and IOS. When configuring MPLS network, do not commit any cross-connect or control-vc on the port. Otherwise, SWERRS or non-working configurations might occur.

Firmware Filenames and Sizes

This section contain URM-B firmware file information.

XBC Firmware Boot Code

Table 54 lists the XBC filenames and sizes.

Table 54 XBC Files 

Filename(s)	Size (bytes)
XBC.000 to XBB.019	65536
XBC.020	33025
XBC.img	784

XAA Firmware Boot Code

Table 55 lists the XAA file names and sizes.

Table 55 XAA Files 

Filename(s)	Size (bytes)
XA2.000	57328
XA2.img	784

Notes and Cautions

1. The URM back card is hot-swappable; however the IOS processor is held in reset when back card is removed.

2. Card Mismatch might occur since XBA supports both BC-2FE2V and BC-2FE. Card mismatch is declared if BC-2FE2V and BC-2FE are swapped out of an ACTIVE URM card. Back cards of two different types can be swapped only in a STANDBY URM card.

3. If Remote Router Configuration feature is used to burn the IOS configuration in the card, the burned configuration cannot be deleted but can be overwritten only by another configuration.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/univercd/home/home.htm

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Documentation DVD

Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.

Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.

Cisco Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

Cisco Marketplace:

http://www.cisco.com/go/marketplace/

Ordering Documentation

You can find instructions for ordering documentation at this URL:

http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm

You can order Cisco documentation in these ways:

•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:

http://www.cisco.com/en/US/partner/ordering/

•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).

Documentation Feedback

You can send comments about technical documentation to bug-doc@cisco.com.

You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:

Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you can perform these tasks:

•Report security vulnerabilities in Cisco products.

•Obtain assistance with security incidents that involve Cisco products.

•Register to receive security information from Cisco.

A current list of security advisories and notices for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:

•Emergencies —  security-alert@cisco.com

•Nonemergencies —  psirt@cisco.com

---

Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:

http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on

---

In an emergency, you can also reach PSIRT by telephone:

•1 877 228-7302

•1 408 525-6532

Obtaining Technical Assistance

For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.

Cisco Technical Support Website

The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do

---

Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.

---

Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

•World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html

CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.

All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)

Copyright © 2005, Cisco Systems, Inc.
All rights reserved.