cc/td/doc/product/wanbu/bpx8600/9_3_0
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

9.3.00 Version Software Release Notes
Cisco WAN Switching System Software

9.3.00 Version Software Release Notes
Cisco WAN Switching System Software

About These Release Notes

Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.

About the 9.3 Release

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

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

Phased Release Strategy

The MSSBU and MSABU 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 below.

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

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 by selected customers. To trial an FCS feature, please contact your account representative. Customers selected for controlled introduction will receive assistance with 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

FCS

9.3.00

BPX

Support for 3 VSI Partitions

FCS

9.3.00

BPX

VSI MIB Support

FCS

9.3.00

BPX/IGX

800 Board Level Revision Number

FCS

9.3.00

BPX/IGX

Priority Bumping

FCS

9.3.00

BPX/IGX

SCR and PCR Policing at Less Than 50 CPS on BXM/BXM-E and UXM/UXM-E

FCS

9.3.00

BPX/IGX

Separate Abort Stack

FCS

9.3.00

BPX/IGX

Upgrades Protection

FCS

9.3.00

BPX/IGX

Control Traffic Shaping

FCS

9.3.00

IGX

2000 VC Bandwidth Parameters

FCS

9.3.00

IGX

UXM/UXM-E ATM Forum IMA Compliant Ports

FCS

9.3.00

Software release 9.3.00:

Introducing 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) which it's 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 towards these three partitions. An application of the feature is the support of a PNNI controller and two redundant MPLS controllers simultaneously.

    3. VSI MIB Support

Prior to this release, the BPX software neither kept nor knew the specific information about a VSI controller (e.g., type, capability, resource usage, etc.). A network management system 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 trouble shooting, 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 back cards.

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

    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 & 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 which 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 stat reserve at highest priority, bumping user traffic also trying to claim available bandwidth.

Clarifications

    1. For the 800-level part number, there is a dependency on the manufacturing to release boards with novram containing 800-level part number. There will be scenarios in which the 800-level part number can not be seen. See table below for the different combination:

    SWSW release NOVRAM contents SWSW CLI (dspcd/dspnovram etc.) display

    >= 9.3.00

    New novram

    Top Assembly Number which is 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 hence the user shall see 8 bytes only. Hence, there is no change in information compared to swsw < 9.3.00.

Notes:

    2. Changes in BPX Parameters

    52 CommBrk Hop Weight [ 25] (D) 53 CB Fail Penalty Hops [ 2] (D) 54 Auto BXM upgrade [ Y] (Y/N
    6 Disabled Priority Bumping
    28 CM updates app timeout [ 5] (10 secs)
    Region memory init 4 Disabled

    3. Changes in IGX parameters:

    52 CommBrk Hop Weight [ 25] (D) 53 CB Fail Penalty Hops [ 2] (D)
    28 CM updates app timeout [ 5] (10 secs)
    SVC Del Bgnd Updates

    4. The dsplog command has been enhanced in IB93. User-visible changes include:

With no arguments, there are no changes to this command.
Reverses the log, showing least recent entries first. This option allows you to see the bottom of the list quickly.
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 backwards and forwards through the log by pages (using "n" and "p") until "q" or DEL is pressed.
Timestamp mode. Begins log display with the entry nearest to the specified time. The time parameters must immediately follow the "t" option.
Integrated mode. Integrates a single-line summary of software error and abort log entries into the display (by timestamp). 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.

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

cnffdrlmiparms

    6. 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 can not 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 follow:
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


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

    8. There is a change in reporting of port group number in this release. The previous image (MEC) of BXM firmware used to report 1 port group for the 2 port group cards at the channel stats level 2 and 3. This made the port belonging to the 2nd 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 2 port groups for 2 port cards all the time. The smooth transition between the earlier 1port group and the newly reported 2 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 MEC or earlier firmware revision, the Channel Stats level 2 or 3 will report 1 port group. Burning a MED or later image will result in 2 port groups, but for backward compatibility the software will not do the re-computation of LCNs based on the new port groups. In its logical database this will not impact the Auto Route 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 that the newly configured card, or the card in standby mode programmed with an MED image brought to the active state, will not have above discrepancy.

    9. The minimum software required to run MPLS are:

or,

    10. 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% idle time usage. Use the command dspprfhist to verify.

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

    12. The trunk reconfiguration feature does not support IMA trunks.

Special Installation/Upgrade Requirements

General Upgrade Procedure

Note   Please consult your Support Representative before performing any software upgrade

The earliest release supported for 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

To enable BXM cards to utilize 9.3 features, all BXM cards must be upgraded to the 9.3 compatible firmware release. The following steps should be taken to avoid card mismatch:

If the switch is running

then perform the following steps to avoid card mismatch:

Step 1   Upgrade BXM firmware to MEC

Step 2   Upgrade BCC switch software to 9.3

Step 3   Upgrade BXM firmware to MFB

For all other cases, perform the following steps:

Step 1   Upgrade BXM firmware to MFB or higher

Step 2   Upgrade BCC switch software to 9.3

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

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

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

Revision Interoperability Supported

The Revision Interoperability feature allows a mixed/ heterogeneous network of 9.2.x and 9.3.x (where "x" equals any GA version of 9.2 and 9.3) nodes to coexist and interoperate. This capability allows 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 network 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:

VNS interworking with Release 9.3 is not tested at the present time.

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

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 the 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 64MB of RAM can not be mixed with BCC-4 cards.

Each redundant pair of NPM cards in a given IGX 8400 node must be of the 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 32MB of RAM cannot be mixed with NPM cards with 64MB 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. (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 back card. (Remove back card only apply to BCC)

Step 7   Replace with new CC front and back cards that are identical to the current active CC. (Replace back card only apply 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 only permitted 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:

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 & Cautions

Additional Notes

    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 which 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 as always..

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

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 table below.
The rate table below lists the highest 200 cell rates supported be 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 followed:
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 below




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.

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 table should be used. Otherwise, cell loss may be experienced. The table 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

.....

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

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

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

    7. Card errors (0x25170076) occur on BXM when only one Virtual Trunk is configured in a physical port. To avoid this situation, configure at least 2 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

    1. The 800 Board Level Revision Number is supported by software only. The hardware support will be released later.

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

    3. Standards compliant IMA trunks is not compatible with the proprietary IMA protocol used in revision A firmware.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. If multiple LSCs are attached to a VSI partition, the results are unpredictable.

    5. On BXM OC3, OC12 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 92 to 9.3.00.

    6. 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 the user is provided with a warning when he tries 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 un-recoverable state. Hence, before deleting a VSI partition, ensure that all the SPVC connections are deleted on that partition.

    7. 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) cells per second, 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 for shaping.

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.

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

    9. Due to performance reasons, AIS status of connections is not sent to the standby BCC. After switchcc, it may take few minutes to update the AIS status of connections. If dspcon does not show the proper status of AIS or dspalms screen shows incorrect number of AIS, (after switchcc) wait for few minutes so that the status gets updated. (dspalms and dspcon commands show the status of AIS).

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

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

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

    13. When upgrading from release 9.2 to 9.3, the 9.2 statistics on BXM/UXM cards are supported to maintain compatibility. However, once a user configures a statistics level in 9.3, he can not configure back to 9.2 stats.

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

    14. 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 3 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 stats enabled, etc.
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, etc. The approximation formula being:
max_stats_per_connection = 48,000 / number_of_connections

    15. We allow the transmit rate on an IGX IMA trunk to be altered at the local node with 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, we cannot add it back unless the transmit rates are the same.

    16. 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 non-graceful upgrade. This error can be ignored since it is harmless to the network.

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

    18. 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 2 feeder trunks, then only (52 - 2) = 50 ports can have LMI/ILMI enabled.
If LMI/ILMI is provided by the BXM firmware:

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

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

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

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

    23. Due to a hardware limitation, the BNI trunk will send 13 -15% 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.

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

    25. When deleting trunks, there is a known limitation with the switch software. The deltrk command should always be executed on the node which remains as part of the network, rather than from the node which 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).

    26. Due to Trunk Based Loading, any commands having to do with trunk loading and the load model (dspload chklm dsplm, etc.) 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.

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

    28. On a heavily loaded BPX 8600 node, during connection re-routing, 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 re-routing of the connections can be given high priority. The status will be eventually updated. (CSCdj10762)

    29. A node whose number is greater than 63 cannot have a clrcnf operation performed on it. This is as designed. A clrallcnf can be done, or the node must be renumbered to less than 63 before running clrcnf. (CSCdj14920)

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

    31. 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-3999 connections

    Polling Rate: 5 Minutes (or higher)

    4000-7999 connections

    Polling Rate: 10 Minutes (or higher)

    > 8000 connections

    Polling Rate: 15 Minutes

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

    33. When a physical-layer failure (e.g., 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 can not 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 only generate 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.

    34. There are problems in the fallback mechanism which 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 the 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).

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

    36. 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 cell per second (explained later why doing so).

    37. 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 that UBR service gains an unfair advantage over ABR service while sharing the same CoS queue.

    38. Combining Frame Base 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.

    39. The maximum number of VC PARMs supported:

i.e. one less that 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 VC's (exclusive of endpoints) use the same set of parameters.

    40. 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 re-routing, due to a trunk failure, will be delayed as provided by the parameter.

Required Workarounds:

    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. 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 only be done 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.

    3. 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 can take a long time. 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.

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

    5. 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 only an issue 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)

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

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

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 back plane which has dual traces incorporating with the BCC-4.

The command dspbpnv can be issued to verify if the node had the new back plane or the old back plane. The following table details the bit fields for the BCC Backplane NOVRAM format, the display of word 2 describes the back plane 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 - MSB

8

10,11

Board FAB number, in ASCII - MSB

9

12,13

Board FAB number, in ASCII - MSB

A

14,15

Board FAB number, in ASCII - MSB

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:

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 5.0 Firmware Compatibility

PCB Description CW2000 Name Latest F/W Min F/W

ASC F/W

ASC

5.0.11

5.0.10

ASC Boot

ASC

1.0.02

1.0.01

BNM-T3

BNM-T3

n/a

n/a

BNM-E3

BNM-E3

n/a

n/a

BNM-155

BNM-155

n/a

n/a

FRSM-4T1

FRSM-4T1

4.0.20

4.0.19

FRSM-4E1

FRSM-4E1

4.0.20

4.0.19

FRSM-4T1-C

FRSM-4T1-C

4.0.20

4.0.19

FRSM-4E1-C

FRSM-4E1-C

4.0.20

4.0.19

FRSM Boot

FRSM-4T1

4.0.00

4.0.00

FRSM Boot

FRSM-4E1

4.0.00

4.0.00

FRSM Boot

FRSM-4T1-C

4.0.00

4.0.00

FRSM Boot

FRSM-4E1-C

4.0.00

4.0.00

SRM T1E1 (B)

SRM-T1E1

n/a

n/a

SRM 3T3

SRM-3T3

n/a

n/a

CESM-4T1

CESM-4T1

4.0.16

4.0.15

CESM-4E1

CESM-4E1

4.0.16

4.0.15

CESM Boot

CESM-4T1

4.0.01

4.0.01

CESM Boot

CESM-4E1

4.0.01

4.0.01

CESM-8T1

CESM-8T1

5.0.11

4.1.05

CESM-8E1

CESM-8E1

5.0.11

4.1.05

CESM-8 Boot

CESM-8T1

1.0.01

1.0.01

CESM-8 Boot

CESM-8E1

1.0.01

1.0.01

AUSM-4T1

AUSM-4T1

4.0.20

4.0.19

AUSM-4E1

AUSM-4E1

4.0.20

4.0.19

AUSM Boot

AUSM-4T1

4.0.00

4.0.00

AUSM Boot

AUSM-4E1

4.0.00

4.0.00

FRSM-8T1

FRSM-8T1

5.0.11

5.0.10

FRSM-8E1

FRSM-8E1

5.0.11

5.0.10

FRSM-8T1 Boot

FRSM-8T1

1.0.02

1.0.01

FRSM-8E1 Boot

FRSM-8E1

1.0.02

1.0.01

AUSM-8T1

AUSM-8T1

5.0.11

5.0.10

AUSM-8E1

AUSM-8E1

5.0.11

5.0.10

AUSMB-8T1

AUSMB-8T1

5.0.11

5.0.10

AUSMB-8E1

AUSMB-8E1

5.0.11

5.0.10

AUSM-8T1E1 Boot

AUSM-8T1

1.0.02

1.0.01

AUSM-8T1E1 Boot

AUSM-8E1

1.0.02

1.0.01

AUSM-8T1E1 Boot

AUSMB-8T1

1.0.02

1.0.01

AUSM-8T1E1 Boot

AUSMB-8E1

1.0.02

1.0.01

FRSM-HS1

FRSM-HS1

5.0.11

4.0.16

FRSM-HS1/B

FRSM-HS1/B

5.0.11

4.0.16

FRSM-HS1 Boot

FRSM-HS1

1.0.01

1.0.01

FRSM-HS1 Boot

FRSM-HS1/B

1.0.01

1.0.01

FRSM-HS2

FRSM-HS2

5.0.11

5.0.10

FRSM-HS2 Boot

FRSM-HS2

1.0.01

1.0.01

IMATM

IMATM-T3T1

5.0.11

5.0.10

IMATM

IMATM-E3E1

5.0.11

5.0.10

IMATM

IMATMB-T1

5.0.11

5.0.10

IMATM

IMATMB-E1

5.0.11

5.0.10

IMATM Boot

IMATM-T3T1

1.0.02

1.0.01

IMATM Boot

IMATM-E3E1

1.0.02

1.0.01

IMATM Boot

IMATMB-T1

1.0.02

1.0.01

IMATM Boot

IMATMB-E1

1.0.02

1.0.01

MGX 8850 1.1 Firmware Compatibility

PCB Description CW2000 Name Latest F/W Min F/W

PXM1

PXM-1

1.1.22

1.1.22

PXM1-2-T3E3

PXM1-2T3E3

1.1.22

1.1.22

PXM1-4-155

PXM1-4OC3

1.1.22

1.1.22

PXM1-1-622

PXM1-OC12

1.1.22

1.1.22

MGX-SRM-3T3/B

SRM-3T3

n/a

n/a

AX-CESM-8E1

CESM-8E1

10.0.10

10.0.05

AX-CESM-8T1

CESM-8T1

10.0.10

10.0.05

MGX-AUSM-8E1/B

AUSMB-8E1

10.0.10

10.0.05

MGX-AUSM-8T1/B

AUSMB-8T1

10.0.10

10.0.05

MGX-CESM-T3

CESM-T3

10.0.10

10.0.05

MGX-CESM-E3

CESM-E3

10.0.10

10.0.05

AX-FRSM-8E1/E1-C

FRSM-8E1

10.0.10

10.0.05

AX-FRSM-8T1/T1-C

FRSM-8T1

10.0.10

10.0.05

MGX-FRSM-HS2

FRSM-HS2

10.0.10

10.0.05

MGX-FRSM-2CT3

FRSM-2CT3

10.0.10

10.0.05

MGX-FRSM-2T3E3

FRSM-2T3

10.0.10

10.0.05

MGX-FRSM-2T3E3

FRSM-2E3

10.0.10

10.0.05

MGX-FRSM-HS1/B

FRSM-HS1/B

10.0.05

10.0.04

MGX-VISM-8T1

VISM-8T1

1.5.01

1.5.01

MGX-VISM-8E1

VISM-8E1

1.5.01

1.5.01

MGX-RPM-128M/B

RPM

12.0(7)T

12.0(5)T1

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

MKB

MKB

BXM-T3-8/12

BXM-T3

BXM

F

MFB

MFB

BXM-E3-8/12

BXM-E3

BXM

F

MFB

MFB

BXM-155-4/8

BXM-155

BXM

F

MFB

MFB

BXM-622/622-2

BXM-622

BXM

F

MFB

MFB

BXM-T3-8E/12E/12EX

BXM-T3

BXM

F

MFB

MFB

BXM-E3-8E/12E/12EX

BXM-E3

BXM

F

MFB

MFB

BXM-155-4D/8D/4DX/8DX

BXM-155

BXM

F

MFB

MFB

BXM-622-2D/DX/2DX

BXM-622

BXM

F

MFB

MFB

IGX 8400 Firmware Compatibility

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

IGX-FRM

FRM

FRM

H

FHB

FHB

IGX-FRM

FRM

FRM

J

FJB

FJB

IGX-FRM-31

FRM

FRM-31

K

FKB

FKB

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

ZAP

ZAP

IGX-UFM-4C/8C

UFM

UFM-C

B

ZBA

ZBA

IGX-UFM-8C

UFM

UFM-C

C

ZCA

ZCA

IGX-UFM-U

UFMU

UFM-U

A

YAJ

YAJ

IGX-UFM-U

UFMU

UFM-U

B

YBA

YBA

IGX-UFM-U

UFMU

UFM-U

C

YCA

YCA

IGX-UVM

UVM

UVM

D

DDF

DDF

IGX-UVM

UVM

UVM

E

DED

DED

IGX-UXM

UXM

UXM

B

ABH

ABH

IGX-UXME

UXM

UXM

B

ABH

ABH

Note   IGX-UVM model E is a super set of models A, B, and C firmware. A, B, and C are obsoleted 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"

FRSM

FRSM-8T1E1

"AA, AB, AC"

FRSM-8T1E1

FRSM-HS1

"AA, AB, AC, AD, AE, AH, AJ"

FRSM-HS1

FRSM-HS1/B

AA

FRSM-HS1

FRSM-HS2

AO

FRSM-HS2

CESM-4T1E1

"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

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

A

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

B

A

BPX-BXM-155-4

800-02666-07

J

B (C for APS)

BPX-BXM-155-4D

800-03094-01

A

A

BPX-BXM-155-8D

800-03092-01

A

A

BPX-BXM-155-4DX

800-03093-01

A

A

BPX-BXM-155-8DX

800-03091-01

A

A

BPX-MMF-155-4-BC

800-03256-01

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-622-2D

800-03150-01

A

A

BPX-BXM-622DX

800-03151-01

A

A

BPX-BXM-622-2DX

800-03149-01

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

800-02738-01

C

A

BPX-XLR-622-2-BC

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

800-03716-02

A

A

BPX-BNI-3-T3/C

800-02858-02

A

A

BPX-BNI-3-E3/B

800-02859-02

A

A

BPX-T3-BC

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 (A)

73-2296-04

E

A

IGX-NTM (B)

IGX-NTM (C)

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

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

BC-UAI-4SMFXLR

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

IGX-UFM-8C

73-2531-05

N

A

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-2J1EC

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

CSCdp45833

Symptom:

Users of VNS may experience poor voice quality. dspchst on the connections shows data in one direction.

When the command xlat_verify is run software error 332 is logged with FFF1 in the data field. This usually seen on the slave and via nodes of the leftover SVC. The master node shows it as deleted. dspcon on the slave and dspviacons on the via show the leftover conn.

Conditions:

CSCdm86633 in 9.1.16 fixed most occurrences but not all of the dangling SVC conns and hence occasionally poor voice.

Workaround:

Manual updates could be sent through the updates 3 * command to clean dangling SVC lcons.

CSCdp85319

Symptom:

The maxVPC Conid field of a trunk is not retained after switchcc/node rebuild. Hence, if we have VSI partitions on an added trunk, and if one of the nodes undergoes switchcc or rebuild, there will be VPC Conid mismatch on both sides of the trunk. This may result in some VPIs being used by both VSI and Auto Route VPC connections.

Condition:

This happens only on an added trunk and only if it has VSI partitions on the trunk interface.

Workaround:

None

CSCdp86866

Symptom:

Only the last event of the series of events came in back to back is sent to CWM. The others are lost.

Condition:

This happens if APS events came in back to back.

Workaround:

None

CSCdr02297

Symptom:

addshelf and vsi partition are using the same VPI. This can cause combreak.

Condition:

addshelf (i, a, or x) using cnfrsrc to configure vsi range to cover VPI = 1 and/or 3.

Workaround:

None

CSCdr10473

Symptom:

Software error 1012 will be logged when the total connection channels on a UXM card exceeds the available lcns on that card. The events hitless rbld, switchcc, node rbld, resetcd triggers the recalculation of lcns configured on ports and trunks activated on the card and during this process, if software finds the total configured channels exceeds the available lcns, then it logs swerr 1012. As soon as it hits swerr 1012, it resets the total used card lcns to the endpoints on that card. i.e. If there are 1000 connections originating or terminating on this card, the total # of lcns used field points to only 1000, though this card has trunks activated if any which is not accounted.

It is strongly recommended to execute the workaround enclosed here before doing any connection provisioning (addition, rerouting) on this card.

Condition:

This may occur due to the following reason:-

a) "connection channels" configured per UXM trunk can be corrupted during the collision of "connection channel" reconfiguration at the same time on one side of the trunk.

UXM_1 @ NODE A ----- UXM_2 @ NODE B

i.e. Re-configuring the connection channels on any one trunk (UXM_1) and any one trunk (UXM_2) at the same time may lead to the corruption of the "connection channels" field. This is a very rare condition.

Workaround:

a) Loop through all the trunks activated and check for the # of channels configured per trunk.

b) Add (270* # trunks upped) to the above (270 is for networking traffic) if it a legacy UXM card. If it is UXM-E, just add 270 to the above irrespective of the number of trunks activated.

c) Add "total # endpoints originating or terminating on this card" count to the above.

d) Make sure the total of all the above should not exceed the "total lcns" supported.

If it exceeds, then reconfigure in such a way to meet the above condition.

CSCdr10575

Symptoms:

Conid Mismatch software error 331 logged after a hitless rebuild.

Conditions:

1.) The errors are logged on the via node on which a hitless rebuild occured.

2.) There are connections which are currently routing through this node. The routing request is received. The conid manager is not ready because the node went through a hitless rebuild.

3.) Errors 331 logged in this situation are benign.

Workaround:

There is no workaround. These errors can be safely removed.

CSCdr10771

Symptom:

Software error 116 is logged.

Conditions:

This happens VERY rarely, we saw it twice.

When the node is very busy, if you try to reset an UXM card which is loaded, you may see swerr 116 (very rare).

Workaround:

Capture & clear the swlog. Reset the UXM card which is giving swerr 116 again, will clear the problem.

CSCdr17056

Symptom:

NMS does not move connections to standby node when the card in the primary node is removed and the standby node/port lifts the lead state.

Conditions:

NMS can not detect hardware failure or missing card in the switch.

Workaround:

When the card is removed, the connection needs to be moved to standby node by operation.

CSCdr21164

Symptoms:

Software error 265s are logged. 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 92 -> 9.3.00.

Conditions:

The following conditions are needed for this problem to occur.

1) The BXM card is an OC3 / OC12 8DX / 2DX enhanced card and has ports upped.

2) The Queue depth(s0 for CBR / rt-VBR / nrt-VBR / UBR/ABR are configured to be greater than 262143 using the cnfportq command.

Customer Impact:

1) Set Queue depth(s) greater than 262143 when switch is running 9.3.00:

a) Sw error 265s will be logged as a result of the failure to update BRAM.

b) Any other changes to the port configuration (or other ports' configuration) will cause additional 265s.

c) When a rebuild occurs now, the new configuration for the port(s) with large queue depths will be lost. The switch reverts back to the old configuration. At this point, these ports have to be reconfigured to the new configuration.

2) Set Queue depth(s) greater than 262143 when switch is running 9.3.00, followed by an upgrade from 92 -> 9.3.00:

a) Sw error 265s will be logged as a result of the failure to update 9.3.00 BRAM.

b) Any other changes to the port configuration (or other ports' configuration) will cause additional 265s.

c) When a rebuild occurs now, the port(s) with large queue depths will be lost. At this point, these ports and connections if any have to be brought up again and configured.

Workaround:

Do not configure the queue depth(s) to be greater than 262143.

.

Additional Deliverables

SNMP MIB

The SNMP IGX/BPX switch SNMP MIB is being provided with the delivery of Release 9.3.00 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

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 end-point, contains the traffic parameters for ATM end-point

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.

sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set 1 Priority Bumping Enabled [ NO] 2 Priority Bumping Bundle [ 10] (D) 3 Priority Bumping Bands: Band 1 [ 2] (D) Band 2 [ 4] (D) Band 3 [ 6] (D) Band 4 [ 8] (D) Band 5 [ 10] (D) Band 6 [ 12] (D) Band 7 [ 14] (D) Last Command: cnfbmpparm sailorm TN Cisco BPX 8620 9.3.00 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 [ 50] (D) 4 Comm-Break Test Offset [ 10] (D) 19 Gateway ID Timer [ 30] (D) 5 Network Timeout Period [ 1700] (D) 20 GLCON Alloc Timer [ 30] (D) 6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [ 60] (D) 7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [ 50] (D) 8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [ 560] (D) 9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [ 280] (D) 10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [ 56] (D) 11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [ 7680] (D) 12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [ 256] (D) 13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [ Y] (Y/N) 14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [ 1] (D) 15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [ 10] (D) 31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [ 100] (D) 32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D) 33 Job Lock Timeout [ 60] (D) 48 Send Abit early [ N] (Y/N) 34 Max Via LCONs [50000] (D) 49 Abit Tmr Multiplier M [ 0] (D) 35 Max Blind Segment Size [ 3570] (D) 50 Abit Tmr Granularity N [ 3] (D) 36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [ N] (Y/N) 37 Max Mem on Stby Q (%) [ 33] (D) 52 CommBrk Hop Weight [ 25] (D) 38 Stat Config Proc Cnt [ 1000] (D) 53 CB Fail Penalty Hops [ 2] (D) 39 Stat Config Proc Delay [ 2000] (D) 54 Auto BXM upgrade [ Y] (Y/N) 40 Enable Degraded Mode [ Y] (Y/N) 41 Trk Cell Rtng Restrict [ Y] (Y/N) 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 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set 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 sailorm TN Cisco BPX 8620 9.3.00 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 This Command: cnfswfunc sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 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 [ 0] (secs) 10 Reset Timer on Line Fail [ Yes] 11 Max Down/Up Per Pass [ 50] (D) 12 Down/Up Timer [30000] (msecs) 13 Max Route Errs per cycle [ 50] (D) 14 Time between Rrt cycles [ 5] (mins) 15 Max. Rrt Err cycles [ 10] (D) 16 Routing pause timer [ 0] (msecs) 17 Max msgs sent per update [ 10] (D) 18 Send SVC urgent msg [ No] 19 Max SVC Retry [ 0] (D) 20 Wait for TBL Updates [ 70] (100 msecs) 21 Max Derouting Bndl (0=all)[ 500] (D) 22 Enable Cost-Based Routing [ No] 23 Enable Route Cache Usage [ No] 24 Use Delay for Routing [ No] 25 # of reroute groups used [ 50] (D) 26 Starting size of RR grps [ 0] (CLU) 27 Increment between RR grps [ 100] (CLU) 28 CM updates app timeout [ 5] (10 secs) This Command: cnfcmparm sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 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 sailorm TN Cisco BPX 8620 9.3.00 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

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 1.1 Config T3 [96000 cps] BNI-T3 slot: 1 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 1.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 1.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 1.1

BNI-E3

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 2.1 Config E3 [80000 cps] BNI-E3 slot: 2 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 2.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 2.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 2.1

BNI-155/155E

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 3.1 Config OC3 [353207cps] BNI-155 slot: 3 Transmit Rate: 353208 VPC Conns disabled: -- Protocol By The Card: -- Line framing: STS-3C VC Shaping: -- coding: -- Hdr Type NNI: -- recv impedance: -- Statistical Reserve: 5000 cps cable type: -- Idle code: 7F hex length: -- Connection Channels: 16050 Pass sync: No Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No 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 3.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 3.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 3.1

BXM-T3

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 10.1 Config T3 [96000 cps] BXM slot: 10 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 10.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 10.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 10.1

BXM-E3

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 11.1 Config E3 [80000 cps] BXM slot: 11 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 11.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 11.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 11.1

BXM-OC3

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 10.1 Config OC3 [353207cps] BXM slot: 10 Transmit Rate: 353208 VPC Conns disabled: No Protocol By The Card: No Line framing: STS-3C VC Shaping: No coding: -- Hdr Type NNI: Yes recv impedance: -- Statistical Reserve: 5000 cps cable type: -- Idle code: 7F hex length: -- Connection Channels: 256 Pass sync: No Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No 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 10.1 sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 10.1 Parameters 1 Q Depth - rt-VBR [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec) 2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec) 3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [20000] (Dec) 4 Q Depth - BData A [10000] (Dec) 18 Low CLP - CBR [ 60] (%) 5 Q Depth - BData B [10000] (Dec) 19 High CLP - CBR [ 80] (%) 6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%) 7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%) 8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%) 9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%) 10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%) 11 High CLP - BData A [ 100] (%) 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 10.1

BXM-OC12

sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 5.1 Config OC12 [1412679cps] BXM slot: 5 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 5.1 Next Command: sailorm TN Cisco BPX 8620 9.3.00 Date/Time Not Set TRK 5.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 5.1

IGX 8400 Nodes

mulder TN Cisco IGX 8420 9.3.00 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.00 Date/Time Not Set 1 Priority Bumping Enabled [ NO] 2 Priority Bumping Bundle [ 10] (D) 3 Priority Bumping Bands: Band 1 [ 2] (D) Band 2 [ 4] (D) Band 3 [ 6] (D) Band 4 [ 8] (D) Band 5 [ 10] (D) Band 6 [ 12] (D) Band 7 [ 14] (D) Last Command: dspbmpparm mulder TN Cisco IGX 8420 9.3.00 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 TFTP Memory (x 10KB) [ 210] (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 [ 50] (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 [ 0] (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) 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.00 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.00 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.00 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 VXM 300 Enabled 100 300 800 Enabled 100 300 RXM 300 Enabled 100 300 800 Enabled 100 300 UDM 300 Enabled 100 300 80 Enabled 100 300 This Command: cnftstparm mulder TN Cisco IGX 8420 9.3.00 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 [ 0] (secs) 10 Reset Timer on Line Fail [ Yes] 11 Max Down/Up Per Pass [ 50] (D) 12 Down/Up Timer [30000] (msecs) 13 Max Route Errs per cycle [ 200] (D) 14 Time between Rrt cycles [ 5] (mins) 15 Max. Rrt Err cycles [ 1] (D) 16 Routing pause timer [ 0] (msecs) 17 Max msgs sent per update [ 10] (D) 18 Send SVC urgent msg [ Yes] 19 Max SVC Retry [ 0] (D) 20 Wait for TBL Updates [ 70] (100 msecs) 21 Max Derouting Bndl (0=all)[ 500] (D) 22 Enable Cost-Based Routing [ No] 23 Enable Route Cache Usage [ No] 24 Use Delay for Routing [ No] 25 # of reroute groups used [ 50] (D) 26 Starting size of RR grps [ 0] (CLU) 27 Increment between RR grps [ 100] (CLU) 28 CM updates app timeout [ 5] (10 secs) This Command: cnfcmparm mulder TN Cisco IGX 8420 9.3.00 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.00 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 mulder TN Cisco IGX 8420 9.3.00 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.00 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.00 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

NTM-SR

mulder TN Cisco IGX 8430 9.3.00 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 Last Command: dsptrkcnf 7 mulder TN Cisco IGX 8430 9.3.00 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

NTM-T1

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 9 Config T1/24 [8000 pps] NTM slot:9 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 Last Command: dsptrkcnf 9 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 9 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 9

NTM-E1

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 10 Config E1/32 [10666 pps] NTM slot:10 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 Last Command: dsptrkcnf 10 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 10 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 10

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

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 11.1 Config T1/24 [3622 cps] UXM slot:11 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 Last Command: dsptrkcnf 11.1 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 11.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 11.1

UXM-T1-IMA (4 physical lines up)

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 11.1(4) Config T1/95 [14339 cps] UXM slot:11 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 Last Command: dsptrkcnf 11.1 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 11.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 11.1

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

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 12.1 Config E1/30 [4528 cps] UXM slot:12 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 Last Command: dsptrkcnf 12.1 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 12.1 Config E1/30 [4528 cps] UXM slot:12 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 Last Command: dsptrkcnf 12.1

UXM-E1-IMA (4 physical lines up)

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 12.1(4) Config E1/119 [17962 cps] UXM slot:12 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 Last Command: dsptrkcnf 12.1 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 12.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]TRK 12.1(4) Parameters: Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%) 35 CBR [ 600] 38 CBR [ 600] 36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000] 37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20] Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%) 41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60] 42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60] 43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60] This Command: cnftrkparm 12.1

UXM-T3

mulder TN Cisco IGX 8430 9.3.00 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 8430 9.3.00 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-E3

mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 14.1 Config E3/530 [80000 cps] UXM slot:14 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 Last Command: dsptrkcnf 14.1 mulder TN Cisco IGX 8430 9.3.00 Date/Time Not Set TRK 14.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 14.1

UXM-OC3

mulder TN Cisco IGX 8420 9.3.00 Date/Time Not Set TRK 7.1 Config OC3 [353207cps] UXM slot:7 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 Last Command: dsptrkcnf 7.1 mulder TN Cisco IGX 8420 9.3.00 Date/Time Not Set TRK 7.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 7.1

Appendix A

BXM Firmware MFB Release Notes

About the Firmware MFB

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

Front Cards

Model Num Description FW model HW Rev FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

B

MFB

BXM-155-8

8 port OC3 Line Module (Front Card)

F

B

MFB

BXM-622

1 port OC12 Line Module (Front Card)

F

D

MFB

BXM-622-2

2 port OC12 Line Module (Front Card)

F

D

MFB

BXM-T3-8

8 port T3 Line Module (Front Card)

F

B

MFB

BXM-T3-12

12 port T3 Line Module (Front Card)

F

B

MFB

BXM-E3-8

8 port E3 Line Module (Front Card)

F

B

MFB

BXM-E3-12

12 port E3 Line Module (Front Card)

F

B

MFB

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A

MFB

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A

MFB

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A

MFB

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A

MFB

BXM-T3-12EX

12 port T3 Line Module (Front Card)

F

A

MFB

BXM-T3-12E

12 port T3 Line Module (Front Card)

F

A

MFB

BXM-T3-8E

8 port T3 Line Module (Front Card)

F

A

MFB

BXM-E3-12EX

12 port E3 Line Module (Front Card)

F

A

MFB

BXM-E3-12E

12 port E3 Line Module (Front Card)

F

A

MFB

BXM-E3-8E

8 port E3 Line Module (Front Card)

F

A

MFB

Front Card for APS Compatibility

Model Num Description FW model HW Rev FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

C

MFB

BXM-155-8

8 port OC3 Line Module (Front Card)

F

C

MFB

BXM-622

1 port OC12 Line Module (Front Card)

F

E

MFB

BXM-622-2

2 port OC12 Line Module (Front Card)

F

E

MFB

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A

MFB

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A

MFB

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A

MFB

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A

MFB

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A

MFB

Back Cards

Model Num 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 OC12 back card

A

na

SMF-622-2

2 port intermediate-reach OC12 back card

A

na

SMFLR-622

1 port long-reach OC12 back card

A

na

SMFLR-622-2

2 port long-reach OC12 back card

A

na

XLR-622

1 port extra long-reach OC12 back card

A

na

XLR-622-2

2 port extra long-reach OC12 back card

A

na

BPX-T3/E3-12

12 port T3/E3 back card

A

na

BPX-T3/E3-8

8 port T3/E3 back card

A

na

RDNT-LR-622-2

2 port long-reach OC12 redundant back card

A

na

RDNT-SM-622-2

2 port intermediate reach OC12 redundant back cards

A

na

RDNT-SM-622

1 port intermediate reach OC12 redundant back cards

A

na

RDNT-LR-155-8

8 port long-reach OC3 redundant back cards

A

na

RDNT-SM-155-4

4 port intermediate-reach OC3 redundant back cards

A

na

RDNT-SM-155-8

8 port intermediate-reach OC3 redundant back cards

A

na

New Features supported in BXM Firmware 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-OC3 and BXM-OC12 (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 Multi-Level Channel Statistics

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

    4. Support for card based LMI and ILMI

Clarifications

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

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

Special Installation/Upgrade Requirements

BXM cards with M.C.B/M.D.A firmware or later can be smoothly migrated to the M.F.A 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 MFB firmware version and wait for all the configuration to be downloaded into the card. Do a switchyred to switch to the card with firmware M.F.A and burn the other card also with M.F.A firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.

Features obsoleted

VSI 1.0 is obsoleted by VSI 2.2 in this release.

Notes & Cautions

    1. MFA is fully compatible with 9.1 and 9.2 Switch Software. It has not been tested for compatibility with 8.4 or 8.5 Switch Software. It is compatible with IOS version 12.05t2 for MPLS

    2. While upgrading from firmware, on OC3, 1 port OC12 BXM cards, if stats level on BXM is greater than 1, the upgrade should take place according to the one of the upgrade procedures below.

Upgrading from firmware revision MEA or higher.
Step 1   Upgrade swsw to 9.2.30 or higher.

Step 2   Upgrade the firmware to MFB.

To avoid card mismatch when upgrading from firmware revision lower than MEA:
Step 1   Upgrade firmware to MEC.

Step 2   Upgrade the swsw to 9.2.30 or higher revision.

Step 3   Upgrade the firmware to MFB.

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

    4. Protection Switching based on BER on BXM may not comply to standards. The GR-253 & 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.

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

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

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

    8. When APS Annex B is added to local end which has the Secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If Secondary card is active, then do a switchyred to make 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

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.

CSCdp05098

Symptom:

Cell discards occur for ABRFST/ABRSTD conns 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 conn are configured with PCR=72000/72000, MBS=1000/1000 and ICR 7200/7200. This is the expected behaviour since the configured MBS < the actual burst size.

Workaround:

Increase the MBS and ICR using cnfcon.

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 excuted 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 doesnot 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 cuurent 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 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

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 intialized 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 itwas changed to uni-dir mode. Fixed by clearing all alarms when re-configuringthe 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:

re-impose the selector and bridge states on both ACTIVE and STANDBY cards aftera 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 upone card removal when lockout is set

Workaround:

None Upgrade to MEF or newer version of firmware

CSCdp49749

Symptom:

node unreachable after resetting two nodes in the network

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 th 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 eventhough 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)

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 Deliniation occurs

Workaround:

None

CSCdp59727

Symptom:

Addlnlocrmt causes node unreachable

Workaround :

Reset the BXM card

Appendix B

UXM Firmware ABH Release Notes

Introduction

ABH is new firmware relelase for UXM card on IGX. Firmware is the same for UXM and UXM-E cards.

New Features

UXM firmware ABH introduces the following features:

    1. CC Traffic Shaping,

Allowing user traffic exclusive use of available trunk bandwidth in favor of CC traffic. CC Traffic is given highest priority to allow network communication to take place effectively. In previous versions of firmware the CC traffic may use available trunk bandwidth in excess of the Stat Reserve at the highest priority; thus, bumping user traffic also trying to momentarily claim available bandwidth. Now user traffic is given exclusive rights to available bandwidth.

    2. Established IMA Groups may be reconnected to different physical ports without the need for reprogramming group.

For example, links in an IMA group may be disconnected from their originally programmed physical ports and moved to another set of physical ports that have been, or will be, configured as an IMA group that matchs the far end. Previously, disconnecting and reattaching links to a group of different physical ports would have required deleting the IMA group and then reconfiguring.

    3. Revision G Hardware Support.

If previous versions of UXM firmware are installed in the rev. G cards and plugged into a slot previously occupied by a UXM card, then it will come up in a MISMATCH state.

Obsolete Features

None

Compatibility

    1. Software

ABH firmware is compatible with Switch Software 9.1, 9.2 and 9.3.

    2. Hardware

ABH is compatible with UXM and UXM-E model H/W all models.

    3. Previous versions of UXM firmware:

On IMA trunks this version is not compatible with UXMs Model B firmware versions ABA to ABD.
On IMA trunks Model B firmware (AB*) is not compatible with model A (AA*) because model B is Standards compliant and model A is not. So IMA trunks must be upgraded together.

Upgrade Instructions

Upgrade boot code to boot 06 if not already installed then upgrade the firmware. Then reset the card.

Notes and Cautions

UXM back card dissappears intermittantly. This only occurs infrequently (CSCdp27320 ).

Boot Code Requirements

Boot Code revision boot_06 is needed for ABH release.

Bugs Fixed in ABH

Bug ID Description

CSCdp55689

UXM becomes unavailable after upcd logging swerr 121

SYMPTOM:

When the card is downed and then upped, first the card becomes active and then after sometime it resets itself and then goes into unavailable state. The three front panel LED's, FAIL, ACTIVE, and STANDBY, are illuminated. Also swerr 121 is logged.

CIRCUMSTANCES:

The problem usually happens on UXMs with T3/E3 or OC3 backcards when the downcd upcd sequence is performed.

FREQUENCY:

Happens 5 out of 10 times on UXMs with T3/E3 backcard. Less frequent with OC3 backcards.

WORKAROUND:

resetcd will bring back the card to active state.

CSCdp34278

IMA group status change

SYMPTOM:

IMA trunks/lines in inverse mux failure due to near-end insufficient number of links remain in the same condition even after reconfiguring the number of retained links to less than or equal to the number of good links.

CIRCUMSTANCES:

Occurs only on IMA groups that are in INVERSE MUX FAILURE due to near end insufficient number of good links, and the number of retained links for the group is reduced to the number of good links or less.

FREQUENCY:

Repeatable.

WORKAROUND:

1) Reduce the retained number of links when the group is up and functional.

2) Physically pull out a link and plug it back in.

CSCdp34265

Transition from IMA to Non-IMA causes swlog (feature enhancement).

SYMPTOM:

Reconfiguring an IMA group to a single link causes a 9081 software error to be logged.

CIRCUMSTANCES:

Set up an IMA trunk/line with more than one line. Reduce the number of retained links to one. Change the group members to one link and disable IMA protocol in the same command.

FREQUENCY:

Reproducible under the above circumstances.

WORKAROUND:

Reduce the group members to 1 link in one "cnftrk" command, and in another "cnftrk" command disable the IMA Protocol Option.

CSCdp79114

9081 software error logged when changing links in an IMA group and upping another link on the card.

SYMPTOM:

UXM standby card in a YRED setup logs software error 9081 and software error 103.

The following sequence of byes shown in "dspswlog d" indicate the error:

52 00 51 00 00 00 02 BC 13

CIRCUMSTANCES:

Happens only on the standby card in a Y-Redundancy configuration with E1/T1 IMA backcards when the number of links is changed.

FREQUENCY:

Reproducible under the above circumstances.

WORKAROUND:

Do not do cnftrk/cnfln to reduce number of member lines. Down the trunk/line and bring it up again with required number of member lines.

CSCdp74681

Connection drops traffic after cnfcon.

SYMPTOMS:

Connections start dropping traffic after cnfcon.

CIRCUMSTANCES:

The sum of minimum rates of all connections on a port are near max port speed, and PCR is decreased on one or more connections and increased on others using cnfcon (or more connections are added

subsequently).

Data loss may be observed on connections that were re-configured, or ant other connection on that port.

FREQUENCY:

Reproducible when the sum of min rates >= port speed and utilization is very high (more than 90%).

WORKAROUND:

Resetting the card should reprogram the connections and bring it back to good state.

CSCdp65736

Link with intolerable delay is allowed to be added to the group and in Clear-ok state.

SYMPTOM:

Whenever a link which is having intolerable delay is added to the IMA group it would show up as being OK in the dspphyslns. The link would get added to the group and the error would not be reported.

CIRCUMSTANCES:

The new link being added needs to have differential delay more than the maximum tolerable delay for that IMA group. The maximum tolerable delay for that group can be seen in the dsptrkcnf or dsplncnf commands.

FREQUENCY:

Reproducible under the above circumstances.

WORKAROUND:

None

CSCdp93240

VI programmed incorrectly for IMA trunk/lines.

SYMPTOM:

Trunk drops traffic on IMA trunk/lines. One example of the error is:

TRK Type Current Line Alarm Status Other End

15.3(4) T1/95 Major - QBIN: Tx NTS Cells Discarded other01/29.3(4)

(THIS IS NOT SPECIFIC TO NTS DISCARDS!)

The command dsptrkstats show discarded cells in the QBIN which is an indication of this problem.

CIRCUMSTANCES:

There must be a UXM IMA group (more than one link) and another trunk (which may or may not be an IMA group) configured on the same card.

FREQUENCY:

Reproducible under above conditions.

WORKAROUND:

None

CSCdp64808

Commbreak/Node goes unreachable.

SYMPTOM:

Commbreak on trunk after performing "switchcc". On nodes with a single trunk connecting them to the rest of the network they will become unreachable. After doing switchCC on IGX, the last hop channel (1) is not getting programmed on the UXM trunk. As a result of this, all other nodes are in commbreak with this node.

CIRCUMSTANCES:

Happens on nodes running switch software 9.3.00 and above and UXM trunk cards running ABF or below. Nodes go unreachable after doing a switchcc.

FREQUENCY:

Reproducible under above circumstances.

WORKAROUND:

Reset both UXM cards at each end of the trunk at the affected node.

CSCdm39109

IMA failure, UXM resets with 0B BCBC error.

SYMPTOM:

Multiple IMA Protocol failures due to trunk clocking problems or trunk errors can lead to the UXM resetting with hardware error 0B.

UXM resets. On query of log, a flurry of "IMA Protocol Status OK" messages are seen. These indicate the IMA trunk/line is going into and out of error. Eventually, a fault on the backcard, the BCBC error, caused by the IMA Protocol errors triggers a UXM reset.

CIRCUMSTANCES:

This has been seen to happen when there is a bad line in the IMA group. The frequency depends on how bad the line errors are. Whenever there is a burst of errors on the line usually this symptom is seen.

FREQUENCY:

This may not happen for weeks and then suddenly happen 2-3 times in a day.

WORKAROUND:

Check clocking is correct and clean trunks. Observe physical line errors to verify.

CSCdp97100

UXM cards failing and resetting themselves.

SYMPTOM:

On February 29, some UXMs and UXMEs, have reset which can interrupt user traffic if the UXM is in use.

CIRCUMSTANCES:

UXM cards automatically removing themselves from IGX after date changes over from FEB 28 to FEB 29.

FREQUENCY:

On Feb. 29, every leap year.

WORKAROUND:

Change network time or date such that all nodes in the network are set to a date and time after March 1.

CSCdp81744

IMA group shows Inverse MUX failure but individual trunks/ lines OK.

SYMPTOM:

When adding an IMA group it is possible that the group will not come out of the INVERSE MUX FAILURE despite the fact that all links in the group are not in physical level alarm. Inverse Mux Failure appears after upping IMA line or trunk and does not clear.

CIRCUMSTANCES:

Adding IMA groups with number of links greater than one and retained links equal to one.

FREQUENCY:

Repeatable.

WORKAROUND:

When configuring the trunk or line to include other links in the IMA group set the retained links to 2 or greater, up to the maximum number of links in the group. Once the link comes up, then the number

of retained links can be reduced back to one if so desired.

CSCdp57824

ABRSTD conns drop traffic when traffic shaping is turned on.

SYMPTOM:

Traffic on standard ABR (no VSVD or Foresight (FST)) connections will be seen as very slow, or not passing at all. CBR/VBR connections are not affected.

CIRCUMSTANCES:

This has been seen in software 9.2.2x, and all UXM firmware model B, revs A-F.

FREQUENCY:

Reproducible under above conditions.

WORKAROUND:

This is a two step process:

1. Disable VC shaping on both sides of the trunk Use the command "CNFTRK <slot>.<line>" and set VC Shaping to "NO".

2. "Bounce" the connections. "Bouncing" includes any one of the following:

rrtcon, down/up, delete/add, failed/cleared.

3. Wait for the transmit VC queue (on the trunk) to empty. This could take as long as 15 minutes, depending on how full the queue was. e.g. rrtcon <slot>.<line>.<vpi>.<vci>

Obtaining Documentation

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.

Documentation CD-ROM

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

Ordering Documentation

Registered CCO users can order the Documentation CD-ROM and other Cisco Product documentation through our online Subscription Services at http://www.cisco.com/cgi-bin/subcat/kaojump.cgi.

Nonregistered CCO users can order documentation through a local account representative by calling Cisco's corporate headquarters (California, USA) at 408 526-4000 or, in North America, call 800 553-NETS (6387).

Obtaining Technical Assistance

Cisco provides Cisco Connection Online (CCO) as a starting point for all technical assistance. Warranty or maintenance contract customers can use the Technical Assistance Center. All customers can submit technical feedback on Cisco documentation using the web, e-mail, a self-addressed stamped response card included in many printed docs, or by sending mail to Cisco.

Cisco Connection Online

Cisco continues to revolutionize how business is done on the Internet. Cisco Connection Online is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

CCO's broad range of features and services helps customers and partners to streamline business processes and improve productivity. Through CCO, you will find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online support services, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on CCO to obtain additional personalized information and services. Registered users may order products, check on the status of an order and view benefits specific to their relationships with Cisco.

You can access CCO in the following ways:

You can e-mail questions about using CCO to cco-team@cisco.com.

Technical Assistance Center

The Cisco Technical Assistance Center (TAC) is available to warranty or maintenance contract customers who need technical assistance with a Cisco product that is under warranty or covered by a maintenance contract.

To display the TAC web site that includes links to technical support information and software upgrades and for requesting TAC support, use www.cisco.com/techsupport.

To contact by e-mail, use one of the following:

Language E-mail Address

English

tac@cisco.com

Hanzi (Chinese)

chinese-tac@cisco.com

Kanji (Japanese)

japan-tac@cisco.com

Hangul (Korean)

korea-tac@cisco.com

Spanish

tac@cisco.com

Thai

thai-tac@cisco.com

In North America, TAC can be reached at 800 553-2447 or 408 526-7209. For other telephone numbers and TAC e-mail addresses worldwide, consult the following web site: http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml.

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, for your convenience many documents contain a response card behind the front cover. Otherwise, you can mail your comments to the following address:

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

We appreciate and value your comments.

Note   If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Mon Jan 15 11:57:00 PST 2001
All contents are Copyright © 1992--2001 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.