Guest

Cisco BPX/IGX/IPX WAN Software

9.3.53 Version Software Release Notes Cisco WAN Switching System Software

 Feedback

Table Of Contents

9.3.53 Version Software Release Notes Cisco WAN Switching System Software

Table of Contents

About the 9.3.53 Release

Phased Release Strategy

Definitions

Minimum Release Versions

Software Release 9.3.53 Files

New Features in Releases 9.3.40 to 9.3.53

New Features in Release 9.3.40

Virtual Trunk Bandwidth Oversubscription

Feeder VCI Restriction Removal

Display Connection Counts

VC Merge

NTM Subrate Trunk Encryptor Synchronization

UXM Trunk and Line Loopback

Single-Ended FCES and Policing

Line and Port Alarm Masking

Trunk VC Shaping

Special Installation/Upgrade Requirements

General Upgrade Procedure

Revision Interoperability Supported

Version Compatibility Notes

Control Card Requirements

Control Card Boot Firmware Requirements

Control Card Compatibility Requirements

Control Card Physical Card Upgrade Procedure

Obsoleted Hardware and Firmware

Notes and Cautions

Limitations for Release 9.3.40

Compatibility Matrix

BPX 8600 Firmware Compatibility

IGX 8400 Firmware Compatibility

Software Compatibility Matrix

MGX 8220 Hardware Compatibility

BPX 8600 Hardware Compatibility

IGX 8400 Hardware Compatibility

Anomalies in Release 9.3.53

Fixed Anomalies in Release 9.3.53

Known Anomalies in Release 9.3.53

Anomaly Status Changes in Release 9.3.53

Anomalies in Release 9.3.51

Anomalies Fixed in Release 9.3.51

Anomaly Status Changes in Release 9.3.51

Anomalies Fixed and Changed Status in Release 9.3.47

Anomalies Fixed in Release 9.3.47

Anomaly Status Changes in Release 9.3.47

Anomalies Fixed and Changed Status in Release 9.3.45

Anomalies Fixed in Release 9.3.45

Anomaly Status Changes in Release 9.3.45

Anomalies Fixed in Release 9.3.42

Anomalies Fixed in Release 9.3.40

Anomaly Status Changes from Previous Releases

Additional Deliverables

SNMP MIB

Default Values

Cisco BPX 8600 Nodes

Cisco IGX 8400 Nodes

Appendix A—BXM Firmware MFZ Release Notes

About the Firmware MFZ

Front Cards

Front Card for APS Compatibility

Back Cards

New Features Supported in BXM Firmware MFZ

New Features Supported in BXM Firmware MFY

New Features Supported in BXM Firmware MFX

New Features Supported in BXM Firmware MFW

New Features Supported in BXM Firmware MFV

New Features Supported in BXM Firmware MFU

New Features Supported in BXM Firmware MFT

New Features Supported in BXM Firmware MFR

New Features Supported in BXM Firmware MFP

New Features Supported in BXM Firmware MFN

New Features Supported in BXM Firmware MFM

New Features Supported in BXM Firmware MFK

New Features Supported in BXM Firmware MFJ

New Features Supported in BXM Firmware MFH

New Features Supported in BXM Firmware MFF

New Features Supported in BXM Firmware MFE

New Features Supported in BXM Firmware MFD

New Features Supported in BXM Firmware MFC

New Features Supported in BXM Firmware MFB

New Features Supported in BXM Firmware MFA

New Features Supported in BXM Firmware MEC

New Features Supported in BXM Firmware MEB

New Features Supported in BXM Firmware MEA

New Features Supported in BXM Firmware MDA

Special Installation/Upgrade Requirements

Features Obsoleted

Notes, Cautions, and Clarifications

Anomalies Fixed in MFZ

Known Anomalies in MFY

Anomalies Fixed in MFY

Known Anomalies in MFX

Anomalies Fixed in MFX

Anomalies Fixed in MFW

Anomalies Fixed in MFV

Anomalies Fixed in MFU

Anomaly Fixed in MFT

Anomalies Fixed in MFR

Anomalies Fixed in MFP

Anomalies Fixed in MFN

Anomalies Fixed in MFM

Anomalies Fixed in MFL

Anomalies Fixed in MFK

Anomalies Fixed in MFJ

Anomalies Fixed in MFH

Anomalies Fixed in MFF

Anomalies Fixed in MFE

Anomalies Fixed in MFD

Anomalies Fixed in MFC

Anomalies Fixed in MFB

Anomalies Fixed in MFA

Anomalies Fixed in MEC

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

Anomalies Fixed in MEB

Anomalies Fixed in MEA

Firmware Filenames and Sizes

Appendix B—UXM Model C ACL Firmware Release Notes

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in ACL

Upgrade Instructions

Boot Code Requirements

Unsupported Configurations or Applications

Notes and Cautions

Firmware Filenames and File Sizes

Appendix C—UXM Model B Firmware ABV Release

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in ABV

Upgrade Instructions

Boot Code Requirements

Unsupported Configuration or Applications

Firmware Filenames and Sizes

Notes and Cautions

Appendix D—URM Model B Firmware XBC Release Notes

Introduction

New Features

Obsolete Features

Compatibility

Anomalies Fixed in XBC

Upgrade Instructions

Boot Code Requirements

Unsupported Configurations or Applications

Firmware Filenames and Sizes

Notes and Cautions

Obtaining Documentation

Cisco.com

Product Documentation DVD

Ordering Documentation

Documentation Feedback

Cisco Product Security Overview

Reporting Security Problems in Cisco Products

Obtaining Technical Assistance

Cisco Technical Support & Documentation Website

Submitting a Service Request

Definitions of Service Request Severity

Obtaining Additional Publications and Information


9.3.53 Version Software Release Notes Cisco WAN Switching System Software


Part Number OL-9907-01 Revision A0, March 7, 2006

Table of Contents

About the 9.3.53 Release

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

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

Phased Release Strategy

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

Definitions

The following terms are used for this release:

Generally Available (GA)

Feature is ready for wide deployment with no restrictions. Customers deploying GA features are supported by the Technical Assistance Center (TAC).

First Customer Ship (FCS)

Feature is available for controlled introduction to selected customers. To trial an FCS feature, contact your account representative. Customers selected for controlled introduction receive assistance with the test plan review and special support from the New Product Team (NPT) in addition to the normal Technical Assistance Center (TAC) support.


Minimum Release Versions

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

Table 1 Minimum SWSW Versions 

Product
Feature Name
FCS/GA
Status
Minimum Release

BPX

Virtual Trunk Bandwidth Oversubscription

FCS

9.3.40

BPX

Feeder VCI Restriction Removal

FCS

9.3.40

BPX/IGX

Display Connection Counts

FCS

9.3.40

BPX/IGX

VC Merge

FCS

9.3.40

IGX

NTM Subrate Trunk Encryptor Synchronization

FCS

9.3.40

IGX

UXM Trunk and Line Loopback

FCS

9.3.40

BPX/IGX

Single-Ended FCES and Policing

FCS

9.3.40

BPX/IGX

Line and Port Alarm Masking

FCS

9.3.40

BPX/IGX

Trunk VC Shaping

FCS

9.3.40

IGX

URM BC-2FE Back Card

GA

9.3.30

IGX

URM VSI Support

GA

9.3.30

IGX

URM Remote Router Configuration

GA

9.3.30

IGX

CRC-4 Error Detection

GA

9.3.30

BPX/IGX

AIS OAM Recognition

GA

9.3.30

BPX/IGX

800 Part Number Support

GA

9.3.30

BPX

Automatic Routing Management to PNNI Migration

GA

9.3.30

BPX

Network to Endpoint Connectivity Verification

GA

9.3.30

BPX

Deferred Connection Alarm Generation

GA

9.3.30

BPX

Enhanced NNI - End-to-end OAM across BPX-MGX Networks

GA

9.3.30

BPX

Provisioning of end-to-end AR - PNNI PVCs (XPVC) across BPX - MGX Networks

GA

9.3.30

BPX

LMI/ILMI on Virtual Ports

GA

9.3.30

BPX/IGX

TFTP Configuration Save and Restore

GA

9.3.30

BPX

F4 - F5 Mapping

GA

9.3.30

BPX/IGX

Virtual Trunk Clock Source Synchronization

GA

9.3.30

BPX

60K Channel support for VSI

GA

9.3.30

BPX/IGX

Trunk Incremental Cell Delay Variance (CDV)

GA

9.3.30

BPX/IGX

Concurrent Routing

GA

9.3.30

IGX

URM Router Functionality

GA

9.3.20

BPX

Dynamic Partitioning

GA

9.3.10

BPX/IGX

Qbin Statistics

GA

9.3.10

IGX

ILMI 4.0

GA

9.3.10

BPX/IGX

ILMI/ELMI Neighbor Discovery

GA

9.3.10

IGX

ELMI for UFMs

GA

9.3.10

IGX

VSI/MPLS

GA

9.3.10

BPX

Virtual Ports

GA

9.3.05

BPX

Hitless Connection Density Upgrade for BXM

GA

9.3.00

BPX

Support for 3 VSI Partitions

GA

9.3.00

BPX

VSI MIB Support

GA

9.3.00

BPX/IGX

800 Board-Level Revision Number

GA

9.3.00

BPX/IGX

Priority Bumping

GA

9.3.00

BPX/IGX

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

GA

9.3.00

BPX/IGX

Separate Abort Stack

GA

9.3.00

BPX/IGX

Upgrades Protection

GA

9.3.00

BPX/IGX

Control Traffic Shaping

GA

9.3.00

IGX

2000 VC Bandwidth Parameters

GA

9.3.00

IGX

UXM/UXM-E ATM Forum IMA-Compliant Ports

GA

9.3.00


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

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/index.htm

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/igx8400/index.htm

Software Release 9.3.53 Files

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

Table 2 Release 9.3.53 BPX Files

File Name(s)
File Size

9353B.000-9353B.024

65536

9353B.025

64012

9353B.img

784


Table 3 Release 9.3.53 IGX Files

File Name(s)
File Size

9353G.000-9353G.028

65536

9353G.029

4668

9353G.img

784


New Features in Releases 9.3.40 to 9.3.53

No new features were introduced in releases 9.3.40 to 9.3.53.

New Features in Release 9.3.40

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

Virtual Trunk Bandwidth Oversubscription

Feeder VCI Restriction Removal

Display Connection Counts

VC Merge

NTM Subrate Trunk Encryptor Synchronization

UXM Trunk and Line Loopback

Single-Ended FCES and Policing

Line and Port Alarm Masking

Trunk VC Shaping

Virtual Trunk Bandwidth Oversubscription

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

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

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

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

Functionality

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

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

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

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

Configuration Requirements

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

The following restrictions apply to VT oversubscription:

Minimum service rate is less than or equal to the maximum service rate for each VT.

Sum of the minimum service rates of all VTs on a physical interface is less than or equal to the total bandwidth of that physical interface.

Maximum service rate is less than or equal to the total bandwidth of the physical interface for each VT on that physical interface.

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

AutoRoute Connections

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

VSI Partitions

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

CLI Additions and Modifications

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

cnftrk

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

Example 1 cnftrk Command

node TN    Cisco           BPX 8620  9.3.40    June 15 2001 13:04 GMT 

TRK 10.1.1 Config   E3      [1962  cps]    BXM slot:     10                     
Transmit Rate[Min/Max]:1962/3000           VPC Conns disabled:    --           
Protocol By The Card:  --                  Line framing:          --           
VC Shaping:            No                       coding:           --           
Hdr Type NNI:          No                       recv impedance:   --           
Statistical Reserve:   1000    cps              cable type:       --           
Idle code:             7F hex                         length:     0-225 ft.    
Connection Channels:   256                 Pass sync:             No           
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR   Loop clock:            No           
Restrict CC traffic:   Yes                 HCS Masking:           Yes          
Link type:             Terrestrial         Payload Scramble:      Yes          
Routing Cost:          10                  Frame Scramble:        --           
F4 AIS Detection:      No                  Vtrk Type / VPI:       CBR / 10     
                                           Incremental CDV:       0            
                                           Deroute delay time:    0 seconds    

Last Command: cnftrk 10.1.1
Next Command: 

dsptrk

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

dspcmi

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

Example 2 dspcmi Command

node TN    Cisco           BPX 8620  9.3.40    June 15 2001 13:04 GMT 

qbdata :0x00001F40  qbdatb :0x00001F40  qcbr   :0x00000190  qvbr   :0x00001388
qabr   :0x00002710  qsig   :0x00000280  multicast:0         Ext Fmt:0
Ext2 Fmt:0          bti_e1:0            Card Sync:0         imacomp:0
RAS Loopback:1      RAS Lpbk Enabled:0  Traffic Gen:1       ics   :0
vsi   :3            vsi_mpart:1         Mlvl Stat:1         Stat Lvl:1
VerifyFc:0          SchdChns:16384      IlmiChan:16322      CdRed Chan:16321
pcrmin supp:1       VSI ILMI  :1        VSI NbrDisc :1      VSI SigQBN:1
Virtual Ln:0        Internal Port:0     Ios Router:0        Ios window :0
Vsi Ctrlr:0         Inhibit Trunk:0     Inhibit Yred:0      F4 AIS F4-F5:1
CRC-4 Config:0      cd upgd supp:1      E/ILMI NbrDisc :1   ILMI support :0
ILMI version :0     X-LMI :1            Total LCN  :16320   VC Merge supp: 0
oamping supp: 0     Vtrk ovrsub supp:1

This Command: dspcmi P 10

dspcd

The dspcd command shows whether the card supports VT oversubscription.

Example 3 dspcd Command

node TN    Cisco           BPX 8620  9.3.40   June 15 2001 13:04 GMT 

Detailed Card Display for BXM-E3 in slot 10
Status:          Active
Revision:        JD16             Backcard Installed          
Serial Number:   692539             Type:          LM-BXM
Top Asm Number:  28221802           Revision:      BA
Queue Size:      228300             Serial Number: 650886
Supp:12 Pts, E3, FST, VcShp         Supp: 12 Pts,T3/E3
Supp: VT,ChStLv 1,VSI(Lv 3,ITSM)
Support: LMIv 1,ILMIv 1,NbrDisc,XL
Supp: OAMLp,TrfcGen, Vtrk ovrsub
Supp: pcr < 50cps, F4F5
#Ch:16320,PG[1]:16320
PG[1]:1,2,3,4,5,6,7,8,9,10,11,12,
#Sched_Ch:16384 #Total_Ch:16320
Type: BXME, revision EX


Last Command: dspcd 10


Next Command: 

dsptrkutl

The dsptrkutl command shows whether or not oversubscription is enabled.

Example 4 dsptrkutl Command

node TN    Cisco           BPX 8620  9.3.40   June 15 2001 13:04 GMT 

TRK 10.1.1 Utilization Display     Vtrk Oversubscription Enabled    Snapshot

Elapsed time (seconds)          233.2          Terminated Connection Statistics
Total cells transmitted         199            Voice terminated         0
Overall cell rate (cells/sec)   0              Data terminated          0
Overall utilization             0%             Frame Relay terminated   0
Peak interval utilization       1%             Num voice OffHook        0
Last interval (seconds)         5.0            ATM terminated           3
Interval cells generated        0              Connection   Modem Modem VAD
Interval cell rate (cells/sec)  0              Type   Num   On    V.25  Enabled
Interval utilization            0%             c      0     0     0     0
                                               a      0     0     0     -
Terminated Connections          3              v      0     0     0     0
Via Connections and Groups      0              p/t    0     0     0     -

Last Command: dsptrkutl 10.1.1

Next Command: 

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

MIB Addition

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

Table 4 atmTrunksTable Addition

MIB Object
Description
Values

atmTrkXmitRateMax

Maximum trunk transmission rate in cells per second.

This object can be SET for virtual trunks. The object is read-only for other types of trunks. The value is the same as the atmTrkXmitRate value.

This object can be SET with all other writable objects in this table except:

atmRteTrkAlmEnable

atmRteTrkBdataBTxQlen

atmRteTrkBdataBTxEfcn

atmRteTrkBdataBTxHiClp

atmRteTrkBdataBTxLoClp

Access: read-write

Default: 3000 cps. (equal to atmTrkRcvRate)


Mismatch Capabilities

The following table shows mismatch conditions.

Table 5 Mismatch

Active Card
Replaced by Card
Result

Without VT oversubscription

With or without VT oversubscription

No mismatch

With VT oversubscription disabled

With or without VT oversubscription

No Mismatch

With VT oversubscription enabled

With VT oversubscription

No mismatch

With VT oversubscription enabled

Without VT oversubscription

Mismatch


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

Redundancy

SWSW 9.3.40 uses the following guidelines for Y-cable redundancy (Y-red):

Allow Y-red if only one card supports the feature, and the feature is disabled.

Do not allow Y-red if one card supports the feature, the feature is enabled, and the second card does not support the feature.

Do not enable this feature if Y-red is configured between a card supporting VT bandwidth oversubscription and a card not supporting this feature.

Feeder VCI Restriction Removal

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

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

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

This feature is available on the BPX switch with BXM trunks.

Usage

VCI shift operations perform the following functions:

Shift/no-shift operation is configured using the cnffdr command. The same setting should be chosen at both ends of a connection. When a connection is added, a difference in setting causes a mismatch warning to display.

When the shift option is enabled on a feeder trunk, the VCI value is shifted left by four bits for cells entering the feeder trunk and shifted right by four bits for cells leaving the feeder trunk.

Via nodes get the shift/no-shift configuration from the master and program the trunks accordingly.

If the VCI is less than or equal to 4095 in a VPC, then the connection does not need to be rerouted.

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

This feature also works with local connections.

Configuration

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

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

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

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

All existing connections over this feeder trunk must be manually rerouted for the change to be effective. The shift/no-shift setting should be configured before adding new connections. However, the connection continues to have data continuity if this setting is not configured.

If the feeder at one end is changed to no-shift, then the feeder at other end also should be changed to no-shift.

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

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

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


Note Since the system does not automatically avoid routing over BNI trunks, configure the VPC connections in the network with directed preferred routes over BXM-only paths. If these paths are lost, the connection fails rather than rerouting over a path with a BNI.


CLI Additions and Modifications

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

cnffdr

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

Trunk must be a BXM trunk.

Trunk must be up.

Trunk must be added as a feeder.

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

Syntax:

cnffdr <trunk number> <H|N>

Parameter
Description

<trunk number>

Specifies the slot.port of the feeder trunk.

[H|N]

Enable or disable shift.

H = Shift VCI

N = No-Shift (default)


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

Example 5 cnffdr Command

node TN    Cisco           BPX 8620  9.3.40    June 12 2002 10:09 PST 

Feeder trunk: 1.1    [AAL/5]

Shift:              SHIFT ON HCF

This Command: cnffdr 1.1  


'H'=SHIFT ON HCF,'N'= NO SHIFT, <H>:N

dspfdrcnf

The dspfdrcnf command displays the shift/no-shift setting on feeder trunks.

Syntax:

dspfdrcnf <trunk number>

Parameter
Description

<trunk number>

Specifies the slot.port of the feeder trunk.


The following example shows the dspfdrcnf display screen:

Example 6 dspfdrcnf Command

node TN    Cisco           BPX 8620  9.3.40    June 12 2002 10:13 PST 

Feeder trunk: 1.1    [AAL/5]

Shift:              NO SHIFT

Last Command: dspfdrcnf 1.1

Next Command: 

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

Example 7 dspfdrcnf Command for BNI Feeders

node TN    Cisco           BPX 8620  9.3.40    June 11 2002 17:00 PST 

Feeder trunk: 3.2    [AXIS]

Shift:              -


Last Command: dspfdrcnf 3.2

Next Command: 

MIB Addition

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

Table 6 atmTrkTable Addition

MIB Object
Description
Values

atmTrkHcfShift

Value to indicate whether VCI shift is enabled on the trunk.

For no-shift of VCI the value of the SET operation should be disable(2) and for shift the value should be enable(1). The default value is no-shift for BXM feeder trunks.

The object is applicable only for BXM feeder trunks. For ATM ports on other cards this object is not applicable, and the value -1 is returned.

This object is not applicable for routing trunks.

If a SET operation is tried without giving a value, the default value is set for BXM feeder trunks. The request is ignored for routing trunks.

If a SET operation with a given value is tried on a routing trunk, an error is returned.

Access: read-write

1 = enable

2 = disable


SNMP Error Messages

The following error messages are generated under the specified conditions:

Error code -1 (There is no such variable name in this MIB) is returned when SNMP GET or SET is tried on an invalid trunk or on a trunk that is not up.

Error code -1 is returned when SNMP GET is tried on a trunk which is not a feeder trunk.

Error code -2 (A general failure occurred) is returned when SNMP SET is tried on a trunk which is not a feeder trunk.

Redundancy

This section contains redundancy requirements of this feature.

Controller Card Redundancy

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

Y-redundancy and APS

The shift/no-shift configuration is available on redundant cards.

Display Connection Counts

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

Number of connection endpoints terminated on the cards and lines.

Number of connection endpoints terminating on ports. The display includes the endpoint counts of the CBR, VBR, ABR, UBR, and Frame Relay connection types that terminate on each active port. The number of VPC and VCC connection endpoints on each port are also displayed.

Number of connections passing over trunks for the node.

CLI Addition

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

dspconcnts

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

Syntax:

dspconcnts [c|p|t|l|h] [h(elp)]

Parameter
Description

c

(Optional) Displays the number of connection endpoints terminating on each card.

p

(Optional) Lists all active ports on the node. For each active port, the number of CBR, VBR, UBR, ABR, and Frame Relay connection endpoints and
terminating VPC and VCC connection endpoints are also listed.

t

(Optional) Displays the number of connections passing over each trunk on the node.

l

(Optional) Displays the number of connection endpoints terminating on each line on the node.

h

(Optional) Displays a help screen.

none

Displays the number of connections mastered to or from this node and the number of via connections passing over the node when no option is specified.


Example 8 shows the active ports with the number of connection endpoints.

Example 8 dspconcnts Command for Ports

node TN    Cisco           BPX 8620  9.3.40    June 13 2002 08:34 GMT 


Port       #atf   #vbr   #cbr   #ubr   #abr  other   #vpc   #vcc  total 
1.3.1        0      0      0      0      0      0      0      0      0
1.3.5      158      0      0      0     10      0      0    168    168
6.3          0      0     37      0      0      0      0     37     37
14.1         0      0      2      0      0      0      0      2      2


Last Command: dspconcnts p

Example 9 shows the number of connection endpoints terminating on each card.

Example 9 dspconcnts Command for Cards

node TN    Cisco           IGX 8430  9.3.40    June 13 2002 08:40 GMT 
Slot  Type   #ConEndPts  Slot  Type   #ConEndPts  Slot  Type   #ConEndPts
  3  UXM        291       13  LDM         21       26  CVM          1
  4  FRM         32       17  Empty        -       27  UXM          0
  5  NTM          -       18  FRM         37       28               0
  6  NTM          -       19  CVM          0       29               0
  7  CVM          0       20  CVM          0       30  Empty        -
  8  Empty        -       21  Empty        -       31  Empty        -
  9  Empty        -       22  UXM        179       32  ALM          0
 10  HDM          8       23  Empty        -
 11  HDM          0       24  Empty        -
 12  UXM          0       25  FRM          0

Last Command:dspconcnts c

VC Merge

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

http://www.cisco.com/univercd/cc/td/doc/product/wanbu/bpx8600/9_3_3/iandc/index.htm

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

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

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

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

The support of VC merge on a card can be verified using the following commands:

dspcd

dspcdparm

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

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

Availability of Contiguous LCNs

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

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

Redundancy

The VC merge feature is supported on the Y-cabled UXM-E pair.

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

Table 7 Mismatch Scenarios

Scenario
Behavior
Logical Card State

Y-red not configured. Replace N (primary) with S (secondary).

OK

S

Y-red not configured. Replace S with N.

If feature is not in use, no mismatch.

If feature is in use, feature mismatch. Feature usage must be removed and card reset to clear mismatch.

N

addyred: N primary, S secondary

No mismatch - addyred is allowed.

N

addyred: S Primary, N secondary

Blocked if feature is in use.

Allowed if feature is not in use. No mismatch.

S/N


CLI Additions and Modifications

This section contains the commands that have been modified to support VC merge.

cnfcdparm

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

Syntax:

cnfcdparm <slot #> <param # (2) > <E/D>

Parameter
Description

slot #

Slot number.

param #2

Parameter(2) that changes the VC Merge State.

E/D

Value to configure the VC merge.

E = enable

D = disable


Example 10 cnfcdparm Command

node TRM   Cisco           IGX 8420  9.3.4Q    May  23 2002
11:41 PST

                            Card Parameters

1  Channel Statistics Level
.........................................     1
2  VC Merge State          
.........................................     D



Last Command:cnfcdparm 10 2 E

dspcd

The dspcd command supports the VC merge capability display.

Syntax:

dspcd <slot #>

Example 11 shows the VC merge capability for the UXM card in slot 10.

Example 11 dspcd Command

node TRM   Cisco           IGX 8420  9.3.4Q    May  23 2002
11:27 PST

Detailed Card Display for UXM in slot 10

Status:         Standby               (Front Card is UXME)
Revision:       CA27                  Front Card Supports:
Serial Number:  290617                 Vtrunks, OAMLpbk & TrfcGen, ILMI
ver 1,
Top Asm Number: 28274601               Neighbor Discovery, SIW, CGW,
CellFwd,
Backplane Installed                     Hot Standby, Trfc Shaping, IMA,
Backcard Installed                      ChnStatLvl 1, NumChans = 8000,
  Type:         E1-IMA                 NumRCMP = 16382, VSI ver 2, VSI
Ctrlr,
  Revision:     AA                     PCR >= 6 cps, F4 AIS
Recognition,
  Serial Number:248402                 CRC-4 Config, VC Merge, Cnf ILMI
chg/trap 
Top Asm Number:28241202
  Ports:        8
  Interface:    BNC


Last Command:dspcd 10

NTM Subrate Trunk Encryptor Synchronization

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

Functions

This feature provides the following functions:

Enables and disables the toggling of the NTMs DTR lead through the cnftrk command.

Configures ON and OFF durations of the NTMs DTR lead through the cnftrk command. The ON and OFF values are in the range of 1 to 128 seconds.

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

Clock loss

Signal loss

Packet loss

Yellow packet received

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

CLI Modifications

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

cnftrk

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

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

dsptrk

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

Example 12 dsptrk Command

node TRM Cisco IGX 8430 9.3.4K May 20 2002 GMT 17:43 G+05
TRK 26 Config SR/30 [10000 pps] NTM slot:26
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
Incremental CDV: 0
Deroute delay time: 0 seconds
DTR toggle on alarm: No
DTR secs ON: 29
DTR secs OFF: 1

Last Command: dsptrk 26
Next Command:

cnftrkict

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

Example 13 cnftrkict Command

node TRM   Cisco         IGX 8430  9.3.4K May  20 2002 GMT 17:40 G+05 
Packet Line:   26 
Interface:     X.21   DTE 

            Interface Control Template for Packet Line 

 Lead    Output Value                   Lead    Output Value 
 DTR (H) ON                             RTS (C) OFF 
  

This Command:cnftrkict 26 DTR 

Warning! DTR lead settings will be overridden by cnftrk during Trk alarms 
Enter signal source (on, off, or local): 

MIB Additions

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

Table 8 fpRteTrkTable Additions

MIB Object
Description
Values

fpRteTrkToggleEnable

Value to enable or disable DTR lead toggling.

This object is applicable only to NTM cards with subrate backcards. A SET on any other type of card is ignored.

A GET on any other type of card returns (-1).

Access: read-write

1 = Yes

2 = No (default)

fpRteTrkDtrOn

The ON time in seconds for DTR lead during toggling.

This object is applicable only to NTM cards with subrate backcards.

A SET on any other type of card is ignored. A GET on any other card returns (-1).

Access: read-write

Range: 1-128

Default: 29

fpRteTrkDtrOff

The OFF time in seconds for DTR lead during toggling.

This object is applicable only to NTM cards with subrate backcards.

A SET on any other type of card is ignored. A GET on any other card returns (-1).

Access: read-write

Range: 1-128

Default: 1


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

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

UXM Trunk and Line Loopback

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


Note This feature already exists on the BPX.


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

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

Local Loopback (addlnloclp)

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

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

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

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

Local Remote loopback (addlnlocrmtlp)

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

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

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

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

Delete Local/Local Remote loopback (dellnlp)

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

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

dsptrks

dsplns

dspphyslns

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

Table 9 Loopback Behavior 

   
Local Node
Remote Node
   
addlnloclp
addlnlocrmtlp
addlnloclp
addlnlocrmtlp

Trunks (Physical and Virtual)

Single Node

LOS is not cleared

LOS is cleared

Not applicable

Not applicable

Trunks (Physical and Virtual)

Network

dsptrks on local node shows Comm Failure. No LOS alarms are present.

dsptrks on local node shows Looped Back. No alarms are present.

dsptrks shows Looped Back status.

dsptrks shows Comm-Fail.

Lines/Ports

Single Node not connected to CPE

1. Port state remains failed

2. LOS is not cleared.

1. Port State changes to active

2. LOS is cleared

Not applicable

Not applicable

Lines/Ports

Connected to CPE

LOS remains clear

1. Port state remains active

2. LOS remains clear

Not applicable

Not applicable

IMA trunks

Same as physical trunks

Same as physical trunks

Same as physical trunks

Same as physical trunks

IMA ports/lines

Same as ports

Same as ports

Same as ports

Same as ports

Feeder trunks

Network

1. dsptrks shows clear-Ok.

2. Node goes into Major alarm and dspnode shows remote node is unreachable.

3. dsplog shows comm-fail with remote node.

1. dsptrks shows clear-Ok.

2. Node goes into Major alarm and dspnode shows remote node is unreachable.

3. dsplog shows comm-fail with remote node.

1. dsptrks shows clear-Ok.

2. Node goes into Major alarm and dspnode shows remote node is unreachable.

3. dsplog shows comm-fail with remote node.

1. dsptrks shows LOS.

2. Node goes into Major alarm and dspnode shows remote node is unreachable.

3. dsplog shows comm-fail with remote node.


Limitations

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

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

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

SWSW does not support these loopback commands on the SNMP interface.

CLI Additions and Modifications

addlnloclp

The command addlnloclp performs the following operations:

Programs the target UXM to put the physical interface into line local loopback.

Logs a system event to indicate that the physical loopback is applied on the physical interface.

Displays the following summary screens for lines or trunks:

For the UXM physical interface that has been configured as trunk(s), the dsptrks output screen displays the proper loopback indicator on the affected trunk(s).

For lines, the dsplns output screen displays the proper loopback indicator on the affected line.

For IMA lines/trunks the dspphyslns output screen is displayed with the proper loopback indicator on the affected link(s).

Syntax:

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

Parameter
Description

slot.port

Format for normal UXM physical interface.

slot.port [-port, port]

Format for IMA interfaces.

slot.port.vport

Format for virtual trunks.

slot.port-port.vport

Format for IMA virtual trunks.


addlnlocrmtlp

The command addlnlocrmtlp performs the following operations:

Programs the target UXM to put the physical interface into line local remote loopback.

Logs a system event to indicate that the physical loopback is applied on the physical interface.

Displays the following summary screens for lines or trunks:

For the UXM physical interface that has been configured for trunk(s), the dsptrks output screen displays the proper loopback indicator on the affected trunk(s).

For lines, the dsplns output screen displays the proper loopback indicator on the affected line.

For IMA lines/trunks the dspphyslns output screen displays the proper loopback indicator on the affected link(s).

Syntax:

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

Parameter
Description

slot.port

Format for normal UXM physical interface.

slot.port [-port, port]

Format for IMA interfaces.

slot.port.vport

Format for virtual trunks.

slot.port-port.vport

Format for IMA virtual trunks.


dellnlp

The command dellnlp performs the following operations:

Programs the target UXM to remove the physical loopback on the UXM physical interface.

Logs a system event to indicate that the physical loopback is removed on the physical interface.

Displays the following summary screens for lines or trunks:

For the UXM physical interface that has been configured for trunk(s), the dsptrks output screen displays the loopback indicator removed on the affected trunk(s).

For lines the dsplns output screen displays the loopback indicator removed on the affected line.

For IMA lines/trunks the dspphyslns output screen displays the loopback indicator on the affected link(s).

Syntax:

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

Parameter
Description

slot.port

Format for normal UXM physical interface.

slot.port [-port, port]

Format for IMA interfaces.

slot.port.vport

Format for virtual trunks.

slot.port-port.vport

Format for IMA virtual trunks.


dsptrks

The dsptrks command includes the following modifications:

UXM interface in local loopback state displays ] as the line local loopback indicator.

UXM interface in local remote loopback state displays [ as the line local remote loopback indicator.

Example 14 dsptrk Command

node1 TN    Cisco           IGX 8430  9.3.40    June 18 2002 15:39 GMT 

TRK        Type   Current Line Alarm Status                  Other End
 4.1      ]T1/24  Major - Looped Back	sw227/3.1


Last Command: dsptrks

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

dsplns

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

UXM interface in local loopback state displays ] as the line local loopback indicator.

UXM interface in local remote loopback state displays [ as the line local remote loopback indicator.

dspphyslns

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

Example 15 dspphyslns Command

node1 TN    Cisco           IGX 8430  9.3.40    June 18 2002 15:40 GMT 

PHYSLN     Type   Current Line Alarm Status                  Trk/Line
 4.1      ]T1/24  Major - Out of Frm (RED)                    4.1-T
 4.5       T1/24  Major - Loss of Sig (RED)                   4.5(4)-T
 4.6       T1/24  Major - Loss of Sig (RED)                   4.5(4)-T
 4.7       T1/24  Major - Loss of Sig (RED)                   4.5(4)-T
 4.8       T1/24  Major - Loss of Sig (RED)                   4.5(4)-T
13.1      ]OC3    Major - Loss of Sig (RED)                  13.1-T
16.1       T3/636 Major - Loss of Sig (RED)                  16.1-T


Last Command: dspphyslns

Redundancy

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

Single-Ended FCES and Policing

Functions

Single-ended FCES and policing provide the following functions:

Allows FCES to be enabled or disabled independently on two endpoints of a connection.

Allows policing to be enabled or disabled independently on two endpoints of a connection.

Supports the configuration from CWM, CLI, and SNMP.

Requirements

These features require the BXM-E and UXM-E cards.

FCES

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

Connections with type ABRSTD, ABRFST, or ATFST (between two ATM endpoints) are added using addcon if both endpoints support FCES (VSVD needs to be enabled for ABRSTD connection).

The above connections are configured using the cnfcon CLI command.

ATM classes are configured using cnfcls or cnfatmcls commands.

The dspcon is used to display the above connections,

The parameter for FCES takes one of the following values:

D/D (or D). FCES is disabled at both endpoints.

E/E (or E). FCES is enabled at both endpoints.

E/D. FCES is enabled at the local endpoint only.

D/E. FCES is enabled at the remote endpoint only.

The default value for FCES is disable.

The following example shows the CLI prompt.

FCES [Disable/Disable]:

In the following cases FCES is specified for only one end of a connection:

A connection with type ATFST, ATFXFST, or ATFTFST is added between ATM and FR endpoints. Enabling or disabling FCES is applicable only to the ATM endpoint. FCES is ignored at the FR endpoint.

If one endpoint is acting as a feeder trunk, FCES is not applicable and displays a [-].

For a local connection which uses one channel, only one endpoint for this connection exists.

In these cases, the parameter for FCES is in the following format:

D. FCES is disabled at the ATM endpoint.

E. FCES is enabled at the ATM endpoint.

The CLI prompt in these cases is

FCES [Disable/-]: or FCES [-/Disable]: or
FCES [Disable]: (for onelcn dax connection)

MIB

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

Policing

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

[1-5]/[1-5] or [1-5]

If the endpoint is a feeder trunk, the policing is shown as

[1-5/- or -/[1-5]

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

D/D (or D when inputting). CLP tagging is disabled at both endpoints.

E/E (or E when inputting). CLP tagging is enabled at both endpoints.

E/D. CLP Tagging is enabled at the local endpoint only.

D/E. CLP Tagging is enabled at the remote endpoint only.

If the endpoint is a feeder trunk, the CLP tagging is shown as

D/-, E/-, -/D or -/E

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

Table 10 Policing Types 

Type
Cells Tested In First Bucket
First Bucket Noncompliance Result
Cells Tested In Second Bucket
Second Bucket Noncompliance Result
Supported Connection Types
Default

1

All

Discard

CLP = 0 or 1

Discard

VBR, ABR

None

2

All

Discard

CLP = 0 only

Discard

VBR, ABR

None

3

All

Discard

CLP = 0 only

Tag with CLP

VBR, ABR

VBR, ABRSTD with VSVD, ABRFST, ATFST, ATFTFST, ATFXFST

4

All

Discard

None

-

CBR, VBR, ABR

CBR, ABRSTD without VSVD

5

None

-

None

-

CBR, VBR, ABR

None



Note Single-ended policing for VBR connections is not supported.


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

The addcon command allows users to configure policing on the two endpoints differently.

The switch MIB definition for remote endpoint policing allows independent SNMP SET operations on the objects of both endpoints.

Compatibility

These features have the following compatibility capabilities:

Provisioning from existing CWM is supported. If the request has only one endpoint value, copy this value to the other end to keep the new feature compatible with the existing CWM. Do not use the default for the other end.

Because the robust message payload definition has not changed, these features function with the CWM 10.5.

MIB

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

Redundancy

Network Interoperability

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

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

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

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

If the switch is upgraded before CWM, the following results occur:

The format of robust message sent from switch is not changed. Only the values of the connection object are changed.

The FCES and policing values cannot be configured differently on CWM, and the display on the CWM is incorrect.

If CWM is upgraded before the switch, the following results occur:

CWM blocks configuring two values differently from the GUI if the switch does not support this feature.

If mixed revisions exist in the network, configuring two values differently is supported if the master node is an upgraded node.

Line and Port Alarm Masking

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

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

This feature is supported in both IGX and BPX platforms.

Functions

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

The cnflnalm and cnfportalm commands mask out the line and port alarm on the specified line or port. However, if any connections exist on those lines or ports, the connections on the affected line or port still fail and cause the node to be in MAJOR alarm. The line and port alarms are enabled by default.

The Port Alarms and Line Alarms entries in the dspalms screen are modified to reflect any active and disabled port alarms.

The existing integrated line alarm related command, cnflnalm, is renamed to cnfintalm to reflect the integrated alarm configuration. The display command dsplnalmcnf is renamed to dspintalmcnf.

Line Alarms

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

Line alarm masking is supported on the following cards:

IGX

FRM-E

UFM-C

CVM

UVM

UXM

BPX

BXM

ASI

BNI

Port Alarms

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

Port alarm masking is supported on the following cards:

IGX

FRM-D

FRM-E

UFM-C

UFM-U

CVM

UVM

UXM

URM

BPX

BXM

ASI

BNI

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

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

MIB Additions

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

Table 11 MIB Additions

MIB Table
MIB Object
Description
Values

frLport

frLportPortAlmEnable

Value to enable or disable a port alarm.

Access: read-write

1 = enable

2 = disable

atmPort

atmPortAlmEnable

Value to enable or disable a port alarm.

Access: read-write

1 = enable

2 = disable

ds1Line

ds1LineAlmEnable

Value to enable or disable a line alarm.

Access: read-write

1 = enable

2 = disable

ds3Line

ds3LineAlmEnable

Value to enable or disable a line alarm.

Access: read-write

1 = enable

2 = disable

sonetIf

sonetIfLineAlmEnable

Value to enable or disable a line alarm.

Access: read-write

1 = enable

2 = disable


CLI Additions and Modifications

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

cnfintalm

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

Syntax:

No change

cnflnalm

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

Syntax:

cnflnalm <line #> <E/D>

Parameter
Description

line #

Line number.

E/D

Value to configure the line alarm.

E = enable

D = disable


Example 16 cnflnalm Command

node TRM   Cisco           IGX 8420  9.3.40    May  23 2002
11:44 PST

Line       Type   Current Line Alarm Status
 4         E1/30  Major - Loss of Sig (RED)
10.1m      E1/30  Major - Loss of Sig 




Last Command:cnflnalm 10.1 d

cnfportalm

The cnfportalm command configures the port alarm.

Syntax:

cnfportalm <port id> <E/D>

Parameter
Description

port id

Port number.

E/D

Value to configure the port alarm.

E = enable

D = disable


Example 17 cnfportalm Command

node TRM   Cisco           IGX 8420  9.3.40    May  23 2002
11:45 PST

 Port States
Port     ID   State
13.1m         FAILED




Last Command:cnfportalm 13.1 d

dspalms

The dspalms command indicates any disabled port alarms.

Syntax:

dspalms

Example 18 dspalms Command

node TRM   Cisco           IGX 8420  9.3.40 	May  29 2001 17:26 GMT 

Alarm summary   (Configured alarm slots: None)
Connections Failed:       None
TRK Alarms:               None
Circuit Line Alarms:      2 Majors 1 Disabled
Port Alarms							2 Minor		1 Disabled
Physical Line Alarms:     None
Cards Failed:             None
Missing Cards:            None
Remote Node Alarms:       5 Majors

Interface Shelf Alarms:   None



FastPAD/Access Dev Alms:  None


Last Command: dspalms

dspintalmcnf

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

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

Syntax:

No change

Trunk VC Shaping

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

Compatibility

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

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

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

Limitations

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

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

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

Functionality

The feature provides the following functions:

Enables PCR-shaping on BXM trunks, virtual trunks, and feeder trunks on a per-QoS basis.

Enables weighted fair queuing (WFQ) on BXM trunks, virtual trunks, and feeder trunks on a per-QoS basis.

Enables VC shaping (WFQ and PCR shaping) on UXM trunks, virtual trunks, and feeder trunks on a per-QoS basis.

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

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

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

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

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

D = Disabled (default)

E = Both WFQ and PCR-shaping

W = WFQ only

On the IGX the options are

E = Both WFQ and PCR-shaping

D = Disabled

CLI Modifications and Additions

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

cnftrk

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

cnftrkq

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


Note The cnftrkq command is a new command applicable only to BXM cards.


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

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

The following example shows the cnftrkq command display.

Example 19 cnftrkq Command

node TRM   Cisco           BPX 8620  9.3.40 June 13 2001 16:11 GMT 

  VC Shaping parameters for Trunk 4.3:

	  VC shaping for Non-TS       : WFQ-only
  VC shaping for rt-VBR       : WFQ-only
  VC shaping for BData A      : PCR+WFQ
  VC shaping for TS           : PCR+WFQ
  VC shaping for BData B      : Disabled
  VC shaping for CBR          : WFQ-only
  VC shaping for ABR/UBR      : PCR+WFQ
  VC shaping for nrt-VBR      : Disabled


This Command: cnftrkq 4.3  

Enable VC shaping for BdataA (e-pcr+wfq, d-disable, w-wfq-only) [e]: 

dsptrkq

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


Note The dsptrkq command is a new command applicable only to BXM cards.


The following example shows the dsptrkq display.

Example 20 dsptrkq Command

node TRM   Cisco           BPX 8620  9.3.40 June 13 2001 16:11 GMT 

  VC Shaping parameters for Trunk 4.3:

	  VC shaping for Non-TS       : WFQ-only
  VC shaping for High Pri     : PCR+WFQ
  VC shaping for rt-VBR       : WFQ-only
  VC shaping for BData A      : PCR+WFQ
  VC shaping for TS           : PCR+WFQ
  VC shaping for BData B      : Disabled
  VC shaping for CBR          : WFQ-only
  VC shaping for ABR/UBR      : PCR+WFQ
  VC shaping for nrt-VBR      : Disabled

This Command: dsptrkq 4.3 

dspcmi

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

The display screen is shown in the following example.

Example 21 dspcmi Command

node TRM   Cisco           IGX 8420  9.3.3M    July 18 2001 18:02 GMT 

qbdata :0x00000000  qbdatb :0x00000000  qcbr   :0x00000000  qvbr   :0x00000000
qabr   :0x00000000  qsig   :0x00000000  multicast:0         Ext Fmt:0
Ext2 Fmt:0          bti_e1:0            Card Sync:0         imacomp:0
RAS Loopback:0      RAS Lpbk Enabled:0  Traffic Gen:0       ics   :0
vsi   :0            vsi_mpart:0         Mlvl Stat:0         Stat Lvl:0
VerifyFc:0          SchdChns:0          IlmiChan:0          CdRed Chan:1001
pcrmin supp:0       VSI ILMI  :0        VSI NbrDisc :0      VSI SigQBN:0
Virtual Ln:0        Internal Port:0     Ios Router:0        Ios window :0
Vsi Ctrlr:0         Inhibit Trunk:0     Inhibit Yred:0      F4 AIS F4-F5:0
CRC-4 Config:0      E/ILMI NbrDisc :0   ILMI support :0     ILMI version :0
LCN Resync:0        Rmt Rtr Cnfg: 0     Trk VC Shap: 1


Last Command: dspcmi p 0


Next Command: 

dspcd

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

Example 22 dspcd Command

node TRM   Cisco           BPX 8620  9.3.40 July 30 2001 15:58 GMT 

Detailed Card Display for BXM-E3 in slot 5
Status:          Active
Revision:        FHM              Backcard Installed          
Serial Number:   634399             Type:          LM-BXM
Top Asm Number:  28221802           Revision:      BS
Queue Size:      131000             Serial Number: 9155
Supp:8 Pts, E3, FST, VcShp          Top Asm Number: 8001234567
Supp: VT,ChStLv 1,VSI(Lv 3,ITSM)    Supp: 8 Pts,T3/E3
Support: LMIv 1,ILMIv 1,NbrDisc,XL
Supp: OAMLp,TrfcGen
Supp: pcr < 50cps,TrkVcShp
#Ch:16320,PG[1]:16320
PG[1]:1,2,3,4,5,6,7,8,
#Sched_Ch:16384 #Total_Ch:16320

Last Command: dspcd 5


Next Command: 

Redundancy

MIB Additions

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

Table 12 describes the new objects that are applicable only on BXM cards.

Table 12 atmTrunks Additions 

MIB Object
Description
Values

atmTrkNonTSVcShaping

Value to indicate whether the trunk should do VC shaping on the non-time stamped (NonTS) Qbin.

This object is valid only for routing trunks. An error is returned for a SET request on feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

atmTrkVoVcShaping

Value to indicate whether the trunk should do VC shaping on the rt-VBR/Voice Qbin.

This object is valid for routing and feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

atmTrkBdataAVcShaping

Value to indicate whether the trunk should do VC shaping on the Bursty data A Qbin.

This object is valid only for routing trunks. An error is returned for a SET request on feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

3 = wfq-pcr

atmTrkTsVcShaping

Value to indicate whether the trunk should do VC shaping on the time stamped (TS) Qbin.

This object is valid only for routing trunks. An error is returned for a SET request on feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

3 = wfq-pcr

atmTrkBdataBVcShaping

Value to indicate whether the trunk should do VC shaping on the Bursty Data B Qbin.

This object is valid only for routing trunks. An error is returned for a SET request on feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

3 = wfq-pcr

atmTrkCbrVcShaping

Value to indicate whether the trunk should do VC shaping on the CBR Qbin.

This object is valid for routing and feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

atmTrkVbrVcShaping

Value to indicate whether the trunk should do VC shaping on the nrt-VBR Qbin.

This object is valid for routing and feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

3 = wfq-pcr

atmTrkAbrVcShaping

Value to indicate whether the trunk should do VC shaping on the ABR/UBR Qbin.

This object is valid for routing and feeder trunks.

If the card does not support trunk VC shaping, the configuration is accepted but not enabled.

This object can only be set with other per Qbin trunk VC shaping objects.

Access: read-write

1 = disabled

2 = wfq-only

3 = wfq-pcr


Special Installation/Upgrade Requirements

This section contains the installation procedures and upgrade requirements.

General Upgrade Procedure


Note Consult a Support Representative before performing any software upgrade.


The earliest release supported for a graceful upgrade is 9.2.23.

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

Procedure for Upgrading BXM cards to the 9.3 Firmware Release

See Appendix A for instructions on upgrading the BXM firmware.

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

Procedure for Upgrading UXM cards to the 9.3 Firmware Release


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


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


Step 1 Execute a graceful upgrade to Release 9.3.30.

Step 2 Upgrade the UXM boot code to boot 8.

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

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



Warning If these procedures are not followed, the card might enter a state from which it can NOT be recovered. See Appendix B for more information about loading the new firmware.


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


Step 1 Execute a graceful upgrade to Release 9.3.30.

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


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

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

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

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

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

Revision Interoperability Supported

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


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


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

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

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

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

URM Remote Router Configuration

TFTP Configuration Save and Restore

Concurrent Routing


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


Version Compatibility Notes

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

This release supports:

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

Any MGX 8220 Release 4.1 and 5.0

Cisco WAN Manager (Cisco StrataView Plus) version 10.5.10 and later

UXM firmware

For MPLS VC merge and trunk loopback features, ACJ or later

For MPLS/VSI feature, UXM model ACB or later

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

BXM firmware

Model MFN or later

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

UFM firmware for ELMI-based topology discovery feature

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

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

URM Model A XAA, or later

URM Model B XBA or later

MGX 8850 version 1.1.40

SES version 1.1.60

IOS version 12.2 (8)T4

LSC IOS Version 12.2(8)T4 for VC merge


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


Control Card Requirements

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

Control Card Boot Firmware Requirements

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

BCC Type
Firmware

BCC-3-64

H.D.M

BCC-4V

H.H.M

BCC-4V/B

H.H.M


NPM Type
Firmware

NPM-32

R.B.S

NPM-64

R.C.S

NPM-32B

R.E.S

NPM-64B

R.F.S


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


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

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

NPM(2) is now active.

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

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

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

NPM(1) is now active.

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


The latest version of the NPM boot code (RxT) incorporates the fixes for the following defects:

CSCdx37714—After runrev IGX hangs when performing a non-graceful upgrade.

CSCec35229— Auto re-initialization (reset) of boot upon reconfiguration of LAN IP address.

Table 13 summarizes the boot code requirements for the various NPM hardware.

Table 13 NPM Boot Code Requirements 

NPM Type
Firmware

NPM-32

R.B.T

NPM-64

R.C.T

NPM-32B

R.E.T

NPM-64B

R.F.T


Control Card Compatibility Requirements

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

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

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

Control Card Physical Card Upgrade Procedure

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


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

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


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


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

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

Step 5 Verify that the network is stable.

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

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

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

The CC physical upgrade is now complete.

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


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

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

16 Bit Word
Byte # (hex)
Contents

0

0,1

Hardware revision

1

2,3

Backplane Type (usually 0x65=101 decimal)

2

4,5

Backplane version (0x0000:old 0x0001:new)

3

6,7

Backplane serial number in ASCII - MSB

4

8,9

Backplane serial number in ASCII - MSB

5

A,B

Backplane serial number in LSB

6

C,D

Board FAB number, in ASCII - MSB

7

E,F

Board FAB number, in ASCII - LSB

8

10,11

Board FAB number, in ASCII - LSB

9

12,13

Board FAB number, in ASCII - LSB

A

14,15

Board FAB number, in ASCII - LSB

B

16,17

Board FAB number, in LSB

C

18,19

Unused

D

1A,1B

Unused

E

1C,1D

Unused

F

1E,1F

Checksum bytes - NOT SUPPORTED


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

Obsoleted Hardware and Firmware

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

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

FTM

BTM

ALM/A

ALM/B

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

Adaptive Voice feature is not supported in IGX SWSW Release 9.3.

Notes and Cautions

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

Cannot be 0.

Must be a multiple of the polling interval.

Must be a factor of the bucket interval.

Can be the same as the bucket interval.

Limitations for Release 9.3.40

None.

Compatibility Matrix

This section contains compatibility information for Release 9.3.53.

BPX 8600 Firmware Compatibility

Table 14 lists the Cisco BPX firmware.

Table 14 Cisco BPX Firmware Matrix 

PCB Description
dspcds Name
Card Name in FW Image
Model
Latest F/W
Min F/W

BCC-3-64 boot

BCC-3

BCC

D

HDM

HDM

BCC4 boot

BCC-4

BCC

E

HEM

HEM

BCC4-128 boot

BCC-4

BCC

H

HHM

HHM

ASI 2T3/2E3

ASI-T3

ASI

B

n/s

n/s

ASI 2T3/2E3

ASI-E3

ASI

B

n/s

n/s

ASI 2T3/2E3

ASI-T3

ASI

C

UCF

UCF

ASI 2T3/2E3

ASI-E3

ASI

C

UCF

UCF

ASI-155

ASI-155

ASI-155

B

n/s

n/s

ASI-155-E

ASI155E

ASI-155

D

n/s

n/s

ASI-155-E

ASI155E

ASI-155

E

WEC

WEC

ASI-155

ASI-155

ASI-155

H

WHC

WHC

ASM

ASM

 

A

GAC

GAC

BXM-BME

BME

BME

K

N/S

N/S

BXM-T3-8/12

BXM-T3

BXM

F

MFZ

MFW

BXM-E3-8/12

BXM-E3

BXM

F

MFZ

MFW

BXM-155-4/8

BXM-155

BXM

F

MFZ

MFW

BXM-622/622-2

BXM-622

BXM

F

MFZ

MFW

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

BXM-T3

BXM

F

MFZ

MFW

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

BXM-E3

BXM

F

MFZ

MFW

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

BXM-155

BXM

F

MFZ

MFW

BXM-622-2D/DX/2DX

BXM-622

BXM

F

MFZ

MFW

BNI-3T3/3E3

BNI-T3

BNI

C

TCM

TCM

BNI-3T3/3E3

BNI-E3

BNI

C

TCM

TCM

BNI-155

BNI-155

BNI-155

B

VBR

VBR

BNI-155-E

BNI155E

BNI-155

D

VDR

VDR


IGX 8400 Firmware Compatibility


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


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


Step 1 Execute a graceful upgrade to Release 9.3.53.

Step 2 Upgrade the UXM boot code to boot 8.

Step 3 Validate that boot code 8 is running.


Caution Upgrading the run-time firmware to ACC without boot code 8 can damage the UXM card.

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

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



Warning If these procedures are not followed, the card might enter a state from which it can NOT be recovered. See Appendix B for more information about loading the new firmware.


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


Step 1 Execute a graceful upgrade to Release 9.3.53.

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


Table 15 lists the Cisco IGX firmware.

Table 15 Cisco IGX Firmware Matrix 

PCB Description
dspcds Name
Card Name in Firmware Image
Model
Latest F/W
Min F/W

NPM 32 boot

NPM

NPM

B

RBT

RBS

NPM 64 boot

NPM

NPM|NPM-64

C

RCT

RCS

NPM-B 32 boot

NPM

NPM|NPM-32B

E

RET

RES

NPM-B 64 boot

NPM

NPM|NPM-64B

F

RFT

RFS

IGX-NTM

NTM

NTM

E

NJA

NEK

IGX-NTM (B)

NTM

NTM

F

NKA

NFK

IGX-UXM

UXM

UXM

B

ABV

ABH

IGX-UXM

UXM

UXM

C

ACL

ACH

VC Merge: ACJ

IGX-UXME

UXM

UXM

B

ABV

ABH

IGX-UXME

UXM

UXM

C

ACL

ACH

IGX-HDM

HDM

HDM

C

SCF

SCF

IGX-LDM

LDM

LDM

C

LCC

LCC

IGX-CVM-DS0A

CVM

CVM

A

DAF

DAF

IGX-CVM

CVM

CVM

B

DBF

DBF

IGX-CVM-TT

CVM

CVM

C

DCA

DCA

IGX-FRM

FRM

FRM

D

FDZ

FDZ

IGX-FRM-31

FRM

FRM-31

E

FEZ

FEZ

IGX-FRM-2

FRM

FRM-2

F

FFD

FFD

FRM(B)

FRM

FRM

H

FHB

FHB

IGX-FRM

FRM

FRM

J

FJB

FJB

IGX-FRM-31

FRM

FRM-31

K

FKB

FKA

IGX-UFM-4C/8C

UFM

UFM-C

A

ZAT

ZAN

IGX-UFM-4C/8C

UFM

UFM-C

B

ZBD

ZBA

IGX-UFM-U

UFMU

UFM-U

A

YAL

YAJ

IGX-UFM-U

UFMU

UFM-U

B

YBC

YBA

IGX-URM

URM

URM

A

XAB

XAA

IGX-URM

URM

URM

B

XBC

XBB

IGX-UVM

UVM

UVM

D

DDF

DDF

IGX-UVM1

UVM

UVM

E

DEF

DEE

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


Software Compatibility Matrix

Table 16 contains software compatibility information for Release 9.3.53.

Table 16 Compatibility with Other Software 

Switch or Component
Latest Version
Minimum Version

MGX 8220 Shelf

MGX 8220 5.0.20

MGX 8220 4.1.12

MGX 8220 5.0.17

MGX 8220 4.1.00

MGX 8230 (PXM1)

MGX 8250 (PXM1)

MGX 8850 (PXM1)

MGX 1.3.14

MGX 1.1.40

MGX 8850 (PXM45)

MGX 5.02.10

MGX 2.1.80

MGX 8850 (PXM1E)

MGX 5.02.10

MGX 3.0.10

MGX 8830 (PXM1E)

MGX 5.02.10

MGX 3.0.10

BPX SES Shelf

SES 4.0.15

SES 3.0.25

VISM-PR

VISM Release 3.3.25

VISM Release 2.1.1

Cisco WAN Manager (CWM)

CWM 15.1.50 Patch 2

CWM 12.0.00 Patch 3

CWM 11.0.10 Patch 4.1

CWM 10.5.10


MGX 8220 Hardware Compatibility

Table 17 lists the Cisco MGX 8220 hardware.

Table 17 Cisco MGX 8220 Hardware Matrix 

Card Type
Hardware Revisions
Image Type

ASC

AH, AJ, AK, AL, AM, AN, AP, AR

ASC

ASC/B

AN

ASC

ASC2

BA, BB, BC, BD, BE, BF

ASC

ASC2F

BA, BB, BC, BD, BE, BF

ASC

BNM-T3

AJ, BA, BB, BC, BD

ASC

BNM-T3/B

BE, BF

ASC

BNM-E3

AA, AB, AC

ASC

BNM-E3/B

AD, AE

ASC

BNM-155

AA, AB, AC, AD, AE, AF, AH

ASC

SRM-T1E1

AB, AC, BA, BB, BC

ASC

SRM-T1E1/B

BD

ASC

SRM-3T3, SRM-3T3/B, SRM-3T3/C

BA, BB, BC, BD, BE, BF

ASC

FRSM-4T1E1

AJ, BK, BL, BM, BN, BP, BQ, CA, CB, CC, CE

ASC

FRSM-8T1E1

AA, AB, AC

FRSM

FRSM-HS1

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

FRSM-8T1E1

FRSM-HS1/B

AA

FRSM-HS1

FRSM-HS2

800-029099-03 AO, 800-02909-04 AO

FRSM-HS2

CESM-RT1E1

AA, BA, BB, BC

CESM

AUSM-4T1E1

AA, AB, AC, BA, BB, BC, BD

AUSM

AUSM-8T1E1

AA, AB, AC, AD, AE, AF

AUSM-8T1E1

AUSM-8T1E1/B

AA

AUSM-8T1E1

IMATM-8T1E1

AA, AB, AC, AD, AE, AF, AG

IMATM8

IMATM-8T1E1/B

AA, AB, AC, AD, AE, AF

IMATM8

CESM-8T1E1

AA, AB, AC

CESM-8T1E1


BPX 8600 Hardware Compatibility

Table 18 lists the Cisco BPX hardware.

Table 18 Cisco BPX 8600 Hardware Matrix 

Card Type
Part Numbers
Latest H/W
Min. H/W
Controller Cards

BPX-BCC-64M (Non-Orderable)

800-04008-04

A

A

BPX-BCC-BC (Non-Orderable)

73-211380-00

D

A

BPX-BCC-3-64M

73-3720-02

R

J

BCC-3BC

800-02916-01

E

A

BPX-BCC4V

800-03580-06

E

C

BPX-BCC-4V/B

800-06483-02

C

A

ASI-2T3

73-216330-00

F

A

ASI-2E3

73-216330-01

F

A

ASI-155E

73-214250-00

H

F

ASI-155E

73-218100-02

J

A

Alarm Group

BPX-ASM

800-04009-01

C

A

BPX-ASM-BC

73-211910-00

C

A

ASM-LM

800-211910-10

B

A

Broadband Switch Group

BPX-BME

800-02855-04

B

A

BPX-BXM-T3-8

800-02777-07

J

B

BPX-BXM-T3-8E

800-03933-02

A

A

BPX-BXM-E3-8

800-02779-07

J

B

BPX-BXM-E3-8E

800-03928-02

A

A

BPX-BXM-T3-12

800-02776-07

J

B

BPX-BXM-T3-12E

800-03931-02

A

A

BPX-BXM-T3-12EX

800-03934-02

A

A

BPX-BXM-E3-12

800-02778-07

J

B

BPX-BXM-E3-12E

800-03929-02

A

A

BPX-BXM-E3-12EX

800-03930-02

A

A

BPX-T3/E3-BC

73-2759-02

A

A

BPX-BXM-155-8

800-02664-07

J

B (C for APS)

BPX-MMF-155-8-BC

800-03255-01

B

A

BPX-SMF-155-8-BC

800-03257-01

B

A

BPX-SMFLR-155-8-BC

800-02593-01

B

A

BPX-BXM-155-4

800-02666-07

J

B (C for APS)

BPX-BXM-E-155-4D

800-03094-02

A

A

BPX-BXM-E-155-8D

800-03092-02

A

A

BPX-BXM-E-155-4DX

800-03093-02

A

A

BPX-BXM-E-155-8DX

800-03091-02

A

A

BPX-MMF-155-4-BC

800-03256-02

B

A

BPX-SMF-155-4-BC

800-03258-01

B

A

BPX-SMFLR-155-4-BC

800-02594-02

B

A

BPX-BXM-622

800-02646-10

M

D (E for APS)

BPX-BXM-622-2

800-02638-10

M

D (E for APS)

BPX-BXM-E-622-2D

800-03150-02

A

A

BPX-BXM-E-622-DX

800-03151-02

A

A

BPX-BXM-E-622-2DX

800-03149-02

A

A

BPX-622-2-BC

73-2884-01

D

A

BPX-SMF-622-BC

800-03249-01

C

A

BPX-SMF-622-2-BC

800-03251-01

C

A

BPX-SMFLR-622-BC

800-03250-01

C

A

BPX-SMFLR-622-2-BC

800-03252-01

D

A

BPX-XLR-622

800-02738-01

C

A

BPX-XLR-622-2

800-02739-01

C

A

BPX-BME-OC12

73-2469-07

F

A

RDNT-SMF-155-4R

800-03677-01

J

A

RDNT-SMF-155-8R

800-03679-01

K

A

RDNT-LR-155-8R

800-03678-01

J

A

RDNT-LR-622-2R

800-03676-01

F

A

RDNT-SMF-622R

800-03675-01

F

A

RDNT-SMF-622-2R

800-03674-01

J

A

BPX-STM1-EL-4

800-03716-02

A

A

BNI-3-T3/C

800-02858-02

A

A

BNI-3-E3/C

800-02859-02

A

A

BNI-155E

73-218100-01

K

A

BNI-2-155/B

73-4133-01

L

L

BPX-T3/E3

800-03058-02

E

A

BPX-E3-BC

73-213070-01

E

A

BPX-MMF-2-BC

73-214290-00

D

A

BPX-SMF-2-BC

73-216270-00

D

A

BPX-SMFLR-2-BC

73-216270-01

D

A

SMF-LM-OC3

800-216270-10

C

A

SMF-LM-OC3-LR

800-216270-11

C

A

MMF-LM-OC3

800-214290-10

B

A

LM-3T3

800-213070-10

D

A

LM-3E3

800-213070-11

D

A


IGX 8400 Hardware Compatibility

Table 19 lists the Cisco IGX hardware.

Table 19 Cisco IGX Hardware Matrix 

Card Type
Part Numbers
Latest H/W
Min. H/W
Comments
Controller Cards

IGX-NPM-32

73-2894-01

W

A

IGX-NPM-64

73-2895-01

W

A

IGX-NPM-32B

73-2554-04

L

A

IGX-NPM-64B

73-2363-02

C

A

IGX-SCM

73-3341-01

Y

A

Revision X or later for nodes with UXM IMA trunks

Alarm Group

IGX-ARM

73-218230-00

B

A

BC-512011

73-212360-00

D

A

Trunk Group

IGX-NTM

73-2296-04

E

A

BC-6271A-TI

73-207380-00

M

A

BC-6171A-E1

73-207370-01

P

A

BC-6083A-SR

73-208540-00

J

A

BC-550150-Y1

73-210820-01

D

A

ACM1

73-2921-03

W

A

BC-571110A-T3

73-2879-01

L

A

BC-571210A-E3

73-2679-01

K

A

BC-571310A-E2

73-215940-00

D

A

BC-571410A-HSSI

73-216370-00

A

A

IGX-UXM

73-2511-03

D

A

IGX-UXM-E

A

A

BC-UAI-4-155-SMF

73-2703-03

D

A

BC-UAI-4-155-MMF

73-2705-03

D

A

BC-UAI-2-155-SMF

73-2699-03

C

A

BC-UAI-2SMFXLR

A

A

BC-UAI-4SMFXLR

A

A

BC-UAI-6-T3

73-2952-02

A

A

BC-UAI-3-T3

73-2954-02

A

A

BC-UAI-6-E3

73-2953-02

A

A

BC-UAI-3-E3

73-2955-02

A

A

BC-UAI-8-E1-BNC

73-2932-02

C

A

BC-UAI-4-E1-BNC

73-3061-01

C

A

BC-UAI-8-T1-DB15

73-2941-02

C

A

BC-UAI-8-E1-DB15

73-2942-02

C

A

BC-UAI-4-T1-DB15

73-3059-01

C

A

BC-UAI-4-E1-DB15

73-3060-01

C

A

BC-UAI-4-STM1E

73-3364-02

A

A

Port Group

IGX-URM

800-06260-06

A

A

BC-2FE2V

800-06257-03

A

A

ACM1A

73-2930-03

W

A

IGX-HDM

73-2853-02

F

A

*Show SDP H/W Rev, DM=SDP+ACM2

ACM2

73-2922-03

T

A

BC-5082A-V35

73-2450-01

K

A

BC-5083A-RS449

73-204850-00

V

A

BC-5084B-RS232

73-2723-01

W

A

IGX-LDM

73-207250-00

K

A

*Show LDP H/W Rev, LDM=LDP+ACM1A

BC-5286A-RS232

73-207180-01

L

A

LDI-4RS232

BC-5287A-RS232

73-207180-00

L

A

LDI-8RS232

IGX-CVM-DSOA

73-3002-02

D

A*

*Show CDP H/W Rev, CVM=CDP+ACM1A

IGX-CVM-T1EC

73-3003-03

E

A*

*Show CDP H/W Rev, CVM=CDP+ACM1A

IGX-CVM-E1EC

73-209660-00

H*

A*

*Show CDP H/W Rev, CVM=CDP+ACM1A

IGX-CVM-TT

BC-6271A-TI

73-207380-00

M

A

BC-6171A-E1

73-207370-01

P

A

BC-550100-J1

73-210820-00

C

A

IGX-FRM

73-2517-03

N

A

IGX-FRM-31

73-2517-03

N

A

IGX-FRM-2

73-2519-01

M*

A*

*Show FRP H/W Rev, FRM-2=FRP+ACM1A

BC-6251B-V35

73-3253-01

M

A

FRI-4V.35-2

BC-6254A-X21

73-211440-00

H

A

FRI-X.21

BC-6355A-X21

73-214120-01

C

A

FRI-2X21

IGX-UFM-4C

73-2531-05

N

A

Needs a minimum of ZAS/ZBC Firmware

IGX-UFM-8C

73-2531-05

N

A

Needs a minimum of ZAS/ZBC Firmware

BC-UFI-8T1-DB15

73-2444-02

D

A

BC-UFI-8E1-DB15

73-2445-02

D

A

BC-UFI-8E1-BNC

73-2449-02

D

A

IGX-UFM-U

73-2349-04

D

A

BC-UFI-12V35

73-2711-01

D

A

BC-UFI-12X21

73-2712-01

D

A

BC-UFI-4HSSI

73-2693-01

C

A

IGX-UVM

73-2361-04

K

A

BC-UVI-2E1EC

73-2420-01

B

A

BC-UVI-2T1EC

73-2373-01

C

A

BC-UVI-2S1EC

73-2374-01

A

A


Anomalies in Release 9.3.53

The following three tables in this section describe the known and resolved caveats and the anomaly status changes in Release 9.3.53.

Fixed Anomalies in Release 9.3.53

Table 20 lists the anomalies that are fixed in Release 9.3.53.

Table 20 Anomalies Fixed in Release 9.3.53 

Bug ID
Description

CSCds47671

dspcurclk displays incorrect clock path for via nodes

CSCef29422

Lost user commands after upgrade

CSCeg37046

BPX BXM corrupts VCCs > 4095 in VPC

CSCeg38815

High BPX CPU during line alarms/BPX/SES configurations

CSCeg45987

Connections become incomplete after coldstart followed by warmstart

CSCei01704

Clock degrades when configuring EXT-1 PRIMARY and EXT-2 secondary on same BCC

CSCej19930

cnfrsrc allows more connections in a port group


Known Anomalies in Release 9.3.53

Table 21 lists the known anomalies in Release 9.3.53.

.

Table 21 Known Anomalies in Release 9.3.53 

Bug ID
Description

CSCdp48861

Headline: Polling for voice conn and line stats results in high TRNS RT usage.

Symptom: The customer might notice slow UI response or a difficulty logging into the node using the normal VT session. The dspprfhist command shows high RT usage in the TRNS process. The thstats shows high RT usage by state machine 55 (0x33).

Conditions: This symptom is due to statistics updates for voice connections. The problem might be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs).

Workaround: The command off1 17 can be performed. Using this command will stop the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats.

If statistics must be collected, limit the number of statistics. Frame Relay statistics are collected at 5 minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1 minute intervals. However, the following statistics are reported at 3 second intervals:

Seconds V.25 Modem On

Seconds DSI Enabled

Seconds Off-Hook

Seconds In Service

CSCdx33468

Headline: dspcons shows connections but dspcon shows connection does not exist

Symptom: dspcons shows all connections but dspcon shows "connection does not exit"

Conditions: The network has the following software configuration:

SWSW is 9.3.51

BXM FW is MFR

Workaround: Use the rbldlogepdb command to rebuild the logical endpoint databases.

CSCdx33733

Headline: swerror 398 on a 9.3.40 IGX node in upgrades network

Symptom: swerror 398 on a 9.3.40IGX node.

Conditions: After a flash non-graceful upgrade.

Workaround: None

CSCdx69339

Headline: 103 logged on IGX when run overnight jobs.

Symptom: A swerr 103 is logged on UXM when running overnight jobs.

Conditions: Run overnight jobs such as switchcc, resetcd on IGX nodes.

Workaround: Unknown.

CSCdx69838

Headline: 3M abort message logged on BPX, then BPX to degraded mode.

Symptom: 3000000 abort message logged on BPX causes a switchcc.

Conditions: This particular 3000000 abort occurs because of a card failure that is causing the card to continually log software error 105's.

Then the messages are queued up. If sufficient memory is not available, the node runs out of memory and then does a 3000000 abort. For the case where this was observed, the node had 15,947 connections—a very heavily populated node.

Workaround: Periodically, the slot that is continually logging the software error 105 that is causing the memory accumulation will clear the queued messages for that slot.

Or, remove the card.

Further Problem Description: This memory fault is occurring because a BXM was continually encountering a buffer full errors for more than 15 continuous hours. 105's are typically caused by faulty firmware, and are not expected to occur regularly. If so, this fault certainly does not occur at the level as encountered by this defect.

CSCea83465

Headline: BXM suspected of failure

Symptom: BPX-8620 system log shows "BXM 4 SUSPECTED OF FAILURE" messages, then after an hour the "BXM 4 SUSPECTED OF FAILURE IS NOW CLEAR" message appears. The switch never goes down and there is no indication of lost connections.

Condition: These log messages occurred in system running 9.3.3.6 and having over 12,000 terminating connections. It was first discovered after upgrading from 9.2.31 to 9.3.36 swsw release.

Workaround: None.

CSCec72834

Headline: Error returned when disabling HCS masking on BXM using snmpset

Symptom: Using snmptool, unable to set the values for HCS Masking on BXM lines and trunks.

Conditions: cnftrk and cnfln allows user to set the values for HCS masking on BXM E3 and T3 cards. But the same functionality is not available from snmp tool snmpset.

Workaround: None

CSCei74018

Headline: Trunk stays in Path Parity Error and sometimes cleared using cnftrk command

Symptom: BXM trunk shows path parity error

Conditions: Trunk with Path parity errors.

Workaround: Change the cable length parameter using cnftrk command to clear the alarm on this trunk

CSCej64267

Headline: BCC mastership - suspected of failure

Symptom: BCC4V refuses to accept mastership when switchcc is issued. The card logs a swerr52 (watchdog timeout)

Conditions: SWSW version 9.2.34

Workaround: None.

CSCin34948

Headline: swerr 586 on BPX node running 9.3.36

Symptom: swerr 586 on BPX node

Conditions: After upgrade from 9.3.24.

Workaround: None

CSCin36516

Headline: swerrors 923, 614,529 and 9000 on IGX feeder running 9.3.11

Symptom: swerrors 923, 614,529 and 9000 on IGX feeder.

Conditions: After loading 9.3.11 on node.

Workaround: None

CSCin98403

Headline: Syncup issue between MGX and BPX over ENNI/XLMI enabled trunk

Symptom: AIS on connections on BPX side ENNI port.

Condition: After a few basic APS-related tests were performed on the ENNI segment.

Workaround: Enter dspchstats on BPX for connections having AIS. This clears the AIS alarms.


Anomaly Status Changes in Release 9.3.53

Table 22 lists anomalies that have changed status since Release 9.3.51. Changed status means that the anomaly went from open to a state other than resolved. The status field states if the anomaly is closed, junked, duplicated, or unreproducible.

Table 22 Anomaly Status Changes in Release 9.3.53 

Bug ID
Status

CSCdr05291

Problems deleting feeder trunks via SNMP: Closed

CSCdr45021

Request to generate an alarm when an SES trunk use default SCT 1: Closed

CSCds68363

first_avail_lcn is UNKNOWN after BCC is switchcc or rebuilt: Closed

CSCdv33406

BXM-155 with APS Automatically loop release by switchyred command:Closed

CSCdv79961

Cannot configure stat level on UXM Y-red standby card: Closed

CSCdv87535

chklm trk topology is inconsistent in lsnt/upgrade/fallback: Closed

CSCdw04847

FastPackets used instead of cells for ATM queue size and delay calculations: Closed

CSCdw42981

off3 parameters 1,2 and 3 get set to the default value after rebuild: Closed

CSCdw64896

Disabling routing state machine does not reduce high CPU usage: Closed

CSCdw68880

Some BXM statistics are not being polled—always zero value: Closed

CSCdw86892

Event log for switchyred errors does not cover all possible errors: Closed

CSCdx27113

Sometimes Seconds in Service reported 3601 seconds for one hour: Forwarded to MGX 1 team

CSCdx39692

swerror 1012 on doing dspchuse on a UXM card: Unreproducible

CSCdx48581

Traffic leaking on IGX trunks upon remote loopback with UXM Y-red: Duplicate

CSCdx51883

Configuring pass sync on virtual trunk does not change Pass Sync on all ports: Closed

CSCdx59734

Swerr 524 is logged on BPX: Duplicate

CSCdx65552

Wrong alarm reporting when APS 1:1 configured on BXM: Unreproducible

CSCdy70622

Routine get_line does not properly handle feeder trunks: Closed

CSCdy81298

Switch does not send ELMI updates to router after changing Dnld type: Closed

CSCdy89732

Software log on standby NPM sometimes cleared after an abort: Closed

CSCdz53573

Add an event in node log when ELMI is activated and deactivated: Closed

CSCea33846

The point of Slot 7 to 7 and 8 on Cross Point is NOT tested by tstber: Closed

CSCea64275

Need SwSw command to display IGX bus parity error counters in UXM/URM: Closed

CSCed88405

BCC cards not communicating with each other: Closed

CSCee18806

bpx8620-add pSN to EEPROM; add entPhysicalSernum.1 Support: Closed

CSCee35937

Frame Relay connection failed to route.

CSCee41531

BXM connection go into inhibited state after being up/downed: Unreproducible

CSCee47644

CRC-YES on Unframed E1 (UXM-IMA): Unreproducible

CSCee79630

A UXM in a failed state caused the CPU to ramp up to 99%: Unreproducible

CSCef32602

Swerr 5050 with cba_verify on IGX with VSI partition: Resolved in UXM firmware version ACL

CSCej09562

Priority Bumping bands missing, BCC aborts, node hangs: Closed

CSCej42564

XGXLMI_JIT: Incomplete XLMI Neighbor I/F name in BXM card: Closed

CSCin68040

Not able to add/delete IGX shelf using snmpset on BPX: Closed

CSCin86145

State table hung error on attempting test delay on BXM-FRSM2CT3 PVC: Closed

CSCin96228

Mismatch occurred when migrating from BXM to BXME(OC12) in Active mode: Closed

CSCin96992

Logical DB not getting updated properly when migrating from UXM-UXME: Closed

CSCst94867

The cnfbkcd command fails to program Revision value properly: Closed


Anomalies in Release 9.3.51

The following three tables in this section describe the known and resolved caveats and the anomaly status changes in Release 9.3.51.

Anomalies Fixed in Release 9.3.51

Table 23 lists the anomalies that are fixed in Release 9.3.51.

Table 23 Anomalies Fixed in Release 9.3.51 

Bug ID
Description

CSCef19285

Control the RT Stats(from SNMP GET) through on/off3 (SNMP Gets causing high CPU use)

Symptom: CPU Usage seen to be very high when the node is processing multiple SNMP GET requests for statistics counters for trunks, lines and connections.

The requests are being sent to node via SNMP scripts from a third party software.

Conditions: Behavior seen only on 9.3.47 release of SWSW onwards.

Workaround: Redesign SNMP scripts to reduce polling on the node.

Further Problem Description: Problem is seen because SNMP GET on statistics causes real time polling on the node. This can increase CPU usage when there are a series of such multiple GET requests issued to a node in quick succession. The impact of these requests is higher when the counters retrieved are actually polled on the node.

Real Time Statistics are polled for under three cases:

1. enabling interval statistics - enable using cnfstatparms/cnfchstats/cnftrkstats/cnfportstats

2. summary statistics -no enabling required. Can be seen using dsptrkstats, dspportstats, dspchstats

3. Real time counter statistics - no enabling required, can be seen using dspcntrstats

Of these three cases, this problem can be observed only for options 1 and 3 which will update the counters retrieved by SNMP GET at real time.

Option 1 will show problems when counters are enabled using any of the above commands and multiple OID SNMP GETs are issued for these counters.

Option 3 does not require any statistics enabling to be explicitly done on the node. The RTC counters are a subset of the available interval statistics. For every SNMP GET involving these RTC counters, the card is polled at real time and the CPU utilisation can be seen going up for multiple OID SNMP GETs involving these counters also.

Note The new ON3 parameter that can be used to disable real time polling for statistics (parameter 8) will work transparently in the case of Option 1. But if Option 3 was being used, interval statistics for the corresponding counters have to be enabled on the node, to continue the statistics collection.

RTC statistics was not controlled before. But by introducing the new ON3 parameter this feature is now controlled.

CSCdm38743

Addcon in a addjob does not let you configure PCR (0+1)

CSCdp26838

SWERR 2058 logged on standby NPM, dspstatparms shows more stats on stby NPM

CSCds10336

cnfprf r limits for STAT and POOL are larger than the maximum allowed

CSCds26082

No Option for disabling HCS Masking on E3/T3 trunks and lines on BXM

CSCdt07203

Hitless rebuilds logged on a failed switchcc can fill hitless log

CSCdt80333

cnfbkcd accepts invalid entry for back card TAN field parameter

CSCdu13764

dspjob always shows cnfcmparm passed even though the command fails.

CSCdu13921

Not enough trunk con ids show as not enough trunk BW for failed cons

CSCdu15686

Diagnostics PortTest V35/X21

CSCdu50696

Code cleanup: incorrect coding in get_rrt_ltrk()

CSCdw37288

Enhance code to notify user of obsolete FTM card

CSCdw44810

Event log for runrev initiated from remote node says loadrev

CSCdw81320

Remove the psm.t state machine and globals from BPX

CSCdx20450

Remove obsolete code for cnfcmdbgparm

CSCdx24746

Error messages are different when provisioning AR over reserved VPI

CSCdx34887

Incorrect status reported for failed connections due to open space calc.

CSCdx92352

Changing peak for already enabled TFTP stats does not work

CSCdx93228

Error message 2004 on the switch

CSCdy17099

Uninitialized variables used in gt_nxt_bndl_con()

CSCdy22026

memmap shows wrong value for space left in case of memory overflow

CSCdy35192

Minor alarm does not clear on CWM GUI BPX icon unless you log into the node

CSCdy49484

Active BCC taking software error 992 continuously

CSCdy54959

SW Error 551 clears only on reseating of the BCC card

CSCdy68473

Prompt for adding or deleting all loopbacks on IMA is misleading

CSCdz00821

delshelf is allowed to proceed while there are VSI connections on fdr trk

CSCdz42375

Swerror 263 appeared on node cerise

CSCdz78273

Incorrect error message returned when assigned VPI/VCI picked on fdr trunk

CSCea00485

Upgrade from 9.2.34 to 9.3.24 APS lines show on their PROT incorrectly

CSCea04404

HEC line displays t3/636 rather than t3/690 - bandwidth limited

CSCea22154

upln on BXM-155 logs swerr 5105, inconsistent databases warning on dnln

CSCea32473

l & t options of dspconcnts wrongly show lns & trks alarms as masked.

CSCea36542

VCI = 0 on overlapping resources created via sw CLI not added in cwm db

CSCea41956

Standby BCC status became Cleared in the cause of SWLOG 586.

CSCea50919

BPX, slotFrontCHCount SNMP does not respond correctly to BXM-E

CSCea55566

dsptrkerrs reporting large amounts of COMM FAIL on trunks after switchcc

CSCea58058

addcon for an SIW conn does not work in a job from the F/Relay side

CSCea60732

Failcd does not accept (self test) and (BUS) for stbybcc from ACTV CLI

CSCea71630

Runjob to configure trunk failing for UXM trunks

CSCeb02540

SNMP get query does not trigger a poll for any object in atmTrunkStatsTable

CSCeb31595

One end of connection failed with one way PVC

CSCeb34045

Under certain conditions, IGX may send incorrect ABIT alarm towards feeder

CSCeb41182

Pass Sync not propagating correctly on trunk add

CSCeb41930

AUTO: Local MCR for this connection cannot be less than 7

CSCeb48398

Toggling Payload Scrambling on a VT not implemented correctly

CSCeb48781

Add AIS/RDI filter option to dspcons command

CSCeb69548

Loop in a UFM port could be deleted but stays in the connections

CSCeb87464

UXM E3 is flagging Minor Alarms for BIP-8s incorrectly

CSCec24228

cnftrk fails on port with multiple virtual trunks

CSCec27023

SWSW gives ICS related error msg with 56k addcon on HDM

CSCec27568

Disallow D4 framing config on FR T1 lines using 24 DS0s

CSCec30644

IGX UXM IMA trunk not allocating correct DS0s when map changed

CSCec53390

Physical UBUs are incrementing on standby UFM after background diag test.

CSCed21795

IGX/BPX QIR timeout value in cnffstparm

CSCed24965

Stats 46 and 47 not collected for IMA line/port

CSCed41679

BXME, Upgrading LCNs to 60K Fails

CSCed45736

Suddenly, all BXM and Standby BCC are removed.

CSCed88906

Each 57 minutes a PNNI trunk goes down & up

CSCee03234

BPX rebuild due to UP failure on active BCC card

CSCee21672

Incorrect output for fpRteTrkRcvCap MIB

CSCee34625

TCP RST vulnerability unexpectedly close telnet session

CSCee39134

Loopback appears, cant delete it

CSCef08257

BXM OC-3 HCS Correctable Error count missing in SNMP

CSCef19285

Control the RT Stats (from SNMP GET) thr on/off3 (SNMP Gets causing high CPUuse)

CSCef19669

Active NPM keeps on resetting and standby is stuck at downloading with 1M3 err

CSCef25628

Disable background test for FR cards, when the tst dc allocated outside reserved

CSCin32081

Enum missing for STS-12c sonetIfFrame in strata.mib

CSCin33083

Swerr 2000 on IGX feeders on SNMPwalk

CSCin34650

cnfrsrc CLI does not refresh properly

CSCin34914

Update atmEndptTestType mib

CSCin36369

swerr 534 on BPX node when dspconcnts t is done

CSCin36370

swerr 105 on powering off and powering on IGX node

CSCin40238

Protocol by card field does not refresh on cnftrk

CSCin43274

dncon/upcon with COS option should be accessed from SUPERGRP or higher levels

CSCin43311

If the conn type changed in cnfatmcls then prev conn types defaults are loaded

CSCin44817

BXM allows to modify ADTF value through connproxy which is out of range

CSCin46239

dspconcnts p does not work properly on IGX and IGX feeders

CSCin47670

Failcd options 2&3 do not work for active & stby BCC

CSCin48202

3M abort on dspch execution repeatedly

CSCin77022

SWLOG 265 while upgrading from 9.2.45 to 9.3.5A

CSCin77463

Incorrect Enable time shown in dspstatparms

CSCin77749

SWLOG 921 on IGX nodes continuously

CSCin78029

SWLOG 513 while working on URM card in IGX

CSCin78126

Change definition of swerr 265 (DATA_RUINED_UPGRADES) to be meaningful


Anomaly Status Changes in Release 9.3.51

Table 24 lists anomalies that have changed status since Release 9.3.47. Changed status means that the anomaly went from open to a state other than resolved. The status field states if the anomaly is closed, junked, duplicated, or unreproducible.

Table 24 Anomaly Status Changes in Release 9.3.51 

Bug ID
Status

CSCdk22430

Word 15 of bpnv checksum is not recalculated: Closed

CSCdk80347

Standby NPM Watchdog Timeout after resetsys, 1M3, 2M, or abort command: Closed

CSCdk91790

Eliminate UVMs modem polling to save system idle time: Closed

CSCdm22426

Commands which lock UI - dspbob - will cause jobs to fail without notice: Closed

CSCdm40952

Two PVCs rerouted during switchcc in BPX network: Closed

CSCdm76279

CiscoView no Data for FR-RealTimeCounters on IGX: Closed

CSCdp44912

Upgrade 9.1.04 to 9.1.16 causes UXM Y-red cards to go into mismatch: Closed

CSCdp98648

CWM 92 equipment MGR does not support BXM enhance card type: Closed

CSCdr25278

Loss of Signal not properly indicated per UNI 3.1: Closed

CSCdr58295

burnfwrev before the completion of resetcd, makes the UXM card to Fail: Closed

CSCds34334

Traffic through IMA trunks on BNI card does not fail: Closed

CSCds64046

SWerror 254 logged over weekend when network was in steady-state: Duplicate

CSCds81526

Downed connections on master come up while on the slave side stay downed on BPX/IGX: Closed

CSCdt66696

AIT-E3 backcard is displayed as BTM-E3 in CLI: Closed

CSCdu03108

1427 (NW_MSG_VERSION_MISMATCH) while nodes are upgrading: Unreproducible

CSCdu22300

Connections not routed due to wrong Gateway LCN calculation (RARE condition): Closed

CSCdv36764

Swerr 1008 was logged due to a BXM card resetting continuously: Duplicate

CSCdv73494

Swerr 886,2071,2059 fills the log: Unreproducible

CSCdw01866

Hitless rebuild, load updates is extremely slow: Closed

CSCdw03498

Backcards empty after resetsys on node sw150: Unreproducible

CSCdw04934

CLI switchyred command, took approx. 40 to 70 seconds to complete: Closed

CSCdw07614

Date and time changed after runrev command was issued: Unreproducible

CSCdw30811

Improperly format FPAD port object and alarm messages sent to CWM: Closed

CSCdw47805

Possible NTM SR trunk with mismatch tx ts queue depth after upgrade: Closed

CSCdw60790

addcon fails to add abrfst conn with PCR < 50 for BXM 0C12 port card: Closed

CSCdw78948

Swerror 105 after node rebuild: Closed

CSCdw85810

upport, cnfport does not enforce port group speed limitation on UFMU card: Closed

CSCdx22448

VSI protocol down if delete and re-add mpls vsi controller quickly: Closed

CSCdx23232

con_verify on BPX for conns logs swerr 1417: Duplicate

CSCdx33468

dspcons shows connections but dspcon shows connection does not exit: Unreproducible

CSCdx34134

testdelay times out every now and then: Closed

CSCdx34855

dsptech displays a false vc db inconsistency warning: Closed

CSCdx34916

Routing open space calculation incorrectly checks the max. VPC limit: Duplicate

CSCdx48315

Time zone not specified in event, error or abort logs: Closed

CSCdx48623

9084/BC06 when local loop back added to a trunk on a Y-RED UXM: Unreproducible

CSCdx68364

1m3 abort logged on IGX: Closed

CSCdx69703

9000 logged on UVM: Duplicate

CSCdx72680

331 fills log on NG upgrade to 934T when on/off (Neighbor Update Errs) enabled: Duplicate

CSCdx78034

542 CRC error&1m2 abort logged when upgrade to 9.3.40 on BPX: Unreproducible

CSCdx84899

Swerr 105/100; aborts:1011,2M appeared with SES 1.1.75.103 attached: Duplicate

CSCdx85868

delallsvcrsrc cause APS errors to be sent to CWM: Unreproducible

CSCdy79353

Spare bandwidth not fairly allocated between autoroute and MPLS traffic: Junked

CSCdy89690

Feeder status changes not logged on BPX hub when BXM runs the protocol: Duplicate

CSCdz02751

Unknown OAM Cell Rx: Unreproducible

CSCdz08271

Rx Port errors on ASI when line is upped but port is not: Junked

CSCdz46757

Swerr 32 logged on bpx: Unreproducible

CSCdz48634

Network clocking split in BPX/IGX nw when IGX is primary clock source: Junked

CSCdz87003

Test Delay Granularity not accurate: Closed

CSCea54762

AIS not reported by BPX dspcon, until dspchstats is executed: Junked

CSCea56662

addcon returns Other end QIR out of range for this end card: Duplicate

CSCea56907

Inter card connection between two BXMs is not programmed correctly: Unreproducible

CSCea67768

Non dax connection information is not updated after dax connection is deleted: Closed

CSCea76950

Node Abort, following swerr 100, 502, 589 and 504: Unreproducible

CSCin09100

SWerror 55 was logged in the entire n/w of BPX/IGX when fallback: Unreproducible

CSCin42263

SWerror 590 logged on BPX node. Node utilization 100%: Closed


Anomalies Fixed and Changed Status in Release 9.3.47

This section contains the anomalies that are fixed and have changed status in Release 9.3.47.

Anomalies Fixed in Release 9.3.47

Table 25 lists the anomalies that are fixed in Release 9.3.47.

Table 25 Anomalies Fixed in Release 9.3.47 

Bug ID
Description

CSCdu38434

NWBrowser shows Back card revision for the absent backcards as EW by default

CSCdu43698

Able to do a cnftermfunc even user level 6

CSCdw02563

Swerr 9000 on node chevy in slot 30 UFM

CSCdw18589

Config for pass sync yes on VT as clock source should not be allowed

CSCdw89836

tstber does not work between ASI & BXM with virtual port

CSCdw93967

switchyred logs event during addjob

CSCdx48549

dspportstats allows feeder trunk interface but displays no data

CSCdy41099

Swerr 923 logged upon card status change of UXM IMA line cards

CSCdy50994

30 & 923 when cnftrkict/dsptrkict run on NTM slot that does not have a trunk up

CSCdy54483

oamlpbac support needs removing from dspcd (IGX) and dsplogcd (BPX)

CSCdy55257

SLT: SWERR 9000 logged on IGX01 when switchcc was done

CSCdy55970

Virtual Trunks can be upped with 0 Tx/Rx rate when no port BW is available

CSCdy63195

IP Relay gateway node not initialized after clrallcnf/lanbtld

CSCdz02229

addlnlocrmtlp on an inactive UXM line yields wrong error message

CSCdz02882

CWM 10.5.10: Unable to modify the connections on the conn manager

CSCdz03828

addapsln allows to add an active protection line

CSCdz10893

Initialize idle data channels as voice channels (Missed reveup changCSCdk80460)

CSCdz19464

CBR cells 100% Oflw CLP0 Dscd at ingress

CSCdz30108

The clock stuck into the HOLDOVER state

CSCdz38313

Killuser does not clear console—Cannot access

CSCdz73261

Load balance problem on parallel trunks between two BPX nodes

CSCea04555

SWSW sending incorrect message to CWM

CSCea36542

VCI=0 on overlapping resources created via switch CLI not added in CWM database

CSCea50327

Unable to modify Slave Endpoint for a DAX conn using SNMP

CSCea50919

BPX, slotFrontCHCount SNMP does not respond correctly to BXM-E

CSCea60732

Failcd does not accept (self test) and (BUS) for stbybcc from ACTV CLI

CSCea71630

Runjob to configure trunk failing for UXM trunks

CSCin03628

Trunks can be added when Pass Sync values at end points do not match

CSCin21585

atmEndPointIBS range is 0-24000, unable to set IBS to 0

CSCin26344

Node alarm status not send for CC alarm

CSCin32081

Enum missing for STS-12c sonetIfFrame in strata.mib

CSCin32713

Failcd (SAR) and (UP) for STBY BCC need to be blocked from ACTV CLI

CSCin32729

Swerr 4208 (BAD_CA_TYPE) after cnfpref

CSCin33657

SNMP GET stat polling does not return real-time stats

CSCin35235

addapsln causes swerr 25

CSCin36346

Swerr 419 on removing a node with voice conns from the network

CSCin36369

Swerr 534 on BPX node when dspconcnts t is done

CSCin40514

atmEndptDesc not handled correctly when modifying atm connection

CSCin43274

dncon/upcon with COS option should be accessed from SUPERGRP or higher levels

CSCin43311

If the connection type changed in cnfatmcls then previous connection type defaults are loaded


Anomaly Status Changes in Release 9.3.47

Table 26 lists anomalies that have changed status since in Release 9.3.47. Changed status means that the anomaly went from open to a state other than resolved. The status field states whether the anomaly is closed, junked, duplicated, or unreproducible.

Table 26 Anomaly Status Changes in Release 9.3.47 

Bug ID
Status

CSCdw01813

LSNT: power down/up 42 real nodes out of 220 nodes, 419 seen: Duplicated

CSCdw40470

tstpingip result display incorrect for multiple users: Duplicated

CSCdx78070

Swerr 5050 with cba_verify: Resolved in UXM AC

CSCdx87582

IMA link not removed from group during statistical errors alarm condition: Closed


Anomalies Fixed and Changed Status in Release 9.3.45

This section contains the anomalies that are fixed and have changed status in Release 9.3.45.

Anomalies Fixed in Release 9.3.45

Table 27 lists the anomalies that are fixed in Release 9.3.45.

Table 27 Anomalies Fixed in Release 9.3.45 

Bug ID
Description

CSCdy54662

Heavily loaded node reports cell bus errors and UXM card removals

CSCdy62028

PXM (feeder) node update status to IGX causes frame bit errors


Anomaly Status Changes in Release 9.3.45

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

Table 28 Anomaly Status Changes in Release 9.3.45 

Bug ID
Status

CSCdw49947

UAS is too small when line is in alarm: Closed

CSCdx10412

Swerr 504 on n5c in regr. n/w: Unreproducible

CSCdx69347

BCC stuck in clear state, sw error 105 repeating: Unreproducible

CSCdy21028

Database corruption occurred during upgrade form 9.2.41 to 9.3.36: Junked

CSCdy48326

CPU Utilization is high and get BXM XX Suspected of failure msg: Closed

CSCdy49484

Active BCC taking software error 992 continuously: Unreproducible


Anomalies Fixed in Release 9.3.42

Table 29 lists the anomalies that are fixed in Release 9.3.42.

Table 29 Anomalies Fixed in Release 9.3.42 

Bug ID
Description

CSCdk37976

No alarm when active BCC-32 backcard removed

CSCdk49036

Multiple errors with cnftrk during Job Addition

CSCdm19518

Pref routes are not displayed correctly by cnfpref and dsprts

CSCdm31682

cnfchvcq for ALM-A connections wont allow user to maximize 16000 cell buffer

CSCdr08809

dspstbyclk shows LOS on a good external clock source

CSCdr28021

addcon on CVM does not prompt for all types of voice connections supported

CSCdr56878

cnfln to change traffic shaping does not change existing VCs

CSCdt22924

Lines configured as clock source goes to bad clock source after dncd/upcd

CSCdu34215

Usage: cnflan - contains inaccurate parameter information

CSCdu75550

Log slot used instead of physical in svr_bxm_card_type()

CSCdv23693

CBR traffic dropped when background test is executed

CSCdw11977

1m3 may be logged in Free_mem when logging other mem corruption errors

CSCdw25128

HCS Correctable error (Stat 55) was not shown when errors were injected

CSCdw28930

External clock switch due to clock master node switchcc

CSCdw30986

Swerr 992 logged after SAR reprograms IP/ILMI channels

CSCdw35862

dspapsln does not show standby fail when standby card removed

CSCdw54520

Potential memory corruption in Pcs_get_event()

CSCdw69403

Shift/no shift inconsistency checks cause problems with CLI and SNMP addcon

CSCdw74242

Enabled from/time fields not updated when TFTP stats partially enabled

CSCdw74266

cnfport allowed on UFMU secondary card

CSCdw78620

Software error 75 logged on BPX

CSCdw80502

Cleanup: no effect statement in nw_r_prot.c

CSCdw83716

UBUs mistakenly assigned to UFMU

CSCdw90487

SWLOG 1423 generated on executing dsprtcache (detailed) command.

CSCdw95273

MIB incorrectly indicates that Virtual Trunks do not support stats

CSCdx02074

Be, Bc values are getting incorrectly set upon addcon

CSCdx02607

Code cleanup in addjobtrig function

CSCdx04153

Frame Relay conns using wrong loadtype, with cnfcon

CSCdx05212

Unable to derive clock signal from UXM Feeder Trunk on IGX Feeder

CSCdx05238

Switchapsln followed by the same priority request is accepted and pending

CSCdx21047

cnfln job connections present prompt causes job to fail

CSCdx24719

dspchuse gives misleading information BXM-DX OC3 cards

CSCdx29539

dsppwd presents security problems; uses clear text format

CSCdx31537

dspcons shows invalid DSP Fl alarm on one end after comm. break

CSCdx42074

dle command causes watchdog timeout and switchcc

CSCdx44668

Lack of allotted space on dsptrkerr screen causes swerr 526 on IGX

CSCdx49193

CWM local/remote IBS reversed fro FRM-FRSM8 ATFST connection

CSCdx51587

upstats does not show Tx and Rx frames incrementing

CSCdx54453

Cannot upgrade from legacy BXM card to DX card when in y-red

CSCdx55308

Slow rerouting time in mixed pre and post 9.3.30 network, bad seq #

CSCdx66581

swlog 933 is logged when IP service port is changed with cnflan

CSCdx66901

Increase PVC LCN not rejected by remote even if no enough LCNs on rmt

CSCdx67113

Wrong parameter passed to send_pdu_to_ip() function from ilmi_hdlr

CSCdx67411

9082 logged with trunk communication failure on UXM

CSCdx72690

504& watchdog timeout cause 52 on IGX during overnight jobs

CSCdx78200

Cannot addloclp on a Frame Relay port if port number is not same as line number

CSCdx83934

Async EIA lead (cmi_lead_mon) upgrade issues when upgrading to 9230 and 93x

CSCdx83970

Card attribute for multi-VSI-partition, VSI ILMI & Topo Disc lost on 92->93

CSCdx83986

UXMs FW lcn resync card attr incorrectly initialized when upgrading from 9310

CSCdx84433

dspcd <slot> shows overlapped display.

CSCdy01237

Default Gateway IP address changes automatically

CSCdy03630

SWSW wrongly sends objects in bps format when tstber is executed.

CSCin03520

Soft loopback is not functioning in switchyred when aps is added on line


Anomalies Fixed in Release 9.3.40

Table 30 lists the anomalies that are fixed in Release 9.3.40.

Table 30 Anomalies Fixed in Release 9.3.40 

Bug ID
Description

CSCdk69912

UFM programming overrides VC_Q settings in non-standard parameters

CSCdm12850

The system idle time can be under-reported to VNS through SNMP

CSCdm60699

Async updates are sent incorrectly when VCQueue fills up

CSCdm75577

100% traffic discard at ATM end of a ATM-FR conn, added from FR side using CWM

CSCdp04164

DC Voltage Alarm - Need to increase upper alarming limit

CSCdr26161

Resetcd h of UXM during burnfwrev leaves card in burnfw state

CSCdr34820

More than 2 connections appear on single channel of DSP

CSCdr43327

If BME card is present we cannot use 0 option to burn firmware

CSCdr64816

VoiceEndptStatus returns offHook for all channels

CSCdr76559

A-bit on NNI ports doesnt clear when LMI removed and added

CSCds03159

BCC4V logged Abort 1011 after reinserting active CC

CSCds10019

Add more information to chklm and dsplm help screen

CSCds10107

New Commands for testing Voice channels (tonegen, dsptone, clrtone, cnftone)

CSCds29404

Enable cell routing is not part of robust message

CSCds37220

after switchcc, dspapsln may show aps deactivated

CSCds66268

copycons does not generate warning message

CSCdt71711

Bad Node Nib error 419 in Flex Switchcc Test

CSCdt86650

RAS: Corporate login to dsptech as default screen

CSCdt88340

Do not allow the M/F switchapsln switch the APS line backward

CSCdt98231

Swerr 9098 logged after reinsert back card for VSI part deletion

CSCdu00161

Connection, Line and QBin interval statistic values displayed are incorrect

CSCdu21187

Temp a-bit failure caused by switchcc, even with feeder alert enabled

CSCdu26594

Remove the logging of 3064 when slave detects reduced number of cons

CSCdu34126

UXM trunk configs give incorrect value for selected cable length

CSCdu34853

vlcon shows wrong pref status after rrtcon reroute at master

CSCdu35011

Cannot configure E1 lines for unframed mode

CSCdu36770

Memory wrt: rr_bld_cbrt_path() overwritten next long of rrt_path/rrcb_path

CSCdu38022

CLI allows ECN threshold to be greater than VCQ for incomplete set of parms

CSCdu46642

IMA trunk not allocating correct no. of DS0s

CSCdu47810

Need SWSW option to configure UXM/BXM ILMI for number of PVC changes per trap

CSCdu49568

1M3 abort upon using addport

CSCdu50924

Reroute wait timer (CM parm 9) was applied to derouted conns

CSCdu53235

Swerr 2051 logged without the addition or deletion of statistics

CSCdu55802

dspfwrev screen shows incorrect information

CSCdu58349

snmpwalk shows sysUptime 497 days after initialization

CSCdu59473

Not able to add FR conns and config/change FR class

CSCdu65259

CLI for cnfsct name failures does not give adequate help

CSCdu70637

rrtinf inprog output is not usable for text screen captures

CSCdu73638

SNMP: cannot add/mod connection to FAIL IMA port with no ACTIVE line

CSCdu75132

Add controller IP to the dspctrlrs screen

CSCdu75709

Informix DB not updated when UFMU front and backcard replace FRM or vice versa

CSCdu77043

UXM IMA trunk fails when adding line to trunk

CSCdu79181

Code added in wrong place to enable VPI Address config on UXM trunks

CSCdu84969

rt-vbr value for atmPortQueueIndex on IGX is not consistent with BPX

CSCdu85702

UXM/BXM card mismatch during upgrades causes LOS

CSCdu88501

Swerr 925 for UVM inactive line when switchcc

CSCdu88771

Swerr 55 seen after ddcuse command is issued on non-BNI card

CSCdv00082

No appropriate value information help for cnfport command

CSCdv01544

rrtinf inprog displays NOTHING and can log 526 when trunk count is 7+

CSCdv02043

RAS: Expand standby mem self test to detect parity (1000001) errors

CSCdv02727

Not able to add 2nd VSI controller when 3 or more trks exist on a card

CSCdv03293

Incorrect display of local clock format for dspcurclk

CSCdv03346

switch.m interface atmEndptOeEfciQSize atmEndptEfciQSize inconsistent

CSCdv03428

Logical slot used with phycd_get_attr() in get_sonetiftable_int and get_shelfs

CSCdv04095

Physical slot pass in to get_line_fmt() which expect logical slot

CSCdv06569

RAS: Expand standby mem selftest to detect parity (1000001) errors- IGX change

CSCdv08233

High LAN traffic can lockup node UI and cause 3M, or 52 aborts

CSCdv08861

Flood of SWerr 9000 when adding voice con on CVM that do not support voice

CSCdv08902

Unique error literals needed for bkcdtype_get_name()

CSCdv09343

Code decompression error for IGX

CSCdv10468

addcon with insufficient UBUs causes 1m3 aborts on UVM

CSCdv12068

dspnds does not show all options (missing -q -x)

CSCdv12776

Misc. enhancements for Deferred conn alm gen feature

CSCdv12786

Total BW of VSI partitions on BXM card can exceed its backplane speed

CSCdv13914

Correct spelling of EPD in dspconcnf

CSCdv14343

AR 32K LCN limit and vsi cnf not handled correctly get_unreserved_chan_cnt

CSCdv15863

SNMP agent does not set XLMI default vpi.vci or atmPortMgmtProtoOnCard

CSCdv15924

RAS: enhance swerr info for vsi channel alloc failure

CSCdv16069

Line functions accept feeder trunks as input and can cause errors or aborts

CSCdv16980

Change dsptech login to always show dsptech, not just when no probe

CSCdv17884

Move cnfrrcpu command to connection help group

CSCdv18027

Problems with dsptech login mechanism

CSCdv19657

get_free_lcn must use a swerr code rather than failure return value for error

CSCdv19842

Add description for SET operations on ds3ClkSource/sonetIfClkSource

CSCdv21091

BNI Total cells rx stat requested twice in 0x56 msg affects def. con alm gen

CSCdv22642

PROJ: CLI cleanup - Remove obsolete fields/commands

CSCdv24166

F4-F5 mapping enabled even when no available channels on the card

CSCdv24220

ddcuse has wrong code and is probably an obsolete command

CSCdv24530

Reducing IMA retained lnks should be blocked if Max BW becomes < Req. BW>

CSCdv24685

Hot standby mismatch causing loss of O.151 OAM and XLMI support on active card

CSCdv25544

dspcd does not show mismatch information for X-LMI feature mismatch

CSCdv26618

dtrkcnfg needs to show if trunk active or not

CSCdv27309

Adding a new prefer path should cancel the reroute timer

CSCdv27346

Swerr 9082 logged on performing tstconseg or tstpingoam

CSCdv29727

9083 when trunks statistical reserve is set to the trunks line rate

CSCdv30106

Stats missing from TX Clp x DSCD

CSCdv30438

BPX: switchyred on BXMs causes AXIS NWIP to go unreachable via CWM

CSCdv31539

ILMI Neighbor Discovery mismatch cleanup should not cleanup XLMI information

CSCdv31936

Fail to add Master VP-Tunneling connection on IGX/UXM

CSCdv34258

Graceful upgrade from a pre 9.2.35 release does not map post 9.2.35 parms

CSCdv34759

Enhance dspconcnts to display connection endpoints terminated on cards, trunks

CSCdv35146

2 min data hit after switchyred when 2ndary card still programming channels

CSCdv35295

CiscoView shows Active and green color for FAILED UFM ports in IGX

CSCdv36176

VT does not indicate that we are logged into a Standby Controller card

CSCdv37628

Polling type toggled to 2 and back to 1 during switchcc

CSCdv38469

tstber fails on BXM if VSI enabled with VPI = 0 or 1

CSCdv38587

Local and remote loopback on individual IMA links fail to loop traffic

CSCdv40684

dsplmistats, does not display the status of protocol, also no Node Status Cntr

CSCdv42399

Not able to add aps line after deleting

CSCdv42531

dspctrlrs always shows default ip address 192.0.0.0 of MPLS VSI controller

CSCdv43983

Switchyred job does not work when VSI is active on BXM

CSCdv44412

Cannot configure stat level on standby card of y-red pair

CSCdv44928

upport on UFMU card does not enforce 24M oversubscription limit

CSCdv45621

[dspprfh] indicates <active> even if invoked from the standby cc

CSCdv48264

Inactive Port Alarm Config is defaulted to ENABLED upon port activation

CSCdv51156

9340REGR: Swerr 9082, and node unreachable after upgrade

CSCdv55045

dspselftst shows CBUS Not Run

CSCdv55322

Usage info for dspviacons not updated

CSCdv55819

Enhancement to display load units on user ports

CSCdv55862

PROJ: Add SNMP Support for IGX/BPX Alarm Masking

CSCdv57337

addjob/cnfport aborts (1m3) when the command times out

CSCdv58342

dspcd screen overflows for BXM-E card supp. Trk VC Shaping

CSCdv58824

Y-red: logical slot does not sync up SR2048 attribute in add/del yred

CSCdv58954

dsplogcd shows UFM port active but dspports shows failed

CSCdv59751

dsptrkutl on a feeder trunk doesnt showing any feeder connections

CSCdv59831

dspchoid displays UXM for URM Cards

CSCdv62358

Cannot clear tstpingip counters

CSCdv63422

atmcls for UBR connections does not work

CSCdv67269

Extend Cline Robust Message to include some more useful fields

CSCdv68534

Bkcd insert and yred alarm messages are logged during a switchcc

CSCdv68775

Invalid CBA array access corrupts SVC Hash Table protection pad

CSCdv69165

BXM mismatch after the stats level changed and BCC rebuild

CSCdv69576

RAS: Reprogram LMI & IP SAR connections on moving protocol & switchyred

CSCdv69717

Incr CDV & F4/F5 AIS Dect values reset to defaults after upgrade or switchcc

CSCdv70413

X-LMI port comm fail causes remote end cons in alarms after switchcc/rbld

CSCdv70803

Observing SWERR 1128 during degrade mode testing

CSCdv70946

PROJ: VC Merge on UXM - Project Checking

CSCdv71074

Swerr 45/3010 upon depletion of card lcns

CSCdv71138

Swerr 9082 logged on switchyred

CSCdv74130

New default power voltage threshold

CSCdv75008

Adding a con when feeder is in comm fail causes alarms when defr con is active

CSCdv75658

Code defects caused due to latest merge into 9340 baseline

CSCdv76026

Wrong check in cnftrk for DTR toggling feature

CSCdv76336

Rate values for Txvcdscd are different from other rate values

CSCdv76903

Card failed when bringing up 2048kbps NTM-SR trunk, HW errs logged

CSCdv77061

X-LMI port comm fail should condition the remote end connections

CSCdv78268

cnftrkparm on NTS Queue Depth Rejected with Unrelated Range Check

CSCdv78474

PROJ: 9.3.40 Unidirectional FCES and Policing

CSCdv78530

Deferred conn alm gen feature doesnot work when LMI protocol runs on the card

CSCdv78776

dsptrkutl: dsptrkutl is blocked after full rebuild and not recovered

CSCdv81030

CLI dspcurclk on BPX node causes sw err. 532, 26, 539

CSCdv81068

Re-numbering BPX node causes 254

CSCdv81287

Prefix warning: Analyze uninitialized variable usage in Pis_fw_req_valid()

CSCdv83923

Default configuration for BXM port and feeder trunks should be NO-SHIFT

CSCdv84329

Prefix: Uninitialized fields in MSG_LETTER in abort_ldiag()

CSCdv85306

PROJ: CLI Cleanup - Remove the obsolete Adaptive Voice from display and cmd

CSCdv87061

Send correct field scrm_payload for payload scramble in Cline Object Msg

CSCdv87642

VT Oversubscription chkin

CSCdv88708

Swerr 45 on switchcc - VSI related

CSCdv90733

Relaxed lmi (dsplmistats) reports wrong info on a los

CSCdv90966

Swerr 384 during F4-F5 config. validation

CSCdv91284

Swerr 1013 on fallback

CSCdw00642

Null Timer Calculation Should Not Be HUGE_DELAY

CSCdw01517

SNMP Set/Get operations incomplete on NTM-SR trunks

CSCdw07452

31 voice channels are send to cwm for CVM T1 card

CSCdw08309

Command cnfchrps is not listed in alphabetical order in help screen

CSCdw10635

ARP message pointer used before initialized, possible SNMP 1M3 abort

CSCdw10654

Prefix errors in 9.3.40 igx baseline

CSCdw11748

Trunk VC shaping does not work properly on BPX fdr trk

CSCdw11872

Potential clocksrc table memory corruption

CSCdw12925

dspcd screen display is difficult to read due to merged strings

CSCdw15039

Command addloclp loops both ends for DAX connections; which is incorrect

CSCdw15054

Allow addlocrmtlp command for DAX connections

CSCdw15064

CBUS message send to BXM for addloclp needs to be corrected

CSCdw15075

addloclp command should not be allowed on connection endpoints on ASI port

CSCdw16041

cnfbusbw does not work in a job

CSCdw16076

Diff. path delays configured for master & slave end points of a connection

CSCdw16364

Swerr 45 and cannot uptrk on a 60K LCN BXM-E card

CSCdw16899

SNMP set/get not working for ds3LineLclLpbk and sonetLineLclLpbk

CSCdw19247

Via/slave node lock up routing

CSCdw19941

Swerr 9093 when configure T3 trunk line framing to be HEC

CSCdw22629

Uninitialized var used for LCON update in int_via_updt

CSCdw23663

cnfnodeparm (job lock timeouts) wrong init value between 9.1 and 9.2

CSCdw26065

Modify the command names to cnfintalm and dspintalmcnf to reflect the age

CSCdw27395

Cannot ADDTRK after changing CNFTRK NTM-SR trk from 2048kbps to lower value

CSCdw29721

Prefix: in syntax mode, cnfpref does not init hops

CSCdw30934

Deferred conn alm gen may/may not get deactivated upon full rebuild

CSCdw32389

dspqbinstats and dspcntrstats can show negative values

CSCdw32729

Improve runrev to detect unsafe standby updates

CSCdw32857

Enabling IMA on single T1 uses extra DS0

CSCdw34453

dsptrkstats/clrtrkstats on down BNI card produces SW log 8096

CSCdw34723

CNFTRK does not work in JOB mode

CSCdw39995

APS act line is not sync between SWSW and FW after BCC switch

CSCdw40453

RAS: Improve dsptech and dlcon to list the number of dax cons on the node

CSCdw43792

UAS stats not collected when line in alarm, caused by CSCdk44173 fix

CSCdw45129

Changing the min tx rate at one end of the VT causes 9093 at other end

CSCdw46236

VC Shaping should use VI Max TX rate to work with VT oversubscription feature

CSCdw48298

Can burn CVM firmware onto UVM & vice versa

CSCdw48570

Cannot add a job trigger to a virtual trunk on a BPX

CSCdw49673

Allow VC Shaping on UXM feeder trunks when IGX is a feeder node

CSCdw50142

Max Tx rate rounding off error on added trunks

CSCdw51173

Need to document rt-VBR index in atmPortQueueIndex

CSCdw52505

VC Shaping (WFQ) is incorrectly applied to timestamped traffic

CSCdw53935

Use of connection max delay values are inconsistent

CSCdw54838

on off bits changed on one node after bpx sw upgrade

CSCdw55273

Redundant calls to clear mismatch

CSCdw55317

Slot alarms are not generated for Monarch Specific card errors

CSCdw58091

CPU usage is message is not logging after graceful upgrade and switchcc

CSCdw58129

BXM went into mismatch after swsw upgrade

CSCdw58704

Free allocated memory errors logged by SNMP process—swerr 502 589 504

CSCdw59553

dspcd screen shows pcr instead of PCR

CSCdw63725

Connection requires 11 hops to route fail to report as failure & CPU idle low

CSCdw64831

Heading for VT Oversubscribe feature appears for physical trunks in dsptrkutl CLI

CSCdw66301

swlog error 50 observed

CSCdw68727

Abort 1000003 logged on BPX after executing dsptrkutl following rebuild

CSCdw68912

dcct LCN information overwritten for DAX connections

CSCdw71520

Help for ip commands causes last line overflow for nwipcache entry

CSCdw71912

dsptrkutl shows non-existent connections

CSCdw74281

addlnlocrmtlp on IGX/AF side of trunk causes comm-fail should be Clear-OK

CSCdw75500

swerr 5050 generated upon cba_verify after deleting vp-tunneling daxcon

CSCdw75730

cnfasm change to temp threshold doesnt reflect in dsppwr screen

CSCdw79108

BPX node with SWSW 9.1.24 does not sync up with CWM

CSCdw80264

10 hop cons fail to route when resources available

CSCdw84340

dsputl command does not work for UVM/CVM connections

CSCdw86061

rs_get_vpivci() does not correctly check for LMI/ILMI VCI

CSCdw86065

CNFRSRC will not allow VPI over 255 although port NNI

CSCdw88571

Incorrect feeder trunk channel programming for dax-cons

CSCdw92030

Port speeds above 6144 Kbps on UFMU-HSSI are reported incorrectly to CWM

CSCdw94435

dclk output does not get updated

CSCdw95202

SNMP support for Trunk VC Shaping and cnftrkq enhancement for feeders

CSCdx06654

Line/trk recovered even the active APS line has LOS

CSCdx07451

AutoRoute channels allocated beyond 32768 when VSI Slave channels used on card

CSCdx08325

Unable to add connection from FR end point to ATM feeder end point

CSCdx08838

IGX reports PRI Loss (CLOCK) when deleting line clock source

CSCdx10239

Memory leak in dsptech (swerr 501, 3000000)

CSCdx10874

Enabling LMI on VSI feeder causes unreachable (always) + comm-fail(9340)

CSCdx16103

Trunk channel programming rejected(9082) when connection has PCR > port rate

CSCdx17275

UXM line looped back after sw upgrade

CSCdx17933

Dangling VLCONs and inconsistent trunk loading/conid

CSCdx18387

dsplns/dspports alarm masking reverse video is not captured on ASCII screen

CSCdx19254

Swerror 521 on bpx node in upgrades network

CSCdx20304

addfrcons and dspfrchan no longer exist

CSCdx20323

752 logged when FW upgraded

CSCdx27972

RAS: Incorrect Open space calculation when inconsistent conids exist

CSCdx29500

BPX clock does not go to Tracking mode if current clock source is on port 1

CSCdx36217

Connection continuously re-routes after active CC fails with swerr 47

CSCdx38407

dspviacons causes session to lockup, IDLE time of 0 and eventually 1m3 abort

CSCdx47173

Incorrect display of IGX FDR NPMs after an upgd

CSCdx57483

Removed ASM card on a BPX cage displayed as Empty Reserved for BCC

CSCdx57872

FRM port alarms are *disabled* by default on upgrade

CSCdx58152

addlnloclp/addlnlocrmtlp does not work when secondary UXM-IMA-YRED active

CSCdx63511

Download Aborted logged and UXM to failed status when burnfwrev to A

CSCin10198

CSCdu85702 fix missing from BPX


Anomaly Status Changes from Previous Releases

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

Table 31 Anomaly Status Changes From Previous Releases 

Bug ID
Status

CSCdr43758

Unreproducible

CSCdv38347

Duplicate of CSCdx88946

CSCdv84853

Junked

CSCdv89240

Closed

CSCdw00459

Closed

CSCdw01957

Unreproducible

CSCdw15697

Duplicate of CSCdu46642

CSCdw21820

Closed

CSCdw35336

Duplicate of CSCdx17933

CSCdw50328

Duplicate of CSCdu00161

CSCdw52771

Duplicate of CSCdx90569

CSCdw58175

Closed

CSCdw66534

Unreproducible

CSCdw68758

Duplicate of CSCin12498

CSCdw94163

Unreproducible

CSCdx11280

Unreproducible

CSCdx48633

Duplicate of CSCdx58152

CSCdx55926

Unreproducible

CSCdx66732

Duplicate of CSCdx66901

CSCdx67460

Duplicate of CSCdx54453

CSCin10654

Junked


Additional Deliverables

SNMP MIB

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

Switch MIB Changes in Release 9.3.53

No MIB changes in Release 9.3.53.

Switch MIB Changes in Release 9.3.51

This section contains the MIB changes in Release 9.3.51.

atmEndptMCR

The description field for this object has been modified to add the following line (refer to CSCeb41930):

For ATFST connections, the minimum value supported is 7.

atmEndptTestType

The description field for this object has been modified to add the following line (refer to CSCin34914):

On IGX an SNMP get always returns write-only (2) for this object.

sonetStatsHcsCrtblErr

This object in SonetStatsEntry was referenced as HCS correctable errors errored seconds, sonetStatsHcsCrtblErrES, instead of the HCS correctable errors, sonetStatsHcsCrtblErr. Description has been updated (refer to CSCef08257).

Switch MIB Changes in Release 9.3.47

This section contains the MIB changes in Release 9.3.47

atmEndptOeIBS

The description of the IBS in atmEndptEntry, for local and remote endpoints, has been modified to reflect the differences in ATFR and non-ATFR connections (refer to CSCin21585).

Default: The range differs for ATFR and ATFST connections.

0 for atfst

1 for atfr

Range:

ATFR = 1-255

ATFST = 0-24000

sonetIfFrame

This object in sonetIfEntry has been modified to include enumerations for OC-12 frames. The following two enumerations have been added (refer to CSCin32081):

sonetSTS-12C (4)

sonetSTM-4 (5)

Switch MIB Changes in Release 9.3.40

For the MIB addition and description of changes in this release, see "New Features in Release 9.3.40" section.

Switch MIB Changes in Release 9.3.35

This section contains the MIB changes in Release 9.3.35.

voiceEndptState

New object

winkUndetermined(6)

Switch MIB Changes in Release 9.3.30

This section contains the switch MIB changes that have been introduced since Release 9.3.30. The changes include modified objects and new objects.

atmEndptTable

Modified objects

atmEndptEntry
atmEndptTestType 

New objects

atmEndPtOAMTestLpCnt 
atmEndptOAMTestAbrtFlg 
atmEndptOAMTestSccCnt 
atmEndptOAMTestRTDMin 
atmEndptOAMTestRTDAvg 
atmEndptOAMTestRTDMax 
atmEndptOAMTestOamFmt

sonetIfTable

Modified objects

sonetIfFrame

atmTrunks

Modified

atmTrkVcShaping

ShelfRtrSlotInfoTable

New objects

shelfRtrSlotInfoEntry
rtrState
rtrIOSAlmStatus
rtrIOSSwImage
rtrVICType
rtrCnfFilename
rtrCnfFilesize
rtrIOSCnf
rtrSerialPort

Switch MIB Changes in Release 9.3.11, 9.3.20, and 9.3.24

No MIB changes are contained in these releases.

Switch MIB Changes in Release 9.3.10

This section contains the switch MIB changes that have been introduced since Release 9.3.10. The changes include obsolete objects, modified objects, and new objects.

switchIfTable

Modified objects

switchIfPartiId		
switchIfScTmpltId

frLportCnfTable

Modified objects

frLportCnfEntry

New objects

frLportNeighborDiscovery
frLportNeighborIpAddress
frLportNeighborIfIndex

atmPortTable

Modified objects

atmPortEntry
atmPortType

New objects

atmPortNeighborDiscovery
atmPortNeighborIpAddress
atmPortNeighborIfNam

atmPortStatTable

Modified objects

atmPortStatEntry

New objects

atmPortStatTxQ0CellDrps
atmPortStatTxQ1CellDrps
atmPortStatTxQ2CellDrps
atmPortStatTxQ3CellDrps
atmPortStatTxQ7CellDrps
atmPortStatTxQ8CellDrps
atmPortStatTxQ9CellDrps
atmPortStatTxQ10CellDrps
atmPortStatTxQ11CellDrps
atmPortStatTxQ12CellDrps
atmPortStatTxQ13CellDrps
atmPortStatTxQ14CellDrps
atmPortStatTxQ15CellDrps

atmEndptTable

Modified objects

atmEndptQIR
atmEndptOeQIR
atmEndptRateUpICA
atmEndptPCR
atmEndptOePCR
atmEndptSCR
atmEndptOeSCR
atmEndptMCR
atmEndptOeMCR

atmTrunkStatsTable

Modified objects

atmTrkStatsEntry

New objects

atmTrkStatsTxQ10CellDrps
atmTrkStatsTxQ11CellDrps
atmTrkStatsTxQ12CellDrps
atmTrkStatsTxQ13CellDrps
atmTrkStatsTxQ14CellDrps
atmTrkStatsTxQ15CellDrps

rsrcPartiTable

Modified objects

rsrcPartiId
rsrcPartiPvcMaxBw
rsrcPartiVsiVpiStart
rsrcPartiVsiVpiEnd
rsrcPartiVsiMinBw
rsrcPartiVsiIlmiEnable
rsrcPartiVsiLcnReprogPermit

rsrcPartiPvcTable

Modified objects

rsrcPartiPvcPvcMaxLcns 
rsrcPartiPvcPvcMaxBw 
rsrcPartiPvcVpiStart1 
rsrcPartiPvcVpiEnd1 
rsrcPartiPvcVpiStart2 
rsrcPartiPvcVpiEnd2 
rsrcPartiPvcVpiStart3 
rsrcPartiPvcVpiEnd3 
rsrcPartiPvcVpiStart4 
rsrcPartiPvcVpiEnd4

atmQbinTable

Modified objects

atmQbinMinBw
atmQbinTmpltCnfg

vsiCtrlrTable

Modified objects

VsiCtrlrEntry
vsiCtrlrPartiId
vsiCtrlrSlot
vsiCtrlrPort

New objects

vsiCtrlrAdminStatus
vsiCtrlrVpi
vsiCtrlrVciStart

Switch MIB Changes in Release 9.3.05

This section contains the switch MIBs that have been introduced since Release 9.3.05.

atmPortTable

New objects

atmPortIlmiResetFlag
atmPortCACReserve
atmPortLportMaxBW
atmPortLportMinVpi
atmPortLportMaxVpi
atmPortMgmtProtoOnCard

Modified objects

atmPortEntry
atmPortMgmtProto
atmPortIlmiAddrReg
atmPortVcShaping

atmPortQueueTable

New objects

atmPortQueueVcShaping

Modified objects

atmPortQueueEntry
atmPortQueueDepth

atmEndptTable

Modified objects

atmEndptVcQSize

switchShelf configuration branch

New objects

shelfCnfgNodeVcSupport
shelfCnfgNodeVcTotal

atmTrunks table

New objects

atmTrkTermUsedPvc
atmTrkViaUsedPvc
atmTrkMgmtProtoOnCard

Modified objects

atmTrkEntry

rsrcPartiTable

New objects

rsrcPartiVsiLcnReprogPermit

Modified objects

rsrcPartiEntry

Obsolete objects

rsrcPartiPvcMaxLcns
rsrcPartiPvcMaxBw 

The following object limits the number of LCNs to be reprogrammed in a continuous loop, so the other software processes get the correct amount of CPU time.

rsrcPartiMaxLcnBatchNumber

rsrcPartiPvcTable

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

New objects

rsrcPartiPvcEntry
rsrcPartiPvcPvcMaxLcns
rsrcPartiPvcPvcMaxBw
rsrcPartiPvcVpiStart1
rsrcPartiPvcVpiEnd1
rsrcPartiPvcVpiStart2
rsrcPartiPvcVpiEnd2
rsrcPartiPvcVpiStart3
rsrcPartiPvcVpiEnd3
rsrcPartiPvcVpiStart4
rsrcPartiPvcVpiEnd4

serialPortTable

Modified objects

serialPortLeadState

Switch MIB changes to Release 9.3.00

This section contains the switch MIB changes that have been introduced after Release 9.2.31. The changes include obsolete objects, modified objects, and new objects.

switchIfTable

This table contains a list of ports and sub-ports and their interfaces.

Modified objects

switchIfService
switchIfPhysPort
switchIfScTmpltId

atmPortTable

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

New objects

The following new MIB variables support IMA Ports:

atmPortRetainedLinks
atmPortImaProtocolOption
atmPortImaDiffDelay
atmPortImaClockMode

Modified objects

atmPortEntry

Obsolete objects

atmPortSvcChannels
atmPortSvcLcnLow
atmPortSvcLcnHigh
atmPortSvcVpiLow
atmPortSvcVpiHigh
atmPortSvcVciLow
atmPortSvcVciHigh
atmPortSvcQbinBitMap
atmPortSvcQbinSz
atmPortSvcBw
atmPortSvcInUse
atmPortPvcInUse

atmEndptTable

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

Modified objects

atmEndptPolicing

shelfSlotInfoTable

This table provides switch slot information.

New objects

slotCardTopAssemNumber

Modified objects

shelfSlotInfoEntry
slotCardMinBusUBU

ds3LineTable

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

Modified objects

ds3LineAlmType
ds3LineStatsTable 

ds3StatsTable

This table provides a list of DS3 line statistics objects.

New objects

ds3StatsUas

Modified objects

ds3LineStatsEntry

sonetStatsTable

This table provides a list of SONET line statistics objects.

Modified objects

sonetStatsPthBip8s
sonetStatsPthFebeEs
sonetStatsSecBip8Ses
sonetStatsPthUas
sonetStatsPthFarendUas

atmTrunkStatsTable

This table provides a list of ATM trunk statistics objects.

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

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

Cisco BPX 8600 Nodes

node TN    Cisco           BPX 8620  9.3.53   Mar. 2 2006 16:31 GMT 
	System-Wide Parameters
1  Max Time Stamped Packet Age (msec) ................................   32
2  Allow CPU Starvation of Fail Handler ..............................   No
7  Max Network Queuing Delay for HDM/LDM NTS Data connections (msec)..   32
9  Max Network Queuing Delay for CVM/UVM VAD connections (msec).......   64
11 Max Network Queuing Delay for CVM/UVM non-VAD connections (msec)...   64
13 Enable Discard Eligibility.........................................   No
14 Use Frame Relay Standard Parameters Bc and Be......................   No
22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm..    0
23 Enable Connection Deroute Delay feature............................   No
24 Interval Statistics polling rate for ATM VCs.......................    5
25 Interval Statistics polling rate for ports on IGX nodes............    5
26 Max Num of Nodes doing Simultaneous TFTP Configuration Save/Restore    4


This Command: cnfsysparm


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:33 GMT 

1  Update Initial Delay   [ 5000] (D)   16 Stats Memory (x 100KB) [  132] (D)   
2  Update Per-Node Delay  [30000] (D)   17 Standby Update Timer   [   10] (D)   
3  Comm-Break Test Delay  [30000] (D)   18 Stby Updts Per Pass    [  150] (D)   
4  Comm-Break Test Offset [   10] (D)   19 BusFail Monitor Window [   12] (D)   
5  Network Timeout Period [ 1700] (D)   20 BusFail PollErr Thrhld [    0] (D) 
6  Network Inter-p Period [ 4000] (D)   21 Comm Fail Delay        [   60] (D)   
7  NW Sliding Window Size [    1] (D)   22 Nw Hdlr Timer (msec)   [   50] (D)   
8  Num Normal Timeouts    [    7] (D)   23 SAR CC Transmit Rate   [  560] (D)   
9  Num Inter-p Timeouts   [    3] (D)   24 SAR High Transmit Rate [  280] (D)   
10 Num Satellite Timeouts [    6] (D)   25 SAR Low Transmit Rate  [   56] (D)   
11 Num Blind Timeouts     [    4] (D)   26 SAR VRAM Cngestn Limit [ 7680] (D)   
12 Num CB Msg Timeouts    [    5] (D)   27 SAR VRAM Cell Discard  [  256] (D)   
13 Comm Fail Interval     [10000] (D)   28 ASM Card Cnfged        [    Y] (Y/N)
14 Comm Fail Multiplier   [    3] (D)   29 TFTP Grant Delay (sec) [    1] (D)   
15 CC Redundancy Cnfged   [    Y] (Y/N) 30 TFTP ACK Timeout (sec) [   10] (D)   
31 TFTP Write Retries     [    3] (D)   46 Max Htls Rebuild Count [  100] (D)   
32 SNMP Event logging     [    Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D)   
33 Job Lock Timeout       [   60] (D)   48 Send Abit early        [    N] (Y/N)
34 Max Via LCONs          [50000] (D)   49 Abit Tmr Multiplier  M [    0] (D)   
35 Max Blind Segment Size [ 3570] (D)   50 Abit Tmr Granularity N [    3] (D)   
36 Max XmtMemBlks per NIB [ 3000] (D)   51 FBTC with PPDPolicing  [    N] (Y/N)
37 Max Mem on Stby Q (%)  [   33] (D)   52 CommBrk Hop Weight     [   25] (D)   
38 Stat Config Proc Cnt   [ 1000] (D)   53 CB Fail Penalty Hops   [    2] (D)   
39 Stat Config Proc Delay [ 2000] (D)   54 Auto BXM upgrade       [    Y] (Y/N)
40 Enable Degraded Mode   [    Y] (Y/N) 55 LCN reprgrm batch cnt  [  100] (D)   
41 Trk Cell Rtng Restrict [    Y] (Y/N) 56 Dnld LanIP or NwIP     [  Nw](Lan/Nw)
42 Enable Feeder Alert    [    N] (Y/N) 57 IP Relay gateway node  [    0] (D)   
43 Reroute on Comm Fail   [    N] (Y/N) 58 Max LAN Window (sec)   [   60] (D)   
44 Auto Switch on Degrade [    Y] (Y/N) 59 Max LAN Packets/Window [18000] (D)   
45 Max Degraded Aborts    [  100] (D)   60 Extended Cline Object  [    N] (Y/N)
This Command: cnfnodeparm

node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:35 GMT 

Index Status    Function

1     Enabled   Automatic TRK Loopback Test on Local/Remote Alarms
2     Enabled   User Command Logging
3     Enabled   Automatic Card Reset on Hardware Error
4     Enabled   Card Error Record Wraparound
5     Disabled  Card Test After Failure
6     Disabled  Download From Remote Cisco StrataView Plus
7     Disabled  Logging of conn events in local event log
8     Disabled  Logging of conn events in Cisco StrataView Plus  event log
9     Disabled  Force Download From a Specific IP address


This Command: cnffunc 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:36 GMT 

Index Status    Function

1     Disabled  Configuration Save/Restore
2     Enabled   ForeSight
3     Disabled  Multiple VTs (1 session enabled)
4     Disabled  Virtual Trunks
5     Enabled   ABR standard with VSVD
6     Disabled  Priority Bumping
7     Disabled  Virtual Ports


This Command: cnfswfunc 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:37 GMT 

Card    Test   - - - - - - Self Test - - - - - - -   - - Background Test - - -
Type    Freq   Enable        Inc   Thresh  Timeout   Enable        Inc   Thresh
----    -----  --------  -------  -------  -------   --------  -------  -------
BCC      1600  Enabled       100      300      800   N/A           100      300
ASM       300  Disabled      100      300       60   N/A           100      300
BNI-T3    300  Enabled       100      300      150   N/A           100      300
BNI-E3    300  Enabled       100      300      150   N/A           100      300
ASI-E3    900  Enabled       100      300      800   Enabled       100      300
ASI-T3    900  Enabled       100      300      800   Enabled       100      300
ASI-155   900  Enabled       100      300      800   Enabled       100      300
BNI-155   300  Enabled       100      300      150   N/A           100      300
BXM      4000  Enabled       100      300     3000   Enabled       100      300


This Command: cnftstparm 

node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:39 GMT 

8  Maximum Routing Bundle    [   90] (D)   
9  Reroute Timer             [    3] (secs)   
10 Reset Timer on Line Fail  [  Yes]
11 Max Down/Up Per Pass      [   50] (D)   
12 Down/Up Timer             [30000] (msecs)   
13 Max Route Errs per cycle  [   50] (D)   
14 Time between Rrt cycles   [    5] (mins)   
15 Max. Rrt Err cycles       [   10] (D)   
16 Routing pause timer       [    0] (msecs)   
17 Max msgs sent per update  [   10] (D)   
18 Send SVC urgent msg       [   No]
19 Max SVC Retry             [    0] (D)   
20 Wait for TBL Updates      [   70] (100 msecs)
21 Max Derouting Bndl (0=all)[  500] (D)   
22 Enable Cost-Based Routing [   No] 
23 Enable Route Cache Usage  [   No]
24 Use Delay for Routing     [   No]
25 # of reroute groups used  [   50] (D)   
26 Starting size of RR grps  [    0] (CLU)
27 Increment between RR grps [  100] (CLU)
28 CM updates app timeout    [    5] (10 secs)
29 Route concurrency level   [    1] (D)   


This Command: cnfcmparm 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:41 GMT 

1  Rmt Blk Freq (msec)     [    100]    16 FW Dnld Msgs/Block(dec) [      4]    
2  Rmt Blk Size (hex)      [    400]    17 Flash Write TO(msec)    [  16000]    
3  Lcl Blk Freq (msec)     [    100]    18 Flash Erase TO(msec)    [    100]    
4  Lcl Blk Size (hex)      [    400]    19 Erase Verify TO(msec)   [  16000]    
5  Image Req Freq (msec)   [  10000]    20 Standby Flash TO(sec)   [    300]    
6  Dnld Req Freq (msec)    [  10000]    21 Lcl Flash Init TO(msec) [   1000]    
7  Session Timeout (msec)  [  30000]    22 Flsh Write Blk Sz (hex) [  10000]    
8  Request Hop Limit (dec) [      1]    23 Flsh Verfy Blk Sz (hex) [    400]    
9  Crc Throttle Freq (dec) [   5000]    24 Chips Per Write/Erase   [      1]    
10 Crc Block Size (hex)    [    400]    
11 Rev Change Wait(dec)    [      0]    
12 CCs Switch Wait(dec)    [   1000]    
13 Lcl Response TO(msec)   [   5000]    
14 Rmt Response TO(msec)   [  20000]    
15 FW Dnld Block TO(msec)  [     50]    


This Command: cnfdlparm 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:42 GMT 

1. Logout Time ........... 20 minutes
2. VT Logout Time ........ 4 minutes
3. Prompt Time ........... 60 seconds
4. Command Time .......... 3 minutes
5. UID Privilege Level ... 6
6. Input Character Echo .. Enabled
7. Screen Update Time .... 10 seconds


This Command: cnfuiparm 

node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:42 GMT 

1  Priority Bumping Enabled                [  NO]
2  Priority Bumping Bundle                 [  50] (D)     
3  Priority Bumping Bands:                               
   Band 1                                  [   2] (D)     
   Band 2                                  [   4] (D)     
   Band 3                                  [   6] (D)     
   Band 4                                  [   8] (D)     
   Band 5                                  [  10] (D)     
   Band 6                                  [  12] (D)     
   Band 7                                  [  14] (D)     


This Command: cnfbmpparm 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:44 GMT 

Function            Number   Status      Function            Number   Status
Background Upcard     1      Enabled     Conn Stat Sampling    15     Enabled
Background Updates    2      Disabled    Neighbor Update Errs  16     Disabled
Standby Terminal      3      Enabled
Memory Protection     4      Enabled
Comm Break            5      Enabled
Comm Fail Test        6      Enabled
CRC Test              7      Enabled
Bus Fail Detection    8      Enabled
Line Diag             9      Enabled
Clock Restoral        10     Enabled
Cm_Rerouting          11     Enabled
Clock Routing         12     Enabled
Dynamic BW Allocation 13     Enabled
Modem Polling         14     Enabled

This Command: on1 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:13 GMT 

Function            Number   Status      Function            Number   Status
Line Stat Sampling    1      Enabled     Robust Alarm Updates  15     Enabled
Statistical Alarm     2      Enabled     Realtime Counters     16     Enabled
Job Ready Checker     3      Enabled     LAN Interface         17     Enabled
Configuration Backup  4      Enabled     Update Standby Stats  18     Enabled
Standby Update        5      Enabled     Telnet Access         19     Enabled
Downloader            6      Enabled     Junction ID           20     Enabled
Cm Updates            7      Enabled     Mult SV+/Routing Node 21     Disabled
Topo/Stat Updates     8      Enabled     Simulated Fdr Trks    22     Disabled
Card Statistical Alms 9      Enabled     Deroute Delay         23     Enabled
Card Stat Sampling    10     Enabled     Auto Renum Fail Recov 24     Enabled
Address Validation    11     Enabled     Card Simulation Tool  25     Disabled
ASM Stats Polling     12     Enabled
Port Stat Sampling    13     Enabled
Robust Updates        14     Enabled

Last Command: on2 


node TN    Cisco           BPX 8620 9.3.53   Mar. 2 2006 16:44 GMT

Function            Number   Status
Trace Msg Sent        1      Disabled
Multi-DB Stby Updates 2      Enabled
Trace Conv Msg        3      Disabled
Region memory init    4      Disabled
VT Clk Switch Evt Log 5      Disabled
Load Bal on Eqcost Rt 6      Disabled
Htls Rbld on SAR Fail 7      Enabled
Stat Poll on SNMP Get 8      Disabled

This Command: on3 

BNI-T3

node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 10:57 GMT 

TRK  3.2 Config     T3      [96000 cps]   BNI-T3 slot:   3                      
Transmit Rate:         96000              VPC Conns disabled:    --             
Protocol By The Card:  --                 Line framing:          PLCP           
Hdr Type NNI:          --                      coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:                      
Connection Channels:   1771                          length:     0-225 ft.      
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      No             
F4 AIS Detection:      --                 Frame Scramble:        --             
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 3.2


node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 10:57 GMT 

TRK 3.2 Parameters
 1 Q Depth - rt-VBR    [  242] (Dec)    15 Q Depth   - CBR     [  600] (Dec)
 2 Q Depth - Non-TS    [  360] (Dec)    16 Q Depth   - nrt-VBR [ 1000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [ 8878] (Dec)
 4 Q Depth - BData A   [ 1000] (Dec)    18 Low  CLP  - CBR     [ 100] (%)
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [ 100] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [ 100] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [ 100] (%)
 8 Red Alm - I/O (Dec) [  2500 /  15000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  15000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  30] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)

This Command: cnftrkparm 3.2 

BNI-E3

node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:01 GMT 

TRK 10.2 Config     E3      [80000 cps]   BNI-E3 slot:   10                     
Transmit Rate:         80000              VPC Conns disabled:    --             
Protocol By The Card:  --                 Line framing:          --             
Hdr Type NNI:          --                      coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:                      
Connection Channels:   1771                          length:     0-225 ft.      
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      Yes            
F4 AIS Detection:      --                 Frame Scramble:        --             
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 10.2


node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:02 GMT 

TRK 10.2 Parameters
 1 Q Depth - rt-VBR    [  202] (Dec)    15 Q Depth   - CBR     [  600] (Dec)
 2 Q Depth - Non-TS    [  300] (Dec)    16 Q Depth   - nrt-VBR [ 1000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [ 8978] (Dec)
 4 Q Depth - BData A   [ 1000] (Dec)    18 Low  CLP  - CBR     [ 100] (%)
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [ 100] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [ 100] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [ 100] (%)
 8 Red Alm - I/O (Dec) [  2500 /  15000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  15000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  30] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 10.2 

BNI-155/155E

node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:03 GMT 

TRK 11.1 Config     OC3     [353207cps]   BNI-155 slot:  11                     
Transmit Rate:         353208             VPC Conns disabled:    --             
Protocol By The Card:  --                 Line framing:          STS-3C         
Hdr Type NNI:          --                      coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:       --             
Connection Channels:   16050                         length:     --             
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      Yes            
F4 AIS Detection:      --                 Frame Scramble:        Yes            
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 11.1


node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:03 GMT 

TRK 11.1 Parameters
 1 Q Depth - rt-VBR    [  885] (Dec)    15 Q Depth   - CBR     [  600] (Dec)
 2 Q Depth - Non-TS    [ 1324] (Dec)    16 Q Depth   - nrt-VBR [ 1000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [15463] (Dec)
 4 Q Depth - BData A   [ 1000] (Dec)    18 Low  CLP  - CBR     [ 100] (%)
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [ 100] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [ 100] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [ 100] (%)
 8 Red Alm - I/O (Dec) [  2500 /  10000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  10000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  30] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 11.1

BXM-T3

node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:04 GMT 

TRK  5.3 Config     T3      [96000 cps]   BXM slot:      5                      
Transmit Rate:         96000              VPC Conns disabled:    No             
Protocol By The Card:  No                 Line framing:          PLCP           
Hdr Type NNI:          Yes                     coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:       --             
Connection Channels:   256                           length:     0-225 ft.      
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      No             
F4 AIS Detection:      --                 Frame Scramble:        --             
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 5.3


node	TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:04 GMT 

TRK 5.3 Parameters
 1 Q Depth - rt-VBR    [  242] (Dec)    15 Q Depth   - CBR     [  400] (Dec)
 2 Q Depth - Non-TS    [  360] (Dec)    16 Q Depth   - nrt-VBR [ 5000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [10000] (Dec)
 4 Q Depth - BData A   [ 8000] (Dec)    18 Low  CLP  - CBR     [  60] (%)
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [  80] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [  60] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [  80] (%)
 8 Red Alm - I/O (Dec) [  2500 /  15000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  15000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  20] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 5.3 

BXM-E3

node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 14:17 GMT 

TRK  9.1 Config     E3      [80000 cps]   BXM slot:      9                      
Transmit Rate:         80000              VPC Conns disabled:    No             
Protocol By The Card:  No                 Line framing:          --             
Hdr Type NNI:          Yes                     coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:       --             
Connection Channels:   256                           length:     0-225 ft.      
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      Yes            
F4 AIS Detection:      --                 Frame Scramble:        --             
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 9.1


node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 14:17 GMT 

TRK 9.1 Parameters
 1 Q Depth - rt-VBR    [  202] (Dec)    15 Q Depth   - CBR     [  400] (Dec)
 2 Q Depth - Non-TS    [  300] (Dec)    16 Q Depth   - nrt-VBR [ 5000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [10000] (Dec)
 4 Q Depth - BData A   [ 8000] (Dec)    18 Low  CLP  - CBR     [  60] (%)
 5 Q Depth - BData B   [ 8000] (Dec)    19 High CLP  - CBR     [  80] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [  60] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [  80] (%)
 8 Red Alm - I/O (Dec) [  2500 /  15000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  15000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  20] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 9.1 

BXM-155

node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:10 GMT 

TRK  5.2 Config     OC3     [353207cps]   BXM slot:      5                      
Transmit Rate:         353208             VPC Conns disabled:    No             
Protocol By The Card:  No                 Line framing:          STS-3C         
Hdr Type NNI:          Yes                     coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:       --             
Connection Channels:   256                           length:     --             
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      Yes            
F4 AIS Detection:      --                 Frame Scramble:        Yes            
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      

Last Command: dsptrkcnf 5.2


node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:10 GMT 

TRK 5.2 Parameters
 1 Q Depth - rt-VBR    [  885] (Dec)    15 Q Depth   - CBR     [  600] (Dec)
 2 Q Depth - Non-TS    [ 1324] (Dec)    16 Q Depth   - nrt-VBR [ 5000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [20000] (Dec)
 4 Q Depth - BData A   [10000] (Dec)    18 Low  CLP  - CBR     [  60] (%)
 5 Q Depth - BData B   [10000] (Dec)    19 High CLP  - CBR     [  80] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [  60] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [  80] (%)
 8 Red Alm - I/O (Dec) [  2500 /  10000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  10000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  20] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 5.2 

BXM-622

node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:11 GMT 

TRK 11.1 Config     OC12    [1412679cps]  BXM slot:      11                     
Transmit Rate:         1412830            VPC Conns disabled:    No             
Protocol By The Card:  No                 Line framing:          STS-12C        
Hdr Type NNI:          Yes                     coding:           --             
Statistical Reserve:   5000    cps             recv impedance:   --             
Idle code:             7F hex                  cable type:       --             
Connection Channels:   256                           length:     --             
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR  Pass sync:             Yes            
Restrict CC traffic:   No                 Loop clock:            No             
Link type:             Terrestrial        HCS Masking:           Yes            
Routing Cost:          10                 Payload Scramble:      Yes            
F4 AIS Detection:      --                 Frame Scramble:        Yes            
                                          Vtrk Type / VPI:       -- / --        
                                          Incremental CDV:       0              
                                          Deroute delay time:    0 seconds      
Last Command: dsptrkcnf 11.1


node           TRM   Cisco           BPX 8620 9.3.53   Mar. 2 2006 11:11 GMT 

TRK 11.1 Parameters
 1 Q Depth - rt-VBR    [ 3533] (Dec)    15 Q Depth   - CBR     [ 1200] (Dec)
 2 Q Depth - Non-TS    [ 5297] (Dec)    16 Q Depth   - nrt-VBR [10000] (Dec)
 3 Q Depth - TS        [ 1000] (Dec)    17 Q Depth   - ABR     [40000] (Dec)
 4 Q Depth - BData A   [40000] (Dec)    18 Low  CLP  - CBR     [  60] (%)
 5 Q Depth - BData B   [40000] (Dec)    19 High CLP  - CBR     [  80] (%)
 6 Q Depth - High Pri  [ 1000] (Dec)    20 Low  CLP  - nrt-VBR [  60] (%)
 7 Max Age - rt-VBR    [   20] (Dec)    21 High CLP  - nrt-VBR [  80] (%)
 8 Red Alm - I/O (Dec) [  2500 /  10000]22 Low CLP/EPD-ABR     [  60] (%)
 9 Yel Alm - I/O (Dec) [  2500 /  10000]23 High CLP  - ABR     [  80] (%)
10 Low  CLP - BData A  [ 100] (%)       24 EFCN      - ABR     [  20] (%)
11 High CLP - BData A  [ 100] (%)
12 Low  CLP - BData B  [  25] (%)
13 High CLP - BData B  [  75] (%)
14 EFCN     - BData B  [  30] (Dec)
This Command: cnftrkparm 11.1 

Cisco IGX 8400 Nodes

node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:23 GMT 

                           System-Wide Parameters

1  Max Time Stamped Packet Age (msec) ................................   32
2  Allow CPU Starvation of Fail Handler ..............................   No
7  Max Network Queuing Delay for HDM/LDM NTS Data connections (msec)..   30
9  Max Network Queuing Delay for CVM/UVM VAD connections (msec).......   64
11 Max Network Queuing Delay for CVM/UVM non-VAD connections (msec)...   64
13 Enable Discard Eligibility.........................................   No
14 Use Frame Relay Standard Parameters Bc and Be......................   No
22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm..    0
23 Enable Connection Deroute Delay feature ...........................   No
24 Interval Statstics polling rate for ATM/Frame Relay VCs............    5
25 Interval Statistics polling rate for ports.........................    5
26 Max Num of Nodes doing Simultaneous TFTP Configuration Save/Restore    4

This Command: cnfsysparm 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:24 GMT 

1  Update Initial Delay   [ 5000] (D)   16 CC Redundancy Cnfged   [    Y] (Y/N)
2  Update Per-Node Delay  [30000] (D)   17 MT3 Pass Through Relay [    Y] (Y/N)
3  Comm-Break Test Delay  [30000] (D)   18 Nw Pkt Tx Rate (pps)   [  500] (D)
4  Comm-Break Test Offset [   10] (D)   19 Stats Memory (x 100KB) [  130] (D)
5  Network Timeout Period [ 1700] (D)   20 Standby Update Timer   [   10] (D)
6  Network Inter-p Period [ 4000] (D)   21 Stby Updts Per Pass    [  150] (D)
7  NW Sliding Window Size [    1] (D)   22 Gateway ID Timer       [   30] (D)
8  Num Normal Timeouts    [    7] (D)   23 GLCON Alloc Timer      [   30] (D)
9  Num Inter-p Timeouts   [    3] (D)   24 Comm Fail Delay        [   60] (D)
10 Num Satellite Timeouts [    6] (D)   25 Nw Hdlr Timer (msec)   [  100] (D)
11 Num Blind Timeouts     [    4] (D)   26 CBUS Delay (msec)      [   20] (D)
12 Num CB Msg Timeouts    [    2] (D)   27 SNMP Event logging     [    Y] (Y/N)
13 Comm Fail Interval     [10000] (D)   28 TFTP Grant Delay (sec) [    1] (D)
14 Comm Fail Multiplier   [    3] (D)   29 TFTP ACK Timeout (sec) [   10] (D)
15 Temperature Threshold  [   50] (D)   30 TFTP Write Retries     [    3] (D)
31 FRP Link Status Alarm  [    Y] (Y/N) 46 Modem polling timer    [    1] (D)
32 Job Lock Timeout       [   60] (D)   47 Verify CBA for non-FRP [    N] (Y/N)
33 Max Via LCONs          [20000] (D)   48 Send Abit early        [    N] (Y/N)
34 Max Blind Segment Size [ 3570] (D)   49 Abit Tmr Multiplier  M [    0] (D)
35 Max XmtMemBlks per NIB [ 3000] (D)   50 Abit Tmr Granularity N [    3] (D)
36 Max Mem on Stby Q (%)  [   33] (D)   51 CommBrk Hop Weight     [   25] (D)
37 Trk Cell Rtng Restrict [    Y] (Y/N) 52 CB Fail Penalty Hops   [    2] (D)
38 Stat Config Proc Cnt   [ 1000] (D)   53 Dnld LanIP or NwIP     [ Lan](Lan/Nw)
39 Stat Config Proc Delay [ 2000] (D)   54 IP Relay gateway node  [    0] (D)
40 Enable Degraded Mode   [    Y] (Y/N) 55 Max LAN Window (sec)   [   60] (D)
41 Enable Rrt on Comm Fail[    N] (Y/N) 56 Max LAN Packets/Window [18000] (D)
42 Auto Switch on Degrade [    Y] (Y/N)
43 Max Degraded Aborts    [  100] (D)
44 Max Htls Rebuild Count [  100] (D)
45 Htls Counter Reset Time[ 1000] (D)
This Command: cnfnodeparm


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:25 GMT 

Index Status    Function

1     Enabled   Automatic CLN/PLN Loopback Test on Local/Remote Alarms
2     Enabled   FDP Loopback button
3     Enabled   User Command Logging
4     Enabled   Automatic Card Reset on Hardware Error
5     Enabled   TXR Model D Download
6     Enabled   Card Error Record Wraparound
7     Disabled  Card Test After Failure
8     Disabled  Download From Remote CWM
9     Disabled  Logging of conn events in local event log
10    Disabled  Logging of conn events in CWM event log
11    Disabled  Logging SVC Connection Events
12    Disabled  Force Download From a Specific IP address
13    Disabled  CDP WinkStart Signalling
14    Enabled   Logging of Bus Diagnostic Events in local event log
15    Enabled   Automatic Card Reset after Burnfw for CBI cards
16    Disabled  Logging of router state events in CWM event log
This Command: cnffunc


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:27 GMT 

Index Status    Function

1     Disabled  Repetitive Pattern Suppression
3     Enabled   Frame Relay
4     Disabled  Configuration Save/Restore
5     Disabled  ForeSight
6     Disabled  Frame Relay Network-to-Network Interface
7     Disabled  Multiple VTs (1 session enabled)
8     Disabled  Interface Shelf
9     Enabled   Virtual Trunks
10    Disabled  ABR standard with VSVD


This Command: cnfswfunc 

node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:27 GMT 
Card   Test    - - - - - - Self Test - - - - - - -   - - Background Test - - -
Type   Freq    Enable        Inc   Thresh  Timeout   Enable        Inc   Thresh
----   -----   --------  -------  -------  -------   --------  -------  -------
PSM      300   Enabled       100      300       31   N/A           100      300
HDM      300   Enabled       100      300       80   Enabled       100      300
LDM      300   Enabled       100      300       80   Enabled       100      300
NTM      300   Enabled       100      300       31   N/A           100      300
FRM      300   Enabled       100      300       80   Enabled       100      300
MT3      300   Enabled       100      300       50   N/A           100      300
CVM      300   Enabled       100      300      300   N/A           100      300
NPM      180   Enabled       100      300      120   N/A           100      300
ARM      300   Enabled       100      300       60   N/A           100      300
BTM      300   Enabled       100      300      120   N/A           100      300
FTM      300   Enabled       100      300       80   Disabled      100      300
UFM      300   Enabled       100      300       80   Enabled       100      300
UFMU     300   Enabled       100      300       80   Enabled       100      300
ALM      300   Enabled       100      300      120   N/A           100      300
UVM      300   Disabled      100      300       60   N/A           100      300
UXM      300   Enabled       100      300      800   Enabled       100      300
URM      300   Enabled       100      300      800   Enabled       100      300
This Command: cnftstparm 
node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:28 GMT 

8  Maximum Routing Bundle    [   90] (D)   
9  Reroute Timer             [    3] (secs)   
10 Reset Timer on Line Fail  [  Yes]
11 Max Down/Up Per Pass      [   50] (D)   
12 Down/Up Timer             [30000] (msecs)   
13 Max Route Errs per cycle  [  200] (D)   
14 Time between Rrt cycles   [    5] (mins)   
15 Max. Rrt Err cycles       [    1] (D)   
16 Routing pause timer       [    0] (msecs)   
17 Max msgs sent per update  [   10] (D)   
18 Send SVC urgent msg       [  Yes]
19 Max SVC Retry             [    0] (D)   
20 Wait for TBL Updates      [   70] (100 msecs)
21 Max Derouting Bndl (0=all)[  500] (D)   
22 Enable Cost-Based Routing [   No]
23 Enable Route Cache Usage  [   No]
24 Use Delay for Routing     [   No]
25 # of reroute groups used  [   50] (D)   
26 Starting size of RR grps  [    0] (CLU)
27 Increment between RR grps [  100] (CLU)
28 CM updates app timeout    [    5] (10 secs)
29 Route concurrency level   [    1] (D)   


This Command: cnfcmparm 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:29 GMT 

1  Rmt Blk Freq (msec)     [    100]    16 FW Dnld Msgs/Block(dec) [      4]    
2  Rmt Blk Size (hex)      [    400]    17 Flash Write TO(msec)    [  16000]    
3  Lcl Blk Freq (msec)     [    100]    18 Flash Erase TO(msec)    [    100]    
4  Lcl Blk Size (hex)      [    400]    19 Erase Verify TO(msec)   [  16000]    
5  Image Req Freq (msec)   [  10000]    20 Standby Flash TO(sec)   [    300]    
6  Dnld Req Freq (msec)    [  10000]    21 Lcl Flash Init TO(msec) [   1000]    
7  Session Timeout (msec)  [  30000]    22 Flsh Write Blk Sz (hex) [  10000]    
8  Request Hop Limit (dec) [      1]    23 Flsh Verfy Blk Sz (hex) [    400]    
9  Crc Throttle Freq (dec) [   5000]    24 Chips Per Write/Erase   [      1]    
10 Crc Block Size (hex)    [    400]    
11 Rev Change Wait(dec)    [      0]    
12 CCs Switch Wait(dec)    [   1000]    
13 Lcl Response TO(msec)   [   5000]    
14 Rmt Response TO(msec)   [  30000]    
15 FW Dnld Block TO(msec)  [     50]    
This Command: cnfdlparm 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:30 GMT 

1. Logout Time ........... 20 minutes
2. VT Logout Time ........ 4 minutes
3. Prompt Time ........... 60 seconds
4. Command Time .......... 3 minutes
5. UID Privilege Level ... 6
6. Input Character Echo .. Enabled
7. Screen Update Time .... 10 seconds


This Command: cnfuiparm 

node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:30 GMT 

1  Priority Bumping Enabled                [  NO]
2  Priority Bumping Bundle                 [  50] (D)     
3  Priority Bumping Bands:                               
   Band 1                                  [   2] (D)     
   Band 2                                  [   4] (D)     
   Band 3                                  [   6] (D)     
   Band 4                                  [   8] (D)     
   Band 5                                  [  10] (D)     
   Band 6                                  [  12] (D)     
   Band 7                                  [  14] (D)     


This Command: cnfbmpparm 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:31 GMT 

Function            Number   Status      Function            Number   Status
Background Upcard     1      Enabled     Dynamic BW Allocation 15     Enabled
Background Updates    2      Disabled    Modem Polling         16     Enabled
Standby Terminal      3      Disabled    Conn Stat Sampling    17     Enabled
Memory Protection     4      Enabled     FastPAD Test          18     Enabled
Comm Break            5      Enabled     Neighbor Update Errs  19     Disabled
Comm Fail Test        6      Enabled     SVC Del Bgnd Updates  20     Disabled
BRAM Memory Protect   7      Enabled
CRC Test              8      Enabled
CDT Clock Test        9      Enabled
Bus Fail Detection    10     Enabled
Line Diag             11     Enabled
Clock Restoral        12     Enabled
Cm_Rerouting          13     Enabled
Clock Routing         14     Enabled
This Command: on1 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:32 GMT 

Function            Number   Status      Function            Number   Status
Line Stat Sampling    1      Enabled     LAN Interface         15     Enabled
Statistical Alarm     2      Enabled     Update Standby Stats  16     Enabled
Job Ready Checker     3      Enabled     EIA Monitoring        17     Enabled
Configuration  Backup 4      Enabled     Telnet Access         18     Enabled
Standby Update        5      Enabled     Junction ID           19     Enabled
Downloader            6      Enabled     Mult SV+/Routing Node 20     Enabled
Cm Updates            7      Enabled     Feeder with NW Trunks 21     Disabled
Power Supply Monitor  8      Enabled     Multiple Fdr Trunks   22     Disabled
Topo/Stat Updates     9      Enabled     Simulated Fdr Trks    23     Disabled
CDP/CIP Sig. Polling  10     Enabled     Auto Renum Fail Recov 24     Enabled
Port Stat Sampling    11     Enabled     IGX - ACM Selftest    25     Enabled
Robust Updates        12     Enabled     Card Simulation Tool  26     Enabled
Robust Alarm Updates  13     Enabled     Major Alarm on NNI    27     Disabled
Realtime Counters     14     Enabled     Deroute Delay         28     Enabled
This Command: on2 


node TN    Cisco           IGX 8430 9.3.53   Mar. 2 2006 17:32 GMT 

Function            Number   Status
Trace Msg Sent        1      Disabled
Multi-DB Stby Updates 2      Enabled
AIT/BTM/ALM 32h Ext2  3      Enabled
Card Synchronization  4      Disabled
Loop Access Dev Init  5      Disabled
Auto allocate UXM UBU 6      Disabled
Trace Conv Msg        7      Disabled
Automatic Cbus Diags  8      Disabled
Region memory init    9      Disabled
VT Clk Switch Evt Log 10     Disabled
Load Bal on EqCost Rt 11     Disabled
Stat Poll on SNMP Get 12     Disabled


This Command: on3 

UXM-T3

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:12 GMT 

TRK  5.3 Config       T3/636   [96000 cps]  UXM slot:5                         
Transmit Trunk Rate:  96000  cps          Payload Scramble:     No           
Rcv Trunk Rate:       96000  cps          Connection Channels:  256          
Pass sync:            Yes                 Gateway Channels:     200          
Loop clock:           No                  Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Statistical Reserve:  5000   cps          Incremental CDV:      0            
Header Type:          NNI                 Deroute delay time:   0 seconds    
VPI Address:          1                   VC Shaping:           No           
Routing Cost:         10                  VPC Conns disabled:   No           
Idle code:            7F hex             
Restrict PCC traffic: No                 
Link type:            Terrestrial        
Line framing:         PLCP               
Line cable length:    0-225 ft.          
HCS Masking:          Yes                
Last Command: dsptrkcnf 5.3


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:12 GMT 

TRK  5.3 Parameters:
 1 Yel Alm-In/Out (D)  [  2500/ 15000]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  532]    15 BDataA [10000]     29 rt-VBR [  532]   32 BDataA [10000]
13 Non TS [  795]    16 BDataB [10000]     30 Non TS [  795]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
Rx Queue Depth(D)    Tx Queue Depth(D)    Rx EFCN       (%)    Tx EFCN       (%)
35 CBR    [  600]    38 CBR    [  600]
36 nrt-VBR[ 5000]    39 nrt-VBR[ 5000]
37 ABR    [20000]    40 ABR    [20000]    47 ABR    [   20]    48 ABR    [   20]
Rx High CLP   (%)    Rx Low CLP/EPD(%)    Tx High CLP   (%)    Tx Low CLP/EPD(%)
41 CBR    [   80]    44 CBR    [   60]    49 CBR    [   80]    52 CBR    [   60]
42 nrt-VBR[   80]    45 nrt-VBR[   60]    50 nrt-VBR[   80]    53 nrt-VBR[   60]
43 ABR    [   80]    46 ABR    [   60]    51 ABR    [   80]    54 ABR    [   60]

This Command: cnftrkparm 5.3

UXM-T1-IMA (1 physical line up)

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 15:18 GMT 

TRK  9.1 Config       T1/24    [3622  cps]  UXM slot:9                         
IMA Group Member(s):  1                   Line coding:          B8ZS         
Retained links:       1                   Line cable type:      ABAM         
Transmit Trunk Rate:  3622   cps          Line cable length:    0-131 ft.    
Rcv Trunk Rate:       3622   cps          HCS Masking:          Yes          
Pass sync:            Yes                 Payload Scramble:     No           
Loop clock:           No                  Connection Channels:  256          
Statistical Reserve:  1000   cps          Gateway Channels:     200          
Header Type:          NNI                 Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
VPI Address:          1                   Incremental CDV:      0            
Routing Cost:         10                  IMA Protocol Option:  Disabled     
Idle code:            7F hex              IMA Max. Diff. Dly:   200 msec.    
Restrict PCC traffic: No                  IMA Clock Mode:       CTC          
Link type:            Terrestrial         Deroute delay time:   0 seconds    
Line framing:         ESF                 VC Shaping:           No           
TRK  9.1 Config       T1/24    [3622  cps]  UXM slot:9                         
VPC Conns disabled:   No 
This Command: dsptrkcnf 9.1

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 15:19 GMT 

TRK  9.1 Parameters:
 1 Yel Alm-In/Out (D)  [   600/   600]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [   22]    15 BDataA [10000]     29 rt-VBR [   21]   32 BDataA [10000]
13 Non TS [   30]    16 BDataB [10000]     30 Non TS [   28]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
Rx Queue Depth(D)    Tx Queue Depth(D)    Rx EFCN       (%)    Tx EFCN       (%)
35 CBR    [  600]    38 CBR    [  600]
36 nrt-VBR[ 5000]    39 nrt-VBR[ 5000]
37 ABR    [20000]    40 ABR    [20000]    47 ABR    [   20]    48 ABR    [   20]
Rx High CLP   (%)    Rx Low CLP/EPD(%)    Tx High CLP   (%)    Tx Low CLP/EPD(%)
41 CBR    [   80]    44 CBR    [   60]    49 CBR    [   80]    52 CBR    [   60]
42 nrt-VBR[   80]    45 nrt-VBR[   60]    50 nrt-VBR[   80]    53 nrt-VBR[   60]
43 ABR    [   80]    46 ABR    [   60]    51 ABR    [   80]    54 ABR    [   60]


This Command: cnftrkparm 9.1

UXM-T1-IMA (4 physical lines up)

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 15:20 GMT 

TRK  9.2(4) Config    T1/95    [14339 cps]  UXM slot:9                         
IMA Group Member(s):  2-5                 Line coding:          B8ZS         
Retained links:       4                   Line cable type:      ABAM         
Transmit Trunk Rate:  14339  cps          Line cable length:    0-131 ft.    
Rcv Trunk Rate:       14339  cps          HCS Masking:          Yes          
Pass sync:            Yes                 Payload Scramble:     No           
Loop clock:           No                  Connection Channels:  256          
Statistical Reserve:  1000   cps          Gateway Channels:     200          
Header Type:          NNI                 Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
VPI Address:          1                   Incremental CDV:      0            
Routing Cost:         10                  IMA Protocol Option:  Enabled      
Idle code:            7F hex              IMA Max. Diff. Dly:   200 msec.    
Restrict PCC traffic: No                  IMA Clock Mode:       CTC          
Link type:            Terrestrial         Deroute delay time:   0 seconds    
Line framing:         ESF                 VC Shaping:           No           
TRK  9.2(4) Config    T1/95    [14339 cps]  UXM slot:9                         
VPC Conns disabled:   No 
This Command: dsptrkcnf 9.2


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 15:20 GMT 

TRK  9.2(4) Parameters:
 1 Yel Alm-In/Out (D)  [   600/   600]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [   81]    15 BDataA [10000]     29 rt-VBR [   80]   32 BDataA [10000]
13 Non TS [  118]    16 BDataB [10000]     30 Non TS [  117]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
Rx Queue Depth(D)    Tx Queue Depth(D)    Rx EFCN       (%)    Tx EFCN       (%)
35 CBR    [  600]    38 CBR    [  600]
36 nrt-VBR[ 5000]    39 nrt-VBR[ 5000]
37 ABR    [20000]    40 ABR    [20000]    47 ABR    [   20]    48 ABR    [   20]
Rx High CLP   (%)    Rx Low CLP/EPD(%)    Tx High CLP   (%)    Tx Low CLP/EPD(%)
41 CBR    [   80]    44 CBR    [   60]    49 CBR    [   80]    52 CBR    [   60]
42 nrt-VBR[   80]    45 nrt-VBR[   60]    50 nrt-VBR[   80]    53 nrt-VBR[   60]
43 ABR    [   80]    46 ABR    [   60]    51 ABR    [   80]    54 ABR    [   60]

                                                                                
This Command: cnftrkparm 9.2

UXM-E1-IMA (1 physical line up)

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:20 GMT 

TRK 13.1 Config       E1/30    [4528  cps]  UXM slot:13                        
Line DS-0 map:        1-15,17-31          Line coding:          HDB3         
IMA Group Member(s):  1                   Line CRC:             Yes          
Retained links:       1                   Line recv impedance:  120 ohm      
Transmit Trunk Rate:  4528   cps          HCS Masking:          Yes          
Rcv Trunk Rate:       4528   cps          Payload Scramble:     Yes          
Pass sync:            Yes                 Connection Channels:  256          
Loop clock:           No                  Gateway Channels:     200          
Statistical Reserve:  1000   cps          Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Header Type:          NNI                 Incremental CDV:      0            
VPI Address:          1                   IMA Protocol Option:  Disabled     
Routing Cost:         10                  IMA Max. Diff. Dly:   200 msec.    
Idle code:            54 hex              IMA Clock Mode:       CTC          
Restrict PCC traffic: No                  Deroute delay time:   0 seconds    
Link type:            Terrestrial         VC Shaping:           No           
TRK 13.1 Config       E1/30    [4528  cps]  UXM slot:13                        
VPC Conns disabled:   No
This Command: dsptrkcnf 13.1

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:20 GMT 

TRK 13.1 Parameters:
 1 Yel Alm-In/Out (D)  [  1000/  2000]     18 Red Alm-In/Out (D) [  1000/  2000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  N/A]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [   27]    15 BDataA [10000]     29 rt-VBR [   26]   32 BDataA [10000]
13 Non TS [   37]    16 BDataB [10000]     30 Non TS [   36]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
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-E1-IMA (4 physical lines up)

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:24 GMT 

TRK 13.5(4) Config    E1/119   [17962 cps]  UXM slot:13                        
Line DS-0 map:        1-15,17-31          Line coding:          HDB3         
IMA Group Member(s):  5-8                 Line CRC:             Yes          
Retained links:       4                   Line recv impedance:  120 ohm      
Transmit Trunk Rate:  17962  cps          HCS Masking:          Yes          
Rcv Trunk Rate:       17962  cps          Payload Scramble:     Yes          
Pass sync:            Yes                 Connection Channels:  256          
Loop clock:           No                  Gateway Channels:     200          
Statistical Reserve:  1000   cps          Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Header Type:          NNI                 Incremental CDV:      0            
VPI Address:          1                   IMA Protocol Option:  Enabled      
Routing Cost:         10                  IMA Max. Diff. Dly:   200 msec.    
Idle code:            54 hex              IMA Clock Mode:       CTC          
Restrict PCC traffic: No                  Deroute delay time:   0 seconds    
Link type:            Terrestrial         VC Shaping:           No           
TRK 13.5(4) Config    E1/119   [17962 cps]  UXM slot:13                        
VPC Conns disabled:   No 
This Command: dsptrkcnf 13.5


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:24 GMT 

TRK 13.5(4) Parameters:
 1 Yel Alm-In/Out (D)  [  1000/  2000]     18 Red Alm-In/Out (D) [  1000/  2000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  N/A]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  101]    15 BDataA [10000]     29 rt-VBR [  100]   32 BDataA [10000]
13 Non TS [  148]    16 BDataB [10000]     30 Non TS [  147]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
Rx Queue Depth(D)    Tx Queue Depth(D)    Rx EFCN       (%)    Tx EFCN       (%)
35 CBR    [  600]    38 CBR    [  600]
36 nrt-VBR[ 5000]    39 nrt-VBR[ 5000]
37 ABR    [20000]    40 ABR    [20000]    47 ABR    [   20]    48 ABR    [   20]
Rx High CLP   (%)    Rx Low CLP/EPD(%)    Tx High CLP   (%)    Tx Low CLP/EPD(%)
41 CBR    [   80]    44 CBR    [   60]    49 CBR    [   80]    52 CBR    [   60]
42 nrt-VBR[   80]    45 nrt-VBR[   60]    50 nrt-VBR[   80]    53 nrt-VBR[   60]
43 ABR    [   80]    46 ABR    [   60]    51 ABR    [   80]    54 ABR    [   60]
This Command: cnftrkparm 13.5

UXM-E3

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:26 GMT 

TRK  5.1 Config       E3/530   [80000 cps]  UXM slot:5                         
Transmit Trunk Rate:  80000  cps          Payload Scramble:     Yes          
Rcv Trunk Rate:       80000  cps          Connection Channels:  256          
Pass sync:            Yes                 Gateway Channels:     200          
Loop clock:           No                  Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Statistical Reserve:  5000   cps          Incremental CDV:      0            
Header Type:          NNI                 Deroute delay time:   0 seconds    
VPI Address:          1                   VC Shaping:           No           
Routing Cost:         10                  VPC Conns disabled:   No           
Idle code:            7F hex             
Restrict PCC traffic: No                 
Link type:            Terrestrial        
Line framing:         HEC                
Line cable length:    0-225 ft.          
HCS Masking:          Yes                
Last Command: dsptrkcnf 5.1


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:26 GMT 

TRK  5.1 Parameters:
 1 Yel Alm-In/Out (D)  [  2500/ 15000]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  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 5.1

UXM-OC3

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:27 GMT 

TRK 10.1 Config       OC3      [353207cps]  UXM slot:10                        
Transmit Trunk Rate:  353208 cps          Connection Channels:  256          
Rcv Trunk Rate:       353207 cps          Gateway Channels:     200          
Pass sync:            Yes                 Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Loop clock:           No                  Incremental CDV:      0            
Statistical Reserve:  5000   cps          Frame Scramble:       Yes          
Header Type:          NNI                 Deroute delay time:   0 seconds    
VPI Address:          1                   VC Shaping:           No           
Routing Cost:         10                  VPC Conns disabled:   No           
Idle code:            7F hex             
Restrict PCC traffic: No                 
Link type:            Terrestrial        
Line framing:         STS-3C             
HCS Masking:          Yes                
Payload Scramble:     Yes                

Last Command: dsptrkcnf 10.1


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:28 GMT 

TRK 10.1 Parameters:
 1 Yel Alm-In/Out (D)  [  2500/ 10000]     18 Red Alm-In/Out (D) [  2500/ 10000]
 2 Rx Max Age - rt-VBR   (D)   [   20]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [   20]     20 Tx EFCN    - BdataB   (%)  [   20]
 4 Gateway Efficiency    (D)   [  2.0]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP/EPD- Rx_Space (%)   [  N/A]     21 BDataA [  N/A]   23 BDataA [  N/A]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  N/A]   24 BDataB [  N/A]
Rx High CLP   (%)    Rx Low CLP/EPD(%)     Tx High CLP   (%)   Tx Low CLP/EPD(%)
 8 BDataA [   80]    10 BDataA [   60]     25 BDataA [   80]   27 BDataA [   60]
 9 BDataB [   80]    11 BdataB [   60]     26 BDataB [   80]   28 BDataB [   60]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [ 1952]    15 BDataA [10000]     29 rt-VBR [ 1952]   32 BDataA [10000]
13 Non TS [ 2925]    16 BDataB [10000]     30 Non TS [ 2925]   33 BDataB [10000]
14 TS     [ 1000]    17 HighPri[ 1000]     31 TS     [ 1000]   34 HighPri[ 1000]
Rx Queue Depth(D)    Tx Queue Depth(D)    Rx EFCN       (%)    Tx EFCN       (%)
35 CBR    [  600]    38 CBR    [  600]
36 nrt-VBR[ 5000]    39 nrt-VBR[ 5000]
37 ABR    [20000]    40 ABR    [20000]    47 ABR    [   20]    48 ABR    [   20]
Rx High CLP   (%)    Rx Low CLP/EPD(%)    Tx High CLP   (%)    Tx Low CLP/EPD(%)
41 CBR    [   80]    44 CBR    [   60]    49 CBR    [   80]    52 CBR    [   60]
42 nrt-VBR[   80]    45 nrt-VBR[   60]    50 nrt-VBR[   80]    53 nrt-VBR[   60]
43 ABR    [   80]    46 ABR    [   60]    51 ABR    [   80]    54 ABR    [   60]

This Command: cnftrkparm 10.1

NTM-T1

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:28 GMT 

TRK  4 Config         T1/24    [8000  pps]  NTM slot:4                         
Line DS-0 map:        0-23                Deroute delay time:   0 seconds    
Pass sync:            Yes                
Loop clock:           No                 
Statistical Reserve:  1000   pps         
Routing Cost:         10                 
Idle code:            7F hex             
Restrict PCC traffic: No                 
Link type:            Terrestrial        
Line framing:         D4                 
Line coding:          B8ZS               
Line cable type:      ABAM               
Line cable length:    0-133 ft.          
Traffic:              V,TS,NTS,FR,FST    
Incremental CDV:      0                  

Last Command: dsptrkcnf 4


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:29 GMT 

TRK  4 Parameters:
 1 Yel Alm-In/Out (D)  [   600/   600]     18 Red Alm-In/Out (D) [  2500/ 15000]
 2 Rx Max Age - rt-VBR   (D)   [  N/A]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [  N/A]     20 Tx EFCN    - BdataB   (D)  [   30]
 4 Gateway Efficiency    (D)   [  N/A]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP  - Rx_Space   (%)   [  N/A]     21 BDataA [  128]   23 BDataA [  128]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  128]   24 BDataB [  128]
Rx High CLP   (%)    Rx Low CLP    (%)     Tx High CLP   (%)   Tx Low CLP    (%)
 8 BDataA [  N/A]    10 BDataA [  N/A]     25 BDataA [  100]   27 BDataA [  100]
 9 BDataB [  N/A]    11 BdataB [  N/A]     26 BDataB [   75]   28 BDataB [   25]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  N/A]    15 BDataA [  N/A]     29 rt-VBR [   22]   32 BDataA [  600]
13 Non TS [  N/A]    16 BDataB [  N/A]     30 Non TS [   30]   33 BDataB [  600]
14 TS     [  N/A]    17 HighPri[  N/A]     31 TS     [ 2648]   34 HighPri[  100]
This Command: cnftrkparm 4 

NTM-E1

node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:29 GMT 

TRK 15 Config         E1/32    [10666 pps]  NTM slot:15                        
Line DS-0 map:        0-31               
Pass sync:            Yes                
Loop clock:           No                 
Statistical Reserve:  1000   pps         
Routing Cost:         10                 
Idle code:            54 hex             
Restrict PCC traffic: No                 
Link type:            Terrestrial        
Line coding:          HDB3               
Line CRC:             No                 
Line recv impedance:  75 ohm + gnd       
Traffic:              V,TS,NTS,FR,FST    
Incremental CDV:      0                  
Deroute delay time:   0 seconds          
                                                                                
Last Command: dsptrkcnf 15


node          TRM   Cisco           IGX 8420 9.3.53   Mar. 2 2006 11:29 GMT 

TRK 15 Parameters:
 1 Yel Alm-In/Out (D)  [  1000/  2000]     18 Red Alm-In/Out (D) [  1000/  2000]
 2 Rx Max Age - rt-VBR   (D)   [  N/A]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [  N/A]     20 Tx EFCN    - BdataB   (D)  [   30]
 4 Gateway Efficiency    (D)   [  N/A]
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP  - Rx_Space   (%)   [  N/A]     21 BDataA [  128]   23 BDataA [  128]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  128]   24 BDataB [  128]
Rx High CLP   (%)    Rx Low CLP    (%)     Tx High CLP   (%)   Tx Low CLP    (%)
 8 BDataA [  N/A]    10 BDataA [  N/A]     25 BDataA [  100]   27 BDataA [  100]
 9 BDataB [  N/A]    11 BdataB [  N/A]     26 BDataB [   75]   28 BDataB [   25]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  N/A]    15 BDataA [  N/A]     29 rt-VBR [   28]   32 BDataA [  600]
13 Non TS [  N/A]    16 BDataB [  N/A]     30 Non TS [   40]   33 BDataB [  600]
14 TS     [  N/A]    17 HighPri[  N/A]     31 TS     [ 2632]   34 HighPri[  100]
This Command: cnftrkparm 15

NTM-SR

node TN    Cisco           IGX 8420 9.3.53   Mar. 2 2006 12:44 PST  
TRK  7 Config         SR/30    [10000 pps]  NTM slot:7                          
Subrate interface:    X.21                                                      
Subrate data rate:    1920 kbps                                                 
Pass sync:            No                                                        
Loop clock:           Yes                                                       
Statistical Reserve:  1000   pps                                                
Routing Cost:         10                                                        
Restrict PCC traffic: No                                                        
Link type:            Terrestrial                                               
Traffic:              V,TS,NTS,FR,FST                                           
Deroute delay time:   0 seconds                                                 
This Command: dsptrkcnf 7                                                       

node TN    Cisco           IGX 8420 9.3.53   Mar. 2 2006 12:44 PST  
TRK  7 Parameters:                                                              
 1 Yel Alm-In/Out (D)  [  1000/  2000]     18 Red Alm-In/Out (D) [  1000/  2000]
 2 Rx Max Age - rt-VBR   (D)   [  N/A]     19 Tx Max Age - rt-VBR   (D)  [   20]
 3 Rx EFCN  - BdataB     (D)   [  N/A]     20 Tx EFCN    - BdataB   (D)  [   30]
 4 Gateway Efficiency    (D)   [  N/A]                                          
 5 EFCN     - Rx Space   (D)   [  N/A]     Tx Age Step2  (D)   Tx Age Step   (D)
 6 Low CLP  - Rx_Space   (%)   [  N/A]     21 BDataA [  128]   23 BDataA [  128]
 7 High CLP - Rx_Space   (%)   [  N/A]     22 BDataB [  128]   24 BDataB [  128]
Rx High CLP   (%)    Rx Low CLP    (%)     Tx High CLP   (%)   Tx Low CLP    (%)
 8 BDataA [  N/A]    10 BDataA [  N/A]     25 BDataA [  100]   27 BDataA [  100]
 9 BDataB [  N/A]    11 BdataB [  N/A]     26 BDataB [   75]   28 BDataB [   25]
Receive Queue Depth                (D)     Transmit Queue Depth              (D)
12 rt-VBR [  N/A]    15 BDataA [  N/A]     29 rt-VBR [   27]   32 BDataA [  600]
13 Non TS [  N/A]    16 BDataB [  N/A]     30 Non TS [   37]   33 BDataB [  600]
14 TS     [  N/A]    17 HighPri[  N/A]     31 TS     [ 2636]   34 HighPri[  100]
This Command: cnftrkparm 7 

Appendix A—BXM Firmware MFZ Release Notes

This section contains information about the BXM firmware MFZ.

About the Firmware MFZ

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

Front Cards

Table 32 lists the front cards that support MFZ firmware.

Table 32 Front Cards Supported by MFZ Firmware 

Model Number
Description
FW model
HW Rev
FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

B

MFZ

BXM-155-8

8 port OC3 Line Module (Front Card)

F

B

MFZ

BXM-622

1 port OC12 Line Module (Front Card)

F

D

MFZ

BXM-622-2

2 port OC12 Line Module (Front Card)

F

D

MFZ

BXM-T3-8

8 port T3 Line Module (Front Card)

F

B

MFZ

BXM-T3-12

12 port T3 Line Module (Front Card)

F

B

MFZ

BXM-E3-8

8 port E3 Line Module (Front Card)

F

B

MFZ

BXM-E3-12

12 port E3 Line Module (Front Card)

F

B

MFZ

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A0

MFZ

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A0

MFZ

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A0

MFZ

BXM-T3-12EX

12 port T3 Line Module (Front Card)

F

A0

MFZ

BXM-T3-12E

12 port T3 Line Module (Front Card)

F

A0

MFZ

BXM-T3-8E

8 port T3 Line Module (Front Card)

F

A0

MFZ

BXM-E3-12EX

12 port E3 Line Module (Front Card)

F

A0

MFZ

BXM-E3-12E

12 port E3 Line Module (Front Card)

F

A0

MFZ

BXM-E3-8E

8 port E3 Line Module (Front Card)

F

A0

MFZ


Front Card for APS Compatibility

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

Table 33 Front Cards Supporting APS with MFZ Firmware 

Model Number
Description
FW model
HW Rev
FW Rev

BXM-155-4

4 port OC3 Line Module (Front Card)

F

C

MFZ

BXM-155-8

8 port OC3 Line Module (Front Card)

F

C

MFZ

BXM-622

1 port OC12 Line Module (Front Card)

F

E

MFZ

BXM-622-2

2 port OC12 Line Module (Front Card)

F

E

MFZ

BXM-155-8DX

8 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-8D

8 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-4DX

4 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-155-4D

4 port OC3 Line Module (Front Card)

F

A0

MFZ

BXM-622-2DX

2 port OC12 Line Module (Front Card)

F

A0

MFZ

BXM-622-2D

2 port OC12 Line Module (Front Card)

F

A0

MFZ

BXM-622-DX

1 port OC12 Line Module (Front Card)

F

A0

MFZ


Back Cards

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

Table 34 Back Cards Supported by MFZ Firmware 

Model Number
Description
HW Rev
FW Rev

MMF-155-4

4 port multi-mode fiber back card

A

na

MMF-155-8

8 port multi-mode fiber back card

A

na

SMF-155-4

4 port single-mode fiber intermediate-reach back card

A

na

SMF-155-8

8 port single-mode fiber intermediate-reach back card

A

na

SMFMR-155-4

4 port single-mode fiber long-reach back card

A

na

SMFMR-155-8

4 port single-mode fiber long-reach back card

A

na

SMF-622

1 port intermediate-reach OC12 back card

A

na

SMF-622-2

2 port intermediate-reach OC12 back card

A

na

SMFMR-622

1 port long-reach OC12 back card

A

na

SMFMR-622-2

2 port long-reach OC12 back card

A

na

XLR-622

1 port extra long-reach OC12 back card

A

na

XLR-622-2

2 port extra long-reach OC12 back card

A

na

BPX-T3/E3-12

12 port T3/E3 back card

A

na

BPX-T3/E3-8

8 port T3/E3 back card

A

na

RDNT-LR-622-2

2 port long-reach OC12 redundant back card

A

na

RDNT-SM-622-2

2 port intermediate reach OC12 redundant back cards

A

na

RDNT-SM-622

1 port intermediate reach OC12 redundant back cards

A

na

RDNT-LR-155-8

8 port long-reach OC3 redundant back cards

A

na

RDNT-SM-155-4

4 port intermediate-reach OC3 redundant back cards

A

na

RDNT-SM-155-8

8 port intermediate-reach OC3 redundant back cards

A

na


New Features Supported in BXM Firmware MFZ

Bug fixes only.

New Features Supported in BXM Firmware MFY

Bug fixes only.

New Features Supported in BXM Firmware MFX

VSI bandwidth overbooking—CSCdy72578.

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

New Features Supported in BXM Firmware MFW

Bug fixes only.

New Features Supported in BXM Firmware MFV

VC merge support added.

New Features Supported in BXM Firmware MFU

Virtual trunk oversubscription.

VC shaping.

New Features Supported in BXM Firmware MFT

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

New Features Supported in BXM Firmware MFR

Bug fix only.

New Features Supported in BXM Firmware MFP

Configurable number of ILMI traps.

New Features Supported in BXM Firmware MFN

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

Support for E2E tstpingoam.

Support for O.151 OAM standard.

New Features Supported in BXM Firmware MFM

Bug fix only.

New Features Supported in BXM Firmware MFK

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

New Features Supported in BXM Firmware MFJ

Bug fix only.

New Features Supported in BXM Firmware MFH

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

SPVC feeder support.

New Features Supported in BXM Firmware MFF

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

New Features Supported in BXM Firmware MFE

Bug fix only.


Note Support for APS 1:1 added for VSI.


New Features Supported in BXM Firmware MFD

Bug fix only.

New Features Supported in BXM Firmware MFC

Support for SES (PNNI controller).

BootCore enhancement to support multi-vendor flash-SIMMs.

A 1 msec granularity for tstdelay measurement.

New Features Supported in BXM Firmware MFB

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

Hitless connection density upgrade for BXM.

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

Control traffic shaping.

New Features Supported in BXM Firmware MFA

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


Note First release in MF branch of firmware.


New Features Supported in BXM Firmware MEC

No new features in Release MEC.

New Features Supported in BXM Firmware MEB

No new features in Release MEB.

New Features Supported in BXM Firmware MEA

VSI version 2.2 (single partition).

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

Table 35 lists the current default thresholds.

Table 35 SD and SF Default Thresholds 

BIP count
Condition

10-4

SF detected

10-5

SD detected & SF clear

10-6

SD clear & SF clear


New Features Supported in BXM Firmware MDA

Virtual trunking.

BXM multi-level channel statistics.

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

Card based LMI and ILMI.

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

Special Installation/Upgrade Requirements

This section contains additional installation and upgrade requirements.

BXM-622DX Upgrade Issue

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

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

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

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

APS Issues

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


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

On the BPX temporarily configure to use unidirectional mode.

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

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

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

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


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

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


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

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

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

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

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

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


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

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

Channel Statistics Issues

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

Upgrade From Firmware Revision MEA or Higher


Step 1 Upgrade SWSW to 9.2.30 or higher.

Step 2 Upgrade the firmware to MFZ.


Upgrade From Firmware Revisions Lower Than MEA.

This procedure avoids card mismatch.


Step 1 Upgrade firmware to MEC.

Step 2 Upgrade the SWSW to 9.2.30 or higher revision.

Step 3 Upgrade the firmware to MFZ.

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


Features Obsoleted

The following features have been obsoleted:

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

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

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

Notes, Cautions, and Clarifications

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

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

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

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

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

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

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

8. MFK and higher versions support LCN CAC for Class of Services. The controller reserves some LCNs for control VC as default. These reserved LCNs cannot be used by any Class of Service in MFZ. If all the LCNs for the partition have been used in a version earlier than MFK, after the MFZ version is updated in the switch, some connections might not be added. These connections try to use LCNs reserved for control VC which is not allowed.

Configure more LCNs for the partition to make sure enough LCNs exist for all the connections.

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

10. APS 1:1 is not supported for VSI in versions before MFE (CSCdp42996). APS 1:1 must not be configured on ports intended to be used by PNNI or MPLS as after switchover traffic flow is stalled on the protection line for releases before MFE. However, in MFE and higher, this problem is fixed.

11. Total bandwidth allocated to all VSI partitions on a BXM must not be more that OC12 rate, 1412832 cps. BCC SWSW allows users to configure more than the OC12 rate, which all of the PNNI connection commit requests are NACKed by BXM.

12. In firmware versions prior to MFF signaling bandwidth for an SES controller was not guaranteed. In MFF and above the signaling qbin feature has been added (with SWSW 9.3.10 and higher and SES image 1.0.10 and higher) to guarantee signaling bandwidth.

13. Statistics level 0 for legacy BXM cards was obsoleted in Model F releases until MFN. However, in version MFP and higher conditional support statistics level 0 for legacy cards is revoked. Statistics level 0 is not supported if VSI configurations exist on the card.

If a card was configured with statistics level 0 with VSI enabled in a previous release of firmware (Model C or E), upgrading to MFP or above revisions causes a mismatch on legacy cards.

To avoid impacting VSI operations, reconfigure the card to statistics level 1 or above before upgrading.


Note BXME (enhanced cards) support all statistics levels unconditionally with all valid configurations, models, and releases.


14. Starting with MFP through this release of MFZ, excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) are now reported to Switch Software as red alarms. This feature is not configurable, and might cause failed connections and rerouted trunks in configurations where APS is not enabled, alternate trunk routes do not exist or on UNI ports. This feature is not active when APS is configured and enabled.

Because this feature is not configurable at this point in time customers who do not want this behavior should not upgrade to MFP through MFZ but rather wait for a subsequent SWSW/BXM fw release where this feature can be turned on and off (default is off) via CLI command.

Anomalies Fixed in MFZ

Table 36 lists that anomalies that are fixed in MFZ.

Table 36 Anomalies Fixed in MFZ 

Bug ID
Description
Apply to SES

CSCec33060

Symptom: dspchstats on atfxfst connections shows CLP0 discards.

These cell are not user cells since user traffic is not affected. These cells are traffic management cells.

Conditions: Run the dspchstats command on an ATFXFST connection on a BXM.

Workaround: Unknown.

No

CSCee45765

Symptom: XLMI/LMI protocol remains in down state.

Conditions: When a switchover is done on an AXSM or remote end, XLMI/LMI on the BXM side might go down due to missing ACKs from the remote end. These ACKs are the responses to the UPDATE STATUS message BXM has been sending. XLMI/LMI might stay in down state.

Workaround: Unknown.

XLMI/LMI might recover if on the AXSM side you execute dnlmi /uplmi or any event to trigger UPDATE STATUS message sent to the BXM.

Note dnlmi and uplmi do not affect traffic.

No

CSCeb54474

Symptom: Backcard LED on standby APS card shows green when it is not carrying active APS line (active traffic).

Conditions: Down the line, and up line again.

Workaround: None.

No

CSCeb32926

Symptom: SF/SD BER APS alarm does not clear.

Conditions:

1. Introduce SF/SD BER error on the standby card.

2. Remove the standby backcard.

3. Remove the source of SF/SD BER error.

4. Reinsert the backcard.

SF/SD BER alarm is stuck doing dspapsln.

Workaround:

1. Reintroduce the SF/SD BER error (do not remove backcard), and clear the source of BER error.

2. Do a forced switchapsln (option 3).

No


Known Anomalies in MFY

No known anomalies exist in the BXM firmware MFY.

Anomalies Fixed in MFY

Table 37 lists that anomalies that are fixed in MFY.

Table 37 Anomalies Fixed in MFY 

Bug ID
Description

CSCea08808

Symptom: In a BPX/SES PNNI scenario, SVC/SPVC connections do not route over PNNI virtual interface (VNNI, virtual trunk) when using different VPIs in both ends of the Virtual Path Connection.

Connections fail with cause code #35: Last Fail Cause: requested VPCI/VCI not available.

Conditions: The scenario is similar to the following:

BXM_VNNI-----VPI1-----VPC_Cloud-----VPI2----BXM_VNNI

where VPI1 is different than VPI2

Workaround: Disable ILMI auto configuration using the command from the SES Controller.

With auto-configuration disabled, the ILMI slave does not start ATM layer parameter-negotiations while ports come up. Instead, the ILMI slave uses the local configuration parameters. The default state for auto-configuration is enabled.

Further Problem Description: If this problem is present, the command, dsppnport, shows a minSvccVpi greater than maxSvccVpi, and a minSvccVci greater than maxSvccVci in the end with higher VPI value.

This can be seen in the following example:

nodename.7.PXM.a > dsppnport 1:1.4:14
Port:               1:1.4:14          Logical ID:       16848910
IF status:          up                Admin Status:     up
UCSM:               enable            SVC Routing Pri:  8
Auto-config:        enable            Addrs-reg:        enable
IF-side:            network           IF-type:          nni
UniType:            private           Version:          pnni10
PassAlongCapab:     n/a
Input filter:       0                 Output filter:    0
minSvccVpi:         11                maxSvccVpi:       10     <=====
minSvccVci:         35                maxSvccVci:       65535
minSvpcVpi:         11                maxSvpcVpi:       10     <=====

MFY resolves this issue. MFY is not compatible to previous images for this particular feature. Both sides have to be MFY or later.

CSCea85590

Symptom: In an XPVC network, BXM at the edge of the AR network connects to an AXSM card in the SPVC network. The NodeStatus message that the BXM sends to AXSM, contains a field of Fdr_slot. This field is where the physical slot number is sent, while the logical slot number is needed for the consistency by the CWM.

Conditions: This symptom occurs when running the XLMI/LMI protocol.

Workaround: None.

CSCeb21297

Symptom: Pseudo AIS on path BIP-8 errors on BXM cards with SONET interfaces is not a configurable feature.

Conditions: This symptoms occurs always.

Workaround: None.

This DDTS makes configurable the customer-specific behavior where AIS-P is triggered from UAS. In previous releases starting with MFP, this was always ON. Now the default is OFF, and it must be turned ON via command, cnfndparm 61, using SWSW 9.4.00 or higher.

For a more detailed description, see SWSW 9.4 Release Notes.


Known Anomalies in MFX

Table 38 lists the known anomalies in MFX.

Table 38 Known Anomalies in MFX 

Bug ID
Description
Apply to SES

CSCdx52484

Symptom: CBR traffic got dropped on ENNI link on BPX side where there is congestion.

Condition: resetcd of BXM can solve the problem.

Workaround: Unknown.

No

CSCdx79141

Symptom: Channel allocation inconsistency between BPX and SES.

Condition: Have only 1 part. first (Max. lcn > Min.), add conns. > min. Add more parts such that sum (Mins) >Max (max.).

Workaround: None

Yes


Anomalies Fixed in MFX

Table 39 lists the anomalies that are fixed in MFX.

Table 39 Anomalies Fixed in MFX 

Bug ID
Description

CSCdw76023

Symptom: For APS 1:1 intracard configuration, dspapsln command keeps showing false and misleading alarm "APS missing card."

Conditions: APS 1:1 intracard setup using R (redundant) designated backcard.

Workaround: Do not use an R designated backcard when configuring APS 1:1 intracard setup.

Use the normal backcard. It is just a false alarm. All APS functionality should still be working correctly.

CSCdw95063

Symptom: "dspapsln" doesn't show "card missing" on standby even though the standby card has been removed. "dspapsln" shows OK even though standby BXM card is removed to cause a switchover to the newly active card.

Conditions: Remove the active BXM to cause the switchover to the newly active card in an APS 1+1 configuration setup.

Workaround: Insert back the standby BXM card.

CSCdx28781

Symptom: When bit errors happen on a line, all the connections provisioned on the line fail.

Conditions: MFM onwards (There is a code change went into firmware image MFM, which puts the line into Path AIS as long as UAS-P condition persists. This change is good for trunks as alternate routes could be chosen. But on lines, especially when they are error prone, there is no choice but to keep using the line, application might slow down but at least connection does not get failed).

Workaround: Use images before MFM or replace the buggy physical cable.

CSCdx40378

Symptom: When sending F5 OAM end to end flows through a DACS SPVC, only the "egress" counters of dspconstats increment. This true for F5 end to end AIS, or F5 end to end loopback.

Conditions: This affects OAM cell counting on all SPVC connections. It occurs with firmware MFW or lower revision.

Workaround: None.

CSCdx50089

Symptom: ILMI did not update its neighbor IP address and IfName to be "N/A", when its physical link on which it was running went down. dspnebdisc would show the previous neighbor IP address and IfName in this situation.

Conditions: The physical link on which ILMI was running went down.

Workaround: Reset the card will clear the old information.

CSCdx72292

Symptom: Commit connection request is failed due to NAK from BXM, while still a lot of available bandwidth at partition level.

Conditions: Single/multiple partitions on a interface enabled.

1. The bandwidth common pool of this interface is zero.

2. At least in one partition, sum of (cos_min_bw) > part_min_bw, due to the round up when applying the policy parameters -minbw to get cos_min_bw.

Workaround: Configuring the multiple partitions gives at least 20 cells in common pool. The work around for CSCdv03058 applies to this problem.

See CSCdv03058 for detail workaround explanation.

CSCdy16927

Symptom: BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred.

Conditions: SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder **

1. The connection segment in the BPX/SES network is down.

2. The corresponding segment in the SPVC feeder is in Abit alarm.

3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "**" tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the downed VSI connection in the BPX/SES network.

Workaround: None.

CSCdy57435

Symptom: Fatal PRFD Pending error has been seen at BXM card. (SIMBA errors excess its threshold).

Conditions: Most likely, it happens during FW/SW upgrade.

Workaround: None.

CSCdy75277

Symptom: A pnport stuck is in down state after being added and configured.

Conditions: Add and configure pnport on a freshly added trunk/port. Delete all the configuration and down all interfaces, then newly add and configure the pnport from scratch.

Workaround: Unknown.

CSCdy80205

Symptom: When physical interface in alarm (LOS), dsppnport shows the operating status as up in SES.

Conditions: When SES is running 3.0(10.0) or later, even if the physical interface is in alarm (LOS), if ILMI is enabled, with out configuring signaling type (NNI or UNI) in SES, the operating status of interface is shown as UP. This issue occurs with BXM Image MFW or prior.

Workaround: Configure signaling type in SES.

CSCdy89521

Symptom: The AAL5 Feeder attached to the BPX routing hub becomes unreachable after a delshelf command was issued on the BPX, even though there are no existing connections on either the feeder or the BPX.

Conditions: BXM runs the LMI protocol.

Workaround: None

CSCdz49797

Symptom: Doing a switchyred on BXM causes AXSM connection to go into Abit/AIS alarm.

Conditions: A switchyred on BXM card running XPVC in a mixed MGX 8220 BPX MGX(PXM1) MGX(PXM45) network can go into alarm, and then the alarm will not clear. Typically a transition outside of the PNNI network (a switchyred on the BPX in this case) can cause the ingress port to generate an AIS alarm, which it sends into the PNNI network and is received by CPE at the other end. Because the AIS is incorrect, there's never any indication to the ingress port that it should clear the alarm.

Workaround: Executing dncon/upcon on the AXSM end which is generating switch side Tx AIS (if that is the master connection) If the problem is on the slave end need to delete and re-add the connection

CSCin33357

Symptom: After burn MFW image, the BXM enhanced card went to resetting.

Conditions: BXME card with statistics level 0 and VSI connections.

Workaround: Do not use statistics level 0 for BXME card.

CSCdz60041

Symptom: BPX may not be able to recover clock from the line with PLCP framing configuration.

Conditions: BPX may experience clock recovery issues when recovering clock from the line connected to other vendor equipment.

Workaround: None


Anomalies Fixed in MFW

Table 40 lists that anomalies that are fixed in MFW.

Table 40 Anomalies Fixed in MFW 

Bug ID
Description

CSCdw80712

Symptom: 1:1 APS allows manual/forced switchapsln P->WLine.

Conditions:

1. 1:1 APS with Bi-Dir configured; remote is AXSM/B.

2. Manual switchaps W->PLine from AXSM/B.

3. Forced switchaps P->WLine from BXM.

Workaround: None.

CSCdx45385

Symptom: BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn).

Conditions:

1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level.

2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated.

Workaround: Add a con or down a con to trigger the update.

CSCdx55794

Symptom: BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4.

Conditions:

1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX.

2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI.

Workaround: None.

CSCdx56537

Symptom: Setting cnftrkparm 9 2500/15000 causes trunk failure.

Conditions: BXM running MFU firmware. Found in lab environment but likely to also be found in a live network if these trunk parameter values are used and the trunk passes over another medium such as a TDAX or SDH backbone.

Workaround: Set cnftrkparm 9 2500/10000 which is the default for STM1. Do not use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.

CSCdx59080

Symptom: Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a "Looped Back" state when the BXM is reset by command "resetcd ? h".

Conditions: BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk.

Workaround: Issue cnftrk and change none of the parameters by stepping through them.

CSCdy01870

Symptom: SIMBA reset card errors logged due to PRFD Pending Errors

Conditions: BXM image MEE and SWSW image 9.3.00

Workaround: None.

CSCdy01951

Symptom: Unnecessary alarms are triggered when BXM sends slot errors to SWSW.

Conditions: The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed.

Workaround: None.

CSCdy05515

Symptom: Current BXM firmware only support a few statistics counters. In order to enhance customer operation and maintenance capability, a few new statistic counters have been added. The detail description about the new created statistics and associated CLI commands and MIBs can be found in the latest VSI document. See DDTS case CSCdy05597 (SES and MIBs).

Conditions: All previous FW do not support the new connection statistics.

Workaround: Not applicable.

CSCdy13987

Symptom: Newly added routed SPVC carries counter values of previously deleted SPVC.

Conditions: Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values.

Workaround: Problem is fixed in MFW (MF20).


Anomalies Fixed in MFV

Table 41 lists the anomalies that are fixed in MFV.

Table 41 Anomalies Fixed in MFV 

Bug ID
Description

CSCdr55738

Symptom: Switchyred on APS 1+1 trunks is taking longer than 250 msec.

Conditions: Performed switchyred on APS 1+1 with SWSW 9.3.10 and BXM FW MF17.

Workaround: Unknown.

CSCds20584

Symptom: BW change by cnftrk command does not change ER stamping BW.

Conditions: When the AR ABR STD connection is programmed and the bw of trunk is changed by the cnftrk command. The changed BW does not take effect.

Workaround: Manually reset the card.

CSCdu09831

Symptom: APS fails when working backcard (active or standby) is removed from chassis when working front card is active.

Conditions: The working front card has to be the active card when working backcard is removed. This occurs when APS 1+1 ITUT non-revertive bi-directional configuration SWSW 9.2.34BXM fw MFJ.

Workaround: In operational situations always have the protecting front card and protecting backcard as active. Any failures will then switch ok and either backcard can be swapped while protecting front card is active.

CSCdv86732

Symptom: Incorrect values for Path Unavailable Seconds statistics are displayed under dspplyslnstathist. The displayed counts maybe higher than expected. For example, over a 900 second period, 910 Path UAS counts may be displayed.

While Path UAS stats are referred to specifically, other duration statistic counts could be affected as well.

Conditions: The problem occurs under the following conditions:

BXM line or trunk

The line or trunk is in major alarm (e.g. LOS, AIS, YEL)

Statistics are collected on the line or trunk to report the duration of the alarm condition (e.g. UAS).

The automatic trunk/line loopback test is disabled using the cnffunc command.

Workaround: None.

CSCdw06552

Symptom: Conns should stop passing traffic when dnpnport on UNI port on SES.

Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node.

Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX 8850 (PXM45) node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic.

When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells.

Workaround: Unknown.

CSCdw21798

Symptoms: Forced switchapsln when secondary section has failed is accepted.

Conditions: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1.

Workaround: Unknown.

CSCdw51601

Symptom: dspportstats on BXM shows Rx as Zero even the port has traffic passes in both directions.

Conditions: Not every single port has this problem. However we found multiple cards in the customer network have this issue. All the problem ports are T3 ports.

Workaround: None

CSCdw81944

Symptom: APS switch options 4,5,6 should not be allowed on AnnexB protocol.

Conditions: Upon switchapsln options 4, 5, 6.

Workaround: Unknown.

CSCdw83849

Symptom: APS 1+1 configured between AXSM/B and BXM running ITU-AnnexB protocol:

APS Lockout request (on BXM) doesn't keep selector position.

Conditions: APS Setup: MGX8850 (AXSM/B) ----> BPX (BXM)

APS 1+1, AnnexB Trigger:

1. On AXSM/B, apply APS force switch from Working section 1 (WS1) to WS2.

2. On BXM, apply lockout request, selector switches to WS1 which is incorrect. Lockout should indeed freeze selector position to WS2 in this scenario.

Workaround: Unknown.

CSCdw94327

Symptom: With 1:1 configuration; either WL or PL in LOS, BPX always sends RDI-P to AXSM/B.

Conditions:

1. Configured Intra 1:1 APS.

Forced switchaps W->PLine for both APS lines. Active on Plines.

2. Removed the WL-Rx from remote ends.

Active stayed on PLines, both lines in Minor alarms. Remote node receives RDI-P on the failed line.

Workaround: Unknown.

CSCdx05529

Symptom: Removing cable on protection line followed by switchyred card on remote node cause remote Yel major alarm on the trunk.

Conditions: It only happened with ITUT protocol with APS 1+1 mode

Workaround: Unknown.

CSCdx29896

Symptom: VrmRetLcnResources CD error logged on BXM.

Conditions: Run AutoRoute/MPLS/PNNI on BPX network. Three partitions (2 MPLS, 1 PNNI) are on an interface with a VC Merge Parent connection.

Workaround: Unknown.

CSCdx32780

Symptom: Card went to Failed state during normal operation with card error: rt_task.c 1258 Task low on real time, SRCID = 4.

Conditions: This symptom occurs with SWSW 9.3.36 SPVC connections and BXM FW MFU.

Workaround: Unknown.

CSCdx49312

Symptom: SES cannot add PVC with PCR = linerate.

Conditions: With old SES image and BXM image, SES does not allow adding connections, and CLI rejects.

Workaround: Use BXM MFV and related SES image (1.1.79).

CSCdx52531

Symptom: APS standby CD to active but no response to BCC after reset active BXM.

Conditions: Enable VSI partition for MPLS and with APS configuration on BXM on BPX.

Workaround: Manually reset BXM.

CSCdx69563

Symptom: Continuous 105 and CD errors logged on BXM cause spvc down on SES.

Conditions: Configure 100K SPVC on BPX with SES.

Workaround: Unknown.

CSCdx73291

Symptom: Fatal card error happened on BXM card in slot 9 after doing a full hitless rebuild on node. The card error should be a Non Fatal card error.

Conditions: A full hitless node rebuild was done on a node with many connections. This problem is related to a temporary HDLC queue overflow and should not be a fatal error.

Workaround: Unknown.

CSCin03340

Symptom: BXM sends ILMI trap with incorrect number of PVCs

Conditions: The SWSW 9.3.40 feature—configurable number of changes per ILMI trap—needs support from the FW when ILMI is run by the card.

Workaround: Unknown.


Anomalies Fixed in MFU

Table 42 lists that anomalies that are fixed in MFU.

Table 42 Anomalies Fixed in MFU 

Bug ID
Description

CSCdt90381

Symptom: A small outage (approx 10 msec) occurs on VPCs terminating/originating on BXM.

Conditions: This will occur only during hitless rebuild.

Workaround: None.

CSCdu21825

Symptom: The WINGZ shows the RX Network stat as zero even when data flows through the network.

Conditions: This occurs only on a BPX-SES Network.

Workaround: The data at the CLI shows the correct statistics, For right now the cli data can be used instead of WINGZ.Or Use MFU or later image.

CSCdu71237

Symptom: BXM card did not automatically switch to standby card

Conditions: This symptom occurs when Non Fatal Error "0xc000002" occurred on BXM trunk card, and the traffic worsened.

Workaround: None.

CSCdv31049

Symptom: BXM sets K1 Tx to Force Switch instead of Reverse Request even though remote had already been sending a Force Switch. BXM, however, maintains the correct line.

Conditions: Remote end already had a Force Switch to Working line in effect, and local BXM receives a user command to do a Force Switch to the Protection line.

Workaround: Clear the BXM Force switch command.

CSCdv89925

Symptom: ACR is only 10 when VC shaping is enabled for UBR con

Conditions: Trunk VC Shaping feature on BXM card is configured between two nodes. UBR connections are routed between the nodes.

Workaround: None.

CSCdv77996

Symptom: dspapsln reports wrong info w.r.t. aps when one of the yred cards is out.

Conditions: This bug fix is available in firmware release MFR, but swsw bug fix should be there in order to have the complete solution.

SWSW bug: CSCdw35862 9.3.30 MJ01

Further Problem Description: When one card of aps pair is removed, then reset dspapsln shows lines as ok. Should show card failed or missing.

CSCdw06552

Symptom: Conns should stop passing traffic when dnpnport on UNI port on SES.

Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node. Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX Release 2 node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic.

When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells.

Workaround: None.

Note This is a partial fix and relies on a SES DDTS CSCdv48496 for resolution.

CSCdw21798

Symptoms: Forced switch when secondary section has failed is accepted.

Conditions: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1.

Work around: None.

CSCdw25074

Symptom: When inserting 1E-03 errors into the whole frame of STM-4 trunk 3.1 (errors inserted in the direction A to B) BPX A becomes unreachable i.e. cannot telnet to BPX A. VT to A from another BPX times out and there's an HPOV event stating that the link is down to A.

The other nodes in the network remain reachable. BPX node log shows that the BCC has a suspected failure (Which indicates corruption of the BCC self test)a few minutes after inserting the errors into the trunk at B.

Removing the errors from the trunk results in BPX becoming reachable. Same problem seen with the other BCC active. This is consistently reproducible. If reroutes on another trunk (e.g. trk 1.1) are taking place when the errors are being inserted into trk 3.1, the connections (which are pref 'd' onto trk 1.1) remain derouted until the errors are removed from trk 3.1.

Conditions: Errors inserted at 10 -3 in one direction from A to B cause A to go unreachable. Found in lab environment running 9.2.38 with MFN firmware on 155 and 622 optical card types.

Workaround: DNTRK to force a reroute.

CSCdw53395

Symptoms: Traffic disrupted in the via node. No ais is propagated to other master end if slave end port is down.

Conditions: This symptom mostly occurs when MGX 8850 (PXM45) is connected to SES.

Workaround: None.

CSCdw54957

Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX (PXM45).

Conditions: This symptom occurs in 9.3.3i MFR.

Workaround: None.

Further Problem Description: When there is a congestion on MGX egress port, MGX 8850 (PXM45) sets EFCI=1 for all SPVCs/xpvcs on that port to the downstream.

CSCdw62999

Symptom: BPX sends a wrong value for K1.

Conditions: This symptom occurs in APS interop testing between BPX and AXSM/B OC-3.

Workaround: None.

CSCdw63238

Symptom: BXM sends RDI trap to SES which does a dnpnport

Conditions: Config is BXM UNI with aps 1+1, SW 9.3.35, FW MFR, SES SW 1.1.71.

Workaround: None.

CSCdw75999

Symptom: Dspconstats on an SES CLI for an SPVC connection shows that clp0 discards and clp1 discard counts are interchanged.

Conditions: This symptom occurs in SES 1.0(14), BXM FW MFR.

Discards, due to the policing action, are reported incorrectly in dspconstats cmd. Discards due to congestion are reported correctly.

Workaround: None.

Update BXM FW to MFU or later.

CSCdw88723

Symptom: Say BXM1 is a BME card. BXM2 is normal BXM card running fw image MFC-MFT. Multicast root connection runs from BXM2 to BXM1 and fans out to other connections at BXM1 port 2. We will see high number of ingress cell discards on the root connection at BXM2.

Conditions: This symptom occurs with BXM2 running f/w image between MFC to MFT.

Workaround: None.

Use firmware image MFU or later on BXM2.


Anomaly Fixed in MFT

Table 43 lists the anomaly that is fixed in MFT.

Table 43 Anomaly Fixed in MFT 

Bug ID
Description

CSCdw54957

Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX (PXM45).

Conditions: This symptom occurs in SWSW: 9.3.3i, BXM FW: MFR.

When there is a congestion on MGX egress port, MGX (PXM45) sets EFCI = 1 for all SPVCs/XPVCs on that port to the downstream.

Workaround: None.


Anomalies Fixed in MFR

Table 44 lists the anomalies that are fixed in MFR.

Table 44 Anomalies Fixed in MFR 

Bug ID
Description

CSCdv90721

Symptom: The prevalent symptom is Tx BIP 16 and B-Frame Parity slot errors on BXM-622 or BXM-155 cards. Occasional SIU Phase and Rx BIP 16 errors may also occur on BXM-622 and BXM-155 cards depending on the severity of the problem.

Conditions: This symptom can occur with any version of BXM firmware on BXM-622 or BXM-155 cards. The aggregate cell transfer rate of the BXM card is 1,412,832 cells/second so the problem can occur on BXM-622 or BXM-155 cards even if the load on each line is well below line rate. The problem occurs during oversubscription when multiple high speed cards have traffic destined for a particular card through the switching fabric.

Workaround: To solve the BCC-4 software error 742 problem, upgrade switch software to 9.1.22, 9.2.31, 9.3.00 or later.

CSCdw16362

Symptom: The BXM card changed the state from active to empty for a particular slot and failed to communicate with the BCC.

Conditions: Switch Software was upgraded for the particular BXM and statistics were enabled before the current state. Now the particular slot is in empty state although both front and back cards are present for the slot.

This loop happened because of spvc statistics task. It happens when new spvc_config_stats command comes in the vsi message with more than currently configured stat ids. Due to this the data base will be updated. During this update some flag was not set properly and it leads to a loop.

Workaround: A workaround is not known other than the physical removal of the card. Or, use MFR or later images.

CSCdm50659

Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms.

Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable.

Workaround: Lowering the alarm threshold for MAJOR and MINORHCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR.

These thresholds are as low as they can be set currently.

CSCdt82384

Symptom: APS trunk built on bxm-155-4d. sf and sd thresholds set to 5 and UNI-direction non-revertive switching with cnfapsln.

Random logic errors inserted into the working pair of the trunk to observe protection switch at sf threshold.

Good switch at 1 in 103 and 105 but when 1 in 104 inserted trunk goes unstable repeatedly switching from working to protection and vice versa.

Trunk continues to toggle until errors removed.

Conditions: This symptom occurs with BXM-155 enhanced cards using APS card cage and injecting 104 error rate into one of the working lines.

Workaround: None.


Anomalies Fixed in MFP

Table 45 lists the anomalies that are fixed in MFP.

Table 45 Anomalies Fixed in MFP 

Bug ID
Description

CSCds47753

Symptoms: Card error will happen in standby "VrmDekConnEndPoint Try to delete".

Conditions: When standby syncs up with active, it tries to delete a not existing connection.

Workaround: The card error indicates that there is a invalid try of deleting a non-existing connection. It should not create any problem in existing or new connection.

CSCds75845

Symptom: There is no ER stamping cell generated from BPX in SES environment. Although, CI is set to be off and ER is on by using cnfabrparam, CI cells are still observed where there is congestion.

Conditions: This symptom occurs when the connection is routed by PNNI (created by using SES controller).

Workaround: None.

CSCdt55356

Symptom: After configured status of all nni links to dwon at SES node svcpop2, then configured all links up. while the 100k SPVC connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by itself.

Condition: MGX nodes p2spvc4 and p2spvc3(via node) both have standalone PXM45-B card.

Initially 100K spvc connections have been established between p2spvc4 and SES node svcpop2 end points.

Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.

CSCdu21842

Symptom: ILMI does not report correct status of the ATM PVCs when Protocol by card is enabled.

Conditions: When a BPX is connected to a router through a BXM card and ILMI Protocol is run by the card.

Workaround: None.

CSCdu04976

Symptom: Around 200 SPVCs stuck in Rx ais after resetting BCC.

Conditions: Resetting the BCC during resync with a SES controller causes this problem as the AIS bit-map is cleared.

PXM: 1.1(50.100)A1

BXM: MF15

SWSW: 9.3.3E

Workaround: Unknown.

CSCdu29758

Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value.

Conditions: The first couple of loopback cells received have incorrect VCI values.

BXM=MFJ, BPX 9.2.31

BXMa-BPX==BPX-BXMb<-> ADTECH (OAM F4Loopback)

Workaround: None.

CSCdu63175

Symptom: LOF and Bert_SD alarm uncleared on BXM.

Conditions: This symptom occurs with 1+1 aps with bi-dir on BPX and MGX.

Workaround: Perform a switchcdred/switchyred on BXM.

CSCdu89263

Symptom: When running XLMI on a BXM port which is connected to an AXSM enni port, BXM XLMI sending slot 0 and incorrect port number in the node status msg.BXM XLMI is configured with polling disabled.

Conditions: Run XLMI and disable the polling.

Workaround: Enable the polling, then disable it.

CSCdv18519

Symptom: In reading MF* BXM MFM fw release notes, it was discovered the Stats collection level 0 is no longer supported in MFM and beyond. Ie, Stats level 0 supports 32k cons stats level 1 16k cons.

Conditions: This symptom occurs in 9.3.3V. MF21.

Workaround: See MFM release notes Stat level 0 no longer supported on Legacy BXM cards.

CSCdv21924

Symptom: By running XLMI, when the NodeStatus message didn't get ack back, it would retry every T396 (polling timer), instead of using the correct T393 timer.

Conditions: This symptom occurs when XLMI is configured and link/line is down. XLMI NodeStatus retry mechanism kicks in. But a wrong timer T396 was used for retrying interval.

Workaround: It does not cause any service interrupting or deteriorating and it won't show up under normal operating condition. If a specific NodeStatus retry interval is really needed, one can configure T396 to that value temporarily before the fix is in.

CSCdv21999

Symptom: BXM sends a port failure VSI msg to the controller after switchyred.

Conditions: This symptom occurs under yred configuration and running LMI on PNNI port on this card. Switchyred so the standby card become active and the port on standby card from failure state to OK.

Workaround: None.

CSCdv32466

Symptom: A enni port is still showing as failed after switchyred when it becomes OK.

Conditions: Yred and APS 1+1 are configured. XLMI is runng on the enni port. On the previous active card, the port was in a fail state. When the failure got recovered very quick during the switchyred, BXM missed the OK report to BCC, so BCC still shows this port as fail state.

SW and FW version: 9.3.30 MF25

Workaround: None.

CSCdv43448

Symptom: The command dsppnports shows the port in "LostConnectivity" state.

Condition: Disable ilmi on BPX using cnfvsiif.

Work Around: Reset the card. This problem happens only in MFN due to the chkin done in Aug 13 2001. Or use Firmware image newer than MFN.

CSCdv52437

Symptom: Comm Failure after Working line experiences Remote Yellow.

Conditions: APS 1+1 bidirectional mode GR-253 and ITU After remote experiences LOS on Protection line, the local active Working line will have a Remote Yellow alarm. This alarm eventually causes a Communications failure, and traffic will be rerouted.

Workaround: Use unidirectional mode.

CSCdv57400

Symptom: Customer removes commands under ATM interface or tears vc down and up again the router will send two traps to the BXM VSI port but only looks like it is re-acting to the first trap hence the remote router will receive AIS and then transmit RDI. The connection will never come out of this state unless the remote end from the SES is bounced.

Conditions: You must be attached to a PNNI VSI port on the BXM.

Workaround:

1. Switch ILMI off on the port.

2. Disable oam-manage on the routers.

CSCdv58157

Symptom: On BXM switchover, the VSI abr VP falls to MCR.

Conditions: This symptom occurs with BXM FW up to MFN (MF30). Standby BXM should collect this VP abr connection during initial data transfer phase. ie. Standby BXM is inserted later than active card or is reset after connection provisioning. Check with 'rsh slot# sabre GetSabreParams sabre# lcn#' and look for 'Path con' field. Switchover to stdby in this case will cause the problem.

Workaround: Reassert/resync all the connections. Use firmware later than MFN.

CSCdv62493

Symptom: BXM does not send Node status counters to BCC.

Conditions: XLMI is running on card.

Workaround: None. This is an enhancement.

CSCdv66806

Symptom: Dax conn does not get rerouted if added when slave interface is down; and later when slave interface is brought back up.

Conditions: This is applicable only for dax conns on SES - not on MGX (PXM45).

Workaround: Delete and re-add the dax conn when the slave interface is up. It will get routed.

CSCdv86166

Symptom: A feeder trk shows UNREACHABLE after switchyred, while it was actually uprunning without any communication problem.

Conditions: When running FDR-LMI in a yred pair, the FDR trunk was in a fail state. After switchyred, the FDR trunk changed its state to be OK, however, dspnode still shows this fdr trk was in the unreachable state.

Workaround: This is not service impacting, although the fdr trk shows as unreachable. To get the correct state, reset the card.


Anomalies Fixed in MFN

Table 46 lists the anomalies that are fixed in MFN.

Table 46 Anomalies Fixed in MFN 

Bug ID
Description

CSCds08461

Symptoms: Incorrect operations (SF_LOW sent) after detecting mode mismatch.

Conditions: BXM is configured as APS 1+1 Bidirectional mode, and is attached to a node configured as 1+1 Unidirectional.

Workaround: Manual administrative intervention to synchronize both nodes to the appropriate mode.

CSCds53524

Symptom: SWLOG error 109 on BPX.

Conditions: This symptom occurs with SWSW 9.3.10, Cards: BXM 155 while adding connections between BPX nodes found a swlog 109.

Workaround: A workaround is under investigation.

CSCds78285

Symptom: Connections in failed or BuildingVC state.

Conditions: CAC policy was not downloaded to some of the BXMs.

Workaround: None.

CSCds91102

Symptom: BXM card interfaces went into provisioning state.

Conditions: BXM card was reset and pxm did a resync.

Workaround: None.

CSCdt35547

Symptom: Cell drops at a cbr connection when a cbr connection and an abr connection are congested at an enni trunk

Conditions: This symptom occurs when congestion exists at an enni trunk in a AR/PNNI hybrid network.

Workaround: None.

CSCdt38471

Symptoms: The available BXM TCB buffer went down to zero and the card got stuck.

Conditions: This happened in the 100k SPVC devtest setup. The problem can be reproduced by performing switchyred on two BXM redundancy cards.

Workaround: The reasons to cause TCB buffer leakage were found. Furthermore, the holes in the firmware code have been sealed. The fix will be included in the firmware releases MFM or later.

CSCdt41728

Symptoms: Card error VrmRetLcnResources was observed.

Conditions: This bug is reproduced in 100K network when port 1.2 of orses7, which is connected to adtech is seeing temporary LOS. This happened when Adtech is power cycling. Also 1.2 is the end point of 6666 routed SPVCs.

Workaround: None.

CSCdt53756

Symptom: SES had huge CDV value compared to MGX 8850 PXM45.

Conditions: This symptom always occurs.

Workaround: None.

CSCdt55356

Symptom: After configured status of all nni links to dwon at SES node svcpop2, then configured all links up. while the 100k spvc connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by itself.

Conditions: MGX nodes p2spvc4 and p2spvc3 (via node) both have standalone PXM45-B card. Initially 100K spvc connections have been established between p2spvc4 and SES node svcpop2 end points.

Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.

CSCdt68427

Symptom: After dellp is done traffic is not right when VP connection and cnfln VC shaping enable.

Conditions: A dellp was done on a VP with VC shaping enabled.

Workaround: None.

CSCdu08104

Symptom: AR connections do not pass traffic or some links be in comm fail condition.

Conditions: The intermediate devtest release for VC-merge project had a problem. On downloading this image would some time bring down the trunk.

Workarounds: There are no known workarounds.

CSCdu12049

Symptom: BXM Card switches on Nortel exercising to test APS Link. This happens everytime test is completed.

Conditions: BXM card is not reacting to K1 bits correctly.

Workaround: There are no known workarounds.

CSCdu20728

Symptom: One end of the trunk experiences unbalanced Rx/Tx high priority cells in dspqbinstats. Any CBR traffic on the trunk will not be seen in the CBR QBIN stats.

Conditions: Unknown.

Workaround: None yet.

CSCdu22039

Symptom: F4 F5 Code mapping modifications.

Conditions: None.

Workaround: None.

CSCdu23725

Symptom: Attempt to configure the booking factor on a UNI port failed. Err msg: ERROR: Switch Response returned Failure

Conditions: The conditions for the error are unknown since the CAC feature on the UNI port hasn't been studied before and there were many activities such as addcon, cable failure prior the problem detected.

Workaround: Unknown.

CSCdu26023

Symptom: When PNNI&MPLS partitions are configured in a interface with no common pool of bandwidth, only one of the partition will be working fine and the other partition will not come up.

Conditions: When PNNI&MPLS is configured in a interface with no common pool of bandwidth, due to the rounding up of the bandwidth for each service type in PNNI by policy parameters, the total bandwidth of a partition, resulted from adding bandwidths of all service types, will go beyond the max bandwidth of both partitions. Because of this, only the first partition will succeed and the other partition will be rejected by cac.

Workaround: Provide at least 20 cells of common pool using cnfrsrc command.

CSCdu29758

Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value.

Conditions: This condition occurs with BXM=MFJ, BPX 9.2.31.

Setup BXMa-BPX==BPX-BXMb<-> ADTECH (OAM F4Loopback).

Workaround: None.

CSCdu44350

Symptom: Although equipment is NOT connected to PROT Line, Standby Line Alarm Status is OK on dspapsln. This symptom appears when CDERR is logged at timing of addapsln.

Conditions: Standby line is not connected to equipment.

Workaround: None.

CSCdu48766

Symptom: VI programming on enhanced cards is improper.

Conditions: Virtual Trunks were dropping all cells.

Workaround: None.

CSCdu50129

Symptom: While cwm coldstart then down two links with 32K connections at orses2 nodes. cwm can not sync up with orses2 node any more and stuck in mode 2.

Condition: There are 50K spvc dax connections at node orses2.

Workaround: CWM needs to coldstart again.

CSCdu59151

Symptoms: APS commands switchapsln F/M on PXM fails.

Condition: BXM running image MF20 with APS configured as ITU-T Annex A and the remote node is any box that strictly adheres to G.783 Annex A, specifically regarding not sending "mode" bits.

Workaround: Do not use image MF20 for ITUT Annex A.

CSCdu59240

Symptom: Alarms on 1:1 APS BPX side uncleared after 1:1 aps back to Bi-dir on MGX side.

Conditions: This symptom occurs with 1:1 aps with bi-dir on BPX and 1:1 aps with uni-dir on MGX.

Workaround: Unknown.

CSCdu62336

Symptom: Code clean-up.

Conditions: None.

Workaround: Unknown.

CSCdu67053

Symptom: When BXM OC-3 card was downgraded from M.F.21 to M.E.K continuous card errors were being logged.

Condition: M.E.K. FW was burned on the standby card that was configured for Y-Red and had APS 1+1 lines configured with traffic.

Workaround: Use matching firmware versions on YRED pair.

CSCdu75130

Symptom: Active card in the y-red pair continuously making the connections.

Resource usage in active and standby card differs.

Conditions:

1. Active card up & running

2. Intracard connections between two interfaces on the same BXM.

3. Booking factor less that 100% on above interfaces.

4. Stdby card is inserted at this time.

Workaround: Resetting both the active and sdtby cards at the same time.

CSCdu82229

Symptom: ILMI polling when "Protocol by Card" is configured to "Yes" is inconsistent and unpredictable.

Conditions: When ILMI is running on card and its peer is running version 3.0/3.1, the polling interval timer was set with wrong value, which was the 1/5 of the configured polling interval. For correct behavior, refer to SCM note of this bug.

Workaround: Use OAM instead of ILMI.

CSCdu87060

Symptom: pnport on SES goes into building vc state.

Condition: Change the signaling vpi using cnfpnportsig.

Workaround: Reset the bxm card.

CSCdu88418

Symptom:

1. After SwSw upgrade from 9.2.34 -> 9.3.3W, BXME OC-12 card with APS 1+1 setup logged swsw err. 105 and card errs.

2. This problem have been observed several times before.

Conditions: This event happened after SWSW upgrade.

Workaround: Need DE input.

CSCdv08977

Symptom: Unable add PNNI VSI connections on a y-red BXM pair when upgraded from BXM to BXM-E. Standby card not in SYNC with active card. Policy parameters for the first interface/partition on the active card missing.

Conditions: This symptom occurs with BXM Firmware MFN and before. Any Sw/Sw supporting hot upgrade on BXM. Upgrade procedure is followed to upgrade a y-red pair of BXM from BXM to BXM-E cards. Note that the policy params for the first interface/partition on the active card are messed up. If this interface has booking factor less than 100% then above defect will surface.

Workaround: Reset both the BXM cards after upgrade. Or, use MFN or later BXM FW before upgrade and on enhanced cards.

CSCdv17853

Symptom: Fix compiler warnings.

Condition: None.

Workaround: None.

CSCdv18775

Symptom: BXM card err. ilmi_task.c 323 pIlmiWd: SoItcSend Failed (currsize 500).

Conditions:

1. This problem occurs after burning BXM FW MF21 -> MJ04.

2. It occurs after switchyred.

3. It occurs after rerouting of connections.

Workaround: Need a fix from BXM FW DEs.

CSCdv30471

Symptoms: Active and Standby card do not sync up in terms on number of connections. VSI yred pair.

Conditions: FW image prior to MFN. When VSI partition 3 is used by controller.

Workaround: Do not use partition 3.

CSCdv30755

Symptom: Traffic discontinuity on SPVC connections on consecutive switch-yreds on BXMs.

Condition: To begin with, BXM with UNI interfaces should have de-routed connections which are later routed properly. This can happen during initial provisioning of the SPVCs or on re-routing the conns after trunks (NNI) go down and up.

Two or more consecutive switchovers on the BXMs hosting UNI interfaces (persistent endpoints of SPVCs).

Workarounds:

1. Reroute/resync all the connections and reset the stdby card once active card has all conns.

2. Do no do BXM switchovers more than once.

3. Reset standby card before doing the first switchover.


Anomalies Fixed in MFM

Table 47 lists the anomalies that are fixed in MFM.

Table 47 Anomalies Fixed in MFM 

Bug ID
Description

CSCdr16007

Symptom: ILMI trap atmfVccChange returns invalid agent-addr (48.48.48.48), while the correct one shall be (0.0.0.0). "ERROR Invalid agent-addr".

Conditions: The error happens during adding or deleting connections.

Workaround: None.

CSCdr44694

Symptom: ILMI trap atmfVccChange returns incomplete information. "variable-bindings (none)".

Conditions: The error happens during adding or deleting connections.

Workaround: None.

CSCds06835

Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk.

Conditions: CC traffic is passed across virtual trunks.

Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.

CSCds74110

Symptom: The second leaky bucket doesn't adhere to the leaky bucket algorithm.

When testing a VBR connection on a BXM-E3 you can burst over the expected value for the connection.

Conditions: A connection can exceed his calculated burst size for a VBR connection.

Workaround: There is no workaround.

CSCds75477

Symptom: When a delay of over 200ms is introduced to a trunk with a Addtech tester, 75% of the time the tstdelay result gives a reading lower than the actual RTD. ie we would expect over 400ms but get 150ms.

Conditions: The tstdelay test reports inaccurate results.

Workaround: None.

CSCdt21547

Symptom: There is no command available to clear SPVC statistics on SES controller.

Conditions: SPVC statistics cannot be cleared via SES

Workaround: None.

CSCdt36060

Symptom: The tstdelay command intermittently fails.

Conditions: Tstdelay intermittently failed when BPX is configured as a segment endpoint for VCC and VPC established between a MGX abd BPX

Workaround: None.

CSCdt43471

Symptom:

1. Card errors of "Non Fatal Error id: 0x12000003"

2. Unknown vpi/vci in dsptrkstats and dspportstats

Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs.

Workaround: None.

CSCdt44670

Symptoms: The available BXM TCB buffer went down to zero and the card got stuck.

Conditions: This happened in the 100k SPVC setup. The problem can be reproduced by performing "switchyred" on two BXM redundancy cards.

Workaround: None.

CSCdt45820

Symptom:

1. Card errors of "Non Fatal Error id: 0x12000003"

2. Unknown vpi/vci in dsptrkstats and dspportstats

Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs.

Workaround: None.

CSCdt45966

Symptom: Resync process starts and SPVC connections are re-asserted on BXM switch over.

Condition: Intra-slave (DACS) SPVC connections are conditioned (AIS/Abit generation) due to external factors.

Workaround: None.

CSCdt46282

Symptom: On SPVC connection CDVT programmed is not observed when testing.

Conditions: When user tries to set up the CDVT value to less than 10ms due to a bug in the firmware BXM uses the value 250ms.

Workaround: Use values above 10ms.

CSCdt48062

Symptom: Ports remain in "provisioning" state on SES.

Condition: Enable /disable the partitions on BXM interfaces (specially on engineering BXM images after MFJ between MF08 to MF12).

Workaround: Do not re-enable the partition after disabling it. BXM need to be reset if re-enabled configuration has to take effect.

CSCdt58185

Symptom: The CESM-E8 dropped cells after 1/2 hrs. (Seeing the clock synchronization problem.

Conditions: This symptom occurs when selecting a clock from the trunk or passing the sync along the trunk. BXM-OC3-D or DX (enhanced) card did not behave properly.

Workaround: Use any other type of BXM card except for the BXM-OC3 enhanced.

CSCdt78404

Symptom: 70K SPVCs stuck in Rx side AIS after resetsys/switchcc on PXM overnight.

Conditions: SPVCs stuck in AIS state.

Workaround: Reset BXM card.

CSCdt75817

Symptom: Asymmetric ABRSTD connections using VSVD will not ramp up ACR to higher than the lower PCR setting.

Conditions: It happens when an asymmetric ABR connection is added or modified.

Workaround: The problem was identified as incorrect programming SABRE chip and has been fixed in MFM or later FW.

CSCdt80542

Symptom: BXM does guarantee at least mcr value on abr connection on a congested port.

Condition: Traffic was pumped on a congested port having abr conns.

Workaround: Unknown.

CSCdt88482

Symptom: The available TX cell rate is lot smaller than available RX cell rate. The available TX cell rate for signalling is a huge negative number

Condition: 100K spvc connections have been established between MGX and BPX nodes.

Workaround: Reset BXM card.


Anomalies Fixed in MFL

Table 48 lists the anomalies that are fixed in MFL.

Table 48 Anomalies Fixed in MFL 

Bug ID
Description

CSCds15145

Symptom: Max BW could be configured as less than Min.

Conditions: This might happen as the policy parameter might not be checked for the consistency.

Workaround: Do not configure Max below min.

CSCds06835

Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk.

Conditions: CC traffic is passed across virtual trunks.

Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.

CSCds75221

Symptom: When Issuing the command "dspconstats" for abr or ubr connection it does not report the CLP0 and CLP1 correctly.

Conditions: Statistics for abr and ubr are not updated.

Workaround: None.

CSCdt38554

Symptom: After executing resetsys on the node (svcmgxpxm45) pxm1 cards. There are two ports stuck in building vc.

Conditions: The node (svcmgxpxm45) has 100k routed spvc connections.

Workaround: Unknown.

CSCdt45966

Symptom: Checksum calculation is not correct in BXM.

Conditions: Connection conditioning occurred via bulk set cmd.

Workaround: Uppnport/dnpnport on UNI and NNI port, and do switchyred to kick resync.

CSCdt48062

Symptom: Port gets stuck in building VC state.

Conditions: This symptom occurs with connection admission control.

Workaround: Establish connections of various service type and bandwidth requirements.


Anomalies Fixed in MFK

Table 49 lists the anomalies that are fixed in MFK.

Table 49 Anomalies Fixed in MFK 

Bug ID
Description

CSCdt21322

Symptom: BXM load info returned to controller is wrong when maxbw set to 0.

Conditions: Reproducible.

Workaround: None.

CSCdp16050

Symptom: maxvc functionality for CAC not working.

Conditions: Reproducible.

Workaround: None.

CSCdt04632

Symptoms: For a vsi partition, the reporting available number of LCN is greater than the maximum number of LCN configured for that partition.

Conditions: This symptom occurs when the port group unused LCN is less than the maximum LCN configured for the partition, and the unused LCN for the port group plus the LCN that still left from the reserved (min-curr) is greater than the max of the partition.

Work around: None.

CSCds85653

Symptom: BXM card error of "cb_if.c 1588 CbCoreTxEvent(): Failed core_cbmsg_put: return.

Conditions: This symptom occurs continually doing switchcc with large amounts of AR/SPVC connections.

Workaround: Reset BXM card.

CSCds76142

Symptom: BXM card shows standby-failed status.

Condition: Download firmware on standby card.

Workaround: Reset BXM card.

CSCds65105

Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than'To Port'.

Conditions: This symptom occurs with DAX conn from BXM-622 port 1-2 on the same node with ADTECH generating traffic.

Workaround: None.

CSCdr19696

Symptom: User never gets to know when the line is out of SD/SF condition. both the aps lines always show in OK state in dspapsln.

Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition.

Workaround: Use rsh command to get all the aps line status.


Anomalies Fixed in MFJ

Table 50 lists the anomalies that are fixed in MFJ.

Table 50 Anomalies Fixed in MFJ 

Bug ID
Description

CSCds61912

Symptom: After downloading new firmware(MF30), card in failed state.

Conditions: This symptom occurs when downloading MF30 firmware release.

Workaround: Do not use MF30 which is a development release between MFH and MFJ.

CSCds11506

Symptom: Min guaranteed cell rate shows a cell less than configured.

Conditions: Set min BW to say 3333334 and policy BW% to 5859.

Workaround: Increase the minBW by few cells.

CSCdr19696

Symptom: User never gets to know when the line is out of SD/SF condition. Both the aps lines always show in OK state in dspapsln.

Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition.

Workaround: Use rsh command to get all the aps line's status.

CSCds32845

Symptom: Connection commits rejected with reason 'no resources even when resources are actually available.

Conditions: Enable/disable a virtual trunk.

Workaround: Reset the BXM after disabling a VT on any interface on the card.

CSCds37237

Symptom: When upgrade BXM firmware image to BXMMFH from images between BXMMFC-BXMMFF, if the network migration flag was enabled in a card before the upgrading, then after burning the new image to the card, the network migration flag becomes disabled mistakenly.

Conditions: The problem only happens to the card whose previous image is BXMMFC-BXMMFF, and the network migration flag was enabled before upgrading, and BXMMFH has to be the new image.

Workaround: Upgrading to image BXMMFH+ (not including BXMMFH), will not have any problem. network migration flag is always enabled, and no user command available any more to disable it.

Only for the situation you need to upgrade image to BXMMFH and your card's previous images is BXMMFC-BXMMFF, you may see the problem. The workaround is, issue either the "rsh <slot> cdcfg network dis" command before the upgrading, or "rsh <slot> cdcfg network ena" after the upgrading, to enable the network migration flag on BXMMFH.

CSCds59710

Symptom: Loss of traffic on a VPC connection added with VPI = 0.

Conditions: This symptom occurs with SWSW: 9.3.10.

BXM FW: MFF

The port on which the VPC connection has been added has a VSI ctrlr attached to it and the Ctrlr is usingVPI = 0 and VCI = x for its signalling channel.

Workaround: If a VPC connection exists with VPI = 0, on the port to which a Ctrlr is to be added, configure the signaling channel on the controller side to use a VPI other than 0.

CSCds63578

Symptom: SW errors 105 logged on BXM while adding VSI connections. Subsequent card errors saying CB_TASK restarted.

Conditions: This error sometimes happens when a VSI partition is enabled/disabled many times.

Workaround: Reset the BXM.

CSCds65105

Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'.

Conditions: This symptom occurs with DAX conn from BXM-622 port 1-2 on the same node with ADTECH generate traffic.

Workaround: None.

CSCds67854

Symptom: SPVC cannot be routed over the virtual trunk even when enough bandwidth and lcn are available. Routed connections discard some traffic.

Conditions: Route connections of different service types over the virtual trunks.

Workaround: None.

CSCds04137

Symptom: Channels remain mismatch after lockout is cleared

Conditions: In ITU-T Annex B protocol for APS, when a condition causes a switch to occur while a lockout request is present, the channel change will not resynchronize even after the lockout is cleared.

Workaround: No

CSCds53645

Symptom: ABR connections (PNNI) not programmed properly for redundant slave.

Conditions: This symptom occurs with switchyred.

When connection is added, redundant card is not there and inserted at later stage.

When connection is added, there is no redundant config; addyred at later stage.

Workaround: None.


Anomalies Fixed in MFH

Table 51 lists the anomaly that is fixed in MFH.

Table 51 Anomaly Fixed in MFH 

Bug ID
Description

CSCds14495

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

Conditions: When a card comes up and has never enabled the network migration flag for life time.This network migration flag is used for enabling dynamic partitioning and SPVC AIS, status report generations. By default, the flag is disabled.

Workaround: Use the "rsh <slot> cdcfg netmig en/dis" command to enable/disable the flag, then reset the card once in a lifetime.


Anomalies Fixed in MFF

Table 52 lists the anomalies that are fixed in MFF.

Table 52 Anomalies Fixed in MFF 

Bug ID
Description

CSCds08448

Symptom: ERS (explicit rate stamping) is working only first virtual trunk and NOT for subsequent VTs (standard ABR)

Conditions: When ERS is enabled on a card basis using "cnfabrparm", the mapping is done on a port-by-port basis. The port_vi is used but for virtual trunks, this mapping does not hold true. Need to change the mapping to the physical port.

Workaround: On any physical port, just set up one virtual trunks. Or a physical trunk. Multiple VTs on the same physical port will cause a problem.

CSCdr79610

Symptom: Change booking factor for a class of service, get rejected.

Conditions: When there are some connections established, and some of the class of service have used bandwidth exceeding their reserved, change booking factor for any class of the service may get rejected.

This is because it fails the check which should only be called when cos_min_bw in the policy parameters is changed. This check should not be called when booking factor is changed.

Workaround: Disable that partition, change the booking factor, then enable the partition again. Or keep the used_bw for all cos under teh cos_min_bw, you will be able to change booking factor freely.

CSCdr76334

Symptom: Connect OC3 port on BXM with 7200 router, connect 2 OC3 ports back to back. enable ILMI on router, and ILMI, protocol on card cnfrsrc VSI part 1 disable NebDiscovery on ports.when running cnfnodeparm 56 0|1 and With VSI disabled, peer info is transmitted to peer. delcntrl, and cnfrsrc deleting VSI partition, fails to disable Peer information as well.

Conditions: ilmi_enable_from_contrl bit was not cleared when delctrlr, or vsi partition deleted, thus vsi code kept issuing get requests and responding to peer information.

In AR/VSI hybrid networks, and for backward compatibility either BXMs w/o NebDisc, or swsw versions. Topo traps are not sent to downrev'd swsw versions, and are controllable by sw software for versions including the feature.

Code was added to properly support disabling of VSI functionality using delctrlr or cnfrsrc @ Bcc in addition to existing dnpnport @ the vsi controller. support for backrev'd cards added, and corrections to logic in Ilmi FSM state machine to properly send TopoTrap to BCC.

Workaround: None

CSCdr79936

Symptom: Stats files not generated/missing on some 15 minutes intervals.

Conditions: System time is changed at 15 minutes boundaries.

Workaround: Minimize system time and card config changes.

CSCdr83144

Symptom: Card error of "N. Fatal from 0x17: 0x25120075 0x809b5f90 0x367e 0x1."

Conditions: This symptom occurs with switchyred, switchcc or reset PXM when there are spvc connections with stats enabled.

Workaround: None.

CSCds11484

Symptom: Available cell rate reported by BXM is incorrect.

Conditions: Sum of the minimum bandwidths of all the interfaces on a BXM reaches OC12.

Workaround: Reduce minimum BW on all interfaces by half.

CSCdr89217

Symptom: Software Error Log of 9098

Conditions: This symptom occurs with cnfrsrc of partition 3 using MEB firmware.

Workaround: None.

CSCdr89966

Symptom: Card Error of 0x41030006.

Conditions: PXM controller is upgraded/re-booted.

Workaround: None.

CSCdp89085

Symptoms: The total call count becomes negative on the BXM interface. However, this problem has not been reproducible.

Conditions: If this problem happens, the following card error is displayed:

'vsi_rsrc_pfns.c 483 VrmRetLcnResources 3, 16316'

Workaround: A related bug CSCdr86894 which reported an incorrect number of total call counts, has been found to be the result of an uninitialized variable in vsi_rsrc_conn_pfns.c: VrmRsrcClrRCMP().

The debugging information embedded in this function may be helpful in verifying the negative call count problem if it is reproduced.


Anomalies Fixed in MFE

Table 53 lists the anomalies that are fixed in MFE.

Table 53 Anomalies Fixed in MFE 

Bug ID
Description

CSCdp05098

Symptom: Cell discards occur for ABRFST/ABRSTD conns when the traffic burst is greater than the MBS

Conditions: This occurs when the traffic burst size is fixed to 140000 cells at 70000 cps. The conn are configured with PCR=72000/72000, MBS=1000/1000 and ICR 7200/7200. This is the expected behavior since the configured MBS < the actual burst size.

Workaround: Increase the MBS and ICR using cnfcon.

CSCdr59731

Symptom: Port 11.1 is connected to 11.2 and ILMI are up and running on both ports. Enable neighbor discovery on 11.1, then 11.2.

The 0x71 responses/traps from BXM fw is not predictable. At least two variations are observed:

1. Port 11.2 has it's neighbor's info but port 11.1 does not.

2. Both port 11.1 and 11.2 only know the IP addresses of their neighbors. The Neighbor's IFName are missing.

Problem was observed in MF17, but code changes in more recent builds had already repaired the problem.

Conditions: When ILMI session restarts, remnants of IfName, IpAddr from previous session left. Clr/reset IfName, IpAddr in MIB, on ILMI session restart In FMSStart, pIlmiProcessFsmStart () calls a new function IlmiClrPeerAndSendTopoTrap (pcb_ptr->session_id).

CSCdr79936

Symptom: Stats files not generated/missing on some 15 minutes intervals.

Conditions: This symptom occurs when system time is changed at 15 minutes boundaries.

Workaround: Minimize system time and card config changes.

CSCdm16800

Symptom: Card error 0xc000007 appears in the card error log.

Conditions: This error indicates that an unknown type of cell which is not expected has arrived in the egress QE.

Workaround: Engineering has done in-depth investigation into this case. We are convinced the problem does not affect user traffic or the node in any other way. Therefore, the symptom will not be reported as a card error. The fix has been incorporated into MEE firmware.

CSCdp22930

Symptom: N/A

Conditions: Cbus rd/wr operations set up in the PUUMBA chip when performing cbus rcv/xmit.

Workaround: None.

CSCdp74680

Symptom: Even if the interface is in LOS, the spvcs do not generate ingress AIS into the network.

Conditions: Connection is added after the interface goes into LOS.

Workaround: None.

CSCdr44250

Symptom: Private image did not allow as many OAM cells to flow as public image.

Conditions: This occurred by undoing a hardware fix in a private image.

Workaround: This was never introduced into the Public view and no workaround is required.

CSCdr45986

Symptoms: Standby and active block checksum value do not match and resync happens on switchover.

Conditions: Active card has many spvc connections derouted it happens.

Workaround: None.

CSCdr71473

Symptom: Unreachable BXM, sw errors and cd errors on the BPX.

Conditions: LMI is enabled when controller either slow to respond or un-reachable.

Workaround: Disable LMI.

CSCdp97307

Symptoms: Executed "rsh <slot> vsi cm VsiIs " without parameter. The card will crash.

Conditions: Always.

Workaround: Pull out the card and reinsert.

CSCdr86894

Symptoms: Many ports have VC failure because BXM has no resource to build the CVC.

Conditions: Intermittent.

Workaround: Reset BXM card.

CSCdr57712

Symptom: Multi_partition fails to report all virtual trunks.

Conditions: This symptom occurs in case of virtual trunks with different partition.

Workaround: Reset the BXM card.

CSCdr77238

Symptom: Switch General Info does not contain bulk set capability bit. With newer images of PXM bulk set will not work with BXM images prior to MFD.

Conditions: PXM images later than 07/06/2000 contain logic to identify the bulk set capability of the slave. BXM images prior to 07/06/2000 will not have this bit set because it is newly introduced parameter in VSI spec.

Workaround: No workaround. Need to upgrade to MFD.


Anomalies Fixed in MFD

Table 54 lists the anomalies that are fixed in MFD.

Table 54 Anomalies Fixed in MFD 

Bug ID
Description

CSCdr29278

Symptom: Originally the card used to get frozen not responding to any request from the controller, as the TCB database was corrupted. But it has been protected now. But whenever a null pointer is being inserted into the TCB list a card error is being flagged. It is a harmless card error (not service affecting)

Conditions: The cause is unknown.

Workaround: None.

CSCdp63445

Symptom: ABR and UBR connections loose traffic when VC shaping is turned on.

Conditions: Enabling of VC shaping on port terminating ABR and UBR connections.

Workaround: Leave VC shaping disabled.

CSCdr30454

Symptom: Connections (LCNs) can not satisfied because of insufficient memory

Conditions: Channel stat level is set to 0

Workaround: Use chan stat level (cnfcdparm) 1, 2 or 3.

CSCdr14247

Symptom: The correct state of an SPVC is not reflected in connection bulk traps for large number of connections (> 1000). Sometimes Connection states keep toggling between AIS and CLR state when the conns are actually in AIS state

Conditions: AIS cells generated by the RCMP on different connections arrive too close to each other in the same second. This sudden burst of cells overwhelm the Class of service buffers (QBINs) in the Egress direction and get discarded. This causes remote end of the trunk to detect a loss of AIS cells and declare connection a CLR.

Workaround: None.

CSCdr40204

Symptom: Service rate for VBR traffic when WFQ is enabled is at SCR (instead of PCR) even when there is no congestion for enhanced cards (1210 QE & Sabre)

Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level.

Workaround: None. Has been fixed.

CSCdr42885

Symptom: All the ports on a BXM slave go into provisioning state.

Conditions: Controller looses communication with the BXM. This happens when AAL5 driver in the BXM mal-functions and does not free the message buffers of the application processes (ILMI/VSI etc). Eventually BXM runs out of message buffers.

Workaround: Reset the BXM card.

CSCdr49056

Symptom: Invalid Part id in SPVC stats after controller is added.

Condition: This problem happens when SFM receives the vsi message before adding the controller. This is possible to happen when there is a delay between 52 and 61 message. Since 52 add the control vc it will receive the frame and give it SFM task. But SFM won't have any information for that partition and will report the error saying that invalid partition. Since this is possible to happen as per design, the card is removed now.

CSCdr40234

Symptom: Service rate for UBR traffic when WFQ is enabled much lower than PCR even when there is no congestion for enhanced cards (1210 QE & Sabre)

Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level.

Workaround: None. Has been fixed.

CSCdr49060

Symptom: When doing a cnfcon for ABR connection, service rate drops to MCR rate even when there is no congestion. This is when WFQ is enabled and the inherent VSVD is not used.

Conditions: There are a certain parameters associated with WFQ that are required in order for WFQ to work. However, for ABR connections, when a cnfcon is done, once it is detected that VSVD is not enabled, the structure (Sabre rate RAM) which holds all these parameters is cleared out. This would cause WFQ not to operate properly.

Workaround: No need. Fix is done.

CSCdr43012

Symptom: All the ports on a BXM slave go into provisioning state.

Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck.

Workaround: Reset the BXM card.

CSCdr52195

Symptom: All the ports on a BXM slave go into provisioning state.

Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck.

Workaround: Reset the BXM card.

CSCdr36963

Symptom: When PNNI controller goes down then comes up, it couldn't establish its control call to the BXM partition, thus VC failure is displayed in PNNI controller for that partition.

Conditions: This problem only happens under the following conditions:

1. The policy parameters for the partition have been configured as nonzero at some of the class of service,i.e. the reserved minimum bandwidth of some class of service are nonzero.

2. Delete/disable that partition. BXM suppose to release all resources. However, it only released resources at partition level, but leave the reserved resources at cos level unchanged. As result, when this partition is enabled again, the internal CAC calculation at partition level became negative. That caused the first control call setup request fail.

Workaround: Reset the BXM card will clear the VC failure.

CSCdr33867

Symptom: Connect OC3 port on BXM with 7200 router, enable ILMI on router, and ILMI, protocol on card and Neighbor Discover, Object 0x31, Peer's IfName is not null terminated.

Conditions: Some peer.ifName's are null terminated, some aren't a PDU containing valid nonzero length peer.ifName doesn't always include '\0'; and is stored accordingly in the MIB. added a test if peer.ifName is non-zero in length, and isn't null terminated, concatenate the '\0'char and bump peer.ifNameLen++ count Added logic CbIlmiStatsReport, ilmi_proc.c pIlmiFsmGetResponseEventAtS3, pIlmiFsmGetResponseEventAtS9, ilmi_fsm_evt.c to ensure TopoTrap, and ILMIStats report are correctly formatted.

Workaround: None.

CSCdp48306

Symptom: On NNI side, when cross connect is established with VPI>1000 (0x3e8) the first nibble is getting chopped off and traffic is flowing on VPI 0xe8 due to bad programming of connection.

Conditions: This happens if on NNI side VPI > 0xff.

Workaround: None.

CSCdr51875

Symptom: Virtual Trunking causing Unreachability

Conditions: At least two virtual trunks share a common port at one node, but their remote endpoints terminate on different nodes.

The virtual trunks are used to carry networking (rt_op) traffic.

The simplest example follows below:

node_A ---- vtrk ----  /---- vtrk ---- node_C

  /

  /

node_B

(vtrks share common port)

With this topology, "node_A" sees "node_C" as unreachable and vice-versa; however, "node_A" communicates to "node_B", and "node_B" communicates to "node_C".

Workaround: Customers who are already using VT wraparound should continue to do so under 9.2.3x until the fix is available.

BXM virtual trunking (no VT wraparound) can still be implemented using software release 9.2.2x.

If virtual trunks are not yet in use, the VT wraparound solution can be implemented in release 9.2.3x.

CSCdr57805

Symptom: Card errors show up indicating "CB_TASK is ready"

Conditions: CB_TASK gets busy processing VSI messages and this causes root task to incorrectly assume that CB_TASK is not in a sane state. Actually a firmware change incorrectly reduced the polling interval by the root task such that it was polling the states of tasks sooner than it is supposed to.

Workaround: None. Ignore these card errors as these are benign.

CSCdr56931

Symptom: After resetsys on PXM or bouncing the feeder/control port or reset of BXM card, some virtual trunks go into vc failure/building vc state.

Conditions: Resetting PXM or pulling out the cable connecting the BXM feeder port to the controller or resetting the BXM cause the interface set policy parameters to be sent to the BXM. This cause ingress BW to be recomputed. CB_TASK passes VI numbers 0 to 31 to the CAC module which expects the range 0 to 15. This caused the problem by overindexing the CAC structures.

Workaround: None.

CSCdr59241

Symptom: Building VC status on UNI ports after repeated enabling/disabling of partition with the control port

Conditions: Controller does not send policy parameters for control port upon enabling of partition. When disabling partition, COS max bandwidth was zeroed out. With no policy parameters from which to obtain the new values, COS max bandwidth is stuck at zero; thus not allowing ant control to be established.

Workaround: Older PXM image does send policy parameters even for the partition with the control port. Control port does not require policy parameters to be sent from controller. Default it to the max bandwidth configured for the partition.

CSCdr51970

Symptom: Change CAC policy parameters will cause the available BW for some cos to be negative.

Conditions: Current implementation does not validate the CAC policy parameter change. It will always take the value. However, in some cases, improper policy parameters change will cause the avail_bw at cos level go negative. In this particular scenario, the current used bandwidth of a cos is equal to its reserved minimum bandwidth.Then the user changed the policy parameter to make this cos min_bw to smaller number. Now current_used_bw for this cos is greater than its reserved, and it has to obtained bw from the common pool to maintain its currently used bw. However, the user changed the policy parameter again, to increase the reserved bw for another cos, which caused the common pool to be zero.Therefore, by normal calculation, the previous cos avail_bw becomes to negative. Decreasing cos_min_bw to be less than it is currently used_bw is an invalid operation and should get rejected, otherwise it will mess up the CAC.

Workaround: Delete some connections to release bandwidth before decreasing cos minimum bandwidth.

CSCdr66273

Symptom: The encoding is in the reverse of the expected value by UNI4.0 spec.

Conditions: This symptom occurs with STD ABR connections.

Workaround: No workaround.


Anomalies Fixed in MFC

Table 55 lists the anomalies that are fixed in MFC.

Table 55 Anomalies Fixed in MFC 

Bug ID
Description

CSCdp63445

Symptom: ABR and UBR connections loose traffic when VC shaping is turned on.

Conditions: Enable VC shaping on port terminating ABR and UBR connections.

Workaround: Leave VC shaping disabled.

CSCdr11396

Symptom: Data transfer has affected while running OAM loopback.

Conditions: All user data is dropped when send in 960 cps of oam.

Workaround: None.

CSCdp11511

Symptom: BPX treats segment oam loopback different from end-to-end oam loopback cells.

Conditions: None.

Workaround: None.

CSCdr13208

Symptom: BXM CD errors while running OAM cells.

Conditions:

1. One PVC has 2880 cps of data and 960 cps of oam cells.

2. Another PVC has 2880 cps of data and 960 cps of oam cells.

Workaround: None.

CSCdr13196

Symptom: BPX reports SWERR 105.

Conditions: SWERR105 is logged while running OAM loopback test.

Workaround: Reset the BXM card.

CSCdr13182

Symptom: tstdelay/tstcon/tstconseg for all PVCs on that card will fail.

Conditions: User sends in >= 960 cps of oam loopback cells.

Workaround: None.

CSCdr13151

Symptom: dspportstats always show Tx port = 0.

Conditions: Send in >= 960 cps of oam loopback cells.

Workaround: None.


Anomalies Fixed in MFB

Table 56 lists the anomalies that are fixed in MFB.

Table 56 Anomalies Fixed in MFB 

Bug ID
Description

CSCdm52254

Symptom: Random BIP-8 errors show up on T3 when running in direct map (HEC) mode. There is no such thing as a BIP-8 error in the direct map mode. But this counter should report 0 in this mode.

Conditions: This is totally random due to the fact that an uninitialized (don't care) counter variable is accumulated in every poll period. This counter is not even read from hardware in the HEC mode.

Workaround: Ignore BIP-8 errors when the T3 trunks are configured in the HEC mode.

CSCdm62817

Symptom: tstconseg command sometimes does not work.

Conditions: Execute tstconseg multiple times with high loop count (10).

Workaround: None

CSCdm84853

Symptom: BW reported via interface load info is erroneous.

Conditions: Forward & Backward BW for VSI connections is different.

Workaround: None.

CSCdm92931

Symptom: APS line switchover occurs upon card removal when lockout is set.

Conditions: None.

Workaround: Upgrade to MEF or newer version of firmware.

CSCdp20848

Symptom: SF switchover doesnot occur after dncd/upcd execution on Annex B 1+1 APS.

Conditions: When the dncd command is executed, SWSW sends 0x27 CBUS message. The handler for this message was putting the lines in loopback and shutting down the laser. Also it was changing the line state in SoCdDown() to DOWN state. This caused subsequent upcd (0x05/0x04) message to re-initialize the lines disabling the S/UNI interrupts in the process.

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp24224

Symptom: WTR does not occur after LOS recovery on protection line

Conditions: The meaning of primary and secondary channels were changed immediately upon switchover instead of waiting for the expiry of WTR. This caused the clearing of the failure to be accounted against the secondary channel and thus there was no WTR. Fixed by introducing a Preparation switch mode where-in the current active channel will remain as the secondary until a WTR occurs or a primary section mismatch pre-empts that state. At the expiry of WTR, the preparation switch mode is complete and the current active channel becomes the primary.

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp25130

Symptom: APS Non-revertive bidirectional feature.

Conditions: Resolved.

Workaround: None.

CSCdp25220

Symptom: Avail Buffer on BXM = 0 on LVC flapping for xtag interfaces

Conditions: This is same as CSCdp58969. During this condition AAL5 driver doesn't release the transmission buffer.

Workaround: Upgrade to/MEF or newer versions of firmware.

CSCdp28931

Symptom: No RDI-P generated when loss of Cell Delineation occurs.

Conditions: The cell header so Loss of Cell Delineation occurs. The SONET "PATH RDI" indication is not transmitted as outlined in the UNI 3.1 specification.

Workaround: None.

CSCdp32646

Symptom: WTR Timer does not work and reversion occurs during SF switchover.

Conditions: Added a preparation switch mode where the current active channel is the secondary channel. At the expiry of WTR, the secondary channel is changed to the become the primary channel.

Workaround: Upgrade to MEF or newer version of firmware.

CSCdp35156

Symptom: BPX APS reverts back to the working line before WTR time has expired

Conditions: TR was being pre-empted by a spurious SD condition. Fixed by setting the right thresholds for SF/SD based on BER.

Workaround: Upgrade to MEF or newer version of firmware.

CSCdp38148

Symptom: Resetcd slot 11 on BPX causes local APS switching.

Conditions: Re-impose the selector and bridge states on both ACTIVE and STANDBY cards after Y-red switchover, re-discover the line states and re-execute and external requests.Also include a STABILITY timer before the line state is processed.

Workaround: Upgrade to MEF or newer version of firmware.

CSCdp39723

Symptom: Aps not functioning in 9.2.21 w/FW ME18@sprintf for Bidirectional w/Nonrevertive

Conditions: Reversion was happening due to spurious SF/SD events.Fixed by setting the right values for SF/SD thresholds.

Workaround: Upgrade to MEF or newer version of firmware

CSCdp46399

Symptom: Need a documentation explains how to setup port groups for FW MEF (me26).

Conditions: None.

Workaround: No known workaround.

CSCdp49640

Symptom: When FCES feature enable on BXM NNI data transfer stops.

Conditions: The ABR parameters like NRM,CRM,FRTT,MCR,ICR were not getting programmed when the FCES is turned on using th cnfcon command.Adding the Connection with the FCES enabled behaved properly.

Workaround: None.

CSCdp49749

Symptom: Node unreachable after resetting two nodes in the network.

Conditions: When combus message 0x52 is sent down to BXM, we were not handling the case when message says activate the lcn, but delete the vpi-vci pair specified in the command.

Workaround: None. Upgrade to MFB.

CSCdp57596

Symptom: CB_TASK on BXM goes into deadlock state causing VSI session to be lost

Conditions: This happens when both Ingress and Egress qe semaphore is taken by IDLE_TASK and it never released in an error condition.

Workaround: None. Upgrade to MEF or newer versions of firmware.

CSCdp58969

Symptom: cb_get.c CB_VPC_STATUS_POLL SoItcSend Failed upon VSI Failure

Conditions: When VSI receives and transmits lot of vsi message AAL5 drive, it will get into deadlock problem if it had missed a DMA interrupt.

Workaround: None. Upgrade to MEF or newer version of firmware

CSCdp59328

Symptom: EPD bit was not set for interslave control vc.

Conditions: This symptom occurs when vsi get congestion (same as CSCdp58969).

Workaround: None. Upgrade to/MEF or newer versions of firmware.

CSCdp59727

Symptom: Addlnlocrmt causes node unreachable.

Conditions: None.

Workaround: Reset the BXM card.

CSCdp59729

Symptom: addlnlocrmt causes node unreachable.

Conditions: addlnlocrmtlp causes node unreachable even though there are other parallel trunks.

Workaround: No known workaround.

CSCdp60696

Symptom: Both lines fail when only one line in alarm.

Conditions: After the standby card comes out of reset, its S/UNI states are not reliable for a period of 1.5 seconds and the S/UNI reports LOS clear on the WORK line. This gets conveyed to the active card and then the Manual switch gets priority and becomes the current local request. This causes a switch back to WORK. When the active card's S/UNI monitors the WORK line, it discovers that the line is in LOS and immediately switches back. The oscillations continue and the line goes into LOCKOUT due to excessive switching. In the Lockout mode only the WORK line is active and thus the defect.

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp62213

Symptom: Switching from bi-dir to uni-dir mode APS generates APS architecture mismatch error

Conditions: When APS pair is configured from bi-dir mode to uni-dir mode the other side indicates APS architecture mismatch error, and then the other side is also configured from bi-dir mode to uni-dir mode, the APS architecture mismatch error does not clear.

Workaround: Delete APS and then add APS again - it defaults to uni-dir.

CSCdp65320

Symptom: Need a trap when BPX puts APS in lockout.

Conditions: Send the traps in the right sequence. First send the Lockout trap and then the failed to switch trap if there is a switch attempt while lockout is in effect.

Workaround: None.Upgrade to MEF or newer version of firmware

CSCdp67673

Symptom: dspapsln does not show ARCH_MIS any more.

Conditions: dspapsln does not show ARCH_MIS when caused for the second time on the same trunk.

Workaround: No known workaround.

CSCdp79156

Symptom: TDP signalling cross connect VSI request rejected by BXM.

Conditions: If BPX is configured with trunks and virtual trunks the virtual trunks are initialized properly with qbin size.

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp84386

Symptom: Connectivity w/BXM lost due to missing DMA completion interrupts.

Conditions: Aal5 driver will be in deadlock and never transmits and receives.

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp86147

Symptom: The removal of Rx cable of APS trunk leading to loss of Frm and Prot Sw Byt Fail.

Conditions: While removing the Rx cable of APS working line (configured to trunk), working line goes to Loss of Frm and dsptrks shows the trunk in alarm. After connecting cable back the APS Alarm status shows "Prot Sw Byt FAIL".

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp89972

Symptom: Node rebuild caused 3 BXM cards failed.

Conditions: Moved the allocation and initialization of the Connection database to the SoCoEnterStandby function instead of in the 0x50 handler (SoCdUp).

Workaround: None.Upgrade to MEF or newer version of firmware.

CSCdp92916

Symptom: Commands executed on stdby card affect APS line.

Conditions: Series of commands executed in stdby card affects APS line.

Workaround: None.Upgrade to MEF or newer version of firmware.


Anomalies Fixed in MFA

Table 57 lists the anomalies that are fixed in MFA.

Table 57 Anomalies Fixed in MFA 

Bug ID
Description

CSCdk42527

Symptom: Rx Queue becomes full after LOS on the feeder trunk.

Conditions: This symptom occurs after LOS condition on the feeder trunk.

Workaround: Reset the feeder trunk.

CSCdk80483

Symptom: TX cell loss counts in dsptrkerrs increase continuously.

Conditions: This symptom occurs when there is trunk configured.

Workaround: None.

CSCdk81384

Symptom: BXM slot errors keeps on incrementing on a BCC3 node, but the reading of 'EAP ARFD' should only be interpreted when using the dual receiver feature on a BCC4 node.

Conditions: BXM slot has errors on a BCC3 node.

Workaround: None.

CSCdm04312

Symptom: The problem is a false failure is declared against the SIMBA Multicast Record RAM.

Conditions: The problem occurs when Self Test is activated against a Y-Redundant pair of BME Cards (BXM-622 cards loaded with the multicast BME firmware) that have more than 1000 connections programmed through them.

Workaround: Disable Self Test via the cnftstparm command.

CSCdm09295

Symptom: Reconfig of FCES from enable to disable does not work, as a result traffic burst is restricted to MCR.

Conditions: This symptom occurs every time changing an existing connection from FCES enable to disable.

Workaround: Delete the connection and add back a new one with FCES disable.

CSCdm09882

Symptom: Log non fatal message related to the RCMP errors.

Conditions: It is mainly seen in the heat chamber.

Workaround: Please make sure the TEST FREQUENCY and TIMEOUT variables under cnftstparm for BXM are set to 4000/3700 level.

CSCdm16505

Symptom: AIS not sent on VP ABRFST/ABRSTD connection.

Conditions: This symptom occurs when LOS on trunk between 2 nodes.

Workaround: None.

CSCdm31923

Symptom: AIS/YEL alarm doesn't go away even after the alarm is clear from the other end.

Conditions: It happens on the E3 when the LOOP TIME parameter is set to YESin the trunk or line configuration.

Workaround: None.

CSCdm39186

Symptom: Card fatal error occurred when running in standby mode under the heat condition. As a result, the card reset periodically.

Conditions: Card is running in standby mode under heat condition.

Workaround: None.

CSCdm50659

Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms.

Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable.

Workaround: Lowering the alarm threshold for MAJOR and MINOR HCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR. These thresholds are as low as they can be set currently.

CSCdm52585

Symptom: DspVsiPartInfo shows very large Available LCN field.

Conditions: The sum of min-lcns is greater than the max (max lcns) on a port group.

Workaround: None.

CSCdm53420

Symptom: switchyred causes APS line to switch when last user request is clear.

Conditions: This symptom occurs with APS 1+1 configuration. The protection line was active and the "last user switch request" was clear. When a switchyred was performed, APS line switched to working line active

Workaround: None.

CSCdm61493

Symptom: When BIP8 errors are received on an E3 line or trunk at a rate of 10E-3, the line or trunk will not declare any alarm.

Conditions: High rates of BIP8 errors are received.

Workaround: None.

CSCdm73220

Symptom: Trunks or Virtual Trunks does not allow traffic going through.

Conditions: This symptom occurs with SWSW 9.1 with ME level of firmware. Trunks or VTs configured on BXM/BXM-E.

Workaround: None.

CSCdm81534

Symptom: ICR of abrfst on BXM-155 falls down to MCR after resetcd.

Conditions: Change the ICR after resetcd before start sending traffic.

Workaround: None.

CSCdm92916

Symptom: Operational commands (dncd, resetcd, remove) on standby card impact active APS line. When active line is PROT line and a switchover of cards occur, WORK line becomes active line on the newly active cards.

Conditions: APS 1+1 Annex B and PROT are active line. switchyred or resetcd on the active card causes line to switchover from PROT to WORK.

Workaround: None.

CSCdm92931

Symptom: APS line switchover occurs upon card removal/insertion when lockout is set

Conditions: When Lockout is set, removing/inserting the card makes it happen.

CSCdm93274

Symptom: OC3 back card LED is wrong after reset/pull cards.

Conditions: Multiple APS lines exist on a card and perform switchyred when Working line is active and Secondary card is active.

Workaround: None.

CSCdp11025

Symptom: Use the "dspapsln" to get the screen to display apsln status.When the working line is taken out the LOS appears on the working line. When the protection line is taken out both the working and protection display LOS. When the protection line is put back in the LOS/Alarms on the protection should clear. They do not.

Conditions: Physically remove and add the rx or both rx and tx lines as follows:

1. Remove the working line.

2. Remove the protection line.

3. Add the protection line back.

Workaround: None.

CSCdp17741

Symptom: 2-portgroup card reports 1 port group at the channel stats level 2 and 3.

Conditions: When channel stats level 2 or 3 are configured on BXm-622-2 port and BXM-155 reports only one port group.

Workaround: Auto Route connections are not affected by this. But for VSI connections there is no work around.

CSCdp18840

Symptom: The CBR.2 Calls do not pass traffic above 50 Cells/second.

Conditions: VSI controller establishes CBR.2 connection and it does not fill in the PCR field.

Workaround: Fill the PCR value also with the CR value.

CSCdp22930

Symptoms: Intlock missing for rd/wr operation

Workaround: Reassert intLock on commbus ISR to prevent SCC access from getting interrupted.

CSCdp31325

Symptom: UBR cells are policed unnecessarily below PCR.

Conditions: Always.

Workaround: None.

CSCdp32853

Symptom: The BXM enhanced cards keep getting reset and card errors are logged and node may go into degraded mode, when command "addapsln slot1.port1 slot2.port2 1" is issued.

Conditions: This symptom occurs with BXM enhanced OC3 cards with 4 port and FW rel earlier that M.E.22/M.F.09.

Workaround:

1. Do not addapsln on second port onwards for BXM-E OC3 4 port card.

OR

2. Replace the BXM-E 4 port card with 8 ports card.

CSCdp33894

Symptom: Standby APS line shows status as Path AIS upon switchyred or on APS switchover on LOS.

Conditions: switchyred on APS, the prot. line report Path AIS.

Workaround: None. Upgrade to ME26/MED or later versions of BXM firmware.

CSCdp36155

Symptom: BXM-E OC3/OC12 does not show supporting APS HW 1+1 in dspcd command and otherwise also.

Condition: This symptom occurs with BXM-E OC3/ OC12 card with HW rev < 'C'.

Workaround: None.

CSCdp36324

Symptom: Last user request affects switching on BPX.

Conditions: None.

Workaround: None.


Anomalies Fixed in MEC

Table 58 lists the anomalies that are fixed in MEC.

Table 58 Anomalies Fixed in MEC 

Bug ID
Description

CSCdm66131

Symptom: After addapsln trunk goes to LOS.

Conditions: Both ends have secondary card active, add aps 1+1 to one end, then add aps to the other end, the trunk sometimes goes into LOS.

Workaround: None.

CSCdm64366

Symptom: APS 1+1 manual switch sometimes does not work after a while after several manual switch and auto switch.

Conditions: Secondary card is active and several manual switch and auto switches are performed.

Workaround: None.

CSCdm62809

Symptom: APS 1+1 bidirectional non-revertive switches back to working line when line condition clears on working.

Condition: APS 1+1 configured in bi-direction non-revertive mode.

Working line is in LOS, current active line is protection, clear LOS on working line.

Workaround: None.

CSCdm69974

Symptom: Card errors (0x25170076) occur when only one virtual trunk is configured in a physical port.

Conditions: Once this card error occurs, illegal pointer access has been made. These errors might result in a card error, "databus error" or network traffic getting hurdled because of inconsistency in swsw/fw databases.

Workaround: To avoid this situation, configure at least two virtual trunks on any physical port that you have VTs on. When preforming the configuration, configure the VTs one directly after the other.

CSCdm65813

Symptom: APS switches back o working line incorrectly.

Conditions: Switch sequence W->P, P->W and then W->P, then cause LOS on WORK line and put the cable back, APS switches to Working line.

Workaround: None.

CSCdm77212

Symptom: When addshelf command is executed, it comes back with a communication breakdown.

Conditions: Channel level stats is set to 0 so that BXM reports wrong maximum channels.

Workaround: For previous releases the statistics level for OC3 card should not be 0 level.

CSCdm74316

Symptom: Re-adding VSI shelf does not work until a resetcd is executed on the LSC control port.

Conditions: Load information on an interface is 4 bytes more that MAX_VSI_MSG.

The message gets dropped on BXM, so VSI controller is in discovery state forever.

Workaround: None.

CSCdm75722

Symptom: No control VC after BXM is reset.

Conditions: When resync request comes down from the VSI controller with 19 checksum blocks, the length check done on BXM does not include padding.

Workaround: None.

CSCdm74968

Symptom: 0B card error causing BXM to reset.

Conditions: Over night jobs are running on controller cards.

Workaround: None.

CSCdp02190

Symptom: tstdelay timed out when going through BNI trunk.

Conditions: More that 12 VTs on an interface causes wrong port-vi mapping while considering STI_SHIFT/NO_SHIFT from 13 th VT/port onwards.

Workaround: None.

CSCdm78335

Symptom: dspvsistatus rarely shows the VSI programming status as Done.

Conditions: Primary and secondary ports have two different VPI ranges.

Workaround: None.

CSCdm26752

Symptom: Card errors continuously logged with "SoItcSend failed" message.

Conditions: RAS oam_lpbk is on and switchyred is executed several times in a job.

Workaround: None.

CSCdm93839

Symptom: Card resets on receiving oam loopback cells at high rate.

Conditions: oamlpbk is enabled with high oam traffic on large number of connections.

Workaround: None.

CSCdm52254

Symptom: BIP-8 code errs occurs on routing trunks.

Conditions: T3 card used in HEC mode can randomly have this problem.

Workaround: None.

CSCdm44183

Symptom: BXM-155 4DX was not able to recover after resetting the card.

Conditions: Traffic is sent at a rate >= 383 cps on a terminated connection on BXM-E card and then card is reset.

Workaround: None.

CSCdm90997

Symptom: BXM-E trunk and port stats are always zero in TX direction.

Conditions: Port terminated on BXM-E card or trunk passing through BXM-E card.

Workaround: None.

CSCdm80991

Symptom: Unable to add 3 segment connections using CM GUI.

Conditions: Feeder is connected to BXM card of BPX routing node and for BXM trunk configuration, ILMI/LMI protocol is enabled as CARD based.

Workaround: None.

CSCdm82688

Symptom: Traffic Shaping problems with VT with and without rap around solution.

Conditions: Large deviations in CDV values.

Workaround: None.

CSCdm94372

(See explanation below.)

Symptom: Trunks sometimes drop cbr traffic.

Conditions: If a trunk is configured to full line rate on BXM cards, then traffic is dropped.

Workaround: None.

CSCdp00063

Symptom: Node unreachability is experienced on VTs (virtual trunks).

Conditions: Multiple VTs are configured on a trunk interface of the BXM/BXM-E.

Workaround: Configure only one VT per trunk interface.


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

if (configured cell rate == full line cell rate) then
	transmitted cell rate = full line cell rate
else
	transmitted cell rate = from equation below or from table 1

For example:

If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is then 98,013 CPS any traffic sent over 98,013 CPS would be discarded.

Only rates in the table or computed from the equation should be used. Otherwise, cell loss may be experienced.

1464865

56552

28832

19348

14559

11670

9738

8355

733860

54458

28278

19097

14416

11579

9674

8308

489558

52513

27744

18852

14277

11488

9611

8261

367288

50703

27231

18614

14139

11399

9549

8215

293888

49013

26736

18381

14005

11311

9487

8169

244938

47432

26258

18154

13872

11225

9426

8124

209966

45950

25798

17933

13743

11140

9366

8079

183733

44558

25353

17717

13616

11056

9307

8035

163327

43247

24923

17506

13491

10974

9248

7992

147001

42012

24508

17300

13368

10892

9190

7948

133642

40845

24106

17099

13248

10812

9133

7906

122509

39741

23717

16902

13129

10733

9077

7863

113088

38695

23341

16710

13013

10656

9021

7822

105012

37703

22976

16522

12899

10579

8966

7780

98013

36761

22623

16339

12787

10503

8912

7739

91889

35864

22280

16159

12677

10429

8858

7699

86485

35010

21947

15983

12568

10355

8805

7659

81681

34196

21625

15812

12462

10283

8753

7619

77383

33419

21311

15643

12357

10212

8701

7580

73515

32676

21007

15479

12254

10141

8650

7541

70014

31966

20711

15318

12153

10072

8599

7502

66833

31286

20423

15160

12053

10003

8549

7464

63927

30634

20143

15005

11955

9936

8500

7427

61264

30009

19871

14853

11859

9869

8451

7389

58814

29409

19606

14705

11764

9803

8403

7352


Anomalies Fixed in MEB

Table 59 lists the anomalies that are fixed in MEB.

Table 59 Anomalies Fixed in MEB 

Bug ID
Description

CSCdm50469

Symptom: Software error 105 and mallet card errors happened continuously.

Conditions: When jobs that cause reroutes of connections (e.g. switchcc, hitless rebuild) are run for a long time, sometimes BXM card freezes with malloc card errors and software error 105.

Workaround: None.

CSCdm50723

Symptom: After deleting APS, switchyred causes temporary LOS when the other end still has APS.

Conditions: One end has APS 1+1, other end was added with APS 1+1 and line is up between the two ends. Then APS is deleted from one end. The primary card is active on non APS end. On switchyred on the non APS end there is a temporary LOS. If APS was never added to one end, then switchyred does not result in temporary LOS.

Workaround: Instead of deleting APS first and then doing a switchyred, do a switchyred first and then delete APS. This does not result in temporary LOS.

CSCdm63038

Symptom: BXM card fails with breakpoint error.

Conditions: When tx cell rate of a trunk is reduced to zero, BXM card fails with break point error (division by zero).

Workaround: None.


Anomalies Fixed in MEA

Table 60 lists the anomalies that are fixed in MEA.

Table 60 Anomalies Fixed in MEA 

Bug ID
Description

CSCdm09882

Symptom: Log non fatal message related to RCMP errors.

Conditions: It is mainly seen in the heat chamber.

Workaround: None.

CSCdm18186

Symptom: AIS status could be randomly be displayed in dspcon

Conditions: When the connection AIS signal is constantly changing, the dspcon/dspchstats OAM status will not be accurate for all the connections on the card.

Workaround: None.

CSCdm26380

Symptom: Software error 9098 occured during switchyred BXM

Conditions: This problem occurs on cards with the APS channels halved option set and then doing a cnfrsrc on a port that belongs to the second port group. Note that this fix will cause a card mismatch on active cards with channel halved option turned on.

Workaround: None.

CSCdm31923

Symptom: AIS/YEL alarm doesn't go away even after the alarm is clear from the other end.

Conditions: It happens on the E3 when the LOOP TIME parameter is set to YES in the trunk or line configuration.

Workaround: None.

CSCdm37519

Symptom: Trunks go to Communication Fail after burning firmware.

Conditions: MC10 is burnt into BXM-OC12 with trunks.

Workaround: None.

CSCdm37709

Symptom: APS line fails to clear channel mismatch after lockout.

Conditions: This symptom occurs with bi-direction APS 1+1. Local end has locked out of protection set. Then WORK cable is pulled out on local end to cause LOS. Lockout is then cleared and then the WORK cable is put back. This causes a channel mismatch on the far end and the mismatch never clears.

Workaround: None.

CSCdm38647

Symptom: This bug has been fixed in MEA such that the firmware reports the correct number of port groups. The side effect of this fix is that the Switch Software could mismatch the BXM card. If there is a card mismatch then down all the lines/trunks on the card and up them again.

Conditions: When the user loads the MEA firmware on the BXM card running MDA with APS halved channeled enabled, then the card will come up in mismatched state.

Workaround: None.

CSCdm46658

Symptom: switchapsln command does not work for APS AnnexB line.

Conditions: Annex B configuration if hitless rebuild is done when active line is PROT, then switchapsln does not work after hitless rebuild.

Workaround: None.


Firmware Filenames and Sizes

Table 61 contains the firmware file information.

Table 61 Firmware Files 

Filename
Size

BXMMFZ.000

65536

BXMMFZ.001

65536

BXMMFZ.002

65536

BXMMFZ.003

65536

BXMMFZ.004

65536

BXMMFZ.005

65536

BXMMFZ.006

65536

BXMMFZ.007

65536

BXMMFZ.008

65536

BXMMFZ.009

65536

BXMMFZ.010

65536

BXMMFZ.011

65536

BXMMFZ.012

65536

BXMMFZ.013

65536

BXMMFZ.014

65536

BXMMFZ.015

65536

BXMMFZ.016

65536

BXMMFZ.017

65536

BXMMFZ.018

65536

BXMMFZ.019

65536

BXMMFZ.020

65536

BXMMFZ.021

65536

BXMMFZ.022

65536

BXMMFZ.023

65536

BXMMFZ.024

65536

BXMMFZ.025

48064

BXMMFZ.026

14

BXMMFZ.027

2

BXMMFZ.IMG

784

BXMMFZ.img

784


Appendix B—UXM Model C ACL Firmware Release Notes

This section contains information about UXM Model C firmware.

Introduction

ACL is a firmware maintenance release for UXM cards on the IGX. The firmware is the same for UXM and UXM-E cards.

New Features

This release does not have new features.

Obsolete Features

This release does not obsolete features.

Compatibility

1. Software

ACL firmware is compatible with Switch Software Release 9.3.10 or later.

2. Hardware

ACL firmware is compatible with all UXM and UXM-E model hardware.

Anomalies Fixed in ACL

Table 62 lists the anomalies that are fixed in firmware ACL.

Table 62 Anomalies Fixed in ACL 

Bug ID
Description

CSCef22935

Two LCNs in MPLS partition use same CBA causing data loss in UXM.

CSCef32602

Swerr 5050 with cba_verify on IGX with vsi partition and swerr 9098.

CSCeg44094

TCB buffer exhaustion.

CSCei10761

9098(c013) logged when switched to yred card after modifying the vsi resources.

CSCin95415

Cleaning up the vsi variables.

CSCei18914

Cba Blocks are not disabled on a hot standby.


Upgrade Instructions

To upgrade the firmware to ACL, complete the following steps:


Step 1 Upgrade the UXM boot code to boot revision 10.

Step 2 Upgrade the firmware to ACL.

Step 3 Reset the card.


Boot Code Requirements

Boot Code revision boot_10 is needed for the ACL release.

Unsupported Configurations or Applications

None.

Notes and Cautions

None.

Firmware Filenames and File Sizes

Table 63 lists the firmware file information for the UXM Model C.

Table 63 UXM Filenames and Sizes 

Filename(s)
Size (bytes)

ACL.000 to ACL.024

65536

ACL.025

5649

ACL.img

784


Appendix C—UXM Model B Firmware ABV Release

This section contains information about UXM Model B firmware.

Introduction

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

New Features

This section contains the new features in ABV.

Cell Bus Parity Diagnostic—CSCdy86516

This feature allows SWSW to detect parity errors on lanes 2-4 of the backplane. Lane 1 errors are detected by the NPM.

A dummy connection is added between two UXM cards in the node and is used to send a test packet from one end of the connection to the other. By observing the parity errors count before the packet is sent and after the packet is received, you can determine whether there are parity errors on the backplane.

Obsolete Features

None.

Compatibility

1. Software:

ABV is compatible with Switch Software Releases 9.1, 9.2, and 9.3.

2. Hardware:

ABV is compatible with all models of UXM and UXM-E hardware.

3. Previous versions of UXM firmware:

On IMA trunks this version is not compatible with UXMs Model B firmware versions ABA to ABD.

On IMA trunks Model B firmware (AB*) is not compatible with model A (AA*) because model B is Standards compliant and model A is not. Therefore, IMA trunks must be upgraded together.

Anomalies Fixed in ABV

Table 64 lists the anomalies that are fixed in firmware ABV.

Table 64 Anomalies Fixed in ABV 

Bug ID
Description

CSCdy29096

Cell drop on IMA 30 channel 7 E1 and 8 E1

CSCdy86516

Parity Errors seen on Cell Lanes 2-4 are not reported

CSCdy88772

Communication Failure after upgrading UXM to A.B.T firmware

CSCdz48550

addloclp causes alarm or continuity problems on ATM connections

CSCea64204

Need to enhance rsh cobra err cli to have lane parity info

CSCeb08097

Deleting ATFXFST connection does not remove FCES from the configuration

CSCed92177

Double Traffic on UXME trunk in Y-Redundancy

CSCee26245

Printfs Not working when test fails for Diag Test rcv_qe_c_qe_ex_loop()

CSCin29753

RCMP rsh command lcnsram is not working as expected

CSCin29766

RCMP rsh command modTime is not working as expected

CSCin33540

Addlnlocrmtlp does not work properly

CSCin34772

Loopback feature not working


Upgrade Instructions

Update boot code to boot_09 before upgrading to ABV.

Boot Code Requirements

Boot code revision boot_09 is needed for the ABV release.

Unsupported Configuration or Applications

None.

Firmware Filenames and Sizes

Table 65 lists the ABV filenames and sizes.

Table 65 ABV Files 

Filenames
Size (bytes)

ABV.000-ABV.017

65536

ABV.018

63765

ABV.img

784


Notes and Cautions

None.

Appendix D—URM Model B Firmware XBC Release Notes

This section contains information about the URM Model B firmware XBC.

Introduction

URM XBC is Model-B firmware release for URM card on IGX. The URM is an IOS-based routing module for the IGX. This release is an upgrade from XBB.

New Features

This section contains new features in XBC.

RCMP Parity Policing

CSCin32112—Implementation of Policing RCMP parity errors on URM.

This feature allows URM card to continue to be in service under low rate of parity errors while informing the user of parity event. The card will be reset if the error rate exceeds a threshold rate.

URM IOS CLI

This feature improves the management of the URM by allowing access to the IOS CLI running on the URM via the IGX CLI. This feature will also enhance Serviceability by further enabling remote recovery of the URM beyond the RRC feature introduced in 9.3.30 software.

This feature allows users to access the IOS CLI of the URM embedded router from the IGX CLI, so that users can access the router without having to be physically connected to the IOS Console port on the URM backcard

Obsolete Features

None.

Compatibility

1. Software

XBC firmware is compatible with Switch Software Release 9.3.47.

2. Hardware

XBC firmware is compatible with URM hardware.

Anomalies Fixed in XBC

Table 66 lists the anomalies that are fixed in firmware XBC.

Table 66 Anomalies Fixed in XBC 

Bug ID
Description

CSCdz48550

addloclp causes alarm or continuity problems on ATM connection.

CSCin15267

DUART hangs up when there is heavy interrupts (Rx and Tx) from both the channels simultaneously.

CSCin21211

For all rsh commands, Lines were truncated beyond 80 characters.

CSCin21212

"-MORE" is attached to the end of the "dsprtrlog" response even though there is no more data to view.

CSCin39677

After changing the Max and Min LCNs of VSI partition using cnfrsrc, SWerr:5050 was logged when "cba_verify" command was executed.


Upgrade Instructions

No special upgrade instructions in upgrading the URM Admin firmware from XBB to XBC.

Boot Code Requirements

Boot Code revision boot_2 is needed for the XBC release.

Unsupported Configurations or Applications

The 0/1023 is a special VC used by URM for IPC between Admin Processor and IOS. When configuring MPLS network, do not commit any cross-connect or control-vc on the port. Otherwise, SWERRS or non-working configurations might occur.

Firmware Filenames and Sizes

This section contain URM-B firmware file information.

XBC Firmware Boot Code

Table 67 lists the XBC filenames and sizes.

Table 67 XBC Files 

Filename(s)
Size (bytes)

XBC.000 to XBB.019

65536

XBC.020

33025

XBC.img

784


XAA Firmware Boot Code

Table 68 lists the XAA file names and sizes.

Table 68 XAA Files 

Filename(s)
Size (bytes)

XA2.000

57328

XA2.img

784


Notes and Cautions

1. The URM back card is hot-swappable; however the IOS processor is held in reset when back card is removed.

2. Card Mismatch might occur since XBA supports both BC-2FE2V and BC-2FE. Card mismatch is declared if BC-2FE2V and BC-2FE are swapped out of an ACTIVE URM card. Back cards of two different types can be swapped only in a STANDBY URM card.

3. If Remote Router Configuration feature is used to burn the IOS configuration in the card, the burned configuration cannot be deleted but can be overwritten only by another configuration.

Obtaining Documentation

Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.

Cisco.com

You can access the most current Cisco documentation at this URL:

http://www.cisco.com/techsupport

You can access the Cisco website at this URL:

http://www.cisco.com

You can access international Cisco websites at this URL:

http://www.cisco.com/public/countries_languages.shtml

Product Documentation DVD

The Product Documentation DVD is a comprehensive library of technical product documentation on a portable medium. The DVD enables you to access multiple versions of installation, configuration, and command guides for Cisco hardware and software products. With the DVD, you have access to the same HTML documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .PDF versions of the documentation available.

The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD= or DOC-DOCDVD=SUB) from Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Ordering Documentation

Registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:

http://www.cisco.com/go/marketplace/

Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.

Documentation Feedback

You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.

You can submit comments about Cisco documentation by using the response card (if present) behind the front cover of your document or by writing to the following address:

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

We appreciate your comments.

Cisco Product Security Overview

Cisco provides a free online Security Vulnerability Policy portal at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

From this site, you will find information about how to:

Report security vulnerabilities in Cisco products.

Obtain assistance with security incidents that involve Cisco products.

Register to receive security information from Cisco.

A current list of security advisories, security notices, and security responses for Cisco products is available at this URL:

http://www.cisco.com/go/psirt

To see security advisories, security notices, and security responses as they are updated in real time, you can subscribe to the Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed. Information about how to subscribe to the PSIRT RSS feed is found at this URL:

http://www.cisco.com/en/US/products/products_psirt_rss_feed.html

Reporting Security Problems in Cisco Products

Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you have identified a vulnerability in a Cisco product, contact PSIRT:

For Emergencies only —  security-alert@cisco.com

An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.

For Nonemergencies —  psirt@cisco.com

In an emergency, you can also reach PSIRT by telephone:

1 877 228-7302

1 408 525-6532


Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product (for example, GnuPG) to encrypt any sensitive information that you send to Cisco. PSIRT can work with information that has been encrypted with PGP versions 2.x through 9.x.

Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:

http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html

The link on this page has the current PGP key ID in use.

If you do not have or use PGP, contact PSIRT at the aforementioned e-mail addresses or phone numbers before sending any sensitive material to find other means of encrypting the data.


Obtaining Technical Assistance

Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.

Cisco Technical Support & Documentation Website

The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:

http://www.cisco.com/techsupport

Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:

http://tools.cisco.com/RPF/register/register.do


Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.


Submitting a Service Request

Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:

http://www.cisco.com/techsupport/servicerequest

For S1 or S2 service requests, or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.

To open a service request by telephone, use one of the following numbers:

Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447

For a complete list of Cisco TAC contacts, go to this URL:

http://www.cisco.com/techsupport/contacts

Definitions of Service Request Severity

To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.

Severity 1 (S1)—An existing network is down, or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.

Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operations are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.

Severity 3 (S3)—Operational performance of the network is impaired, while most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.

Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.

Obtaining Additional Publications and Information

Information about Cisco products, technologies, and network solutions is available from various online and printed sources.

The Cisco Product Quick Reference Guide is a handy, compact reference tool that includes brief product overviews, key features, sample part numbers, and abbreviated technical specifications for many Cisco products that are sold through channel partners. It is updated twice a year and includes the latest Cisco offerings. To order and find out more about the Cisco Product Quick Reference Guide, go to this URL:

http://www.cisco.com/go/guide

Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:

http://www.cisco.com/go/marketplace/

Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:

http://www.ciscopress.com

Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:

http://www.cisco.com/packet

iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:

http://www.cisco.com/go/iqmagazine

or view the digital edition at this URL:

http://ciscoiq.texterity.com/ciscoiq/sample/

Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:

http://www.cisco.com/ipj

Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:

http://www.cisco.com/en/US/products/index.html

Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:

http://www.cisco.com/discuss/networking

World-class networking training is available from Cisco. You can view current offerings at this URL:

http://www.cisco.com/en/US/learning/index.html