9.3.45 Version Software Release Notes Cisco WAN Switching System Software

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

About the 9.3.45 Release

The 9.3.45 software release supports the Cisco WAN switching products: Cisco BPX 8600 series and Cisco IGX 8400 series. This release does not support the IPX switch.

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

Phased Release Strategy

The rollout plan for the 9.3 release is based upon a series of incremental feature releases. This phased feature release strategy is designed to allow the earliest customer availability of key new features, consistent with maintaining high product quality. For the latest status of each 9.3 feature, see the following information.

Definitions

Minimum Release Versions

The minimum release version noted in the table represents the minimum switch software version required for each feature. It is recommended that customers use the most current maintenance releases.

Product	Feature Name	FCS/GA Status	Minimum Release
BPX	Virtual Trunk Bandwidth Oversubscription	FCS	9.3.40
BPX	Feeder VCI Restriction Removal	FCS	9.3.40
BPX/IGX	Display Connection Counts	FCS	9.3.40
BPX/IGX	VC Merge	FCS	9.3.40
IGX	NTM Subrate Trunk Encryptor Synchronization	FCS	9.3.40
IGX	UXM Trunk and Line Loopback	FCS	9.3.40
BPX/IGX	Single-Ended FCES and Policing	FCS	9.3.40
BPX/IGX	Line and Port Alarm Masking	FCS	9.3.40
BPX/IGX	Trunk VC Shaping	FCS	9.3.40
IGX	URM BC-2FE Back Card	GA	9.3.30
IGX	URM VSI Support	GA	9.3.30
IGX	URM Remote Router Configuration	GA	9.3.30
IGX	CRC-4 Error Detection	GA	9.3.30
BPX/IGX	AIS OAM Recognition	GA	9.3.30
BPX/IGX	800 Part Number Support	GA	9.3.30
BPX	Automatic Routing Management to PNNI Migration	GA	9.3.30
BPX	Network to Endpoint Connectivity Verification	GA	9.3.30
BPX	Deferred Connection Alarm Generation	GA	9.3.30
BPX	Enhanced NNI - End-to-end OAM across BPX-MGX Networks	GA	9.3.30
BPX	Provisioning of end-to-end AR - PNNI PVCs (XPVC) across BPX - MGX Networks	GA	9.3.30
BPX	LMI/ILMI on Virtual Ports	GA	9.3.30
BPX/IGX	TFTP Configuration Save and Restore	GA	9.3.30
BPX	F4 - F5 Mapping	GA	9.3.30
BPX/IGX	Virtual Trunk Clock Source Synchronization	GA	9.3.30
BPX	60K Channel support for VSI	GA	9.3.30
BPX/IGX	Trunk Incremental Cell Delay Variance (CDV)	GA	9.3.30
BPX/IGX	Concurrent Routing	GA	9.3.30
IGX	URM Router Functionality	GA	9.3.20
BPX	Dynamic Partitioning	GA	9.3.10
BPX/IGX	Qbin Statistics	GA	9.3.10
IGX	ILMI 4.0	GA	9.3.10
BPX/IGX	ILMI/ELMI Neighbor Discovery	GA	9.3.10
IGX	ELMI for UFMs	GA	9.3.10
IGX	VSI/MPLS	GA	9.3.10
BPX	Virtual Ports	GA	9.3.05
BPX	Hitless Connection Density Upgrade for BXM	GA	9.3.00
BPX	Support for 3 VSI Partitions	GA	9.3.00
BPX	VSI MIB Support	GA	9.3.00
BPX/IGX	800 Board-Level Revision Number	GA	9.3.00
BPX/IGX	Priority Bumping	GA	9.3.00
BPX/IGX	SCR and PCR Policing at Less Than 50 CPS on BXM/BXM-E and UXM/UXM-E	GA	9.3.00
BPX/IGX	Separate Abort Stack	GA	9.3.00
BPX/IGX	Upgrades Protection	GA	9.3.00
BPX/IGX	Control Traffic Shaping	GA	9.3.00
IGX	2000 VC Bandwidth Parameters	GA	9.3.00
IGX	UXM/UXM-E ATM Forum IMA-Compliant Ports	GA	9.3.00

For information about these features, refer to the corresponding release notes at the following URLs:

Software Release 9.3.45 Files

New Features in Release 9.3.40

Virtual Trunk Bandwidth Oversubscription

Virtual trunking defines multiple trunks within a single physical trunk interface. Virtual trunking allows the user to allocate as much bandwidth as needed instead of the full T3, E3, OC3, or OC12 bandwidths. Virtual trunking bandwidth refers to the service rate.

Prior to Release 9.3.40, the bandwidth of a virtual trunk (VT) is limited by its allocated portion of the total physical bandwidth at the interface. If a VT on a single interface is not utilizing its allocated share of bandwidth, other VTs cannot use this available bandwidth when their traffic exceeds the configured level. Each of the VTs on a physical interface has a fixed bandwidth which leads to inefficient use of the total bandwidth.

In Release 9.3.40 the purpose of oversubscribing is to allow a VT to utilize up to a maximum configured bandwidth on the physical interface. The sum of individual maximum bandwidths of the VTs on a single physical interface can exceed the actual physical bandwidth available on that interface. If a VT is not utilizing its share of bandwidth, another VT can use the bandwidth.

VT bandwidth oversubscription is applicable to AutoRoute (AR) and PNNI. This feature is available on the BPX switch with the BXM-E card. This feature is not supported on any other BPX card or on the IGX switch.

Functionality

The VTs on a physical interface can be configured with minimum and maximum service rates. The maximum service rate can be oversubscribed. If some connections on one VT burst traffic, they are allowed through on the oversubscribed VT up to the maximum service rate.

By default oversubscription on a VT is disabled, and the minimum and maximum service rates are set to the same value. Whenever the minimum and maximum values are changed by the user to be not equal, oversubscription is implicitly enabled.

By default the minimum and maximum service rates on a VT are set to 3000 cps or to the maximum bandwidth available on the physical interface, whichever is smaller.

VT oversubscription is disabled by making both the minimum and maximum service rates equal.

Configuration Requirements

The trunk on which this feature is to be enabled must be up. The remote end can be a BPX or IGX.

The sum of the maximum service rates of all VTs on a physical interface can be greater than the total bandwidth of that physical interface.

AutoRoute Connections

When routing connections over a VT, AutoRoute (AR) searches for the VT which has maximum available bandwidth and routes the connection over that VT. When a connection is routed over an oversubscribed VT, AR uses the minimum service rate to check for available bandwidth.

VSI Partitions

A VSI partition on a VT can be oversubscribed since the VSI partition shares the same virtual interface (VI) as that of the VT on which VSI partition is configured. The VI now has a minimum and a maximum service rate. Thus, connections on a VSI partition can burst up to the maximum VI rate with enough bandwidth on the interface. This maximum VI rate is configured through the cnftrk CLI command.

CLI Additions and Modifications

This section contains the commands that have been modified to support VT bandwidth oversubscription.

cnftrk

The cnftrk command has been modified to allow configuration of minimum and maximum service rates.

dsptrk

The dsptrk command shows the minimum and maximum service rate values. This display is the same as Example 1.

dspcmi

The dspcmi debug command shows whether the card supports VT oversubscription.

dspcd

dsptrkutl

The Overall utilization field in the display screen indicates the percent utilization of the trunk. If a trunk is oversubscribed, the percentage utilization might exceed 100% when the bandwidth usage exceeds the minimum configured value.

MIB Addition

This section contains the following addition to the atmTrunks table in the switch MIB to support VT bandwidth oversubscription.

Mismatch Capabilities

VT oversubscription is considered enabled if at least one VT on a active BXM is oversubscribed.

Redundancy

Feeder VCI Restriction Removal

STI cells used by Cisco WAN switches and ATM standard UNI/NNI cells have different header formats. ATM standard cells use a 16-bit VCI address field; whereas, STI cells use a 12-bit VCI field. In STI cells the higher 4 bits of octet 4, which contain the last 4 bits of VCI address in ATM standard cells, contain ForeSight information. Therefore, UNI/NNI cells support 65535 VCI addresses while STI cells can support only 4095 VCI addresses.

Since BNI cards use only STI cells, an ATM network with BNI and non-BNI modules must ensure that VCI address translation occurs whenever a cell moves from an ATM (non-BNI) segment to an STI (BNI) segment and vice-versa. Otherwise, the lower 4 bits of VCI information in the UNI/NNI cell are overwritten with ForeSight information when the cell enters the STI segment. This translation is achieved by shifting the lower twelve VCI bits of an ATM cell left or right when it enters or exits an STI segment.

This feature allows VCI shift to be turned on or off on BXM feeder trunks, enabling them to use the full 65535 VCI UNI/NNI address range. This feature also applies to MPLS which requires a VCI range greater than 4095.

Usage

To get the VCI unchanged in a VPC connection, shift must be disabled on all nodes in the path of the connection. The no-shift option must be selected at the master and slave nodes of the connection. Via nodes take on the same shift configuration as the master and must be no-shift if the master node configuration is no-shift.

Configuration

By default in Release 9.3.40 BXM feeder trunks have VCI shift disabled. The feeder trunks that exist prior to Release 9.3.40 have the VCI shift enabled by default.

To pass VCI without shift on a connection, the master and slave nodes should be configured as no-shift. The connection should not route over a BNI trunk.

For an existing connection, a change in the shift/no-shift setting is effective after the connection is rerouted. For example, if a node is upgraded from a version of SWSW that does not provide cnffdr support to one that does, any existing connections over BXM feeder trunks shift the VCI for cells passing over the connection.

Use the following guidelines for changing the shift/no-shift setting on a feeder trunk:

No configuration is required on via nodes since via nodes follow the configuration of the master node.

For a routing trunk, the cnfport command is used to turn shift on or off. For a feeder trunk, shift has to be configured using the cnffdr command or through SNMP.

When new feeder trunks are added on a node running SWSW software with this feature, the trunks come up with shift turned off.

To ensure that the VCI is not changed on a VPC connection, BNI trunks must not be in the path of the connection since BNI trunks use only 12-bit VCI (STI cells).

CLI Additions and Modifications

This section contains the commands that have been modified to support VCI restriction removal.

cnffdr

The cnffdr command is used to configure shift/no-shift on a BXM feeder trunk. The cnffdr command configures the shift/no-shift setting only under the following conditions:

If any of the above conditions are not true, the system displays an error message and prompts for another trunk number.

The following example shows the cnffdr display screen The Feeder trunk field displays the trunk number followed by the type of shelf.

dspfdrcnf

For BNI feeder trunks, the VCI field is copied to an STI cell. The shift/no-shift setting is not applicable. Therefore, for BNI feeders the dspfdrcnf command displays a [-] in the Shift field, shown in the following example.

MIB Addition

This section contains the addition to the atmTrk table in the switch MIB to support VCI restriction removal.

SNMP Error Messages

Redundancy

Controller Card Redundancy

Standby updates are applicable for the shift/no-shift parameter setting. The same configuration is available after executing a switchCC. If a switchCC (automatic) occurs when the configuration is changed but the connections are not rerouted, the configuration is available in the new active controller card. For the configuration to be to be effective, a manual reroute must be done after the switchCC.

Y-redundancy and APS

Display Connection Counts

In SWSW Release 9.3.40 the CLI command, dspconcnts, is modified to include the following connection counts:

CLI Addition

This section contains the command that has been added to support connection counts.

dspconcnts

The dspconcnts command shows the number of connection and connection endpoints.

VC Merge

The VC merge feature is already supported on BPX nodes. For more information on this feature, refer to the BPX Installation and Configuration documentation at the following URL:

On the IGX VC merge feature is supported only on UXM-E cards running firmware ACJ or higher.

This feature allows multiple incoming VCs to be merged in to a single outgoing VC. A UXM enhanced card with the VC merge capability can be configured to allow the merging of frame-based connections into a merged VC. The merged VC is controlled by the VSI controller.

The VC merge feature allows scalability of MPLS networks since one VC is allocated to each destination of each link.

The SWSW allows the configuration of VC merge for an enhanced UXM card through the cnfcdparm command. VC merge can be enabled only if the card supports this feature.

The VC merge feature is supported only for frame-based connections. These connections carry AAL5 frames consisting of multiple cells. The cells from a particular frame must be in an uninterrupted sequence when the frame goes out after merging.

After the node is upgraded to Release 9.3.40, VC merge can be enabled on the UXM-E cards by using the cnfcdparm command. The VC merge configuration parameters are saved in BRAM and are sent to the standby processor card.

Availability of Contiguous LCNs

The UXM card requires 550 contiguous logical channels (LCNs) in the AutoRoute (AR) partition to support this feature. The VC merge configuration request is denied if 550 LCNs are not available on the AR partition. The user is prompted to allocate LCNs on the card if the feature needs to be enabled.

The traffic on the VCs might get affected when this feature is enabled where 550 non-contiguous LCNs are available on the card. A trap is sent to indicate that the card needs to be deactivated and reactivated to enable the feature support. Since deactivation of the card disturbs the traffic, the user is prompted with a Y/N to proceed with the request. After the user enters Y to proceed, the SWSW configures the VC merge feature by sending appropriate commands upon card activation. The user is prompted before the interruption of any data traffic.

Redundancy

Graceful mismatch is supported. A mismatch condition is declared if the VC merge feature is in use, and Y-redundancy is attempted using a card that does not support the feature. In such cases, feature mismatch is declared (see Table 6).

CLI Additions and Modifications

cnfcdparm

The cnfcdparm command supports the VC merge configuration on UXM supported cards. A card must have at least one active partition to enable VC merge.

dspcd

NTM Subrate Trunk Encryptor Synchronization

This feature toggles the DTR lead on an NTM subrate interface backcard for a preconfigured ON and OFF cycle in the case of a disturbance to the trunk. This toggling continues until the trunk alarms clear.

Functions

When this feature is enabled, the NTM firmware detects a loss of synchronization by monitoring the following alarms:

The firmware then toggles the DTR lead periodically as specified by the ON and OFF times until all the above alarms are cleared. When the alarms are cleared, the firmware restores the state of the DTR lead.

CLI Modifications

This section contains the commands that have been modified to support NTM subrate trunk encryptor synchronization.

cnftrk

DTR toggling is enabled and disabled using the cnftrk command. A DTR toggle on alarm field is displayed for an NTM subrate trunk. Valid values are Y or N.

Fields for configuring ON and OFF duration are DTR secs ON and DTR secs OFF. Valid values for both fields are in the range of 1-128 seconds. Default for DTR secs ON is 29 seconds. Default for DTR secs OFF is 1 second. See the display screen in Example 12.

dsptrk

The dsptrk command is extended to display state of DTR toggling (enabled or disabled) and the ON/OFF durations.

cnftrkict

If the feature is enabled on a trunk, the cnftrkict command displays a warning message whenever DTR settings are changed. This warning indicates that the settings will be overridden by cnftrk settings in case of trunk disturbance.

MIB Additions

This section contains the three additions to the fpRteTrk table in the switch MIB for this feature.

SNMP supports enable/disable toggling and configures the ON/OFF toggling parameters.

SNMP OIDs are partitioned into two sets, legal_fprtetrkcnfg_tbl and legal_fptrkparm_tbl. Each table has a separate access function, corresponding to cnftrk and cnftrkparm CLIs. These OIDs are contained in the fpRoutingTrunks table.

UXM Trunk and Line Loopback

This feature provides the loopback commands on a UXM physical interface that is configured for physical, virtual, or feeder trunk(s) in trunk mode and configured for an UNI or NNI ATM port in line mode.

When a physical loopback is added on a UXM physical interface, all the traffic on the physical interface is looped back.

The physical loopback configuration is stored in BRAM and updated to the standby NPM. The configuration is retained after a rebuild, switchcc, or software upgrade. SWSW does not broadcast the physical loopback information on a UXM physical interface to the other BPX/IGX nodes in the network.

Local Loopback (addlnloclp)

When a UXM port interface is put in local loopback state, the traffic that comes into the cell bus from the local cable is looped back on the cell bus and sent back out the cable. This traffic is passed into the network.

The traffic that comes from the remote end through the network is not sent to this interface. This traffic is dropped and is not mixed with the traffic being looped back.

For local loopback on normal trunks the node which has the trunk-end in local loopback state goes into Comm-Fail state while the remote node goes into loopback state. The traffic from the remote node is looped back by the local node.

The symbol "]" always indicates local loopback for both lines and trunks. The loopback behavior on IMA lines/trunks, IMA virtual trunks, and feeder trunks is similar to that of normal lines/trunks. The user can reduce the number of retained links (to ensure that IMA group status is OK using cnfln or cnftrk commands) and safely put a local loopback on one or more of the individual physical IMA links. The test traffic entering the looped IMA links is looped back while the main user traffic remains unaffected (as long as a sufficient number of retained links remain).

Local Remote loopback (addlnlocrmtlp)

For local remote loopback on normal lines, the node that has its line interface in the local remote loopback state loops back the traffic coming from the cell bus. The traffic is looped back and is not passed to the cable. Traffic from the ports on the local node is not sent on to the network. Traffic is dropped at the local node and is not mixed with the traffic being looped back.

For local remote loopback on normal trunks, the node that has its trunk-end in local remote loopback state loops back the traffic coming from the cell bus. The remote node does not receive this traffic.

The traffic being received from the remote node is dropped and is not passed on to the CPE attached to the local node. This traffic is not mixed with the traffic being looped back.

The symbol "[" always indicates local remote loopback for both lines and trunks. The loopback behavior on IMA lines/trunks, IMA virtual trunks, and feeder trunks is similar to that of normal lines/trunks. Local remote loopback on individual IMA links is not supported.

Delete Local/Local Remote loopback (dellnlp)

The dellnlp command deletes either local or local remote loopback on a line or trunk interface.

The displaying (output) screens of the following existing IGX user commands include the loopback indicators on all the trunks or lines on the UXM physical interface:

Table 8 lists the expected behavior upon using the loopback commands on a single (isolated) node and other nodes in a network. The behavior at both the local and remote nodes is shown. All loopback commands are executed on local nodes.

Limitations

The physical loopback commands on IGX can be executed on the UXM physical interface only, not on an individual virtual interface.

Local remote loopback on individual IMA physical links (either lines/trunks) are not supported. Either all or none of the individual IMA physical links might be put into loopback. This loopback behavior is a firmware limitation. However, for local loopbacks either one or more (including all) of the individual IMA physical links can be put into local loopback.

Traffic loopback behavior on feeder trunks is the same as on normal physical trunks. However, the display is different, as shown in Table 8. Feeder trunks do not have an alarm state called Looped Back. For loopbacks on feeder trunks, both local and remote ends are in major alarm and go into communication-failure state. The states are different because feeder trunks use LMI/ILMI protocol for communication failure tests while normal physical trunks use AutoRoute protocol.

CLI Additions and Modifications

addlnloclp

addlnloclp <slot.port> or <slot.port[-port, port]> or <slot.port.vport> or <slot.port-port.vport>

addlnlocrmtlp

addlnlocrmtlp <slot.port> or <slot.port[-port, port]> or <slot.port[.vport]> or <slot.port-port.vport>

dellnlp

dellnlp <slot.port> or <slot.port[-port, port]> or <slot.port.vport> or <slot.port-port.vport>

dsptrks

If a UXM physical interface is put in loopback state (either local or remote local), the dsptrks command displays a loopback indicator associated with each of the logical trunks (physical or virtual) that are configured on that UXM physical interface.

dsplns

The dsplns command displays a loopback indicator for the logical line. This command includes the following modifications:

dspphyslns

The changes in dspphyslns are identical to those of the dsplns and dsptrks commands except that the loopback indicator is shown against each individual IMA physical line as appropriate.

Redundancy

If Y-redundancy is configured on a UXM card that supports hot-standby the line loopback configuration on its physical interface, if SET, is also programmed to the standby UXM.

Single-Ended FCES and Policing

Single-ended FCES mechanism is used to provide an end-to-end flow control capability to ABR and FST types of connections consisting of multiple segments. This feature allows the BXM-E and UXM-E to provide congestion information to non-Cisco products using a standard interface. ABR flow control is extended to the external segment.

Policing is the process of monitoring ingress traffic of a connection to determine if the traffic can enter and how that traffic is handled once inside the network.

These features allow single-ended FCES and policing on a connection to be configured on an endpoint basis rather than on a connection basis. The congestion control loop is enabled between only those devices that support this feature.

Similarly, policing is independently configured at each endpoint of the connection. This feature allows maximum traffic throughput to avoid cell discards due to traffic clumping on the NNI interfaces.

Functions

Requirements

FCES

Independent values for FCES provisioning can be configured for the following reasons:

MIB

To integrate with CWM, the switch MIB atmEndptOeBCM object for FCES is read-write.

Policing

When a connection is added using addcon, configured using cnfcon, or displayed using dspcon CLI commands, the parameter for policing takes one of the following value combinations:

For UBR connections, CLP tagging is used and corresponds to the following input values:

The policing type has a range from 1 to 5. Table 9 shows how these policing types are defined. The value to the left of [/] is the local endpoint policing type and the value to the right of [/] is the remote endpoint policing type. The two endpoints are provisioned independently using these two input values.

To configure policing based on endpoints rather than connections, use the addcon and cnfcon CLI commands.

Compatibility

MIB

A new MIB object atmEndptOePolicing supports policing type on the other end.

Redundancy

One-to-one redundancy is preserved since the values for FCES and policing endpoint provisioning are stored in BRAM and are sent to the standby card.

Network Interoperability

When connections are added from a node with this feature to another node without this feature, the endpoint-based provisioning can be achieved. On the node the display without this feature, the dspcon command displays only one local endpoint value.

The dcct, dvc, and dvcparms commands display the values on both endpoints.

When an ATM class is configured from a node with this feature to have two different values for FCES or policing, the CWM Connection Manager (CM) updates this ATM class definition on all the nodes in the network including nodes without this feature. If a connection is added from an old revision node using this updated class, the connection uses the two different values to provision the connection.

With an upgraded CWM and mixed revisions on a switch, single-ended FCES is supported if the master node is an upgraded node.

Line and Port Alarm Masking

Alarms on a line or port can be masked so that they are not propagated to the network. This masking allows the known alarms in the network to be hidden from the new alarms.

Line and port alarms can be masked through CLI and SNMP interfaces. Activation and deactivation of the interface alarms are logged in the local event log.

Functions

Line and port alarm masking mirrors the existing trunk alarm masking and provides the following functions:

Line Alarms

The line alarms on a node are caused by physical line failures which result in failure of all of the connections on the line interface.

Port Alarms

The port alarms in a node can be caused by a failure on the end device (CPE) connected to it. These alarms can be caused by an LMI/ILMI failure to restrict communication between the interface card and the CPE. This failure results in a port communication failure that causes a minor alarm on the node.

In addition to port communication failures, the serial port interface card, UFMU, can have port configuration, port over speed, and cable mismatch failures. These failures result in minor alarms on port interfaces.

An IGX Frame Relay NNI port can go in to major alarm only when an NNI failure occurs, and the debug flag is enabled.

MIB Additions

This section describes the objects added as a part of the alarm masking feature.

CLI Additions and Modifications

This section contains the commands that have been modified to support line and port alarm masking.

cnfintalm

The cnfintalm command configures the thresholds for the integrated line/trunk alarm parameters. This command is the renamed version of the existing cnflnalm command.

cnflnalm

The cnflnalm command enables or disables a line alarm. Upon successful completion of this command, the dsplns screen is displayed with the configured line number in highlighted display.

cnfportalm

dspalms

dspintalmcnf

The dspintalmcnf command configures the thresholds for the integrated line/trunk alarm parameters.

This command is the renamed version of the existing CLI command dsplnalmcnf to avoid the conflict between the line alarm masking and integrated alarm parameter configuration of lines.

Trunk VC Shaping

This feature provides the capability to enable VC shaping on UXM and BXM trunks, virtual trunks, and feeder trunks per Qbin or QoS.

Compatibility

On the BPX, the BXM card must support the trunk VC shaping feature for VC shaping to be enabled on the trunks.

On the IGX, the UXM card must support traffic shaping for VC shaping to be enabled on the trunks.

This feature is compatible only with firmware releases supporting traffic shaping. Additionally, PCR shaping can be disabled per QBin only if the firmware release supports trunk VC shaping. Otherwise, PCR shaping cannot be disabled.

Limitations

The capability to enable and disable VC shaping is available only on AutoRoute Qbins (1-9). VC shaping cannot be enabled on the high priority Qbin (2) since this Qbin services the CC traffic. VC shaping cannot be enabled on other Qbins (Qbin 0, VSI Qbins 10-15).

The maximum rate at which a VC can transmit is limited by its PCR value if PCR shaping is enabled.

Enabling VC Shaping (or disabling from previous enable state) on a trunk applies only to new connections routed over the trunk. VC shaping can be applied to all the connections belonging to a Qbin by performing a reroute.

Functionality

The VC shaping capability can be turned on per QoS on the BXM card by configuring the appropriate Qbin to enable the function. When VC shaping is enabled on a Qbin, egress cells are placed on their respective VC queues before they are scheduled into the Qbin. Cells are scheduled from different VC queues into the Qbin using WFQ to ensure fairness among the different VCs.

On the UXM card, VC shaping can be turned on per trunk. The configuration is then applied to relevant Qbins.

Traffic from a VC queue into the Qbin is limited to the PCR. When VC shaping is enabled, both PCR-shaping and WFQ are in effect. However, PCR-shaping can be removed by programming the PCR of the connection to a large value, leaving only WFQ in effect.

The user can enable VC shaping for a particular Class of Service (CoS) on a trunk or virtual trunk using the cnftrkqparm command, cnftrk command on the IGX, or SNMP.

On the BXM, depending on the CoS, the user is provided with the following options:

CLI Modifications and Additions

This section contains the CLI modifications to support the trunk VC shaping feature.

cnftrk

The cnftrk command on the IGX was used to enable VC shaping on a per trunk basis before this feature. Since the feature moves the capability to a per-QoS basis, the VC shaping parameter in the cnftrk command is removed.

cnftrkq

The cnftrkq command enables and disables VC shaping for trunks, virtual trunks, and feeders on a per-Qbin basis.

VC shaping can be enabled only on the AutoRoute Qbins using this command. Enabling VC shaping on VSI Qbins is not supported. The default values for all the Qbins is disabled.

VC shaping can be enabled on a QBin only if that card supports VC shaping. If a card does not support VC shaping the following error message displays: VC shaping not supported on the card.

dsptrkq

The dsptrkq command displays the VC shaping parameters per Qbin for trunks, virtual trunks, and feeder trunks.

dspcmi

The dspcmi command display includes the new card attribute, Trunk VC Shaping. This field is valid only on the BPX.

dspcd

The dspcd command display includes trunk VC shaping on the BPX (shown in Example 22).

Redundancy

This feature does not have impact on redundancy. No mismatch is declared if one of the cards in a Y-red pair supports this feature and the other does not. However, the feature is activated only if both cards in Y-red support the feature.

MIB Additions

The atmTrunks MIB table currently contains the atmTrkVcShaping object to enable VC shaping per trunk. This object is not used for the BPX and nine new objects are added to enable VC shaping per Qbin. The existing object, atmTrkVcShaping, is still used on the IGX.

Special Installation/Upgrade Requirements

General Upgrade Procedure

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

Procedure for Upgrading BXM cards to the 9.3 Firmware Release

See the Compatibility Matrix for the tested/supported versions of other firmware and software that work with this release.

Procedure for Upgrading UXM cards to the 9.3 Firmware Release

If the switch software version on the node is Release 9.2.x, the following steps are required to upgrade the UXM firmware to revision ACC or later:

Step 4 After the card comes up, upgrade the run-time firmware to revision ACC or later.

If a Switch Software Release 9.3.x has already been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACC:

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

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

Revision Interoperability Supported

The Revision Interoperability feature allows a mixed/ heterogeneous network of 9.2.x and 9.3.x (where "x" equals any GA version of 9.2 and 9.3) nodes to coexist and interoperate. This capability allows users to upgrade their networks from 9.2 to 9.3 in multiple steps.

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

In a mixed-revision network, functions that are implemented in 9.3 but not in 9.2 are disabled. For example, features that are supported in both Releases 9.2 and 9.3 function at their 9.2 level. New features developed in 9.3 are automatically enabled when all nodes are upgraded to the 9.3 revision level.

Specifically, connection provisioning, connection rerouting, alarming, and CWM support for these features are supported but function at their 9.2 capabilities, and not at their 9.3 levels until all nodes are upgraded. The dspblkdfuncs command displays blocked (disabled) features.

For 9.3.30 and above, the following features are blocked in a mixed network. These features require that all nodes of the network are running 9.3.30.

Version Compatibility Notes

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

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

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

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

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

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

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.

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.

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

Obsoleted Hardware and Firmware

Notes and Cautions

The peak intervals are controlled to be only those values for which peaks can be accurately collected The following rules apply to peak intervals:

Limitations for Release 9.3.40

Compatibility Matrix

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

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

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

BPX 8600 Firmware Compatibility

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	MFW	MFT
BXM-E3-8/12	BXM-E3	BXM	F	MFW	MFT
BXM-155-4/8	BXM-155	BXM	F	MFW	MFT
BXM-622/622-2	BXM-622	BXM	F	MFW	MFT
BXM-T3-8E/12E/12EX	BXM-T3	BXM	F	MFW	MFT
BXM-E3-8E/12E/12EX	BXM-E3	BXM	F	MFW	MFT
BXM-155-4D/8D/4DX/8DX	BXM-155	BXM	F	MFW	MFT
BXM-622-2D/DX/2DX	BXM-622	BXM	F	MFW	MFT
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

If the switch software version on the node is Release 9.2.x, the following steps are required to upgrade the UXM firmware to revision ACC or later:

Step 5 After the card comes up, upgrade the run-time firmware to revision ACC or later.

If a Switch Software Release 9.3.x has been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACC:

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	XBB	XBB
IGX-UVM	UVM	UVM	D	DDF	DDF
IGX-UVM¹	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

BPX 8600 Hardware Compatibility

Card Type	Part Numbers	Latest H/W	Min. H/W
Controller Cards
BPX-BCC-64M (Non-Orderable)	800-04008-04	A	A
BPX-BCC-BC (Non-Orderable)	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

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

Known Anomalies for Release 9.3.45

Bug ID	Description
CSCdk91790	Symptom: SWSW system idle time is below 30% when more than 10 UVMs are activated. Conditions: SWSW polls each activated UVM for modem status every 1 second for each port. SWSW also spends time in processing the responses of the modem polling. When many UVMs are activated, the modem polling handling consumes a lot of system time and resources (buffer queue) which affect system performance. UVM FW has supported asynchronous event to report modem event. SWSW needs to stop polling modem status if the FW in UVM supports the async event. Workaround: Use cnfnodeparm 46 to increase polling timer to improve system performance.
CSCdp48861	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
CSCds47671	Symptom: dspcurclk displays incorrect trunk numbers in the clock path. Conditions: Need the following clock path in dspcurclk for this problem to surface: destination IGX slot ------ slot via node slot.port ----- source node Workaround: None. Further Details: The display attempts to display the port on the via trunk before it is properly set.
CSCdu13921	Symptom: Connection routing fails with the message "No route available (insufficient trunk bandwidth)" -- as seen with the [dspcon] command, but when checking the trunk bandwidth usage via [dspload], there is enough bandwidth. Conditions: This problem occurs when we run out of connection identifiers, conids. The most common occurrence of this is on BXM cards as they have a configurable conid limits and the defaults are rather small, 256. Workaround: Check the [dspload] command and if the "Con ID Avail" count is 0, then the routing failure is really do to connection Id exhaustion rather than bandwidth.
CSCdu38434	Symptom: NWBrowser shows Back card revision for the absent backcards as EW by default. Conditions: Base line issue. This bug is applicable to all the switch software revisions. Workaround: Ignore the back card information in the dspcd screen and the one from NW browser if dspcds shows that back card is empty.
CSCdv36764	Symptom: swerr 1008 is logged when a BXM card is continuously reset every five minutes. Conditions: One of the BXM cards is continuously reset every five minutes due to an issue with the Stats Collection task of the BXM firmware running every five minutes on the card. Workaround: Unknown.
CSCdv73494	Symptom: swerr 886,2071,2059 fills the log. Conditions: The log display shows the swerr. Workaround: Unknown at present.
CSCdv79961	Symptom: Unable to configure stats level on standby card after upgrading SWSW on IGX from 9.2 to 9.3 with UXM in Yred. Conditions: After upgrading from 9.2.34 to 9.3.11 UXM pair in Yred try to cnfcdparm for stat level change you receive this error message "Cannot change stats level for yred card or card in service". However, if you try the same thing when the card is not in yred, the node allows you to change. Workaround: 1. Remove the standby card and place in some other empty slot. 2. Configure the stat level in the new, non-yred slot. 3. Replace the card into the y-red standby slot. 4. Wait until the card comes up fully as a standby, and has completed its programming. 5. Switch to the standby card that has the modified stat level. 6. Remove the new standby card and place in some other empty slot. 7. Repeat steps 2-3 on the next card.
CSCdw01813	Symptom: In the network, there are 44 real nodes + enumlated nodes. Totally 220 nodes. After power down 43 and up (except one real node), nodes in a 220 nodes network, logged software error 419. Conditions: A node has been removed by deleting the trunk. Power down and power up all nodes in the network. Workaround: None.
CSCdw01866	Symptom: After hitless rebuild in a large network, dspload does not show used recv load info for a long time. chklm could not be trust until all load updates sync up. Conditions: Hitless rebuild. Workaround: None.
CSCdw02563	Symptom: The Software Error log was filled with 9000s on a UFM card in an IGX node. Conditions: This was found while executing runrev command after a graceful upgrade from 9.3.30 to 9.3.4G. This anomaly not happen after every runrev, only on revision changes in which the global address of novram_data changes. Moreover, this condition only occurs when the back card is missing. Workaround: This anomaly has no customer impact, other than filling the software error log with 9000's. These errors can be cleared and ignored since they are logged against a UFM front card that does not have its back card.
CSCdw03498	Symptom: Backcards are "empty" in slot 3, 4, and/or 8 on node. Conditions: resetsys on node. Workaround: "resetcd h" on the affected cards.
CSCdw04847	Symptom: The default value and the range allowed for queue size is wrong. Conditions: This can be seen while using cnftrkparm to configure the queue sizes. Workaround: A valid range is approximately half of that allowed in cnftrkparm. Configure the queue sizes to be within the valid range.
CSCdw04934	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	Symptom: Date and time changed during upgrade Conditions: 9.3.3b and 9.3.3d, MF01 Workaround: None
CSCdw18589	Symptom: A virtual trunk configured as a clock source can be configured to Pass sync. Conditions: Enabling PASS SYNC to YES on any virtual trunk sharing the same physical interface as the virtual trunk configured as a clock source will cause PASS SYNC to be set to YES on all virtual trunks associated with that physical interface including the virtual trunk configured as the clock source. Workaround: If the physical interface for a virtual trunk is used as a clock source, do not set PASS SYNC to YES on any of the virtual trunks associated with the interface. Further Problem Description: In 9.2, when the physical interface for a virtual trunk is used as a network clock source, the source associates itself with the first virtual trunk on the interface. Should that trunk fail, the clock source fails and the system will search for a new source. In this configuration, you are not allowed to set PASS SYNC to YES on the first virtual trunk (which is correct), but it is possible to set the Virtual Trunk for PASS SYNC YES. By setting PASS SYNC to yes on any other virtual trunk on the interface causes PASS SYNC to be set to YES on all of the Virtual Trunks - even the first one which is associated with the clock source. Having a trunk as a clock source and set to PASS SYNC YES is an unsupported configuration. In 9.3, the situation is slightly different in that a change made to any of the virtual trunks does not affect the first virtual trunk, which has the clock association. The problem here is that if the first virtual trunk fails, the clock source associates itself with the second virtual trunk. If PASS SYNC were set to YES on that trunk, problems would result.
CSCdw30811	Symptom: Port and alarm messages for FTM ports are not formatted correctly, consequently the CWM cannot track or manage these entities. Because this message is misformated, the CWM does not know where it starts or ends, and consequently other messages from the switch can be discarded. This could then result in incomplete database tables so the CWM cannot collect statistics, manage the ports or establish new connections. This could also result in discarded alarm messages on the CWM so it may not set or clear alarm messages appropriately. Conditions: This problem will only occur when FTM/FTC cards are on the IGX. Workaround: Remove all configuration related to the FTM/FTC cards and remove them from the switch all together. FTM/FTC cards are not supported in 93 software, the last version of software that supported these cards was 92. After removing FTM/FTC configuration and hardware, resync the CWM workstation by doing one of the following: 1. Do a controller card switch over on the IGX switch. This requires a redundant NPM switch. This will break the link to the CWM, and when the CWM reattaches it will resync with this one node. 2. Do a hitless rebuild on the IGX switch. This will break the link to the CWM, and when the CWM reattaches it will resync with this one node. 3. Do a full rebuild on the IGX switch. This will cause an outage on the node and is customer impacting. This will break the link to the CWM, and when the CWM reattaches it will resync with this one node. 4. On the CWM, stop and then restart the CWM core. This causes the CWM to resync with all nodes in the network.
CSCdw40470	Symptom: When there are multiple users issuing the "tstpingip" command, the results of the successful "tstpingip" are mixed in with the results of the other users' "tstpingip". Conditions: Multiple users issuing the "tstpingip" command at about the same time and there is a mix of successful and unsuccessful results. Workaround: Repeat the command after the other users have finished with their "tstpingip".
CSCdw42981	Symptom: The setting for off3 Multi-DB Stby Updates changes from disabled back to enabled after a full rebuild. Trace Msg Sent 1 Disabled Multi-DB Stby Updates 2 Enabled Trace Conv Msg 3 Disabled Conditions: This only occurs if the user has modified the setting of Multi-DB Stby Updates from its default value of enabled to disabled, and then a full rebuild occurs. For example if the value of "Multi-DB Stby Updates" was set to Disabled then after rebuild it will be set to 'Enabled'. Workaround: After the full rebuild, reset the value back to disabled if that is desired.
CSCdw44810	Symptom: Event log indicates "loadrev (new-revision) initiated from node (remote node)" when the remote node really did a runrev. Conditions: This will occur whenever a node invokes a runrev for another node by doing: 1. runrev (newrev) *, or 2. runrev (newrev) (remote node). Workaround: None.
CSCdw47805	Symptom: The NTM subrate trunk transmission timestamp queue depth is different at the two ends. Conditions: 1. With one side of the trunk is up only (the other end down), upgrade from pre-9331 images the node to post-9331 images on both side. Up the other side of the trunk. Workaround: 1. down the upped trunk after upgrade 2. or use cnftrkparm to change the transmission timestamp queue to be the same size as the other end after upgrade.
CSCdw60790	Symptom: Addcon fails to add abrfst connection with PCR < 50 on OC12 card. Conditions: Add abrfst connection with PCR < 50. * The port card is bxm OC12. Workaround: When adding the connection, disable 'Default Ext Parms [Enable]:'. * Add the connection to a rate >= 50. Use cnfcon to change it to a lower value.
CSCdw64896	Symptom: When a node has a lot of unroutable derouted connections in a node that has more than 12K connections, the CPU usage is very high (close to 90%). When the routing state machine is turned off, the CPU load does not go down for a long time. Conditions: A node with a lot of unroutable failed connections which have several hops between the master and slave. Workaround: Down the unroutable connections to bring down CPU load.
CSCdw68880	Symptom: The interval statistics listed below always return a value of zero: 59 Good Pdu's Received by the Sar 60 Good Pdu's Transmitted by the Sar 61 Rx pdu's discarded by the Sar 62 Tx pdu's discarded by the Sar 63 Ivld crc32 pdu 64 Invalid Length pdu rx by the sar 65 Shrt-Lgth Fail detected by the sar 66 Lng-Lgth Fail detected by the sar Conditions: Always occurs Workaround: None
CSCdw86892	Symptom: When a switchyred fails the event log may occasionally log an event of: switchyred error:BXM <prislot>/<secslot> ? where instead of displaying the error code, or the textual reason, it instead shows ?. Conditions: This occurs rarely, when the switchyred command encounters an error that the event log does not know how to map to text. The customer is given an appropriate message at the user interface, but it is not presented in the event log. Customer Impact: This can make debugging of switchyred issues more difficult, because if the failure happens to be one of these more rare cases the event log will only indicate "?". However, since the CLI shows the failure type at the time of the switchyred, the customer can report the warning given at that time. Workaround: None
CSCdw89836	Symptom: The 'tstber a' command does not work correctly between ASI and BXM cards when BXM cards have virtual ports before physical ports in the interface order (e.g. 3.2.1 is before 3.3). Conditions: The virtual port on the BXM card should come first in the sequence of ports. Workaround: On the BXM cards, up physical ports with lower interface orders than the virtual ports (for example, 3.1 is lower than 3.2.1). Or, change the virtual port shift option to SHIFT_ON_HCF. Status: Resolved
CSCdw93967	Symptom: An event appears in the event log indicating that a switchyred started even though the command switchyred was not invoked. This can be confusing because sometimes you might see to switchyred start such as: Info switchyred End:Empty 9/0 03/07/02 14:34:45 Info switchyred error:Empty 9 empty slot 03/07/02 14:34:45 Info switchyred Start:Empty 9 03/07/02 14:34:45 Info switchyred Start:Empty 9 03/07/02 14:34:27 Conditions: This only occurs when a job is created that includes the command switchyred. When the job is being created an event is logged, even though the command is not actually starting. Workaround: The user needs to recognize that we could have some extra switchyred start events, the "real" start event is the one that immediately proceeds the end event. Further Problem Description: Other than the issue, logging events while adding the job, there are other problems in event logging associated with switchyred. See the logs for the switchyred in the following cases, 1. Command:'switchyred 16' dsplog: Info switchyred End:Card 16/0 06/05/02 11:23:46 Info switchyred Start:Card 16 06/05/02 11:23:39 2. Command:'switchyred 7' dsplog: Info switchyred End:BCC 7/0 06/05/02 11:25:54 Info switchyred error:BCC 7 y-red not supported 06/05/02 11:25:51 Info switchyred Start:BCC-4 7 06/05/02 11:25:51 3. Command:'switchyred [Empty slot]' dsplog: Info switchyred End:Empty 2/0 06/05/02 11:26:25 Info switchyred error:BXM 2 empty slot 06/05/02 11:26:24 Info switchyred Start:Empty 2 06/05/02 11:26:24 4. 4. Command:'switchyred [BXM slot not in y-red]' dsplog: Info switchyred End:BXM 1/0 06/05/02 11:26:16 Info switchyred error:BXM 1 not cnfgd for redundancy 06/05/02 11:26:14 Info switchyred Start:BXM 1 06/05/02 11:26:14
CSCdw93967 (continued)	In all the cases above it does not make sense to log "switchyred Start...." or "switchyred End:..." message in the log. The event is getting logged when the syntax checking or the validity checking phase itself. Log the event after the syntax/validity checking is done.
CSCdx23232	Symptom: con_verify on BPX for connections resulted in swerror 1417 Conditions: One end of the connection should be on a node running 9.2.36 and the other end on a node running an upgraded firmware. Workaround: None
CSCdx30787	Symptom: IGX, MGX, and BPX mibs cannot be found at: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml and the OID translator at: http://www.cisco.com/cgi-bin/Support/Mibbrowser/unity.pl Conditions: Customers can never find the mibs in the above expected location. Moreover, the oid translator never works for the Stratacom mibs. Workaround: Call the TAC to find out where the mibs are.
CSCdx33468	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.
CSCdx34855	Symptom: Upon login, or invocation of the [dsptech] command, the display for the VC field is bold and has an asterisk next to it, indicating there is a VC inconsistency -- even when there really is not an inconsistency. Conditions: This has only been observed when: 1. There are a large number of connections on the node, in our case 14,000 or more, and 2. the user logs in and see the [dsptech] login screen or they manual invoke the [dsptech] CLI command, while 3. connections are still being added Workaround: Wait until connection additions have stopped, and then invoke the [dsptech] command
CSCdx34887	Symptom: Connections failed to route but the 'dspcon' command displays their status as "OK" and the "Path:" as 'looking for a route'. The 'dspalms' command does not show the correct number of failed connections. Conditions: The open space calculation incorrectly checks the path as OK to route the connection, but the path is actually NOT OK due to lack of resources such as load and conid. Workaround: The 'dsprrgrps' command can be used to get the accurate number of connections requesting reroute (failed connections).
CSCdx34916	Symptom: Connections are not routed but 'dspcon' command displays the status as "OK" and "Path" as "looking for a route". The 'dnib' and 'dspload' commands show inconsistent Conid usage. Conditions: Vpc resource on a trunk is almost used up and only one VPC conid is left. The connection fails on this trunk because the lack of VPC conid. Workaround: Make VPC conid resource available to route the failed connection by either adding new trunks or free up some VPC conid resource on the trunk with the problem.
CSCdx37714	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/num/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). I also believe 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", This command allows me to set the SWSW level for use in code patches. Once i have set the required Upgrade SWSW level and issue the runrev command the node will again remain in boot mode but now i can still connect via the Ethernet Port and perform the Setrev command 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. Moving on further and trying to simplify this further i have tested in my lab on 2 separate occasions for each NPM type that if you wire the control port to the below specification you ensure the node rebuilds and comes back online with the new rev. My 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 SR 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 i used the same two card types in a single node and performed upgrades through 9.2.33, 9.2.38, 9.3.24 and 9.3.36 without problems being encounter.
CSCdx37714 (continued)	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 issue.
CSCdx48018	Symptom: swerrors 502 and 504 get logged Conditions: Not known Workaround: Not known
CSCdx48315	Symptom: The event log, error log and abort logs do not specify the time zone for when the event, error or abort occured. Conditions: This always occurs. Workaround: None. Further Problem Description: This can make debugging of a customer network a little more difficult if time zone changes have been made because support cannot easily or concretely determine when an action occured.
CSCdx48549	Symptom: The command dspportstats takes a feeder trunk interface but displays no data. Conditions: This only happens when dspportstats is given a feeder trunk interface. Workaround: Always use dsplmistats for a feeder trunk interface.
CSCdx48623	Symptom: A software error 9084 is logged on an UXM with Y-RED configuration when add local trunk loopback on UXM. Conditions: This occurs when addlnloclp is executed on a UXM trunk on a y-red card set. Workaround: Unknown
CSCdx59734	Symptom: SW Error 524 is logged Conditions: Node has SW Error 524 Workaround: Not applicable.
CSCdx65552	Symptom: Remote SIGNl FAIL alarm reported as the current APS alarm state. Conditions: Happens when APS 1:1 is configured and then trunks are upped. One end is seen to report this alarm. Workaround: Down the trunk and up it again or switch to the protection line.
CSCdx78070	Symptom: swerr 5050 is logged. Conditions: Occurs on an IGX node when cba_verify is done. Workaround: None
CSCdx84899	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	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 node 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 node 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
CSCdx87582	Symptom: Injecting errors at a rate of 10 -3 into one line of a 6 line IMA group on a UXM causes the line to be declared in Major-Frame bit Error in dspphyslnerrs output. However it is not removed from the UXM IMA group and therefore causes traffic passing over the trunk to error. Increasing the error injection rate to 10 -2 causes the line to declare a Major Loss of cell and only then is it remove from the IMA group and bandwidth is reduced. PHYSLN Type Current Line Alarm Status TRK 3.1 E1/30 Clear - OK 3.1(6) 3.2 E1/30 Clear - OK 3.1(6) 3.3 E1/30 Clear - OK 3.1(6) 3.4 E1/30 Clear - OK 3.1(6) 3.5 E1/30 Clear - OK 3.1(6) 3.6 E1/30 Major - Frames Bit Errors 3.1(6) 31.1 T1/24 Clear - OK 31.1 32.1 T3/636 Clear - OK 32.1 32.2 T3/636 Clear - OK 32.2 32.3 T3/636 Clear - OK 32.3 Last Command: dspphyslns TRK Type Current Line Alarm Status Other End 3.1(6) E1/177 Clear - OK xx/3.1(6) 31.1 T1/24 Clear - OK xxx/10.1 32.1 T3/636 Clear - OK xx/12.1 32.2 T3/636 Clear - OK x/1.7 32.3 T3/690 Clear - OK xxx/9.1 Last Command: dsptrks Conditions: Tests performed with 9.2.38 SWSW and ABR firmware on the UXME. Workaround: Current workaround is to down the Line or remove it from the group until errors cleared.
CSCdy41099	Symptom: Software error 923s are logged when there is a status change for a UXM card with IMA lines. Conditions: An IGX running software release 9.3.xx with UXM IMA lines on cards which are removing and inserting themselves. The data field of the software error shows a (hex) value between 21 and 0x40 (33 and 40 decimal). Workaround: This SWerr log is only cosmetic message. To avoid filling up the software log and preventing the logging of critical software errors the software error log should be cleared after a UXM card with IMA lines is activated. Further problem description: Software is incorrectly using the logical trunk limits (1 to 32) to check the logical line number (valid limits 1 to 64). The dlns command can be used to show the logical line to physical line mapping. The software error will be logged for active physical lines with a logical line number greater than 32. Note that physical lines with slot number "33" are not active physical lines.
CSCdy54959	Symptom: Software Error 551 is logged and the BCC aborts. On reseating the BCC the problem gets resolved. Conditions: Customer is running 9.3.36 Workaround: Reseating the BCC.
CSCdy55257	Symptom: Software Error 9000 was logged on IGX01 on UXM cards in Y-RED Conditions: This was observed on UXM cards in Y-RED and when a [switchcc] was done. There were VSI partitions on trunks on these UXM cards when the error occurred. Workaround: Not known.

Anomalies Fixed in Release 9.3.45

Anomaly Status Changes in Release 9.3.45

The following table lists anomalies that have changed status since in Release 9.3.45 as of 12/12/02. Changed status means that the anomaly went from open to a state other than resolved. The status field states whether the anomaly is closed, junked, duplicated, or unreproducible.

Anomalies Fixed in 9.3.42

Bug ID	Description
CSCdk37976	No alarm when active BCC-32 backcard removed
CSCdk49036	Multiple errors with cnftrk during Job Addition
CSCdm19518	Pref routes are not displayed correctly by cnfpref and dsprts
CSCdm31682	cnfchvcq for ALM-A connections wont allow user to maximize 16000 cell buffer
CSCdr08809	dspstbyclk shows LOS on a good external clock source
CSCdr28021	addcon on CVM does not prompt for all types of voice connections supported
CSCdr56878	cnfln to change traffic shaping does not change existing VCs
CSCdt22924	Lines configured as clock source goes to bad clock source after dncd/upcd
CSCdu34215	Usage: cnflan - contains inaccurate parameter information
CSCdu75550	log slot used instead of physical in svr_bxm_card_type()
CSCdv23693	CBR traffic dropped when background test is executed.
CSCdw11977	1m3 may be logged in Free_mem when logging other mem corruption errors
CSCdw25128	HCS Correctable error (Stat 55) was not shown when errors were injected.
CSCdw28930	External clock switch due to clock master node switchcc
CSCdw30986	swerr 992 logged after SAR reprograms IP/ILMI channels
CSCdw35862	dspapsln does not show standby fail when standby card removed
CSCdw54520	Potential memory corruption in Pcs_get_event()
CSCdw69403	shift/noshift inconsistency checks cause problems with CLI and SNMP addcon
CSCdw74242	Enabled from/time fields not updated when TFTP stats partially enabled
CSCdw74266	cnfport allowed on UFMU secondary card
CSCdw78620	Software error 75 logged on BPX
CSCdw80502	Cleanup: no effect statement in nw_r_prot.c
CSCdw83716	UBUs mistakenly assigned to UFMU
CSCdw90487	SWLOG 1423 generated on executing dsprtcache (detailed) command.
CSCdw95273	MIB incorrectly indicates that Virtual Trunks do not support stats
CSCdx02074	Be, Bc values are getting incorrectly set upon addcon
CSCdx02607	Code cleanup in addjobtrig function
CSCdx04153	Frame relay conns using wrong loadtype, with cnfcon
CSCdx05212	Unable to derive clock signal from UXM Feeder Trunk on IGX Feeder
CSCdx05238	Switchapsln followed by the same priority request is accepted and pending
CSCdx21047	cnfln job connections present prompt causes job to fail
CSCdx24719	dspchuse gives misleading information BXM-DX OC3 cards
CSCdx29539	dsppwd presents security problems; uses clear text format
CSCdx31537	dspcons shows invalid DSP Fl alarm on one end after comm. break
CSCdx42074	dle command causes watchdog timeout and switchcc
CSCdx44668	Lack of allotted space on dsptrkerr screen causes swerr 526 on IGX
CSCdx49193	CWM local/remote IBS reversed fro FRM-FRSM8 ATFST connection.
CSCdx51587	upstats doesnt show Tx and Rx frames incrementing
CSCdx54453	Cannot upgrade from legacy BXM card to DX card when in y-red
CSCdx55308	Slow rerouting time in mixed pre and post 9.3.30 network, bad seq #
CSCdx66581	swlog 933 is logged when IP service port is changed with cnflan
CSCdx66901	Increase PVC LCN not rejected by remote even if no enough LCNs on rmt
CSCdx67113	Wrong parm passed to send_pdu_to_ip() function from ilmi_hdlr
CSCdx67411	9082 logged with trunk communication failure on UXM
CSCdx72690	504& watchdog timeout cause 52 on IGX during overnight jobs
CSCdx78200	Cannot addloclp on a Frame Relay port if port number is not same as line number
CSCdx83934	Async EIA lead (cmi_lead_mon) upgrade issues when upgrading to 9230 and 93x
CSCdx83970	Card attribute for multi-VSI-partition, VSI ILMI & Topo Disc lost on 92->93
CSCdx83986	UXMs FW lcn resync card attr incorrectly initialized when upgrading from 9310
CSCdx84433	dspcd <slot> shows overlapped display.
CSCdy01237	Default Gateway IP address changes automatically
CSCdy03630	SWSW wrongly sends objects in bps format when tstber is executed.
CSCin03520	soft loopback is not functioning in switchyred when aps is added on line

Anomalies Fixed in 9.3.40

Bug ID	Description
CSCdk69912	UFM programming overrides VC_Q settings in non-standard parameters
CSCdm12850	The system idle time can be under-reported to VNS through SNMP
CSCdm60699	Async updates are sent incorrectly when VCQueue fills up
CSCdm75577	100% traffic discard at ATM end of a ATM-FR conn, added from FR side using CWM
CSCdp04164	DC Voltage Alarm - Need to increase upper alarming limit
CSCdr26161	Resetcd h of UXM during burnfwrev leaves card in burnfw state
CSCdr34820	more than 2 connections appear on single channel of DSP
CSCdr43327	If BME card is present we cannot use 0 option to burn firmware
CSCdr64816	VoiceEndptStatus returns offHook for all channels
CSCdr76559	A-bit on NNI ports doesnt clear when LMI removed and added
CSCds03159	BCC4V logged Abort 1011 after reinserting active CC
CSCds10019	Add more information to chklm and dsplm help screen
CSCds10107	New Commands for testing Voice channels (tonegen, dsptone, clrtone, cnftone)
CSCds29404	Enable cell routing is not part of robust message
CSCds37220	after switchcc, dspapsln may show aps deactivated
CSCds66268	copycons does not generate warning message
CSCdt71711	Bad Node Nib error 419 in Flex Switchcc Test
CSCdt86650	RAS: Corporate login to dsptech as default screen
CSCdt88340	Don't allow the M/F switchapsln switch the APS line backward
CSCdt98231	swerr 9098 logged after reinsert back card for VSI part deletion
CSCdu00161	Connection, Line and QBin interval statistic values displayed are incorrect
CSCdu21187	Temp a-bit failure caused by switchcc, even with feeder alert enabled
CSCdu26594	Remove the logging of 3064 when slave detects reduced number of cons
CSCdu34126	UXM trunk configs give incorrect value for selected cable length
CSCdu34853	vlcon shows wrong pref status after rrtcon reroute at master
CSCdu35011	Cannot configure E1 lines for unframed mode
CSCdu36770	memory wrt: rr_bld_cbrt_path() overwritten next long of rrt_path/rrcb_path
CSCdu38022	CLI allows ECN threshold to be greater than VCQ for incomplete set of parms
CSCdu46642	IMA trunk not allocating correct no. of DS0s
CSCdu47810	Need SWSW option to configure UXM/BXM ILMI for number of PVC changes per trap
CSCdu49568	1M3 abort upon using addport
CSCdu50924	Reroute wait timer (CM parm 9) was applied to derouted conns
CSCdu53235	SWERR 2051 logged without the addition or deletion of statistics
CSCdu55802	dspfwrev screen shows incorrect information
CSCdu58349	snmpwalk shows sysUptime 497 days after initialization
CSCdu59473	Not able to add FR conns and config/change FR class
CSCdu65259	CLI for cnfsct name failures does not give adequate help
CSCdu70637	rrtinf inprog output is not usable for text screen captures
CSCdu73638	SNMP: cannot add/mod connection to FAIL IMA port with no ACTIVE line
CSCdu75132	Add controller IP to the dspctrlrs screen
CSCdu75709	Informix DB not updated when UFMU front and backcard replace FRM or vice versa
CSCdu77043	UXM IMA trunk fails when adding line to trunk
CSCdu79181	Code added in wrong place to enable VPI Address config on UXM trunks
CSCdu84969	rt-vbr value for atmPortQueueIndex on IGX is not consistent with BPX
CSCdu85702	UXM/BXM card mismatch during upgrades causes LOS
CSCdu88501	swerr 925 for UVM inactive line when switchcc
CSCdu88771	sw error 55 seen after ddcuse command is issued on non-BNI card
CSCdv00082	No appropriate value information help for cnfport command
CSCdv01544	rrtinf inprog displays NOTHING and can log 526 when trunk count is 7+
CSCdv02043	RAS: Expand standby mem self test to detect parity (1000001) errors
CSCdv02727	Not able to add 2nd VSI controller when 3 or more trks exist on a card
CSCdv03293	Incorrect display of local clock format for dspcurclk
CSCdv03346	switch.m interface atmEndptOeEfciQSize atmEndptEfciQSize inconsistent
CSCdv03428	logical slot used with phycd_get_attr() in get_sonetiftable_int and get_shelfs
CSCdv04095	physical slot pass in to get_line_fmt() which expect logical slot
CSCdv06569	RAS: Expand standby mem selftest to detect parity (1000001) errors- IGX change
CSCdv08233	High LAN traffic can lockup node UI and cause 3M, or 52 aborts
CSCdv08861	Flood of SWerr 9000 when adding voice con on CVM that do not support voice
CSCdv08902	unique error literals needed for bkcdtype_get_name()
CSCdv09343	Code decompression error for IGX
CSCdv10468	addcon with insufficient UBUs causes 1m3 aborts on UVM
CSCdv12068	dspnds does not show all options (missing -q -x)
CSCdv12776	Misc. enhancements for Deferred conn alm gen feature
CSCdv12786	Total BW of VSI partitions on BXM card can exceed its backplane speed
CSCdv13914	Correct spelling of EPD in dspconcnf
CSCdv14343	AR 32K LCN limit and vsi cnf not handled correctly get_unreserved_chan_cnt
CSCdv15863	SNMP agent does not set XLMI default vpi.vci or atmPortMgmtProtoOnCard
CSCdv15924	RAS: enhance swerr info for vsi channel alloc failure
CSCdv16069	Line functions accept feeder trunks as input and can cause errors or aborts
CSCdv16980	Change dsptech login to always show dsptech, not just when no probe
CSCdv17884	move cnfrrcpu command to connection help group
CSCdv18027	Problems with dsptech login mechanism
CSCdv19657	get_free_lcn must use a swerr code rather than failure return value for error
CSCdv19842	Add description for SET operations on ds3ClkSource/sonetIfClkSource
CSCdv21091	BNI Total cells rx stat requested twice in 0x56 msg affects def. con alm gen
CSCdv22642	PROJ: CLI cleanup - Remove obsolete fields/commands
CSCdv24166	F4-F5 mapping enabled even when no available channels on the card
CSCdv24220	ddcuse has wrong code and is probably an obsolete command
CSCdv24530	Reducing IMA retained lnks should be blocked if Max BW becomes < Req. BW>
CSCdv24685	hot standby mismatch causing loss of O.151 OAM and XLMI support on active card
CSCdv25544	dspcd does not show mismatch information for X-LMI feature mismatch
CSCdv26618	dtrkcnfg needs to show if trunk active or not
CSCdv27309	adding a new prefer path should cancel the reroute timer
CSCdv27346	swerr 9082 logged on performing tstconseg or tstpingoam
CSCdv29727	9083 when trunks statistical reserve is set to the trunks line rate
CSCdv30106	STATS missing from TX Clp x DSCD
CSCdv30438	BPX: switchyred on BXMs causes AXIS NWIP to go unreachable via CWM
CSCdv31539	ILMI Neighbor Discovery mismatch cleanup should not cleanup XLMI information
CSCdv31936	Fail to add Master VP-Tunneling connection on IGX/UXM
CSCdv34258	Graceful upgrade from a pre 9.2.35 release does not map post 9.2.35 parms
CSCdv34759	Enhance dspconcnts to display connection endpoints terminated on cards, trunks
CSCdv35146	2 min data hit after switchyred when 2ndary card still programming channels
CSCdv35295	Cisco view shows Active and green color for FAILED UFM ports in IGX
CSCdv36176	vt does not indicate that we are logged into a Standby Controller card
CSCdv37628	polling type toggled to 2 and back to 1 during switchcc
CSCdv38469	tstber fails on BXM if VSI enabled with VPI = 0 or 1
CSCdv38587	Local and remote loopback on individual IMA links fail to loop traffic
CSCdv40684	dsplmistats, does not display the status of protocol, also no Node Status Cntr
CSCdv42399	not able to add aps line after deleting
CSCdv42531	dspctrlrs always shows default ip address 192.0.0.0 of MPLS VSI controller
CSCdv43983	Switchyred job doe not work when VSI is active on BXM
CSCdv44412	Cannot configure stat level on standby card of y-red pair
CSCdv44928	upport on UFMU card does not enforce 24M oversubscription limit
CSCdv45621	[dspprfh] indicates <active> even if invoked from the standby cc
CSCdv48264	Inactive Port Alarm Config is defaulted to ENABLED upon port activation
CSCdv51156	9340REGR: Swerr 9082, and node unreachable after upgrade
CSCdv55045	dspselftst shows CBUS Not Run
CSCdv55322	Usage info for dspviacons not updated
CSCdv55819	enhancement to display load units on user ports
CSCdv55862	PROJ: Add SNMP Support for IGX/BPX Alarm Masking
CSCdv57337	addjob/cnfport aborts (1m3) when the command times out
CSCdv58342	dspcd screen overflows for BXM-E card supp. Trk VC Shaping
CSCdv58824	yred: logical slot does not sync up SR2048 attribute in add/del yred
CSCdv58954	dsplogcd shows UFM port active but dspports shows failed
CSCdv59751	dsptrkutl on a feeder trunk doesnt showing any feeder connections
CSCdv59831	dspchoid displays UXM for URM Cards
CSCdv62358	cannot clear tstpingip counters
CSCdv63422	atmcls for UBR connections does not work
CSCdv67269	Extend Cline Robust Message to include some more useful fields
CSCdv68534	bkcd insert and yred alarm messages are logged during a switchcc
CSCdv68775	Invalid CBA array access corrupts SVC Hash Table protection pad
CSCdv69165	BXM mismatch after the stats level changed and BCC rebuild
CSCdv69576	RAS: Reprogram LMI & IP SAR connections on moving protocol & switchyred
CSCdv69717	Incr CDV & F4/F5 AIS Dect values reset to defaults after upgrade or switchcc
CSCdv70413	X-LMI port comm fail causes remote end cons in alarms after switchcc/rbld
CSCdv70803	Observing SWERR 1128 during degrade mode testing
CSCdv70946	PROJ: VC Merge on UXM - Project Checking
CSCdv71074	swerr 45/3010 upon depletion of card lcns
CSCdv71138	swerr 9082 logged on switchyred
CSCdv74130	New default power voltage threshold
CSCdv75008	Adding a con when feeder is in comm fail causes alarms when defr con is active
CSCdv75658	Code defects caused due to latest merge into 9340 baseline
CSCdv76026	Wrong check in cnftrk for DTR toggling feature
CSCdv76336	Rate values for Txvcdscd are different from other rate values
CSCdv76903	CARD FAILED when bringing up 2048kbps NTM-SR trunk, HW errs logged
CSCdv77061	X-LMI port comm fail should condition the remote end connections
CSCdv78268	Cnftrkparm on NTS Queue Depth Rejected with Unrelated Range Check
CSCdv78474	PROJ: 9.3.40 Unidirectional FCES and Policing
CSCdv78530	Deferred conn alm gen feature doesnot work when LMI protocol runs on the card
CSCdv78776	dsptrkutl: dsptrkutl is blocked after full rebuild and not recovered
CSCdv81030	CLI dspcurclk on bpx node causes sw err. 532, 26, 539
CSCdv81068	re-numbering bpx node causes 254
CSCdv81287	Prefix warning: Analyze uninitialized variable usage in Pis_fw_req_valid()
CSCdv83923	Default configuration for BXM port and feeder trunks should be NO-SHIFT
CSCdv84329	Prefix: Uninitialized fields in MSG_LETTER in abort_ldiag()
CSCdv85306	PROJ: CLI Cleanup - Remove the obsolete Adaptive Voice from display and cmd
CSCdv87061	Send correct field scrm_payload for payload scramble in Cline Object Msg
CSCdv87642	VT Oversubscription chkin
CSCdv88708	SWerr 45 on switchcc - VSI related
CSCdv90733	relaxed lmi (dsplmistats) reports wrong info on a los
CSCdv90966	swerr 384 during F4-F5 config. validation
CSCdv91284	SW ERR 1013 on fallback
CSCdw00642	Null Timer Calculation Should Not Be HUGE_DELAY
CSCdw01517	SNMP Set/Get operations incomplete on NTM-SR trunks
CSCdw07452	31 voice channels are send to cwm for CVM T1 card
CSCdw08309	Command cnfchrps is not listed in alphabetical order in help screen
CSCdw10635	ARP message pointer used before initialized, possible SNMP 1M3 abort
CSCdw10654	Prefix errors in 9.3.40 igx baseline
CSCdw11748	Trunk VC shaping does not work properly on BPX fdr trk
CSCdw11872	potential clocksrc table memory corruption
CSCdw12925	dspcd screen display is difficult to read due to merged strings
CSCdw15039	Command addloclp loops both ends for DAX connections; which is incorrect
CSCdw15054	Allow addlocrmtlp command for DAX connections
CSCdw15064	CBUS message send to BXM for addloclp needs to be corrected
CSCdw15075	addloclp command should not be allowed on connection end points on ASI port
CSCdw16041	cnfbusbw does not work in a job
CSCdw16076	Diff. path delays configured for master & slave end points of a connection
CSCdw16364	SWERR 45 and cannot uptrk on a 60K LCN BXM-E card
CSCdw16899	SNMP set/get not working for ds3LineLclLpbk and sonetLineLclLpbk
CSCdw19247	via/slave node lock up routing
CSCdw19941	swerr 9093 when configure T3 trunk line framing to be HEC
CSCdw22629	Uninitialized var used for LCON update in int_via_updt
CSCdw23663	cnfnodeparm (job lock timeouts) wrong init value between 9.1 and 9.2
CSCdw26065	Modify the command names to cnfintalm and dspintalmcnf, to reflect the age
CSCdw27395	Cannot ADDTRK after changing CNFTRK NTM-SR trk from 2048kbps to lower value
CSCdw29721	prefix: in syntax mode, cnfpref does not init hops
CSCdw30934	Deferred conn alm gen may/may not get deactivated upon full rebuild
CSCdw32389	dspqbinstats and dspcntrstats can show negative values
CSCdw32729	Improve runrev to detect unsafe standby updates
CSCdw32857	Enabling IMA on single T1 uses extra DS0
CSCdw34453	dsptrkstats/clrtrkstats on down BNI card produces SW log 8096
CSCdw34723	CNFTRK does not work in JOB mode
CSCdw39995	APS act line is not sync between SWSW and FW after BCC switch
CSCdw40453	RAS: Improve dsptech and dlcon to list the number of dax cons on the node
CSCdw43792	UAS stats not collected when line in alarm, caused by CSCdk44173 fix
CSCdw45129	Changing the min tx rate at one end of the VT causes 9093 at other end
CSCdw46236	VC Shaping should use VI Max TX rate to work with VT oversubscription feature
CSCdw48298	Can burn CVM firmware onto UVM & vice versa
CSCdw48570	Cannot add a job trigger to a virtual trunk on a BPX
CSCdw49673	Allow VC Shaping on UXM feeder trunks when IGX is a feeder node
CSCdw50142	Max Tx rate rounding off error on added trunks
CSCdw51173	need to document rt-VBR index in atmPortQueueIndex
CSCdw52505	VC Shaping (WFQ) is incorrectly applied to timestamped traffic
CSCdw53935	Use of connection max delay values are inconsistent
CSCdw54838	on off bits changed on one node after bpx sw upgrade
CSCdw55273	Redundant calls to clear mismatch
CSCdw55317	Slot alarms are not generated for Monarch Specific card errors
CSCdw58091	Cpu usage is... message is not logging after graceful upgrade and switchcc
CSCdw58129	BXM went into mismatch after swsw upgrade
CSCdw58704	Free allocated memory errors logged by SNMP process- swerr 502 589 504
CSCdw59553	dspcd screen shows pcr instead of PCR
CSCdw63725	Connection requires 11 hops to route fail to report as failure & CPU idle low
CSCdw64831	Heading for VT Ovrsubs feature appears for phy trunks in dsptrkutl CLI
CSCdw66301	swlog error 50 observed
CSCdw68727	Abort 1000003 logged on BPX after executing dsptrkutl following rebuild
CSCdw68912	dcct LCN information overwritten for DAX connections
CSCdw71520	help for ip commands causes last line overflow for nwipcache entry
CSCdw71912	dsptrkutl shows non-existent connections
CSCdw74281	addlnlocrmtlp on IGX/AF side of trunk causes comm-fail should be Clear-OK
CSCdw75500	swerr 5050 generated upon cba_verify after deleting vp-tunneling daxcon
CSCdw75730	cnfasm change to temp threshold doesnt reflect in dsppwr screen
CSCdw79108	BPX node with SWSW 9.1.24 does not sync up with CWM
CSCdw80264	10 hop cons fail to route when resources available
CSCdw84340	dsputl command does not work for UVM/CVM connections
CSCdw86061	rs_get_vpivci() does not correctly check for LMI/ILMI VCI
CSCdw86065	CNFRSRC will not allow VPI over 255 although port NNI
CSCdw88571	Incorrect feeder trunk channel programming for dax-cons
CSCdw92030	Port speeds above 6144 Kbps on UFMU-HSSI are reported incorrectly to CWM
CSCdw94435	dclk output doesnt get updated
CSCdw95202	SNMP support for Trunk VC Shaping and cnftrkq enhancement for feeders
CSCdx06654	line/trk recovered even the active APS line has LOS
CSCdx07451	AutoRoute chans allocated beyond 32768 when VSI Slave chans used on card
CSCdx08325	Unable to add connection from FR end point to ATM feeder end point
CSCdx08838	IGX reports PRI Loss (CLOCK) when deleting line clock source
CSCdx10239	Memory leak in dsptech (swerr 501, 3000000)
CSCdx10874	Enabling LMI on VSI feeder causes unreachable (always) + comm-fail(9340)
CSCdx16103	Trunk channel programming rejected(9082) when connection has PCR > port rate
CSCdx17275	UXM line looped back after sw upgrade
CSCdx17933	Dangling VLCONs and inconsistent trunk loading/conid
CSCdx18387	dsplns/dspports alarm masking reverse video is not ASCII screen capturable
CSCdx19254	swerror 521 on bpx node in upgrades network
CSCdx20304	addfrcons and dspfrchan no longer exist
CSCdx20323	752 logged when FW upgraded
CSCdx27972	RAS: Incorrect Open space calculation when inconsistent conids exist
CSCdx29500	BPX clock does not go to Tracking mode if current clock source is on port 1
CSCdx36217	connection continuously re-routes after active CC fails with swerr 47
CSCdx38407	dspviacons causes session to lockup, IDLE time of 0 and eventually 1m3 abort
CSCdx47173	Incorrect display of IGX FDR NPMs after an upgd
CSCdx57483	Removed ASM card on a BPX cage displayed as Empty Reserved for BCC
CSCdx57872	FRM port alarms are disabled by default on upgrade
CSCdx58152	addlnloclp/addlnlocrmtlp does not work when secondary UXM-IMA-YRED active
CSCdx63511	Download Aborted logged and UXM to failed status when burnfwrev to A
CSCin10198	CSCdu85702 fix missing from BPX

Anomaly Status Changes from Previous Releases

The following table lists the anomalies that have changed status prior to Release 9.3.42 as of 12/12/02. Changed status means that the anomaly went from open to a state other than resolved. The status field states whether the anomaly is closed, junked, duplicated, or unreproducible.

Additional Deliverables

SNMP MIB

The SNMP IGX/BPX switch SNMP MIB is being provided with the delivery of Release 9.3 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. There were no MIB changes in Releases 9.3.11, 9.3.20, 9.3.24, and 9.3.36.

Switch MIB changes of Release 9.3.35

voiceEndptState

New object

Switch MIB changes of Release 9.3.30

The following Switch MIB changes have been introduced since Release 9.3.30. The changes include modified objects and new objects.

atmEndptTable

Modified objects

New objects

sonetIfTable

Modified objects

atmTrunks

Modified

ShelfRtrSlotInfoTable

New objects

Switch MIB changes of Release 9.3.11, 9.3.20 and 9.3.24

Switch MIB changes of Release 9.3.10

The following Switch MIB changes have been introduced since Release 9.3.10. The changes include obsolete objects, modified objects, and new objects:

switchIfTable

Modified objects

frLportCnfTable

Modified objects

New objects

atmPortTable

Modified objects

New objects

atmPortStatTable

Modified objects

New objects

atmEndptTable

Modified objects

atmTrunkStatsTable

Modified objects

New objects

rsrcPartiTable

Modified objects

rsrcPartiPvcTable

Modified objects

atmQbinTable

Modified objects

vsiCtrlrTable

Modified objects

New objects

Switch MIB Changes to Release 9.3.05

atmPortTable

New objects

Modified objects

atmPortQueueTable

New objects

Modified objects

atmEndptTable

Modified objects

switchShelf configuration branch

New objects

atmTrunks table

New objects

Modified objects

rsrcPartiTable

New objects

Modified objects

Obsolete objects

This object limits the number of LCNs to be reprogrammed in a continuous loop so that other software processes get a fair share of the CPU time.

rsrcPartiPvcTable

This table is only available for BXM cards. The AutoRoute resource partition does not exist for a down line.

New objects

serialPortTable

Modified objects

Switch MIB changes to Release 9.3

The following Switch MIB changes have been introduced since Release 9.2.31. The changes include obsolete objects, modified objects, and new objects:

switchIfTable

Modified objects

atmPortTable

This table provides the manager a detailed view of the ATM ports available on the switch.

New objects

Modified objects

Obsolete objects

atmEndptTable

This table is used to model a PVC endpoint and contains the traffic parameters for the ATM endpoint.

Modified objects

shelfSlotInfoTable

New objects

Modified objects

ds3LineTable

This table provides the manager a view of the DS3 interfaces on the switch and supports SET functions.

Modified objects

ds3StatsTable

New objects

Modified objects

sonetStatsTable

Modified objects

atmTrunkStatsTable

Obsolete objects

vsiCtrlrTable

This new table contains the configuration for VSI controllers. The objects are advertised to all of the VSI slaves on the switch when the configuration is changed.

New objects

Default Values

Cisco BPX 8600 Nodes

BNI-T3

BNI-E3

BNI-155/155E

BXM-T3

BXM-E3

BXM-155

BXM-622

Cisco IGX 8400 Nodes

UXM-T3

UXM-T1-IMA (1 physical line up)

UXM-T1-IMA (4 physical lines up)

UXM-E1-IMA (1 physical line up)

UXM-E1-IMA (4 physical lines up)

UXM-E3

UXM-OC3

NTM-T1

NTM-E1

NTM-SR

Appendix A: BXM Firmware MFW Release Notes

About the Firmware MFW

BXM firmware version MFW 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 MFW.

Front Cards

Front Card for APS Compatibility

Back Cards

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

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

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

APS Issues

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

Step 2 After MGX Release 1 dspapsln shows both lines OK, delete the APS line on the BPX.

Step 5 Reconfigure both MGX Release 1 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 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 into 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 MFx (minus MFA) image versions. During an upgrade procedure from MEx or MFA image to MFx (minus MFA) image, both cards must be upgraded to the MFx (minus MFA) image with minimal interval between them.

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 lower than MEA. This procedure avoids card mismatch.

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

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 onwards conditional support for stats level 0 is revoked. See the Notes, Cautions, and Clarifications section point 13 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 may be used to upgrade BXMs 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. It is compatible with IOS version 12.05t2 or greater for MPLS.

3. Protection Switching based on BER on BXM may 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 may 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 above 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 MFT. If all the LCNs for the partition have been used in a version earlier than MFK after the MFT version is updated in the switch, some connections may 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.

10. APS 1:1 is not supported for VSI in versions before MFE. (Bug CSCdp42996) APS 1:1 should 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 above, this problem is fixed.

11. Total bandwidth allocated to all VSI partitions on a BXM should not be more that OC12 rate, 1412832 cps. BCC SWSW allows users to configure more than OC12 rate, in which case all 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 above and SES image 1.0.10 and above) 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 above 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.

14. Starting with MFP through this release of MFW, changes to the alarm handling have been implemented. Excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) now report to SWSW as red alarms. Therefore, SWSW fails these connections and initiates trunk rerouting.

Known Anomalies in MFW

Anomalies Fixed in MFW

Anomalies Fixed in MFV

Bug ID	Description
CSCdr55738	Symptom: Switchyred on APS 1+1 trunks is taking longer than 250 msec Condition: 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. Condition: 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. Condition: 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. Condition: 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: MGX8850 (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: SWSW 9.3.36 SPVC connections. BXM FW MFU Workaround: Unknown
CSCdx49312	Symptom: SES cannot add PVC with PCR=linerate Condition: With old ses image and BXM image ses doesn't allow to add connection and cli will reject. 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

Bug ID	Description
CSCdt90381	Symptom: A small outage (approx 10 msec) occurs on VPCs terminating/originating on BXM. Condition: 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: 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 Condition: 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. Condition: 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 Condition: 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: 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 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. Condition: 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: mostly when MGX 8850 (PXM45) is connected to SES. Workaround: None
CSCdw54957	Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX45 Conditions: 9.3.3i MFR Workaround: 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 Condition: 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: SES 1.0(14), BXM FW MFR Discards due to the policing action are reported incorrectly in dspconstats cmd. 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. Condition: BXM2 running f/w image between MFC to MFT Workaround: None. Use firmware image MFU or later on BXM2.

Anomalies Fixed in MFT

Anomalies Fixed in MFR

Anomalies Fixed in MFP

Bug ID	Description
CSCds47753	Symptoms: Card error will happen in standby "VrmDekConnEndPoint Try to delete". Condition: 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. Condition: When the connection is routed by PNNI (created by using SES controller.) Workaround: No workaround
CSCdt55356	Symptom: After configured status of all nni links to dwon at SES node svcpop2, 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 svcpop2 end points. 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: 1+1 aps with bi-dir on BPX and MGX Workaround: 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. Condition: Running 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. Ie, Stats level 0 supports 32k cons stats level 1 16k cons. Condition: 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 didn't get ack back, it would retry every T396 (polling timer), instead of using the correct T393 timer. Condition: 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. Work around: It won't 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 msg to the controller after switchyred. Conditions: 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 runng 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 Work Around: Reset the card. This problem happens only in MFN due to the chkin done in Aug 13 2001. 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: 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. Condition: BXM FW up to MFN (MF30). Standby BXM should collect this VP abr connection during initial data transfer phase. ie. 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 conn does not get rerouted if added when slave interface is down; and later when slave interface is brought back up. Condition: This is applicable only for dax conns on SES - not on MGX2. 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 uprunning without any communication problem. Condition: 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 UNREASHABLE state. Workaround: No service impact, though the fdr trk shows as unreachable. To get the correct state, reset the card.

Anomalies Fixed in MFN

Bug ID	Description
CSCds08461	Symptoms: Incorrect operations (SF_LOW sent) after detecting mode mismatch Conditions: BXM 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: SWSW 9.3.10, Cards: BXM 155 While adding connections between BPX nodes found a swlog 109 Workaround: 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: When congestion exists at an enni trunk in a AR/PNNI hybrid network. Workaround: No workaround
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: No workaround
CSCdt53756	Symptom: SES had huge CDV value compared to MGX 8850 R2. Conditions: Always occurs Workaround: None
CSCdt55356	Symptom: After configured status of all nni links to dwon at SES node svcpop2, 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. 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 svcpop2 end points. 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 isn't 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 don't 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 everytime 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. Err msg: "ERROR: Switch Response returned Failure". Conditions: The conditions for the error is 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&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&MPLS is configured in a 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: 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 devtest 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: Don't use devtest 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: 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. Stdby card is inserted at this time. Workaround: Resetting both the active and sdtby 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 signalling 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. Condition: BXM FirmWare MFN and before. Any Sw/Sw 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 params 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: Resetting 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 conns 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 stdby card once active card has all conns. 2. Do no do BXM switchovers more than once. 3. Reset standby card before doing the first switchover.

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 200ms is introduced to a trunk with a Addtech tester, 75% of the time the tstdelay result gives a reading lower than the actual RTD. ie we would expect over 400ms but get 150ms. 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 devtest 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 10ms due to a bug in the firmware BXM uses the value 250ms. Workaround: Use values above 10ms.
CSCdt48062	Symptom: Ports remain in "provisioning" state on SES. Condition: Enabling /disabling 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: 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 conns. 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

Anomalies Fixed in MFK

Anomalies Fixed in MFJ

Anomalies Fixed in MFH

Anomalies Fixed in MFF

Anomalies Fixed in MFE

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: When 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 conns 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 & 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 mal-functions and does not free the message buffers of the application processes (ILMI/VSI etc). 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 won't 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.
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,i.e. 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 aren't a PDU containing valid nonzero length peer.ifName doesn't 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: STD ABR connections. Workaround: No workaround.

Anomalies Fixed in MFC

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: When 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 doesnot 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: 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 w/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 th 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 combus message 0x52 is sent down to BXM, we were not handling the case when message says activate the lcn, but delete the vpi-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 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: When vsi get congestion (same as CSCdp58969). Workaround: None. Upgrade to/MEF or newer versions of firmware.
CSCdp59727	Symptom: Addlnlocrmt causes node unreachable. Conditions: 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 signalling 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 stdby card affect APS line. Conditions: Series of commands executed in stdby card affects APS line. Workaround: None.Upgrade to MEF or newer version of firmware.

Anomalies Fixed in MFA

Bug ID	Description
CSCdk42527	Symptom: Rx Queue becomes full after LOS on the feeder trunk. Conditions: After LOS condition on the feeder trunk. Workaround: Reset the feeder trunk.
CSCdk80483	Symptom: TX cell loss counts in dsptrkerrs increase continuously. Conditions: 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 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: 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: LOS on trunk between 2 nodes. Workaround: None
CSCdm31923	Symptom: AIS/YEL alarm doesn't 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 YESin 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 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 Farend 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: When 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: 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:
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: When high rates of BIP8 errors are received. Workaround: None.
CSCdm73220	Symptom: Trunks or Virtual Trunks does not allow traffic going through. Conditions: 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 is 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 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: 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: BXM-E OC3/ OC12 card with HW rev < 'C'. Workaround: None.
CSCdp36324	Symptom: Last user request affects switching on BPX. Conditions: Workaround:

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 h 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 o 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 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 port has two different VPI range. 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 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 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

Anomalies Fixed in MEA

Anomalies Fixed in MDA

Firmware Filenames and Sizes

Appendix B. UXM Model C ACH Firmware Release Notes

Introduction

ACH is a firmware maintenance release for UXM card on IGX. Firmware is the same for UXM and UXM-E cards.

New Features

Obsolete Features

Compatibility

Bugs Resolved in ACH

The open bugs known at this stage are listed in the Known Anomalies section of this appendix. The firmware release ACH also contains the bug fixes done in the Model B firmware up to revision ABL.

Upgrade Instructions

If the firmware being upgraded is not revision ACB or higher, then the firmware upgrade to revision ACH requires an intermediate upgrade to revision ABJ. However, before upgrading the firmware to revision ABJ, the boot code must be upgraded to boot revision 8.

If the firmware revision ACB has not been burned, follow these steps to upgrade the firmware to revision ACH:

Step 3 Upgrade the Administration application firmware to revision ABJ or greater.

Step 4 After the card comes up, upgrade the Administration application firmware to revision ACH.

If the firmware revision ACB has been burned onto the card, follow these steps to upgrade the firmware to revision ACH:

Known Anomalies in UXM Model C ACH

Anomalies Fixed in ACH

Boot Code Requirements

Unsupported Configurations or Applications.

2. Port Adapter PA-A3 on the 7200 series router not supported for "multi-vc" configuration.

5. Adding controllers on trunks is not supported. The controllers must be attached to line interfaces.

6. Usage of IMA interfaces is not supported for attaching the LSCs (Label Switched Controllers) or LERs (Label Edge Routers). This restriction is because of the non availability of IMA interface support in IOS software release 12.1.(3)T for LSC and LER interfaces. The IMA interfaces can be used for trunks between IGX nodes.

7. ILMI implementation does not support service registration and address registration.

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:

2. Changing the VPI range on a UXM interface partition is not causing the Xtagatm interface configuration on the controller to be updated.

When the slave ATM switch reports a VPI range change through an "IFC GET CNFG TRAP" the LSC does the following:

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.

The following errors display the messages: VPI/VCI in use or VCI in use. Overloading of the 0/32 tag-control PVC has occurred.

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

The following example shows xtagatm71 configuration on an LSC connected to 19.3 using configured tag-control-vc of 90/32

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.

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.

Firmware Filenames and File Sizes

Appendix C. URM Model B Firmware XBB Release Notes

Introduction

URM XBB 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 XBA.

New Features

Obsolete Features

Compatibility

Bugs Resolved in ABT

Upgrade Instructions

Boot Code Requirements

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

XBB Firmware Boot Code

XAA Firmware Boot Code

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.

Appendix D - UXM Model B Firmware ABT Release

Introduction

UXM ABT is Model-B firmware release for UXM card on IGX. Firmware is the same for UXM and UXM-E cards.

New Features

Obsolete Features

Compatibility

Anomalies Resolved in ABT

Upgrade Instructions

Boot Code Requirements

Unsupported Configuration or Applications

Firmware Filenames and Sizes

Notes and Cautions

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following URL:

Documentation CD-ROM

Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.

Ordering Documentation

Documentation Feedback

If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.

Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to

You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:

Technical Assistance Center

The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.

Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.

Cisco TAC Web Site

The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:

All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:

If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:

If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.

Cisco TAC Escalation Center

The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.

To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:

Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.

CCIP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, Networking Academy, ScriptShare, SMARTnet, TransPath, and Voice LAN are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other trademarks mentioned in this document or Web site 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. (0208R)

Generally Available (GA)	Feature is ready for wide deployment with no restrictions. Customers deploying GA features are supported by the Technical Assistance Center (TAC).
First Customer Ship (FCS)	Feature is available for controlled introduction to selected customers. To trial an FCS feature, contact your account representative. Customers selected for controlled introduction receive assistance with the test plan review and special support from the New Product Team (NPT) in addition to the normal Technical Assistance Center (TAC) support.

Filename(s)	Size (bytes)
ACH.000 to ACH.023	65536
ACH.0024	37230
ACH.img	784

Filename(s)	Size (bytes)
AC08.000	56624
AC08.img	784

Filenames	Size (bytes)
ABT.000-ABT.017	65536
ABT.018	58074
ABT.img	784

Table of Contents