9.3.25 Version Software Release Notes Cisco WAN Switching System Software

The 9.3 software release supports the Cisco WAN switching products: BPX 8600 series and 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 plans 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.

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

Definitions

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

Minimum Release

The minimum release 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	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
BPX	Virtual Ports	GA	9.3.05
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
IGX	URM Router Functionality	FCS	9.3.20

Software Release 9.3.25

This is a maintenance release including all features supported up to Release 9.3.20.

Table 1 Release 9.3.25 BPX Files

File Name(s)	File Size
9325B.000 to 9325B.024	65536
9325B.025	5146
9325B.img	784

Table 2 Release 9.3.25 IGX Files

File Name	File Size
9325G.000 to 9325G.026	65536
9325B.027	57040
9325B.img	784

Software Release 9.3.25

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

Software Release 9.3.24

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

Software Release 9.3.20

All features are supported up to Release 9.3.10, and the following additional feature is introduced:

1. Universal Router Module (URM) for IGX

This feature introduces a new card for the IGX, the Universal Router Module (URM). It consists of a new front and back card hardware combination that incorporates UXM and router functionality along with the relevant networking capabilities in a single card pair. This feature allows users to provision VoIP and VoATM on IGX switches. The URM card runs standard IOS software, which has been enhanced to support the URM card, and provides the VoIP capability. The URM card also supports VoATM provisioning which is derived from the existing UXM card. The ability to have IOS voice on the IGX is the key capability of this new feature, and the router part of this card can do IP routing by using the two FE ports on the back card.

The following features are not supported in this release of the URM feature:

VoFR (only ATM interface supported on the URM)
VSI support
MPLS LSC/LER support
VoATM support using SVCs
Y-redundancy is not supported for URM cards

Note There is not a generally available CWM revision that can support or manage the URM cards with Release 9.3.20. Some changes have been made for the Migration 1B feature, but are not part of this release.

Software Release 9.3.11

This is a maintenance release including all features supported up to Release 9.3.10.

Software Release 9.3.10

All features are supported up to Release 9.3.10, and the following additional features are introduced:

1. Dynamic Partitioning for BPX

Dynamic partitioning enables the addition of a PNNI partition to existing interfaces (both ports and trunks) without affecting any of the existing AR connections on that interface. Dynamic partitioning also enables the expansion of PNNI VPI/VCI range into the AR partition without impacting existing connections. This feature is required to facilitate the migration from AutoRoute to PNNI.

2. Qbin Statistics

In previous releases of the BPX and IGX, only statistics from Qbins 1-9 were collected on AutoRoute trunks. Starting with Release 9.3.10, the switch allows the collection of additional Qbin statistics. Following is a summary of all Qbin statistics collected by the BPX and IGX. Qbin statistics are Cells Served, Cells Discarded, and Cells Received.

UXM and BXM Qbins 1-9 on AutoRoute trunks.
BXM Qbins 0-3, 9 on AutoRoute ports.
UXM Qbins 2,3, 7-9 on AutoRoute ports.
UXM and BXM Qbins 10-15 on VSI ports and trunks.

All other Qbins are unused and the switch does not provide statistics for them.

Also starting in Release 9.3.10, the switch provides the collection of Qbin Cells Discarded statistics via SNMP for the above mentioned Qbins.

3. ILMI 4.0 for IGX

This feature allows the ILMI 4.0 protocol to be run on the UXM card instead of on an NPM card. The feature can be enabled on a port or virtual trunk basis, but the UXM card requires that the new firmware is loaded to support the new feature.

4. ILMI/ELMI Neighbor Discovery

This feature enables the Cisco Wan Manager (CWM) to discover any ATM devices attached to the BXM or UXM ports on the BPX or IGX switches, provided that those neighbor ATM devices also support ILMI Neighbor Discovery. If the BXM or UXM card supports the ILMI Neighbor Discovery feature, the user only needs to configure ILMI and Protocol-By-Card on the port, then the relay of the neighbor's topology information to CWM is automatic.

However, in order to authorize the switch to give out its own topology information to the neighboring ATM devices, the user has to use the cnfport command to enable the Neighbor Discovery Enable/Disable parameter. Use the new command dspnebdisc to display neighboring ATM devices' topology information.

Note Cisco WAN Manager (CWM) 10.3 is required for Switch Software 9.3.10. However, this version of CWM will not be going GA. When CWM 10.4 is released, it will be necessary for users to upgrade to this version of CWM to be able to use all of the features in this switch software 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 1 Execute a graceful upgrade to Release 9.3.10.

Step 2 Upgrade the UXM boot code to boot 8.

Step 3 Upgrade the run-time UXM firmware to revision ABJ or greater.

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

Warning If these procedures are not followed, there is a big possibility that the card will enter a state from which it can NOT be recovered. Please refer to Appendix B for more information about loading the new firmware.

Software Release 9.3.05

Introduced the following features:

1. Virtual Port

This feature supports a combination of Virtual Port traffic shaping and connection traffic shaping. The Virtual Port feature allows one or more Virtual Ports per Physical Port interface. Connection- level traffic shaping within Virtual Ports is supported. Although Virtual Ports can connect directly to an ATM edge device or a CPE device, they generally are used to connect indirectly through an ATM network, because direct connections to an ATM edge device or CPE equipment can be done with currently available Physical Ports. A maximum of 31 Virtual Ports is available per BXM card on the BPX. Each Virtual Port supports all AutoRoute traffic types that are currently supported by Physical Ports. (This is a chargeable feature on the BPX.)

Software Release 9.3.00

Introduced the following features:

1. Hitless Connection Density Upgrade for BXM

This feature provides a way to hitlessly upgrade an active BXM (legacy or regular enhanced model)—configured for 16K connections or less—to an enhanced BXM (version DX or EX) configured for more connections (16K or 32K). User traffic is not affected during the upgrade. This BXM connection density upgrade feature provides the customer with the ability to hitlessly scale up their networks using the enhanced BXM supporting up to 32K connections with level 1 channel statistics on the trunk side, port side, or a combination of ports and trunks. The new enhanced BXM card must be configured such that its channel statistics level and number of connections are either equal to or higher than the ones configured on the existing BXM (legacy or enhanced) that it is going to replace. This can be done automatically, based on a configurable option. The upgrade can be done for both Y-redundant and non-Y-redundant BXMs.

2. Support for 3 VSI Partitions

This feature enables support of three (3) simultaneous VSI partitions on a BXM line/trunk interface. With this feature, up to three VSI controllers can independently control the BPX switch by using different partitions of the BXM interface resources including VPI range, bandwidth, and number of connections. AutoRoute is not counted toward these three partitions. An application of the feature is the simultaneous support of MPLS controllers. However, the coexistence of MPLS and PNNI controllers on a node running Release 9.2 or later is not supported.

3. VSI MIB Support

Prior to this release, the BPX software neither kept nor knew the specific information about a VSI controller (for example, type, capability, resource usage, and so on). A network management system is needed to query the controller directly via SNMP to learn such information. This feature enables, via SNMP MIB, an NMS to query the BPX switch for VSI controllers attached to that BPX and the associated information. The feature allows for easier discovery of BPX-attached VSI controllers by external SNMP-capable application (such as CWM).

4. 800 Board-Level Revision Number

The manufacturing board-level revision number, also known as the manufacturing 800 number, provides the maximum information possible about a given card. The ability to remotely identify the manufacturing board-level revision number assists in troubleshooting, maintenance, and sparing. Prior to this release, there was no mechanism to remotely identify the board level revision number without physically removing the card from the slot. This project provides the capability to identify the board-level revision number via CLI, Cisco WAN Manager, or CiscoView for IGX and BPX cards. This feature is currently not available for backcards.

5. Priority Bumping

This feature allows connections for both BPX and IGX that are classified as more important (via COS value) to bump existing connections that are of lesser importance. Priority Bumping is useful when there are insufficient resources (for example, bandwidth) to route these important connections due to trunk failures in the network. (This is a chargeable feature on the BPX).

6. SCR (Sustained Cell Rate) and PCR (Peak Cell Rate) Policing at Less Than 50 CPS on BXM and UXM

With this feature, the minimum SCR and PCR policing values supported by the BXM and UXM are lowered depending on card types:

For BXM and UXM models with interface speeds lower than, or equal to, T3/E3, the minimum SCR and PCR values are lowered (see the following chart) for the connections terminating on the card with policing enabled.

Card Name	Card Types	Min SCR and PCR Policing Values
IGX-UXM	T1/E1	6 cells per second
IGX-UXM	T1/E1 IMA	6 cells per second
IGX-UXM	T3/E3	12 cells per second
IGX-UXM	OC3/STM-1	50 cells per second
BPX-BXM	T3/E3	12 cells per second
BPX-BXM	OC3/STM-1	50 cells per second
BPX-BXM	OC12/STM-4	50 cells per second

The CLI and CWM blocks attempts to set up a connection on a BXM or UXM with policing on and with the SCR and/or PCR value below the new minimum SCR and/or PCR policing value of the card.

The policing prompt will be introduced for ABRSTD connections with VSVD=OFF. Previously, policing was always enabled for ABRSTD connections with VSVD=OFF. This change delivers the following advantages for ABRSTD connections with VSVD=OFF.

Policing prompt is now consistent in all connection types.
The minimum PCR is lowered to 6 cps when policing is disabled.

7. Separate Abort Stack

The software error table on the IGX and BPX currently contains up to 12 entries. When the table is full, additional errors overwrite the last entry. Errors that are not fatal are processed equally with aborts. This means that if an abort is logged into the last entry of the table, an error can then be logged, overwriting the more important abort information. Similarly, if more than one abort is logged when the table is full, only the last one logged remains in the table. This feature allows the preservation of abort stack information which, in turn, allows for faster debugging and fix implementation.

8. Upgrades Protection

This enhancement provides additional protection against running loadrev/runrev and doing upgrades during the time that statistics collection is enabled. This enhancement warns and automatically disables statistics collection if the user says "Yes" to the warning prompt.

9. 2000 VC Bandwidth Parameters

This enhancement increases the maximum number of VC bandwidth parameters from 700 to 2000 on an IGX. This enables service providers to increase service offerings where additional VC bandwidth parameters are required.

10. UXM and UXM-E ATM Forum IMA-Compliant Ports

This feature enables the UXM and UXM-E to support ATM Forum IMA Standard version 1.0 compliant IMA ports in addition to IMA trunks. Support for IMA ports allows the IGX to directly interoperate with other Cisco devices that support IMA ports, and provide a more cost-effective alternative to using an AUSM/B in an SES feeder to IGX to support the same functionality. This IMA functionality complies with the ATM Forum IMA Standard version 1.0.

11. Control Traffic Shaping

This enhancement allows users traffic-exclusive use of available trunk bandwidth. Previously CC Traffic used available trunk bandwidth in excess of statistic reserve at the highest priority, bumping user traffic also trying to claim available bandwidth. This feature also requires the appropriate firmware versions for the cards.

Clarifications for Release 9.3.24

None.

Clarifications for Release 9.3.20

1. Changes in IGX Parameters

New options for dsplns and dspclns

dsplns (no options) displays the detailed screen, and queries the user if summary lines need to be displayed

dsplns d displays the detailed screen, and user is not queried for summary display

dsplns s displays only the summary screen, for example:

Line Summary

Active Lines	7

Active Router Ports	1

Available Lines	56

Total Lines	64

dsplns <invalid input> user is prompted for a valid input

Removed VC-shaping parameter from cnfln

This command does not query the user for the VC shaping parameter.

New parameters for cnfport

This command queries the user for the VC shaping parameter.

VC Shaping Required?  [N] :

Changes for cnfport for URM ports

For URM ports, the port type is always UNI, and the protocol can be either ILMI or NONE. If ILMI is configured, only Protocol-run-on-the-card is supported.

These changes also apply to the SNMP interface.

Note XLMI and ENNI options are displayed for cnfport and dspport. However, users should note that this is an unsupported feature in 9.3.20.

Changes for addport, delport, and dspports for URM ports

Accepts URM ports.

Changes for cnftstparm and dspblkdfuncs for URM card

Accepts URM card type

Changes for dspalms for URM card

Added new alarm type for URM router alarm

IOS Unavailable

Changes for dspcds, dspcd, and dsplogcd

Supports URM card

New command dsprtrslot

This command displays detailed operational information and alarm status for all URM embedded router on a specified router slot.

New command dsprtrslots

This command displays a summary of the operational information and alarm status for all URM embedded routers.

New command rstrtr

This command resets the embedded router in a URM card. This does not affect the embedded UXM.

New command cnfrtr

This command configures the router parameters on a specified URM card slot.

New command dsprtr

This command displays all the router configuration parameters on a specified URM card slot.

New command cnfrtrparm

This command displays all the router configuration parameters on a specified URM card slot.

New command cnfoamseg and dspoamseg

Note For the Migration 1B feature, these commands have been added but are not part of this release.

2. Changes in BPX Parameters

Changes for dspcd

This command now displays the type and revision for BXM-E cards.

Clarifications for Release 9.3.11

None.

Clarifications for Release 9.3.10

1. Only the cell discard Qbin statistics for the allowed Qbins are provided via SNMP.

2. Starting with Release 9.3.10 on the BPX, the cnfvsipart command is only applicable to BXM trunks. To enable VSI ILMI on the port, use the cnfport command to enable ILMI and protocol by card. Doing so effectively enables VSI ILMI on the port interface.

3. Changes in BPX Parameters:

New parameter in cnfport when Protocol is set to I (ILMI):

Reset ILMI when VSI controller is added? [Y]:

New port parameter in cnfport for BXM physical port:

Neighbor Discovery? [N]:

Meaning of the Neighbor Discovery parameter:

Y—The BPX sends its interface information to the neighbor if queried by the neighbor.

N—The BPX does not send its information to the neighbor.

The BPX always queries for its neighbor's interface information using the ILMI Neighbor Discovery procedure and reports to CWM if the information is available, whether the Neighbor Discovery parameter is set to Y or N.

New parameters in cnfnodeparm:

55 LCN reprgrm batch cnt [  100] (D)

56 Dnld LanIP or NwIP [  Lan] (Lan/Nw)

New parameters in cnfrsrc:

Configure PVC VPI ranges? [N]

Start of PVC VPI range 1 [-1]

End of PVC VPI range 1 [-1]

Start of PVC VPI range 2 [-1]

End of PVC VPI range 2 [-1]

Start of PVC VPI range 3 [-1]

End of PVC VPI range 3 [-1]

Start of PVC VPI range 4 [-1]

End of PVC VPI range 4 [-1]

The cnfvsipart is modified to only support trunks.

User needs to use cnfport command to enable/disable ILMI/VSI ILMI on ports.

New command dspnebdisc:

This new command is used to display neighboring ATM devices' topology information. This command is added to support the BPX ILMI Neighbor Discovery feature.

4. Changes in IGX parameters:

New port parameter in cnfport for UXM physical port:

Neighbor Discovery ? [N]:

Meaning of the Neighbor Discovery enable/disable parameter:

Y—The IGX sends its interface information to the neighbor if queried by the neighbor.

N—The IGX does not send its information to the neighbor.

The IGX always queries for its neighbor's interface information using the ILMI Neighbor Discovery procedure and reports to CWM if the information is available, whether the Neighbor Discovery parameter is set to Y or N.

New port parameter in cnfport and dspport for UXM port:

Protocol run on the card [Y]:

When the protocol is set to ILMI, the meaning of the parameter:

Y—The ILMI protocol is executed by the UXM card.

N—The protocol is executed by the NPM.

New port parameter in cnfport and dspport for UFM port:

Neighbor Discovery 		Enable

New virtual trunk parameter in cnftrk and dsptrk:

Protocol run on the card (Y):

Meaning of the parameter:

If the parameter is enabled, the UXM virtual trunk runs the ILMI protocol; NPM does not run the protocol.
If the parameter is disabled, NPM runs the protocol; UXM does not run the protocol.

New parameters on cnfnodeparm:

53 Dnld LanIP or NwIP	 [ Lan](Lan/Nw)

New command dspnebdisc:

This new command is used to display neighboring ATM devices' topology information. This command is added to support the IGX ILMI Neighbor Discovery feature.

5. The IMA-added trunk transmit rate can be configured without deleting it. But it is done locally and is not propagated to the other end.

Clarifications for Release 9.3.05

1. Starting with Release 9.3.05 on the BPX, the user needs to execute the following sequence of commands to create an ATM service port or virtual port: upln, addport, cnfport, upport. Previously, only upln and upport were required.

2. Starting with Release 9.3.05 on the BPX, the VC-Shaping parameter is no longer available with the cnfln command. Use the cnfportq command to enable/disable VC Shaping.

3. Starting with Release 9.3.05 on the BPX, the user can configure the port bandwidth. Previously this parameter was defaulted to the line speed.

4. Starting with Release 9.3.05 on the BPX, the user can configure the VC Queue Depth parameter for the CBR and VBR connection. Previously, this parameter was configurable only with ABR-type connections.

5. The restriction of not being able to configure additional VSI partitions if one partition already uses VPI=0 has been removed. VPI is allowed to be 0 for a VSI partition on feeder trunks, in addition to ports. However, since both the PNNI and MPLS controllers uses certain default control channels, users should be extremely cautious with the controller's channels. Side effects of the collisions are unpredictable for BPXs.

6. The addloclp/dellp command cannot be used for port loopbacks on virtual ports. Use addportloclp/delportlp instead.

7. Changes in BPX Parameters:

New port numbering in addport for virtual ports:

5.1.1 	0 / 0 3096 (cps) LM-BXM		INACTIVE 	NONE 	UNI

New parameters in cnfport and upport for virtual ports:

Port: 5.1.1 [INACTIVE] 

Bandwidth/AR BW:  3096/3096

VPI Range: 1 - 1 

CAC Reserve: 0

New parameter in cnfswfunc:

6   Disabled Priority Bumping

7							Disabled Virtual Ports

8. The dsplog command has been enhanced in Release 9.3.05. User-visible changes include:

dsplog

A counter at the top of the event log indicates both the user's place and the total entries in the event log.

dsplog i (Service level and above)

Integrated mode. Integrates a single-line summary of software error and abort log entries into the display (by time-stamp) and are displayed in reverse video. For example:

Info  Log Cleared                      	12/15/99 09:38:20

Info  Error   527 Data:00000081 PC:302C6D8E/USR1 						9.3.n6 12/15/99 09:38:13

Info  Abort   1015 Data:DEADBEEF PC:302BE03E/TN_1 9.3.n5 12/10/99 14:38:45

This can be combined with all of the above options EXCEPT "p". Thus, dsplog i r t, but not dsplog p i t.

Clarifications for Release 9.3.00

1. For the 800-level part number, there is a dependency on manufacturing to release boards with NOVRAM containing an 800-level part number. There are scenarios in which the 800-level part number cannot be seen. See the following chart for the different combinations:

SWSW release	NOVRAM contents	SWSW CLI (dspcd/dspnovram and so on) display
>= 9.3.00	New NOVRAM	Top Assembly Number, which is the 800-level part number (10 bytes).
< 9.3.00	New NOVRAM	Fab number which shows part of the 800-level number. The display shows as per the SWSW release prior to 9.3.0, except that the data displayed is partial 800-level part number.
< 9.3.00	Old NOVRAM	Fab Number. The display shows as per the SWSW release prior to 9.3.0
>= 9.3.0	Old NOVRAM	Top Assembly Number showing 10 bytes, of which 8 bytes may convey 28, or 73-level, or raw fab number. The last two bytes are blank spaces and the user sees 8 bytes only. Hence, there is no change in information compared to SWSW < 9.3.00.

Notes:

New NOVRAM means that manufacturing has entered the 800-level part number into NOVRAM.
Old NOVRAM means that manufacturing uses old numbering scheme (non-800-level numbering).
In the case of new NOVRAM and old SWSW, the last two digits of the 800 numbers would not show up on the screen. The last two digits are the ones that point to the specific board version level. For example: 800-33415-01 would be the first version and 800-33415-02 would be the second version of the same board.

2. The dsplog command has been enhanced in Release 9.3.00. User-visible changes include:

dsplog r

Reverses the log, showing oldest entries first. This option allows you to see the bottom of the list quickly.

dsplog p

Allows paging through the log, much like dspcons. For a single page log, this option acts just like dsplog and terminates immediately. But for multiple page logs, it allows you to move backward and forward through the log by pages (using "n" and "p") until "q" or DEL is pressed.

dsplog t <yyyy mm dd hh mm ss>

Time-stamp mode. Begins log display with the entry nearest to the specified time. The time parameters must immediately follow the "t" option.

Combinations of options: All the above options can be combined (in any order) and behaves in the appropriate fashion. Thus

dsplog p r (allows bidirectional paging through reversed log)
dsplog t <yyyy mm dd hh mm ss> p (allows bidirectional paging through log, starting with time yyyy mm dd hh mm ss

3. The Robust APS Alarm message that the BPX sends to CWM is being modified to contain a new field. CWM converts these Robust APS Alarm messages into SNMP trap 20100. When APS Alarm Clear messages are sent from the BPX to CWM, the resulting 20100 trap contains a new field indicating the alarm condition that is being cleared.

4. Changes in BPX Parameters:

New parameter in cnfcmparm:

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

New parameter in on3:

Region memory init  4   Disabled

New parameters on cnfnodeparm:

52 CommBrk 	Hop Weight	[ 25](D)

53 CG Fail Penalty Hops	[ 2](D)

54 Auto BXM Upgrade	[ Y](Y/N)

5. Changes in IGX parameters:

New parameter in cnfcmparm:

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

New parameters on cnfnodeparm:

52 CommBrk 	Hop Weight	[ 25](D)

53 CG Fail Penalty Hops	[ 2](D)

Parameter removed from on1:

SVC Del Bgnd Updates

Clarifications for Release 9.2

1. There is a change in reporting of the port group number starting in Release 9.2.30. The previous image (MEC) of BXM firmware used to report one port group for the two-port group cards at the channel statistics level 2 and 3. This made the port belonging to the second port group unusable.

When upgrading from MEA-MEC, you must upgrade the software to 9.2.30 (or later) first and then burn the BXM card with the MED (or later) firmware. The BXM reports two port groups for two port cards all the time. The smooth transition between the earlier one-port group and the newly reported two- port groups also displays message in dspcd "Inconsistency with logical PG #" (port group number). All earlier software mismatches the card.

If the BXM card is programmed with an MEC or earlier firmware revision, the Channel Statistics level 2 or 3 reports one-port group. Burning a MED or later image results in two-port groups, but for backward compatibility the software does not recompute the LCNs based on the new port groups. In its logical database, this does not impact the AutoRoute connections.

For a VSI controller, the reported value is higher than the actual available LCNs. That means a VSI controller may not be able to add connections even though the available connections are non-zero. If the user wishes to remove the above discrepancy, the card must be put in the standby mode.

Note The newly configured card, or the card in standby mode programmed with an MED image brought to the active state, does not have the above discrepancy.

2. The combinations of system limits such as the number of trunks, lines, ports, and connections, as well as enabled TFTP interval statistics, should be provisioned so that the node has at least 50 percent idle time usage. Use the command dspprfhist to verify.

3. On the BXM and UXM, for the OC-3 Multimode Fiber back cards, Y-Redundancy/hot standby is not supported due to reduced optical power.

4. Release 9.2.31 introduces a new command—cnffdrlmiparms which makes the feeder LMI timers and counters configurable. This command is currently supported on BPX only and cannot be added in the Job mode.

Usage: cnffdrlmiparms slot.port T393 T394 T396 N394 N395

Where slot.port specifies the feeder trunk to configure. The details of the other parameters is as follows:

Timer	Description	Range (sec.)	Default (sec.)
T396	LMI polling timer	5-30	10
T393	SPC STATUS ENQUIRY timer	5-30	10
T394	SPC UPDATE STATUS timer	5-30	10
N394	Max. retry count for SPC STATUS ENQUIRY/ REPORT procedures	1-10	5
N395	Max. retry count for SPC UPDATESTATUS / ACK procedures	1 -10	5

5. In Release 9.2.31, the system parameter 2 (cnfsysparm 2) is changed from "Fail Connections On Communication Break" to "Allow CPU Starvation of Fail Handler."

The old parameter has been removed as it violated the principle of separating the control and data plane. The new parameter allows a new feature to be turned off that gives CPU to the Fail Handler at the expense of the Transaction Handler in case the Fail Handler does not get scheduled for a long time.

6. The minimum software required to run MPLS are:

BPX Switch Software Release 9.2.30 or later
BXM Firmware MEF
IOS Release 12.07 T or later (refer to IOS Release Note)
Virtual Switch Interface (VSI) 2.2

or,

BPX Switch Software Release 9.1.08 or later within the 9.1 release,
BXM Firmware MCB
IOS software release 11.1(19)CT or later within the 11.1.x CT release (refer to IOS Release Note)
VSI 1.0

Special Installation/Upgrade Requirements

Note There are no generally available CWM revision that can support or manage the URM card with Release 9.3.20, or support the features in Release 9.3.10.

General Upgrade Procedure

Note Please consult your Support Representative before performing any software upgrade.

The earliest release supported for a graceful upgrade is 9.2.23.

Before you upgrade 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 Appendix A for instructions on upgrading the BXM firmware.

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

Note For the VSI/MPLS feature, upgrade the UXM firmware to revision ACC or later. Note that the upgrade procedure has changed.

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 1 Execute a graceful upgrade to Release 9.3.24.

Step 2 Upgrade the UXM boot code to boot 8.

Step 3 Upgrade the run-time UXM firmware to revision ABJ or greater.

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:

Step 1 Execute a graceful upgrade to Release 9.3.24.

Step 2 Upgrade the run-time 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.

If upgrading to BCC-4 cards on BPX 8600 nodes, the software upgrade should be done first, followed by the BCC-4 physical card upgrade. If BCC-4 is already installed, then upgrade as normal.
If any other type of BCC cards are being physically upgraded, then the physical upgrade of the cards should be completed first, followed by the 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 customers to upgrade their networks from 9.2 to 9.3 in multiple steps. It is not recommended that users operate in this state for extended periods of time.

Normal network maintenance and operations such as provisioning, trunk reroutes, card insertions and removals, and normal network alarming, are supported in the mixed revision network. Normal alarms can be received while upgrading a node to Release 9.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 will 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 will function at their 9.2 capabilities, and not at their 9.3 levels until all nodes are upgraded. The command dspblkdfuncs will display blocked (disabled) features.

Note The URM card cannot be activated in a network with mixed switch software releases.

Version Compatibility Notes

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

This release runs with:

Any MGX 8220 Release 4.1 and 5.0

Note MGX 8220 Release 4.1 cannot be used to have an IMA trunk to a UXM Model B card because MGX 8220 Release 4.1 uses a non-standard IMA standard while UXM Model B firmware uses a ATM Forum IMA compliant standard.

Cisco WAN Manager (Cisco StrataView Plus) version 10.4.01

Note Cisco WAN Manager (CWM) 10.3 is required for Switch Software 9.3.10 or later. However, this version of CWM will not be going GA. When CWM 10.4 is released, it will be necessary for users to upgrade to this version of CWM to be able to use all of the features in this switch software release.

CiscoView version 5.2
UXM firmware

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

BXM model MFD or later
UFM firmware for ELMI-based topology discovery feature

For UFM-C model B, version ZBD, and UFM-U model B, version YBC
For UFM-C model A, version ZAT, and UFM-U model version A, YAL

URM Model XAA, or later
MGX 8850 version 1.1.32
SES version 1.10.12
IOS version 12.1 (5)T

Note VNS interworking is supported in Release 9.3.24.

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.

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

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

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

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

Step 2 Execute the switchcc command and wait until the NPM(1) becomes standby. NPM(2) is now active.

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

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

Step 5 Execute the switchcc command and wait until the NPM(2) becomes standby. NPM(1) is now active.

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

Control Card Compatibility Requirements

Each redundant pair of BCC cards in a given BPX 8600 node must be of identical type and memory configuration. That is, for example, if the active card is a BCC-3-64, then so must be the standby. 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. That is, for example, if the active card is an NPM-32, then so must be the standby. 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.

This is a requirement for all software upgrade procedures. It does 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. This applies to all processors: BCCs, and/or NPMs.

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

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

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

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

Step 5 Verify that the network is stable.

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

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

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

Step 9 The CC physical upgrade is now complete.

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

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

Obsoleted

BPX BCC-32 cards are no longer supported in Release 9.3.

The following IGX cards are no longer supported in Release 9.3:

FTM
BTM
ALM/A
ALM/B

UVM model A, B, and C firmware are not supported in SWSW Release 9.3 and beyond.

Adaptive Voice feature is not supported in IGX SWSW Release 9.3

Notes and Cautions

This section contains additional information about previous releases.

Additional Notes for Release 9.3.24

None.

Additional Notes for Release 9.3.20

The URM lines are included in the maximum number of lines on the nodes.

Additional Notes for Release 9.3.11

None.

Additional Notes for Release 9.3.10

1. VSI/MPLS controllers should be added on a line and not on trunks. The following steps should be followed:

Step 1 Up the line by using the upln command.

Step 2 Up the ports by using the upport command.

Step 3 Configure the partition resources by using the cnfrsrc command.

Step 4 Add an MPLS controller by using the addctrlr command.

2. Typical ILMI configuration on the router side should have the following type of information:

interface ATM2/0

IP address 10.9.8.4 255.255.255.0

no IP directed-broadcast

ATM PVC 41 0 16 ILMI

ATM PVC 46 0 5 qsaal

ATM ILMI-keepalive 20

no ATM address-registration

ATM ILMI-PVC-discovery

3. The VPI/VCI for ILMI control PVC should match on UXM port and the neighbor router/IGX/BPX for ILMI protocol to work correctly.

4. Certain parameters for the router configuration would require shutdown and up the router interface using router command "shut/no shut" on the interface to take effect on the modified configuration.

Additional Notes for Release 9.3.05

1. An incompatibility exists between the ASI and BXM implementations of the HCF no-shift mode. As a result, the diagnostic command tstdelay fails for a connection terminating on an ASI and a BXM when the associated ports are configured for the HCF no-shift. Note that the following connection types are not affected by this incompatibility (and thus tstdelay works as expected):

ASI-BXM connections terminating on ports in HCF shift mode
ASI-ASI and BXM-BXM connections, regardless of HCF shift mode

In general, customers should, whenever possible, avoid mixing ASI and BXM ports when the use of HCF no-shift mode is required.

2. When Priority Bumping is turned on, connections are added with a cos value of 15 instead of 0. When Priority Bumping is turned off, all connections except voice connections add with a default value of 0. Voice connections add with a default value of 2. If a different value for cos (other than 15) is desired, use the cnfcos command to change the value.

3. VPI 0 is now supported on a VSI partition even when there are multiple VSI partitions on the interface. This functionality reverses the restriction in the 9.2 release.

4. On the enhanced BXM card (BXM-E), the firmware translates the configured transmit cell rate (cells per second) into a minimum inter-cell gap. The mathematics of this conversion involves non-integer computations, which introduces rounding/truncation effects. As a result, the actual output bandwidth is somewhat larger than the configured bandwidth. This behavior is manifested in certain situations when the bandwidth of a port, virtual port, trunk, or virtual trunk is configured for less than the line rate, and the port/trunk is heavily loaded. The Cisco WAN Switching Command Reference, Release 9.3.05, Appendix A, BXM-E Configured and Actual Bandwidths, contains a table showing the actual output bandwidth versus the configured bandwidth.

Additional Notes for Release 9.3.00

1. Once Priority Bumping feature is enabled, the reroute timer in cnfcmparm (9 Reroute Timer) is recommended to be set to a value of 3 seconds or greater.

The need to do so is to make the bumped connections (connections that are derouted when priority bumping is exercised) wait for this period before they are eligible to route again.

2. The "Adaptive Voice" feature, also known as the "Adaptive VAD" feature, is not supported by the IGX Switch Software. However, Voice Activity Detection, or VAD, is still supported.

Additional Notes for Release 9.2

1. Because of a hardware limitation, the non-enhanced versions of the BXM hardware are not able to recognize all user-programmed cell transmission rates. Rather, only discrete transmission rates can be used.

The equation below shows what the BXM hardware actually transmits given a user-configured cell rate. The transmitted cell rate is always less than or equal to the configured cell rate. To prevent any cell loss, the transmitted cell rate must be equal to the configured rate. To do so, a cell rate must be chosen from the chart that follows.

The rate chart lists the highest 200 cell rates supported by BXM such that if used results in no cell loss (given cell traffic is less than configured cell rate). Additional rates can be calculated using 1470588/[n + (1/256)], where n is an integer.

The logic to calculate the actual cell transmission rate in a BXM card is as follows:

if (configured cell rate = full line cell rate) then

transmitted cell rate = full line cell rate

else

transmitted cell rate = from equation below or from the following chart

Example:

If a trunk is configured at 100,000 cps, the actual transmitted cell rate is then 98,013 cells per second (cps), and any traffic sent over 98,013 cps would be discarded.

If a trunk is configured at 98,013 cps, then the actual transmitted cell rate is 98,013 cps with no cell loss.

Therefore, only rates in the following chart should be used. Otherwise, cell loss may be experienced. The chart is not be exhausted at the end, but still go on with the computing from the above equation.

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

2. On the BPX with MGX 8220 feeder(s), regardless of the setting of the Node Parameter "42 Enable Feeder Alert", a feeder alert message is sent to all MGX 8220 feeders immediately before a hitless rebuild takes place. The feeder alert message temporarily disables the LMI polling from the MGX 8220 feeders. The MGX 8220 polling resumes as soon as the BPX is ready to exchange LMI messages.

3. The amount of traffic allowed on a VP Tunneling connection is two-thirds the bandwidth of that connection. The minimum bandwidth must be 100 cells per second. For example, a CBR connection with peak cell rate 1500 cps then can pass traffic up to 1000 cps.

4. For an IMA trunk, the configuration is blocked if the converted cps of the number of links to be decremented is MORE than the transmit rate (CSCdm71616).

5. Card errors (0x25170076) occur on BXM when only one virtual trunk (VT) is configured in a physical port. To avoid this situation, configure at least two virtual trunks on any physical port that you have VTs on. When performing the configuration, make sure to configure the VTs one directly after the other (CSCdm69974).

Limitations for Release 9.3.24

None.

Limitations for Release 9.3.20

1. No generally available CWM revision can support or manage the URM cards with Release 9.3.20.

2. Y-redundancy is not supported for the URM cards.

3. The UPM card cannot be activated in a network with mixed switch software releases.

4. On URM ports, VPI 0 and VCI 1023 is reserved.

5. The following features are not supported in this release of the URM feature:

VoFR (only ATM interface supported on the URM)
VSI support
MPLS LSC/LER support
VoATM support using SVCs

Limitations for Release 9.3.11

When an IGX feeder node has a trunk connected to an IGX routing node, the UXM card can go into a mismatch state when the Switch Software is upgraded to 9.3.x and the voice and data connections are terminated on the UXM feeder trunk. The workaround for this limitation is either (1) burn UXM firmware ABK or later, or burn firmware ACB or later onto the card or (2) reset the UXM card. (CSCds85758)

Limitations for Release 9.3.10

1. If ILMI is enabled to run on a UXM card, than no address registration or service registration is supported for ILMI 4.0.

2. When ILMI is running on the cards on a virtual trunk port, all the virtual trunks on the same port share the same ILMI session.

3. The LMI protocol must not run on the BXM cards connected to an Axis shelf. It should run on the BCC cards.

4. Executing a dncd command on a BNI-155 does not turn off the laser on the physical port. As a result, the other trunk end connected to this card still detects a physical layer signal and regards this as a trunk "communication failure" rather than as a LOS (loss of signal). Hence, all connections fail and are not derouted/rerouted by the connection management (AutoRoute or Priority Bumping in 9.3x).

5. ILMI Neighbor Discovery is only supported on BXM/UXM physical ports.

6. An NPM-64B card is required for the VSI feature.

7. Release 9.3.10 does not support the VSI feature in a mixed revision network. All nodes in the network must run Release 9.3.10 or later in order to use the VSI feature.

8. ILMI can be enabled on a UXM card, but it cannot be enabled on the same card as VSI.

9. When an MPLS controller is added to a port, it sets up a signalling channel to the port to which it is attached. The VPI and VCI for this connection are user-configurable. Default values of 0 and 32 are used if the user does not configure different values. So extreme card should be taken before adding an Auto Route connection with VPI = 0. An Auto Route connection should never be added with a VPI and VCI that is being used by the MPLS controller. If an addcon command fails with swerr 9082 (with firmware error code 0x01EF), this means that an attempt was made to add an Auto Route connection where an MPLS signalling VC was already existing. If this error is seen, the Auto Route connection that caused it should be deleted immediately. The way to avoid to getting to this situation is to configure the signalling VC on the router such that it is within the VSI partition. In other words, instead of having the signalling VC as 0/32, configure the signalling VC on X/32 where X is the starting VPI of the VSI partition configuration for the control port interface.

10. The BPX only supports ILMI address registration with a PNNI controller. In the case where the BXM port does not have a VSI partition controlled by a PNNI controller, it is necessary to disable address registration on the attached router. This is to prevent the router from sending unnecessary ILMI cold start trap to the BPX.
Below is an example of how to disable address registration on a Cisco 7200 series router:
interface atm 1/0"
no atm address registration
Refer to the IOS command reference and Configuring ATM on ATM port adapter for further details.

11. Release 9.3.10 supports only MPLS controllers for the IGX. The PNNI controller is not supported in Release 9.3.10 for the IGX.

12. Release 9.3.10 supports only up to 3 controllers (1 controller per partition).

13. Release 9.3.10 does not support controller redundancy for the IGX.

14. Release 9.3.10 does not support compact CBA on slave side, that is the command compactrsrc VSI is not supported for the IGX.

15. Release 9.3.10 does not support Auto UBU allocation for the UXM only. UBUs must be allocated manually for the IGX.

16. For the IGX, when a VSI partition is deleted/disabled, all connections are deleted.

17. If CBR connections are configured with PCR less than or equal to 50cps, CBR cells may be dropped at a BXM trunk interface. Do not add a CBR connection with the PCR less than or equal to 50 cps. Using CBR connections with the PCR greater than or equal to 51 cps does not cause any cell drops.

Limitations for Release 9.3.05

None.

Limitations for Release 9.3.00

1. Level Version Number is supported for front cards only.

2. Standards-compliant IMA ports (MGX 8220, Release 5.x) on UXM/UXM-E are not compatible with the proprietary protocol used in the IMATM (MGX 8220, Release 4.x).

3. Standards-compliant IMA trunks are not compatible with the proprietary IMA protocol used in Model A UXM firmware. Model B and later firmware releases are IMA standard-compliant. Both ends of an IMA trunk must have the same protocol.

4. Switch software 9.3.00 and BXM firmware MFB support the attachment of multiple VSI controllers to the BPX. In case of MPLS, however, only one LSC should be attached to a VSI partition, which is the same for the IGX. If multiple LSCs are attached to a VSI partition, the results are unpredictable, which is the same for the IGX.

5. On BXM OC-3, OC-12 8DX, and 2DX enhanced cards, do not configure the queue depth(s) for CBR / rt-VBR / nrt-VBR / UBR/ABR to be greater than 262143 using the cnfportq command. All configuration changes made while or after configuring queue depth(s) greater than 262143 are lost after a rebuild, when the switch is running 9.3.00. All ports, whose queue depth(s) are configured to be greater than 262143 in 92 are lost after upgrading from 9.2 to 9.3.00.

6. When doing a grouped upgrade from Release 9.2 to 9.3, the software error 1427 may be logged on the BPX/IGX node during a non-graceful upgrade. This error can be ignored since it is harmless to the network.

7. When upgrading from Release 9.2 to 9.3, the 9.2 statistics on BXM/UXM cards are supported to maintain compatibility. However, once users configure a statistics level in 9.3, they cannot configure back to 9.2 statistics.

Prior to replacing a bad BXM/UXM, make sure that the level of channel statistics is the same as the original card.

Limitations for Release 9.2

1. The coexistence of MPLS and PNNI controllers on a node running Release 9.2 or later is not supported.

2. When cnfrsrc command is used to delete VSI partitions on an interface, software does not check if any Soft Permanent Virtual Circuit (SPVC) connections exists on that partition. Even if there are SPVC connections on a partition, the partition can be deleted using the cnfrsrc command. The only protection is that users are provided with a warning when they try to delete the partition.

If there are SPVC connections on a partition and the partition is deleted, the SPVC connections are left in a undefined and unrecoverable state. Hence, before deleting a VSI partition, ensure that all the SPVC connections are deleted on that partition.

3. The cloud port to which a virtual trunk is connected should have ILMI polling disabled. Otherwise, it could lead to a virtual trunk being clear on one end and declaring Virtual Trunk Path Failure at the other end (CSCdm52909).

4. For performance reasons, AIS connection status is not sent to the standby BCC. After switchcc, it may take a few minutes to update the AIS connection status. If dspcon does not show the proper status of AIS or the dspalms screen shows the incorrect number of AIS, (after switchcc) wait a few minutes until the status gets updated. (the dspalms and dspcon commands show the status of AIS.)

5. Hitless Rebuild has similar limitations to that of a switchcc and full rebuild:

On IGX nodes, there is a four second continuity break. (Same as in a switchcc.)
There might be brief communication breaks with other nodes in the network. This is logged in the node's event log. There is no traffic loss or trunk failures. (This is similar to a switchcc and depends highly on the network and number of connections.)
If a hitless rebuild occurs during a node rebuild, the hitless event may not always be logged in the event log.
If a hitless rebuild occurs before getting the hitless threshold from BRAM, the software assumes that "Max Htls Rebuild Count" in cnfnodeparm is set to 100, and that "Enable Degraded Mode" also in cnfnodeparm is set to False. In other words, the node performs a full rebuild if 100 hitless rebuilds occurs.
Some line/trunk cards that are in the standby state may reset during a Hitless Rebuild.
The statistics that are collected by Cisco Wan Manager are not maintained across a rebuild.
Some statistics are reenabled automatically. These include:

Auto Statistics
Summary Statistics
Real Time Statistics
All other statistics have to be re-enabled for collection after a hitless rebuild takes place. These mainly include the user statistics.

6. UVM cards in Y-redundancy mismatch if one is burned with Idle Code Suppression Firmware and the other is not.

When installing/burning Idle Code Suppression Firmware on UVM pairs, the Y-redundancy must be removed, firmware in both UVM cards burned, and then the Y-redundancy can be restored.

7. Mismatch is reported when replacing a BXM card with another BXM card that has a different Port Group, even though both BXM cards have the identical channel number.

8. Care must be taken when changing the Deroute Delay parameter, which is controlled by the cnftrk command. This defaults to zero, but if set to anything but zero, connection rerouting, due to a trunk failure, is delayed as provided by the parameter.

9. To provide ABR service on a connection, set up an ABRSTD connection, enable VSVD and enable FCES to allow RM cells to be passed to and from customer equipment. The MCR for such ABRSTD connection can be set at any user-desired value.

When the network is experiencing congestion, all the affected ABRSTD connections, regardless of the services (ABR or UBR) they are carrying, are all throttled back at the VSVD points at the network edge. During network congestion, connections carrying UBR services are virtually stopped (to a through-put of mere 6 cps) while connections carrying ABR services can send at a much higher, user desired MCR. This option would avoid the situation where UBR service gains an unfair advantage over ABR service while sharing the same CoS queue.

10. Reconfiguring the trunk parameter may cause the connection to be rerouted if the changed bandwidth load is smaller than what was used by the connections that use the trunk.

11. The BXM and UXM channel stat-level feature gives these cards the capability of collecting more than 4 statistics per connection. However, it is the controller card's limitations, available memory and performance, that indicates how many statistics can actually be collected from the cards and then reported to the Cisco Wan Manager (CWM).

The BCC-3-64 can collect at most three interval statistics per connection when there are 16,000 AutoRoute connections configured on the node. (Interval statistics are those statistics that are reported to the CWM. They are often referred to as TFTP statistics.)

You can collect approximately 48,000 statistics (3 x 16,000) on the BCC-3-64. This is approximate because there are many variables that affect this value such as: are peaks enabled, how many buckets are collected, are all connection of the same type, are trunk, line, or port enabled, and so on

With this approximation of 48,000 statistics on the BCC-3-64, this then means that, as a rough estimate, you could enable 32 stats on 1,500 connections, 48 stats on 1,000 connections or 9 stats on 5,000 connections, and so on The approximation formula being:

max_stats_per_connection = 48,000/number_of_connections

12. The transmit rate on an IGX IMA trunk can be altered at the local node without any trunk outage. It is possible that the transmit rates are different at the two ends of an IMA trunk. After this trunk is deleted, it cannot be added back unless the transmit rates are the same.

Limitations for Release 9.1

1. The maximum number of VC PARMs supported:

2,999 for BCC 3-64 (CSCdj48589)
1999 for NPM-64B
254 for NPM-32 or NPM-64

In other words, one less than the stated maximum value.

VC PARMs are Virtual Circuit Parameters combinations/sets. One set of VC Parameters is used for each unique Virtual Circuit that has been provisioned. Identically provisioned VCs (exclusive of endpoints) use the same set of parameters.

Limitations for Release 8

1. If LMI/ILMI is provided by the BCC:

The maximum possible number of ports on the BPX 8600 that can be configured with LMI/ILMI enabled is 52. However, each BPX supports up to a total of 16 feeder trunks and each feeder trunk has LMI enabled. That is, if a BPX 8600 is configured with only two feeder trunks, then only (52 - 2) = 50 ports can have LMI/ILMI enabled.

If LMI/ILMI is provided by the BXM firmware:

There is no limitation on the number of ports that can have LMI/ILMI enabled.
When running ILMI on the BXM, ILMI version 3.1 WITHOUT address registration is supported.

2. Virtual Path Connections with cells whose VCI values are above 4095 are transmitted correctly only if the path is exclusively through BXM trunks and terminates at BXM ports.

3. The feature of CIR=0 for Frame Relay connections is not supported for connections terminating between FRM cards in IGX nodes and FRSM cards in an MGX 8220 shelf.

4. SVC Voice Connections are derouted after decreasing the allocated bandwidth (increasing Statistic Reserve). It is the design intent that increasing the statistical reserve causes SVC conns to be derouted and not be rerouted.(See bug CSCst92308).

5. For the loadrev operation, it is important that the Cisco Wan Manager/TFTP buffers are maintained at their default size.

6. Due to a hardware limitation, the BNI trunk sends 13 to 15 percent more traffic than what it is configured for when the trunk is configured for less speed (cps) than the maximum port speed. This is especially important when the BNI trunk is connected to IMATM pairs, which carry less than T3 bandwidth.

7. When using the shift/no-shift feature on a BPX 8600 node's port card, controlled via the cnfport command, the other end of the connection must have the same setting. Otherwise, there is a loss of continuity.

8. The external ABR segment control loop on ForeSight (ABRFST) is an option at the User Interface. It is supported by UXM-E/BXM-E (enhanced versions), but is not supported by UXM/BXM hardware. The user should not enable this option on ForeSight connections (CSCdi92451). In any case, there is no coupling between the loops.

9. The interface between a BXM feeder trunk and an MGX 8220 feeder is always considered to be an NNI interface (CSCdj16808).

10. When adding more than 4000 connections on a BPX node, the VC polling rate must be changed to a higher interval, to accommodate the additional time needed to poll for the statistics for each VC. The cnfsysparm command, parameter 24 must be changed according to the following:

0 to 3999 connections	Polling Rate: 5 Minutes (or higher)
4000 to 7999 connections	Polling Rate: 10 Minutes (or higher)
> 8000 connections	Polling Rate: 15 Minutes

11. Because the detailed card error event log is not retained within BRAM, this information is lost should a processor rebuild occur. Therefore, when issuing a dspcderrs command on a particular slot, the display does not show the detailed card error information should rebuild event occur. This functionality has not been modified from previous releases.

12. When a physical-layer failure (for example, LOS) is detected on the BXM, a Major Alarm is generated, and any connection routed over that port is downed (Fail state). The software sends a command to the remote end of the connection to generate AIS in the egress direction. (CSCdj30543).

Impact:

Since the connection is in a failed state, AIS is generated in the upstream direction (in addition to the downstream direction). Although this does conform to the letter of the I.610 standard, this is not necessarily what a user would expect to see, because it interferes with the RDI response from the end-to-end connection termination point. (A fault in the downstream direction causes a fault in the upstream direction.)

Reason for the current implementation:

The BNI cannot generate AIS. If there is a fault at a BNI trunk, the current mechanism is to cause AIS to be generated by the BXM port by downing the connection. Since the BXM can generate only OAM cells from the RCMP, and the RCMP is in the ingress path, the cells must be backward routed to the egress (egress QE). Also, since end-to-end OAM cells are required, the ingress QE must be configured to drop ALL cells in the ingress path. This creates a break in continuity in the opposite direction, and AIS cells must also be generated at the other end of the same connection, in the upstream direction of the original fault.

13. There are problems in the fallback mechanism that can cause database corruption. If fallback is performed immediately after upgrading, the Stby_Info revision fields are not yet filled in on the new active CC. They don't get filled in until there is an upcard response from the new locked CC. This causes restart instead of a switchcc. If the locked CC is reset, then fallback immediately, a restart occurs instead of a switchcc (CSCdj30811).

14. In order to test/simulate the Y-redundant switchover of ASI T3 or E3 pairs, the resetcd command must be used, or by pulling out the active card. It is not be correctly simulated by doing a dncd (down card) on the active card. Using dncd causes cell discards. (CSCdj08923).

15. UBR traffic gains an advantage over ABR traffic when UBR and ABR PVC's are combined on the same network. This is because UBR and ABR PVC's share the same Qbin (Class of Service Queue) on the BXM card. ABR PVC's use a flow control mechanism, VSVD, which ensures that traffic sources slow down when the Qbin usage exceeds the EFCI threshold. However, UBR PVC's do not have this throttling mechanism. Therefore, ABR is throttled back, whereas UBR is not. This unfair advantage is not considered a problem, since the decision to share a Qbin for ABR and UBR traffic was intentional. Any best-effort service that one would route over UBR can be routed over ABR(VSVD), with the additional benefit of protecting resources in the network. If UBR and ABR PVC's are required then:

Option 1—Consider adding all best-effort PVC's as UBR or

Option 2—Isolate the ABR and UBR paths by using cnfpref command to ensure that ABR and UBR PVC's do not share the same queues.

Option 3—To provide UBR service on a connection, rather than setting up a UBR connection, do the following:

Step 1 Set up an ABRSTD connection

Step 2 Enable VSVD

Step 3 Disable FCES (Flow Control External Segment)

Step 4 Disable DEFAULT EXTENDED PARAMETERS

Step 5 Choose policing option "4" to allow access as UBR.1 (PCR policing only). This connection has ABR VSVD in the network and allows UBR.1 access. The MCR for such ABRSTD connection may be set at the minimum acceptable value of 6 cells per second (explained later why to do so).

16. Combining Frame-Based Traffic Control (FBTC) and non-FBTC connections within a Class of Service can cause FBTC connections to not receive a fair share of bandwidth. For example, if VBR connections are added at a terminating port, and some of these VBR connections have FBTC enabled while other VBR connections have FBTC disabled, the VBR connections with FBTC disabled may obtain all of the excess bandwidth before the connections with FBTC enabled receive any of the excess bandwidth. The same holds true for ABR or UBR connections. This only is relevant where FBTC and non-FBTC connections share a Qbin, either at a port or at a trunk.

Required Workarounds for Release 9.1

1. When adding a node into an existing network, ensure that its node number is unique prior to actually adding it into the network. Use the rnmnd command, and renumber the individual node while it is still stand-alone. This makes the joining of this node much simpler, and avoids the problem of node renumbering an active network, as described below.

Required Workarounds for Release 8

1. There is a problem with node renumbering. Node renumbering (the rnmnd command) should be executed only during a stable network environment and only if absolutely necessary. A stable network environment would be, for example, one in which no connection was added for the past 30 minutes and no topology change was made in the last hour and there are no alarms or node unreachabilities. Node renumbering must be done only when the network is stable to reduce the possibility of certain temporarily blocked messages during the node renumbering process being delivered to the wrong nodes. This would occur after the completion of the node renumbering process. It is recommended that a node be renumbered prior to being added to the network.

2. The settling time for network-wide updates can take a long time in certain situations, specifically, the settling time for updates due to network-wide topology changes and connections in a large network when a processor switchover occurs. The time is proportional to the number of nodes as well as the number of connections. A general estimate would be 30 seconds per node. During the period of transitions (when the updates are occurring) some network operations such as adding connections might, in some cases, take somewhat longer to complete.

3. When using Cisco Wan Manager, there could be a problem with communicating with a node that just had a processor switchover. The problem is within the SPARCstation itself and its caching of EtherNet addresses. It can be solved by execution the following command on the workstation as the superuser: # arp -d <node_name>

4. Users may not use the command addcon slot.1-24 v to add 24 voice connections to a CVM/UVM at once. Instead, they must separate this activity into two or more commands, so that no more than 16 connections are added at once. This is an issue only for voice connections. Data connections can be added using the "1-24" syntax. This also applies when the CVM/UVM circuit line is an E1, in which case "1-32" would apply (CSCdj14319).

5. When a switchcc is executed on a BPX 8600 configured with two BCC-4 cards and contains a BXM-622 trunk card, there may be a bad clock path problem reported. It is indicated as a Minor Alarm—bad clock path. This is a transitory problem, although the alarm indication persists. To clear this, execute the clrclkalm command.

Additional Documentation

In order 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 command dspbpnv can be issued to verify if the node had 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 command cnfbpnv can be used to configure the backplane, if backplane is so enabled.

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

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

It cannot be 0.
It must be a multiple of the polling interval.
It must be a factor of the bucket interval.
It can be the same as the bucket interval.

Compatibility Notes

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

This release runs with Release 4.1.0x or 5.0.0x of the MGX 8220.

Compatibility Matrix

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.16	5.0.10	4.1.10	4.1.00
ASC Boot	ASC	1.0.03	1.0.01	1.0.03	4.0.04
ASC/2 FW	ASC	5.0.16	5.0.10	4.1.10	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.16	5.0.10	4.1.10	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 Firmware Compatibility

PCB Description	CW2000 Name	Latest F/W	Min F/W
PXM1	PXM-1	1.1.32	1.1.32
PXM1-2-T3E3	PXM1-2T3E3	1.1.32	1.1.32
PXM1-4-155	PXM1-4OC3	1.1.32	1.1.32
PXM1-1-622	PXM1-OC12	1.1.32	1.1.32
MGX-SRM-3T3/B	SRM-3T3	n/a	n/a
MGX-SRM-3T3/C	SRM-3T3	n/a	n/a
AX-CESM-8E1	CESM-8E1	10.0.21	10.0.21
AX-CESM-8T1	CESM-8T1	10.0.21	10.0.21
MGX-AUSM-8E1/B	AUSMB-8E1	10.0.21	10.0.21
MGX-AUSM-8T1/B	AUSMB-8T1	10.0.21	10.0.21
MGX-CESM-T3	CESM-T3	10.0.21	10.0.21
MGX-CESM-E3	CESM-E3	10.0.21	10.0.21
AX-FRSM-8E1/E1-C	FRSM-8E1	10.0.21	10.0.21
AX-FRSM-8T1/T1-C	FRSM-8T1	10.0.21	10.0.21
MGX-FRSM-HS2	FRSM-HS2	10.0.22	10.0.22
MGX-FRSM-2CT3	FRSM-2CT3	10.0.22	10.0.22
MGX-FRSM-2T3E3	FRSM-2T3	10.0.22	10.0.22
MGX-FRSM-2T3E3	FRSM-2E3	10.0.22	10.0.22
MGX-FRSM-HS1/B	FRSM-HS1/B	10.0.21	10.0.21
MGX-VISM-8T1	VISM-8T1	2.0.(1)	1.5.05
MGX-VISM-8E1	VISM-8E1	2.0.(1)	1.5.05
MGX-RPM-128M/B	RPM	12.1(5.3)T_XT	12.1(5.3)T_XT
MGX-RPM-PR	RPM	12.1(5.3)T_XT	12.1(5.3)T_XT
CWM		10.4	10.4

MGX 8230 1.1 Firmware Compatibility
MGX 8250 1.1 Firmware Compatibility

PCB Description	CW2000 Name	Latest F/W	Min F/W
PXM1	PXM-1	1.1.32	1.1.32
PXM1-2-T3E3	PXM1-2T3E3	1.1.32	1.1.32
PXM1-4-155	PXM1-4OC3	1.1.32	1.1.32
PXM1-1-622	PXM1-OC12	1.1.32	1.1.32
MGX-SRM-3T3/C	SRM-3T3	n/a	n/a
AX-CESM-8E1	CESM-8E1	10.0.21	10.0.21
AX-CESM-8T1	CESM-8T1	10.0.21	10.0.21
MGX-AUSM-8E1/B	AUSMB-8E1	10.0.21	10.0.21
MGX-AUSM-8T1/B	AUSMB-8T1	10.0.21	10.0.21
MGX-CESM-T3	CESM-T3	10.0.21	10.0.21
MGX-CESM-E3	CESM-E3	10.0.21	10.0.21
AX-FRSM-8E1/E1-C	FRSM-8E1	10.0.21	10.0.21
AX-FRSM-8T1/T1-C	FRSM-8T1	10.0.21	10.0.21
MGX-FRSM-HS2	FRSM-HS2	10.0.22	10.0.22
MGX-FRSM-2CT3	FRSM-2CT3	10.0.22	10.0.22
MGX-FRSM-2T3E3	FRSM-2T3	10.0.22	10.0.22
MGX-FRSM-2T3E3	FRSM-2E3	10.0.22	10.0.22
MGX-FRSM-HS1/B	FRSM-HS1/B	10.0.21	10.0.21
MGX-VISM-8T1	VISM-8T1	2.0.(1)	1.5.05
MGX-VISM-8E1	VISM-8E1	2.0.(1)	1.5.05
MGX-RPM-128M/B	RPM	12.1(5.3)T_XT	12.1(5.3)T_XT
MGX-RPM-PR	RPM	12.1(5.3)T_XT	12.1(5.3)T_XT
CWM		10.4	10.4

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

Note For the VSI/MPLS feature, the UXM firmware needs to be upgraded to revision ACC or later. The upgrade procedure has changed.

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 1 Execute a graceful upgrade to Release 9.3.24.

Step 2 Upgrade the UXM boot code to boot 8.

Step 3 Upgrade the run-time UXM firmware to revision ABJ or greater.

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 been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACC:

Step 1 Execute a graceful upgrade to Release 9.3.24.

Step 2 Upgrade the run-time UXM firmware to revision ACC or later.

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	NEK	NEK
IGX-NTM (B)	NTM	NTM	F	NFK	NFK
IGX-UXM	UXM	UXM	B	ABJ	ABJ
IGX-UXM	UXM	UXM	C	ACE	ACB
IGX-UXME	UXM	UXM	B	ABJ	ABJ
IGX-UXME	UXM	UXM	C	ACE	ACB
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-UVM	UVM	UVM	D	DDF	DDF
IGX-UVM	UVM	UVM	E	DEF	DEE

Note IGX-UVM model E is a super set of models A, B, and C firmware. A, B, and C are obsolete and should not be used.

MGX 8220 5.0 Hardware Compatibility

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

BPX 8600 Hardware Compatibility

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-21800-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	H	F	*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 in Release 9.3.25

The following table lists the known anomalies in SWSW Release 9.3.25.

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 spchstats. 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: Seconds V.25 Modem On Seconds DSI Enabled Seconds Off-Hook 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 Workaround: None. Further Details: The display attempts to display the port on the via trunk before it is properly set.
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.
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. or, 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. or, do a full rebuild on the IGX switch. Note: 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. or, on the CWM, stop and then restart the CWM core - Note this causes the CWM to resync with all nodes in the network.
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.
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. Workaround: None
CSCdx33468	Symptom: dspcons shows all connections but dspcon shows "connection does not exit" Conditions: The network has the following software configuration: SWSW is 9.3.10 and 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.
CSCdx92352	Symptom: TFTP interval statistics peak values are smaller or larger than expected. Conditions: This problem occurs when a user attempts to change the peak interval for statistics that already have peaks enabled, while leaving the file and bucket interval unchanged. For example, if they started with a TFTP interval stat with a 5 minute bucket, a 60 minute file and a peak interval of say 60 seconds. And they then left all of the other values the same, but changed the peak interval to say 120 seconds, then the operation would "succeed", the high level displays would say that the peak interval is 120 seconds, but the individual statistics would still be doing 60 second peaks. Workaround: When changing the peak interval, first delete all of the stats then change the peak interval and send the new enable request.
CSCdy50994	Symptom: Software errors 30 and 923 are logged after issuing the command [cnftrkict] on an NTM card that does not have a trunk up on it (i.e. the NTM card is in the Standby state). Conditions: This problem only happens when the command is executed on a NTM slot that does not have its trunk upped yet. Workaround: None. This is basically caused by incorrectly running the command. There is no reason to invoke [cnftrkict] on an NTM slot that is not currently upped as a trunk.
CSCdy81617	Symptom: Node in Degraded mode, all other nodes in network unreachable. swerr 47 in swlog, and POLL BUS failure on active BCC bus. Conditions: No special conditions known. Workaround: Switchcc, clears degraded mode. Bus remains failed even with diagbus, requires replacement
CSCdy89690	Symptom: BPX does not log feeder alarm change events when the LMI protocol runs on the BXM. Conditions: The problem only happen when BXM runs the LMI protocol. Workaround: None.
CSCdy89732	Symptom: 1. NPM switch over to standby NPM. 2. Event log shows restart reason is a Watchdog Timeout. 3. Abort profile on the standby NPM (dspprf a s t) shows a date and time matching the date and time of the Watchdog Timeout event. 4. The standby error log (abort log in 9.3) is empty. Conditions: IGX with an abort on the active NPM switches over to the standby NPM. Workaround: Use the "dmstby" to collect the software log from BRAM on the standby NPM. The software log is from address 0x1010 to 0x19C0.
CSCdz00821	Symptom: delshelf is allowed to proceed when there are active VSI partitions and VSI connections on the feeder trunk. Conditions: The problem only happens when there are only VSI but no auto route connections on the feeder trunks. Workaround: None.

Problems Fixed in Release 9.3.25

The following table lists the fixed problem and brief description in Release 9.3.25.

Bug ID	Description
CSCdx08838	IGX reports PRI Loss (CLOCK) when deleting line clock source

Problems Fixed in Release 9.3.24

The following table lists the problems that are fixed in Release 9.3.24.

Bug ID	Description
CSCdk48068	Unable to copy UVM FW DCA, DDA & DEC over trunks with getfwrev
CSCdk48180	sar_free_pdu() should not be called more times than aal5 sar buffers
CSCdm12139	Packet_line table not updating Bursty_a_load, Bursty_b_load
CSCdm65231	Unable to add over 300 Frame Relay ports without changing Polling Interval
CSCdr25253	No AIS-P alarm reported when Path AIS is sent from upstream equipment
CSCdr51769	dspqbinstats show negative values.
CSCdr55450	flood of swlog 992 kills ILMI task on BCC making all AXISs unreachable
CSCdr66407	Crash during download process
CSCdr91680	1000003 abort in SNMP during SVC deletes
CSCds15146	dspclksrcs does not display correctly when cancelled and more screens available
CSCds41674	dsppwr shows incorrect information
CSCds82820	SWSW err 55 on all nodes running Pre 9.3.1x after Full rebuild/Nongraceful upg
CSCds84776	APS 1:1 shows SignalDegrade BER message on bpx nodes
CSCdt01430	NWIP traffic is not delivered, other CC traffic is delivered as expected
CSCdt12153	CLI allows ECN threshold to be greater than VCQ depth
CSCdt14450	524 on any rebuild or connection conditioning due to LCN conflict.
CSCdt24344	Stby Bus Errors was being counted after the card BCC-4V was removed
CSCdt24454	A Minor Alarm isnt flagged on your screen for a card failure
CSCdt29906	Abort 1000003 (1m3) and 3000000 (3m) when ILMI running on UXM
CSCdt31369	Terminated tstber, swerr 55
CSCdt35981	UXM-OC3 card shows Active-F, dspcd shows PLN Loopback Test Intermittent
CSCdt38696	ILMI is not enabled on URM, and can cause swerr 110, after upcd on URM
CSCdt39873	Port stats incorrect when secondary card of yred pair active and LMI/ILMI enb.
CSCdt42261	SF/SD shown on incorrect line
CSCdt49018	Node re-numbering from 39 causes IGX aborts and comm. break
CSCdt58349	1m3 abort or 516 if TFTP upload or download
CSCdt61092	loop clock parameter not displayed correctly in cnfln and dsplncnf
CSCdt66348	After adding VBR VP Tunneling conn IGX logs multiple 1000003 aborts
CSCdt93721	cnftrk and dsptrk screens overwrites for IMA trunks
CSCdt96187	Channel configuration not sent to Stby yred BXM after Full rebuild
CSCdu00116	Invalid Object ID/Length sent for Fastpad Port Object Robust Messages
CSCdu05864	swerr 9000 in flex_hitless test while hitless rebuild NPM in sw134
CSCdu20330	BNI fdr con cnt/LU incr w/ every full/hitless rebuild cause 319 + more
CSCdu20972	Stop Sending Router Object Robust message Since it is unsupported in CWM

Problems Fixed in Release 9.3.20

Following is the list of fixed problems in the 9.3.20 Switch Software release. Included with each is a brief discussion of the problem.

Bug ID	Description
CSCdr02036	Adjacency infrastructure needs mods to support tunnels on gsr
CSCdr55450	flood of swlog 992 kills ILMI task on BCC making all AXISs unreachable
CSCdr82206	NPM in slot 2 may not be able to communicate with UXM
CSCds16795	Incorrect programming of ingress/egress MCR on a terminating UXM trk
CSCds55132	dspcd command for enhanced BXM/UXM cards
CSCds59761	dspcd command for enhanced BXM/UXM cards
CSCds59779	SWSW did not send a deactivate message when an active BXM card is removed
CSCds61240	Connections added on BPX displays Unknown Response(17)
CSCds62060	The new dspcurclk display shows extreme clock deviation
CSCds69977	Unable to modify atmportqdepth for a port on BXM card using PortProxy
CSCds71475	swerr 9083 & -ve value set for stats reserve on UXM while using SNMP
CSCds74027	rsrc screen update does not refresh stats reserve for an input of 0
CSCds75283	CWM cannot ping BPX and its attaching feeder nodes
CSCds75929	dspctrlrs output in BPX does not wraparound and the output is truncate
CSCds80136	LMI/ILMI stats not updated on Y-red swithover
CSCds82033	dspnebdisc does not accept command line inputs and screen title is inc
CSCdt01430	NWIP traffic is not delivered, other CC traffic is delivered as expect
CSCdt07043	BPX feeder endpoint needs to display Non-Segment always
CSCdt11920	swerr 1418 while trying to up a trunk
CSCdt14450	524 on any rebuild or connection conditioning due to LCN conflict
CSCdt22351	Memory leak in TFTP FW/SW upload and statistics enable
CSCdt24951	TFTP stat file not created but stats enabled for several hours
CSCdt29906	Abort 1000003 (1m3) and 3000000 (3m) when ILMI running on UXM
CSCdt31011	Cannot delete con loopback, 750, loopback survives delcon/addcon
CSCdt31282	TRkutl on feeder trunks shows all the conns to be Frame relay type.

Problems Fixed in Release 9.3.11

Following is the list of fixed problems from Switch Software Release 9.3.11. Included with each is a brief discussion of the problem.

Bug ID	Description
CSCdp50091	Data_channel table is not updating with Release 9.1.15 Switch Software
CSCdr82206	NPM in slot 2 may not communicate with UXM
CSCdm42912	SNMPProxyAgent fails on SET of PrefRoute with 10 hops (switch rejects)
CSCdm60699	Async updates are sent incorrectly when VCQueue fills up.
CSCdp53419	UXM trunk LCN verification is not performed on card configuration
CSCdr78404	UVM has excessive delay for g729 conn which route on uxme 2 Mbps virtual trunk
CSCds11473	MPLS LER cannot recover from addcon 0/32. xtag intf stays non-operational
CSCds36582	BCC clock failure is not processed by SWSW during switchcc
CSCds52706	dspports does not allow user to see the port information
CSCds58629	Re-Sync with master ctrlr needed when stby->act resync fails and stby is active
CSCds59259	BXM to BXME upgrade with APS 1 1 enabled can cause channel management issues
CSCdm07690	Problems with memory calculations for standby queue flushing can lead to 586s
CSCdr74919	BNNI lights do not go out after a dntrk
CSCdr95419	delapsln executes without confirmation
CSCds08777	Incorrect card/image accepted in tftp request. Missing CMI_FWDL_PREFIX
CSCds16812	Trunk Channel programmed with wrong values on BXM, UXM.
CSCds39545	dspfdr does not display the VSI channels correctly.
CSCds40327	dsptrkstats - VI: CLP=0 stats missing shown as CLP1, VI: CLP=1 stats duplicate
CSCds40501	Prefix modifications
CSCds41291	ddb_bus_stat_b2r_map() dereferences NULL ptr when get_nvc_ptr() fails
CSCds41299	is_only_vt dereferences NULL pointer if get_lccb() fails
CSCds41303	sv3_ck_xmit() dereferences NULL pointer if pio_deque_first() returns NULL
CSCds41307	svr_revision_msg() dereferences NULL bufptr for Free_mem
CSCds41476	DDB_BUS_STAT may not be written to BRAM during clrcnf
CSCds42377	Prefix warnings. Dereferencing NULL pointer in dspqbinstats.c
CSCds43387	Software error 1128 on executing dspbuses when standby bus is failed
CSCds43641	Block addition of VPC con with VPI=0 if a VSI controller is added to slot.port
CSCds44377	Prefix checkin
CSCds44972	tst_con_cdt() can use uninitialized cdtype if index1(slot) parm is less than 0
CSCds45012	max_st_errors() can use uninit log_cd var when map_logline() fails
CSCds45559	Prefix bug
CSCds45822	Software error 52 appears when runrev command entered
CSCds47570	Modify the incorrect SCR value range (7..1412832) to (6..1412832).
CSCds49393	prefix: ask_continu.c and dspprfhist.c in 93x
CSCds50411	delyred executes without confirmation
CSCds51603	cnftrafficgen is not supported
CSCds52888	Prefix fixes IB93x BPX
CSCds53553	Software error 922 logs in Release 9.3.10
CSCds55573	set_trk_add() and sum_errors() can deref NULL ptr if ltrk is 0 (very unlikely)
CSCds55599	Prefix error with init_ls_db(). Theoretically possible to use uninit vars
CSCds56558	Unable to add cnfchfax command in jobs
CSCds57700	Assorted IGX PREfix Errors
CSCds59745	Prefix warnings
CSCdr63174	MPLS traffic does not change the route after disabling qbin
CSCdr98254	BPX does not reject IGX image when downloading software with TFTP
CSCds33676	cnfvsiif command on a line with no active port gives misleading error
CSCds36322	Wrong warning message - Channel(s) used for LMI and ILMI when addcon
CSCds43122	Prefix for IB93x
CSCds44335	Prefix: Uninitialized memory slot2 at fail_card.c(249) and av_card.c(565)
CSCds44528	Prefix error
CSCds48062	Assorted prefix errors
CSCds48484	Prefix warning in sar_cmd_utlt.c
CSCds59670	Implement auto screen refresh for the commands dspctrlrs and dsprsrc
CSCds43072	New debug command failbus to simulate bus clock failure

Problems Fixed in Release 9.3.10

Following is the list of fixed problems from Switch Software Release 9.3.10. Included with each is a brief discussion of the problem.

Bug ID	Description
CSCdk19709	BPX may sync a neighbor test in error and report a suspected BCC failure
CSCdm29466	Cannot addtrk on the VSI network because of VPC conid mismatch
CSCdp73606	Port LED remains on when line is downed on UXM.
CSCdr32235	cnfportstats/dspportstathist/dspstrec display all port statistics (including invalid)
CSCdr43694	Events Not Explicitly Handled In Many States of Cm_ST
CSCdr48340	dspnw on a nw with IMA virtual trunks causes software error 1423 or 1M3
CSCdr53164	Incorrect error message when trying to configure VPI range to used ones
CSCdr53669	SLT:ILMI is not disabled after changing virtual trunk to line port.
CSCdr68507	dsplog shows wrong VPI/VCI when port loopback deleted
CSCdr70502	Problems with dspsvmsg user command due to revup and new object types
CSCdr71705	When add/deleting remote local loopback, five-part address is shown
CSCdr71781	Auto Memory Reserved Is Not set to Zero (software error 3000) after upln on BXM-E
CSCdr72296	snmp walk on shelfslotinfotable causes software error 26 when UXM is missing a back card
CSCdr73183	111 when 23 ifcs (trk/prt) on a BXM slot, 23+ causes trunk/port statistic loss
CSCdr73442	Deleting a simulated AAL5 feeder causes 1M3 abort and software errors 513, 589, and 502
CSCdr73595	BPX does not clear the last user request after SF switch
CSCdr74841	Display Routing Table Contents does not work
CSCdr75723	Software error 938 PNA_SEND_ERR when LAN default gateway is set to 0
CSCdr76182	Port speed of E1-IMA port with non-cont. IMA links is calculated incorrectly.
CSCdr76451	cnfport: ILMI on card and neighbor discovery parameters handling in Syntax/Job mode
CSCdr76988	Rounding problem in calculating UBU on dspbusbw
CSCdr78202	Software error 1120 logged during upgrade from 9.3.1T to 9.3.1V
CSCdr78391	Software error 3074 when upgrading from 931T to 931V
CSCdr80522	Investigate user commands included HIPRI login for problem caused by Pause_proc
CSCdr80662	Some connection parameters are reset to default on rebuild/switchcc
CSCdr81947	dspselftst stopped working due to fragmented dynamic memory
CSCdr82470	Port loopback for the local slave end of a daxcon fails
CSCdr85197	The random() function is deterministic
CSCdr86188	AIS generate bit set for slave end of ATM daxcon with line in LOS
CSCdr86717	Mismatched back cards are allowed in a Y-red configuration
CSCdr91284	Two software errors 997s are logged after addtrk <vtrk>
CSCdr92045	Communication failure on trunks creates swlog 1417
CSCdr93280	Cannot modify PVC max BW and cannot give VSI bw>0 if IMA port in alarm
CSCdr95576	Software error 327 with switchcc and failed connections
CSCdr95788	Enhancement for signalling Qbin support
CSCdr96026	Incorrect default Discard Threshold (1 cell) set for VSI Qbins on OC-3 BXM port
CSCdr96513	The first interface upped on BXM/UXM has incorrect max discard threshold
CSCds01587	Switch sending cells rx/tx statistics as 0 to CWM
CSCds02627	cnfqbin cannot use the default discard threshold
CSCds02931	ILMI interval val statistics not collected
CSCds03275	No trunk statistics are collected for the last slot of IGX which is caused by the fix for CSCdm04491
CSCds05668	Node went into degraded mode after upgrading from 931Y to 931b
CSCds07761	SLT:SWERR103 UBU allocation errors

Problems Fixed in Release 9.3.05

Following is the list of fixed problems from Switch Software Release 9.3.05. Included with each is a brief discussion of the problem.

Bug ID	Description
CSCdj14920	Unable to use the clrcnf command on a BPX node whose number is > 63.
CSCdk03916	Trunk information is inconsistent
CSCdk22052	Switchcc event logged under trapd.log when the command is cancelled
CSCdk48816	No Alarming on UAS
CSCdk55887	The dspport command is moved from user-level 6 to user-level 2 in Release 8.1.
CSCdk91790	Eliminate UVMs modem polling to save system idle time.
CSCdm04491	Switch software error 921 flooding
CSCdm10213	After an upgrade or a switchcc command in 9.1, extra connections may appear.
CSCdm13222	586s occured on deletion of large number of connections
CSCdm13655	VC bandwidth parameter is not reused (initializes differently during upgrade vs prov).
CSCdm26083	dsptrkbob causes swerr 30 and 923 when performed on sec yred card
CSCdm31518	Active CC failure (EEPROM, SAR) and standby unlock or reseat causes rebuild
CSCdm46032	SNMP identifies ALM/A line as ATM trunk
CSCdm68968	VC-Q depth setting at default value, Conn Mgr, IGX, routing and feeder node
CSCdm87788	Unable to add con with max rate on BXM-T3 port with direct mapping
CSCdp15350	SNMP GET-NEXT does not work for frLportStatTable
CSCdp20486	UXM IMA physical line alarms are not sent to SV+.
CSCdp25034	TOPO_HP_UPDATE NETW messages with 0 trunks causes a node to be removed
CSCdp34687	Node experiences repeated commbreak, commbreak cleared events
CSCdp41410	Modem Silence duration can be set to a maximum of only 5.1 seconds
CSCdp47053	ALM/B y-red does not work if you upgrade from 8.5.09->9.1.15->9.2.23
CSCdp49951	BPX hanging up with TUNL task using up to 60% CPU RT
CSCdp52802	UVM ports do not pass data due to stuck CCS Conditioning
CSCdp55388	dspchuse shows wrong number for max PVC configured.
CSCdp59960	UVM do not send yellow-alarm to PBX when it receives a yellow-alarm from P
CSCdp73065	Background test problems. Background test uses VPI in the VSI range.
CSCdp83902	UVM line pass through does not work on the second physical line on UVM.
CSCdp90130	cnfrsrc shows more bandwidth than physical max for feeder.
CSCdp98760	swerr 923 (invalid ltrunk number) after adding maximum virtual trunks on
CSCdp98970	A virtual trunk session times-out on a particular page when it is running dsprts.
CSCdr00360	The tstdelay command cannot run while card is initializing.
CSCdr02297	A conflict occurs between VPI used for feeder channels and VSI.
CSCdr06280	Conditional update should not be integrated for a trunk between T1 & E1
CSCdr08084	62 message not send on addyred if the secondary card is running selftest
CSCdr08430	Non-TS queue size is not saved in BRAM; also strange queue size behavior occurs.
CSCdr09440	ASI Qbin config lost when programming 2ndary card in Y-Red set
CSCdr10473	Switch software error 1012 (BAD_RS_NCHANS) occurs after a hitless rebuild.
CSCdr10575	Conid mismatch occurs after a hitless rebuild (software error 331.)
CSCdr11698	TS cell discards on virtual trunks with overbooked Frame Relay traffic.
CSCdr11823	BCC tstber channel could use VPI that is in the VSI range.
CSCdr12300	Switch MIB is inconsistent with the CLI.
CSCdr14489	A memory leak occurs in r92_db_cln_inf_u2b_map (93->93 upgrades).
CSCdr14544	PNNI VPI.VCI 0.18 is blocked when path 0 is built on BXM.
CSCdr14935	Unable to add UFM UXM connections from the UFM side and there is corruption of Be.
CSCdr15804	Band lu is incorrect. This is probably caused by dncon CoS.
CSCdr15924	Failure to receive proper traps with 2+ CWMs pointing to same network.
CSCdr17056	Provide unknown state for serialPortLeadState.
CSCdr19348	NTS connections get bit errors when Frame Relay bursts fills up the trunk capacity.
CSCdr20925	Connection data stops when it is reverted to primary in Y-red.
CSCdr21164	Software error 265 occurs on rewrite_bram following a graceful upgrade from Release 9.2
CSCdr21739	Node hangs up and loses access after deleting a trunk.
CSCdr22568	The ILMI disable command is not sent to BXM firmware when ILMI is disabled on a port.
CSCdr23303	Prtphyslnerrs, prtyred, and prtcdred cannot be included in a job.
CSCdr23432	The switch aborts when the cnfport command is issued.
CSCdr25318	The UFMU port reports an active state when the back card is missing.
CSCdr26582	The delctrlr and addctrlr commands used in quick succession will cause BXM firmware pr.
CSCdr26613	When an active APS line has YEL, the trunk fails.
CSCdr27853	The cnfcmparm 9 (reroute timer) should default to 3 seconds.
CSCdr28837	Software error 9098 is logged when upgrading from BXM to BXM-E
CSCdr30234	Available Conids only gets updated on the nodes connected by the trunk.
CSCdr30308	Statistics are not working after a graceful upgrade.
CSCdr32789	Gateway LCNs are not getting updated if the other end is a BXM and the cnfrsrc command is used.
CSCdr32875	int_all_usr_updt, trkchans: kicks of reroute only for trunks attached locally
CSCdr33298	The feeder node becomes unreachable after upgrading from BXM to BXM-E
CSCdr33428	UXM number of channels mismatch after the card rebuilds.
CSCdr33894	Switchapsln when one line in YEL causes a temporary trunk failure.
CSCdr35085	Switchcc cannot be cancelled when updates are pending.
CSCdr36526	SNMP upline is broken.
CSCdr36819	Message 0x53 is not sent when a dntrk/deltrk is done on Egress/Ingress side.
CSCdr37752	Stricter warnings should be displayed when the user does a hard reset on active.
CSCdr38707	SLT: Total VSI minimum bandwidth > 1412830 should not be allowed on BPX.
CSCdr39139	Swlog 3001 observed after overnight jobs.
CSCdr41370	The dspchstat from port counter slowly ramps-up to send rate
CSCdr41814	Prevents AR/VSI conflicts for VPIs used by feeders for LMI/IP-SNMP channels.
CSCdr47101	The load_trun_addr_endpt is not checked for its return value
CSCdr50347	Move second parameter codes used in error() to new files
CSCdr51105	Software error 30 is logged while a UXM is inserted
CSCdr55491	APS 1:1 trunk shows a major alarm after an APS switch and it does not reroute the connection.
CSCdr56249	Transition counter stats (LOS,.) not updated when line goes into alarm
CSCdr58725	In Self-tests, a frequency value of less than 40 seconds causes a consistent resetting of UXM.
CSCdr59630	PB bump statics shows bumping but no latest bumping band info
CSCdr60460	cnfrsrc in bpx restore lcn could not bring back gateway connection
CSCdr60463	Free_mem software error occurs when the number of bumped cons in the same CoS band is equal to 1023.
CSCdr65980	APS alarm status is not being reported correctly.
CSCdr67236	SES has statistics file one hour ahead of the BPX statistics file even if the times are same
CSCdr68446	dsplog shows inconsistent logs for add and deletion of connection local
CSCdr70502	problems with dspsvmsg user command due to revup and new object types
CSCdr70919	Interface shelf major alarm is logged when changing the protocol to run on BXM.
CSCdr74734	The resource partition LCN deadlocks and is unable to delete any ports.
CSCdr75146	Connections will not route due to lack of LCNs as seen in constats command.
CSCdr75723	swerr 938 PNA_SEND_ERR when lan default gateway set to 0

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.

Switch MIB changes of Release 9.3.11, 9.3.20, 9.3.24, 9.3.25

No MIB changes were made since Release 9.3.10.

Switch MIB changes of Release 9.3.10

The following Switch MIB changes were introduced since Release 9.3.05. The changes include Obsolete objects, Modified objects, and New objects:

switchIfTable

Modified objects

switchIfPartiId		

switchIfScTmpltId

frLportCnfTable

Modified objects

frLportCnfEntry

New objects

frLportNeighborDiscovery

frLportNeighborIpAddress

frLportNeighborIfIndex

atmPortTable

Modified objects

atmPortEntry

atmPortType

New objects

atmPortNeighborDiscovery

atmPortNeighborIpAddress

atmPortNeighborIfNam

atmPortStatTable

Modified objects

atmPortStatEntry

New objects

atmPortStatTxQ0CellDrps

atmPortStatTxQ1CellDrps

atmPortStatTxQ2CellDrps

atmPortStatTxQ3CellDrps

atmPortStatTxQ7CellDrps

atmPortStatTxQ8CellDrps

atmPortStatTxQ9CellDrps

atmPortStatTxQ10CellDrps

atmPortStatTxQ11CellDrps

atmPortStatTxQ12CellDrps

atmPortStatTxQ13CellDrps

atmPortStatTxQ14CellDrps

atmPortStatTxQ15CellDrps

atmEndptTable

Modified objects

atmEndptQIR

atmEndptOeQIR

atmEndptRateUpICA

atmEndptPCR

atmEndptOePCR

atmEndptSCR

atmEndptOeSCR

atmEndptMCR

atmEndptOeMCR

atmTrunkStatsTable

Modified objects

atmTrkStatsEntry

New objects

atmTrkStatsTxQ10CellDrps

atmTrkStatsTxQ11CellDrps

atmTrkStatsTxQ12CellDrps

atmTrkStatsTxQ13CellDrps

atmTrkStatsTxQ14CellDrps

atmTrkStatsTxQ15CellDrps

rsrcPartiTable

Modified objects

rsrcPartiId

rsrcPartiPvcMaxBw

rsrcPartiVsiVpiStart

rsrcPartiVsiVpiEnd

rsrcPartiVsiMinBw

rsrcPartiVsiIlmiEnable

rsrcPartiVsiLcnReprogPermit

rsrcPartiPvcTable

Modified objects

rsrcPartiPvcPvcMaxLcns 

rsrcPartiPvcPvcMaxBw 

rsrPartiPvcVpiStart1 

rsrcPartiPvcVpiEnd1 

rsrcPartiPvcVpiStart2 

rsrcPartiPvcVpiEnd2 

rsrcPartiPvcVpiStart3 

rsrcPartiPvcVpiEnd3 

rsrcPartiPvcVpiStart4 

rsrcPartiPvcVpiEnd4

atmQbinTable

Modified objects

atmQbinMinBw

atmQbinTmpltCnfg

vsiCtrlrTable

Modified objects

VsiCtrlrEntry

vsiCtrlrPartiId

vsiCtrlrSlot

vsiCtrlrPort

New objects

vsiCtrlrAdminStatus

vsiCtrlrVpi

vsiCtrlrVciStart

Switch MIB Changes to Release 9.3.05

atmPortTable

New objects

atmPortIlmiResetFlag

atmPortCACReserve

atmPortLportMaxBW

atmPortLportMinVpi

atmPortLportMaxVpi

atmPortMgmtProtoOnCard

Modified objects

atmPortEntry

atmPortMgmtProto

atmPortIlmiAddrReg

atmPortVcShaping

atmPortQueueTable

New objects

atmPortQueueVcShaping

Modified objects

atmPortQueueEntry

atmPortQueueDepth

atmEndptTable

Modified objects

atmEndptVcQSize

switchShelf configuration branch

New objects

shelfCnfgNodeVcSupport

shelfCnfgNodeVcTotal

atmTrunks table

New objects

atmTrkTermUsedPvc

atmTrkViaUsedPvc

atmTrkMgmtProtoOnCard

Modified objects

atmTrkEntry

rsrcPartiTable

New objects

rsrcPartiVsiLcnReprogPermit

Modified objects

rsrcPartiEntry

Obsolete objects

rsrcPartiPvcMaxLcns

rsrcPartiPvcMaxBw 

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

rsrcPartiMaxLcnBatchNumber		

rsrcPartiPvcTable

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

New objects

rsrcPartiPvcEntry

rsrcPartiPvcPvcMaxLcns

rsrcPartiPvcPvcMaxBw

rsrcPartiPvcVpiStart1

rsrcPartiPvcVpiEnd1

rsrcPartiPvcVpiStart2

rsrcPartiPvcVpiEnd2

rsrcPartiPvcVpiStart3

rsrcPartiPvcVpiEnd3

rsrcPartiPvcVpiStart4

rsrcPartiPvcVpiEnd4

serialPortTable

Modified objects

serialPortLeadState

Switch MIB changes to Release 9.3

The following Switch MIB changes were introduced since Release 9.2.31. The changes include Obsolete objects, Modified objects, and New objects:

switchIfTable

This table contains a list of ports and subports, and their interface.

Modified objects

switchIfService

switchIfPhysPort

switchIfScTmpltId

atmPortTable

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

New objects

These new MIB variables support IMA Ports.

atmPortRetainedLinks

atmPortImaProtocolOption

atmPortImaDiffDelay

atmPortImaClockMode

Modified objects

atmPortEntry

Obsolete objects

atmPortSvcChannels

atmPortSvcLcnLow

atmPortSvcLcnHigh

atmPortSvcVpiLow

atmPortSvcVpiHigh

atmPortSvcVciLow

atmPortSvcVciHigh

atmPortSvcQbinBitMap

atmPortSvcQbinSz

atmPortSvcBw

atmPortSvcInUse

atmPortPvcInUse

atmEndptTable

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

Modified objects

atmEndptPolicing

shelfSlotInfoTable

This table provides switch slot information.

New objects

slotCardTopAssemNumber

Modified objects

shelfSlotInfoEntry

slotCardMinBusUBU

ds3LineTable

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

Modified objects

ds3LineAlmType

ds3LineStatsTable 

ds3StatsTable

This table provides a list of DS3 line statistics objects.

New objects

ds3StatsUas

Modified objects

ds3LineStatsEntry

sonetStatsTable

This table provides a list of SONET line statistics objects.

Modified objects

sonetStatsPthBip8s

sonetStatsPthFebeEs

sonetStatsSecBip8Ses

sonetStatsPthUas

sonetStatsPthFarendUas

atmTrunkStatsTable

This table provides a list of ATM trunk statistics object.

Obsolete objects

atmTrkSvcChannels

atmTrkSvcLcnLow

atmTrkSvcLcnHigh

atmTrkSvcVpiLow

atmTrkSvcVpiHigh 

atmTrkSvcVciLow

atmTrkSvcVciHigh

atmTrkSvcQbinBitMap

atmTrkSvcQbinSz

atmTrkSvcBw

atmTrkSvcInUse

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

vsiCtrlrEntry

vsiCtrlrId

vsiCtrlrPartiId

vsiCtrlrIpAddr

vsiCtrlrType

vsiCtrlrSlot

vsiCtrlrPort

Default Values

BPX 8600 Nodes

The default values for BXM and Enhanced-BXM cards are the same.

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:21 GMT 

                           System-Wide Parameters                               

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

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

3  Max Network Delay for 'v' connections (msec).......................   14     

4  Max Network Delay for 'c' connections (msec).......................   27     

5  Max Network Delay for 't' & 'p' connections (msec).................   14     

6  Max Network Delay for 'a' connections (msec).......................   27     

7  Max Network Delay for High Speed Data connections (msec)...........   32     

8  Max Network Delay for CDP-CDP 'v' connections (msec)...............   64     

9  Max Network Delay for CDP-CDP 'c' connections (msec)...............   64     

10 Max Network Delay for CDP-CDP 't' & 'p' connections (msec).........   64     

11 Max Network Delay for CDP-CDP 'a' connections (msec)...............   64     

12 Max Network Delay for CDP-CDP High Speed Data connections (msec)...   64     

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

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

15 Max Local Delay for Interdom CDP-CDP 'v' conns (msec)..............   27     

16 Max Local Delay for Interdom CDP-CDP 'c' conns (msec)..............   27     

17 Max Local Delay for Interdom CDP-CDP 't' & 'p' conns (msec)........   27     

18 Max Local Delay for Interdom CDP-CDP 'a' conns (msec)..............   27     

19 Max Local Delay for Interdom CDP-CDP High Speed Data conns (msec)..   27     

20 Max Local Delay for Interdom High Speed Data conns (msec)..........   28     

21 FastPAD Jitter Buffer Size  (msec).................................   15     

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

23 Enable Connection Deroute Delay feature............................  Yes     

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

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

This Command: cnfsysparm                                                        

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:21 GMT 

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

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

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

4  Comm-Break Test Offset [   10] (D)   19 Gateway ID Timer       [   30] (D)   

5  Network Timeout Period [ 1700] (D)   20 GLCON Alloc Timer      [   30] (D)   

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

42 Enable Feeder Alert    [    N] (Y/N)                                         

43 Reroute on Comm Fail   [    N] (Y/N)                                         

44 Auto Switch on Degrade [    Y] (Y/N)                                         

45 Max Degraded Aborts    [  100] (D)                                           

This Command: cnfnodeparm                                                       

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:22 GMT 

Index Status    Function                                                        

1     Enabled   Automatic TRK Loopback Test on Local/Remote Alarms              

2     Enabled   User Command Logging                                            

3     Enabled   Automatic Card Reset on Hardware Error                          

4     Enabled   Card Error Record Wraparound                                    

5     Disabled  Card Test After Failure                                         

6     Disabled  Download From Remote Cisco StrataView Plus                      

7     Disabled  Logging of conn events in local event log                       

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

9     Disabled  Force Download From a Specific IP address                       

This Command: cnffunc                                                           

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:22 GMT 

Index Status    Function                                                        

1     Disabled  Configuration Save/Restore                                      

2     Enabled   ForeSight                                                       

3     Disabled  Multiple VTs (1 session enabled)                                

4     Disabled  Virtual Trunks                                                  

5     Enabled   ABR standard with VSVD                                          

6     Disabled  Priority Bumping                                                

7     Disabled  Virtual Ports                                                   

This Command: cnfswfunc                                                         

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:22 GMT 

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

Type    Freq   Enable        Inc   Thresh  Timeout   Enable        Inc   Thresh 

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

BCC      1600  Enabled       100      300      800   N/A           100      300 

ASM       300  Disabled      100      300       60   N/A           100      300 

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

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

ASI-E3    900  Enabled       100      300      800   Enabled       100      300 

ASI-T3    900  Enabled       100      300      800   Enabled       100      300 

ASI-155   900  Enabled       100      300      800   Enabled       100      300 

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

BXM      4000  Enabled       100      300     3000   Enabled       100      300 

This Command: cnftstparm                                                        

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:22 GMT 

1  Normalization Interval    [    2] (D)                                        

2  Max Number To Normalize   [    5] (D)                                        

3  Normalization Logging     [   No]                                            

4  Settling Interval         [    4] (D)                                        

5  Minimum Open Space        [ 1000] (D)                                        

6  Normalization Priority    [ Load]                                            

7  Load Sample Period        [    4] (D)                                        

8  Maximum Routing Bundle    [   90] (D)                                        

9  Reroute Timer             [    0] (secs)                                     

10 Reset Timer on Line Fail  [  Yes]                                            

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

12 Down/Up Timer             [30000] (msecs)                                    

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

14 Time between Rrt cycles   [    5] (mins)                                     

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

16 Routing pause timer       [    0] (msecs)                                    

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

18 Send SVC urgent msg       [   No]                                            

19 Max SVC Retry             [    0] (D)                                        

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

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

22 Enable Cost-Based Routing [   No]                                            

23 Enable Route Cache Usage  [   No]                                            

24 Use Delay for Routing     [   No]                                            

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

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

27 Increment between RR grps [  100] (CLU)                                      

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

This Command: cnfcmparm                                                         

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:22 GMT 

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

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

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

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

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

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

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

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

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

10 Crc Block Size (hex)    [    400]                                            

11 Rev Change Wait(dec)    [      0]                                            

12 CCs Switch Wait(dec)    [   1000]                                            

13 Lcl Response TO(msec)   [   5000]                                            

14 Rmt Response TO(msec)   [  20000]                                            

15 FW Dnld Block TO(msec)  [     50]                                            

This Command: cnfdlparm                                                         

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

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

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

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

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

5. UID Privilege Level ... 6                                                    

6. Input Character Echo .. Enabled                                              

7. Screen Update Time .... 10 seconds                                           

This Command: cnfuiparm                                                         

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

1  Priority Bumping Enabled                [  NO]                               

2  Priority Bumping Bundle                 [  50] (D)                           

3  Priority Bumping Bands:                                                      

   Band 1                                  [   2] (D)                           

   Band 2                                  [   4] (D)                           

   Band 3                                  [   6] (D)                           

   Band 4                                  [   8] (D)                           

   Band 5                                  [  10] (D)                           

   Band 6                                  [  12] (D)                           

   Band 7                                  [  14] (D)                           

This Command: cnfbmpparm                                                        

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

Function            Number   Status      Function            Number   Status    

Background Upcard     1      Enabled     Conn Stat Sampling    15     Enabled   

Background Updates    2      Disabled    Neighbor Update Errs  16     Disabled  

Standby Terminal      3      Enabled                                            

Memory Protection     4      Enabled                                            

Comm Break            5      Enabled                                            

Comm Fail Test        6      Enabled                                            

CRC Test              7      Enabled                                            

Bus Fail Detection    8      Enabled                                            

Line Diag             9      Enabled                                            

Clock Restoral        10     Enabled                                            

Cm_Rerouting          11     Enabled                                            

Clock Routing         12     Enabled                                            

Dynamic BW Allocation 13     Enabled                                            

Modem Polling         14     Enabled                                            

This Command: on1                                                               

node	 TN    Cisco           BPX 8620  9.3.24   Jan. 22 2001 09:43 GMT 

Missing Cards: 1 BXM, 1 LM-BXM

   FrontCard    BackCard                    FrontCard    BackCard

   Type    Rev  Type  Rev   Status          Type    Rev  Type  Rev   Status

1  BNI-155 BDR  Empty       Standby      9  Empty                               

2  BNI155E DDL  Empty       Standby      10 Empty reserved for BXM             

3  BNI-T3  CJM  T3-3  FN    Active       11 BNI155E DER  MMF-2 AC    Active

4  BNI-E3  CFM  E3-3  FJ    Active       12 BXM-E3  FLJ  TE3-12BA    Active

5  BXM-T3  FDJ  TE3-12BA    Active       13 BXM-E3  FLJ  Empty       Standby

6  BXM-622 FDJ  SM-2  P02   Active       14 Empty                               

7  BCC-4   H2011LM-2  AD    Active       15 ASM     ABC  Empty       Active

8  BCC-4   HEM  LM-2  AC    Standby     

Last Command: dspcds

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

Function            Number   Status      Function            Number   Status    

Line Stat Sampling    1      Disabled    Robust Alarm Updates  15     Enabled   

Statistical Alarm     2      Enabled     Realtime Counters     16     Enabled   

Job Ready Checker     3      Enabled     LAN Interface         17     Enabled   

Configuration Backup  4      Enabled     Update Standby Stats  18     Enabled   

Standby Update        5      Enabled     Telnet Access         19     Enabled   

Downloader            6      Enabled     Junction ID           20     Enabled   

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

Topo/Stat Updates     8      Enabled     Simulated Fdr Trks    22     Disabled  

Card Statistical Alms 9      Enabled     Deroute Delay         23     Enabled   

Card Stat Sampling    10     Enabled     Auto Renum Fail Recov 24     Enabled   

Address Validation    11     Enabled     Card Simulation Tool  25     Disabled  

ASM Stats Polling     12     Enabled                                            

Port Stat Sampling    13     Enabled                                            

Robust Updates        14     Enabled                                            

This Command: on2                                                               

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

Function            Number   Status                                             

Trace Msg Sent        1      Disabled                                           

Multi-DB Stby Updates 2      Enabled                                            

Trace Conv Msg        3      Disabled                                           

Region memory init    4      Disabled                                           

This Command: on3                                                               

BNI-T3

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:23 GMT 

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

Transmit Rate:         96000               VPC Conns disabled:    --            

Protocol By The Card:  --                  Line framing:          PLCP          

VC Shaping:            --                       coding:           --            

Hdr Type NNI:          --                       recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:                     

Idle code:             7F hex                         length:     0-225 ft.     

Connection Channels:   1771                Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      No            

Routing Cost:          10                  Frame Scramble:        --            

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 3.1                                                     

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK 3.1 Parameters                                                              

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 3.1                                                    

BNI-E3

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK  4.1 Config     E3     [80000 cps]     BNI-E3 slot:  4                      

Transmit Rate:         80000               VPC Conns disabled:    --            

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

VC Shaping:            --                       coding:           --            

Hdr Type NNI:          --                       recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:                     

Idle code:             7F hex                         length:     0-225 ft.     

Connection Channels:   1771                Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      Yes           

Routing Cost:          10                  Frame Scramble:        --            

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 4.1                                                     

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK 4.1 Parameters                                                              

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 4.1                                                    

BNI-155/155E

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:25 GMT 

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

Transmit Rate:         353208              VPC Conns disabled:    --            

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

VC Shaping:            --                       coding:           --            

Hdr Type NNI:          --                       recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:       --            

Idle code:             7F hex                         length:     --            

Connection Channels:   16050               Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      Yes           

Routing Cost:          10                  Frame Scramble:        Yes           

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 11.1                                                    

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:25 GMT 

TRK 11.1 Parameters                                                             

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 11.1                                                   

BXM-T3

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

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

Transmit Rate:         96000               VPC Conns disabled:    No            

Protocol By The Card:  No                  Line framing:          PLCP          

VC Shaping:            No                       coding:           --            

Hdr Type NNI:          Yes                      recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:       --            

Idle code:             7F hex                         length:     0-225 ft.     

Connection Channels:   256                 Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      No            

Routing Cost:          10                  Frame Scramble:        --            

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 5.1                                                     

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK 5.1 Parameters                                                              

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 5.1                                                    

BXM-E3

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:25 GMT 

TRK 12.1 Config     E3     [80000 cps]     BXM slot:     12                     

Transmit Rate:         80000               VPC Conns disabled:    No            

Protocol By The Card:  No                  Line framing:          --            

VC Shaping:            No                       coding:           --            

Hdr Type NNI:          Yes                      recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:       --            

Idle code:             7F hex                         length:     0-225 ft.     

Connection Channels:   256                 Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      Yes           

Routing Cost:          10                  Frame Scramble:        --            

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 12.1                                                    

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:25 GMT 

TRK 12.1 Parameters                                                             

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 12.1                                                   

BXM-155

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

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

Transmit Rate:         353208              VPC Conns disabled:    No            

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

VC Shaping:            No                       coding:           --            

Hdr Type NNI:          Yes                      recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:       --            

Idle code:             7F hex                         length:     --            

Connection Channels:   256                 Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      Yes           

Routing Cost:          10                  Frame Scramble:        Yes           

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 10.1                                                    

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:25 GMT 

TRK 10.1 Parameters                                                             

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 10.1                                                   

BXM-622

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK  6.1 Config     OC12   [1412679cps]    BXM slot:     6                      

Transmit Rate:         1412830             VPC Conns disabled:    No            

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

VC Shaping:            No                       coding:           --            

Hdr Type NNI:          Yes                      recv impedance:   --            

Statistical Reserve:   5000    cps              cable type:       --            

Idle code:             7F hex                         length:     --            

Connection Channels:   256                 Pass sync:             No            

Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No            

Restrict CC traffic:   No                  HCS Masking:           Yes           

Link type:             Terrestrial         Payload Scramble:      Yes           

Routing Cost:          10                  Frame Scramble:        Yes           

                                           Virtual Trunk Type:    --            

                                           Virtual Trunk VPI:     --            

                                           Deroute delay time:    0 seconds     

Last Command: dsptrkcnf 6.1                                                     

node	 TN    Cisco           BPX 8620  9.3.24    Jan. 4 2001  18:24 GMT 

TRK 6.1 Parameters                                                              

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

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

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

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

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

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

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

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

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

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

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

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

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

14 EFCN     - BData B  [  30] (Dec)                                             

This Command: cnftrkparm 6.1                                                    

IGX 8400 Nodes

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:42 PST 

                           System-Wide Parameters                               

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

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

3  Max Network Delay for 'v' connections (msec).......................   14     

4  Max Network Delay for 'c' connections (msec).......................   27     

5  Max Network Delay for 't' & 'p' connections (msec).................   14     

6  Max Network Delay for 'a' connections (msec).......................   27     

7  Max Network Delay for High Speed Data connections (msec)...........   32     

8  Max Network Delay for CDP-CDP 'v' connections (msec)...............   64     

9  Max Network Delay for CDP-CDP 'c' connections (msec)...............   64     

10 Max Network Delay for CDP-CDP 't' & 'p' connections (msec).........   64     

11 Max Network Delay for CDP-CDP 'a' connections (msec)..............    64     

12 Max Network Delay for CDP-CDP High Speed Data connections (msec)...   64     

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

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

15 Max Local Delay for Interdom CDP-CDP 'v' conns (msec)..............   27     

16 Max Local Delay for Interdom CDP-CDP 'c' conns (msec)..............   27     

17 Max Local Delay for Interdom CDP-CDP 't' & 'p' conns (msec)........   27     

18 Max Local Delay for Interdom CDP-CDP 'a' conns (msec)..............   27     

19 Max Local Delay for Interdom CDP-CDP High Speed Data conns (msec)..   27     

20 Max Local Delay for Interdom High Speed Data conns (msec)..........   28     

21 FastPAD Jitter Buffer Size  (msec).................................   15     

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

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

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

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

This Command: cnfsysparm                                                        

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:42 PST 

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

39 Stat Config Proc Delay [ 2000] (D)                                           

40 Enable Degraded Mode   [    Y] (Y/N)                                         

41 Enable Rrt on Comm Fail[    N] (Y/N)                                         

42 Auto Switch on Degrade [    Y] (Y/N)                                         

43 Max Degraded Aborts    [  100] (D)                                           

44 Max Htls Rebuild Count [  100] (D)                                           

45 Htls Counter Reset Time[ 1000] (D)                                           

This Command: cnfnodeparm                                                       

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:43 PST 

Index Status    Function                                                        

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

2     Enabled   FDP Loopback button                                             

3     Enabled   User Command Logging                                            

4     Enabled   Automatic Card Reset on Hardware Error                          

5     Enabled   TXR Model D Download                                            

6     Enabled   Card Error Record Wraparound                                    

7     Disabled  Card Test After Failure                                         

8     Enabled   Download From Remote CWM                                        

9     Disabled  Logging of conn events in local event log                       

10    Disabled  Logging of conn events in CWM event log                         

11    Disabled  Logging SVC Connection Events                                   

12    Disabled  Force Download From a Specific IP address                       

13    Disabled  CDP WinkStart Signalling                                        

14    Enabled   Logging of Bus Diagnostic Events in local event log             

15    Enabled   Automatic Card Reset after Burnfw for CBI cards                 

16    Disabled  Logging of router state events in CWM event log                 

This Command: cnffunc                                                           

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:43 PST 

Index Status    Function                                                        

1     Disabled  Data Frame Multiplexing                                         

2     Disabled  Adaptive Voice                                                  

3     Enabled   Frame Relay                                                     

4     Disabled  Configuration Save/Restore                                      

5     Disabled  ForeSight                                                       

6     Disabled  Frame Relay Network-to-Network Interface                        

7     Disabled  Multiple VTs (1 session enabled)                                

8     Disabled  Interface Shelf                                                 

9     Enabled   Virtual Trunks                                                  

10    Disabled  ABR standard with VSVD                                          

This Command: cnfswfunc                                                         

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:43 PST 

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

Type   Freq    Enable        Inc   Thresh  Timeout   Enable        Inc   Thresh 

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

PSM      300   Enabled       100      300       31   N/A           100      300 

HDM      300   Enabled       100      300       80   Enabled       100      300 

LDM      300   Enabled       100      300       80   Enabled       100      300 

NTM      300   Enabled       100      300       31   N/A           100      300 

FRM      300   Enabled       100      300       80   Enabled       100      300 

MT3      300   Enabled       100      300       50   N/A           100      300 

CVM      300   Enabled       100      300      300   N/A           100      300 

NPM      180   Enabled       100      300      120   N/A           100      300 

ARM      300   Enabled       100      300       60   N/A           100      300 

BTM      300   Enabled       100      300      120   N/A           100      300 

FTM      300   Enabled       100      300       80   Disabled      100      300 

UFM      300   Enabled       100      300       80   Enabled       100      300 

UFMU     300   Enabled       100      300       80   Enabled       100      300 

ALM      300   Enabled       100      300      120   N/A           100      300 

UVM      300   Disabled      100      300       60   N/A           100      300 

UXM      300   Enabled       100      300      800   Enabled       100      300 

URM      300   Enabled       100      300      800   Enabled       100      300 

This Command: cnftstparm                                                        

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:43 PST 

1  Normalization Interval    [    2] (D)                                        

2  Max Number To Normalize   [    5] (D)                                        

3  Normalization Logging     [   No]                                            

4  Settling Interval         [    4] (D)                                        

5  Minimum Open Space        [ 1000] (D)                                        

6  Normalization Priority    [ Load]                                            

7  Load Sample Period        [    4] (D)                                        

8  Maximum Routing Bundle    [   90] (D)                                        

9  Reroute Timer             [    0] (secs)                                     

10 Reset Timer on Line Fail  [  Yes]                                            

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

12 Down/Up Timer             [30000] (msecs)                                    

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

14 Time between Rrt cycles   [    5] (mins)                                     

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

16 Routing pause timer       [    0] (msecs)                                    

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

18 Send SVC urgent msg       [  Yes]                                            

19 Max SVC Retry             [    0] (D)                                        

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

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

22 Enable Cost-Based Routing [   No]                                            

23 Enable Route Cache Usage  [   No]                                            

24 Use Delay for Routing     [   No]                                            

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

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

27 Increment between RR grps [  100] (CLU)                                      

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

This Command: cnfcmparm                                                         

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:44 PST 

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

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

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

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

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

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

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

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

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

10 Crc Block Size (hex)    [    400]                                            

11 Rev Change Wait(dec)    [      0]                                            

12 CCs Switch Wait(dec)    [   1000]                                            

13 Lcl Response TO(msec)   [   5000]                                            

14 Rmt Response TO(msec)   [  30000]                                            

15 FW Dnld Block TO(msec)  [     50]                                            

This Command: cnfdlparm                                                         

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:44 PST 

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

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

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

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

5. UID Privilege Level ... 6                                                    

6. Input Character Echo .. Enabled                                              

7. Screen Update Time .... 10 seconds                                           

This Command: cnfuiparm                                                         

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:44 PST 

1  Priority Bumping Enabled                [  NO]                               

2  Priority Bumping Bundle                 [  10] (D)                           

3  Priority Bumping Bands:                                                      

   Band 1                                  [   2] (D)                           

   Band 2                                  [   4] (D)                           

   Band 3                                  [   6] (D)                           

   Band 4                                  [   8] (D)                           

   Band 5                                  [  10] (D)                           

   Band 6                                  [  12] (D)                           

   Band 7                                  [  14] (D)                           

This Command: cnfbmpparm                                                        

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:44 PST 

Function            Number   Status      Function            Number   Status    

Background Upcard     1      Enabled     Dynamic BW Allocation 15     Enabled   

Background Updates    2      Disabled    Modem Polling         16     Enabled   

Standby Terminal      3      Disabled    Conn Stat Sampling    17     Enabled   

Memory Protection     4      Enabled     FastPAD Test          18     Enabled   

Comm Break            5      Enabled     Neighbor Update Errs  19     Disabled  

Comm Fail Test        6      Enabled                                            

BRAM Memory Protect   7      Enabled                                            

CRC Test              8      Enabled                                            

CDT Clock Test        9      Enabled                                            

Bus Fail Detection    10     Enabled                                            

Line Diag             11     Enabled                                            

Clock Restoral        12     Enabled                                            

Cm_Rerouting          13     Enabled                                            

Clock Routing         14     Enabled                                            

This Command: on1                                                               

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:44 PST 

Function            Number   Status      Function            Number   Status    

Line Stat Sampling    1      Enabled     LAN Interface         15     Enabled   

Statistical Alarm     2      Enabled     Update Standby Stats  16     Enabled   

Job Ready Checker     3      Enabled     EIA Monitoring        17     Enabled   

Configuration  Backup 4      Enabled     Telnet Access         18     Enabled   

Standby Update        5      Enabled     Junction ID           19     Enabled   

Downloader            6      Enabled     Mult SV+/Routing Node 20     Enabled   

Cm Updates            7      Enabled     Feeder with NW Trunks 21     Disabled  

Power Supply Monitor  8      Enabled     Multiple Fdr Trunks   22     Disabled  

Topo/Stat Updates     9      Enabled     Simulated Fdr Trks    23     Disabled  

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

Port Stat Sampling    11     Enabled     IGX - ACM Selftest    25     Enabled   

Robust Updates        12     Enabled     Card Simulation Tool  26     Enabled   

Robust Alarm Updates  13     Enabled     Major Alarm on NNI    27     Disabled  

Realtime Counters     14     Enabled     Deroute Delay         28     Enabled   

This Command: on2                                                               

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

Function            Number   Status                                             

Trace Msg Sent        1      Disabled                                           

Multi-DB Stby Updates 2      Enabled                                            

AIT/BTM/ALM 32h Ext2  3      Enabled                                            

Card Synchronization  4      Disabled                                           

Loop Access Dev Init  5      Disabled                                           

Auto allocate UXM UBU 6      Disabled                                           

Trace Conv Msg        7      Disabled                                           

Automatic Cbus Diags  8      Disabled                                           

Region memory init    9      Disabled                                           

This Command: on3                                                               

UXM-T3

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK 13.1 Config       T3/636   [96000 cps]  UXM slot:13                         

Transmit Trunk Rate:  96000  cps          Payload Scramble:     No              

Rcv Trunk Rate:       96000  cps          Connection Channels:  256             

Pass sync:            Yes                 Gateway Channels:     200             

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

Statistical Reserve:  5000   cps          Deroute delay time:   0 seconds       

Header Type:          NNI                 VC Shaping:           No              

VPI Address:          1                   VPC Conns disabled:   No              

Routing Cost:         10                                                        

Idle code:            7F hex                                                    

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Line framing:         PLCP                                                      

Line cable length:    0-225 ft.                                                 

HCS Masking:          Yes                                                       

Last Command: dsptrkcnf 13.1                                                    

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK 13.1 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  2.0]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]                                          

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

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

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

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

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

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

This Command: cnftrkparm 13.1  

UXM-T1-IMA (with 1 physical only line up)

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.4 Config       T1/24    [3622  cps]  UXM slot:8                          

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

Retained links:       1                   Line cable type:      ABAM            

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

Rcv Trunk Rate:       3622   cps          HCS Masking:          Yes             

Pass sync:            Yes                 Payload Scramble:     No              

Loop clock:           No                  Connection Channels:  256             

Statistical Reserve:  1000   cps          Gateway Channels:     200             

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

VPI Address:          1                   IMA Protocol Option:  Disabled        

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

Idle code:            7F hex              IMA Clock Mode:       CTC             

Restrict PCC traffic: No                  Deroute delay time:   0 seconds       

Link type:            Terrestrial         VC Shaping:           No              

Line framing:         ESF                 VPC Conns disabled:   No              

This Command: dsptrkcnf 8.4                                                     

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:46 PST 

TRK  8.4 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  2.0]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]                                          

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

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

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

41 CBR    [   80]    44 CBR    [   60]                                          

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

43 ABR    [   80]    46 ABR    [   60]                                          

This Command: cnftrkparm 8.4                                                    

UXM-T1-IMA (with 4 physical lines up)

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.4 Config       T1/95    [14339  cps]  UXM slot:8                          

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

Retained links:       4                   Line cable type:      ABAM            

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

Rcv Trunk Rate:       14339  cps          HCS Masking:          Yes             

Pass sync:            Yes                 Payload Scramble:     No              

Loop clock:           No                  Connection Channels:  256             

Statistical Reserve:  1000   cps          Gateway Channels:     200             

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

VPI Address:          1                   IMA Protocol Option:  Disabled        

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

Idle code:            7F hex              IMA Clock Mode:       CTC             

Restrict PCC traffic: No                  Deroute delay time:   0 seconds       

Link type:            Terrestrial         VC Shaping:           No              

Line framing:         ESF                 VPC Conns disabled:   No              

This Command: dsptrkcnf 8.4                                                     

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:46 PST 

TRK  8.4 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  2.0]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]                                          

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

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

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

41 CBR    [   80]    44 CBR    [   60]                                          

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

43 ABR    [   80]    46 ABR    [   60]                                          

This Command: cnftrkparm 8.4                                                    

UXM-E1-IMA (with only one physical line up)

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.1 Config       E1/30    [4528  cps]  UXM slot:8                          

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

IMA Group Member(s):  1                   Line recv impedance:  120 ohm         

Retained links:       1                   HCS Masking:          Yes             

Transmit Trunk Rate:  4528   cps          Payload Scramble:     Yes             

Rcv Trunk Rate:       4528   cps          Connection Channels:  256             

Pass sync:            Yes                 Gateway Channels:     200             

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

Statistical Reserve:  1000   cps          IMA Protocol Option:  Disabled        

Header Type:          NNI                 IMA Max. Diff. Dly:   200 msec.       

VPI Address:          1                   IMA Clock Mode:       CTC             

Routing Cost:         10                  Deroute delay time:   0 seconds       

Idle code:            54 hex              VC Shaping:           No              

Restrict PCC traffic: No                  VPC Conns disabled:   No              

Link type:            Terrestrial                                               

This Command: dsptrkcnf 8.1                                                     

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.1 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  N/A]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]

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

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

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

41 CBR    [   80]    44 CBR    [   60]    

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

43 ABR    [   80]    46 ABR    [   60]    

This Command: cnftrkparm 8.1                                                    

UXM-E1-IMA (4 physical lines up)

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.1(4) Config    E1/119   [17962 cps]  UXM slot:8                         

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

IMA Group Member(s):  1-4                 Line recv impedance:  120 ohm      

Retained links:       4                   HCS Masking:          Yes          

Transmit Trunk Rate:  17962  cps          Payload Scramble:     Yes          

Rcv Trunk Rate:       17962  cps          Connection Channels:  256          

Pass sync:            Yes                 Gateway Channels:     200          

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

Statistical Reserve:  1000   cps          IMA Protocol Option:  Enabled      

Header Type:          NNI                 IMA Max. Diff. Dly:   200 msec.    

VPI Address:          1                   IMA Clock Mode:       CTC          

Routing Cost:         10                  Deroute delay time:   0 seconds    

Idle code:            54 hex              VC Shaping:           No           

Restrict PCC traffic: No                  VPC Conns disabled:   No           

Link type:            Terrestrial        

This Command: dsptrkcnf 8.1

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  8.1(4) Parameters:

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

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

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

 4 Gateway Efficiency    (D)   [  N/A]

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]

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

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

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

41 CBR    [   80]    44 CBR    [   60]    

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

43 ABR    [   80]    46 ABR    [   60]    

This Command: cnftrkparm 8.1                                                    

UXM-E3

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  7.1 Config       E3/530   [80000 cps]  UXM slot:7                          

Transmit Trunk Rate:  80000  cps          Payload Scramble:     Yes             

Rcv Trunk Rate:       80000  cps          Connection Channels:  256             

Pass sync:            Yes                 Gateway Channels:     200             

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

Statistical Reserve:  5000   cps          Deroute delay time:   0 seconds       

Header Type:          NNI                 VC Shaping:           No              

VPI Address:          1                   VPC Conns disabled:   No              

Routing Cost:         10                                                        

Idle code:            7F hex                                                    

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Line framing:         HEC                                                       

Line cable length:    0-225 ft.                                                 

HCS Masking:          Yes                                                       

This Command: dsptrkcnf 7.1                                                     

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  7.1 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  2.0]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]                                          

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

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

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

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

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

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

This Command: cnftrkparm 7.1                                                    

UXM-OC3

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  6.1 Config       OC3      [353207cps]  UXM slot:6                          

Transmit Trunk Rate:  353208 cps          Connection Channels:  256             

Rcv Trunk Rate:       353207 cps          Gateway Channels:     200             

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

Loop clock:           No                  Frame Scramble:       Yes             

Statistical Reserve:  5000   cps          Deroute delay time:   0 seconds       

Header Type:          NNI                 VC Shaping:           No              

VPI Address:          1                   VPC Conns disabled:   No              

Routing Cost:         10                                                        

Idle code:            7F hex                                                    

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Line framing:         STM-1                                                     

HCS Masking:          Yes                                                       

Payload Scramble:     Yes                                                       

This Command: dsptrkcnf 6.1                                                     

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  6.1 Parameters:                                                            

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

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

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

 4 Gateway Efficiency    (D)   [  2.0]                                          

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

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

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

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

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

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

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

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

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

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

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

35 CBR    [  600]    38 CBR    [  600]                                          

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

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

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

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

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

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

This Command: cnftrkparm 6.1                                                    

NTM-T1

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

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

Line DS-0 map:        0-23                                                      

Pass sync:            Yes                                                       

Loop clock:           No                                                        

Statistical Reserve:  1000   pps                                                

Routing Cost:         10                                                        

Idle code:            7F hex                                                    

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Line framing:         D4                                                        

Line coding:          B8ZS                                                      

Line cable type:      ABAM                                                      

Line cable length:    0-133 ft.                                                 

Traffic:              V,TS,NTS,FR,FST                                           

Deroute delay time:   0 seconds                                                 

This Command: dsptrkcnf 5                                                       

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  5 Parameters:                                                              

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

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

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

 4 Gateway Efficiency    (D)   [  N/A]                                          

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

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

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

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

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

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

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

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

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

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

This Command: cnftrkparm 5                                                      

NTM-E1

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

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

Line DS-0 map:        0-31                                                      

Pass sync:            Yes                                                       

Loop clock:           No                                                        

Statistical Reserve:  1000   pps                                                

Routing Cost:         10                                                        

Idle code:            54 hex                                                    

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Line coding:          HDB3                                                      

Line CRC:             No                                                        

Line recv impedance:  75 ohm + gnd                                              

Traffic:              V,TS,NTS,FR,FST                                           

Deroute delay time:   0 seconds                                                 

This Command: dsptrkcnf 6                                                       

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  6 Parameters:                                                              

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

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

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

 4 Gateway Efficiency    (D)   [  N/A]                                          

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

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

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

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

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

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

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

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

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

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

This Command: cnftrkparm 6                                                      

NTM-SR

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

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

Subrate interface:    X.21                                                      

Subrate data rate:    1920 kbps                                                 

Pass sync:            No                                                        

Loop clock:           Yes                                                       

Statistical Reserve:  1000   pps                                                

Routing Cost:         10                                                        

Restrict PCC traffic: No                                                        

Link type:            Terrestrial                                               

Traffic:              V,TS,NTS,FR,FST                                           

Deroute delay time:   0 seconds                                                 

This Command: dsptrkcnf 7                                                       

node	 TN    Cisco           IGX 8420  9.3.24    Jan. 4 2001  20:45 PST 

TRK  7 Parameters:                                                              

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

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

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

 4 Gateway Efficiency    (D)   [  N/A]                                          

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

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

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

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

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

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

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

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

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

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

This Command: cnftrkparm 7                                                 

Appendix A: BXM Firmware MFW Release Notes

This section contains information about the BXM firmware MFW.

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

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

Front Card for APS Compatibility

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

Back Cards

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

New Features supported in BXM Firmware MFW

Bug fixes only.

New Features supported in BXM Firmware MFV

VC merge support added.

New Features supported in BXM Firmware MFU

Virtual trunk oversubscription.
VC shaping.

New Features Supported in BXM Firmware MFT

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

New Features Supported in BXM Firmware MFR

Bug fix only.

New Features Supported in BXM Firmware MFP

Configurable number of ILMI traps.

New Features Supported in BXM Firmware MFN

F4-F5 Mapping on ports and F4 AIS detection on virtual trunks.
Support for E2E tstpingoam.
Support for O.151 OAM standard.

New Features Supported in BXM Firmware MFM

Bug fix only.

New Features Supported in BXM Firmware MFK

LCN CAC with policing parameters set by PNNI controller. (See Notes, Cautions & Clarifications).

New Features Supported in BXM Firmware MFJ

Bug fix only.

New Features Supported in BXM Firmware MFH

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

New Features Supported in BXM Firmware MFF

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

New Features Supported in BXM Firmware MFE

Bug fix only.

Note Support for APS 1:1 added for VSI.

New Features Supported in BXM Firmware MFD

Bug fix only.

New Features Supported in BXM Firmware MFC

Support for SES (PNNI controller).
BootCore enhancement to support multi-vendor flash-SIMMs.
A 1 msec granularity for tstdelay measurement.

New Features Supported in BXM Firmware MFB

Multiple VSI (2.2) partition feature. Three partitions are supported.
Hitless connection density upgrade for BXM.
SCR and PCR policing at less than 50 CPS for T3/E3 BXMs.
Control traffic shaping.

New Features Supported in BXM Firmware MFA

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

Note First release in MF branch of firmware.

New Features Supported in BXM Firmware MEC

There is no new feature in release MEC.

New Features Supported in BXM Firmware MEB

There is no new feature in release MEB.

New Features Supported in BXM Firmware MEA

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

The current default thresholds are

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

New Features Supported in BXM Firmware MDA

Virtual trunking
BXM multi-level channel statistics
SONET linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1)
Card based LMI and ILMI
Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. See Special Installation/Upgrade Requirements.

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 1 Change the MGX Release 1 feeder to use APS1+1 unidirectional AND disable K1K2 processing (may need to delete and then add back APS). On the BPX temporarily configure to use unidirectional mode.

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

Step 3 Proceed to upgrade the BXM cards as if YRED.

Step 4 After both cards are MFW, add back the APS 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 1 Upgrade the standby card with the MFA or above firmware version. Wait for all of the configuration to be downloaded into the card.

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

Step 3 Burn the other card with the desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware 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.

Intra-MFx (minus MFA) and intra-MEx upgrades are compatible.

Channel Statistics Issues

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

Upgrade from firmware revision MEA or higher.

Step 1 Upgrade SWSW to 9.2.30 or higher.

Step 2 Upgrade the firmware to MFW.

Upgrade from firmware revision lower than MEA. This procedure avoids card mismatch.

Step 1 Upgrade firmware to MEC.

Step 2 Upgrade the SWSW to 9.2.30 or higher revision.

Step 3 Upgrade the firmware to MFW.

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

Features Obsoleted

The following features have been obsoleted:

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

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

2. M.F.E is a not on CCO as it is an SES specific release.

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.

9. The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.

10. APS 1:1 is not supported for VSI in versions before MFE. (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.

Note BXME (enhanced cards) support all statistics levels unconditionally with all valid configurations, models, and releases.

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.

Note This feature is not active when APS is configured and enabled. However, an exposure might occur in configurations where APS is not enabled, on alternate trunk routes that do not exist, or on UNI ports. Because this feature is not configurable users who do not want this behavior should not upgrade to MFP through MFW. Instead, Users should wait for a subsequent SWSW BXM FW release in which this feature can be turned on and off (default is off) via CLI.

Known Anomalies

The following table lists the known anomalies for the BXM firmware.

Bug ID	Description	Apply to SES
CSCdw16017	Symptom: Traffic is only seen on the ingress of the master and slave nodes. Condition: This problem is triggered by a network condition that causes the VPC to reroute. VPC experiencing this problem have been ABRSTD with VSVD enabled one megabits or larger VPC connections. Workaround: Uping and downing the connection clears the problem.	No
CSCdx28781	Symptom: When inserting BIP-8 from an ADTECH test set into a OC-3 or OC-12, it is failing all connections and sending an AIS back to the test set. The proper response is only to send a FEBE back to the test set disconnected and reconnected to BXM with MEE. Condition: Tested with 9.3.4P and MF14 (BETA TB) and results are the same as MFP. Workaround: Unknown	No
CSCdx52484	Symptom: CBR traffic got dropped on ENNI link on BPX side where there is congestion. Condition: resetcd of BXM can solve the problem. Workaround: Unknown.	No
CSCdx72292	Symptom: BPX not allowing SES to cross-commit SPVCs Conditions: SWSW 9.3.40 and BXM FW MF17 with 12000 SPVCs routed between two BPX/SES nodes only half are routed the rest are NACK'ed. Workaround: There are two ways to work around: 1. When the sum of the policy parameter (% of the partition minimum bandwidth reserved for each service of class) is reaching 100% (PNNI partition only), provide at least 20 cells of common pool using cnfrsrc command. For example: the max bandwidth of partition 1 is X and min bandwidth of partition 1 is Y the max bandwidth of partition 2 is W and min bandwidth of partition 2 is Z Make sure that max (X, W, Y+Z) should be greater than Y+Z+20. Here, the total bandwidth allocated to that interface = max (X,W,Y+Z), the common pool for that interface = max (X, W, Y+Z) - (Y + Z). 2. When the common pool resulted from the cnfrsrc is zero, try to reduce the sum of the policy parameter (% of partition minimum bandwidth for each class of service) to less than 100% for PNNI partition.	Yes
CSCdy16927	Symptom: BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred. Conditions: SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder 1. The connection segment in the BPX/SES network is down. 2. The corresponding segment in the SPVC feeder is in Abit alarm. 3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "" tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the downed VSI connection in the BPX/SES network. Workaround: None.	Yes

Bugs Fixed in MFW

Bug ID	Description
CSCdw80712	Symptom: 1:1 APS allows manual/forced switchapsln P->WLine. Conditions: 1. 1:1 APS with Bi-Dir configured; remote is AXSM/B. 2. Manual switchaps W->PLine from AXSM/B. 3. Forced switchaps P->WLine from BXM. Workaround: None.
CSCdx45385	Symptom: BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn). Conditions: 1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level. 2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated. Workaround: Add a con or down a con to trigger the update.
CSCdx55794	Symptom: BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4. Conditions: 1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX. 2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI. Workaround: None.
CSCdx56537	Symptom: Setting cnftrkparm 9 2500/15000 causes trunk failure. Conditions: BXM running MFU firmware. Found in lab environment but likely to also be found in a live network if these trunk parm values are used and the trunk passes over another medium such as a TDAX or SDH backbone. Workaround: Set cnftrkparm 9 2500/10000 which is the default for STM1. Do not use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.
CSCdx59080	Symptom: Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a "Looped Back" state when the BXM is reset by command "resetcd ? h". Conditions: BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk. Workaround: Issue cnftrk and change none of the parameters by stepping through them.
CSCdy01870	Symptom: SIMBA reset card errors logged due to PRFD Pending Errors Conditions: BXM image MEE and SWSW image 9.3.00 Workaround: None.
CSCdy01951	Symptom: Unnecessary alarms are triggered when BXM sends slot errors to SWSW. Conditions: The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed. Workaround: None.
CSCdy05515	Symptom: Current BXM firmware only support a few stats counters. In order to enhance customer operation and maintenance capability, a few new stats counters have been added. The detail description about the new created stats and associated CLI cmd and MIB can be found in the latest VSI document. See DDTS case CSCdy05597 (SES and Mibs). Conditions: All previous FW do not support the new connection stats. Workaround: Not applicable.
CSCdy13987	Symptom: Newly added routed SPVC carries counter values of previously deleted SPVC. Conditions: Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values. Workaround: Problem is fixed in MFW (MF20).
CSCdy75277	Symptom: pnport stuck in down state Conditions: Configure PNNI trunk between SES and MGX 8850 (PXM45) using automation script PROU001. Workaround: Unknown.

Bugs 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

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

Bugs Fixed in MFT

Bug ID

Description

CSCdw54957

Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX45.

Conditions: SWSW: 9.3.3i, BXM FW: MFR

When there is a congestion on MGX egress port, MGX45 sets EFCI=1 for all SPVC's/xpvc's on that port to the downstream.

Workaround: None

Bugs Fixed in MFR

Bug ID	Description
CSCdv90721	Symptom: The prevalent symptom is Tx BIP 16 and B-Frame Parity slot errors on BXM-622 or BXM-155 cards. Occasional SIU Phase and Rx BIP 16 errors may also occur on BXM-622 and BXM-155 cards depending on the severity of the problem. Conditions: Can occur with any version of BXM firmware on BXM-622 or BXM-155 cards. The aggregate cell transfer rate of the BXM card is 1,412,832 cells/second so the problem can occur on BXM-622 or BXM-155 cards even if the load on each line is well below line rate. The problem occurs during oversubscription when multiple high speed cards have traffic destined for a particular card through the switching fabric. Workaround: To solve the BCC-4 software error 742 problem upgrade switch software to 9.1.22, 9.2.31, 9.3.00 or later.
CSCdw16362	Symptom: The BXM card changed the state from active to empty for a particular slot and failed to communicate with the BCC. Condition: Switch software was upgraded for the particular BXM and statistics were enabled before the current state. Now the particular slot is in empty state although both front and back cards are present for the slot. This loop happened because of spvc statistics task. It happens when new spvc_config_stats command comes in the vsi message with more than currently configured stat ids. Due to this the data base will be updated. During this update some flag was not set properly and it leads to a loop. Workaround: Not known other than the physical removal of the card. Or, use MFR or later images.
CSCdm50659	Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms. Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable. Workaround: Lowering the alarm threshold for MAJOR and MINORHCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR. These thresholds are as low as they can be set currently.
CSCdt82384	Symptom: APS trunk built on bxm-155-4d. sf and sd thresholds set to 5 and UNI-direction non-revertive switching with cnfapsln. Random logic errors inserted into the working pair of the trunk to observe protection switch at sf threshold. Good switch at 1 in 10³ and 10⁵ but when 1 in 10⁴ inserted trunk goes unstable repeatedly switching from working to protection and vice versa. Trunk continues to toggle until errors removed. Conditions: BXM-155 enhanced cards using APS card cage and injecting 10^4 error rate into one of the working lines. Workaround:

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

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

Bugs 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

Bugs Fixed in MFL

Bug ID	Description
CSCds15145	Symptom: Max BW could be configured as less than Min. Conditions: This might happen as the policy parameter might not be checked for the consistency. Workaround: Do not configure Max below min.
CSCds06835	Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk. Conditions: CC traffic is passed across virtual trunks. Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.
CSCds75221	Symptom: When Issuing the command "dspconstats" for abr or ubr connection it does not report the CLP0 and CLP1 correctly. Conditions: Statistics for abr and ubr not updated. Workaround: None
CSCdt38554	Symptom: After executing resetsys on the node(svcpop2) pxm1 cards. there are two ports stuck in building vc. Conditions: The node(svcpop2) has 100k routed spvc connections. Workaround: Unknown
CSCdt45966	Symptom: Checksum calculation is not correct in BXM. Conditions: Connection conditioning via bulk set cmd. Workaround: Uppnport/dnpnport on UNI and NNI port and do switchyred to kick resync.
CSCdt48062	Symptom: Port gets stuck in building VC state. Conditions: Connection admission control. Workaround: Establish connections of various service type and bandwidth requirements.

Bugs Fixed in MFK

Bug ID	Description
CSCdt21322	Symptom: BXM load info returned to controller is wrong when maxbw set to 0. Conditions: Reproducible Workaround: None.
CSCdp16050	Symptom: maxvc functionality for CAC not working Conditions: reproducible Workaround: None.
CSCdt04632	Symptoms: For a vsi partition, the reporting available number of LCN is greater than the maximum number of LCN configured for that partition. Conditions: When the port group unused LCN is less than the maximum LCN configured for the partition and the unused LCN for the port group plus the LCN that still left from the reserved (min-curr) is greater than the max of the partition. Work around: None.
CSCds85653	Symptom: BXM card error of "cb_if.c 1588 CbCoreTxEvent(): Failed core_cbmsg_put: return. Conditions: Continually doing switchcc with large amounts of AR/SPVC connections Workaround: Reset BXM card
CSCds76142	Symptom: BXM card shows standby-failed status Condition: Download firmware on standby card Workaround: Reset BXM card.
CSCds65105	Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'. Conditions: DAX conn from BXM-622 port 1-2 on the same node with ADTECH generate traffic. Workaround: None
CSCdr19696	Symptom: User never gets to know when the line is out of SD/SF condition. both the aps lines always show in OK state in dspapsln. Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition. Workaround: Use rsh command to get all the aps line's status.

Bugs Fixed in MFJ

Bug ID	Description
CSCds61912	Symptom: After downloading new firmware(MF30), card in failed state. Conditions: Downloading MF30 firmware release. Workaround: Don't use MF30 which is a development release between MFH and MFJ.
CSCds11506	Symptom: Min guaranteed cell rate shows a cell less than configured. Conditions: Setting min BW to say 3333334 and policy BW% to 5859 Workaround: Increase the minBW by few cells.
CSCdr19696	Symptom: User never gets to know when the line is out of SD/SF condition. Both the aps lines always show in OK state in dspapsln. Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition. Workaround: Use rsh command to get all the aps line's status.
CSCds32845	Symptom: Connection commits rejected with reason 'no resources even when resources are actually available. Conditions: Enabling/disabling a virtual trunk. Workaround: Resetting the BXM after disabling a VT on any interface on the card.
CSCds37237	Symptom: When upgrade BXM firmware image to BXMMFH from images between BXMMFC-BXMMFF, if the network migration flag was enabled in a card before the upgrading, then after burning the new image to the card, the network migration flag becomes disabled mistakenly. Conditions: The problem only happens to the card whose previous image is BXMMFC-BXMMFF, and the network migration flag was enabled before upgrading, and BXMMFH has to be the new image. Workaround: Upgrading to image BXMMFH+ (not including BXMMFH), will not have any problem. network migration flag is always enabled, and no user command available any more to disable it. Only for the situation you need to upgrade image to BXMMFH and your card's previous images is BXMMFC-BXMMFF, you may see the problem. The workaround is, issue either the "rsh <slot> cdcfg network dis" command before the upgrading, or "rsh <slot> cdcfg network ena" after the upgrading, to enable the network migration flag on BXMMFH.
CSCds59710	Symptom: Loss of traffic on a VPC connection added with VPI=0. Conditions: SWSW: 9.3.10 BXM FW: MFF The port on which the VPC connection has been added has a VSI ctrlr attached to it and the Ctrlr is usingVPI=0 and VCI=x for its signalling channel. Workaround: If a VPC connection exists with VPI=0, on the port to which a Ctrlr is to be added, configure the signallingchannel on the controller side to use a VPI other than 0.
CSCds63578	Symptom: SW errors 105 logged on BXM while adding VSI connections. Subsequent card errors saying CB_TASK restarted. Conditions: This error sometimes happen when a VSI partition is enabled/disabled many times. Workaround: Reset the BXM.
CSCds65105	Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'. Conditions: DAX conn from BXM-622 port 1-2 on the same node with ADTECH generate traffic. Workaround: None
CSCds67854	Symptom: SPVC cannot be routed over the virtual trunk even when enough bandwidth and lcn are available. Routed connections discard some traffic. Conditions: Routing connections of different service types over the virtual trunks. Workaround: None.
CSCds04137	Symptom: Channels remain mismatch after lockout is cleared Conditions: In ITU-T Annex B protocol for APS, when a condition causes a switch to occur while a lockout request is present, the channel change will not resynchronize even after the lockout is cleared. Workaround: No
CSCds53645	Symptom: ABR connections (PNNI) not programmed properly for redundant slave. Conditions: Switchyred. When connection is added, redundant card is not there and inserted at later stage. When connection is added, no redundant config, addyred at later stage. Workaround: None

Bugs Fixed in MFH

Bug ID

Description

CSCds14495

Symptom: Dynamic Partitioning and SPVC AIS generation would not work on a card until a rsh command is issued to enable the network migration flag and reset the card.

Conditions: When a card comes up and has never enabled the network migration flag for life time.This network migration flag is used for enabling dynamic partitioning and SPVC AIS, status report generations. By default, the flag is disabled.

Workaround: Use the "rsh <slot> cdcfg netmig en/dis" command to enable/disable the flag, then reset the card once in a lifetime.

Bugs Fixed in MFF

Bug ID	Description
CSCds08448	Symptom: ERS (explicit rate stamping) is working only first virtual trunk and NOT for subsequent VTs (standard ABR) Conditions: When ERS is enabled on a card basis using "cnfabrparm", the mapping is done on a port-by-port basis. The port_vi is used but for virtual trunks, this mapping does not hold true. Need to change the mapping to the physical port. Workaround: On any physical port, just set up one virtual trunks. Or a physical trunk. Multiple VTs on the same physical port will cause a problem.
CSCdr79610	Symptom: Change booking factor for a class of service, get rejected. Conditions: When there are some connections established, and some of the class of service have used bandwidth exceeding their reserved, change booking factor for any class of the service may get rejected. This is because it fails the check which should only be called when cos_min_bw in the policy parameters is changed. This check should not be called when booking factor is changed. Workaround: Disable that partition, change the booking factor, then enable the partition again. Or keep the used_bw for all cos under teh cos_min_bw, you will be able to change booking factor freely.
CSCdr76334	Symptom: Connect OC3 port on BXM with 7200 router, connect 2 OC3 ports back to back. enable ILMI on router, and ILMI, protocol on card cnfrsrc VSI part 1 disable NebDiscovery on ports.when running cnfnodeparm 56 0\|1 and With VSI disabled, peer info is transmitted to peer. delcntrl, and cnfrsrc deleting VSI partition, fails to disable Peer information as well. Conditions: ilmi_enable_from_contrl bit was not cleared when delctrlr, or vsi partition deleted, thus vsi code kept issuing get requests and responding to peer information. In AR/VSI hybrid networks, and for backward compatibility either BXMs w/o NebDisc, or swsw versions. Topo traps are not sent to downrev'd swsw versions, and are controllable by sw software for versions including the feature. Code was added to properly support disabling of VSI functionality using delctrlr or cnfrsrc @ Bcc in addition to existing dnpnport @ the vsi controller. support for backrev'd cards added, and corrections to logic in Ilmi FSM state machine to properly send TopoTrap to BCC. Workaround: None
CSCdr79936	Symptom: Stats files not generated/missing on some 15 minutes intervals. Conditions: When system time is changed at 15 minutes boundaries. Workaround: Minimize system time and card config changes.
CSCdr83144	Symptom: Card error of: Description: 'N. Fatal from 0x17: 0x25120075 0x809b5f90 0x367e 0x1 Conditions: switchyred, switchcc or reset PXM when there are spvc connections with stats enabled. Workaround: None
CSCds11484	Symptom: Available cell rate reported by BXM is incorrect. Conditions: Sum of the minimum bandwidths of all the interfaces on a BXM reaches OC12. Workaround: Reduce minimum BW on all interfaces by half.
CSCdr89217	Symptom: Software Error Log of 9098 Conditions: cnfrsrc of partition 3 using MEB firmware Workaround: None
CSCdr89966	Symptom: Card Error of 0x41030006 Conditions: PXM controller is upgraded/re-booted Workaround: None
CSCdp89085	Symptoms: The total call count becomes negative on the BXM interface. However, this problem has not been reproducible. Conditions: If this problem happens, the following card error is displayed: 'vsi_rsrc_pfns.c 483 VrmRetLcnResources 3, 16316' Workaround: A related bug CSCdr86894 which reported an incorrect number of total call counts, has been found to be the result of an uninitialized variable in vsi_rsrc_conn_pfns.c: VrmRsrcClrRCMP(). The debugging information embedded in this function may be helpful in verifying the negative call count problem if it is reproduced.

Bugs Fixed in MFE

Bug ID	Description
CSCdp05098	Symptom: Cell discards occur for ABRFST/ABRSTD conns when the traffic burst is greater than the MBS Conditions: This occurs when the traffic burst size is fixed to 140000 cells at 70000 cps. The conn are configured with PCR=72000/72000, MBS=1000/1000 and ICR 7200/7200. This is the expected behavior since the configured MBS < the actual burst size. Workaround: Increase the MBS and ICR using cnfcon.
CSCdr59731	Symptom: Port 11.1 is connected to 11.2 and ILMI are up and running on both ports. Enable neighbor discovery on 11.1, then 11.2. The 0x71 responses/traps from BXM fw is not predictable. At least two variations are observed: 1. port 11.2 has it's neighbor's info but port 11.1 doesn't. 2. both port 11.1 and 11.2 only know the IP addresses of their neighbors. The Neighbor's IFName are missing. Problem was observed in MF17, but code changes in more recent builds had already repaired the problem. Conditions: When ILMI session restarts, remnants of IfName, IpAddr from previous session left. Clr/reset IfName,IpAddr in MIB, on ILMI session restart In FMSStart, pIlmiProcessFsmStart() calls a new function IlmiClrPeerAndSendTopoTrap(pcb_ptr->session_id)
CSCdr79936	Symptom: Stats files not generated/missing on some 15 minutes intervals. Conditions: When system time is changed at 15 minutes boundaries. Workaround: Minimize system time and card config changes.
CSCdm16800	Symptom: Card error 0xc000007 appears in the card error log. Conditions: This error indicates that an unknown type of cell which is not expected has arrived in the egress QE. Workaround: Engineering has done in-depth investigation into this case. We are convinced the problem does not affect user traffic or the node in any other way. Therefore, the symptom will not be reported as a card error. The fix has been incorporated into MEE firmware.
CSCdp22930	Symptom: N/A Conditions: cbus rd/wr operations set up in the PUUMBA chip when performing cbus rcv/xmit. Workaround: None
CSCdp74680	Symptom: Even if the interface is in LOS, the spvc's do not generate ingress AIS into the network. Conditions: Connection is added after the interface goes into LOS. Workaround: None
CSCdr44250	Symptom: Private image did not allow as many OAM cells to flow as public image. Conditions: This occurred by undoing a hardware fix in a private image. Workaround: This was never introduced into the Public view and no workaround is required.
CSCdr45986	Symptoms: Standby and active block checksum value do not match and resync happens on switchover. Conditions: When active card has many spvc connections derouted it happens. Workaround: None.
CSCdr71473	Symptom: Unreachable BXM, sw errors and cd errors on the BPX. Conditions: LMI is enabled when controller either slow to respond or un-reachable. Workaround: Disable LMI.
CSCdp97307	Symptoms: When executed "rsh <slot> vsi cm VsiIs " without parameter. The card will crash. Conditions: Always. Workaround: Pull out the card and reinsert.
CSCdr86894	Symptoms: Many ports have VC failure because BXM has no resource to build the CVC. Conditions: Intermittent Workaround: Reset BXM card.
CSCdr57712	Symptom: Multi_partition fails to report all virtual trunks. Conditions: In case of virtual trunks with different partition. Workaround: Reset the BXM card.
CSCdr77238	Symptom: Switch General Info does not contain bulk set capability bit. With newer images of PXM bulk set will not work with BXM images prior to MFD. Conditions: PXM Images later than 07/06/2000 contains logic to identify the bulk set capability of the slave. BXM images prior to 07/06/2000 will not have this bit set because it is newly introduced parameter in VSI spec. Workaround: No workaround. Need to upgrade to MFD.

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

Bugs Fixed in MFC

Bug ID	Description
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.
CSCdr11396	Symptom: Data transfer has affected while running OAM loopback Conditions: All user data is dropped when send in 960 cps of oam. Workaround: None
CSCdp11511	Symptom: BPX treats segment oam loopback different from end-to-end oam loopback cells. Conditions: Workaround:
CSCdr13208	Symptom: BXM CD errors while running OAM cells. Conditions: One PVC has 2880 cps of data and 960 cps of oam cells. Another PVC has 2880 cps of data and 960 cps of oam cells. Workaround: None
CSCdr13196	Symptom: BPX reports SWERR 105. Conditions: SWERR105 logged while running OAM loopback test Workaround: None reset the BXM card.
CSCdr13182	Symptom: tstdelay/tstcon/tstconseg for all PVCs on that card will fail. Conditions: When user sending in >= 960 cps of oam loopback cells Workaround:
CSCdr13151	Symptom: dspportstats always show Tx port = 0 Conditions: Sending in >= 960 cps of oam loopback cells. Workaround:

Bugs 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: Workaround: None 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: None. Upgrade to/MEF or newer versions of firmware
CSCdp28931	Symptom: No RDI-P generated when loss of Cell Delineation occurs. Conditions: Workaround:
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: None.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: None.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: None.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: None.Upgrade to MEF or newer version of firmware
CSCdp46399	Symptom: Need a documentation explains how to setup port groups for FW MEF (me26). Conditions: 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.

Bugs 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:

Bugs 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:
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:
CSCdm62809	Symptom: APS 1+1 bidirectional non-revertive switches back to working line when line condition clears on working. Conditions: 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:
CSCdm69974	Symptom: Card errors (0x25170076) occur when only one Virtual Trunk is configured in a physical port. Workaround:
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:
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 max channels. Workaround:
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:
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:
CSCdm74968	Symptom: 0B card error causing BXM to reset. Conditions: Over night jobs running on controller cards. Workaround:
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:
CSCdm78335	Symptom: dspvsistatus rarely shows the VSI programming status as Done. Conditions: Primary and secondary port has two different VPI range. Workaround:
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:
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:
CSCdm52254	Symptom: BIP-8 code errs occurs on routing trunks Conditions: T3 card used in HEC mode can randomly have this problem. Workaround:
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:
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:
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:
CSCdm82688	Symptom: Traffic Shaping problems with VT with and without rap around solution. Conditions: Large deviations in CDV values. Workaround:
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:
CSCdp00063	Symptom: Node unreachability is experienced on VTs (virtual trunks). Conditions: Multiple VTs are configured on a trunk interface of the BXM/BXM-E. Workaround: Configure only one VT per trunk interface.

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

if (configured cell rate == full line cell rate) then

	transmitted cell rate = full line cell rate

else

	transmitted cell rate = from equation below or from table 1

For example:

If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is then 98,013 CPS any traffic sent over 98,013 CPS would be discarded.

Only rates in the table or computed from the equation should be used. Otherwise, cell loss may be experienced.

1464865	56552	28832	19348	14559	11670	9738	8355
733860	54458	28278	19097	14416	11579	9674	8308
489558	52513	27744	18852	14277	11488	9611	8261
367288	50703	27231	18614	14139	11399	9549	8215
293888	49013	26736	18381	14005	11311	9487	8169
244938	47432	26258	18154	13872	11225	9426	8124
209966	45950	25798	17933	13743	11140	9366	8079
183733	44558	25353	17717	13616	11056	9307	8035
163327	43247	24923	17506	13491	10974	9248	7992
147001	42012	24508	17300	13368	10892	9190	7948
133642	40845	24106	17099	13248	10812	9133	7906
122509	39741	23717	16902	13129	10733	9077	7863
113088	38695	23341	16710	13013	10656	9021	7822
105012	37703	22976	16522	12899	10579	8966	7780
98013	36761	22623	16339	12787	10503	8912	7739
91889	35864	22280	16159	12677	10429	8858	7699
86485	35010	21947	15983	12568	10355	8805	7659
81681	34196	21625	15812	12462	10283	8753	7619
77383	33419	21311	15643	12357	10212	8701	7580
73515	32676	21007	15479	12254	10141	8650	7541
70014	31966	20711	15318	12153	10072	8599	7502
66833	31286	20423	15160	12053	10003	8549	7464
63927	30634	20143	15005	11955	9936	8500	7427
61264	30009	19871	14853	11859	9869	8451	7389
58814	29409	19606	14705	11764	9803	8403	7352

Bugs Fixed in MEB

Bug ID

Description

CSCdm50469

Symptom: Software error 105 and mallet card errors happened continuously.

Conditions: When jobs that cause reroutes of connections (e.g. switchcc, hitless rebuild) are run for a long time, sometimes BXM card freezes with malloc card errors and software error 105.

Workaround: None

CSCdm50723

Symptom: After deleting APS, switchyred causes temporary LOS when the other end still has APS.

Conditions: One end has APS 1+1, other end was added with APS 1+1 and line is up between the two ends. Then APS is deleted from one end. The primary card is active on non APS end. On switchyred on the non APS end there is a temporary LOS. If APS was never added to one end, then switchyred does not result in temporary LOS.

Workaround: Instead of deleting APS first and then doing a switchyred, do a switchyred first and then delete APS. This does not result in temporary LOS.

CSCdm63038

Symptom: BXM card fails with breakpoint error.

Conditions: When tx cell rate of a trunk is reduced to zero, BXM card fails with break point error (division by zero).

Workaround: None

Bugs Fixed in MEA

Bug ID	Description
CSCdm09882	Symptom: Log non fatal message related to RCMP errors. Conditions: It is mainly seen in the heat chamber. Workaround: None
CSCdm18186	Symptom: AIS status could be randomly be displayed in dspcon Conditions: When the connection AIS signal is constantly changing, the dspcon/dspchstats OAM status will not be accurate for all the connections on the card. Workaround: None
CSCdm26380	Symptom: Software error 9098 occured during switchyred BXM Conditions: This problem occurs on cards with the APS channels halved option set and then doing a cnfrsrc on a port that belongs to the second port group. Note that this fix will cause a card mismatch on active cards with channel halved option turned on. Workaround: None
CSCdm31923	Symptom: AIS/YEL alarm 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 YES in the trunk or line configuration. Workaround: None
CSCdm37519	Symptom: Trunks go to Communication Fail after burning firmware. Conditions: When MC10 is burnt into BXM-OC12 with trunks. Workaround: None
CSCdm37709	Symptom: APS line fails to clear channel mismatch after lockout. Conditions: Bi-direction APS 1+1. Local end has locked out of protection set. Then WORK cable is pulled out on local end to cause LOS. Lockout is then cleared and then the WORK cable is put back. This causes a channel mismatch on the far end and the mismatch never clears. Workaround: None
CSCdm38647	Symptom: This bug has been fixed in MEA such that the firmware reports the correct number of port groups. The side effect of this fix is that the Switch Software could mismatch the BXM card. If there is a card mismatch then down all the lines/trunks on the card and up them again. Conditions: When the user loads the MEA firmware on the BXM card running MDA with APS halved channeled enabled, then the card will come up in mismatched state. Workaround: None
CSCdm46658	Symptom: switchapsln command does not work for APS AnnexB line. Conditions: Annex B configuration if hitless rebuild is done when active line is PROT, then switchapsln does not work after hitless rebuild. Workaround: None

Bugs Fixed in MDA

Bug ID	Description
CSCdm38647	Symptom: MDA fw may report incorrect number of port-groups when APS channels are set to halved. Conditions: When user attempts to add all the channels available on the card on one port-group, it may be allowed even though the BXM may not have enough memory to support it. Also, this may cause a mismatch state when MDB firmware is burnt. Workaround: Down all the line/trunks on the card and up them again.
CSCdm23713	Symptom: VI numbers are not modified by firmware. Conditions: When one or more trunks are failed in the network, there may be a combreak in the network. Workaround: Set all the Virtual trunks to restrict CC traffic.
CSCdm23827	Symptom: APS alarm may clear on switchyred. Conditions: After a switchyred, an existing a LOS/LOF alarm may get cleared. This will only happen when the line has switched to protection before the card switchover is performed. Workaround: None
CSCdm23752	Symptom: BXM fw does not allow a networking channel on VTs to configured for egress only. Conditions: BXM fw allowed configuration of networking channel to be bidirectional only. Workaround: None

Firmware Filenames and Sizes

Filename	Size
BXMMFW.000	65536
BXMMFW.001	65536
BXMMFW.002	65536
BXMMFW.003	65536
BXMMFW.004	65536
BXMMFW.005	65536
BXMMFW.006	65536
BXMMFW.007	65536
BXMMFW.008	65536
BXMMFW.009	65536
BXMMFW.010	65536
BXMMFW.011	65536
BXMMFW.012	65536
BXMMFW.013	65536
BXMMFW.014	65536
BXMMFW.015	65536
BXMMFW.016	65536
BXMMFW.017	65536
BXMMFW.018	65536
BXMMFW.019	65536
BXMMFW.020	65536
BXMMFW.021	65536
BXMMFW.022	65536
BXMMFW.023	65536
BXMMFW.024	65536
BXMMFW.025	45744
BXMMFW.026	14
BXMMFW.027	2
BXMMFW.IMG	784
BXMMFW.img	784

Appendix B: UXM Model C ACE Firmware Release Notes

Introduction

ACE is a maintenance firmware release for UXM cards on IGX. The firmware is the same for UXM and UXM-E cards.

New Features

There are no new features in the UXM firmware ACE.

Obsolete Features

None.

Compatibility

1. Software

ACE firmware is compatible with Switch Software Release 9.3.10 or later.

2. Hardware

ACE firmware is compatible with UXM and UXM-E model hardware.

Bugs Resolved in ACE

UXM firmware ACE is a maintenance release. The open bugs known at this stage are listed in the Known Anomalies section of this appendix. The firmware release ACE 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 ACE requires an intermediate upgrade to revision ABJ. However, before upgrading the firmware to revision ABJ, the boot code has to be upgraded to boot revision 8.

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

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

Step 2 Upgrade the UXM boot code to boot revision 8.

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

Warning If these procedures are not followed, the card might enter a state from which it can NOT be recovered. Pay attention to this section before loading the new firmware.

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

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

Step 2 Upgrade the run-time UXM firmware to revision ACE.

Known Anomalies

Bug ID

Description

CSCdt17297

Symptoms: swerr 103 logged.

Conditions: Back card was improperly seated.

Workaround: Remove the front card, reseat and tighten screws on back card, reinsert the front card.

Bugs Fixed in ACE

Bug ID	Description
CSCdt29649	Symptoms: tstdelay fails or not accurate. Conditions: Will fail on PVC's traversing UXM lines/trunks. User may sometimes see tstdelay passing on some PVC's in which case the RTC may not be correct. Workaround: None, not service affecting. NOTE: Foresight RTDs are not affected by this problem.
CSCds58417	Symptoms: Initial TCB pool size decrements on active card in a YRED pair after reset of active card while other card in YRED pair is in standby. Conditions: TCB pool size on the active card in a YRED pair is decremented after each hardware reset of the card. Workaround: Avoid hardware reset of active card in YRED pair.
CSCdr65252 CSCds80842	Symptoms: YRED switchover generates swerr 9098 C01C and C505. Conditions: A YRED switchover occurs after multiple add/del of VSI connection followed by modifications to the VSI resource configuration with cnfrsrc. Workaround: Will not affect existing connections. May reduce the number of CBAs available to VSI on card. Down the redundant card and reset the active card.
CSCds69784	Symptoms: swerr 9000 C10A logged when delyred executed. Conditions: Executing delyred on IMA-T1 Workaround: None.
CSCdt13974	Symptoms: swerr 9000 continuously logged by the standby card of a YRED pair in which one card is a UXM and the other a UXM-E. Conditions: Triggered for the first time by a switch from primary to secondary after which the error is continuously logged without any more triggers. Workaround: Delete YRED (delyred).
CSCdt04968	Symptoms: The 0x50 message repeatedly times out when a hitless rebuild, hardware reset, or switchcc occurs on the node and until a 0xAF message (sync) is sent out to the UXM card. Conditions: Execution of either `resetcd h', `resetcd r', or switchcc on a UXM card. Workaround: The UXM takes 20 seconds or more to regain synch with the NPM.
CSCdu25184	Symptoms: Backcard(s) missing after a hitless rebuild on NPM. Conditions: Issuing `resetcd 1 r' (hitless rebuild of NPM). Workaround: Either reset or `dncd/upcd' the affected card.
CSCdt66310	Symptoms: ILMI messaging declares Comm. Failure instead of VT Path Failure if the VPC in the cloud port fails. Conditions: Cloud port is UXM and VT trunk port is BXM; ILMI is configured to run on the UXM card; VPC in the cloud port fails. Workaround: Run ILMI on the UXM port from the NPM.
CSCds77189	Symptoms: swerr C202 0x2F is logged. Conditions: During full rebuild of the node some of the keep alive messages from YRED pair is dropped. Workaround: None.
CSCdt22276	Symptoms: UXM goes into failed state. Conditions: When VSI trunk goes down due to a full rebuild on IGX node, UXM tries to delete all VSI connections over the VSI trunk. While deleting the connections, the UXM encounters a data bus exception and declares a fatal condition. Workaround: None (difficult to produce).
CSCdr71426	Symptoms: If selftest frequency is set to 1 second (using cnftstparm) and upln is done on a standby UXM card, the card goes into failed state and resets itself. Conditions: The card should be in standby and the line upped is not connected to any device on the other end. Workaround: Do not set the selftest frequency to 1 second.
CSCds08193	Symptoms: A delay is toggled several times on one of the lines on an IMA trunk and eventually the trunk discards all traffic on the trunk. No physical line alarms are shown and the traffic does not re-route. Trunk discards can be seen with dsptrkerrs. Conditions: Delay is toggled (introduced and then set back to zero) on one of 4 lines between 0 and 100ms using an ADTECH SX/12 line simulator. The other 3 lines are left at 0ms delay. Once the delay has toggled between 5 to 10 times, the whole trunk discards all traffic. Workaround: None. Execute resetcd or dncd/upcd for the trunk to resume functioning.
CSCdt23593	Symptoms: dspchstats on the connection end where VC shaping is turned ON shows Egress VSVD rate set to 6 cps. Conditions: Whenever there is a ABR connection between two UXM port cards with Model C f/w and VC shaping is turned ON on the port the port will start transmitting data out at a rate of 6cps instead of the connection rate. Workaround: Do cnfcon and change the PCR of the connection by say lcps just to invoke reconfiguration of the connection. This clears the problem.
CSCdt58429	Symptoms: After a dncd/upcd, VSI does not come up. Conditions: dncd/upcd is performed and the VSI control channels are not programmed on the card. Workaround: Not service affecting, however if the VSI does not come up, reset the card and the card comes up fine.
CSCdp05824	Symptoms: When ABRFST VPC input to UXM port is broken, no OAM AIS cells are transmitted at far end for this connection. Conditions: All instances. Workaround: None.
CSCdr98036	Symptoms: When CRC is disabled on E1 lines by using cnfln we see the line go into OOF alarm. The line will remain in the failed state until CRC is enabled again on the line. Conditions: The swsw release should be >= 9.3.30 in order to be able to configure enabling/disabling of CRC on E1 lines. Prior to 9.3.30, the CRC is always enabled and this problem will not be seen. Workaround: Keep CRC enabled on the E1 lines.
CSCdp34788	Symptoms: When the Far end equipment generates HP_UNEQ signal or the supervisory unequipped signal, the UXM OC3 port connected to it does not recognize it and so there is a problem. Conditions: The far end has to be connected to the OC3 port and it needs to send either the HP_UNEQ or the Supervisory unequipped signals. Workaround: None.
CSCds11244	Symptoms: After a switchcc, if the active and standby NPMs connection databases are not consistent, SW errors can happen on UXM cards at any time after the switchcc. On 9.1 Switch Software, SW error 21 may be seen. On 9.2 Switch software, SW error 9081 may be seen. Conditions: After a switchcc, switch software on the current NPM does a check on the UXM card to make sure that the connection database on the NPM matches that on the UXM card. All connections on the UXM card but on the NPM database will be deleted. Connections on the NPM but not on the UXM will be added. This feature is required for cleaning up any dangling connections due to database inconsistencies before the switchcc between the active and standby NPM cards. So every time a switchcc occurs, the current NPM has to make sure its database is reflected on the UXM. Workaround: None.
CSCds32782	Symptoms: swerror 9081 is logged when DS0 map is changed on a UXM-E1 line or trunk. Conditions: DS0 map is changed using cnfln/cnftrk. The error does not occur always. Workaround: None, swerror 9081 logged under this conditions can be safely removed.
CSCds43564	Symptoms: UXM-UFMU atfxfst connection. Once the UFMU side had a communication failure and also recovered from the failure, then UXM side would start to have non-compliant cells although traffic was far below the PCR. Conditions: UFMU side had a communication failure and failure recovered. Workaround: 1. dncon/upcon 2. reroute con somewhere, then reroute back 3. change any parameters of the con, such as SCR/PCR, then change it back All above actions will stop increasing non-compliant cells and stop discarding.
CSCdt17534	Symptoms: After seeing several "IMA protocol OK " messages in the log intermittently the IMA protocol between the each ends of the UXM IMA trunk appears to become out of sync. Traffic in one direction sees about 75% data loss, traffic in the other direction is OK. Conditions: Occurs in IMA trunks where the T1's have taken hits. So far every occurrence of the problem was seen with T1's that cross 1/0 DACS (not clear T1). Workaround: 1. Physically removing one T1 from either end and reinserting it after a few seconds will allow the IMA protocol to resync. 2. Resetting the UXM card on the side that sees the discards (resetcd <slot> h).

Boot Code Requirements

Boot Code revision boot_08 is needed for the ACE release.

Unsupported Configurations or Applications.

1. MPLS Controllers other than 7200 series routers.

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

3. The OC3 MMF backcard is not supported for Y-redundancy configuration.

4. Adding more than one controller to a VSI partition is not supported.

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

6. Usage of IMA interfaces is not supported for attaching the LSCs (Label Switched Controllers) or LERs (Label Edged 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:

IOS 12.1(3)T and later

PA-A1 (non enhanced) flavors of T3, E3, and OC3 ATM adapters

[PA-A3 adapters are not supported for multi-VC mode as of 9/2000.]

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

This is a recently discovered issue in 12.1(3)T.

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

a) If the VPI range is reduced, the XTAG interface is toggled down and back up to force LDP/TDP to be reset. This is because LDP currently negotiates label ranges (VPI,VCI ranges) only when the session is established. The info displayed through a "show tag int detailed" command should be correct in this case.

NOTE: The above does not apply to the BPX where the VPI or VCI range cannot be SHRUNK using the cnfrsrc command unless the interface is in the disabled state.

b) If the VPI range is increased, the information is updated in the VSI master but the information is NOT propagated to the XTAG. This is done so that the LSC will ignore the increased range instead of resetting the LDP session which forces VCs to be torn down. The VPI range from the "show tag int detailed" command can be interpreted as the LOCAL range that LDP/TDP used when setting up the session that is active. Changes at the ATM switch level are not reflected in the LSC unless the change explicitly causes the LDP session to be re-established.

3. Only one Xtag interface corresponding to a partition on a UXM interface that has multiple-partitions comes up. Other Xtag interface based on different partitions on the same UXM interface is not coming up.

Turn on "debug VSI errors."

If you see errors that say something of the kind "VPI/VCI in use" or "VCI in use"; the problem is overloading of the 0/32 tag-control PVC.

Example 1: Node tagigx4

a. dspctrlrs for tagigx4, shows two controllers, one each for partition 1 and partition 2.

	tagigx4        TN    Cisco           IGX 8430  9.3.1Z    Aug. 3 2000  11:05 PDT  

                    VSI Controller Information 

	 CtrlrId   PartId     ControlVC            Intfc    Type     CtrlrIP 

        	             VPI    VCIRange 

   	 1         1       0      40-70          3.3      MPLS     6.6.6.6 

   	 2         2       0      40-70          19.3     MPLS     66.66.66.66 

b. Example 2: dsprsrc for 7.1, shows partitions 1, 2 and 3 on trunk 7.1

	Trunk : 7.1 

	 Maximum PVC LCNS: 256             Maximum PVC Bandwidth: 65000 

                                   (Statistical Reserve: 5000) 

        	       State   MinLCN   MaxLCN   StartVPI   EndVPI   MinBW    MaxBW 

	 Partition 1:   E       30       100      50         75       1000     10000 

	 Partition 2:   E       10       100      90         150      1000     10000 

 	Partition 3:   E       10       100      180        240      1000     5000 

c. Xtagatm interface configuration for partitions 1 and 2 on Trunk 7.1

Make sure that only xtag atm interface uses the default tag-control-vc of 0/32. All other xtag atm interfaces on the same UXM interface should use non-defaulttag-control-vcs using the "tag-switching atm control-vc" command.

xtagatm71 configuration on the LSC connected to 3.3, using default tag-control-vc of 0/32

	Current configuration: 

!

	 interface XTagATM71 

	  ip unnumbered Loopback0 

  	no ip mroute-cache 

  	extended-port ATM2/0 vsi 0x00070100 

 	 tag-switching ip 

end

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

 	Current configuration: 

!

	 interface XTagATM71 

  	ip unnumbered Loopback1 

  	no ip directed-broadcast 

  	no ip route-cache cef 

  	extended-port ATM5/0 vsi 0x00070100 

  	tag-switching atm control-vc 90 32 

  	tag-switching ip 

end

4. The URL for open and resolved caveats for IOS release image 12.1.(3)T can be found at: http://www.cisco.com/univercd/cc/td/doc/product/software/ios121/121relnt/121cavs/121tcavs.htm

5. An MPLS LSC on a T3 port cannot see the IGX.

When configuring a Cisco MPLS LSC on T3 interfaces, make sure the payload scrambling option on the UXM T3 line matches the config on the LSC. The default for the LSC is OFF, and the default for the UXM is ON. This can cause a lot of wasted time, since the lines will come UP and CLEAR.

For example, T3 UXM configuration:

dsplncnf 12.6

         tagigx3        VT    Cisco           IGX 8430  9.3.1Z    Aug. 3 2000  10:14 PDT  

         LN  12.6 Config       T3/636                UXM slot:12  

         Loop clock:           No  

         Line framing:         PLCP Idle code:            7F hex  

         HCS Masking:          Yes  

         Payload Scramble:     No  

         VC Shaping:           No  

dspctrlrs

         tagigx3        VT    Cisco           IGX 8430  9.3.1Z    Aug. 3 2000  10:14 PDT  

                    VSI Controller Information 

         CtrlrId   PartId     ControlVC            Intfc    Type     CtrlrIP 

                                 VPI    VCIRange 

            1         1       0      40-70          12.6     MPLS     7.7.7.7 

            2         2       0      40-70          12.1     MPLS     99.99.99.99 

For example, 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 you will see 0.0.0.0.

Firmware Filenames and File Sizes

Table 3 ACE Firmware Application Code

Filename(s)	Size (bytes)
ACE.000 to ACE.023	65536
ACE.024	34590
ACE.img	784

Table 4 ACE Firmware Boot Code

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

Obtaining Documentation

The following sections explain how to obtain documentation from Cisco Systems.

World Wide Web

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

http://www.cisco.com

Translated documentation is available at the following URL:

http://www.cisco.com/public/countries_languages.shtml

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

Cisco documentation is available in the following ways:

Registered Cisco Direct Customers can order Cisco product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco corporate headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).

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.

You can e-mail your comments to bug-doc@cisco.com.

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

We appreciate your comments.

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

Streamline business processes and improve productivity
Resolve technical issues with online support
Download and test software packages
Order Cisco learning materials and merchandise
Register for online skill assessment, training, and certification programs

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

http://www.cisco.com

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.

Inquiries to Cisco TAC are categorized according to the urgency of the issue:

Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.

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:

http://www.cisco.com/tac

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:

http://www.cisco.com/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:

http://www.cisco.com/tac/caseopen

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:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

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)

Table of Contents