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

The MSSBU and CSEBU 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, please 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 will 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.
Pre-First Customer Ship (Pre-FCS)	Feature is not yet available in the Switch Software baseline.
Target Date	This is the date for feature delivery that is supported by current Engineering and Marketing plans. This date is subject to change.

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

Software Release 9.3.11

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

Table 1: Release 9.3.11 Files

File Name	File Size
9311B.000	65536
9311B.001	65536
9311B.002	65536
9311B.003	65536
9311B.004	65536
9311B.005	65536
9311B.006	65536
9311B.007	65536
9311B.008	65536
9311B.009	65536
9311B.010	65536
9311B.011	65536
9311B.012	65536
9311B.013	65536
9311B.014	65536
9311B.015	65536
9311B.016	65536
9311B.017	65536
9311B.018	65536
9311B.019	65536
9311B.020	65536
9311B.021	65536
9311B.022	65536
9311B.023	65536
9311B.024	57698
9311B.img	784
9311G.000	65536
9311G.001	65536
9311G.002	65536
9311G.003	65536
9311G.004	65536
9311G.005	65536
9311G.006	65536
9311G.007	65536
9311G.008	65536
9311G.009	65536
9311G.010	65536
9311G.011	65536
9311G.012	65536
9311G.013	65536
9311G.014	65536
9311G.015	65536
9311G.016	65536
9311G.017	65536
9311G.018	65536
9311G.019	65536
9311G.020	65536
9311G.021	65536
9311G.022	65536
9311G.023	65536
9311G.024	65536
9311G.025	65536
9311G.026	65536
9311G.027	36452
9311G.img	784

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.

5. ELMI for UFM

: The ELMI protocol enhancements for the UFM serves the same purpose as the ILMI enhancements for the UXM, and shares similar mechanisms to reach the neighbor discovery purpose.

6. VSI/MPLS for UXM

This feature provides IGX switches with the capabilities for setting up connections based on the PNNI and MPLS protocols, which allows the user to expand their existing network. VSI is a resource management scheme that allocates IGX resources, needed for setting up connections, such as system bandwidth and channel space, to a number of external connection-management entities which manage calls/connections with PNNI, MPLS, or other protocols.

This feature supports:

Up to 3 VSI partitions per interface.
Up to 3 MPLS controllers (1 controller per partition).
Up to 30 slaves.
VSI slave redundancy.
MPLS controller redundancy (with each controller controlling a different VSI partition).
Dynamic partitioning support.
CWM support for topology displays.
CiscoView support for configuring the partitions.

To add the VSI/MPLS feature, the UXM firmware needs to be upgraded to revision ACB or later and NPM-64B cards are required. The UXM firmware upgrade to revision ACB or later first requires that the run-time firmware be upgraded to an intermediate version, revision ABJ. However, before upgrading the firmware to revision ABJ, upgrade the UXM boot code to boot 8.

If Release 9.3.10 has not been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACB or later:

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

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

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.

If Release 9.3.10 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.11.

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

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 will generally be 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 will support 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 will block 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 will 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 will remain 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 will warn and automatically disable 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 will enable 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 will allow 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.11

None.

Clarifications for Release 9.3.10

1. Only the cell discard Qbin statistics for the allowed Qbins will be 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 will effectively enable 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 will send its interface information to the neighbor if queried by the neighbor.
: N—The BPX will not send its information to the neighbor.
: The BPX will always query 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 will send its interface information to the neighbor if queried by the neighbor.
: N—The IGX will not send its information to the neighbor.

The IGX will always query 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 will need 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 will be able to 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 will be 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 will show part of the 800-level number. The display will show 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 will show 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 will be blank spaces and the user will see 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 will act just like dsplog and will terminate immediately. But for multiple page logs, it will allow 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 will behave 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 will contain 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.x

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 will now report 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 will mismatch the card.

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

For a VSI controller, the reported value will be 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, will 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 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.

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

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

If Release 9.3.10 has not been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACB or later:

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

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

If Release 9.3.10 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.11.

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.

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 will run with:

Any MGX 8220 Release 4.0, 4.1, and 5.0

Cisco WAN Manager (Cisco StrataView Plus) version 10.3

Cisco View version 2.00
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 YAL
MGX 8850 version 1.1.23 or later
SES (IGX feeder) version 1.0

Note VNS interworking is supported in Release 9.3.11.

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

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 will fail 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 will work 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 will add 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.x

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, will result 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 will 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 will be sent to all MGX 8220 feeders immediately before a hitless rebuild takes place. The feeder alert message will temporarily disable the LMI polling from the MGX 8220 feeders. The MGX 8220 polling will resume 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.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 will 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.x

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 will be 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. For a virtual trunk on a BXM/UXM, the Transmit Trunk Rate (the transmit rate of the virtual trunk) is configurable to match the PCR value of the subscribed public VPC service. In this release, the actual shaping rate for a virtual trunk is higher than the configured Transmit Trunk Rate (CSCdm80482). The actual virtual trunk shaping rates are 1/(n x 680 x 10^-9) cps, where n is an integer from 1 to 29,411. In this release, the user-configured Transmit Trunk Rate is rounded to the next higher (as opposed to lower) actual shaping rate.

: To configure a virtual trunk so that the actual shaping rate is no greater than the PCR value of the subscribed public VPC service, the following steps can be taken:

Step 1 Determine the n such that 1/(n x 680 x 10^-9) cps (the actual shaping rate) is no greater than the PCR value of the subscribed public PVC service. For example, if the PCR value of the subscribed public PVC service is 10 Mbps or 23,585 cps, the n will be 63 and the actual shaping rate is 23,342.67 cps.

Step 2 Configure the Transmit Trunk Rate for the virtual trunk to be less than 1/(n x 680 x 10^-9) cps but greater than 1/((n+1) x 680 x 10^-9) cps. For example, if the PCR value of the subscribed public VPC service is 10 Mbps or 23,585 cps, configure the Transmit Trunk Rate for the virtual trunk to be less than 1/(63 x 680 x 10^-9) = 23,342.67 cps but greater than 1/(64 x 680 x 10^-9) = 22,977.94 cps.

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

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

6. 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 will be 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 will assume 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 will perform 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 will not be maintained across a rebuild.
Some will be re-enabled 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.

7. UVM cards in Y-redundancy will 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.

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

9. 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, will be delayed as provided by the parameter.

10. 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, will all be 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.

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

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

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

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

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 will support up to a total of 16 feeder trunks and each feeder trunk will have 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 will be 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 will cause 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 will send 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 will be a loss of continuity.

8. When deleting the last trunk from a node, there is a known limitation with the switch software. The deltrk command should always be executed on the node that remains as part of the network, rather than from the node that ends up being removed from the network. This is to ensure that all the necessary updates are sent to the rest of the network (CSCdi85134). Also, If the command is not used as recommended here, a software error 419 could occur (CSCdi91285).

9. Due to Trunk-Based Loading, any commands having to do with trunk loading and the load model (dspload, chklm, dsplm, and so on) need to be done only after waiting a certain period of time. This time is directly a function of the trunk load update interval time (as configurable) plus the conditional update latency time.

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

11. On a heavily loaded BPX 8600 node, during connection rerouting, the status of a particular connection is indicated as OK even though the line status of the other end of the connection is listed as failed. The connection is in fact OK, because the conditioning of the connection (to update the status for both ends) is done by a low-priority process so that the rerouting of the connections can be given high priority. The status will be eventually updated (CSCdj10762).

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

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

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

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

16. 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 will occur instead of a switchcc (CSCdj30811).

17. 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 will not be correctly simulated by doing a dncd (down card) on the active card. Using dncd will cause cell discards. (CSCdj08923).

18. 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 will throttle back, whereas UBR will 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).

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

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 will make the joining of this node much simpler, and will avoid the problem of node renumbering an active network, as described below.

2. Currently, T3-3 and T3-2 back cards are not interchangeable between ASI and BNI front cards, as has been the case since the introduction of these cards. The back cards must be configured using cnfbkcd (with setnovram) so as to avoid back card mismatch (CSCdj41999).

Required Workarounds for Release 8.x

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 will run with Release 4.0.0x, 4.1.0x, or 5.0.0x of the MGX 8220.

Compatibility Matrix

MGX 8220 Firmware Compatibility
MGX 8850 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.15	5.0.10	4.1.08	4.1.00
ASC Boot	ASC	1.0.03	1.0.01	1.0.03	4.0.04
ASC/2 FW	ASC	5.0.15	5.0.10	4.1.08	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.15	5.0.10	4.1.08	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.20	4.0.13
FRSM-4E1	FRSM-4E1	4.0.22	4.0.19	4.0.20	4.0.13
FRSM-4T1-C	FRSM-4T1-C	4.0.22	4.0.19	4.0.20	4.0.13
FRSM-4E1-C	FRSM-4E1-C	4.0.22	4.0.19	4.0.20	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.16	4.0.11
CESM-4E1	CESM-4E1	4.0.17	4.0.15	4.0.16	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.13	4.1.05	4.1.08	4.1.00
CESM-8E1	CESM-8E1	5.0.13	4.1.05	4.1.08	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.20	4.0.13
AUSM-4E1	AUSM-4E1	4.0.21	4.0.19	4.0.20	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.14	5.0.10	4.0.20	4.0.13
FRSM-8E1	FRSM-8E1	5.0.14	5.0.10	4.0.20	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.13	5.0.10	4.0.21	4.0.14
AUSM-8E1	AUSM-8E1	5.0.13	5.0.10	4.0.21	4.0.14
AUSMB-8T1	AUSMB-8T1	5.0.13	5.0.10	4.0.21	4.0.19
AUSMB-8E1	AUSMB-8E1	5.0.13	5.0.10	4.0.21	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.13	4.0.16	4.0.17	4.0.11
FRSM-HS1/B	FRSM-HS1/B	5.0.13	4.0.16	4.0.17	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.20	4.0.13
IMATM	IMATM-E3E1	n/s	n/s	4.0.20	4.0.13
IMATM	IMATMB-T1	5.0.13	5.0.10	4.0.20	4.0.13
IMATM	IMATMB-E1	5.0.13	5.0.10	4.0.20	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.31	1.1.31
PXM1-2-T3E3	PXM1-2T3E3	1.1.31	1.1.31
PXM1-4-155	PXM1-4OC3	1.1.31	1.1.31
PXM1-1-622	PXM1-OC12	1.1.31	1.1.31
MGX-SRM-3T3/B	SRM-3T3	n/a	n/a
AX-CESM-8E1	CESM-8E1	10.0.20	10.0.12
AX-CESM-8T1	CESM-8T1	10.0.20	10.0.12
MGX-AUSM-8E1/B	AUSMB-8E1	10.0.20	10.0.12
MGX-AUSM-8T1/B	AUSMB-8T1	10.0.20	10.0.12
MGX-CESM-T3	CESM-T3	10.0.20	10.0.12
MGX-CESM-E3	CESM-E3	10.0.20	10.0.12
AX-FRSM-8E1/E1-C	FRSM-8E1	10.0.20	10.0.12
AX-FRSM-8T1/T1-C	FRSM-8T1	10.0.20	10.0.12
MGX-FRSM-HS2	FRSM-HS2	10.0.21	10.0.12
MGX-FRSM-2CT3	FRSM-2CT3	10.0.21	10.0.12
MGX-FRSM-2T3E3	FRSM-2T3	10.0.21	10.0.12
MGX-FRSM-2T3E3	FRSM-2E3	10.0.21	10.0.12
MGX-FRSM-HS1/B	FRSM-HS1/B	10.0.20	10.0.12
MGX-VISM-8T1	VISM-8T1	2.0.(0)	1.5.05
MGX-VISM-8E1	VISM-8E1	2.0.(0)	1.5.05
MGX-RPM-128M/B	RPM	12.1(3)T	12.1(3)T
MGX-RPM-PR	RPM	12.1(5)T	12.1(5)T
CWM		10.3	10.3

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

IGX 8400 Firmware Compatibility

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

If Release 9.3.10 has not been loaded onto the node, the following steps are required to upgrade the UXM firmware to revision ACB or later:

Step 1 Execute a graceful upgrade to Release 9.3.10 or greater.

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

If Release 9.3.10 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.11.

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

PCB Description	dspcds Name	Card Name in Firmware Image	Model	Latest F/W	Min F/W
NPM 32 boot	NPM	NPM	B	RBS	RBS
NPM 64 boot	NPM	NPM\|NPM-64	C	RCS	RCS
NPM-B 32 boot	NPM	NPM\|NPM-32B	E	RES	RES
NPM-B 64 boot	NPM	NPM\|NPM-64B	F	RFS	RFS
IGX-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-HDM	HDM	HDM	C	SCF	SCF
IGX-LDM	LDM	LDM	C	LCC	LCC
IGX-NTM	NTM	NTM	E	NEK	NEK
IGX-NTM (B)	NTM	NTM	F	NFK	NFK
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-UVM	UVM	UVM	D	DDF	DDF
IGX-UVM	UVM	UVM	E	DEF	DEE
IGX-UXM	UXM	UXM	B	ABJ	ABH
IGX-UXM	UXM	UXM	C	ACC	ACB
IGX-UXME	UXM	UXM	B	ABJ	ABH
IGX-UXME	UXM	UXM	C	ACC	ACB

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-ET3/B	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
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	B
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

The following is the list of known anomalies in this Switch Software delivery. Included with each is a brief discussion of the problem. A more in-depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
CSCdk77478	Symptom: Large number of card polls are generated when an SNMP walk is done for a connection or port stats, which greatly decreases the amount of idle time. Conditions: The excessive card polling occurs when an SNMP walk is done on IGX connection or port stats or on BPX port stats. Workarounds: None. Customer Impact: The impact is mainly performance. The system response time will slow down (but not stop) when these requests are occurring. The task that generates these polls is at the same priority as the other user input tasks, so important events such as reroutes, etc. will not be blocked from running. The main observation will be that the command line interface is not as responsive and idle time drops.
CSCdk91790	Symptom: Switch software system idle time is below 30% when more than ten UVMs are activated. Conditions: The switch software polls each activated UVM for modem status every second for each port. Switch software also spends time processing the responses of the modem polling. When many UVMs are activated, the modem polling handling consumes system time and resources (buffer queue) which affect system performance. UVM firmware supports asynchronous event to report modem event. Switch software needs to stop polling modem status if the firmware in UVM supports the asynchronous event. Workaround: Use cnfnodeparm 46 to increase polling timer to improve system performance.
CSCdp45833	Symptom: Users of VNS may experience poor voice quality. a dspchst command on the connections shows data in one direction. When the xlat_verify command is run software error 332 is logged with FFF1 in the data field. This is usually on the slave and via nodes of the leftover SVC. The master node shows it as deleted. A dspcon command n the slave and a dspviacons on the vias show the leftover connection. Conditions: CSCdm86633 in Release 9.1.16 fixed most occurrences but not all of the dangling SVC connections. Occasionally poor voice conditions occur. Workaround: Manual updates could be sent through the updates 3 * command to clean-up dangling SVC lcons.
CSCdp51531	Symptom: A software error 21 is logged when a UBR connection is added on an ASI-155 card. Conditions: Prior to Release 9.1.17, this error was logged when the UBR connection has CLP disabled, and the PCR was less than 10 cps. In Release 9.1.17 and later, the error is logged under two conditions; when the UBR connection has CLP enabled, OR when CLP is disabled on a connection with PCR is less than 10 cps. Workaround: When adding the connection, do not enable the “CLP Setting.” This will avoid a software error and ensure that the connection is programmed correctly.
CSCdr79193	Symptom: The UXM OC-3 card goes into Active-F state when any port/trunk is in LOS. Condition: This only happens on a UXM OC-3 card when any of the ports/trunks is in LOS state. Workaround: Down the port/trunk.
CSCdr88977	Symptom: A software error 618 (AUTO_DEL_NIBTOPO) is logged during a full node rebuild. Condition: This only happens if an inconsistency is found between the trunk_config and the topo_info of a particular trunk during anode rebuild (For example, Trunk_config says that there is no trunk upped but the corresponding top_info says that there is trunk upped). Workaround: None.
CSCdr93214	Symptom: A software error 504 (memory error) occurs, followed by a software error 502. The 504 memory error has historically been found to be caused by a bad BCC. Workaround: Replace the BCC.
CSCds04587	Symptom: Software error 20 is logged. Conditions: When the UVM card receives a packet with an out of range VCI. Workaround: None.
CSCds06534	Symptoms: Software error 1417 is logged at the master node when connections reroute. Conditions: On IGX and BPX nodes using the cost-based routing feature. Workaround: Configure the maximum routing bundle size to “1” (cnfcmparm). Connections will take longer to reroute. Disable the cost-based routing feature.
CSCds61240	Symptoms: When adding connections on a BPX node, “Unknown Response (17)” appears. This occurs while adding AUSM to AUSM connections. Conditions: On the remote end, the total minutes exceeds the port speed and the number of connections are not compatible with the poll rate. This occurs on BPX nodes running 9.3.10 MGX PXM firmware running 1.1.31 AUSM running 10.0.20. Workaround: Use cnfsysparm to change the pooling rate to 10 minutes which allows up to 8000 connections.
CSCds64587	Symptom: Copycons allows atfx connections to be added on FRM card which does not support atfx connections. Conditions: Observed on IGX. addcon cannot add atfx connections to FRM card while copycons can. Workaround: None.
CSCds72447	Symptom: Cost-based route recovery allows route to exceed connection cost cap. Conditions: Cost-based routing could not find a path for the connection. New route calculated exceeded the connection cost cap. Observed in 9.1.24 and 9.2.35. Workaround: Possible workarounds include using cnfpref to specify a preferred route. This provides a route for the connection. Cost-based routing can be disabled using cnfcmparm. Also, the trunk cost can be tuned with cnftrk. The connection cost cap can be configured with cnfrtcost. Further Problem Description: dsprrst “# cost exceeded hop recovery” indicates the connection cost cap was exceeded following cost-base route recovery.
CSCds75054	Symptom: Switch software logs error 9093 on the standby Y-red BXM after a full rebuild. Conditions: Unknown. Workaround: To ensure that switch software programs the BXM hardware with the correct configuration, rebuild the BXM. 1. Determine the slot on which the BXM firmware reports the problem from the dspswlog screen. For the sample dspswlog screen below, the Most-Significant-Byte (MSB) of the “Data” column ("06"06005D) indicates the BXM slot which reported the problem. a_bpx TN Cisco BPX 8620 9.3.2M Nov. 18 2000 22:50 PST Active CC's Software Log No. Type Number Data(Hex) PC(Hex) PROC SwRev Date Time 1. Error 9093 0606005D 30467B7A TRNS 9.3.2M 11/18/00 15:36:26 Last Command: dspswlog Next Command: 2. Enter the command: resetcd <slot> h where <slot> is the standby y-red BXM slot.
CSCds80136	Symptom: LMI/ILMI statistics for the port interfaces on Y-red cards are not displayed correctly. Conditions: This problem only happens when the secondary card of the Y-redundant pair is the active card. Workaround: None.
CSCds82820	Symptom: Software error 55 logs on all nodes running 9.2.xx, 9.3.00, 9.3.05. The dnib <node> displays the node type as "????" where NPM running on node is 64k/4M BRAM. Condition: This only occurs when there is a mix of nodes running revisions prior to Release 9.3.10 and nodes running Release 9.3.10 and later and with the following conditions/events: 1. Full rebuild on node running revision 9.3.10\|9.3.11 and the NPM is 64k/4M BRAM. 2. Nongraceful upgrade to 9.3.10 or later (on nodes having NPM 4M BRAM). Workaround: Upgrade all nodes running releases prior ro 9.3.10 to Release 9.3.10 or later. This only impacts the display of <dnib> and there are no service/operation impacts.
CSCds85758	Symptom: The UXM card on an IGX feeder node, which has the trunk connected to the routing node, goes into mismatch state after upgrading (graceful/nongraceful upgrade) to Switch Software Release 9.3.00 or later. Conditions: This will only happen on an IGX feeder node with following configuration: voice/data connections terminated on an UXM feeder node. This occurs on all UXM Model C firmware and on Model B firmware from revision ABK and later. Workaround: Case 1: If the switch software supports PCR less than 50 cps feature and the firmware doesn't support the PCR < 50 cps feature, then the workaround is to burn UXM firmware that supports the PCR < 50 cps feature. Case 2: If the switch software and firmware supports the PCR < 50 cps feature, then the workaround is to reset the card (which is in a mismatch state). This occurs when the firmware is upgraded before the software.
CSCds86461	Symptom: Configuring an additional Virtual Trunk VPI on NODE_B using the same interface as an existing Virtual Trunk can cause unreachables. The communication breaks are between NODE_B and other nodes in the network that use the existing virtual trunk. CC traffic that uses the existing Virtual Trunk as a via path to other nodes are not affected. Workaround: To clear the unreachability (or fix the last hop channel) the BXM card must be reprogrammed (switchcc or resetcd on the BXM). Iif the VPI configuration is not altered from the initial setting when the trunk is first upped, this problem does not occur.

Known Anomalies from Previous Releases

Bug ID	Description
CSCdr93214	Closed. This problem could not be consistently repeated.
CSCdp85319	Duplicate of CSCdm29466 which was fixed in Release 9.2.33 but has not been integrated in Release 9.3.
CSCdp86866	Duplicate of CSCdr15924 which was fixed in Release 9.3.05
CSCdr10771	Closed. This problem could not be consistently repeated.
CSCdr71825	Closed. This problem could not be consistently repeated.
CSCds04587	Closed. This problem could not be consistently repeated.
CSCds06534	Duplicate of CSCdr92045 which was fixed in Release 9.3.10.

Problems Fixed in Release 9.3.11

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

Bug ID	Description
CSCdm07690	Symptom: Active logs a software error 586 and resets the standby CC. The secondary controller card is reset. Customer loses redundancy during that time Conditions: For this problem to occur the node needs: 1. To have its dynamic memory region very fragmented or so much of it allocated that memory allocation overflows occur. 2. An event that causes many standby updates to occur. Workaround: Regular, controlled switchcc will cause the active and standby’s to switch positions. When the active becomes standby, all of its allocated memory is freed and any new allocations start with a clean memory slate, so fragmentation is cleaned. Essentially, this workaround is where the standby becomes unavailable for a small amount of time. Further Information: The various memory regions have different minimum block sizes, however, the mechanism that checks if the standby queue is consuming too many blocks is always using the minimum block size for one of the many possible memory regions. This region has one of the largest possible block sizes. With a fragmented node, or when most of the dynamic memory is already allocated, it is possible to prematurely report a standby queue overflow because a minimum block size is used that is larger than the true minimum block size of the overflowed region.
CSCdm07982	Symptom: The failure of a UFM card triggers a hardware failure of an ALM in the same node. The ALM removes and reinserts itself, logs a software error 21, and also logs a hardware failure card error. Connections may be rerouted. Conditions: Occurs if a node with both a UFM and ALM has a failure of the UFM. Workaround: The problem fixes itself but is disruptive to the network because connections can be rerouted during trunk failure. No workaround.
CSCdm42912	Symptom: When configuring a prefer route of 10 hops using CWM Service Agent, the request failed will error message that the “Route contains too many hops for its connection type (9)”. Same request works from the CLI of node. Conditions: No special conditions are required. Workaround: Use the CLI to specify 10 hop pref routes.
CSCdm56535	Symptom: When trying to collect ATM statistics the MIB is being initialized but the entry for siw connections are never populated with anything but 0’s. The entries from the same entry (ATM_END_PT_STAT_ENTRY) for PVCs and PVPs are being populated. Conditions: When collecting statistics from the ATM end point of ATFR connections added between the two IGXs. Workaround: Collect statistics through CLI using dspchstats. Further Problem Description: The problem is due to the connection type. The value of the Connection Type (Conn Type) is always set to FRELAY in the case of ATFR conns in IGX.
CSCdm60699	Symptom: Port configured for Annex_D LMI and Async updates will send async updates showing a PVC is active when the PVC’s VCQ fills to approximately 75%, and reduces to 25%. Conditions: No relevant conditions are required in the network to see this problem other than the connections VCQ filling. The problem was noticed after the customer started a program to reduce the size of connection VCQ’s. It can cause Bay router DLCI’s to lock up. The only way to restore the Bay DLCI is to either DOWN and UP the PVC, or reset the Bay DLCI. Workaround: Switch Async Updates off, however this does prevent the CPE from detecting a change in PVC status until a full status is sent by the switch. Can also make sure the VCQ does not reach 75% by using foresight, and making sure there is enough bandwidth in the network to prevent congestion If Async Updates must be left enabled, the following step can reduce the amount of Async Updates caused by exceeding the RNR Threshold. This workaround measure will reduce the amount of Async Updates due to reaching the RNR: 1. Temporarily configure the port to Stratum LMI 2. Change Upper RNR Threshold to 100% (leave lower RNR Threshold as is). 3. Change the port back to the other LMI (such as Annex D). This will force the VCQ level to be at 100% before an Async update is sent due to exceeding this level.
CSCdp50091	Symptom: data_channel table not updating with 9.1.15 software code. The data_channel table in the SV+ stores information on the HDM/LDM port. Following an upgrade from pre-9.1.11 release to a 9.1.11 or higher release the data_channel table is empty on SV+. The node is fine. Conditions: Upgrade from a release earlier than 9.1.11 to a release 9.1.11 or higher. Workaround: Configure the port using cnfchutl or cnfchdfm. Issue is corrected in Switch Software Releases 9.1.24 or 9.2.34.
CSCdp53419	Symptom: UXM connection channel resynchronization is not performed on the card configuration. Conditions: UXM card insertion and reset. IGX node reset during SVC provisioning. Software errors 612 and/or 614 are seen in the error log during the database resynchronization. Software error 21 is logged on UXM slot in response to the connection configuration command with function code 0x52. Workaround: 1. Reset the UXM card (resetcd <slot> h) during off hours. This clears the existing card programming and reconfigures the cards. 2. Format a control bus message using scp to deactivate the channel on the UXM. This should be done by Cisco only. Further Problem Description: Card configuration message contains an incorrect length for the LCN verification object. This causes dangling LCNs to not be deleted following database resynchronization after a node reset.
CSCdr03517	Symptom: Info Bus A Reports 1 Error(s) (CNTL) appears frequently in the event log. Conditions: The problem happens randomly whenever a (one or more than one LDM) card is in the chassis and is not in a down state. If the card is in standby, it will produce the errors. The problem also happens when background testing is turned off. Workaround: Downing all LDM cards in network gets rid of the constant error message in logs.
CSCdr58956	Symptom: Connection only adds from one end with Cost-Based Routing. Conditions: This was observed on a path that is 10 hops. Appears in Switch Software 9.1.16. Workaround: Use cnfpref to specify a preferred route. This will provide a route for the connection. Cost-based routing can be disabled using cnfcmparm. Also, the trunk cost can be tuned with cnftrk to force the connection to have a route length of 10 hops or less. Further Problem Description: dsprrst indicates the connection failed to route using cost-based routing because the route length constraint of 10 hops was exceeded. Operational solution is to provide an enhancement to recover after cost-based route selection failure. If the cost-based route algorithm fails to find a route, it will invoke the hop-based route selection algorithm to calculate a new route for the PVC or SVC. The new route is used even if the trunk cost on the new path exceeds the configured cost cap for the connection.
CSCdr63174	Symptom: After disabling (any of) Qbins 10-15 on UXM/BXM interface, the MPLS/PNNI controller does not reroute traffic flowing though that Qbin. Condition: This happens only when MPLS/PNNI controllers are used; and when Qbins 10-15 are disabled using cnfqbin command. Workaround: Do NOT disable Qbins 10-15 using cnfqbin command.
CSCdr65152	Symptom: Statistics from the MIB entry for fast packet trunk statistics does not update objects under this subcategory return counters of 0. Conditions: This has been observed in 9.1.11, 9.2.23, and 9.2.30. Workaround: Collect statistics using Statistics Collection Manager (SCM) instead of snmp.
CSCdr71482	Symptom: dsptrkstats fields Percent load TX and Percent load RX show incorrect values, often greater than 100%. Conditions: Always occurs. Workaround: None Further Problem Description: In most cases the percentage displayed is a factor of 10 high, for example, 96.3% displayed is actually 9.63%. However, for high data rates on high rate interfaces, OC3 and above, the percentage displayed is unpredictable.
CSCdr74031	Symptom: After adding a BPX node to a network, there are problems with voice connections. Conditions: Observed with 9.2.33 Switch Software on IGX and BPX nodes. The IGX nodes had some cnfcmb parameters configured to non default values. These parameters returned to their default values when the BPX was added. Workaround: After adding the BPX, use cnfcmb on any IGX to reconfigure the parameters. Further Problem Description: The protocol for combine timeout parameters is to accept the highest value. This will cause a problem on IGX nodes if a parameter has been configured to less than the default value and a BPX is added with the default values. The IGX nodes will take the higher value from the BPX. The BPX does not have the cnfcmb command, so the parameters on the BPX cannot be configured to match the network prior to adding the BPX to the network. A change has been implemented to give parameters from an IGX priority when received by a BPX. The BPX will accept the IGX parameters, even it they are lower. The IGX has been modified to not accept combine timeout parameters from a BPX, even if they are higher. This change allows the BPX to continue to maintain a system parameter database which is consistent with the IGX database, but not impose its combine timeout values on an IGX in special circumstances where they may be different (such as adding a BPX to a network with IGXs).
CSCdr74447	Symptom: VC Depth is not set to the correct value during the addition of PVC from IGX end of ATFR connection. Conditions: ATFR connection added from IGX end. Workaround: Add connection from BPX end. Further Problem Description: The connection between the feeder node and the routing node is a ATFR connection. And the problem is occurring for all type of atfr connection added between the IGX and BPX from IGX side. The ATFR connections added from BPX side are modifying the vc_q value as set during addcon. Bug CSCdm68968 address the issue of atfr connections added between IGX.
CSCdr74841	Symptom: Routing table entries on NTM card are not displayed using drtbl. Also, not able to read routing table in the case of UXM. Condition: This problem exists since 8.1.xx. Workaround: drtbl command is not applicable on UXM card. In the case of NTM, use dsptrns to verify channel programming.
CSCdr74919	Symptom: The port status lights on the BNI card are not extinguished when expected. Conditions: If more than one trunk is up on a BNI card and then one of the trunks is downed using dntrk, the port status light for that trunk stays lit. Workaround: There is no workaround. The problem is benign because the trunk is actually downed correctly. It is only the light that is incorrect. If all trunks on the BNI card are downed, all of the port status lights will then be extinguished.
CSCdr78404	Symptom: Voice delay of approximately three seconds on both endpoints when routed on UXM virtual trunk. Conditions: Only occurs when the voice connections are routed on UXM virtual trunk. Workaround: None.
CSCdr82206	Symptom: The Active NPM in slot 2 cannot communicate with any of the UXM cards in the IGX shelf which has an active NTM trunk card. Hence, some or all of the UXM cards in the IGX chassis are in “Unavail” state (dspcds). Conditions: The problem does NOT occur if the active NPM is in slot 1 or the IGX does not have any active NTM trunk card. The problem may occur after one of the following events: 1.Node rebuild on NPM in slot 2 (resetcd 2 h) 2. switchcc to switch to the NPM in slot 2 3.cnfbusbw to increase the UBUs that are allocated to the UXM cards while NPM in slot 2 is the active NPM. 4. Activating a new UXM card Workaround: 1. switchcc to make NPM in slot 1 the active NPM. Limitation: NPM in slot 2 becomes an unreliable standby NPM if the IGX still has at least one active NTM. 2. Deactivate all the active NTM trunks on the IGX. Limitation: Cannot use the NTM (T1/E1) trunks in the IGX. 3. Avoid putting an active NTM in slot 3. Putting an UXM (active or standby) in slot 3 would reduce the chances that the problem would occur. Limitation: May have to rearrange cards in the IGX chassis. Further Problem Description: The root cause of this problem is described in CSCdk43303.
CSCdr83296	In the following topology BPX - BXM - trunk - BXM - BPX When adding two VT’s over this physical trunk and then creating a resource partition on the second VT the nodes become un reachable.
CSCdr95419	Symptom: delapsln is executed without confirmation when performing a forced switch from working to protection line. Conditions: Protection line active. delapsln timed out waiting for user input and executed delapsln anyway. Workaround: None
CSCdr95604	Symptom: The transmit rate for UXM regular and virtual trunk cannot be changed after the trunk is added. Conditions: This DDTS is an enhancement for the UXM trunk including T1/E1, T3/E3 and OC3 regular trunk and virtual trunk. Workaround: None
CSCdr97442	Symptom: The statistical reserve value for a trunk sent to Ciscoview/CWM is incorrect. Conditions: The following conditions are needed for this problem to occur. 1) One or more trunks upped. 2) A trunk has one or more VSI partitions enabled, with non-zero VSI bandwidth. 3) dsptrkcnf <trunk #> shows the correct statistical reserve value. 4) Ciscoview -> Trk # -> Configure -> IGX: More ATM Trk Config, and CWM -> NW Browser -> Routing Trks -> Trk # show the statistical reserve as (actual statistical reserve + sum of VSI BW for that trunk). Workaround: No workaround. This has been fixed. Further Problem Description: Internally, SWSW stores the sum of the Statistical reserve value and the VSI bandwidth in one field. When accessing the statistical reserve, the VSI bandwidth should be subtracted. This was not done in the SNMP get function, that gets the atmTrk table (trunk configuration) for CiscoView/CWM.
CSCdr98254	Symptom: It is possible to download an IGX image onto a BPX or a BPX image onto an IGX. There is no check to prevent this. Conditions: On a switch with redundant processor cards, this should not be a problem with graceful upgrades. The incorrect image could be downloaded into flash memory, but the standby processor would never come up to standby state. It would not be possible to switchover to the incorrect software. It would be possible to lanbtld an incorrect image, and then the card would not come up. Workaround: Software image names always end in a B for BPX images, and they end in a G or an R for IGX images. Check the name to make sure it is the correct image before loading it onto a switch.
CSCdr98400	Symptom: 1. Cannot run debug command dbramidx in R92 2. The database names on the IGX do not match the literal numbers (i.e. DB_TRUNK_CNFG which has a value of 135 is being displayed for database entry 123) Workaround None. Do not rely on the database names, refer to the number instead.
CSCds04784	Symptom: When copycons command is used to create one or more connections with a template connection that has its preferred path set, the new connections do not inherit the preferred path of the template connection. Condition: This is an expected behavior of the copycons command. Workaround: After the connections are created by copycons, use cnfpref to configure the preferred path of each of the new connections.
CSCds07761	Symptom: Software error 103 is logged when a UXM card is inserted to the node. Condition: This happens only when there are no UBUs available on the node to establish the CMI link for this card. Workaround: Use cnfbusbw to reduce the UBU usage of another UXM and then insert the new card.
CSCds08777	Symptom: The switch accepts a tftp request for UFM and image name Y._._ Image name starting with “Y” is for UFMU (UFM is UFM-C) Trying to burn firmware the following error message is displayed: Image name must start with ’ ’ for the UFMU in slot 4 Next Command: Workaround: Use UFMU as CardName in the dnld.sw file.
CSCds08808	Symptoms: Q depths of OC12/T3/E3 trunks are set to default Q depths of OC3 trunk. Conditions: The trunk transmit/receive rate is changed by the cnftrk command. Workaround: Use the cnftrkparm command to change the Q depths to the correct values.
CSCds09778	Symptom: CBR cells get dropped on a BXM trunk interface Condition: This happens only when the CBR connections with PCR <= 50 cps is routed over that trunk. Workaround: Change the PCR of all the CBR connections to be greater than 51 cps and reset all the BXM cards in the path of the connections.
CSCds10839	Symptom: A negative value of statistic reserve is prompted when reducing the Trunk Transmit Rate using cnftrk. Conditions: When an attempt is made to reduce the Trunk Transmit Rate to a value less than the (VSI bandwidth + stat reserve) configured on the trunk. This is seen only in release 9.3.10. Workaround: Do not attempt to reduce the Trunk Transmit Rate to a value less than the (VSI bandwidth + stat reserve) configured on the trunk.
CSCds10851	Symptom: There are 2 problems that are described here. 1. When the stat reserve for an IMA trunk is increased (using cnftrk), the software does not check whether the number of retained links is enough to support the new stat reserve. If some of the physical lines on the IMA trunk go down, leaving only the configured number of retained links active, the trunk shows no alarm. Because there is not enough bandwidth for the stat reserve, CC traffic may get dropped resulting in unreachabilities in the network. Also, if an attempt is made to do a cnftrk on the same trunk later, the software will then warn the user about the number of retained links. 2. When the VSI min. bandwidth for a partition on an IMA trunk is increased (using cnfrsrc), the software does not check whether the number of retained links is enough to guarantee the minimum bandwidth. If some of the physical lines on the IMA trunk go down, leaving only the configured number of retained links active, the trunk shows no alarm. Because there is not enough BW for the minimum VSI BW guaranteed, there maybe some drop in VSI traffic. Also, if an attempt is made to do a cnftrk on the same trunk later, the software will then warn the user about the number of retained links. But the warning will not mention VSI BW. It will only mention the stat reserve. Conditions: These 2 problems happen only for IMA trunks. They manifest only if the number of retained links is reduced to a value which less than the minimum required to support the stat reserve and the VSI BW. Reducing the number of retained links on an IMA trunk by itself will not cause loss of traffic. Only if some of the physical lines on the IMA trunk fail leaving only the number of retained links active will there be any traffic loss. Problem 1 has been confirmed as present in 9.3.05 & 9.3.00. It has probably existed since the first release that the added IMA trunks feature. Problem 2 is new in 9.3.10. Workaround: 1. When increasing the stat reserve on an IMA trunk, ensure that the new value of stat reserve can be supported with only the number of retained links active. 2. When increasing the VSI minimum bandwidth on an IMA trunk, ensure that the new value of VSI bandwidth can be supported with only the number of retained links active.
CSCds11473	Symptom: A connection got deleted automatically, immediately after it was added. The event log shows the message “Connection slot.port.vpi.vci collided with VSI”. Conditions: SWSW: 9.3.11 UXM FW: Any release after ACB. This happens only if the vpi.vci on the slot.port was being used by a VSI controller. Workaround: This is NOT a bug and does not need a workaround. The deletion of connection will never happen if the user does not attempt to add a connection with a VPI and VCI that is already being used by a VSI controller (for e.g.: for an MPLS signalling-vc). Further Problem Description: When the user issues an addcon command, if the UXM FW detects that a VSI connection already exists on the slot.port.vpi.vci, it will not let the AR addition go through. Instead, the UXM sends a special 0x02 message to SWSW. This message will cause SWSW to delete the connection that was being added. Please note that on the IGX, unlike other 0x02s from FW, this special 0x02 will not cause the dspslotmsg trace to be disabled.
CSCds12523	Symptom: Interval LMI statistics are not collected when LMI is enabled. Conditions: The following conditions are needed for this problem to occur. 1) TFTP/USER LMI statistics are enabled for a port. 2) LMI protocol is enabled for the port. 3) dspportstats <port #> displays summary LMI statistics. 4) LMI interval statistics are not collected/displayed. Workaround: No workaround. This has been fixed. Further Problem Description: The data for each Interval statistic enabled is collected in a statistic record, and displayed at the end of the collection time. While requesting statistics from the UXM card, the “response pending bit” in these statistic records should be SET to signify that data is being requested for that statistic record. If the pending bit is not set, at the end of the collection time, SWSW assumes that no data has been collected for that record. As a result, at the end of the collection time, no data is displayed for these interval statistics. The code to set the pending bits for the LMI statistics records was missing and has been added. This is why summary statistics were collected while interval statistics were not.
CSCds13718	Symptom: Software error 50 may occur on BPX node. Conditions: BPX software version 9.2.23 and BXM FW MF27. Workaround: None.
CSCds13766	Symptom: The dsptrkerrs command may show the incorrect Unavailable seconds auto statistic for the trunk type (OC3, T3/E3) or may not show any unavailable seconds auto statistic. Conditions: When there is a combination of regular and virtual trunks in a node. Workaround: Use the dspphyslnstathist command to show the auto statistics.
CSCds15433	Symptom: Error message “x.1 is a trunk. MPLS Controllers are not allowed on trunks” when attempting to add a controller to a trunk on slot x. The “port” displayed in the error message is wrong. Conditions: This error message is triggered when attempt is made to add an MPLS controller to a trunk. Workaround: The displayed port number is wrong. But an MPLS controller cannot be added to a trunk. So the user should not attempt to add it to a trunk.
CSCds16795	Symptom: For VBR and CBR connections, the ingress/egress MCR on a UXM trunk interface are programmed incorrectly on both the master end and slave end if the load is asymmetrical. Conditions: The load for VBR/ABR has to be asymmetrical. Workaround: None.
CSCds16812	Symptom: When a cbr/ubr/vbr connection is programmed, the channel programming value sent to the trunk card are incorrect. Conditions: This only happens with the asymmetrical load. Workaround: None.
CSCds21218	Symptom: When VSI ILMI is enabled on the port interface, dspvsipartcnf will incorrectly indicate that VSI ILMI is not enabled. Condition: The problem only happens when VSI ILMI is enabled on the port via the cnfport command. (Note that starting in 9.3.10 and above, the cnfvsipart command is only used to enable VSI ILMI on trunk interfaces.) Workaround: Use the dsprsrc command to display the VSI ILMI status on port interfaces
CSCds22399	Symptom: When the primary card of a Y-red pair connected to an Axis shelf is removed, connections that can be displayed with dspcons can not be displayed with dspcon. Also, no new connections can be added to the shelf. Conditions: The primary card must be removed from the node. This is seen on both BXMs and BNIs. Workaround: Insert the primary card. It does not have to be active, just in the node (as long as it is functional enough to be recognized by the software).
CSCds22519	Symptom: Software error 9082 is logged on a UXM card with error code 0x0188 (Trying to program a channel when the card is in standby state). Condition: This happens on a node rebuild (may happen during resetcd also). Workaround: None. The channel is programmed correctly later on.
CSCds24473	Symptom: The switch MIB does not support atmTrkMgmtProtoOnCard for IGX. Conditions: When SNMP is used, atmTrkMgmtProtoOnCard is not available for IGX. Workaround: Use the CLI command(s) cnftrk/dsptrkcnf to configure/display the field “ILMI run on the card”.
CSCds25536	Symptom: VSI traffic will not flow after UXM firmware upgrade to revision ACA. Condition: This happens when the UXM firmware is upgraded after 9.3.10 software (the recommended procedure). Workaround: The reason is that the VSI Qbins (10-15) are not programmed during the upgrade process. Enable all the Qbins of all UXM interfaces using cnfqbin command. The VSI traffic will flow.
CSCds26249	Symptom: Number of retained links configured for a slot.port containing several IMA virtual trunks is not enough to support stat reserve/VSI min. bandwidth for all the virtual trunks on that slot.port. For an AR IMA vtrk, if some of the physical lines on the IMA interface go down leaving only the configured number of retained links active, the trunk would show no alarm. But because there is not enough BW for the stat reserve, CC traffic may get dropped resulting in unreachabilities in the network. For a VSI IMA vtrk, if some of the physical lines on the IMA interface go down leaving only the configured number of retained links active, the trunk would show no alarm. But because there is not enough BW for the minimum VSI BW guaranteed, there maybe some drop in VSI traffic. Conditions: This problem may occur when cnftrk is used to reduce the number of retained links for an IMA virtual trunk on a slot.port with other IMA virtual trunks on it. Workaround: When reducing the number of IMA virtual trunks make sure that the new value can support stat reserve/VSI min. bandwidth of all the virtual trunks configured on that slot.port. Further Problem Description: When the number of retained links for an IMA virtual trunk is reduced, using the cnftrk command, software checks whether the new number of retained links is enough to support the stat reserve + VSI min bandwidth on that particular virtual trunk. But, this check is not sufficient. When the number of retained links for one IMA virtual trunk is changed, the change affects ALL the other virtual trunks on that slot.port as well. The check needs to be modified to include all of them.
CSCds28463	Symptom: UXM card with VSI FW does not support VSI after delyred. None of the VSI commands (e.g.: cnfrsrc) can be executed on the VSI UXM. Conditions: During the following operations in sequence: 1. Add a Y-red between a VSI UXM and a non-VSI UXM with the VSI card as primary. 2. Down and Up the active VSI UXM. 3. Delete the Y-red. Workaround: Reset the card.
CSCds31563	Symptom: 1. cnfrsrc is not accepting the suggested bandwidth 2. cnfrsrc suggested a negative bandwidth value after user input the first suggested bandwidth Conditions: The problem will happen when a previously enabled VSI partition is reenabled, AND the “old MAX VSI BW” value in this reenabled partition causes the total VSI bandwidth on card to exceed the maximum supported bandwidth of 1412830 Workaround: This workaround will be service affecting! 1. Disable one of the other active partitions (say partition x), 2. Enable this partition with legal VSI bandwidth values, 3. Reenable the disabled partition (partition x).
CSCds33600	Symptom: During cnfport to enable ILMI to run on the card, the software error 111 is logged. Conditions: After the card firmware is upgraded on the y-redundant card. Workaround: The software error did not cause any problem in this case. It fixed itself. However the cnfport can be issued again to disable ILMI on the card and then enable again.
CSCds33676	Symptom: On BXM card, issue cnfvsiif command on a enabled line before enabling the port, it displays misleading error message “Invalid Card Type for this operation” Condition: Port should be inactive Workaround: The error message should be “Port is not active!”. There is no workaround.
CSCds36322	Symptom: When adding a connection with VPI = 0 on a port with ILMI configured, the following warning message appears: This Command: addcon 7.1.0.100 Channel(s) used for LMI and ILMI configuration. Enter remote nodename: Even if ILMI is configured in other VPI/VCI (0/16 by default) or LMI (0/31) The connection can be added without problems. The display of the warning is wrong. The warning message appears when a connection is added and has the same VPI as the ILMI or LMI Channel. If the addcon is tried on the same channel as used by the signalling protocol, it’s not possible to add the connection. Conditions: ILMI or LMI configured on a port Workaround: Ignore the warning message.
CSCds36582	Symptom: During switchcc, if the standby BCC has a commbus clock failure, this failure will not be recognized by software and software will think that the bus is ok. If the commbus clock fails, the commbus is rendered useless and all communication between the cards in the node will cease. There will be no hit to the traffic though since it is not using the commbus. Condition: This happens only when the BCC bus fails (bad BCC hardware) during the initial small time period after switchcc. Workaround: Switchcc back to the original BCC will clear the problem provided that BCC is “good”.
CSCds39545	Symptom: dspfdr command shows invalid values for VPI in the VSI LCN info screen if the feeder is not a VSI feeder (or a VSI controller). Condition: This happens only when the feeder is NOT a VSI feeder (or a VSI controller) Workaround: Ignore the VPI value. It does not have any significance if there is not a VSI feeder/controller on that interface.
CSCds40327	Symptom: dsptrkstats shows Virtual Interface statistics wrong: VI: CLP0 cells are displayed as CLP=1; VI: CLP1 are duplicate. From a screen capture of dsptrkstats: VI: Cells rcvd w/CLP=1 695684 <== This 4 lines. 695559 <== This 4 lines. VI: Cells rcvd w/CLP=1 695694 <== This 4 lines. VI: Cells tx w/CLP=1 695559 <== This 4 lines. The values printed are for CLP = 0 Conditions: Reproducible Workaround: For VI statistics, calculate the statistics as follow: * ’VI: Cells rcvd w/CLP=1’ shows ’VI: Cells rcvd w/ CLP=0’ * ’VI: Cells tx w/CLP=1’ shows ’VI: Cells tx w/CLP=0’ * For CLP=1 cell statistics, subtract the CLP=0 statistics from the Total cells received or transmitted. ’VI: Cells rcvd w/CLP=1’ = ’VI: Cells received’ - ’VI: Cells rcvd w/ CLP=0’ ’VI: Cells tx w/CLP=1’ = ’VI: Cells transmitted’ - ’VI: Cells tx w/CLP=0’
CSCds41079	Symptom: The command “cba_verify” does not work in job mode. Condition: It does not work only in Job mode. The command works fine on the CLI. Workaround: Do not use job mode for “cba_verify”. Always use CLI.
CSCds42377	Symptom: Software error 1413 when deleting a port and line in quick succession. Conditions: The following conditions are needed for this problem to occur. 1. dspqbinstats command is run on a port. 2. From another telnet session, the port is downed and deleted and the line is also deleted in quick succession with the dspqbinstats command still running. Workaround: The customer should exit the dspqbinstats command before deleting the ports and lines in quick succession. Or, the customer should wait after deleting the port until the dspqbinstats command gracefully exits. This has been fixed.
CSCds43072	Symptom: Software error 1128 is logged when dspbuses is executed. This happens only when the standby bus is failed. Condition: This happens only when dspbuses command is executed and only when standby bus is failed. Workaround: Ignore the software error. It is benign.
CSCds43641	Symptom: Addition of a VPC connection with VPI=0 on a fdr trunk succeeds even though a VSI controller exists on the same slot.port and uses VPI=0 for its Control VCs Condition: 1. A VSI controller uses VPI=0 for its Control VCs 2. addcon is done on the same slot.port for a VPC with VPI=0 Workaround: Do not use VPI=0 to add a VPC connection.
CSCds47570	Symptom: Through SNMP, not able to set SCR to be 6 cps. Condition: This is due to an invalid atmEndptSCR and atmEndptOeSCR range 7 - 1412830 specified in switch.m. it should be 6 - 1412830 Workaround: Use CLI commands cnfcon or addcon or cnfcls if SCR is configured to be 6 cps.
CSCds50411	Symptom: delyred executes without confirmation when confirming deletion of active secondary card. Conditions: Y-redundancy configured with active secondary slot. delyred timed out waiting for user input and executed delyred anyway. Workaround: None
CSCds52706	Symptoms: dspport does not show port information. Conditions: Switch software 9.3.10 BXM155: MFF After adding some connections on executing the command dspport does not display any information for the port and displays a message “Secondary slot selected” The problem happens when the port number happens to be equal standby Y-red slot + 1. Workaround: None.
CSCds52888	Symptom: Software error 922 (INV_SLOT) logged while downing lines using CiscoView (SNMP). Conditions: On BPX nodes running SWSW image 9.3.10. Doing dnln from CLI does not cause this error. Only the process of downing lines using SNMP causes it. Further Description: The problem occurs when SWSW tries to log the downing of the line in the event log. It affects only event logging. There is no database corruption or other serious errors caused as a result. The only side-effect other than the software error is that the message “LN slot.port Deactivated” in the event log might display the wrong slot and port. Workaround: Ignore the software error. Also when downing lines using CiscoView (SNMP), ignore the event logged.
CSCds58629	Symptom: Loss of VSI connections after Y-red switchover. Active Y-red UXM in invalid state. Conditions: SWSW: 9.3.10 UXM FW: ACB The problem happens only if Y-red switchover was done before the Standby was able to fully sync up with the Active card. Further Description: When the Hot-standby card is syncing up with the Active card during the initial bring up phase of the Hot-standby card [addyred, or resetcd], if the Active card fails, the Hot_standby will switchover to Active. But if the database sync up between Active and Standby was not completed before the switchover occurred, some of the VSI connections maybe left dangling. This can cause a variety of problems including continuity failures through the card. Workaround: Reset the Active card.
CSCds59259	Symptom: Various channel management issue occur after upgrading a BXM to a BXM-E. The full extent of these problems is unknown at this time and will need to be updated by the engineer that owns this defect. The net effect of this defect is that after the upgrade the VSI partition will indicate that it can support more LCNs than is physically possible on the interface. This could then lead to various software and hardware errors as AutoRoute and VSI conflict for the LCN space on the interface. To test, invoke the CLI command cnfrsrc on each port in the first partition and check if any of the enabled VSI partitions have a maximum LCN value that is larger than the maximum number of LCNs available on the card, where the port group maximum is obtained from the CLI dspcd. Conditions: In order for this problem to occur, the following conditions must be met: The customer upgraded a legacy BXM to a BXM-DX or BXM-EX card, where prior to the upgrade the legacy BXM card: -) was a BXM-OC3 (155) or BXM-OC12-2port (622) -) had a VSI partition enabled on a port in the 1st port group (port 1 on a 2 port card, ports 1-2 on a 4 port card or ports 1-4 on an 8 port card) -) had APS 1:1 enabled for “channels halved for APS operation” (as set by the CLI cnfcdaps command.) and the BXM-DX or BXM-EX card that we are upgrading to has their channel stat option set to either stat level 0 or 1. Customer Impact: An LCN conflict between the AutoRoute and VSI areas could lead to traffic loss, potential misconfiguration or programming of connections, software errors caused by conflicts, etc. Workaround: If the legacy BXM has APS configured, do not upgrade it.
CSCds66861	Symptom: Connections stop routing across a UXM trunk when the configured gateway connection limit is reached. Increasing the number of gateway connections supported on the trunk, allows further connections until the gateway connection limit is once again reached. Then no further via connections will route and a failure report of unable to find route will occur. There is sufficient bandwidth and conid's to support the remaining failed connections. Conditions: UXM trunk card with CGW and SGW connections pref routed across it. Found in SWSW 9.1.19 and UXM BBJ on E3 trunk cards. Workaround: 1. Down one of the connections that is a gateway connection on the trunk that has reached its limit. 2. Wait for all the failed connections to reroute and come to normal status. Add new via connections if required. 3. Up the connection that were downed in step 1.
CSCds79874	Symptom: The Cisco Wan Manager (CWM) is not updated with the latest port object information for some ports. Conditions: Occurs when there is more than one port on a card, and two or more of the ports have a change or alarm to be reported to the CWM Workaround: There is no workaround for missing alarm updates. For object updates, the least desired option is to completely resynch the CWM, but this is time consuming. Another option is to “force” a robust port object update to the CWM, or do the port updates very slowly (i.e. wait for 5-10 minutes between modifying ports on the same card). If a port update is missing, a robust port object update can be triggered by using cnfport to change on of its values, and then change it back (this change needs to be done quickly). If ILMI or LMI is enabled, than quickly change one of its timer values and then change it back. If neither ILMI or LMI is enabled then quickly turn one of the protocols on and then back off.
CSCds80403	Symptom: Communication failure(s) and Looped back alarms are getting cleared after hitless rebuild. Condition: This will occur only when there are communication failure(s), looped back alarms and hitless rebuilds. This only occurs on the IGX platform. Workaround: None.
CSCds82339	Symptom: When a graceful upgrade is done on an IGX node, the idle time of the node may be reduced to less than 10% for a long time. The TRNS task takes more than 50% of the CPU. After this period of time, the node functions as normal. Conditions: This only happens if there are ATFR connections on the IGX node with the FR side as the master end of the connection. The larger the number of ATFR connections with FR as the master on the node, the longer the TRNS process takes a lot of the CPU. Workaround: Do a cnfcon on all the ATFR connections with FR as the master end-point and modify at least one of the BW parameters. Further Problem Description: This is due to an inconsistency between the BW parameters of the ATFR connections stored on the ATM side (can be IGX or BPX) and the FR side. This discrepancy arises only if the connection is added from the IGX node (on the FR side). When doing swithcc/upgrade, the master node will send BW updates of all its connections to all the slave nodes. If the slave node detects any discrepancy, it will respond back with a BW Change request. If there are large number of connections with this discrepancy, a BW change request is generated by the slave node for each of those connections - and these messages are processes by the TRNS task on the master node, thus utilizing many CPU cycles.

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

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

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.

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
                           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 Statistics polling rate for ATM VCs.......................    5     
25 Interval Statistics polling rate for ports on IPX/IGX 8400 nodes...    5     
                                                                                
This Command: cnfsysparm                                                        
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
1  Update Initial Delay   [ 5000] (D)   16 Stats Memory (x 100KB) [  132] (D)   
2  Update Per-Node Delay  [30000] (D)   17 Standby Update Timer   [   10] (D)   
3  Comm-Break Test Delay  [30000] (D)   18 Stby Updts Per Pass    [  150] (D)   
4  Comm-Break Test Offset [   10] (D)   19 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                                                       
                                                                                
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                                                           
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                         
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                        
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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             [    3] (secs)                                     
10 Reset Timer on Line Fail  [  Yes]                                            
11 Max Down/Up Per Pass      [   50] (D)                                        
12 Down/Up Timer             [30000] (msecs)                                    
13 Max Route Errs per cycle  [   50] (D)                                        
14 Time between Rrt cycles   [    5] (mins)                                     
15 Max. Rrt Err cycles       [   10] (D)                                        
16 Routing pause timer       [    0] (msecs)                                    
17 Max msgs sent per update  [   10] (D)                                        
18 Send SVC urgent msg       [   No]                                            
19 Max SVC Retry             [    0] (D)                                        
20 Wait for TBL Updates      [   70] (100 msecs)                                
21 Max Derouting Bndl (0=all)[  500] (D)                                        
22 Enable Cost-Based Routing [   No]                                            
23 Enable Route Cache Usage  [   No]                                            
24 Use Delay for Routing     [   No]                                            
25 # of reroute groups used  [   50] (D)                                        
26 Starting size of RR grps  [    0] (CLU)                                      
27 Increment between RR grps [  100] (CLU)                                      
28 CM updates app timeout    [    5] (10 secs)                                  
                                                                                
This Command: cnfcmparm                                                         
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                         
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                         
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                        
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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                                                               
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
Function            Number   Status      Function            Number   Status    
Line Stat Sampling    1      Enabled     Robust Alarm Updates  15     Enabled   
Statistical Alarm     2      Enabled     Realtime Counters     16     Enabled   
Job Ready Checker     3      Enabled     LAN Interface         17     Enabled   
Configuration Backup  4      Enabled     Update Standby Stats  18     Enabled   
Standby Update        5      Enabled     Telnet Access         19     Enabled   
Downloader            6      Enabled     Junction ID           20     Enabled   
Cm Updates            7      Enabled     Mult SV+/Routing Node 21     Disabled  
Topo/Stat Updates     8      Enabled     Simulated Fdr Trks    22     Disabled  
Card Statistical Alms 9      Enabled     Deroute Delay         23     Enabled   
Card Stat Sampling    10     Enabled     Auto Renum Fail Recov 24     Enabled   
Address Validation    11     Enabled     Card Simulation Tool  25     Disabled  
ASM Stats Polling     12     Enabled                                            
Port Stat Sampling    13     Enabled                                            
Robust Updates        14     Enabled                                            
                                                                                
This Command: on2                                                               
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK  2.1 Config     T3     [96000 cps]     BNI-T3 slot:  2                      
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            
SVC Vpi Min:           --                  HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      No            
SVC Bandwidth:         0      cps          Frame Scramble:        --            
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 2.1                                                     
                                                                                
 
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 2.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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 2.1

BNI-E3

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK  3.1 Config     E3      [80000 cps]    BNI-E3 slot:  3                      
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            
SVC Vpi Min:           --                  HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      Yes           
SVC Bandwidth:         0      cps          Frame Scramble:        --            
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 3.1                                                     
                                                                                
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 3.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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 3.1

BNI-155/155E

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK  1.1 Config     OC3    [353207cps]     BNI-155 slot: 1                      
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            
SVC Vpi Min:           --                  HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      Yes           
SVC Bandwidth:         0      cps          Frame Scramble:        Yes           
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 1.1                                                     
                                                                                
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 1.1 Parameters                                                              
 1 Q Depth - rt-VBR    [  885] (Dec)    15 Q Depth   - CBR     [  600] (Dec)    
 2 Q Depth - Non-TS    [ 1324] (Dec)    16 Q Depth   - nrt-VBR [ 1000] (Dec)    
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [15463] (Dec)    
 4 Q Depth - BData A   [ 1000] (Dec)    18 Low  CLP  - CBR     [ 100] (%)       
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [ 100] (%)       
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [ 100] (%)       
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [ 100] (%)       
 8 Red Alm - I/O (Dec) [  2500 /  10000]22 Low CLP/EPD-ABR     [  60] (%)       
 9 Yel Alm - I/O (Dec) [  2500 /  10000]23 High CLP  - ABR     [  80] (%)       
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  30] (%)       
11 High CLP - BData A  [ 100] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 1.1

BXM-T3

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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            
SVC Vpi Min:           0                   HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      No            
SVC Bandwidth:         0      cps          Frame Scramble:        --            
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 5.1                                                     
                                                                                
 
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
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

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 13.1 Config     E3     [80000 cps]     BXM slot:     13                     
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            
SVC Vpi Min:           0                   HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      Yes           
SVC Bandwidth:         0      cps          Frame Scramble:        --            
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 13.1                                                    
                                                                                
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 13.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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 13.1

BXM-155

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK  6.1 Config     OC3    [353207cps]     BXM slot:     6                      
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            
SVC Vpi Min:           0                   HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      Yes           
SVC Bandwidth:         0      cps          Frame Scramble:        Yes           
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 6.1                                                     
                                                                                
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 6.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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 6.1

BXM-622

hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK  9.1 Config     OC12   [1412679cps]    BXM slot:     9                      
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            
SVC Vpi Min:           0                   HCS Masking:           Yes           
SVC Channels:          0                   Payload Scramble:      Yes           
SVC Bandwidth:         0      cps          Frame Scramble:        Yes           
Restrict CC traffic:   No                  Virtual Trunk Type:    --            
Link type:             Terrestrial         Virtual Trunk VPI:     --            
Routing Cost:          10                  Deroute delay time:    0 seconds     
                                                                                
Last Command: dsptrkcnf 9.1                                                     
                                                                                
hugo           TN    Cisco           BPX 8620  9.3.11    Date/Time Not Set      
                                                                                
TRK 9.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] (%)       25 SVC Queue Pool Size [    0] (Dec)    
12 Low  CLP - BData B  [  25] (%)                                               
13 High CLP - BData B  [  75] (%)                                               
14 EFCN     - BData B  [  30] (Dec)                                             
                                                                                
This Command: cnftrkparm 9.1

IGX 8400 Nodes

mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
                           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                                                        
 
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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       [ 1000] (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                                                       
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
Index Status    Function                                                        
                                                                                
1     Enabled   Automatic CLN/PLN Loopback Test on Local/Remote Alarms          
2     Enabled   FDP Loopback button                                             
3     Enabled   User Command Logging                                            
4     Enabled   Automatic Card Reset on Hardware Error                          
5     Enabled   TXR Model D Download                                            
6     Enabled   Card Error Record Wraparound                                    
7     Disabled  Card Test After Failure                                         
8     Disabled  Download From Remote Cisco StrataView Plus                      
9     Disabled  Logging of conn events in local event log                       
10    Disabled  Logging of conn events in Cisco StrataView Plus 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                 
                                                                                
This Command: cnffunc                                                           
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                         
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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 
                                                                                
This Command: cnftstparm                                                        
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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             [    3] (secs)                                     
10 Reset Timer on Line Fail  [  Yes]                                            
11 Max Down/Up Per Pass      [   50] (D)                                        
12 Down/Up Timer             [30000] (msecs)                                    
13 Max Route Errs per cycle  [  200] (D)                                        
14 Time between Rrt cycles   [    5] (mins)                                     
15 Max. Rrt Err cycles       [    1] (D)                                        
16 Routing pause timer       [    0] (msecs)                                    
17 Max msgs sent per update  [   10] (D)                                        
18 Send SVC urgent msg       [  Yes]                                            
19 Max SVC Retry             [    0] (D)                                        
20 Wait for TBL Updates      [   70] (100 msecs)                                
21 Max Derouting Bndl (0=all)[  500] (D)                                        
22 Enable Cost-Based Routing [   No]                                            
23 Enable Route Cache Usage  [   No]                                            
24 Use Delay for Routing     [   No]                                            
25 # of reroute groups used  [   50] (D)                                        
26 Starting size of RR grps  [    0] (CLU)                                      
27 Increment between RR grps [  100] (CLU)                                      
28 CM updates app timeout    [    5] (10 secs)                                  
                                                                                
This Command: cnfcmparm                                                         
                                                                                
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                         
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                           
                                                                                
Enter parameter index:                                                          
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                        
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                               
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                               
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                               
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK         Type   Current Line Alarm Status               Other End            
 4.1        T1/24  Major - Loss of Sig (RED)               -                    
 5          T1/24  Major - Loss of Sig (RED)               -                    
 6          E1/32  Major - Loss of Sig (RED)               -                    
 7          SR/30  Major - Bad Clock (RED)                 -                    
 8.1        E1/30  Major - Loss of Sig (RED)               -                    
12.1        E3/530 Major - Loss of Sig (RED)               -                    
14.1        T1/24  Major - Loss of Sig (RED)               -                    
16.1        OC3    Major - Loss of Sig (RED)               -                    
                                                                                
This Command: dsptrks

UXM-T3

mulder         TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                    
                                                                                
 
mulder         TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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 (using the T1-IMA backcard with only one physical line up)

mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK  4.1 Config       T1/24    [3622  cps]  UXM slot:4                          
IMA Group Member(s):  1                   Line coding:          B8ZS            
Retained links:       1                   Line cable type:      ABAM            
Transmit Trunk Rate:  3622   cps          Line cable length:    0-131 ft.       
Rcv Trunk Rate:       3622   cps          HCS Masking:          Yes             
Pass sync:            Yes                 Payload Scramble:     No              
Loop clock:           No                  Connection Channels:  256             
Statistical Reserve:  1000   cps          Gateway Channels:     200             
Header Type:          NNI                 Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
VPI Address:          1                   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 4.1                                                     
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK  4.1 Parameters:                                                            
 1 Yel Alm-In/Out (D)  [   600/   600]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]                                          
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [   22]    15 BDataA [10000]     29 rt-VBR [   21]   32 BDataA [10000]
13 Non TS [   30]    16 BDataB [10000]     30 Non TS [   28]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
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 4.1

UXM-T1-IMA (4 physical lines up)

mulder         TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set
 
TRK  4.1(4) Config    T1/95    [14339 cps]  UXM slot:4                         
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:  Enabled      
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 4.1
 
 
mulder         TRM   Cisco           IGX 8420  9.3.11    Date/Time Not Set
 
TRK  4.1(4) Parameters:
 1 Yel Alm-In/Out (D)  [   600/   600]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [   81]    15 BDataA [10000]     29 rt-VBR [   80]   32 BDataA [10000]
13 Non TS [  118]    16 BDataB [10000]     30 Non TS [  117]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
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 4.1

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

mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                     
                                                                              
 
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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]    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 8.1

UXM-E1-IMA (4 physical lines up)

                                                                                
mulder         TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set
 
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
 
                                                                                
mulder         TRM   Cisco           IGX 8420  9.3.11    Date/Time Not Set
 
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]    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 8.1

UXM-E3

                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK 12.1 Config       E3/530   [80000 cps]  UXM slot:12                         
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 12.1                                                    
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK 12.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 12.1

UXM-OC3

mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK 16.1 Config       OC3      [353207cps]  UXM slot:16                         
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:         STS-3C                                                    
HCS Masking:          Yes                                                       
Payload Scramble:     Yes                                                       
                                                                                
This Command: dsptrkcnf 16.1                                                    
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
TRK 16.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 16.1

NTM-T1

mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                       
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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

                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                       
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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

                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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                                                       
                                                                                
                                                                                
mulder       TN    Cisco           IGX 8420  9.3.11    Date/Time Not Set      
                                                                                
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 MFJ Release Notes

About the Firmware MFJ

BXM Firmware version MFJ supports all the existing interfaces and models of BXM hardware. Following table outlines various levels of hardware revisions supported for BXM firmware version MFJ.

Front Cards

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

Front Card for APS Compatibility

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

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
SMFLR-155-4	4-port single-mode fiber long-reach back card	A	na
SMFLR-155-8	4-port single-mode fiber long-reach back card	A	na
SMF-622	1-port intermediate-reach OC-12 back card	A	na
SMF-622-2	2-port intermediate-reach OC-12 back card	A	na
SMFLR-622	1-port long-reach OC-12 back card	A	na
SMFLR-622-2	2-port long-reach OC-12 back card	A	na
XLR-622	1-port extra long-reach OC-12 back card	A	na
XLR-622-2	2-port extra long-reach OC-12 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 OC-12 redundant back card	A	na
RDNT-SM-622-2	2-port intermediate reach OC-12 redundant back cards	A	na
RDNT-SM-622	1-port intermediate reach OC-12 redundant back cards	A	na
RDNT-LR-155-8	8-port long-reach OC-3 redundant back cards	A	na
RDNT-SM-155-4	4-port intermediate-reach OC-3 redundant back cards	A	na
RDNT-SM-155-8	8-port intermediate-reach OC-3 redundant back cards	A	na

New Features Supported in BXM Firmware MFJ

None

New Features Supported in BXM Firmware MFH

1. Dynamic partitioning feature is supported on the BXM card by default. The Remote Shell Feature through the BCC CLI provides a mechanism to turn off this feature.

2. SPVC feeder support.

New Features Supported in BXM Firmware MFF

None

New Features Supported in BXM Firmware MFE

None

New Features Supported in BXM Firmware MFD

None

New Features Supported in BXM Firmware MFC

1. Support for SES (PNNI controller).

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

3. 1 msec granularity for tstdelay measurement.

New Features Supported in BXM Firmware MFB

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

2. Hitless Connection Density Upgrade for BXM.

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

4. Control Traffic Shaping.

New Features Supported in BXM Firmware MFA

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

New Features Supported in BXM Firmware MEC

There are no new features in release MEC.

New Features Supported in BXM Firmware MEB

There are no new features in release MEB.

New Features Supported in BXM Firmware MEA

1. VSI version 2.2 (single partition).

2. ITUT Annex B and configurable Signal Degrade (SD) and Signal Failure (SF) thresholds for SONET Linear APS on BXM-OC-3 and BXM-OC-12 (1+1, 2 card, 1:1).

: The current default thresholds are as follows:

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

1. Support for Virtual Trunking.

2. Support for BXM MultiLevel Channel Statistics.

3. SONET Linear APS on BXM-OC-3 and BXM-OC-12 (1+1, 2 card, 1:1).

4. Support for card-based LMI and ILMI.

Clarifications:

1. The OC-3 MultiMode Fiber back cards do not support Y-cable redundancy.

2. Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. See upgrade section on page 15.

3. APS 1:1 is not supported for VSI. (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 for release MFE and after, this problem is fixed.

4. Total BW allocated to all VSI partitions on a BXM should not be more that OC-12 rate, i.e., 1412832 cells/s. Currently BCC switch software allows uses to configure more than OC-12 rate, in which case all the PNNI connection commit requests would be NACKed by BXM

Special Installation/Upgrade Requirements

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, first upgrade the standby card with the MFA or above firmware version and wait for all the configuration to be downloaded into the card. Do a switchyred to switch to the card with firmware MFA or above version and burn the other card also with desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.

If BCC switch software version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Statistics it should be OK to go directly to MFC or above versions directly from MCC.

Features Obsoleted

1. VSI 1.0 is obsolete by VSI 2.2 in this release.

2. 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. However it is still supported for all the other models (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 and Cautions

1. BXM Model F firmware is intended for use with Release 9.3 Switch Software. BXM Model F firmware may be used to upgrade BXMs during the upgrade process from Switch Software Release 9.2 to 9.3. BXM Model F firmware has not been tested for compatibility with Release 8.4, 8.5, and 9.1 Switch Software. It is compatible with IOS version 12.05t2 for MPLS.

2. MFE is a not on CCO, as it an Orion specific release.

3. While upgrading from firmware, on OC-3, 1-port OC-12 BXM cards, if statistics level on BXM is greater than 1, the upgrade should take place according to the one of the upgrade procedures below to avoid the card mismatch:

Upgrading from firmware revision MEA or higher.

Step 1 Switch software should be upgraded to Release 9.2.30 or higher.

Step 2 Upgrade the firmware to MFJ.

Upgrading from firmware revision lower than MEA:

Step 1 Firmware should be upgraded to MEC.

Step 2 Upgrade the switch software to Release 9.2.30 or higher.

Step 3 Upgrade the firmware to MFJ.

4. Burn firmware should not be interrupted. Card resets in the middle of burn firmware will result 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 will report the card as FAILED. This state can be recovered by reburning the firmware into the card.

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

6. 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 back card should be green, since it is carrying traffic. WORK back card should also be green since that is the physical path for the primary (and active) card to pass traffic. So back card LED green means the back card is directly or indirectly carrying traffic and pulling the back card will cause traffic disruption (CSCdm53430).

7. In APS 1+1 default configuration and manual W->P is on and a switchyred command 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).

8. 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 will become active (CSCdm53420).

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

Known Anomalies

The following is the list of known anomalies for the BXM firmware:

Bug ID	Description
CSCdr06316	Symptoms: VPC connection drops cells over BXM trunks. Condition: Reproducible Workaround: None.
CSCdr11806	Symptoms: BXM does not report A-bit errors when SPVC feeder is provisioned without Auto Route feeder segment. Condition: None available at this time. Workaround: None.
CSCdr45464	Symptoms: 0B card error reported on BXM-OC3 cards. Condition: When the cards are in Y-redundancy configuration. Probably caused by bad hardware. Workaround: None.
CSCdr85398	Symptom: 2 nodes with 2 PNNI controllers, and cnfpnportrange command used to force a LOC, missing COA point trap dnpnport/uppnport, restarting ILMI session, results in COA trap. Condition: When ILMI session is first initialized or restarted, if SysUpTime doesn’t change, COA trap shouldn’t not be sent to controller. When an LOC is detected by ILMI on BXM and it is followed by a “Loss of Attachment Point” when connectivity is re-established, ILMI on slave does not give a “Loss of Attachment Point” trap. Workaround: None
CSCds01128	Symptoms: LOS sometimes occurs on several trunks. Conditions: Unknown. According to the bug report, once in awhile for a couple of minutes. Workaround: None. The trunks recover on their own.
CSCds16136	Symptom: A channel mismatch appears as status even though LOS is still present. Conditions: In near succession, recovery of LOS on Working line and appearance of LOS on Protection line. Workaround: None.
CSCds21403	Symptom: After downing the NNI ports, ports go into a provisioning state because of running buffer leakage. Conditions: Not available at this time. Workaround: Reset the card and continue.
CSCds47753	Symptoms: Card error occurs in standby “VrmDekConnEndPoint Try to delete” Condition: When standby syncs up with active, it tries to delete a non-existing connection. Workaround: The card error indicates an invalid attempt to delete a non-existing connection. This does not create a problem in existing or new connections.

Bugs Fixed in MFJ

The following bugs are fixed in MFJ.

Bug ID	Description
CSCdr19696	Symptom: Unable to determine when the line is out of SD/SF condition. Both the aps lines always show OK state in dspapsln. Conditions: APS Line switches to standby line because of SD/SF condition. dspapsln will still show OK for both lines. Workaround: Use rsh command for aps line status.
CSCds04137	Symptom: Channels remains in 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 ne.
CSCds11506	Symptom: Minimum guaranteed cell rate shows a cell less than configured. Conditions: Setting minimum BW to 3333334 and policy BW% to 5859 Workaround: Increase the minimum BW by a few cells.
CSCds32845	Symptom: Connection commits rejected with “no resources” even when resources are available. Condition: Enabling/disabling a virtual trunk. Workaround: Reset the BXM after disabling a VT on any interface on the card.
CSCds37237	Symptom: If the network migration flag is enabled before upgrading, then after burning the new image, the network migration flag is incorrectly disabled. Condition The problem only occurs to the card whose previous image is BXMMFC-BXMMFF, and the network migration flag was enabled before upgrading, and BXMMFH is the new image. Workaround: Issue either the rsh <slot> cdcfg netmig dis command before the upgrading, or rsh <slot> cdcfg netmig en after upgrading, to enable the network migration flag on BXMMFH.
CSCds53645	Symptom: ABR connections (PNNI) are not properly programmed for redundant slave. Condition: Switchyred When connection is added, the redundant card is not there and inserted at later stage. When connection is added, no redundant config, addyred at later stage. Workaround: Resolved in MFJ. Use switchapsln to synchronize states.
CSCds59710	Symptom: Loss of traffic on a VPC connection added with VPI=0 Conditions: Switch Software Release9.3.10 and BXM firmware 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: Configure the signalling channel on the controller side to use a VPI other than 0.
CSCds61912	Symptom: After downloading MF30 firmware, card is in failed state. Condition: Downloading MF30 firmware. Workaround: Avoid MF30 which is a development release between MFH and MFJ.
CSCds63578	Symptom: Software error 105 is logged on BXM while adding VSI connections. Subsequent card errors saying CB_TASK restarted. Condition: This error may occur 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. Condition: Routing connections of different service types over the virtual trunks. Workaround: None.

Bugs Fixed in MFH

The following bugs are fixed in MFH.

Bug ID

Description

CSCds14495

Symptom:

Dynamic Partitioning and SPVC AIS generation does not work until a rsh command is issued to enable the network migration flag and reset the card.

Condition:

When a card comes up and has never enabled the network migration flag for lifetime. 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

The following bugs are fixed in MFF.

Bug ID	Description
CSCdp89085	Symptom: The total call count becomes negative on the BXM interface. However, this problem has not be reproducible. Condition: 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.
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 Neighbor Discovery 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. Condition: 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 Neighbor Discovery, 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 at@ Bcc in addition to existing dnpnport at 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.
CSCdr79610	Symptom: Change booking factor for a class of service, get rejected. Condition: When there are some connections established, and some of the class of service have used bandwidth exceeding their reserved, change booking factor for any class of the service may get rejected. This is because it fails the check which should only be called when cos_min_bw in the policy parameters is changed. This check should not be called when booking factor is changed. Workaround: Disable that partition, change the booking factor, then enable the partition again. Or keep the used_bw for all cos under the cos_min_bw, you will be able to change booking factor freely.
CSCdr79936	Symptom: Statistics files not generated/missing on some 15 minutes intervals. Condition: When system time is changed at 15 minutes boundaries. Workaround: Minimize system time and card config changes.
CSCdr83144	Symptom: Card error of ’N. Fatal from 0x17: 0x25120075 0x809b5f90 0x367e 0x1 Condition: switchyred, switchcc or reset PXM when there are spvc connections with stats enabled. Workaround: None.
CSCdr89217	Symptom: Software error log of 9098. Condition: cnfrsrc of partition 3 using MEB firmware. Workaround: None.
CSCdr89966	Symptom: Card error of 0x41030006. Condition: PXM controller is upgraded/rebooted. Workaround: None.
CSCds08448	Symptoms: ERS (explicit rate stamping) is working only on the first virtual trunk and not for subsequent VTs (standard ABR). Cause: 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 trunk or a physical trunk. Multiple virtual trunks on the same physical port will cause a problem.
CSCds11484	Symptom: Available cell rate reported by BXM is incorrect. Condition: Sum of the minimum bandwidths of all the interfaces on a BXM reaches OC12 rate. Workaround: Reduce the minimum BW on all interfaces by half.

Bugs Fixed in MFE

Bug ID	Description
CSCdm16800	Symptom: Card error 0xC000007 appears in the card error log. Cause: This error indicates that an unknown type of cell which is not expected has arrived in the egress QE. Resolution: Engineering has done an in-depth investigation into this case. We are convinced that 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.
CSCdp05098	Symptom: Cell discards occur for ABRFST/ABRSTD connections when the traffic burst is greater than the MBS. Condition: This occurs when the traffic burst size is fixed to 140000 cells at 70000 cps. The connection 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.
CSCdp22930	Symptom: Not available. Condition: Cbus read/write operations set-up in the PUUMBA chip when performing cbus receive/transmit. Workaround: None
CSCdp74680	Symptom: Even if the interface is in LOS, the SPVCs do not generate ingress AIS into the network. Condition: Connection is added after the interface goes into LOS. Workaround: None
CSCdp97307	Symptom: When executed “rsh<slot> vsi cm Vsils” without parameter, the card will crash. Conditions: Always. Workaround: Pull-out the card and reinsert.
CSCdr44250	Symptom: Private image did not allow as many OAM cells to flow as public image. Condition: 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	Symptom: Standby and active block checksum value do not match and resync happens on switchover. Condition: When active card has many SPVC connections derouted, it happens. Workaround: None.
CSCdr57712	Symptom: Multi-partition fails to report all virtual trunks. Condition: In case of virtual trunks with different partition. Workaround: Reset the BXM card.
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 firmware are not predictable. At least two variations are observed: Variation 1: port 11.2 has it’s neighbor’s info, but port 11.1 doesn’t. Variation 2: both ports 11.1 and 11.2 only know the IP addresses of their neighbors. The neighbor’s IFName is missing. Condition: When ILMI session restarts, remnants of IfName, IpAddr from previous session are left. Clear/reset IfName, IpAddr in MIB, on ILMI session restart. In FMSStart, pIlmiProcessFsmStart() calls a new function, IlmiClrPeerAndSendTopoTrap(pcb_ptr->session_id).
CSCdr71473	Symptom: Unreachable BXM, sw errors and cd errors on the BPX. Condition: LMI is enabled when controller either slow to respond or unreachable. Workaround: Disable LMI.
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. Condition: 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: None. Upgrade to MFD or later.
CSCdr79936	Symptom: Statistics files not generated/missing on some 15 minutes intervals. Condition: When system time is changed at 15 minutes boundaries. Workaround: Minimize system time and card config changes.
CSCdr86894	Symptom: Many ports have VC failure because BXM has no resource to build the CVC. Condition: Intermittent. Workaround: Reset BXM card.

The following bugs are fixed in MFE.

Bugs Fixed in MFD

The following bugs are fixed in MFD.

Bug ID	Description
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. Condition: This happens if on NNI side VPI > 0xff. Workaround: None.
CSCdp63445	Symptom: ABR and UBR connections loose traffic when VC shaping is turned on. Condition: Enabling of VC shaping on port terminating ABR and UBR connections Workaround: Leave VC shaping disabled.
CSCdr14247	Symptom: The correct state of an SPVC is not reflected in connection bulk traps for large number of connections (> 1000). Sometimes Connection states keep toggling between AIS and CLR state when the connections are actually in AIS state Condition: 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.
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) Condition: The cause is unknown. Workaround: None.
CSCdr30454	Symptom: Connections (LCNs) can not satisfied because of insufficient memory Condition: When channel stat level is set to 0 Workaround: Use chan stat level (cnfcdparm) 1, 2 or 3
CSCdr33867	Symptom: Connect OC-3 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. Condition: 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.
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. Condition” 1. The policy parameters for the partition have been configured as nonzero at some of the class of service, for example, 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.
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) Condition: 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.
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) Condition: 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. Condition: Controller looses communication with the BXM. This happens when AAL5 driver in the BXM malfunctions and does not free the message buffers of the application processes (ILMI/VSI and so on). Eventually BXM runs out of message buffers. Workaround: Reset the BXM card.
CSCdr43012	Symptom: All the ports on a BXM slave go into provisioning state. Condition: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck. 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.
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. Condition: 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.
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
CSCdr51970	Symptom: Change CAC policy parameters will cause the available BW for some cos to be negative. Condition: 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.
CSCdr52195	Symptom: All the ports on a BXM slave go into provisioning state. Condition: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck. Workaround: Reset the BXM card.
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. Condition: 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.
CSCdr57805	Symptom: Card errors show up indicating “CB_TASK is ready” Condition: 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.
CSCdr59241	Symptom: Building VC status on UNI ports after repeated enabling/disabling of partition with the control port Condition: 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.
CSCdr66273	Symptom: The encoding is in the reverse of the expected value by UNI4.0 spec. Condition: STD ABR connections. Workaround: None.

Bugs Fixed in MFC

The following bugs are fixed in MFC.

Bug ID	Description
CSCdp63445	Symptom: ABR and UBR connections loose traffic when VC shaping is turned on. Condition: 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: 1. One PVC has 2880 cps of data and 960 cps of oam cells. 2. Another PVC has 2880 cps of data and 960 cps of oam cells. Workaround: None.
CSCdr13196	Symptom: BPX reports SWERR 105 Conditions: SWERR105 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

The following bugs are 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. Condition: 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.
CSCdp58969	Symptom: cb_get.c CB_VPC_STATUS_POLL SoItcSend Failed upon VSI Failure Condition: 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
CSCdp57596	Symptom: CB_TASK on BXM goes into deadlock state causing VSI session to be lost Condition: 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.
CSCdp25220	Symptom: Avail Buffer on BXM = 0 on LVC flapping for xtag interfaces Condition: Same as CSCdp58969. During this condition AAL5 driver doesn’t release the transmission buffer. Workaround: None. Upgrade to/MEF or newer versions of firmware
CSCdp59328	Symptom: EPD bit was not set for interslave control vc Condition: When vsi get congestion (same as CSCdp58969) Workaround: None. Upgrade to/MEF or newer versions of firmware
CSCdp92916	Symptom: Commands executed on stdby card affect APS line Condition: Series of commands executed in stdby card affects APS line 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 Condition: 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
CSCdp20848	Symptom: SF switchover does not occur after dncd/upcd execution on Annex B 1+1 APS Condition: 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 Condition: 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
CSCdp32646	Symptom: WTR Timer does not work and reversion occurs during SF switchover Condition:. 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 Condition: 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
CSCdp60696	Symptom: Both lines fail when only one line in alarm Condition: 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
CSCdp65320	Symptom: Need a trap when BPX puts APS in lockout Condition: 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
CSCdp25130	Symptom: APS Non-revertive bidirectional feature Condition: Resolved Workaround: None
CSCdp79156	Symptom: TDP signalling cross connect VSI request rejected by BXM Condition: 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
CSCdp62213	Symptom: Switching from bi-direction APS to un-directional APS generates mismatch err Condition: The alarms generated while the line was in bi-dir mode was not cleared when it was changed to uni-dir mode. Fixed by clearing all alarms when reconfiguring the lines.None. Workaround: None. Upgrade to MEF or newer version of firmware
CSCdp89972	Symptom: Node rebuild caused 3 BXM cards failed Condition: 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
CSCdp86147	Symptom: The removal of Rx cable of APS trunk leading to loss of Frm and Prot Sw Byt Fail Condition: 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
CSCdp84386	Symptom: Connectivity w/BXM lost due to missing DMA completion interrupts Condition: Aal5 driver will be in deadlock and never transmits and receives. Workaround: None. Upgrade to MEF or newer version of firmware
CSCdp38148	Symptom: Resetcd slot 11 on BPX causes local APS switching Condition: Reimpose the selector and bridge states on both ACTIVE and STANDBY cards after a 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
CSCdm92931	Symptom: APS line switchover occurs upon card removal when lockout is set Condition: Workaround: None. Upgrade to MEF or newer version of firmware
CSCdp49749	Symptom: Node unreachable after resetting two nodes in the network Condition: Workaround: None.
CSCdp49640	Symptom: When FCES feature enable on BXM NNI data transfer stops Condition: The ABR parameters like NRM,CRM,FRTT,MCR,ICR were not getting programmed when the FCES is turned on using the cnfcon command.Adding the Connection with the FCES enabled behaved properly. Workaround: None.
CSCdm62817	Symptom: tstconseg command sometimes does not work. Condition: Execute tstconseg multiple times with high loop count (10). Workaround: None.
CSCdm84853	Symptom: BW reported via interface load info is erroneous. Condition: When Forward & Backward BW for VSI connections is different. Workaround: None.
CSCdp62213	Symptom: Switching from bi-dir to uni-dir mode APS generates APS architecture mismatch error Condition: 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
CSCdp59729	Symptom: addlnlocrmt causes node unreachable. Condition: addlnlocrmtlp causes node unreachable even though there are other parallel trunks. Workaround: No known workaround
CSCdp67673	Symptom: dspapsln does not show ARCH_MIS any more Condition: dspapsln does not show ARCH_MIS when caused for the second time on the same trunk. Workaround: No known workaround
CSCdp46399	Symptom: Need a documentation explains how to setup port groups for FW MEF (me26) Condition: Workaround: No known workaround
CSCdp49749	Symptom: Node unreachable after resetting two nodes in the network Condition: 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
CSCdp28931	Symptom: No RDI-P generated when loss of Cell Delineation occurs Condition: Workaround:
CSCdp59727	Symptom: Addlnlocrmt causes node unreachable Conditions: Workaround: Reset the BXM card

Bugs Fixed in MFA

The following bugs are fixed in MFA.

Bug ID	Description
CSCdm53420	Symptom: switchyred causes APS line to switch when last user request is clear Condition: 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:
CSCdm93274	Symptom: OC-3 back card LED is wrong after reset/pull cards Condition: Multiple APS lines on a card and perform switchyred when Working line is active and Secondary card is active Workaround: None.
CSCdm04312	Symptom: The problem is a false failure is declared against the SIMBA Multicast Record RAM. Condition: 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.
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.
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. Condition: 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.
CSCdk42527	Symptom: Rx Queue becomes full after LOS on the feeder trunk Condition: After LOS condition on the feeder trunk Workaround: Reset the feeder trunk
CSCdm16505	Symptom: AIS not sent on VP ABRFST/ABRSTD connection Condition: LOS on trunk between 2 nodes Workaround: None.
CSCdm81534	Symptom: ICR of abrfst on BXM-155 falls down to MCR after resetcd Condition: Change the ICR after resetcd before start sending traffic Workaround: None
CSCdm61493	Symptom: When BIP8 errors are received on an E3 line or trunk at a rate of 10E-3, the line or trunk will not declare any alarm. Condition: When high rates of BIP8 errors are received. 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. Condition: BXM slot errors on a BCC3 node Workaround: None
CSCdk80483	Symptom: TX cell loss counts in dsptrkerrs increase continuously. Condition: When there is trunk configured. Workaround: None.
CSCdm04312	Symptom: The problem is a false failure is declared against the SIMBA Multicast Record RAM. Condition: 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. Condition: Every time changing an existing connection from FCES enable to disable. Workaround: Delete the connection and add back a new one with FCES disable
CSCdm39186	Symptom: Card fatal error occurred when running in standby mode under the heat condition. As a result, the card reset periodically. Condition: Card running in standby mode under heat condition Workaround: None
CSCdm09882	Symptom: Log non fatal message related to the RCMP errors Condition: 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.
CSCdm31923	Symptom: AIS/YEL alarm doesn’t go away even after the alarm is clear from the other end Condition: It happens on the E3 when the LOOP TIME parameter is set to YESin the trunk or line configuration 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.
CSCdm52585	Symptom: DspVsiPartInfo shows very large Available LCN field. Condition: When the sum of min-lcns is greater than the max(max lcns) on a port group. Workaround: None.
CSCdp18840	Symptom: The CBR.2 Calls do not pass traffic above 50 Cells/second. Condition: VSI controller establishes CBR.2 connection and it does not fill in the PCR field. Workaround: Fill the PCR value aslo with the CR value.
CSCdp17741	Symptom: 2-port group card reports 1 port group at the channel stats level 2 and 3. Condition: 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.
CSCdp22930	Symptoms: Intlock missing for rd./wr operation Workaround: Reassert intLock on commbus ISR to prevent SCC access from getting interrupted
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
CSCdp36324	Symptom: Last user request affects switching on BPX. Conditions: Workaround:
CSCdp31325	Symptom: UBR cells are policed unnecessarily below PCR. Conditions: Always. Workaround: None.
CSCdp36155	Symptom: BXM-E OC-3/OC-12 does not show supporting APS HW 1+1 in dspcd command and otherwise also. Condition: BXM-E OC-3/ OC-12 card with HW rev < ’C’ 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. Condition: BXM enhanced OC-3 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 OC-3 4 port card. or 2. Replace the BXM-E 4 port card with 8 ports card.
CSCdp17741	Symptom: 2-portgroup card reports 1 port group at the channel stats level 2 and 3. Condition: When channel stats level 2 or 3 are configured on BXm-622-2 port and BXM-155 reports only one port group. Workaround: AutoRoute connections are not affected by this. But for VSI connections. There is no work around.
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
CSCdm73220	Symptom: Trunks or Virtual Trunks does not allow traffic going through. Condition: Switch software 9.1 with ME level of firmware. Trunks or VTs configured on BXM/BXM-E. Workaround: None

Bugs Fixed in MEC

The following bugs are fixed in MEC

Bug ID	Description
CSCdm66131	Symptom: After addapsln trunk goes to LOS Condition: 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. Condition: 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. Condition: APS 1+1 configured in bidirection 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. Condition: 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. Condition: 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. Condition: Load information on an interface is 4 bytes more that MAX_VSI_MSG, So the message gets dropped on BXM, so VSI controller is in discovery state forever. Workaround:
CSCdm75722	Symptom: No control VC after BXM is reset. Condition: 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 Condition: Over night jobs running on controller cards. Workaround:
CSCdp02190	Symptom: tstdelay timed out when going through BNI trunk Condition: More that 12 VTs on an interface causes wrong port-vi mapping while considering STI_SHIFT/NO_SHIFT from 13 the VT/port onwards. Workaround:
CSCdm78335	Symptom: dspvsistatus rarely shows the VSI programming status as Done Condition: Primary and secondary port has two different VPI range. Workaround:
CSCdm26752	Symptom: Card errors continuously logged with “SoItcSend failed” message. Condition: 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 Condition: oamlpbk is enabled with high oam traffic on large number of connections. Workaround:
CSCdm52254	Symptom: BIP-8 code errs occurs on routing trunks Condition: 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 Condition: 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. Condition: Port terminates on BXM-E card or on trunk passing through BXM-E card. Workaround:
CSCdm80991	Symptom: Unable to add 3 segment connections using CM GUI Condition: 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 wraparound solution Condition: Large deviations in CDV values Workaround:
CSCdm94372 (see explanation below)	Symptom: Trunks sometimes drop cbr traffic Condition: 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) Condition: 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 is As Follows (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

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.

Therefore, 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

The following is the list of bugs fixed in release MEB.

Bug ID

Description

CSCdm50469

Symptom:

Software error 105 and malloc card errors happened continuously

Condition:

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.

Condition:

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.

Condition:

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

The following is the list of bugs fixed in MEA.

Bug ID	Description
CSCdm09882	Symptom: Log non fatal message related to RCMP errors. Condition: It is mainly seen in the heat chamber. Workaround: None
CSCdm18186	Symptom: AIS status could be randomly be displayed in dspcon Condition: When the connection AIS signal is constantly changing, the dspcon/dspchstats OAM status will not be accurate for all the connections on the card. Workaround: None
CSCdm26380	Symptom: Software error 9098 occurred during switchyred BXM Condition: 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. Condition: 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. Condition: When MC10 is burnt into BXM-OC-12 with trunks. Workaround: None
CSCdm37709	Symptom: APS line fails to clear channel mismatch after lockout. Condition: 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. Condition: 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 Annex B line. Condition: 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

The following is the list of 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. Condition: 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. Condition: 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. Condition: 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. Condition: BXM fw allowed configuration of networking channel to be bidirectional only. Workaround: None

Firmware Filenames and Sizes

Filename	Size
BXMMFJ.000	65536
BXMMFJ.001	65536
BXMMFJ.002	65536
BXMMFJ.003	65536
BXMMFJ.004	65536
BXMMFJ.005	65536
BXMMFJ.006	65536
BXMMFJ.007	65536
BXMMFJ.008	65536
BXMMFJ.009	65536
BXMMFJ.010	65536
BXMMFJ.011	65536
BXMMFJ.012	65536
BXMMFJ.013	65536
BXMMFJ.014	65536
BXMMFJ.015	65536
BXMMFJ.016	65536
BXMMFJ.017	65536
BXMMFJ.018	65536
BXMMFJ.019	65536
BXMMFJ.020	65536
BXMMFJ.021	65536
BXMMFJ.022	65536
BXMMFJ.023	65536
BXMMFJ.024	44512
BXMMFJ.025	14
BXMMFJ.026	2
BXMMFJ.IMG	784
BXMMFJ.img	784

Appendix B

UXM Firmware ACC Release Notes

Introduction

ACC is a new 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 ACC.

UXM firmware ACB introduced the following features:

1. VSI Slave on UXM card.

: The VSI slave functionality enables the UXM card to be connected to an external MPLS controller (7200 series Router) and offers MPLS solutions to IGX customers.

2. ILMI on UXM card.

Obsolete Features

None.

Compatibility

1. Software

: ACC firmware is compatible with Switch Software Release 9.3.10 or later.

2. Hardware

: ACC firmware is compatible with UXM and UXM-E model hardware.

Bugs Resolved in ACC

UXM firmware ACC is a maintenance release. The open bugs known at this stage are listed in the Known Anomalies section of this appendix. The firmware release ACC also contains the bug fixes done in the Model B firmware up to revision ABJ and the fixes for the bugs CSCdr98036 and CSCdp05824, which were fixed after ABJ was released.

Upgrade Instructions

The firmware upgrade to ACC version requires that the run-time firmware to be first upgraded to an intermediate version, revision ABJ. However, before upgrading the firmware to revision ABJ, the boot code has to be upgraded to boot 8.

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

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

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.

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 pay attention to this section before loading the new firmware.

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

Step 1 Execute a graceful upgrade to Release 9.3.10 or later.

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

Known Anomalies

Bug ID	Description
CSCdr71426	Symptom: If the self-test frequency is set to one second (using cnftstparm), and upln is issued on a Standby UXM card, the card goes into a failed state and resets itself. Conditions: The card is in Standby. The line upped is not connected to any device on the other end. Workaround: Do not set the self-test frequency to one second.
CSCdr79193	Symptom: UXM OC-3 card goes into Active-F state when any port/trunk is in LOS. Condition: This only happens on a UXM OC-3 card when any of the ports/trunks is in LOS state. Workaround: Down the port/trunk.
CSCds34479	Symptoms: Software error 104 is logged. Conditions: When burning UXM boot revision 8. Workaround: Resetcd and reburn the boot.
CSCds69784	Symptoms: Software error 9000/C10A is logged when delyred is used. Conditions: Using delyred on IMA-T1. Workarounds: None.
CSCds77189	Symptoms: Software error C202,0x2f is logged. Conditions: During a full rebuild of the node, some of the keep alive messages from the Y-red pair are dropped. Workarround: None.
CSCds80842	Symptom: Software error C01C is sometimes logged when UXM switches from Active to HotStby. Effect: Will not affect existing connections. May reduce the number of CBAs available to VSI on the card. Workaround: Down the redundant card and reset the active card.
CSCds84317	Symptom: Neighbor discovery information, IfName/IfIndex, is being sent even though Neighbor Discovery is not enabled on the port. Conditions: The UXM port is up with ILMI enabled to run on the card, with ILMI polling and traps enabled. Workarounds: None.

Bugs Fixed in ACC

Bug ID	Description
CSCds01706	Symptoms: During burnfw operations on a Y-red pair, one of UXM receives a VSI_SW_RESYNC_END_RSP on on its YRED CVC, presumably from the other UXM pair and finds it is not in ACTIVE YRED state and drops the message causing it to log this 0xc202 (Fn code 0x87). Conditions: Intermittent. Workaround: Clear the software log and continue.
CSCds04085	Description: When the hot-standby card is syncing with the active card during the initial bring-up phase of the hot-standby card (addyred or resetcd), if the active card fails, the hot_standby will switchover to active. But some of its connection state may be dangling since the sync-up was not completed. This can cause a variety of problems including continuity failures through the card. Workaround: Reset the active card.
CSCds05041	Symptom: C02D is logged on the standby. Condition: Delyred executes on the Y-red pair. Workaround: Reset the standby card. This will not impact service since the card is already in the standby state.
CSCds13881	Symptoms: During a full rebuild of the node, the UXM card receives a new command before it completes processing the previous pending command. UXM than logs 0xC30E. Conditions: Intermittent Workaround: Clear the swlog. This is a trivial issue as the controllers resyncs after a period of time.
CSCds14102	Description: IfName may be incorrectly truncated to six bytes with the dspnebdisc command when a UXM is connected back-to-back to another UXM/BXM with ILMI enabled. Workaround: Refresh the screen.
CSCds20180	Symptoms: Loss of VSI connections for router via port that is reporting errors. Conditions: Hitless rebuild followed by Y-red switchover. Workaround: Reset the card.
CSCds42040	Symptoms: When the Cisco7200 (in Cisco IOS version 12.1(4.0.1)T) is operating as a Label Switch Controller for the IGX switch, label bindings may not succeed for all destinations. Some bindings remain in the ParentWait/BindWait state. In this state, MPLS will not function for those destinations. Conditions: This problem is only seen when the switch being controlled is the IGX and when the number of destinations/bindings is greater than 100. Workaround: Reduce the number of destinations/bindings that need to be created (change topology).
CSCds43364	Symptoms: When LCNs are increased and decreased in Y-red in such a way that a CBA block is released to the software during cnfrsrc. Conditions: The cards are in a Y-red pair and CBAs on the cards are out of sync.If a switchover is done the C01b's are getting logged.
CSCds43915	Symptoms: Router does not display neighbor information of IGX. IGX displays correct neighbor information of router. Conditions: Dncd/upcd causes this problem. Workaround: Resetcd will restore the information on the router.
CSCds58417	Symptoms: When two cards are a Y-red and one is down, resetting the active card will cause a TCB leak of two buffers when the card comes up. Conditions: Running rsh slot vsi DspVsiSize will show a TCB count of 15 instead of 17. Workaround: Do not reset the active card when the standby is down.
CSCds72010	Symptoms: Software error C30D logs during a hitless rebuild. Conditions: When there is a Y-red switch over from HotStandby to Active. Workaround: None.

Boot Code Requirements

Boot Code revision boot_08 is needed for the ACC 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.

e.g. T3 UXM config.

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

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

6. The complete list of the FAQs (Frequently Asked Questions) that assist in troubleshooting VSI/MPLS problems on IGX can be found at the URL:

http://wwwin-eng.cisco.com/Eng/WAN/IGX/WWW/VSI/igxvsifaq.htm

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 Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, Internet Quotient, 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, GigaStack, 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. (0201R)

Table of Contents

9.3.11 Version Software Release Notes Cisco WAN Switching System Software

MGX 8220 Firmware CompatibilityMGX 8850 Firmware Compatibility

switchIfTable

frLportCnfTable

atmPortTable

atmPortStatTable

atmEndptTable

atmTrunkStatsTable

rsrcPartiTable

rsrcPartiPvcTable

atmQbinTable

vsiCtrlrTable

atmPortTable

atmPortQueueTable

atmEndptTable

switchShelf configuration branch

atmTrunks table

rsrcPartiTable

rsrcPartiPvcTable

serialPortTable

switchIfTable

atmPortTable

atmEndptTable

shelfSlotInfoTable

ds3LineTable

sonetStatsTable

atmTrunkStatsTable

vsiCtrlrTable

Logic to Calculate Actual Cell Transmission Rate in a BXM Card is As Follows (CSCdm94372):

MGX 8220 Firmware Compatibility
MGX 8850 Firmware Compatibility