8.4.30 Version Software Release Notes Cisco WAN Switching Software


Bug ID	Descriptions
CSCst96798	Switch software sets shelfCnfgRebuildStatus object as REBUILD when switchcc occurs. DNS software interprets this as the node went down and deletes all SVCs associated with that node. This will cause calls to be dropped.

Problems Fixed in Release 8.4.06:


Bug ID	Descriptions
CSCdj24114	A 1000003 abort occurred when attempting to add more than 12,000 connections.
CSCdj26862	A software error 4209 occurred while adding connections due to the local resources unavailability.
CSCdj28579	Remove debugging code that logged software error 7777.
CSCdj27744	BXM feeder trunks weren't being programmed during the card configuration process.

Problems Fixed in Release 8.4.05:


Bug ID	Descriptions
CSCdj19652	The dspclksrcs command shows invalid clock source information, The primary, secondary, and tertiary sources are incorrect.
CSCdj03075	A virtual path connection could not be added because the support for BNI-E3 cards is missing.
CSCdj21794	A software error 614 (LCON automatically deleted) due to the logical endpoint VC index did not agree at each end.
CSCdj22424	Routing virtual trunk traffic through a BXM via trunk does not work.
CSCdj23350	IPX feeder nodes cannot use the trunk as a timing source. The "pass sync" option is not allowed on feeder trunks. Packet lines which pass sync are not allowed to be clock sources.
CSCdj27532	When nwip_on is asserted in the ~svplus/config.sv file, the savecnf operation does not work from an IPX feeder.
CSCdj23570	Multiple problems after performing a switchcc on a BPX with many connections: the problems are all caused by comm failures due to inefficient programming of the BXM cards.
CSCdj27129	A 100003 abort occurred when handling an error condition returned by the SAR which indicated that an invalid command was received.
CSCdj27059	Software error 514 occurred on a heavily loaded BPX node.
CSCdj19165	There is a 10-15 second delay in traffic continuity after a port Y-redundant switchover.
CSCdj19637	Incorrect trunk number is shown as the clock source when using the dspcurclk command.
CSCdj19512	The dspports command only displays the first 96 ports of a BPX node.
CSCdj20069	Standby Y-redundant cards can still drive the clock bus.
CSCdj15103	Software error 4208 (Bad connection address type) occurred on a BPX node.
CSCdj21070	Invoking dspcons with a starting channel number as the only argument fails to display the appropriate connections.
CSCdj20682	A BPX event log indicates that there are BFrame parity errors and Rx Invalid Port errors, but the StrataView Plus HPOV event log does not indicate any of these.
CSCdj22346	After a graceful upgrade from 8.1.50, trunk number 32 is missing.
CSCdj21369	The cnfswfunc feature 6 on a BPX, ABR standard with VSVD, becomes disabled when any IPX or IGX routing node rebuilds.
CSCdj23566	Using dspport or dspports with only a slot number as the argument incorrectly displays Speed as "UNKNOWN" and Interface as "EMPTY".
CSCdj26131	The cnfclksrc command allows a trunk to be a primary clock source while it is passing sync.
CSCdj25301	On the BXM, Early Packet Discard (EPD) and/or Frame Discard is not enabled.
CSCdj26827	On an ASI-T3 card, the 1000th connection on the card is not programmed correctly.
CSCdj27511	Software error 618 occurred on a heavily loaded BPX node.

Problems Fixed in Release 8.4.03:


Bug ID	Descriptions
CSCdj15795	Software error 1406 (indicating a bad checksum on a network topology update message) floods the error log.
CSCdj16467	For BXM-DS3 terminated connections, Virtual Path Connections do not operate when the other end terminates on an AXIS shelf in NNI mode.
CSCdj16162	After a Y-Redundant switchover between a pair of BXM cards, it has been observed that a software error 105 (CBUS buffers full) was logged. This is due to multiple connections being re-configured within one CBUS message, which results in a much longer than expected execution time. This will be addressed in the next release where appropriate message throttling will be inserted. At this time, BXM port and trunk cards should not be configured in Y-redundant pairs.
CSCdj14719	The BPX is constantly re-routing connections due to the failure of topology updating, which caused an incorrect view of the topology to exist.
CSCdj18088	There is network topology corruption caused by a node, whose number is set to 64, when that node rebuilds.
CSCdj19179	After a Node-by-Node upgrade, there are cases where the battery backed up RAM is not being rewritten properly.
CSCdj15047	The dspnwip command repeatedly displays the same node's information, rather than all the nodes.
CSCdj09736	There is an intermittent condition where a self-test timeout occurs on the BCC-32. This is not a true indication of a problem with the BCC.
CSCdj12314	When rerouting connections that terminate on AXIS shelves due to the establishment of a preferred route, failure status is reported because an A-bit alarm is being sent by the BPX.
CSCdj15594	Multiple software errors 21 were logged on a BPX.
CSCdj15999	The addcon command cannot be used in jobs on the BPX. An infinite loop results.
CSCdj15226	After a node rebuilds, messages indicating that the time of day is changing is flooding the event log.
CSCdj11989	After a switchcc command is issued, the event log is formatted after the switch, and thus the switchcc even will not be reported to StrataView Plus.
CSCdj17569	A BXM-DS3 trunk card in y-redundant configuration indicated a backcard mismatch after being reset. At the time, the standby card was in failed state.
CSCdj18216	Invoking the dsptrkstats commands on virtual trunks shows incorrect BFrame cell count values.
CSCdj09369	On the cnftrk command, for BNI-OC3 trunks the Payload Scramble option cannot be set to "No" because it results in an Out Of Frame alarm. The software must prevent the user from making this setting.
CSCdj19165	There is a 15 second delay/interruption of traffic on BXM port cards after a Y-redundant switchover occurs.
CSCdj19637	An incorrect trunk number is displayed as the clock source when running the dspcurclk command.
CSCdj19512	The dspports command displays only the first 96 ports of a node.
CSCdj13934	The dspports command works on IPX nodes but not on BPX nodes.
CSCdj10363	The Deroute Delay Timer value used always varies 2 seconds from the configured value.

Problems Fixed in Release 8.4.02:


Bug ID	Descriptions
CSCdj17869	During an upgrade from 8.1.5, multiple node unreachabilities were encountered, along with software errors 254 and 526.
CSCdj15833
CSCdj16479	A feeder shelf cannot be deleted. When the delshelf command is issued, the message "Resources Low---Interface Shelf not changed."is returned.
CSCdj16874	During an upgrade from 8.1.5 to 8.4.0, the standby BCCs on all the BPX nodes keep toggling between the upgrading and upgraded/(clear) state.

Compatibility Matrix

AXIS 4.0 F/W Compatibility


PCB Description	Rev.	Latest F/W	Minimum F/W
IMATM F/W	C	4.0.16	4.0.04
IMATM Boot	N/A	4.0.01	4.0.00
ASC F/W	M	4.0.18	4.0.04
ASC Boot	N/A	4.0.04	4.0.03
BNM-E3	B	N/A	N/A
FRSM-4T1	C	4.0.16	4.0.04
FRSM-4T1 Boot	N/A	4.0.00	4.0.00
SRM T1E1 (B)	B	N/A	N/A
CESM-4T1/E1	C	4.0.13	4.0.04
CESM Boot	N/A	4.0.00	4.0.00
AUSM-4T1E1	B	4.0.16	4.0.04
AUSM Boot	N/A	4.0.00	4.0.00
FRSM-8T1	A	4.0.16	4.0.04
FRSM-8T1 Boot	N/A	4.0.01	4.0.00
FRSM-HS1	A	4.0.13	4.0.04
FRSM-HS1 Boot	N/A	4.0.00	4.0.00
AUSM-8T1/E1	A	4.0.17	4.0.04
AUSM-8T1/E1 Boot	N/A	4.0.01	4.0.00

Release 8.4 BPX System F/W Compatibility

BPX Boot Codes


PCB Description	Rev.	Latest F/W	Minimum F/W
BCC (model B) boot	K	HBJ	HBH
BCC3-32 (model C) boot	K	HCM	HCH
BCC3-64 (model D) boot	K	HDM	HDJ
BCC4 (model E) boot	K	HEM	HEM

BPX F/W


PCB Description	Rev.	Latest F/W	Minimum F/W
ASI 155	EOL	WHC	WHB
ASI 155 E	E	WEC	WEB
ASI-1 2T3/C	D	UCE	UCA
ASI-1 2T3/B	D	UBK	UBH
BNI 3T3/C	F	TCM	TCK
BNI 3E3/B	F	TCM	TCK
BNI 155 E	E	VDP	VDN
BNI I55	EOL	VBP	VBN
ASM	B	GAC	GAC
BXM 4P	A	MBY	MBM
BXM 8P	A	MBY	MBM

Release 8.4 IPX/IGX System F/W Compatibility

Boot Codes


PCB Description	Latest F/W	Minimum F/W
NPC Boot	BAF	BAF
NPC 32 Boot	BBF	BBF
NPC 64 Boot	BCF	BCF
NPM Boot	RAP	RAJ
NPM 32 Boot	RBP	RBJ
NPM 64 Boot	RCP	RCN
NPM 32B Boot	REN	REJ
NPM 64B Boot	RFN	RFN

IPX/IGX F/W


PCB Description	Latest F/W	Minimum F/W	Comments
ALM-A	CAE	CAA
ALM-B	CBH	CBB
BTM Model A	IAF	IAF
BTM Model B	IBL	IBK
BTM Model D	IDA	IDA
CVM Model A	DAF	DAF
CVM Model B	DBD	DBD
CVM Model C	DCA	DCA
FRM Model D	FDZ	FDR	Avoid Rev. FDU & FDV
FRM Model E	FEZ	FER	Avoid Rev. FEU & FEV
FRM (B)	FHB	FHB
FRM-2	FFD	FFC
FTM Model B	JBJ	JBB
FTM Model C	JCB	JCA
HDM	SCF	SCF
LDM	LCB	LC3
NTM	NEJ	NED
NTM (B)	NFH	NFD	Recommend using NFF
AIT Model A	IAF	IAE
AIT Model B	IBL	IBK
CDP Model A	DAF	DAF
CDP Model B	DBD	DBC
FRP(M) Model D	FDZ	FDR	Avoid Rev FDU & FDV
FRP(M) Model E	FEZ	FER	Avoid Rev FEU & FEV
FRP(M) Model H	FHB	FHB	FRM(B)
FTC Model B	JBJ	JBB
FTC Model C	JCB	JCA
NTC	NEJ	NED
SDP	SCF	SCF
UFM-C	ZAL	ZAB
UFM-U	YAD	YAA
UVM	DAC	DAA
UVM-B	DBA	DBA
UVM-C	DCA	DCA
UVM-D	DDA	DDA

Release 8.4.30 System Content

Switch Software and Boot Codes


Release ID	Product	Rev.	Model	Image
SwSw 8.4.30	Sys S/W IPX	8.4.30
	Sys S/W IGX	8.4.30
	Sys S/W BPX	8.4.30
	BCC (Model B) Boot	J0	B	HBJ
	BCC3-32 (Model C) Boot	M0	C	HCM
	BCC3-64 (Model C) Boot	M0	D	HDM
	BCC4 (Model E) Boot	M0	E	HEM
	NPC Boot	F0	A	BAF
	NPC 32 Boot	F0	B	BBF
	NPC 32 Boot	F0	C	BCF
	NPM Boot	P0	A	RAP
	NPM 32 Boot	P0	B	RBP
	NPM 64 Boot	P0	C	RCP

StrataView Plus


Release ID	Product	Rev.
SV 8.4.12	StrataView Plus	8.4.12
	StrataView Plus SCM	8.4.12
	SNMP	8.4.12

Hardware and Firmware Products


Release ID	Product	Rev	Model	Image
AXIS 4.0.18	IMATM F/W	A0	4.0.16	4.0.16
	IMATM Boot	N/A	4.0.00	4.0.00
	ASC F/W	A0	4.0.18	4.0.18
	ASC Boot	A0	4.0.04	4.0.04
	BNM-E3	N/A	N/A	N/A
	FRSM-4T1	A0	4.0.16	4.0.16
	FRSM-4T1 Boot	N/A	4.0.00	4.0.00
	FRSM-8T1	A0	4.0.16	4.0.16
	FRSM-8T1 Boot	N/A	4.0.01	4.0.01
	FRSM-HS1	A0	4.0.13	4.0.13
	FRSM-HS1 Boot	N/A	4.0.00	4.0.00
	SRM T1/E1 (B)	N/A	N/A	N/A
	CESM-4 T1/E1	A0	4.0.13	4.0.13
	CESM Boot	N/A	4.0.00	4.0.00
	AUSM-4 T1/E1	A0	4.0.16	4.0.16
	AUSM-4 T1/E1 Boot	N/A	4.0.00	4.0.00
	AUSM-8 T1/E1	A0	4.0.17	4.0.17
	AUSM-8 T1/E1 Boot	N/A	4.0.01	4.0.01
BPX 8.4.30	ASI 155	B0	E	WEC
	ASI 155E	B0	H	WHC
	ASI-1 2T3/E3	E0	C	UCE
	ASI-2 T3/E3	J0	B	UBJ
	BNI 3T3/E3	M0	C	TCM
	BNI 155E	P0	D	VDP
	BNI I55 0C3	P0	B	VBP
	BNI 3T3/E3	M0	C	TCM
	ASM	A0	A	GAC
IGX 8.4.30	BTM	L0	B	IBL
	CVM	F0	A	DAF
	CVM Model B	D0	B	DBD
	CVM Model C	A0	C	DCA
	FRM (Model D)	Z0	D	FDZ
	FRM (Model E)	Z0	E	FEZ
	FRM -2	D0	F	FFD
	HDM	F0	C	SCF
	ALM-A	E0	A	CAE
	ALM-B	H0	B	CBH
	UFM-C	E0	A	ZAE
	UFM-U	D0	A	YAD
	UVM	C0	A	DAC
	FTM	A0	C	JCA
	LDM	B0	C	LCB
	NTM	J0	E	NEJ
	NTM (B)	H0	F	NFH
IPX 8.4.30	AIT Model A	F0	A	IAF
	AIT Model B	L0	B	IBL
	CDP	F0	A	DAF
	LDP	B0	C	LCB
	FRP Model D	Z0	D	FDZ
	FRP Model E	Z0	E	FEZ
	FTC Model C	B0	C	JCB
	NTC	J0	E	NEJ
	SDP	F0	C	SCF

Hardware Compatibility Matrices

AXIS 4.0 H/W Compatibility


PCB Description	Part Number	Latest H/W	Minimum H/W
IMATM 8T1	73-3026-01	F	A
IMATM 8E1	73-3027-01	F	A
ASC	73-2454-01	N	H
ASC 2	73-2586-01	B	A
BNM-E3	73-2866-01	B	A
BNM-T3	73-2802-01	C	A
BNM-155	73-2459-02	C	A
FRSM-4T1	73-2455-01	C	A
FRSM-4E1	73-2456-01	C	A
SRM T1E1 (B)	73-2565-01	C	B
CESM-4T1	73-2525-02	F1	B
CESM-4E1	73-2541-02	E2	B
AUSM-4T1	73-2990-01	C	A
AUSM-4E1	73-2991-01	C	A
FRSM-8T1	73-2367-04	A1	A1
FRSM-8E1	73-2360-04	A1	A1
FRSM-HS1	73-2602-02	C	A
AUSM-8T1	73-2493-05	C	A
AUSM-8E1	73-2494-05	C	A
FRASM-8T1	73-2347-04	A2	A2

Obtaining Service and Support

Cisco Connection On-line

8.4.30 Version Software Release Notes
Cisco WAN Switching Software

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

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

The 8.4.30 software release supports the existing Cisco WAN Switching family (including the Cisco IGX 8400 series and Cisco BPX 8600 series) and introduces the following features:

•Flood Control

•High Priority Login

Clarifications:

Although the BCC-4 card is supported in this release, its availability is limited at this time.

If you are upgrading from an earlier version of 8.4 (8.4.08 or earlier), you MUST perform a non-graceful upgrade. See the next section.

Special Installation/Upgrade Requirements

Note If upgrading from an earlier release of 8.4 (8.4.03 - 8.4.08) a Graceful upgrade CANNOT be done; a Non-Graceful upgrade MUST be done.

General

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

•If BCC-4 cards are being installed in BPX nodes replacing older type BCCs then the software upgrade to 8.4 is done first, followed by the BCC-4 physical card upgrade.

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

Statistics collection must be disabled prior to and during the software upgrade process.

Before upgrading to this release, if there are any ABR connections with an MCR value set to 0, it is highly recommended that the MCR value for each of these connections be set to 1. This is to insure that the Load Module will be correct after an upgrade. This addresses a problem in earlier releases which did not handle Load Module calculations correctly for connections having MCR=0.

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

Consult Customer Advocacy for any additional Software Upgrade procedural issues.

Control Card Requirements

All BCC cards must be configured with a minimum of 32 MB of RAM.

The NPC (and the NPM) must be configured with 32 MB of RAM when used within a network of more than 63 nodes.

BCC Boot Firmware Requirements

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


BCC Type	Firmware
BCC-32	H.B.J
BCC-3-32	H.C.M
BCC-3-64	H.D.M
BCC-4	H.E.M

BCC Compatibility Requirements

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

This is a requirement for all software upgrade and downgrade procedures. It does not apply to the physical card upgrade procedure, as described below.

BCC Physical Card Upgrade Procedure

Step 1 Remove the current standby BCC front and back card.

Step 2 Replace with new BCC front and back cards.

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

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

Step 5 Verify that the network is stable.

Step 6 Remove the current standby BCC front and back card.

Step 7 Replace with new BCC front and back cards that are identical to the current active BCC.

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

The BCC physical upgrade is now complete.

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

Software Upgrades Supported

Software upgrades have been tested from and are supported from the following versions of switch software:

• 8.1.18

• 8.1.50

•8.1.70

• 8.2.04, 8.2.07

• 8.4.03, 8.4.05, 8.4.06, 8.4.07, 8.4.08 - Non-Graceful upgrades ONLY

•8.4.09

Software upgrades are also supported from any earlier release in the 8.1.50, 8.1.70, and 8.2.07 switch software product streams.

Node-by-Node upgrades are supported from the following version of switch software:

• 8.1.50

Restrictions on Node-by-Node Upgrade From 8.1.50:

During the upgrade mode, the chklm and dsplm commands are not supported. These commands should not be executed while the Node-by-Node upgrade is in progress.

During the upgrade mode, all the gateway nodes should be switched as part of the first group of nodes upgraded. If not, then software error 938 may be reported on the 8.1.50 gateway nodes. This error indicates that a large message is being sent from an 8.4 node through an 8.1.50 gateway to StrataView Plus.

No provisioning can occur while a Node-by-Node upgrade is in progress.

If a connection fails during Node-by-Node upgrade, it will not be re-routed until the upgrade process is completed.

Additional Deliverables

SNMP MIB:

The SNMP IPX/IGX/BPX switch SNMP MIB is being provided with the delivery of Release 8.4.00 Switch Software. The MIB is in standard ASN.1 format and is located in the ASCII text files switch.m, swtraps.m, and errors.m which are included in the same directory as the Switch Software images. These files may be compiled with most standards-based MIB compilers.

Switch MIB changes of Release 8.4.00:

1. atmEndptTable (Existing)

In order to support ATM Forum 4.0 Traffic Management specification,

atmEndptTable has been modified with obsolete, changed, and new objects.

* Obsolete objects:

. atmEndptMIR

. atmEndptCIR

. atmEndptPIR

. atmEndptMFS

. atmEndptOeMIR

. atmEndptOeCIR

. atmEndptOePIR

. atmEndptOeMFS

. atmEndptUPC

. atmEndptFastDnICA

. atmEndptScrPlc

. atmEndptOeScrPlc

. atmEndptPCR0

. atmEndptOePCR0

. atmEndptCDVT0

. atmEndptOeCDVT0

* Changed objects:

. atmEndptSubtype

. atmEndptConnDesc

. atmEndptQIR

. atmEndptPercUtil

. atmEndptCBS

. atmEndptIBS

. atmEndptCCDV

. atmEndptHiCLP

. atmEndptLoCLP

. atmEndptOeVcQSize

. atmEndptOeEfciQSize

. atmEndptOeQIR

. atmEndptOePercUtil

. atmEndptOeCBS

. atmEndptOeIBS

. atmEndptOeCCDV

. atmEndptOeHiClp

. atmEndptOeLoClp

. atmEndptCLPTagging

. atmEndptEnableFST

. atmEndptRateUpICA

. atmEndptRateDnICA

. atmEndptToQIR

. atmEndptMinAdjustICA

. atmEndptFGCRA

. atmEndptOeBCM

. atmEndptOeFGCRA

. atmEndptGroupDesc

* New objects:

. atmEndptNRM

. atmEndptFRTT

. atmEndptTBE

. atmEndptVSVD

. atmEndptPolicing

. atmEndptPCR

. atmEndptOePCR

. atmEndptSCR

. atmEndptOeSCR

. atmEndptMCR

. atmEndptOeMCR

2. atmBwClassTable (Existing)

In order to support ATM Forum 4.0 Traffic Management specification,

atmEndptTable has been modified with obsolete, changed, and new objects.

* Obsolete Objects:

. atmBwClassMIR

. atmBwClassCIR

. atmBwClassPIR

. atmBwClassOeMIR

. atmBwClassOeCIR

. atmBwClassOePIR

. atmBwClassUPC

. atmBwClassFastDnICA

. atmBwClassScrPlc

. atmBwClassOeScrPlc

. atmBwClassPCR0

. atmBwClassOePCR0

. atmBwClassCDVT0

. atmBwClassOeCDVT0

* New Objects:

. atmBwClassNRM

. atmBwClassFRTT

. atmBwClassTBE

. atmBwClassVSVD

. atmBwClassPolicing

. atmBwClassPCR

. atmBwClassOePCR

. atmBwClassSCR

. atmBwClassOeSCR

. atmBwClassMCR

. atmBwClassOeMCR

. atmBwClassRateUpICA

3. ShelfSlotInfoTable

* New Objects:

. slotFrontIfMode

. slotFrontNumPort

. slotFrontQueue

. slotFrontLnFormat

. slotFrontChCount

. slotBackNumPort

. slotBackLnFormat

. slotBackSonetMode

. slotFSTSupport

4. ds3LineTable

New objects in ds3LineTable have been introduced to support local

and remote DS3 interface (lines, trunks) loopback. DS3 interfaces

on ASI, BNI, and BXM are supported.

* New Objects:

. ds3LineLclLpbk

. ds3LineLclRmtLpbk

5. sonetIfTable

New objects in ds3LineTable have been introduced to support local

and remote Sonet interface (lines, trunks) loopback. Sonet interfaces

on ASI, BNI, and BXM are supported.

* New Objects:

. sonetIfLclLpbk

. sonetIfLclRmtLpbk

====================================================

Switch MIB changes of Release 8.4 Additional Requirements:

====================================================

Note: Section 1-5 list new tables introduced. Section 6-8 list new

objects added to existing tables.

1. ds1LineStatsTable (New)

New Real Time Counters (RTCs) have been introduced for DS1 media.

* ds1StatsBpvs

* ds1StatsFs

* ds1StatsOofs

* ds1StatsLos

* ds1StatsFers

* ds1StatsCrcs

* ds1StatsOoms

* ds1StatsAis16s

* ds1StatsHcsErrs

* ds1StatsLcvs

* ds1StatsCPcvs

* ds1StatsPPcvs

* ds1StatsPlcpBcvs

2. ds3LineStatsTable (New)

New Real Time Counters (RTCs) have been introduced for DS3 media.

* ds3StatsOofs

* ds3StatsLos

* ds3StatsLcvs

* ds3StatsCPcvs

* ds3StatsPPcvs

* ds3StatsPlcpBcvs

* ds3StatsAtmCrcs

* ds3StatsPktCrcs

* ds3StatsPlcpOofs

3. sonetStatsTable (New)

New Real Time Counters (RTCs) have been introduced for Sonet media.

* sonetStatsOofs

* sonetStatsLos

* sonetStatsAtmCrcs

4. fpTrunkStatsTable (New)

New Real Time Counters (RTCs) have been introduced for Fast Packet trunks.

* fpTrkStatsTxVoPktDrps

* fpTrkStatsTxTsPktDrps

* fpTrkStatsTxNonTsPktDrps

* fpTrkStatsTxHiPrioPktDrps

* fpTrkStatsTxBdataAPktDrps

* fpTrkStatsTxBdataBPktDrps

* fpTrkStatsTotalPktsTxtoMxbs

* fpTrkStatsTotalPktsRxFromMxbs

5. atmTrunkStatsTable (New)

New Real Time Counters (RTCs) have been introduced for ATM trunks.

* atmTrkStatsTxVoPktDrps

* atmTrkStatsTxTsPktDrps

* atmTrkStatsTxNonTsPktDrps

* atmTrkStatsTxHiPrioPktDrps

* atmTrkStatsTxBdataAPktDrps

* atmTrkStatsTxBdataBPktDrps

* atmTrkStatsRxVoPktDrps

* atmTrkStatsRxTsPktDrps

* atmTrkStatsRxNonTsPktDrps

* atmTrkStatsRxHiPrioPktDrps

* atmTrkStatsRxBdataAPktDrps

* atmTrkStatsRxBdataBPktDrps

* atmTrkStatsSpacerPktsDrps

* atmTrkStatsTotalPktsTxtoLns

* atmTrkStatsTotalPktsRxFromLns

6. fpRoutingTrunks Table (Existing)

fpRoutingTrunks table has been enhanced with new objects.

* New Objects:

* fpRteTrkXmitRate

* fpRteTrkPassSync

* fpRteTrkStatRes

* fpRteTrkLoopClock

* fpRteTrkBdataBTxQlen

* fpRteTrkBdataBRxQlen

* fpRteTrkBdataBTxEfcn

* fpRteTrkBdataBRxEfcn

* fpRteTrkBdataBTxHiClp

* fpRteTrkBdataBRxHiClp

* fpRteTrkBdataBTxLoClp

* fpRteTrkBdataBRxLoClp

7. atmTrunks Table (Existing)

atmTrunks table has been enhanced with new objects.

* New Objects:

* atmTrkXmitRate

* atmTrkPassSync

* atmTrkStatRes

* atmTrkLoopClock

* atmTrkBdataBTxQlen

* atmTrkBdataBRxQlen

* atmTrkBdataBTxEfcn

* atmTrkBdataBRxEfcn

* atmTrkBdataBTxHiClp

* atmTrkBdataBRxHiClp

* atmTrkBdataBTxLoClp

* atmTrkBdataBRxLoClp

* atmTrkMaxChanPort

8. shelfSlotInfoTable (Existing)

* New Object:

* slotCardMuxBusUtil

Features Not Supported

Committed (but not being delivered in this release):

None

Explicitly Excluded:

Virtual Trunks on any BXM cards.

The following cards are not supported in this release:

— ALM-A

— ALM-B

— UFM-C

— UFM-U

— UVM

Obsoleted:

Grouped Connections are not supported, unless they existed prior to the upgrade to this release. In that case, they are carried forward as part of the upgrade. Grouped connections can no longer be created in this release. Existing grouped connections can be modified with the cnfcon command.

Priority Bumping is no longer supported.

Notes & Cautions

Limitations

Structured Networks are not supported.

The maximum number of ports on the BPX that can be configured with LMI enabled is 38. Note that the total number of ports is 72 (for 32MB BCC) or 100 (for 64MB BCC), although only 38 of these can have LMI enabled. This is due to the polling that must be done for the LMI enabled ports. However, if any or all of the 16 possible feeder trunks are not being used on that specific node, then that many additional lines may have LMI enabled. That is, if a BPX is configured with only 2 feeder trunks, then 36 + (16 - 2) = 50 lines can have LMI enabled. Thus, the overall total can be 52 ports, when no feeder trunks exist.

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

The feature of CIR=0 for Frame Relay connections is not supported for connections terminating between FRP /FRM cards in IPX/IGX nodes and FRSM cards in an AXIS shelf.

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

The FRP port does not show the FECN/BECN frames count. FECN and BECN bits are only registered on the egress port or connection, not the ingress. (See bug CSCst96096).

For the loadrev operation, it is important that the StrataView Plus/TFTP buffers are maintained at their default size.

When the BNI trunk is connected to IM-ATM pairs, which carry less than T3 bandwidth, the granularity of the cell output engine must be taken into account in setting the BNI transmit rate.

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

If using the no shift feature to utilize Virtual Trunks across a Cisco/StrataCom cloud operating an 8.1 release, then the node number "2" must either not be used, or be the node connecting to the cloud.

If using the no shift feature to utilize Virtual Trunks across a Cisco/StrataCom cloud operating any Switch Software release, then the ForeSight feature will not be utilized. In general, any connections which are routed or potentially may be routed through Virtual Trunks must not be configured with ForeSight enabled.

If the Stat Reserve field on a trunk is dramatically increased to a value which represents a significant majority of the total trunk bandwidth, then if connections are present on the trunk, the dspload command will show negative values. This is to signify that the trunk is oversubscribed. The trunk load values will eventually reach 0, or a small positive number after all the necessary connections are routed off that trunk. (CSCdi84878)

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

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

The BXM cannot return Foresight Round Trip Delay cells. Thus, as of this release, the ForeSight adjust interval will no longer be a function of the Round Trip Delay calculation for the connection. Instead, all BXM terminated connections will use the maximum adjust interval. This affects all ForeSight endpoints on AXIS, BPX, and IGX. (CSCdi87455)

The external ABR segment control loop on ForeSight (ABRFST) is an option at the User Interface, but is not supported in hardware. The user should not enable this option on ForeSight connections (CSCdi92451). In any case, there is no coupling between the loops.

A problem has been observed, on several instances, where the time to re-route connections may take over an hour. When large numbers of connections are being re-routed, this can be caused by routing collisions, which means that routing attempts being initiated at different nodes collide when they meet a common node at which point one of the routing attempts must be rescheduled. (CSCdi89734)

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

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

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

The Command Line Interface currently allows a standard ABR VSVD endpoint to be configured (with cnfcon) as a non-VSVD endpoint. This should not be allowed because the BXM does not support this. This should not be attempted since it will cause connection continuity failure. (CSCdj08862)

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

0-3999 connections Polling Rate: 5 Minutes (or higher)

4000-8000 conns Polling Rate: 10 Minutes (or higher)

8000-12000 conns Polling Rate: 15 Minutes

Given a connection that terminates on an IGX FRM at one end and an ASI on the other end, tstdelay initiated at the FRM end may not work if the ASI firmware is below the appropriate revision and does not support OAM cells as opposed to supervisory cells. This is because the updated BTM on the IGX will always generate OAM cells. Please check the compatibility matrix.

The tstcon command does not work (it indicates continuity failure when it is not the case) when initiated from an FRSM card on an AXIS shelf and the path of the connection passes through an IGX node. (CSCdj23908).

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

The setnovram command can be used on BXM cards to change the number of channel statistics. If this number is set to 0 to increase the number of channels available on the card, dspchstats command will not work properly.

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

Impact:

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

Reason for the current implementation:

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

Future AIS support:

There is a discussion in progress for an improvement, which will apply only to connections that are routed only over BXM trunks (or dax connections).

Two new options are added to cnfcmparm (CSCdj26583):

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

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

When you first bring up the image through lanbtld your default values will be 100 for Wait for TBL Updates and 258 for Max Derouting Bndl. This is because some fields in CM_PARMS are being reused. The recommended values for these parameters are 70 (for option 20) and 500 (for option 21). These will be the default values if you do a clear mem or upgrade to 8.4.1. If you don't want this new feature:

1) set option 20 to 0

2) set option 21 to 0 (which means all connections)

These parameters are used for:

1) Wait for TBL Updates will delay failing the connection if it fails to find a path due to no load and no conid available. This delay allows TBL updates to be processed. This value should always be greater than the cnftlparm Fast Interval interval. This will clear some PVCs going in and out of alarm.

2) Max Derouting Bndl works like Maximum Routing Bundle, except it's for the derouting case. Currently we go and deroute all 12,000 connections at one time without giving up the process to handle TBL updates, and other tasks. This value will allow us to deroute x number of connections at a time, then go and try to route. Do remember that as this number goes up, the table updates takes a little longer to be sent out, since the node is busy derouting.

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

During a conditional upgrade or downgrade in the network that has more than 20 nodes, there is a likelihood for some nodes to receive all the updates before receiving the revision change message (to upgrade/downgrade). Since the standby had the update capacity of approximately only 10 mesg/sec, it may take over 3 seconds for these nodes to finish these updates. The revision change update may not be properly delivered to the standby, and thus causes non-graceful upgrade to occurred on these nodes. (CSCdj32054).

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

In certain conditions where memory is exhausted, an Abort 3000000 can occur, which is fully recoverable. This is due to an accumulation of memory in the telnet process, and the root cause is the improperly terminated telnet sessions that were originated from a StrataView Plus workstation. To prevent this condition from occurring, exit all SV+ telnet sessions correctly by using the CTRL-] key chord and then typing q. (CSCdi92256).

BXM cards can support 32K PVCs only when no stats are collected. If collecting 4 stats per PVC is desired, the number of PVCs per BXM card drops to 16K. (CSCdj31773).

When connection status logging to StrataView Plus is enabled in the switch (via the cnffunc command), when more than 1500 PVCs exist on a node, an event log entry indicating there is a "comm break on flooding" may occur. This is because the network handler is being flooded with messages due to the per-PVC status updates flowing to the StrataView Plus workstation. This is a recoverable situation. However, PVC status may not be available for all connections. (CSCdj36127)

It is not recommended to combine ABR and UBR PVCs on the same network. ABR and UBR PVCs share the same QBIN (Class of Service Queue) on the BXM card. However, ABR (VSVD) uses a flow control mechanism which ensures that the traffic source slows down when the QBIN usage exceeds the EFCI threshold. However, UBR does not have a mechanism to slow down. Thus, UBR traffic gains an unfair advantage over ABR. This implementation is not considered a problem, since the decision to share a QBIN for ABR and UBR traffic was intentional, since any best-effort service that one would route over UBR can be routed over ABR (VSVD), with the additional benefit of protecting resources in the network. If there is a real requirement to use UBR PVCs instead of ABR (VSVD), then either (1) add all best-effort PVCs as UBR, or (2) isolate the ABR and UBR paths by using cnfpref and separating ABR and UBR endpoints.

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

If a TFTP download has been started, and a fault occurs in the network that interrupts the download, then it is possible to get an software error 513 logged into the software error table. This occurs when there is an attempt to free a memory block that has not been allocated. There is no negative side effect to this attempt, other than the appearance of the error in the table. (CSCdj45311).

The maximum number of VC PARMS supported: 749 for BCC-32 MB, 2,999 for BCC-64 MB. (CSCdj48589).

Upgrading from release 8.2.xx to release 8.4.11 may necessitate re-routing of the "path" connections and data discontinuity on some connections. (CSCdj53625).

A hardware limitation on the BXM card can cause the background test to fail. This occurred when the BXM card was used as trunk card with number of stats set to 0 so that all 32K channels could be used, followed by the card being changed to a port card. Software uses the last 15K channels for background test. Since the card is configured to use all 32K channels, there is not enough memory available for the background test, and therefore the test fails. For the background test to work on the BXM card, only 16K channels can be utilized. (CSCdj49679).

Required Workarounds:

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

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

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

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

After a Node-by-Node upgrade, it has been observed that Load Model inconsistencies may exist on BPX nodes. User should check the current load value. If the load value for MCR=0 is zero, then the MCR value should be changed to MCR=1 before upgrading to 8.4. (CSCdj35064).

Statistics collection must be disabled prior to the start of an upgrade.

Statistics sampling must be disabled prior to the start of an upgrade (using off1/off2).

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

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

When the last trunk to a node is deleted and it has 2500+ connections, it will cause software errors 1000's and 590's. This can be avoided by first deleting all connections across the trunk before deleting the trunk. If the problem occurs a switch over or rebuild will clean up the node. (CSCdj25075).

The software error occurs when deleting a trunk that

1) Splits the network (i.e. the last trunk to a node, or the only trunk connecting two sub nets).

2) Has 2500+ connections routed across it to a single node.

Note: These connections do not have to terminate at the two nodes directly connected to the deleted trunk. The trunk being deleted could be connecting two subnets. If those 2500+ connections are on one node in either of the subnets then this problem can occur. If these 2500+ connections are spread about different nodes in the connected subnets there should not be a problem.

EFFECT: Not all connections that should be deleted will be deleted. In addition, memory leak may occur.

WORKAROUND: Prior to deleting the last trunk to a node, determine the connections going across the trunk and manually delete them first.

CLEANUP: If software errors 1000's and 590's are received because the last trunk on the node was deleted AND that trunk had 2500+ connections routed across it. The problem can be cleaned up by:

1) Clear the active CC's software log.

2) Check then clear the standby CC's software log.

3) switchcc

If the network does not have a redundant CC then rebuild the active CC by doing the following:

Clear the active CC's software log.

resetcd <active CC slot>

For grouped connections, if and when all connections of a group are deleted, then the connection group itself should be deleted as soon as possible to avoid any possible side effects that could potentially be caused by having empty connection groups. (CSCdj47562)

Additional Documentation:

Prior to Release 8.1.70, with regards to statistics collection, any time period was allowed to be a peak interval. However, those peaks were not gathered correctly. In this release, the peak intervals are controlled to be only those values for which peaks can be accurately collected The rules for peak intervals are as follows:

•It cannot be 0.

•It must be a multiple of the polling interval.

•It must be a factor of the bucket interval.

•It can be the same as the bucket interval.

There are additional commands to control trunk and line loopbacks in this release:

•addlnlocrmtlp <trunk> | <line>

On the node on which it is executed, creates a loop back within the port such that the cells do not leave the card.

•addlnloclp <trunk> | <line>

On the node on which it is executed, creates a loop such that incoming cells are looped back to the other end.

•dellnlp <trunk> | <line>

Removes the loopback added by either of the above two commands.

Compatibility Notes

See the Compatibility Matrix document, which is included in this release package.

This release will run with any AXIS Release 4.0.0x, 3.0.x, and 2.1.x

Known Anomalies in this Software Release

The following is the list of known problems in this switch software delivery.


Bug ID	Descriptions
CSCdj51978	Symptom: Upgrade and downgrade to fast modem state causes data hit
CSCdj54495	Symptom: Resetting a BXM trunk card on a BPX node causes lots of PVC to receive fail status and being rerouted. It was noted that ILMI failure also occurred on the neighbor slot with BXM line card installed. Condition: When the ILMI timers and retry values are low, momentary communication failures will be noticed when the switch is extremely busy. Workaround: Adjust the values for T491, N491 and N492 using the cnfport command.
CSCdj55305	During the BNI/ASI Firmware upgrade to TCK, Comm Breaks occurred on BPX nodes after BCC switch over and started to clear immediately. It was noted that there was a node rebuild in the network at the time which lasted for approximately 55 minutes.
CSCdj58038	Symptom: Software error 21s are seen on several BPX nodes running switch software 8.4.11. These software errors appear to be intermittent. Workaround: There's no known workaround at this time.
CSCdj63195	Abstract: Need a counter for BXM cell discard due to port congestion. Description: Cells are discarded by BPX due to BXM port congestion is to compare FROM network counter congestion is to compare FROM network counter with TO PORT counter. A counter is needed to show how many cells are discarded.
CSCdj68190	After upgrading a BCC-3-32 to SW 8.4 software, the BCC can experience "SAR Failures" (swerr 742 - selftest failures).
CSCdj72899	atfr connections using a VPI greater than 15 on the ASI card won't pass traffic. The axis shelf will record IngressInvalidCellCount on the bnm card.
CSCdj72907	Symptom: After a CC switchover (including graceful upgrades), the receive side loading for trunks on that node (where the switchover occurred) show zero (0). Conditions: Upgrades and switchovers. Workaround: 1) For each trunk exhibiting the load inconsistency, use dsptrks command to determine the node on other end of that trunk. From the node at the other end of the trunk issue "updates 2 <node with load = 0)". This will initiate a conditional update which passes the trunk loading information for the node issuing the updates. OR 2) Wait for the conditional updates to issue themselves. This will occur normally after a switchcc or upgrade, but at a slower rate. The nodeparm #2 dictates the interval between requests for conditional updates, and a different node (in node number order) is requested at each interval. So the load will correct itself after (nodeparm#2) x (#nodes in network). Further Problem Description: This is a relatively benign. If a connection fails to route because a node's loading information is not up to date, the nodes which the connection (when routing) determines is "out of synch" automatically issue the loading update to the connection's master node. Therefore, the worse case scenario here is that if connections need to reroute after an upgrade/switchover, they may take multiple tries to reroute.
CSCdj77629	Software error (4208) on BPX node.
CSCdj78167	Three software errors reported: 37, 4208 and 3049 in a test environment running 8.4.1e on BPX/IPXs and 4.0.06 on Axis shelves.
CSCdj79112	Unable to add a PVC on a BXM T3 at less than 50cps/19.2kbps. It appears the BXM has a limit for smallest SCR/CIR, not allowing a PVC to have a SCR/CIR less than 50cps/19.2kbps. The ASI does not have this restriction. This Command: addcon 9.3.44.444 nodename 9.2.44.444 abrfst 40 PCR(0+1) value out of range (local end). Valid range 50 - 96000. PCR(0+1) [50/50]:
CSCdj79121	BXM-T3 in slot 9 logged one non fatal 0A hw error. The BPX node being tested rebuilt due to a power failure just before this happened. The node is testing sw rel 8.4.1e. Hardware Error Event: 0A 08 00 00 00 01 00 00 09 09 00 4E 6F 6E 20 46 61 74 61 6C 20 45 72 72 ... Processor : 00 Module : 01 Error Code : 00 Card Type : 09 ??? Description : `Non Fatal Error Info from 0x17: 0x250f0075 0x0 0xd3b 0x1 `
CSCdj80063	Abstract: Max Channels/Port can be below the actual #Channels!! Description: The Max Channels/Port cnt was set to 5000 on trunk 5.11 on bpx. There were 2985 channels added on the AXIS Feeder attached to 5.11. I later reduced the value of the "Max Channels/Port" on this trunk to 2710. Though the #channels on the feeder attached to this trunk > 2710, I was allowed to bring it down to 2710. What are the implications?? The switch should not allow the user to configure this value below the existing Channel count on the trunk. This needs to be investigated. Workaround: For TRUNKS - none required. The connections will be derouted and then rerouted up to the new limit. For FEEDERS - check the current usage prior to modifying it. SWS Engineering write up sent to customer: Max Channels/Port may be configured below current use. For routing trunks the connections would be derouted and then rerouted back onto the trunk (up to the new limit). There for, this would be a non-issue. For feeder trunks, what is expected is that the channels stay allocated for their current use, and failures are expected when allocation requests are made for the in use channels. The planned correction is to screen the user inputs for feeder trunks to be equal to or greater than the current allocation.
CSCdj80943	Symptom: Fallback from 8.5 to 8.4.13 corrupts BPX password
CSCdj83433	Symptom: BPX running software release 8.4.11 logged software error 4208 twice. The event log shows only login/out activity at the time the errors occurred. The customer wants to know why these errors were logged.
CSCdk02608	Symptom: When a BXM is reset and expected to come to the standby state, the standby state is reported before the switch software has completed the reprogramming of the card. Conditions: This problem exist when a BXM is reset and the risk is that pvc not yet programmed will lose service if this card is activated before the card is reprogrammed. Workaround: In release 8.4.21 (or later) use the dspcd command to see if the "PRGM" symbol is displayed. When it is, the card is in a `cold' standby state, but has not finished channel programming to be in a `hot' standby state.
CSCdk03916	Symptom: Trunk information is inconsistent
CSCdk04087	Description: Running scripts to add PVC's from a bpx node to an axis shelf via a routing bpx node with software release 8.4.2c, multiple software error 37 were logged at the bpx node and to the routing bpx node.
CSCdk21995	Symptom: Upon upgrade from 8.1.25 to 8.4.18 the cnfclksrc E 2 P 2 failed! Conditions: Upgrade from 8.1.25 to 8.4.18 swsw did not accept external clk src. Workaround: cnfclksrc E 1 P 2 instead of cnfclksrc 2... should work. Further Problem Description: THE SCM on igx has two ports. one bnc and the other d-type. In 81 the customer always used nfclkcsrc command with line option and value 2 as line. After upgrade we saw ext clock source alarm. I saw that ckdb command showed that Failed Line was 3. Which looked in-correct. because if customer used cnfclksrc l 2 then it show the failed line as 2. So what we did was to do cnfclksrc l 1 - and then everything zipped back to normalcy. Earlier it was refusing to accept that as the clock! However, if we configured a different line which had a pbx connected to it as clk src - it worked correctly.
CSCdk24406	Symptom: StrataView Plus database shows incomplete pvc not in network
CSCdk26372	Symptom: Same LCN range allocated to 2 y-cabled BXM ports (same card)
CSCdk28346	Symptom: Dspswlog shows software error 419
CSCdk29737	Symptom: Unable to provision PVC Conditions: Parameter 24 of cnfsysparm set @ 5 Workaround: Disable stats from cmgui and reconfigure cnfsysparm 24 back to 15
CSCdk29997	Symptom: Software error 21 Occurs when do switchcc. This occurs because an ACM self test command is sent to the BTM-HP card, which, since it is not an ACM card, does not accept this command. Conditions: Bug does not occur in 9.1 Workaround: None.
CSCdk30177	Symptom: dsplog reports NTM missing after power cycle. Description: Power was turned off and on an IGX node. NTM cards show missing on dspcds. dsplog shows NTM missing.
CSCdk34273	The problem could be reproduced in the lab by invoking a `cnfport' cmd on a ipx node. Findings: The msg from the ipx captured in the StrataView Plus log (emsc process log) indicates that the value of dethreshold as sent by the ipx is incorrect.
CSCdk34622	When adding a FR port on IPX FRP card (thru SNMP) with protocol type as LMI-ASYNC, the node creates the corresponding port with the correct protocol type but in the robust message the value is sent as type 1 (no protocol) instead of 3 (LMI-ASYNC). This works fine if adding it through the CLI.
CSCdk42459	Symptom: Y-red switch on BXM causes BIP16 errors and 88 unreachables
CSCdk42527	Symptom: FCES: When LOS, VSVD rates are wrong on dspchstats
CSCdk42533	Symptom: FCES: on LOS, RateDowns do not cross NNI (FCES fails to work)
CSCdk42543	Symptom: FCES: When LOS occurs, chan stats counters change.
CSCdk42546	Symptom: FCES: After LOS cleared display problem/Queuing problem
CSCdk42552	Symptom: FCES: Wrong values displayed for Ingr VSVD/Egr VSVD
CSCdk42555	Symptom: FCES: avg cps egress port doesn't match ingress port on nni
CSCdk42557	Symptom: FCES: Foresight does not work at ingress point of network
CSCdk45040	Standby BCC-3-32 goes into UP Failure when Primary clock source goes into Bad Clock Source.
CSCdk45279	Symptom: Unable to configure PCR0+1 above 96,000cps because the mib is not updated to do so. StrataView Plus ConnMgr GUI does user input validation on the values given according the SWITCH mib. Following is the extract from SWITCH mib for PCR(0+1). atmEndptPCR OBJECT-TYPE SYNTAX INTEGER (50..1412832) ACCESS read-write STATUS mandatory DESCRIPTION "PCR(0+1), Peak Cell Rate, specifies an upper bound on rate at which traffic can be submitted on an ATM connection. This object applies to the First Leaky Bucket for leaving cells with Cell Loss Priority of 0 or 1. . Units: cells per second. . Applicable connection types: UBR, CBR, VBR, ATFR, ABRSTD, ABRFST, ATFST . Default: 50 . Ranges: T3 : MCR-96000 E3 : MCR-80000 OC3 : MCR-353208 OC12: MCR-1412832 Limited to 7-5333 cells/sec for ATFR connections. " ::= { atmEndptEntry 76 } According to this definition for T3 interface the range for PCR(0+1) is from 50-96000 CPS and that's what is checked by StrataView Plus. However, if the line is configured for HEC Cell Framing the port speed is changed from 96000 CPS to 104268 CPS on the switch for BXM-T3 card. And, switch accepts connections with PCR(0+1) value set to this maximum limit. However, StrataView Plus can't check for this limit and accept as there is no description of this behavior in the Switch MIB and that is the only interface for StrataView Plus connection manager and the SNMP Agent on the switch. Please also note that similar differences may exist for other interfaces like E3, OC3 or OC12 with Cell Framing set to HEC. Conditions: BPX Switch Software 8.4.19 BXM card (with M.B.X. of BXM Firmware) StrataView Plus 9.0.03 Workaround: None
CSCdk26164	dsprts command will not show voice and data connection routes. dsprts can be issued on an individual connection and the route will be displayed. This is a display problem, not a problem with the connections themselves.
CSCdj43626	After a dncd and a deltrk command were issued on a BPX card that had connections, no other connections would route because the node kept trying to route the deleted connections. The User interface became locked up.
CSCdj91072	BXM card state and card type are not correct in the dbase
CSCdj95344	2 AXIS shelves unreachable from BPX node.
CSCdj95355	Cannot add PVCs on BPX node.
CSCdk00534	BPX node cannot find routes for PVCs and PVCs do not fail.
CSCdj18255	Phantom FP connections appear in the dspcons command When performing dspcons, connections appear in the list that have not been added and are not valid, when `n' pressed at the `Continue?' prompt Conditions: Occurred after upgrade from 8.1.26 to 8.2.04 Workaround: None
CSCdj54495	BXM ILMI failure
CSCdj55305	During the BNI F/w upgrade, atlnga82 reported Comm Breaks with all BPXs
CSCdj55787	BCC cards stuck in down loader state.
CSCdj63195	Need a counter for BXM cell discard due to port congestion.
CSCdj66407	BPX Reports Swerr 135 at 10 Sec Interval
CSCdj68190	BPX: BCC-3-32 swerr 742 (SAR_FAILED) after upgrade to SW 8.4
CSCdj70098	swerr 2057 seen on bpx nodes
CSCdj70792	Specifying pathname and file in the dnld.sw/fw files the nodes use a / al
CSCdj72867	BPX has B-frame parity errors
CSCdj72907	Updates not getting properly propagated after upgrade
CSCdj77592	s/w err (37) on BPX node.
CSCdj77629	s/w errs (4208) on BPX node.
CSCdj78733	BPX drops static memory from 100 k bites to 0 in just few hours
CSCdj78766	additional s/w 21 errors on kbbpx700
CSCdj78870	BPX experienced swerr 370 after resetcd on the active BCC
CSCdj79040	BPX running 8.4.1e experienced swerr 372
CSCdj79112	BXM does not allow SCR/CIR less than 50cps/19.2kbps
CSCdj80063	Max Channels/Port can be below the actual #Channels!
CSCdj81244	3M (3000000) abort and swerr 501 on bpx. Memory accumulation in ILMI problem
CSCdj83416	BXM rev BBU logs one 0A hw error following active BCC resetcd
CSCdj83433	BPX logged swerr 4208
CSCdj86905	Can not route OC12 traffic load over an OC12 BXM trunk
CSCdj88281	BXM-OC3 shows erroneous value (2^32 -1) every 24 hrs on line stat in SV+
CSCdj89212	line transmit rate not initialized on an E1 trunk
CSCdj89583	BIP16 Slot alarm does not clear automatically in the absence of alarms
CSCdj89954	can not modify atmEndPointICRTO on asi port to 10000
CSCdj93825	abrfst connection from BXM to BXM over virtual trunk does not work.
CSCdj94479	SV+: HPOV Event log reporting incorrect information on IGX
CSCdj95224	Card errors on 4 different cards on a BPX
CSCdj95268	Card error #6 (1) and s/w error 105 on a BPX
CSCdj95300	Multiple s/w err (501 332 333) occurring on a bpx
CSCdk00310	card error (BXM/BDW) and s/w err 21 on a bpx node

Corrected Anomalies in this Software Release

The following conditions have been corrected with the 8.4.30 version of the software release.


Bug ID	Descriptions
CSCdj28429	Symptom: Frame relay connections routed through a BTM trunk experience egress discards. Conditions: On the `dspchstats', the rate of egress discards increases with increased utilization on the BTM trunk. Infrequent bursts of Rx Spacer Queue discards (under `dsptrkerrs') are also seen. Connection egress discards cease when traffic falls below ~5% utilization on the trunk. At least one via connection which traverses from BTM to NTM. Work Around: None
CSCdj39813	Symptom: On screens showing QBIN thresholds for the BXM, such as cnftrkparm and cnfportq, the prompt for `CLP Lo threshold' should actually read as `EPD threshold' for VBR, ABR, and UBR QBINs. On these connection classed, CLP hysteresis has been disabled. Also, on ABR connections, when FBTC is selected, both addcon and cnfcon should use `EPD' instead of `CLP Lo'. Conditions: Under all conditions Workaround: No workaround.
CSCdj47177	Symptom: BCC Selftest may not run if the node does not have a 100K block of memory available. Condition: When a BCC's dynamic memory is heavily used and a 100K block of memory is not available the selftest does not run. The test should check for a smaller size, since it does use this memory during the test. Workaround: None.
CSCdj48992	Symptom: dnfrport and delfrport are not allowed when an active FRP/FRP is removed. This is inconvenient, since the card has to be replaced before the commands are allowed. Condition: An FRP/FRP slot is active and all connections are deleted. If the card is removed, downing the port or deleting the port will not be allowed. This used to be allowed. Workaround: Reinserted the FRP/FRM and then execute the commands.
CSCdj49647	Symptom: Standby controller card gets reset. Conditions: Standby Controller card would not be in a steady standby state which is a result of periodic standby resets. These resets could be confirmed from the log (using dsplog command). This should not effect the functionality of the Active. Workaround: Further Problem Description: This problem seems to be the result failed communication between the active and the standby. Active keeps all the messages on the standby queue and frees them only when an acknowledgment is received from the standby. Because of the failed communication, lots of these standby messages are getting collected on the queue, resulting in shortage of memory, memory error and memory abort. The current fix puts a limit on the amount of memory that can be collected on the standby queue and hence we would not encounter memory shortage on the active card.
CSCdj49869	Symptom: Node aborts with a 1M3 (1000003) after entering the source port for the cpyict command. The initial 1M3 abort may be followed by additional 1M3 aborts, 2M aborts, and software error 514s, all of which indicate memory corruption. In some releases a clrcnf may be required to bring the node back online. Conditions: Use of the cpyict command with software releases between 7.2 and 8.4.1x. Release 8.5 does not have the problem. Workaround: Do not use the cpyict in releases between 7.2 and 8.4.1x. The cpyict command was broken when the FastPAD (FTC) feature was added.
CSCdj52297	Symptom: A-bit alarm does not clear even if both sides of the NNI connection are upped and in OK state Condition: 1. Two networks with 8.2 release and the other is 8.5 2. A bpx is attached to an axis and an ATFR 2 segment connection is added. 3. An FR-FR 1 segment non-dax connection is added between 2 routing IPX (or IGX) one of which has its FRM physically cabled to the axis in (2). The axis FRSM and the FRM/FRP has NNI established. 8.2 network 8.5 network bpx ipx2 \| \| at-fr 2 seg \| \| fr-fr 1 seg \| \| axis ----------------------- ipx1 down the ipx1 down the bpx up the ipx1 up the bpx The A-bit alarm does not clear. NOTE: It does not matter whether the networks are of 2 different releases. This happens in 8.5.E2 on both networks with AXIS FW 4.0.3a also Workaround: Down and up the other end of the connection to cause a change of state, i.e., down the connection on the other endpoint node attached to the AXIS.
CSCdj54662	Symptom: 1000003 software abort occurred on an IGX node. Conditions: Runrev command had recently been executed on the node, and node was busy sending inter-task messages (as evidenced by dspprf a t n screen). Workaround: None
CSCdj55059	Symptom: Test delay failed. Condition: Test delay (tstdelay) will fail when the connection routed through BTM and AIT. Work Around: None
CSCdj56926	Symptom: Display port failure indication is wrong. Condition: When a BXM port fails, the alarm display on the dspalm screen reads "ASI Port Failure". This is misleading as the ASI ports may be ok. Work Around: If the dspalms page shows a Port Failure on a BPX, check which ports failed by issuing the dspports command.
CSCdj58429	Symptom: 1. The connection deroute delay timer may not get cancelled due to invalid logic in the code. 2. Software error 923 may appear. Condition: 1. Have the connection deroute delay timer be enabled by configuring a nonzero value for the timer. 2. Fail the trunk. 3. If the trunk repairs, the timer should get cancelled. With the bug, the deroute delay timer may not be cancelled. Workaround: Do a switchcc to reset the trunk delay timers of all the trunks in the node. If any of the trunks is still in fail state, the timers will get restarted. If the trunk is in OK state, the trunk will not have its timer restarted. Do this for both endpoint nodes of the trunk that will not clear. Merely turning the state machine for deroute delay "off2 28" will not cause the timer of an actual failed trunk to get restarted until a trunk change of state happens for that trunk, i.e., repair, then fail. So, if the trunk remains in failed state, its timer will not kickoff to start after the "off2 28". If the trunk deroute delay timer is configured to zero to disable the deroute delay feature, the connections will get derouted off the trunk even though it has repaired. This is because the bug causes the repair trunk event to not clear the state of the trunk with respect to monitoring its deroute delay timer.
CSCdj58620	Symptom: BPX node, without warning, suddenly performs a switchcc and complains about bus failure. Conditions: Currently, there is a counter (visible using the clkdb command) that specifies the number of Bad Bus Signals that have been seen. This counter can be cleared using clkdb clear. If not cleared and the counter increases past five (5) errors, the current processor is switched to the standby. Unfortunately, the number continues to increase over time and is not cleared automatically if no errors present over a period of time. Workaround: Use clkdb clear to periodically clear any error encountered.
CSCdj58729	Symptom: Could not burn fwrev from HCH to HCL with SuperUser level access Conditions: Customer was upgrading software and needed to go to HCL Workaround: Get StrataCom level access and burn firmware
CSCdj59313	Symptom: If a user attempts to add a connection to a trunk card, a software error 55 will result. Conditions: The most likely commands that will cause this problem are addcon, addfrcons and copycons. An SNMP script that adds connections can also cause the problem. Workaround: To prevent this software error, the user should not attempt to add connections to trunk cards. However, there is no serious harm to the switch software as the user will be notified that it is an illegal connection and there will be no attempt to actually add the connection.
CSCdj60364	Symptom: Occasionally nodes' information were erased from its database. Conditions: When multiple Strata View Plus workstations subscribed Link0 to the same node, and the multiple Strata View Plus workstations requested the topology at the same time, the gateway node would send partial network information to one Strata View Plus and partial to the other. Workaround: Restart the Strata View Plus. Further Problem Description: The Strata View Plus would think some or all nodes became inactive, and users could not add or modify connections, for instance.
CSCdj60607	Symptoms: Connections that were passing traffic prior to the switchcc or graceful upgrade may experience the following problems after the switchcc or graceful upgrade: a) connection no longer pass traffic, or b) connection traffic is being multiplied, more data is received than is passed in, data original from no source. Conditions: On a switchcc or graceful upgrade, the routing table on a trunk may not get cleared. This is an intermittent problem and is only observed on a NTC card. Workaround: Downing and upping the trunk card will cause the trunk card to be reprogrammed.
CSCdj60759	Symptom: A scanrgn of the dynamic region (RGN2) showed about 80 permanent allocations out of nw_assgn_rsmb(), which allocates memory for received network messages. Conditions: If tstcon fails, the memory is not always free. Analysis of the contents of the messages shows they are all C3 fcode, which is the TST_PKT_REQ message used by tstcon. The lpcons.t state table receives this network message, but does not free the memory after processing it. This leak does not occur if tstcon passes, and it may not occur in all fault isolation scenarios. Workaround: None. This is not a critical memory loss.
CSCdj63591	Symptom: It was observed that after adding FastPAD voice connections, the display screen may not show the mixed type FastPAD connections in order and that non-FR FastPAD connections may be missing from the display screen. Workaround: No known workaround.
CSCdj64676	Symptom: The date is off by 1 day starting 1/1/2001 00:00:00. Conditions: The leap year calculation was wrong. It did not account for the fact the years evenly divisible by 400 are leap years (e.g. 2000). Workaround: None. Further Problem Description: There would have been no effect until January 1, 2001.
CSCdj66231	Symptom: - The command addrmtlp doesn't work properly for BXM virtual path connections. The following message appears after attempting the loopback: "Remote connection loop back failed". - The command dspcons shows that the remote end of the connection is looped. - The loop cannot be removed because the local side thinks there is no remote loop. Loopback deletion may also fail due to a problem logged in CSCdj65863. Conditions: Problem has only been observed while attempting addrmtlp on BXM endpoints. Workaround: Delete and re-add the affected connection(s).
CSCdj66529	Symptom: dsplnerrs command does not count txcell dropped for BXM configured as line Conditions: Under all conditions Workaround: No workaround.
CSCdj68050	Symptom: Data discontinuity observed in a connection between two BPX endpoints. Conditions: The following conditions are met for at least one of the BPX cards along the connection's path: 1. A BXM card occupies a particular slot. 2. The BXM is never put in the ACTIVE state. 3. The BXM is removed, a BNI or ASI is installed in its place, and subsequently put in the ACTIVE state.. Workaround: No known workaround.
CSCdj68142	Symptom: When the SVC bandwidth is changed on a trunk, connections are not re-routed. Condition: SVC bandwidth was not taken into account to determine re-route condition. Workaround: The work around is to change the Statistical Reserve to force a re-route of connections on the trunk.
CSCdj69338	Symptom: Displaying a connection via dspcon whose endpoint is a card in slot 16 may give the error message "Connection does not exist". However the connection does exist and is visible with dspcons. Conditions: Same as above. Workaround: Display the connection using the other endpoint with dspcon. If a remote connection, vt to the remote node and issue the command there.
CSCdj69968	Symptom: When a endpoint is on slot 32, the connection shows up in dspcons but the message "Connection does not exist" when the dspcon, dcct or cnfcon commands are issued. Conditions: Same as above. Workaround: Examine the connection from its other end. Vt to the remote end if not a daxcon.
CSCdj71834	Symptom: All 1M3 aborts are not the same. The 1000003 abort in this bug report can at best be identified as an 1M3 abort from nw_respond_to_proc() and is logged from the NETW task (as can be seen in the error log entry). Only engineering/development team will be able to determine whether the abort is occurring from nw_respond_to_proc() or somewhere else by inspecting the descriptive abort error log. This abort happened in the software area of internal messaging between tasks. When messages are sent between processes, memory pointers are used to indicate where the message is and where the return message (answer) can be placed in memory for the process to access it. An index into the return message table was out of range. Use of this out of range index resulted in the abort. The engineer could not determine the chain of events that resulted in because many tasks use this function and the information from the abort did not provide the trace back of routine calls. He could, however, prevent it from happening again by checking the index to make sure it was in the valid range. It was the engineer's opinion that it was unlikely that this particular problem would occur in releases without his range checking fix. Conditions: There were no known exact conditions for this particular 1M3 abort. There could be other 1M3 aborts which have specific conditions and related workarounds. The chances for this particular abort to occur is extremely small in releases which do not include the fix for this bug report. This particular 1M3 abort instance will not occur in software releases which include the fix mentioned in this bug report. Workaround: There is no workaround for this particular 1M3 abort. There could be other 1M3 aborts which do have workarounds so as to avoid another occurrence. If there is a standby on the node experiencing the abort, a processor switchover will occur. If there is no standby on the node in question a rebuild of the node would occur.
CSCdj74644	Symptoms: Downed connections do not show the A-bit status in dspcons -abit. Condition: 1. Down a Connection 2. Cause a-bit status changes 3. The connection does not show in dspcons -abit WorkAround: Invoked dspcon <connection> to check the A-bit status. Related Information: A Downed or pending down connection that is in failed A-bit state will not show in dspcons -fabit, dspalms, or generate minor alarms for A-bit status changes. Downed connections should not generate alarms. A connection may be downed because: 1. It is a backup connection. In case of a failure on the primary connection the backup connection can be activated with a job. The backup connection should not generate an alarm. 2. The endpoint equipment has not been configured or is not in service, the connection can be downed to avoid generating an alarm. 3. It is a low priority connection and it can be downed to allow a priority connection to route. 4. It is a temporary connection which requires a large amount of bandwidth while it is in service (such as video conference). The connection may be downed when the service is not required. 5. The connection is one segment of an NNI connection. The segment can be downed to prevent an alarm when another segment is not in service.
CSCdj75662	Symptom: Random change in line status during switchover (CC) on logical lines greater than 64. Conditions: When do CC switchover, the erroneous line status change. Workaround: None. Further Information: Should clear by itself.
CSCdj75803	Symptom: SNMP, Strata View Plus, IP Relay functions seem to hang or do not respond. Conditions: Caused by SNMP managers sending multiple requests to SNMP Agent that have a PDU size of larger than 512 bytes. In some cases this can be caused by sending PDUs of size larger than 256 bytes if more than sixteen requests sent before the SNMP Agent can respond. Workaround: Use SNMP Managers that do not retransmit after a timeout period. Further Problem Description: Once occurred, the dsppna command shows that one of the buffer pool is depleted. If the wait: portion of the display shows nonzero, then a process (usually SNMP) is waiting on pNA+ for a resource that will never be serviced. Once a buffer pool is depleted, any process that needs a buffer of that size will be deadlocked waiting for the resource. So, Strata View Plus (the PROT process) can deadlock once the bug occurs.
CSCdj75805	Symptom: When the user command "freemem" is used, it is possible to cause a 1M3 abort. This can occur sometimes when an incorrect memory address is entered as input to the command. Conditions: Same as above. Workaround: This command is not often used, and is restricted to the highest login privilege level. Avoid using the command, or enter input data carefully.
CSCdj76228	Symptom: When trying to execute the "addtrk" command, The error message "Deactivated" is displayed. Conditions: This problem can be encountered on IPX and IGX nodes running Release 8.2.xx or 8.5.xx. Workaround: 1. Deactivate the card by deleting the lines (dnln/dntrk) and downing the lines (dnln/dntrk). 2. Physically remove the effected card from the slot and reinsert it. 3. Reactivate the lines (upln/uptrk)
CSCdj76844	Symptom: Software error 1427 and software error 254 and bpx node "dspnw" command shows UNREACHABLE. Conditions: Two problems occurs: 1) Software error 1427 - minor error - no apparent side effect - occurs when nw reroute is triggered or when msg_r_xchg is not set to zero before calling Send_xchg. 2) Software error 254 - major error - occurs when there are two or more nodes adding a trunk between bpx (node number greater than 63) and ipx/igx in release 9.1 Workaround: 1) It could cause problem if msg_r_xchg happens to be initialized randomly to a valid xchg, it will send response msg to the wrong return xchg. 2) Only happens in 9.1. Avoid rnmnd node numbers larger than 63 with a IPX/IGX node in the network. Once it happens, delete the trunk that has the IPX/IGX and rnmnd all nodes that have node number larger than 63 to number less or equal to 63, and re-add the trunk.
CSCdj78211	Symptoms: Pass Sync parameter is not updated to the standby. If the processor card switches, then the value is still default. Condition: The value reverts back after a switchover. Workaround: Again do the configuration using cnftrk on after a switchover.
CSCdj83509	Symptom: After loading 8.4.16 the first TSTPORT executed on the node works OK. Every subsequent one executed is aborted. Conditions: Effects 8.4.16 Workaround: I have not found a workaround
CSCdj84372	Symptom: 1) CVM/UVM dax voice connections with endpoints on the same card will not be re-programmed after rebuild or switchcc. This is a relatively rare case. Observed in 9.1, same code in 8.5, 8.4 and 8.2.5. 2) CVM/UVM to FTM interworking voice connections voice card endpoint is not reprogrammed after rebuild or switchcc. This maybe less rare. Observed in 9.1 may happen in 8.5 and 8.2.5 Condition: Same as above Workaround: Down connection and up connection should re-establish the continuity.
CSCdj85198	Symptom: An auxiliary port configured as an alarm collector port does not collect and log alarm messages. Conditions: Applies to IPX, IGX, and BPX platforms. Workaround: There is no workaround available. Further Problem Description: Before the auxiliary port accepts a character, system software must first validate the port's operating mode (e.g. VT100, autodial modem port, etc.). An auxiliary port configured as an alarm collector port was not properly validated, which caused the port to reject character input.
CSCdk01714	Symptom: In the function nw_hp_ptl_bmap where we integrate the high priority CC traffic bit from the other nodes the code doesn't really do any integration... In fact, this may cause potential aborts in the system - the way we are checking the topo_ptr. Conditions: Under all conditions Workaround: No workaround.
CSCdk04291	Symptom: BCC switch over after using the cnfpref * + command. Software error log shows a 1M3 (1000003) abort. Conditions: Using the cnfpref * on a BPX running release 8.4.14 software. Specific information about the BPX node that experienced this problem is unknown (such as the number of connections on the node and BRAM size). Workaround: Avoid using the cnfpref * command to configure preferred routes. There should not be a problem using the cnfpref command without the wildcard ("") argument. Further: There is a pointer which may not be initialized when the wildcard argument ("") is used with the cnfpref command on a BPX. The uninitialized pointer is for a structure which has a pointer to a second structure. The BCC aborted because the second pointer was to an address which was outside the memory address range for the BCC. If the second pointer had been to a valid memory address the BCC would not have aborted and the preferred routes would have been correctly configured. The wildcard option will usually work because the second pointer is usually "0" (a valid address for read access), but should be avoided due to the risk of an abort. The memory access is for a memory read (not write), thus there is no risk of memory corruption.
CSCdk04940	Symptom: When the sequence of commands as presented below is executed node aborts. while running swsw 8.4.18 Next Command: dspprfhist s Command - f, b, l, r, a, i, q: (option a) Enter first sample: any number (0-11) Enter last sample: any number greater then range allows (>= 12) Conditions: If a dspprfhist s is issued before a dspprfhist then the system crashes. Workaround: A dspprfhist needs to be issued before the dspprfhist s and that will avoid the problem
CSCdk11366	Symptom: There are Unknown Addr errors on BXM ports as well as some loss of data on those ports. Furthermore, the timing of the Unknown Addr errors seem to parallel rather closely that of the Background Test for the BXM. Conditions: 1. There must be a virtual path connection on the BXM in question. 2. There must be traffic on that connection. 3. BXM Background test must be enabled. This conditions do not insure that the error will occur (they are necessary but not sufficient). The problem occurs only when the Background test chooses a VPI/VCI for testing purposes such that the VPI is used for a virtual patch connection. Workaround: Disable the BXM Background Test.
CSCdk18425	Symptom: Data Continuity loss of all connections routed over BNI trunk. Conditions: When an active BNI card is replaced with an ASI or BXM card, the card mismatch is declared properly. However, after reinserting the original BNI card into the same slot, the BNI user channels on this trunk card are not being programmed. Work Around: Reset BNI card after mismatch state is cleared.
CSCdk19026	Symptom: There was an observance of gaps in traffic using DS0A connections. The gap duration corresponds to the in/out framing threshold of the CVM determined by the cnfcdpparm command. Conditions: Utilizing a unique DS0A application which is sensitive to the delay caused by the traditional range of configurable in/out framing thresholds (500 to 1000 msec). A lower threshold value is required. Workaround: None
CSCdk20258	Symptom: Trunk load reverts back to default values on IGX. Conditions: When a BPX, connected to an IGX via a trunk with non default configuration for both receive and transmit side, is reset (BPX is reset), trunk load values on the IGX and on the BPX revert to default values when the BPX comes up. Workaround: There is no workaround for this condition.
CSCdk26240	Symptom: AIS alarm counts are not displayed for E3 lines and trunks when using the commands dsplnerrs line_num and dsptrkerrs trk_num. Conditions: The problem occurs on BPX nodes using E3 lines or trunks. Workaround: No workaround is available; however, the AIS alarm status is correctly displayed.
CSCdk27774	Symptom: The loop backs added on the trunk are cleared following a Node rebuild. Conditions: Rebuild the Node with the software loopbacks on Workaround: Need to add the loopbacks back in after a rebuild. Further Problem Description: Software loopbacks are cleared after the node is rebuilt, but it is preserved on a switchcc or a graceful upgrade, even though it is stored in the BRAM
CSCdk28946	Symptom: Major and minor statistical alarms are not triggered at the rates configured using the cnflnalm command. Alarms are triggered after thirty seconds. Conditions: This is the case for all statistical line alarms. NOTE: This software fix corrects the problem for errors in the range of 10E-8 to 10E-4. Errors detected at these rates will cause alarms based on the thresholds configured using the cnflnalm command. Errors at the rates of 10E-9 and 10E-3 do not properly trigger alarms. There is a workaround for errors detected at 10E-3 which is to change the major alarm threshold from 10E-3 to 10E-4. There is no workaround for declaring minor errors at 10E-9. Both of these issues are still considered open and will be addressed. Although there are no trunk alarms triggered at 10E-3 and 10E-9, the errors are correctly reported and can be displayed using the dsptrkerrs command.
CSCdk32500	Symptom: Node aborts with 1000003 error in the NETW process. Conditions: Some trunks have or had high priority traffic restriction enabled. Following a switchcc, upgrade, clearing of unreachability, database updates are shared between nodes. If a difference in the HP restriction status is detected, the integration of the information can result in this situation. WorkAround: 1. When the node is aborting AND the dspswlog shows that it is the netw AND the program counter is 300161DA - down the trunk cards to that node. The abort should stop. 2. loadrev the standby with 8.4.21 which would be in locked state. 3. switchcc to go to standby.
CSCdk32790	Symptom: ASI-155/BNI to BXM connections may lose traffic. Conditions: BCC-4 arbiter does not recognize that the ASI-155 has only single receiver, therefore, all the cells go through the second receiver will be dropped. This happen on BNI cards also. Workaround: No Workaround.
CSCdk43947	Symptom: The command: tstport port leaves the remote ends of the connections stuck in test mode. The connections do not pass customer data while in this mode. The test mode is identified by performing dspcons at the remote nodes. The connections will be displayed as follows: 6.1.102 igx 24.1.200 TOk fst 0 6.1.103 igx 24.1.400 TOk fst 0 Subsequent attempts to run tstport are not successful because the test aborts. Conditions: The problem occurs when running the tstport command on a FRP/FRM V.35 DCE port. The port must have connections, and these connections must terminate on a remote node. The problem has not been seen on ports containing only DAX connections. This problem could also occur on FTC/FTM ports under similar conditions. Workaround: Switchcc on the node where tstport was performed.

Corrected Anomalies from the 8.4.20 Software Release

The following conditions have been corrected with the 8.4.21 version of the software release.


Bug ID	Descriptions
CSCdj43626	Dangling LCN happened after dncd then deltrk After a dncd and a deltrk command were issued on a card that had connections, no other connections would route because the node kept trying to route those connections that were deleted. The User interface became locked up.
CSCdj47827	S/W Error 2064 seen on BPX. When adding a dax connection from a feeder trunk to an ASI port while the ASI connection interval statistics are enabled, the BPX will try to enable statistics on the feeder trunk. Adding these dax connections from a feeder trunk depletes static memory.
CSCdj47933	BPX shows an uninitialized LCN value when calling rs_set_clot_cnfg_by_lcn. An uninitialized variable had the potential to overwrite memory.
CSCdj75540	BPX. swerr 137 --- BAD_SDIR Software error 137 is logged on the standby CC of a BPX when the BPX is the second segment of a two segment connection in which one endpoint terminates on a trunk card and the other endpoint terminates on a line card. The error is logged when the trunk endpoint is added first.
CSCdj85636	A VCC connection has a 1-way loss of data continuity on a BPX. This was visible using either the command tstdelay or dspchstats.
CSCdj87214	Swabort 1K and 2M on 7 BPX nodes Addlnlocrmtlp causing continuous aborts and rebuilds on other BPX nodes. It was observed that the Addlnrmtlp command may cause continuous aborts and rebuilds on BPX nodes.
CSCdj87484	BXM removed itself and would not recover after burn fw rev on IPX, IGX, and BPX. If the getfwrev 0.0 <node> command is issued during a a firmware download, the corrupted firmware may be burned into the cards, and the cards will not come up.
CSCdj88699	dspcons on a BPX doesn't show the existing connections that terminate on slot 16 of IPX/IGX.
CSCdj90444	On BPX, a BXM-T3 being used as a trunk sends out more traffic than the transmission rate was configured for.
CSCdj94277	On BPX, a resetcd command was issued on a BXM card. Before the card was in a standby state, a switchcc was done and the node rebuilt.
CSCdk01897	On BPX, swerr 123 caused a BXM reset. The y-red pair of BXMs were simultaneously reset from a swerr 123 on a node with a large number of CC restricted BXM trunks.
CSCdk02104	swerr 378 will fill up log on addcons if we use BXM trunks on a BPX switch. Software error 378 will be logged when connections are routed over BXM trunks. There are no side effects as result of this error.
CSCdk03040	High priority login through the Control Port is needed on IPX, IGX, and BPX. New functionality is being added to allow high priority login through the Control Port.
CSCdk03369	Uninitialized variable in init_single_vc_stats()in CSCdj75540 fix The statistics information block is not initialized on the standby processor when connections are added on a BPX Switch.
CSCdk03433	Add a command to run route_op whenever needed on IPX, IGX, and BPX. A new StrataCom level debug command, runrtop, has been added. This command is used to run the route-op algorithm and recalculate networking paths whenever needed. The command is expected to be run only by Cisco personnel.
CSCdk04781	nhdeg_parms fields need to be initialized for IGX base in IGX/IPX An initialization of a new field was added for the Flood control feature. This is new in 8.4.21 and was never a field problem.
CSCdk04998	On IPX IGX BPX, the move check for coerced msg floods from msg to put level. Control traffic consisting of coerced (high priority) messages did not have a throttle on the receiving end. Excessive coerced messages locked up the network handler due to the time spent processing the received messages.
CSCdk06365	Can't transfer data on new PVC created after rebuild of BPX.
CSCdk06428	On IPX, IGX, and BPX, high priority login messages appear in dsplog when the user logs in through telnet.
CSCdk08937	After an upgrade from 8.4.09 to 8.4.18, an internal database entry was not deleted as it should have been. This resulted in a loss of continuity on Virtual Path connections.
CSCdk11702	IPX IGX 1M3 (1000003) abort on Upgrading standby CC during 8.1.19 to 8.4.14 upgrade. Under specific topology and status conditions, (FRP in slots 2,3,4, and ports in comfail), a 1M3 abort occurred when upgrading swsw 8.1.19 to 8.4.14. (This did not apply to 8.1.20-8.1.74 revisions upgrading to 8.4).
CSCdk13558	On BPX, an indication was added to dspcd to display card (channel) programming activity.The output of the cli command dspcd <slot> now indicates whether the specified slot is undergoing channel programming. This indication is updated in intervals of 2 to 5 seconds for about 1 min. The indication is changed if the card channel programming activity changes, i.e. channel programming starts or stops.
CSCdk16017	On BPX, the upgrade from 8.4.20 to 8.4.2H lost a lot of connections. This was never a field problem as it was introduced in 8421 and corrected in the same release before shipment
CSCdk16366	On BPX, BCC-4 does not recognize 19.2 Gbps backplane after running switchcc A switchcc on BCC-4 does not force it to recognize the 19.2 Gbps backplane.
CSCdk18709	On IPX IGX BPX, the console port DTR detection not high priority (This is a fix to a new 8.4.21 feature) If a user is logged into the Control Port at normal user priority while the processor card is very busy with high priority work, the Control Port user will get locked up. It will not be possible to force a logout, so the user can then log in at high priority. A change is being made to have the DTR check of the Control Port at a very high priority. This way, the user can pull the RS232 cable at the Control Port to force the low priority user session to end. Then the user can log in at high priority.
CSCdk20470	On BPX, dspcon reports incorrect status for connection. After upgrade to 8.4.21, all connections on feeder trunks on port 2 and port 3 will not be visible via dspcon OR dcct command. They will however appear on dspcons. This is on BPX only and only for BNI feeder trunks.
CSCdk20874	On IPX, IGX, BPX. A couple of additional commands were requested to run under hipriority login. The commands dspnode and cnfnhparm are added to the list of commands that run under the new hi-priority login feature.

Corrected Anomalies from the 8.4.19 Software Release

The following conditions have been corrected with the 8.4.20 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj87214	Swabort 1K and 2M on 7 BPX nodes
CSCdj90444	BXM-T3 which is configured as trunk sends out traffic over Transmit Rate

Corrected Anomalies from the 8.4.18 Software Release

The following conditions have been corrected with the 8.4.19 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj41899	It was observed during the provisioning of an FRP-ASI connection segment through StrataView Plus that the SNMP agent returned an error indicating that there is a shift-mode mismatch on the ASI card.
CSCdj46687	The peak interval displayed by the dsplnstatcnf and dsptrkstatcnf commands are incorrect. This may cause confusion, as the actual peak intervals ARE correct, but these two commands are displaying them incorrectly.
CSCdj50681	Enhancement to the dspmemblk command. The StrataCom level command dspmemblk has been enhanced to help to indicate possible memory fragmentation by calculating the largest allocatable block of memory.
CSCdj52014	dspcon does not show the card type for CVM-HDM dax connections When the dspcon command was executed on the HDM end of an CVM-HDM dax connection the card type of the CVM was not shown in the display.
CSCdj54598	dspnds display corrupted The dspnds command would intermittently display the wrong data. Some fields in the dspnds screen were overwritten by an irrelevant data string.
CSCdj59263	swerr 532 - when deleting connections The software error 532 was logged if a connection was displayed at the same time it was being deleted.
CSCdj61454	dspmemblk only does calculations for STATIC and DYNAMIC region See Release note for CSCdj50681
CSCdj61992	Modem Upgrade from v type conn incorrectly displayed on UVM The display of voice connections does not show when a modem is detected.
CSCdj66322	Abort during switchcc at node sw275 Watch Dog Timeout abort after a switchcc or an upgrade. This only happens on a node that has the endpoints (a dax con has 2 end points and other conns have 1) of the order of 20K. But if the connections are in a FAILED state the problem can happen with lesser number of endpoints.
CSCdj67954	cons don't rte on 64K BXM card, get_free_trk_chans gives inv rslt Connections do not route on 64k channel BXM cards.
CSCdj68220 CSCdj68885	swerr 4208 logged after cnfpref * + was done on ipx/igx nodes Multiple occurrences of software error 4208 were logged after executing the cnfpref command.
CSCdj68220 CSCdj68885
CSCdj70195	An intermittent software error was logged during a field-trial. The software error number 55 which indicated an invalid or unknown card type was logged when displaying a connection status via the user interface (rather than StrataView+)
CSCdj72753	SNMP: able to exceed Range of parm MinAdjustPeriod for FrATM The value range for atmEndPointMinAdjustPeriod was incorrect. The StrataView+ Service MIB parameter atmEndPointMinAdjustPeriod Value range should be 3-255. The current MIB SYNTAX showed it as 1-100.
CSCdj73314	Trunk stats and dsptrkerrs command do not count up telco errors (E3) HCS and BIP8 errors were not being tallied for E3 trunks. These statistics can be viewed using the dsptrkerrs command.
CSCdj74527	dspcons shows connections that do not exist Connections that had been deleted when a node was in an upgraded state did not have all data properly deleted. These cons would be displayed by the dspcons command.
CSCdj77027	addcon no longer shows the connection being added While executing addcon, the connection being added was not displayed while waiting for confirmation. This occurred while adding any connection.
CSCdj78846	SV+ cannot enable all of the BXM trunk statistics FEBE counts did not appear for E3 trunks on StrataView+.
CSCdj90601	Introducing the CAC Feature for BXM/ASI Ports CAC stands for Connection Admission Control. Currently, connections are added (or configured) even if the bandwidth requirements exceed the Port capacity. In the switch, Port Over Subscription is allowed, so the default value for CAC Override is set to Enabled. A new feature is being implemented, using which CAC Override can be enabled or disabled on a per port basis. This would give the customer freedom to allow or disallow port over subscription. This feature can be enabled/disabled on a per port basis. It is possible to have a card with CAC Override feature enabled on one port and disabled on another. ASI and BXM cards will support this feature. Enforcing of CAC Override involves, rejecting requests to add connections or change the parameters of a connection if port over subscription is detected. It applies for both DAX and NON-DAX connections. CAC Override Feature is applicable only on the port on which it is enabled. If a connection is added between two ports one with CAC Override enabled and another with CAC Override disabled, enforcing of the CAC Override (port oversubscription) is done only on the side where it is disabled. In this sense it is a strictly a local feature, applicable and enforced on a single port. Some examples: Network containing nodes running 8.4.19 and earlier releases of 8.4 (ex. 8.4.18) a.) If CAC Override Feature is disabled on the ports on nodes running 8.4.19 and above. Addcon If addcon (from 8.4.18 to 8.4.19) results in Port Oversubscription on the 8.4.19 node, the following error message will be displayed on the node running 8.4.18: "Unknown response at remote node : 96" The connection is not added. Cnfcon cnfcon also generates an error message: "Unknown response : 96" The connection is not changed. b.) Percent Util greater than 100% on nodes running 8.4.19 with or without disabling the CAC Override Option Addcon: ------- If addcon uses a value greater than 100 for percent utilization, the remote node running (8.4.18 or lower) will reject the connection add request with the following error message: "Remote % Util value out of range." The connection is not added. Cnfcon: Using cnfcon to change the percent utilization to higher values than 100, also produces the same error message. c.) Cnfcls command can be used in 8.4.19 and higher releases to configure classes to have values higher than 100 for percent utilization. Since ATM classes are network wide, all the nodes in the network are updated. If there happens to be a node in the network running 8.4.18 or lower. If now an attempt is made to add a connection using the class which has been changed, the connection will not add. An error message: " % Util value out of range (remote end). Valid range 1 - 100." is seen. The solution is to reconfigure the class and add the connection, or add the connection by specifying all the parameters.

Corrected Anomalies from the 8.4.17 Software Release

The following conditions have been corrected with the 8.4.18 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj47236 CSCdj47578	Calling an exception() or abort() funcs with > 2 parms is incorrect When the internal exception or abort routines are called with more than two parameters an abort can occur.
CSCdj54129	Spare bits have to be cleared when sending RMT_MDM_MSG The spare bits in an internal message should always be cleared before sending out an RMT_MDM_MSG. This fix allows for interoperability between other switch software releases.
CSCdj56499	VPI > 4096 for NNI connection should be denied on BXM Users should not be allowed to add NNI connections in which the VPI is greater than or equal to 4096 on BXM-155-4 cards. For an NNI connection, the VPI should be less than or equal to 4095.
CSCdj76850 CSCdj83655	Additional channels stats and state information are added to BXM summary stats. These additional statistics are for BXM's used as trunks, lines, or feeder trunks. The new statistics are: `Statistic Field shown on dspchstats screen--------- --------------------------------Non-compliant CLP0 discard (Rx NC CLP0 Dcd)Non-compliant CLP1 discard (Rx NC CLP1 Dcd)Non-compliant CLP0+1 discard (Rx NC CLP01Dcd)Congested CLP0 discard (Rx CG CLP0 Dcd)Congested CLP1 discard (Rx CG CLP1 Dcd)Congested CLP0+1 discard (Rx CG CLP01Dcd)AIS/RDI states (OAM RX State)CLP0+1 cells from port (Rx CLP0+1)CLP0 to port (Tx CLP0)CLP0 dropped (Tx CLP0 Dscd)CLP1 dropped (Tx CLP1 Dscd)CLP0+1 dropped (Tx CLP0+1 Dscd)` The following is an example a dspchstats screen output with the new statistics. These new statistics are all summary statistics and are not forwarded to StrataView+. `Channel Statistics for 2.2.200.201 Cleared: Mar. 20 1998 17:32 (\|)PCR: 50/50 cps Collection Time: 0 day(s) 00:00:00 Corrupted: NOTraffic Cells CLP Avg CPS %util Chan Stat Addr: 30EE05ECFrom Port : 0 0 0 0 OAM RX State: ClearTo Network : 0 --- 0 0From Network: 0 0 0 0To Port : 0 0 0 0Rx Frames Rcv : 0 Rx CLP0 : 0 Tx CLP0 : 0NonCmplnt Dscd: 0 Rx Nw CLP0 : 0 Tx CLP0 Dscd : 0Igr VSVD ACR : 0 Rx NC CLP0 Dcd: 0 Tx CLP1 Dscd : 0Egr VSVD ACR : 0 Rx NC CLP1 Dcd: 0 Tx CLP0+1 Dscd: 0Rx Q Depth : 0 Rx NC CLP01Dcd: 0Tx Q Depth : 0 Rx CG CLP0 Dcd: 0Rx CLP0+1 : 0 Rx CG CLP1 Dcd: 0 Rx CG CLP01Dcd: 0`
CSCdj81471	On FRM/FRP with y-redundancy, if incoming LMI stops and there is a y-red switchover, the port failure database is not handled properly. When LMI resumes, all connections on that port will stay failed with the reason being "Port Comm Fail".
CSCdj82434	Add on-line support for BCC-128 On-line support for the BCC-128 card is now available. This change allows the BCC-128 to behave operationally the same as the BCC-64 card.
CSCdj85064	New UP firmware to provide BPX EXT-1/EXT-2 Clock glitch robustness A new version of the software component of UP firmware is being delivered.This change adds checksum protection to the code and also has a fix for bad clock sources.

Corrected Anomalies from the 8.4.16 Software Release

The following conditions have been corrected with the 8.4.17 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj46943	SV+ event logging interface not working properly. The SV+ event logging interface does not send any event logs to StrataView Plus, even though the StrataView Plus gateway node has link0 up and maintenance log subscribed.
CSCdj70553	One way PVC on ASI-ASI connection after upgrade from 8.1.19 to 8.4.09 There were excessive cell drops (approximately 80%) in ATM PVC, in a BPX ASI--ASI for path connections.
CSCdj82656	REV_UPDT_TP - revision update msg not propagated to remote nodes properly When a secondary revision changes on a node (by command loadrev), the revision change is not propagated to all the nodes in the network.
CSCdj83158	Problems with connections being in loopback after upgrade Some connections were stuck in tstcon state after an upgrade from 8.1.2x to 8.4.x.

Corrected Anomalies from the 8.4.15 Software Release

The following conditions have been corrected with the 8.4.16 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj55993	The addyred command erroneously allows the user to use an active BXM card as the YRED Secondary card. This should not be allowed since the Y-RED Secondary card is required to be in Standby state when the addyred command is executed. This may happen when one of the BXM's is a trunk card and the other BXM card is a line card. This is not a problem for BNI and ASI cards. Symptoms of this problem include loss of continuity on one or both active BXM's, and software error 21 may appear in the dspswlog command. Workaround: Recommend issuing the commands delyred and switchcc to restore database values.
CSCst95767	Able to configure USER statistics beyond the accepted limit and cause 2060 software errors It was possible to have all TFTP interval statistics configured and then have USER statistics enabled that would use the space that the TFTP interval statistics file would occupy. This would result in a software error 2060 every time the switch attempted to create the TFTP interval statistics file.
CSCdj27210	tstber command out of date - needs updating The tstber service level command did not work properly in switch software release 8.4.
CSCdj38767	Loss of Frame alarm appears at UI as Out Of Frame If a line was in a "Loss of Frame" alarm, the dsplns command would show the wording "Out of Frame". The "Loss of Frame" alarm is now correctly displayed.
CSCdj39552	BPX aborts multiple times with WDT 52 If an external device was streaming ASCII NULL characters (0x00) into the control port it could cause Watchdog time-outs. The control (and aux) ports no longer handle ASCII NULLs differently than ordinary characters.
CSCdj40315	Unable to set CLP-HI/CLP-LO parameters value to zero SNMP was unable to set the Cell Loss Priority Hi and Lo parameters on ATM connections to zero. This was because the range 0-100 was incorrect. The correct range is 1-100 and the switch MIB has been modified to allow this range.
CSCdj40551	No alarm generated when FRP/AIT cards were removed. There was no error generated on SV+ when AIT and FRP cards were manually removed from the slots.
CSCdj43705	cnfchstats on dax connection shows wrong statistics When the cnfchstats command was executed on the "other end" of a dax connection that terminated on two different cards (BXM and ASI), the statistics where shown for "this end" of the connection. For example, on a connection originating on an ASI and terminating on a BXM within the same node, cnfchstats on the BXM ("other end") endpoint of the connection would show the data from the ASI ("this end") endpoint of the connection.
CSCdj44011	2 level 1 BXM channel statistics not available There are two statistics for BXM card channels added to the dspchstats display. These statistics apply when the BXM card is used as a line card. The statistics are "To Port" CLP and "Rx Frames Rcv". An example of the dspchstats screen appears below. `Channel Statistics for 10.1.1.100 Cleared: Feb. 10 1998 10:02 (\)PCR: 50/50 cps Collection Time: 0 day(s) 00:02:46 Corrupted: NOTraffic Cells CLP Avg CPS %util Chan Stat Addr: 30EE1B58From Port : 0 0 0 0To Network : 0 --- 0 0From Network: 0 0 0 0To Port : 0 0 0 0Rx Frames Rcv : 0 NonCmplnt Dscd: 0 Rx Q Depth : 0Tx Q Depth : 0 Rx Clp 0 : 0 Rx Nw Clp 0 : 0Igr Vsvd ACR : 0 Egr Vsvd ACR : 0`
CSCdj44826	SWERR 419 logged on IPX node when it was deleted from the network (trunks deleted) A software error 419 was logged on an IPX node when it was removed from the network by deleting the trunk that connected it to the network.
CSCdj54718	tstber is not working on BNI trunks if it is executed from one end The tstber service level command was not working properly.
CSCdj56274	Line in logical loopback intermittently causes port failure after switchcc A different port failure status on the active and the standby BCCs caused an intermittent failure on the port.
CSCdj56486	Incorrect NTS queue delay calculation for Tx. Rate >= 80000 cps The queue delay when calculated on the IGX from the Tx Queue Depth was being calculated incorrectly. The number of DS0s used for this calculation did not reflect the actual number at which the queue is being serviced.
CSCdj56646	cnftrkparm for parm 9 sets parm 19 on BXM trunk The cnftrkparm command updates parameter 19 with an invalid value whenever parameter 9 is changed. Parameter 9 is the Yellow alarm I/O and parameter 19 is the High CLP for CBR traffic. This problem occurs on both BNI and BXM trunks.
CSCdj60325	BXM port discards all data when remote segment fails. The BXM port discards all data (user data, AIS, tstcon, tstdelay) at its PVC ingress when dspcon shows PVC has remote segment failure (such as FR LMI failure).
CSCdj61384	Re-enable the on/off switch for standby statistics updates to avoid 501s and 3Ms When large numbers of TFTP interval statistics are enabled, standby updates queue up faster than they can be serviced. This is indicated by a growing number in the 'Standby CC Update' field in the dspqs screen.
CSCdj65863	The dellp command does not work on a BXM Virtual Path connection, the connection stays looped If a BXM VPC connection that was not the first one on a port was looped back using the addloclp or addrmtlp command, the loopback could not be removed with the dellp command.
CSCdj66601	strata.mib doc=error & unable to get/set cbr port q parms The atmPortQueueEntry object had an index for ABR and VBR, but not for CBR. CBR port queueing parameters were configurable from CLI but not SNMP.
CSCdj67238	Unable to access ATM PortQ info on BXM in SNMP Could not create ATM Port Queues on BXM cards using SNMP.
CSCdj67823	C-bit errors not showing up [BNI trunk errors (dsptrkerrs) are not collected]. Trunk errors are not collected from BNI cards. When trunk errors exist the dsptrkerrs screen shows no errors, and minor or major alarms are not generated.
CSCdj70968	Add a flag for controlling UID DB updates The User ID database is checked to assure integrity prior to transmission to other nodes during the update process. Also, incoming messages are checked prior to integration into active use.
CSCdj71802	BXM trunks stay in LOS and report swerr 21. If a BXM trunk's cable was disconnected and it went into LOS (loss of signal) it would not clear the LOS after the cable was reconnected.
CSCdj75881	Slow memory leak has been detected. A slow memory leak was found. An occasional block of memory is found to have not been deallocated after execution of the savecnf command.

Corrected Anomalies from the 8.4.14 Software Release

The following conditions have been corrected with the 8.4.15 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj24325	Slot errors are not collected on BNI-OC3 and ASI-OC3 The dspslotalms command did not show if there were any slot errors on BNI-OC3 or ASI-OC3 cards because these errors were not being accumulated.
CSCdj34069	SWERR 532 upon switchcc on IGX routing node A software error 532 (Bad logical card index) was logged on an IGX routing node after a switchcc.
CSCdj34168	Idle time for fail handler is too high The internal FAIL handler has been optimized and the percentage of processor time that it requires has been reduced.
CSCdj34220	sw err 4208 logged when deleting PVCs/SVCs on VNS start-up. A VNS was restarted after a non-graceful exit. During the restart and the normal deletion of PVCs and SVCs, a software error 4208 was logged.
CSCdj34754	Nodes take up to 10 minutes to revert to circuit line clock sources after clearing LOS When the Circuit Line clock source on which an LOS is created is on the highest numbered node, it could take up to 10 minutes to switch back to the source on clearing the LOS.
CSCdj37700	Takes too long to add or delete an object when statistics are enabled Adding a single connections locked the user interface up for a minute or more when there were 1000 or more connections, with several connection statistics enabled.
CSCdj38564	After switchcc, event log shows an extra unnecessary BXM Inserted event. After a switchcc command was executed on a BPX with BXM cards, the log would have an unnecessary informational message stating that a BXM backcard had been inserted and activated.
CSCdj38922	No continuity after adding a connection There was no data continuity after adding a new ASI connection. It was noted that during the card verification process, the ASI back card is being reset, but never cleared. This will result in channel configuration message not being sent to the card.
CSCdj41999	T3/E3 back cards mismatch with ASI card T3-3 and E3-3 backcards were not interchangeable between ASI and BNI frontcards (this has been the case since the introduction of these cards). The ASI T3/E3 frontcards will now support these backcards
CSCdj42027	VNS Bulk Calls causes SWSW abort During stress testing of the VNS a race condition occurred that resulted in a 1000003 abort.
CSCdj42841	ASM events are reported only to local StrataViews. Event log messages related to the ASM, such as power supply failures and temperature alarms, are logged to locally attached (link0) StrataViews, but are not broadcast to remote nodes that have StrataViews.
CSCdj46114	Expensive inserts in add_lcn_sorted() affecting switchcc performance. One of the functions performed during a switchcc has been optimized to improve the time required to complete the switchover.
CSCdj46124	For VPC conn, if no VPC conid available, other conns will not get routed. If routing chose a path which had the shortest hops, but no available VPC conids, the routing attempt failed. The failure did not increment the failure wait count to allow other connections to route. Every time candidate selection ran, the VPC connection was chosen, and the same invalid route was chosen. Other connections waiting to route would never be routed.
CSCdj46387	IPX IGX BPX swerr 129 occasionally is logged. A task was in the process of logging a software error when it was interrupted by a higher priority task that logged a software error. This race condition can lead to corruption of the software error table.
CSCdj46406	BPX ASI-T3 Remains on OOF after line failure If two ASI lines are connected each other and the line between them is broken and then remade, the line remains in OOF.
CSCdj46536	IPX IGX SWSW not adding connections when requested by VNS SNMP will now record error descriptions (in the strmErrors table) when an SNMP request for a voice SVC is rejected by the embedded agent.
CSCdj49377	BPX dspportstats become unexecutable after switchcc The dspportstats did not operate as expected after a switchcc and instead of displaying the correct information, the message "specified port already being monitored" was shown on the screen. This happened only if the port was being monitored by the dspportstats command at the time that the switchcc occurred.
CSCdj49422	IPX IGX A voice connection goes to lu (load unit) inconsistent It was noted that on an IPX node, the slave dsi for a voice connection is different from the master dsi.
CSCdj50010	IPX IGX BPX Potential for using an uninitialized local in routine free_vc_sib() An uninitialized variable could possibly be used in an internal routine, and potentially create problems. Some of the possible symptoms are software error 2051 being logged, the Tftp_File_Size is incorrect and the SV+ complains that the file is not parseable.
CSCdj50106	IPX IGX BPX Optimization for clock routing A Clock Routing Simulator has been created that can run on UNIX workstations to analyze clock routing performance.
CSCdj54902	IGX SVC connections do not return the timeslots to idle 54h on deletion The CVM card is not returning channels to idle 54h when the connections have been deleted. This leaves the timeslot in an uncertain state with varying levels of noise.
CSCdj55384	Error 514 while deleting/adding conns through SNMP Software error 514 (from Free_mem call, overwrote block) occurred while deleting and adding connections through SNMP.
CSCdj56223	BPX BNI-OC3s generate lots of invalid port errors. The BNI-OC3 generates lots of rx invalid port errors, causing major alarms when the errors are counted.
CSCdj57674	IPX IGX 1M3 abort after clrallcnf in VNS SVC calls. After the command clrallcnf is issued, the establishment of a VNS SVC call could cause the switch to reset.
CSCdj57783	IPX IGX BPX Conns not routed after ungraceful upgrade. After an ungraceful upgrade the constats command reported that some FRP connections were deleted. In addition, dspcons showed that conns are gone. The dcct showed that the conns are still there. SWERRs 384 were being logged continuously.
CSCdj64355	BPX 8.1.72 -> 8.4.12 dspcon shows atm values = 0, dspcons shows type field blank After an upgrade from 8.1.7x to 8.4 some connections would show zero(0) values in all fields of the VC BW Params.

Corrected Anomalies from the 8.4.13 Software Release

The following conditions have been corrected with the 8.4.14 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj47955	Software abort 1000003 occurs on a BPX node running switch software release 8.4.11 after inserting and replacing BXM cards on the node.
CSCdj49422	It was noted that on an IPX node, the slave dsi for a voice connection is different from the master dsi.
CSCdj50812	Voice connections using ADPCM do not upgrade to fast modem. The connection can pass voice calls normally until a Fast Modem type connection is attempted. At that point, the connection upgrades to Fast Modem mode but does not allow the modems to sync up. After the modems go back on-hook, the connection remains in the Fast Modem state (use "dspconst" command to see this) and can no longer pass voice for some time.
CSCdj49647	Software error 3000000 and 3000000 abort occurred on an IGX node during VNS bulk call testing.
CSCdj30407	BXM receives `card errors' status when card change status from standby to active.
CSCdj32601	On a BPX node running switch software release 8.4.07, it appears that no slot errors have been collected when the cards was in the standby state. The slot errors appears later after the card is brought to active from the standby state.
CSCdj43344	On a BPX node running switch software release 8.4.09 (and/or 8.4.10) with BXM firmware revision MBM/MBR, it was observed that the port LED stop reporting line errors/alarms when the port number exceeds 100. The LEDs would stay green even if there were no signal inputs (no loop back cable). This problem occurred on BXM-E3/T3.
CSCdj45984	In a network running regression test for switch software release 8.4, it was noted that communication failure occurred on one of the two virtual trunks connected to a BPX node in the network. The failure occurred for a few hours, but later recovered/cleared itself, and the failure condition disappeared.
CSCdj48107	The ESP object message needs to be sent to SV+ whenever the ESP status changes.
CSCdj35108	During a Node-by-Node upgrade, one node went into a non-graceful upgrade.
CSCdj36307	A BPX node received a network message with a bad function code (software error 104). This condition is recoverable since the incorrect message will not be acknowledged and thus re-transmitted.
CSCdj35556	On a BPX node with a large number of connections, when a switchcc is issued, the control console communication with that node will be interrupted for a certain length of time, up to 10 minutes. During this time, there is no loss of continuity. Also, if a non-redundant BXM port card is reset, control console communication will also be interrupted. In this case, continuity for connections terminating on that BXM is interrupted.
CSCdj33896	No warning is given when the maximum number PVC is reached on a given trunk. When a cnftrk command is issued for a given trunk, the local end can support the new max PVC number, but the remote end cannot. Workaround: Use the cnftrk command on the remote node (for the same trunk) to determine the maximum permissible value (it will be the lower value of the two nodes).
CSCdj03022	When performing a upgrade from 8.1.70 to 8.4.00, it was observed after the loadrev command was issued, one of the BPX nodes remained in the Loaded state. When a dspstby is done, all states are in the clear state. This is not readily reproducible.
CSCdj33985	Software error 445 occurred on a BPX node.
CSCdj34226	Software error 532 will occur when a dspcons command is executed while SVCs or PVCs are being added or deleted from a VNS station.
CSCdj08657	During a Node-by-Node upgrade, after the switch -g command was executed, a software error 938 (an error from the pSOS pNA facility) was logged. This does not adversely affect the upgrade. Workaround: Use the rrtcon command for the failed connections so that they will be routed again, which will correct the problem.
CSCdj39811	On BXM port cards, unfairness and tail discards can exist due to the non-optimal settings of the QBIN, VI, and VC threshold values.
CSCdj41103	After a runrev to the current release is executed, some of the nodes, via the dsprev command may report an older, incorrect version of software running. In actuality, the correct software is running on the node.
CSCdj41517	Software error 21 was observed at an IGX routing node both before and after a non-graceful upgrade from 8.2.04 to the 8.4 release. This did not result in any service outages.
CSCdj41077	After invoking a switchcc from a BCC-3 card in slot 7 to a BCC-4 card in slot 8, it was observed that connection continuity was interrupted for 40 minutes, as most of the existing trunks were in Communication Failure.
CSCdj36589	In some circumstances, after a Node-by-Node upgrade was completed, load model inconsistencies were detected via the dsplm command.
CSCdj41231	The background test for the BXM (port) card fails frequently. This is not necessarily an indication that the BXM card is defective.
CSCdj41235	The self-test for the BCC-4 processor card may fail in certain (unknown) circumstances. In the observed case, there were 2 failures in 596 passes. This may not necessarily indicate that the card is defective.
CSCdj41899	It was observed during the provisioning of an FRP-ASI connection segment through StrataView Plus that the SNMP agent returned an error indicating that there is a shift-mode mismatch on the ASI card.
CSCdj42027	During stress testing of the VNS application, an Abort 1000003 occurred. This is due to a race condition, which will be fixed in a future release.
CSCdj41731	It was observed on a BPX node with about 5000 terminating connections and about 12000 via connections which was in the process of re-routing connections and performing a switchcc, that all memory was exhausted such that software errors 501, 977, and 3000000 were logged. This was a recoverable situation.
CSCdj32544	It has been observed in one particular node that the name of the BCC card was listed as "ASM" rather than "BCC". This did not affect the operation of the switch.
CSCdj35108	During a Node-by-Node upgrade, one node went into a non-graceful upgrade.
CSCdj36307	A BPX node received a network message with a bad function code (software error 104). This condition is recoverable since the incorrect message will not be acknowledged and thus re-transmitted.
CSCdj35064
CSCdj36589	After a Node-by-Node upgrade, it has been observed that Load Model inconsistencies may exist on BPX nodes.
CSCdj35556	On a BPX node with a large number of connections, when a switchcc is issued, the control console communication with that node will be interrupted for a certain length of time, up to 10 minutes. During this time, there is no loss of continuity. Also, if a non-redundant BXM port card is reset, control console communication will also be interrupted. In this case, continuity for connections terminating on that BXM is interrupted.
CSCdj33896	No warning is given when the maximum number PVC is reached on a given trunk. When a cnftrk command is issued for a given trunk, the local end can support the new max PVC number, but the remote end cannot. Workaround: Use the cnftrk command on the remote node (for the same trunk) to determine the maximum permissible value (it will be the lower value of the two nodes).
CSCdj03022	When performing a upgrade from 8.1.70 to 8.4.00, it was observed after the loadrev command was issued, one of the BPX nodes remained in the Loaded state. When a dspstby is done, all states are in the clear state. This is not readily reproducible.
CSCdj33985	Software error 445 occurred on a BPX node.
CSCdj34226	Software error 532 will occur when a dspcons command is executed while SVCs or PVCs are being added or deleted from a VNS station.
CSCdj08657	During a Node-by-Node upgrade, after the switch -g command was executed, a software error 938 (an error from the pSOS pNA facility) was logged. This does not adversely affect the upgrade. Workaround: Use the rrtcon command for the failed connections so that they will be routed again, which will correct the problem.
CSCdj39811	On BXM port cards, unfairness and tail discards can exist due to the non-optimal settings of the QBIN, VI, and VC threshold values.
CSCdj37871
CSCdj41103	After a runrev to the current release is executed, some of the nodes, via the dsprev command may report an older, incorrect version of software running. In actuality, the correct software is running on the node.
CSCdj40779	If a telnet session to the Command Line Interface is terminated abnormally, by not using the bye command to return to the Enter User ID prompt before disconnecting using Control-] chord, then a portion of system memory will be lost (not returned to free memory pool).
CSCdj41517	Software error 21 was observed at an IGX routing node both before and after a non-graceful upgrade from 8.2.04 to the 8.4 release. This did not result in any service outages.
CSCdj39412	On IGX and IPX nodes, the cnfpref command will not correctly recognize trunk specifications which include a virtual trunk number that is two digits in length. That is, for example, using "13.2.31/bpx4" will not work.
CSCdj41077	After invoking a switchcc from a BCC-3 card in slot 7 to a BCC-4 card in slot 8, it was observed that connection continuity was interrupted for 40 minutes, as most of the existing trunks were in Communication Failure.
CSCdj36589	In some circumstances, after a Node-by-Node upgrade was completed, load model inconsistencies were detected via the dsplm command.
CSCdj41231	The background test for the BXM (port) card fails frequently. This is not necessarily an indication that the BXM card is defective.
CSCdj41235	The self-test for the BCC-4 processor card may fail in certain (unknown) circumstances. In the observed case, there were 2 failures in 596 passes. This may not necessarily indicate that the card is defective.
CSCdj41899	It was observed during the provisioning of an FRP-ASI connection segment through StrataView Plus that the SNMP agent returned an error indicating that there is a shift-mode mismatch on the ASI card.
CSCdj42027	During stress testing of the VNS application, an Abort 1000003 occurred. This is due to a race condition, which will be fixed in a future release.
CSCdj41731	It was observed on a BPX node with about 5000 terminating connections and about 12000 via connections which was in the process of re-routing connections and performing a switchcc, that all memory was exhausted such that software errors 501, 977, and 3000000 were logged. This was a recoverable situation.
CSCdj32544	It has been observed in one particular node that the name of the BCC card was listed as "ASM" rather than "BCC". This did not affect the operation of the switch.
CSCdj24325	BPX Slot errors are not collected on BNI-OC3 and ASI-OC3 The dspslotalms command did not show if there were any slot errors on BNI-OC3 or ASI-OC3 cards because these errors were not being accumulated.
CSCdj34069	IGX SWERR 532 upon switchcc on IGX routing node A software error 532 (Bad logical card index) was logged on an IGX routing node after a switchcc.
CSCdj34168	IPX IGX BPX Idle time for fail handler is too high The internal FAIL handler has been optimized and the percentage of processor time that it requires has been reduced.
CSCdj34220	IPX IGX sw err 4208 logged when deleting PVCs/SVCs on VNS start-up. A VNS was restarted after a non-graceful exit. During the restart and the normal deletion of PVCs and SVCs, a software error 4208 was logged.
CSCdj34754	IPX IGX BPX Nodes take up to 10 min. to revert to ckt line clk srcs after clearing LOS When the Circuit Line clock source on which an LOS is created is on the highest numbered node, it could take up to 10 minutes to switch back to the source on clearing the LOS.
CSCdj37700	IPX IGX BPX Takes too long to add/del an object when stats are enabled Adding a single connections locked the user interface up for a minute or more when there were 1000 or more connections, with several connection stats enabled.
CSCdj38564	BPX After switchcc, event log shows an extra unnecessary BXM inserted event. After a switchcc command was executed on a BPX with BXM cards, the log would have an unnecessary informational message stating that a BXM backcard had been inserted and activated.
CSCdj38922	BPX No continuity after adding a connection. There was no data continuity after adding a new ASI connection. It was noted that during the card verification process, the ASI back card is being reset, but never cleared. This will result in channel configuration message not being sent to the card.
CSCdj41999	BPX T3/E3 back cards mismatch with ASI card. T3-3 and E3-3 backcards were not interchangeable between ASI and BNI frontcards (this has been the case since the introduction of these cards). The ASI T3/E3 frontcards will now support these backcards
CSCdj42027	IPX IGX VNS Bulk Calls causes SWSW abort During stress testing of the VNS a race condition occurred that resulted in a 1000003 abort.
CSCdj42841	IPX IGX BPX ASM events are reported only to local StrataViews. Event log messages related to the ASM, such as power supply failures and temperature alarms, are logged to locally attached (link0) StrataViews, but are not broadcast to remote nodes that have StrataViews.
CSCdj43705	BPX cnfchstats on daxcon shows wrong stats When the cnfchstats command was executed on the "other end" of a dax connection that terminated on two different cards (BXM and ASI), the statistics where shown for "this end" of the connection. For example, on a connection originating on an ASI and terminating on a BXM within the same node, cnfchstats on the BXM ("other end") endpoint of the connection would show the data from the ASI ("this end") endpoint of the connection.
CSCdj46114	IPX IGX BPX Expensive inserts in add_lcn_sorted() affecting SWITCHCC performance One of the functions performed during a switchcc has been optimized to improve the time required to complete the switchover
CSCdj46124	IPX IGX BPX For VPC conn, if no VPC conid available, other conns will not get routed If routing chose a path which had the shortest hops, but no available VPC conids, the routing attempt failed. The failure did not increment the failure wait count to allow other connections to route. Every time candidate selection ran, the VPC connection was chosen, and the same invalid route was chosen. Other connections waiting to route would never be routed.

Corrected Anomalies from the 8.4.12 Software Release

The following conditions have been corrected with the 8.4.13 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj52187	After upgrading from 8.1.50 to 8.4.11, some connections were found to lose data. On BPX trunks, line stat sampling was turned on and the "cell header mismatch" error was discovered on some trunks.
CSCdj52353	It was observed that if a DACS connection uses LCN 255 on the trunk then the connection will not route traffic properly.
CSCdj50311	Users are allowed to add more connections on a BXM feeder than it have been configured using the cnftrk command.
CSCdj50812	Voice connections using ADPCM will not upgrade to Fast Modem mode while running release 8.4.07 or 8.4.09.

Corrected Anomalies from the 8.4.11 Software Release

The following conditions have been corrected with the 8.4.12 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj46535	When upgrading IPX feeder node from release 8.4.10 to 8.4.11, the nodename changes from what it was under 8.4.10 to NODENAME. Multiple software errors occurred on the standby NPC card running release 8.4.11.
CSCdj44714	An error message indicating `RIF cannot exceed the peak 50' was received when attempting to modify FR-FR PVCs that don't have RIF parameter.
CSCdj44718	The trap for BCC restart is not generated with right status, severity and reason code.
CSCdj38335	Invoking the nwupgrade switch command can cause the node to downgrade unexpectedly.
CSCdj40779	If a telnet session to the Command Line Interface is terminated abnormally, by not using the bye command to return to the Enter User ID prompt before disconnecting using Control-] chord, then a portion of system memory will be lost (not returned to free memory pool).
CSCdj38707	Executing Node-by-Node upgrade process from software release 8.1.50 to release 8.4.09 resulted in a node unreachability.
CSCdj32054	In a large network containing more than 20 nodes, it is likely that some nodes may take more than three seconds to finish processing the standby update messages during a flash upgrade and thus causing further delay when the command `runrev *' is issued.
CSCdj42590	Data discontinuity observed on connections that are routed over a BNI virtual trunk.
CSCdj32603	BXM generates AIS (end-end) for both upstream and downstream when it detects LOS,LOF,LOC, etc. According to the standard, it should generate AIS only for downstream. Generating AIS also for upstream could cause the misbehavior of the whole alarm transmission system.
CSCdj43640	Comm failure occurs when issuing the command, dsplmistats <slot #>, during BCC switchover or card reset.
CSCdj42923	Software error 123 occurs on a BPX node when a neighbor feeder trunk is in a `in-and out of alarm' state.
CSCdj42511	When invoking the tstdelay command, an error message occurs stating that tstdelay is not valid at trunk end point.
CSCdj27210	The tstber command does not work properly when running switch software release 8.4. The tstber is a vital diagnostic command. It is also used by manufacturing for verification of several important BCC functions.

Corrected Anomalies from the 8.4.10 Software Release

The following conditions have been corrected with the 8.4.10 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj34394	When attempting to re-add the connections deleted by the autodelete command (see CSCdj33379), software error 4205 occurred for every attempt.
CSCdj36826	Incorrect values in the physical card attribute table cause AXIS shelves to become unreachable after loading the software release 8.4.08 image.
CSCdj37318	Resetting the BXM-DS3 Y-redundant card causes communication failure on the DS3 trunk to occur.
CSCdj38707	Executing Node-by-Node upgrade process from software release 8.1.50 to release 8.4.09 resulted in a node unreachability.
CSCdj38337	It was noted that during a Node-by-Node upgrade, CLEAR_MSG messages are queued but not dumped to the network. The would potentially cause nodes to become unreachable when the messages are finally dumped.
CSCdj38922	There was no data continuity after adding a new ASI connection. It was noted that during the card verification process, the ASI back card is being reset, but never cleared. This will result in channel configuration message not being sent to the card.
CSCdj39341	During an upgrade, it was noted that a rebuild problem could likely occur on the node number 64.
CSCdj39402	Abort 1000003 occurred while a batch job reset all cards every 0.5 hour.
CSCdj40425	BXM card with 32K or greater LCNs would use up to 50% of the processor time even if no channels are set.
CSCdj40257	Data discontinuity observed with connections routed over virtual trunks.
CSCdj39700	During a Flash upgrade from software release 8.2.04 to release 8.4.09, software error 21 occurred on two nodes (one IPX, one IGX). A subsequent non-graceful upgrade resulting in data discontinuity.
CSCdj35538	The expected mismatch messages were not displayed when replacing one of the Y-Redundant BXM cards with a card having different PVC counts (i.e., 32K vs. 16K).
CSCdj36677	The tstdelay command reports `test passed' results even when the link being tested is down.
CSCdj36834	The tstdelay command does not work on VP connections added between two ports of the same ASI card.
CSCdj37348	The reroute state machine is not re-enabled after a Node-by-Node upgrade ends.
CSCdj38335	Invoking the nwupgrade switch command can cause the node to downgrade unexpectedly.
CSCdj38228	The dsplog command displays erroneous alarm status.
CSCdj36932	After the reset of a BXM-622 card, a software error 1000 was logged. This indicates a shortage of memory buffers for inter-process message transmission. This occurs on heavily loaded systems.
CSCdj39028	The following event log strings need to have a corresponding Robust Alarm Trap:
	1. BCC n Restarted due to a System Reset
	2. BCC n Restarted due to a Powerfail
	3. CC Redundancy Alarm in slot n
	4. Y Redundancy Alarm in slot n.
CSCdj19597	Software errors (45, 3016, 364) occurred while executing a batch job, which reset cards at a 10-minute interval.
CSCdj39701	The SNMP routine returns an incorrect index value for Frame Relay ports.
CSCdj39969	Software error 424 occurred after removing an active BCC card during a Node-by-Node upgrade.
CSCdj39627	A Robust Alarm Message needs to be generated for a Communication Break event.

Corrected Anomalies from the 8.4.09 Software Release

The following conditions have been corrected with the 8.4.09 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj32934	Handling of error conditions in Utility Processor is not correct, which could cause a Bus Error.
CSCdj33231	The delcon command does correctly delete the channel information from the other end of the connection. This is for BPX-BPX connections.
CSCdj34045	The execution of an addtrk command caused 1M3 abort (Bus Error) and a software error 1117 (Too many topology messages).
CSCdj35421	Memory is lost if a switched virtual circuit is deleted before the routing of the connection has been completed.
CSCdj35151	Comm failure occurred between AXIS and BPX after switchcc on a BPX node.
CSCdj36220	When attempting to clear a comm failure with a manual switchcc, the comm failure continued to occur on the port.
CSCdj36276	Software error 4206 is reported on the standby BCC of a BPX node after the node has recovered from a power failure.
CSCdj36282	Software error 52 (watchdog timer timeout) occurred on a BPX node after failure recovery from a power failure.
CSCdj33379	Software error 614 occurred on a BPX node after invoking a switchcc command.
CSCdj34394	When attempting to re-add the connections that had already been deleted, software error 4205 occurred for every connection addition attempt.
CSCdj36826	AXIS shelves become unreachable after the lanbtld command was invoked.
CSCdj28245	There was no communication between two BCC3s in Boot.
CSCdj32495	The cnfbpnv and dspbpnv commands did not display backplane novram content correctly.
CSCdj32843	Invoking the cbstats clear command did not clear the value in the DROPPED MSGS category.
CSCdj34949	Invoking the clrlnerrs command caused software error 1000003 and a switchcc.
CSCdj34754	BPX takes too long to revert to the primary clock source.
CSCdj33696	Invoking the nwupgrade end * command caused software error 3333 and 1427 to occur.
CSCdj29008	Software error 2064 occurred when VNS bulk calls are being provisioned.
CSCdj34724	Deroute Delay Maximum needs to be raised to 600 seconds.
CSCdj33772	Software error 4205 occurred when running VNS Bulk Call provisioning.
CSCdj35917	Software error 1417 occurred when deltrk and dntrk commands are issued.
CSCdj34821	A switchcc during firmware download caused the target card to fail.
CSCdj36148	Parity errors are not cleaned up correctly on the BPX node.
CSCdj35538	BXM does not report mismatch message when a new Y-redundant card is inserted which has a different max PVC count configured.
CSCdj36677	The tstdelay command reports erroneous test results.
CSCdj36834	The tstdelay command fails on VP connections added between 2 ports on the same ASI card.
CSCdj37649	Logical Endpoint allocation takes lot of time during rebuilds.
CSCdj37348	Connection rerouting was not re-enabled after a Node-by-Node upgrade ends.
CSCdj33667	The clrlnerrs command does not work when the port number is greater than 2.
CSCdj35764	The dspalms command does not display any alarm status even though the node is in major alarm due to problems after a switchcc.
CSCdj31909	When invoking the clrportstats command, user may not be allowed to specify the "all ports" option via use of ala * .
CSCdj36568	The cnfclnsigparm and cnfclnsigparm commands do not work correctly.
CSCdj37070	When attempting to issue dsputl command before the stats areas have not been created for the IPX/IGX node, an error message `Line currently being monitored' is displayed even though there is only one user on the system.

Corrected Anomalies from the 8.4.08 Software Release

The following conditions have been corrected with the 8.4.08 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.


Bug ID	Descriptions
CSCdj25851	It was observed that, at the completion of a burnfwrev command on a BXM-155, the active BCC switched to the standby BCC due to watchdog timeout.
CSCdj25121	Software error 52 occurred and followed by a system abort when routing was turned-on after switchcc is completed.
CSCdj24913	tstdelay command may not working properly when BTM trunk is in the path.
CSCdj27193	Virtual trunks stopped working after upgrade from 8.2 to 8.4.0 release.
CSCdj27713	Due to a database mapping problem, the trunks configurations were lost on an IGX node and hence the connections configured on those trunks received failed status. This problem occurred during the upgrade testing (from 8.2.07 to 8.4.0 release) and was after completion of the power failure test.
CSCdj28302	Due to an error in trunk alarm checking, the alarm counters was incremented even though the ILMI task has stopped sending node status message to SAR when a the trunk or port is in a Major Alarm status. This may have caused an AXIS node to become unreachable.
CSCdj28234	BPX nodes could not be recovered after power failure in the lab.
CSCdj26349	After switchcc on a BPX node, the node continued sending out LMI messages for ASI and BXM ports and would not allow users to telnet or vt to the node for 10-11 minutes. This causes ATM ASI/BXM port failure.
CSCdj29233	It was observed that when routing more than 1500 connections through a BNI-OC3 trunk, communication failure on the trunk would occur.
CSCdj31042	After upgrading the node from release 8.1.19 to 8.4.0, a slow memory depletion (leak) was observed.
CSCdj33231	While investigating tstdelay time-out problem on BXM-T3 to ASI-T3 connections, when the connection were attempted to be deleted from the master side, the VPCs were deleted, but not from the other end. There was software error 3017 generated at the slave end on each delcon.
CSCdj25962	After a Node-by-Node upgrade (from 8.1.50 to 8.4.0), it was observed from an BPX node within the same group to be upgraded that two IPX nodes were not shown status as being upgraded even though the upgrade was successfully completed.
CSCdj25826	Time for ILMI port stats was incremented incorrectly, causing the time polling cycle to restart every 48 seconds rather than every 60 seconds.
CSCdj22859	Due to a mapping problem, an inconsistent status would be shown on the Standby card. This problem occurred during an upgrade from 8.1.xto 8.4.x and the NIB standby update message were processed.
CSCdj24120	It was observed that duplicate "file not found" events were logged by the TFTP Client code and would potentially fill up the event log.
CSCdj26257	When configuring a Frame Relay class on an IPX node, the PIR value was displayed as . but interpreted as 19.2/19.2.
CSCdj17569	On a BXM-T3 Y-Redundant trunk, the active BXM card was reset while the standby card was in a failed state due to a fatal hardware error. Invoking the dspcds command after the card reset showing BXM backcard in a mismatch state.
CSCdj25075	Software error 1000 occurred on a BPX node when deleting a trunk that: 1). splits the network (i.e. the last trunk to a node, or the only trunk connecting two sub nets); 2). has 2500+ connections routed across it to a single node.
CSCdj32686	The clock source was configured on a virtual trunk port BNI-OC3 on a BPX node. When invoking the dspcurclk command on an remote IPX node, the display showed incorrect trunk port value.
CSCdj24948	Connections were added from FRSM-HSSI to FRP and FRM. FRSM-HSSI is configured in DTE mode and traffic is being pumped at the rate of 20Kbps on those connections. The connections are configured with CIR=MIR=PIR=100kbps. Invoking dspchancnt command on both FRP and FRM showed that all frames are received in excess of CIR. It was noticed that bc (Committed Burst) for IPX was set to 0 when it should be set to 65535. FRP/FRM tagging all frames as received in excess of CIR.
CSCdj28594	When issuing a cnfcon command to change the EPD (FBTC) value from disabled to enabled for BXM card, only the ingress of the ports and trunks was enabled. The egress remains as EPD disabled.
CSCdj29291	Memory leak occurred during execution of the FRP background test.
CSCdj24118	BCC stay at DnLder status after switchcc and can only be recovered by removing and putting back the card to for it become active.
CSCdj12410	Inconsistent connection status between two endpoints occurred when the master node was not informed of an error found at the completion of connection re-route on the endpoint node.
CSCdj29001	Software error 532 occurred when invoking VNS voice SVC calls.
CSCdj29677	Changing the receive rate using the cnftrk command following a addtrk command caused some neighbor nodes to become unreachable.
CSCdj07631	An TFTP error 22 indicating that the peak value was invalid occurred when enabling statistics for a BPX node through the Statistics Manager GUI.
CSCdj31320	Changes to the maximum channel count for a trunk were lost after a switchcc. If the channel count was changed at the remote end of a trunk, the local end would not update its standby CC correctly. A subsequent switchcc at the local end would wipe out the new configuration.
CSCdj27042	Due to the changes made to the ADTF value range, a preferred route could not be configured for the connections that has ADTF value equal to 10.
CSCdj33370	Software error 2117 occurred on a BPX node when burning FW is interrupted by a "getfwrev 0.0" command.
CSCdj31439	When attempting to add an AXIS to a BPX node, communication breakdown message occurred. The AXIS shelf can not be added.
CSCdj30470	Software error 2065 occurred on a BPX node approximately 20 minutes after a switchcc. Further investigation indicated that the root cause of this problem was an invalid boundary check on the active, which created a flawed update message for the standby.
CSCdj25547	Background test failure was reported on an ASI Y-Redundant card when congestion on the port occurred and software error 105 were logged.
CSCdj26583	PVCs were in an in-and-out of Alarm state when deltrk was issued or a trunk is in a fail state.
CSCdj29493	Software error 4209 occurred on BPX nodes while the BCC was in standby status.
CSCdj31105	Even though the dnln command was issued for ASI-155E card the front LED stayed on active. It appeared as though the card was active when it wasn't.
CSCdj32843	When trying to clear cbstats using cbstats clear command, the DROPPED MSGS category were never cleared.
CSCdj31091	When a clrlnerrs command was issued, it caused 1000003 abort and a switchcc.

Problems Fixed in Release 8.4.07:

Bug ID

Descriptions

CSCst96798

Switch software sets shelfCnfgRebuildStatus object as REBUILD when switchcc occurs. DNS software interprets this as the node went down and deletes all SVCs associated with that node. This will cause calls to be dropped.

Problems Fixed in Release 8.4.06:

Bug ID

Descriptions

CSCdj24114

A 1000003 abort occurred when attempting to add more than 12,000 connections.

CSCdj26862

A software error 4209 occurred while adding connections due to the local resources unavailability.

CSCdj28579

Remove debugging code that logged software error 7777.

CSCdj27744

BXM feeder trunks weren't being programmed during the card configuration process.

Problems Fixed in Release 8.4.05:

Bug ID

Descriptions

CSCdj19652

The dspclksrcs command shows invalid clock source information, The primary, secondary, and tertiary sources are incorrect.

CSCdj03075

A virtual path connection could not be added because the support for BNI-E3 cards is missing.

CSCdj21794

A software error 614 (LCON automatically deleted) due to the logical endpoint VC index did not agree at each end.

CSCdj22424

Routing virtual trunk traffic through a BXM via trunk does not work.

CSCdj23350

IPX feeder nodes cannot use the trunk as a timing source. The "pass sync" option is not allowed on feeder trunks. Packet lines which pass sync are not allowed to be clock sources.

CSCdj27532

When nwip_on is asserted in the ~svplus/config.sv file, the savecnf operation does not work from an IPX feeder.

CSCdj23570

Multiple problems after performing a switchcc on a BPX with many connections: the problems are all caused by comm failures due to inefficient programming of the BXM cards.

CSCdj27129

A 100003 abort occurred when handling an error condition returned by the SAR which indicated that an invalid command was received.

CSCdj27059

Software error 514 occurred on a heavily loaded BPX node.

CSCdj19165

There is a 10-15 second delay in traffic continuity after a port Y-redundant switchover.

CSCdj19637

Incorrect trunk number is shown as the clock source when using the dspcurclk command.

CSCdj19512

The dspports command only displays the first 96 ports of a BPX node.

CSCdj20069

Standby Y-redundant cards can still drive the clock bus.

CSCdj15103

Software error 4208 (Bad connection address type) occurred on a BPX node.

CSCdj21070

Invoking dspcons with a starting channel number as the only argument fails to display the appropriate connections.

CSCdj20682

A BPX event log indicates that there are BFrame parity errors and Rx Invalid Port errors, but the StrataView Plus HPOV event log does not indicate any of these.

CSCdj22346

After a graceful upgrade from 8.1.50, trunk number 32 is missing.

CSCdj21369

The cnfswfunc feature 6 on a BPX, ABR standard with VSVD, becomes disabled when any IPX or IGX routing node rebuilds.

CSCdj23566

Using dspport or dspports with only a slot number as the argument incorrectly displays Speed as "UNKNOWN" and Interface as "EMPTY".

CSCdj26131

The cnfclksrc command allows a trunk to be a primary clock source while it is passing sync.

CSCdj25301

On the BXM, Early Packet Discard (EPD) and/or Frame Discard is not enabled.

CSCdj26827

On an ASI-T3 card, the 1000th connection on the card is not programmed correctly.

CSCdj27511

Software error 618 occurred on a heavily loaded BPX node.

Note There is no 8.4.04 Release

Problems Fixed in Release 8.4.03:

Bug ID

Descriptions

CSCdj15795

Software error 1406 (indicating a bad checksum on a network topology update message) floods the error log.

CSCdj16467

For BXM-DS3 terminated connections, Virtual Path Connections do not operate when the other end terminates on an AXIS shelf in NNI mode.

CSCdj16162

After a Y-Redundant switchover between a pair of BXM cards, it has been observed that a software error 105 (CBUS buffers full) was logged. This is due to multiple connections being re-configured within one CBUS message, which results in a much longer than expected execution time. This will be addressed in the next release where appropriate message throttling will be inserted. At this time, BXM port and trunk cards should not be configured in Y-redundant pairs.

CSCdj14719

The BPX is constantly re-routing connections due to the failure of topology updating, which caused an incorrect view of the topology to exist.

CSCdj18088

There is network topology corruption caused by a node, whose number is set to 64, when that node rebuilds.

CSCdj19179

After a Node-by-Node upgrade, there are cases where the battery backed up RAM is not being rewritten properly.

CSCdj15047

The dspnwip command repeatedly displays the same node's information, rather than all the nodes.

CSCdj09736

There is an intermittent condition where a self-test timeout occurs on the BCC-32. This is not a true indication of a problem with the BCC.

CSCdj12314

When rerouting connections that terminate on AXIS shelves due to the establishment of a preferred route, failure status is reported because an A-bit alarm is being sent by the BPX.

CSCdj15594

Multiple software errors 21 were logged on a BPX.

CSCdj15999

The addcon command cannot be used in jobs on the BPX. An infinite loop results.

CSCdj15226

After a node rebuilds, messages indicating that the time of day is changing is flooding the event log.

CSCdj11989

After a switchcc command is issued, the event log is formatted after the switch, and thus the switchcc even will not be reported to StrataView Plus.

CSCdj17569

A BXM-DS3 trunk card in y-redundant configuration indicated a backcard mismatch after being reset. At the time, the standby card was in failed state.

CSCdj18216

Invoking the dsptrkstats commands on virtual trunks shows incorrect BFrame cell count values.

CSCdj09369

On the cnftrk command, for BNI-OC3 trunks the Payload Scramble option cannot be set to "No" because it results in an Out Of Frame alarm. The software must prevent the user from making this setting.

CSCdj19165

There is a 15 second delay/interruption of traffic on BXM port cards after a Y-redundant switchover occurs.

CSCdj19637

An incorrect trunk number is displayed as the clock source when running the dspcurclk command.

CSCdj19512

The dspports command displays only the first 96 ports of a node.

CSCdj13934

The dspports command works on IPX nodes but not on BPX nodes.

CSCdj10363

The Deroute Delay Timer value used always varies 2 seconds from the configured value.

Problems Fixed in Release 8.4.02:

Bug ID

Descriptions

CSCdj17869

During an upgrade from 8.1.5, multiple node unreachabilities were encountered, along with software errors 254 and 526.

CSCdj15833

CSCdj16479

A feeder shelf cannot be deleted. When the delshelf command is issued, the message "Resources Low---Interface Shelf not changed."is returned.

CSCdj16874

During an upgrade from 8.1.5 to 8.4.0, the standby BCCs on all the BPX nodes keep toggling between the upgrading and upgraded/(clear) state.

Compatibility Matrix

AXIS 4.0 F/W Compatibility

PCB Description

Rev.

Latest F/W

Minimum F/W

IMATM F/W

C

4.0.16

4.0.04

IMATM Boot

N/A

4.0.01

4.0.00

ASC F/W

M

4.0.18

4.0.04

ASC Boot

N/A

4.0.04

4.0.03

BNM-E3

B

N/A

N/A

FRSM-4T1

C

4.0.16

4.0.04

FRSM-4T1 Boot

N/A

4.0.00

4.0.00

SRM T1E1 (B)

B

N/A

N/A

CESM-4T1/E1

C

4.0.13

4.0.04

CESM Boot

N/A

4.0.00

4.0.00

AUSM-4T1E1

B

4.0.16

4.0.04

AUSM Boot

N/A

4.0.00

4.0.00

FRSM-8T1

A

4.0.16

4.0.04

FRSM-8T1 Boot

N/A

4.0.01

4.0.00

FRSM-HS1

A

4.0.13

4.0.04

FRSM-HS1 Boot

N/A

4.0.00

4.0.00

AUSM-8T1/E1

A

4.0.17

4.0.04

AUSM-8T1/E1 Boot

N/A

4.0.01

4.0.00

Release 8.4 BPX System F/W Compatibility

BPX Boot Codes

PCB Description

Rev.

Latest F/W

Minimum F/W

BCC (model B) boot

K

HBJ

HBH

BCC3-32 (model C) boot

K

HCM

HCH

BCC3-64 (model D) boot

K

HDM

HDJ

BCC4 (model E) boot

K

HEM

HEM

BPX F/W

PCB Description

Rev.

Latest F/W

Minimum F/W

ASI 155

EOL

WHC

WHB

ASI 155 E

E

WEC

WEB

ASI-1 2T3/C

D

UCE

UCA

ASI-1 2T3/B

D

UBK

UBH

BNI 3T3/C

F

TCM

TCK

BNI 3E3/B

F

TCM

TCK

BNI 155 E

E

VDP

VDN

BNI I55

EOL

VBP

VBN

ASM

B

GAC

GAC

BXM 4P

A

MBY

MBM

BXM 8P

A

MBY

MBM

Release 8.4 IPX/IGX System F/W Compatibility

Boot Codes

PCB Description

Latest F/W

Minimum F/W

Comments

NPC Boot

BAF

BAF

NPC 32 Boot

BBF

BBF

NPC 64 Boot

BCF

BCF

NPM Boot

RAP

RAJ

NPM 32 Boot

RBP

RBJ

NPM 64 Boot

RCP

RCN

NPM 32B Boot

REN

REJ

NPM 64B Boot

RFN

RFN

IPX/IGX F/W

PCB Description

Latest F/W

Minimum F/W

Comments

ALM-A

CAE

CAA

ALM-B

CBH

CBB

BTM Model A

IAF

IAF

BTM Model B

IBL

IBK

BTM Model D

IDA

IDA

CVM Model A

DAF

DAF

CVM Model B

DBD

DBD

CVM Model C

DCA

DCA

FRM Model D

FDZ

FDR

Avoid Rev. FDU & FDV

FRM Model E

FEZ

FER

Avoid Rev. FEU & FEV

FRM (B)

FHB

FHB

FRM-2

FFD

FFC

FTM Model B

JBJ

JBB

FTM Model C

JCB

JCA

HDM

SCF

SCF

LDM

LCB

LC3

NTM

NEJ

NED

NTM (B)

NFH

NFD

Recommend using NFF

AIT Model A

IAF

IAE

AIT Model B

IBL

IBK

CDP Model A

DAF

DAF

CDP Model B

DBD

DBC

FRP(M) Model D

FDZ

FDR

Avoid Rev FDU & FDV

FRP(M) Model E

FEZ

FER

Avoid Rev FEU & FEV

FRP(M) Model H

FHB

FHB

FRM(B)

FTC Model B

JBJ

JBB

FTC Model C

JCB

JCA

NTC

NEJ

NED

SDP

SCF

SCF

UFM-C

ZAL

ZAB

UFM-U

YAD

YAA

UVM

DAC

DAA

UVM-B

DBA

DBA

UVM-C

DCA

DCA

UVM-D

DDA

DDA

Release 8.4.30 System Content

Switch Software and Boot Codes

Release ID

Product

Rev.

Model

Image

SwSw 8.4.30

Sys S/W IPX

8.4.30

Sys S/W IGX

8.4.30

Sys S/W BPX

8.4.30

BCC (Model B) Boot

J0

B

HBJ

BCC3-32 (Model C) Boot

M0

C

HCM

BCC3-64 (Model C) Boot

M0

D

HDM

BCC4 (Model E) Boot

M0

E

HEM

NPC Boot

F0

A

BAF

NPC 32 Boot

F0

B

BBF

NPC 32 Boot

F0

C

BCF

NPM Boot

P0

A

RAP

NPM 32 Boot

P0

B

RBP

NPM 64 Boot

P0

C

RCP

StrataView Plus

Release ID

Product

Rev.

Model

Image

SV 8.4.12

StrataView Plus

8.4.12

StrataView Plus SCM

8.4.12

SNMP

8.4.12

Hardware and Firmware Products

Release ID

Product

Rev

Model

Image

AXIS 4.0.18

IMATM F/W

A0

4.0.16

4.0.16

IMATM Boot

N/A

4.0.00

4.0.00

ASC F/W

A0

4.0.18

4.0.18

ASC Boot

A0

4.0.04

4.0.04

BNM-E3

N/A

N/A

N/A

FRSM-4T1

A0

4.0.16

4.0.16

FRSM-4T1 Boot

N/A

4.0.00

4.0.00

FRSM-8T1

A0

4.0.16

4.0.16

FRSM-8T1 Boot

N/A

4.0.01

4.0.01

FRSM-HS1

A0

4.0.13

4.0.13

FRSM-HS1 Boot

N/A

4.0.00

4.0.00

SRM T1/E1 (B)

N/A

N/A

N/A

CESM-4 T1/E1

A0

4.0.13

4.0.13

CESM Boot

N/A

4.0.00

4.0.00

AUSM-4 T1/E1

A0

4.0.16

4.0.16

AUSM-4 T1/E1 Boot

N/A

4.0.00

4.0.00

AUSM-8 T1/E1

A0

4.0.17

4.0.17

AUSM-8 T1/E1 Boot

N/A

4.0.01

4.0.01

BPX 8.4.30

ASI 155

B0

E

WEC

ASI 155E

B0

H

WHC

ASI-1 2T3/E3

E0

C

UCE

ASI-2 T3/E3

J0

B

UBJ

BNI 3T3/E3

M0

C

TCM

BNI 155E

P0

D

VDP

BNI I55 0C3

P0

B

VBP

BNI 3T3/E3

M0

C

TCM

ASM

A0

A

GAC

IGX 8.4.30

BTM

L0

B

IBL

CVM

F0

A

DAF

CVM Model B

D0

B

DBD

CVM Model C

A0

C

DCA

FRM (Model D)

Z0

D

FDZ

FRM (Model E)

Z0

E

FEZ

FRM -2

D0

F

FFD

HDM

F0

C

SCF

ALM-A

E0

A

CAE

ALM-B

H0

B

CBH

UFM-C

E0

A

ZAE

UFM-U

D0

A

YAD

UVM

C0

A

DAC

FTM

A0

C

JCA

LDM

B0

C

LCB

NTM

J0

E

NEJ

NTM (B)

H0

F

NFH

IPX 8.4.30

AIT Model A

F0

A

IAF

AIT Model B

L0

B

IBL

CDP

F0

A

DAF

LDP

B0

C

LCB

FRP Model D

Z0

D

FDZ

FRP Model E

Z0

E

FEZ

FTC Model C

B0

C

JCB

NTC

J0

E

NEJ

SDP

F0

C

SCF

Hardware Compatibility Matrices

AXIS 4.0 H/W Compatibility

PCB Description

Part Number

Latest H/W

Minimum H/W

IMATM 8T1

73-3026-01

F

A

IMATM 8E1

73-3027-01

F

A

ASC

73-2454-01

N

H

ASC 2

73-2586-01

B

A

BNM-E3

73-2866-01

B

A

BNM-T3

73-2802-01

C

A

BNM-155

73-2459-02

C

A

FRSM-4T1

73-2455-01

C

A

FRSM-4E1

73-2456-01

C

A

SRM T1E1 (B)

73-2565-01

C

B

CESM-4T1

73-2525-02

F1

B

CESM-4E1

73-2541-02

E2

B

AUSM-4T1

73-2990-01

C

A

AUSM-4E1

73-2991-01

C

A

FRSM-8T1

73-2367-04

A1

A1

FRSM-8E1

73-2360-04

A1

A1

FRSM-HS1

73-2602-02

C

A

AUSM-8T1

73-2493-05

C

A

AUSM-8E1

73-2494-05

C

A

FRASM-8T1

73-2347-04

A2

A2

BPX 8.4 H/W Compatibility


PCB Description	Part Number	Latest H/W	Minimum H/W
BCC-32M (Non -Orderable)	73-213840-00	P	A
BCC-64M (Non-Orderable)	73-213840-01	P	A
BCC-BC (Non-Orderable)	73-211380-00	D	A
BCC-3-32M	73-217770-00	M	J
BCC-3-64M	73-217701-01	M	J
BCC-3-BC	73-2671-01	C	A
ASM	73-214020-00	C	A
ASM-BC	73-211910-00	C	A
BXM-T3-8	73-2589-05	D	A
BXM-E3-8	73-2591-05	D	A
BXM-T3-12	73-2588-05	D	A
BXM-E3-12	73-2590-05	D	A
T3/E3-BC	73-2759-02	A	A
BXM-155-8	73-2490-05	D	A
MMF-155-8-BC	73-219870-00	A	A
SMF-155-8-BC	73-219870-02	A	A
SMFLR-155-8-BC	73-2411-01	A	A
BXM-155-4	73-2492-05	D	A
MMF-155-4-BC	73-219870-01	A	A
SMF-155-4-BC	73-219870-03	A	A
SMFLR-155-4-BC	73-2412-01	A	A
BXM-622-2	73-2473-08	H	A
622-2-BC	73-2884-01	B	A
SMFLR-622-2-BC	73-2885-01	B	A
BNI-3-T3/C	73-2637-01	J	A
BNI-3-E3/B	73-2638-01	K	A
BNI-2-155/B	73-218100-01	K	A
ASI-2-E3/B	73-216330-01	F	A
ASI-2-T3/C	73-216330-00	F	A
ASI-2-155E	73-218100-00	K	A
T3-BC	73-213070-01	E	A
E3-BC	73-213070-01	E	D
MMF-2-BC	73-214290-00	C	A
SMF-2-BC	73-216270-00	C	A
SMFLR-2-BC	73-216270-01	C	A
BCC-4V	73-3057-02	B	B
BME-0C12	73-2469-07	F	A

IPX 8.4 H/W Compatibility


PCB Description	Part Number	Latest H/W	Minimum H/W
IPX-NPC-550051	73-215280-00	H	A
IPX-NPC-550052	73-215280-01	H	A
IPX-ARC-512010	73-212340-01	E	A
BC-512011	73-212360-00	C	A
IPX-FTC-6350	73-2611-01	K	A
BC-6351A-V35	73-213240-00	E1	A
BC-6352A-T1	73-213420-00	C	A
BC-6353A-E1	73-213410-00	B	A
BC-6354A-X21	73-214120-00	C	A
IPX-NTC-6161E	73-213210-00	L	A
BC-6271A-T1	73-207380-00	L	A
BC-6171A-E1	73-207370-01	N	A
BC-6083A-SR	73-208540-00	H1	A
BC-550150-Y1	73-210820-01	D	A
IPX-AIT-571000	73-215130-00	E	A
BC-571110A-T3	73-2879-01	J	A
BC-571210A-E3	73-2679-01	H	A
IPX-SDP-5080C	73-2853-01	F	A
BC-5082A-V35	73-2450-01	K	A
BC-5083A-RS449	73-204850-00	V1	A
BC-5084B-RS232	73-2723-01	W1	A
IPX-LDP-5285C	73-207250-00	K2	A
BC-5286A-RS232	73-207180-01	L	A
BC-5287A-RS232	73-207180-00	L	A
IPX-T1-511477	73-209660-01	H	A
IPX-E1-511478	73-209660-02	H	A
IPX-511475-TT	73-209660-20	H	A
BC-6271A-T1	73-207380-00	L	A
BC-6171A-E1	73-207370-01	N	A
BC-550100-J1	73-210820-00	C	A
IPX-FRP31-6260E	73-207560-00	U	A
IPX-FRP2-6270A	73-2611-01	K	A
BC-6251B-V35	73-209570-00	L	A
BC-6254A-X21	73-211440-00	H	A
BC-6355A-X21	73-214120-01	C	A

IGX 8.4 H/W Compatibility


PCB Description	Part Number	Latest H/W	Minimum H/W
IGX-NPM-32	73-2894-01	W	A
IGX-NPM-64	73-2895-01	W	A
IGX-NPM-32B	73-2554-02	C	A
IGX-NPM-64B	73-2363-02	C	A
IGX-SCM	73-215080-00	T	A
IGX-ARM	73-218230-00	A	A
BC-512011	73-212360-00	C	A
IGX-NTM	73-2296-04	D	A
BC-6271A-T1	73-207380-00	L	A
BC-6171A-E1	73-207370-01	N	A
BC-6083A-SR	73-208540-00	H	A
BC-550150-Y1	73-210820-01	D	A
IGX-BTM/B	73-3005-02	E	A (BTM/B=AIT+ACM1)
ACM1	73-2921-02	T	A
BC-571110A-T3	73-2879-01	J	A
BC-571210A-E3	73-2679-01	H	A
BC-571310A-E2	73-215940-00	D	A
BC-571410A-HSSI	73-216370-00	A	A
IGX-ALM/A	73-2558-02	E	A (NO ACM CARD)
IGX-ALM/B	73-2558-02	E	A (NO ACM CARD)
BC-UAI-1T3	73-217040-00	C	A
BC-UAI-1E3	73-2986-01	C	A
IGX-UXM-4-155-SMF	73-2511-02	A	A (NO ACM CARD)
BC-UAI-4-155-SMF	73-2703-03	A	A
IGX-UXM-4-155-MMF	73-2511-02	A	A (NO ACM CARD)
BC-UAI-4-155-MMF	73-2705-03	A	A
IGX-UXM-2-155-SMF	73-2511-02	A	A (NO ACM CARD)
BC-UAI-2-155-SMF	73-2699-03	A	A
IGX-UXM-6-T3	73-2511-02	A	A (NO ACM CARD)
BC-UAI-6-T3	73-2952-02	A	A
IGX-UXM-3-T3	73-2511-02	A	A (NO ACM CARD)
BC-UAI-3-T3	73-2954-02	A	A
IGX-UXM-6-E3	73-2511-02	A	A (NO ACM CARD)
BC-UAI-6-E3	73-2953-02	A	A
IGX-UXM-3-E3	73-2511-02	A	A (NO ACM CARD)
BC-UAI-3-E3	73-2955-02	A	A
IGX-UXM-8-E1-BNC	73-2511-02	A	A (NO ACM CARD)
BC-UAI-8-E1-BNC	73-2932-02	A	A
IGX-UXM-4-E1-BNC	73-2511-02	A	A (NO ACM CARD)
BC-UAI-4-E1-BNC	73-3061-01	A	A
IGX-UXM-8-T1-DB15	73-2511-02	A	A (NO ACM CARD)
BC-UAI-8-T1-DB15	73-2941-02	A	A
IGX-UXM-8-E1-DB15	73-2511-02	A	A (NO ACM CARD)
BC-UAI-8-E1-DB15	73-2942-02	A	A
IGX-UXM-4-T1-DB15	73-2511-02	A	A (NO ACM CARD)
BC-UAI-4-T1-DB15	73-3059-01	A	A
IGX-UXM-4-E1-DB15	73-2511-02	A	A (NO ACM CARD)
BC-UAI-4-E1-DB15	73-3060-01	A	A
IGX-FTM	73-2519-01	K	A (FTM=FTC+ACM1A)
ACM1A	73-2930-02	T	A
BC-6351A-V35	73-213240-00	E	A
BC-6352A-T1	73-213420-00	C	A
BC-6353A-E1	73-213410-00	B	A
BC-6354A-X21	73-214120-00	C	A
IGX-HDM	73-2853-01	F	A (HDM=SDP+ACM2)
ACM2	73-2922-02	R	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 (LDM=LDP+ACM1A)
ACM1A	73-2930-02	T	A
BC-5286A-RS232	73-207180-01	L	A
BC-5287A-RS232	73-207180-00	L	A
IGX-CVM-DSOA	73-3002-02	H	A (CVM=CDP+ACM1A)
IGX-CVM-T1EC	73-3003-02	H	A (CVM=CDP+ACM1A)
IGX-CVM-E1EC	73-209660-02	H	A (CVM=CDP+ACM1A)
BC-6271A-T1	73-207380-00	L	A
BC-6171A-E1	73-207370-01	N	A
BC-550100-J1	73-210820-00	C	A
IGX-FRM	73-2517-03	M	A (NO ACM CARD)
IGX-FRM-31	73-2517-03	M	A (NO ACM CARD)
IGX-FRM-2	73-2519-01	K	A (FRM-2=FRP+ACM1A)
BC-6251B-V35	73-209570-00	L	A
BC-6254A-X21	73-211440-00	H	A
BC-6355A-X21	73-214120-01	C	A
IGX-UFM-4C	73-2531-01	D	A (NO ACM CARD)
IGX-UFM-8C	73-2531-02	F	A (NO ACM CARD)
BC-UFI-8T1-DB15	73-2444-02	B	A
BC-UFI-8E1-DB15	73-2445-02	B	A
BC-UFI-8E1-BNC	73-2449-02	B	A
IGX-UFM-U	73-2349-04	D	A (NO ACM CARD)
BC-UFI-12V35	73-2711-01	A	A
BC-UFI-12X21	73-2712-01	A	A
BC-UFI-4HSSI	73-220200-00	B	A
IGX-UVM	73-2361-01	C	A (NO ACM CARD)
BC-UVI-2E1EC	73-2420-01	B	A

Obtaining Service and Support

For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.

Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services.

For service and support for a product purchased directly from Cisco, use CCO.

Cisco Connection On-line

Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.

Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.

CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.

You can access CCO in the following ways:

•WWW: http://www.cisco.com

•WWW: http://www-europe.cisco.com

•WWW: http://www-china.cisco.com

•Telnet: cco.cisco.com

•Modem: From North America, 408 526-8070; from Europe, 33 1 64 46 40 82. Use the following terminal settings: VT100 emulation; databits: 8; parity: none; stop bits: 1; and connection rates up to 28.8 kbps.

For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.

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

78-4843-06

Table Of Contents

8.4.30 Version Software Release Notes Cisco WAN Switching Software

Clarifications:

Special Installation/Upgrade Requirements

General

Control Card Requirements

BCC Boot Firmware Requirements

BCC Compatibility Requirements

BCC Physical Card Upgrade Procedure

Software Upgrades Supported

Restrictions on Node-by-Node Upgrade From 8.1.50:

Additional Deliverables

SNMP MIB:

Switch MIB changes of Release 8.4.00:

Features Not Supported

Committed (but not being delivered in this release):

Explicitly Excluded:

Obsoleted:

Notes & Cautions

Limitations

Required Workarounds:

Additional Documentation:

Compatibility Notes

Known Anomalies in this Software Release

Corrected Anomalies in this Software Release

Corrected Anomalies from the 8.4.20 Software Release

Corrected Anomalies from the 8.4.19 Software Release

Corrected Anomalies from the 8.4.18 Software Release

Corrected Anomalies from the 8.4.17 Software Release

Corrected Anomalies from the 8.4.16 Software Release

Corrected Anomalies from the 8.4.15 Software Release

Corrected Anomalies from the 8.4.14 Software Release

Corrected Anomalies from the 8.4.13 Software Release

Corrected Anomalies from the 8.4.12 Software Release

Corrected Anomalies from the 8.4.11 Software Release

Corrected Anomalies from the 8.4.10 Software Release

Corrected Anomalies from the 8.4.09 Software Release

Corrected Anomalies from the 8.4.08 Software Release

Problems Fixed in Release 8.4.07: Bug ID Descriptions CSCst96798 Switch software sets shelfCnfgRebuildStatus object as REBUILD when switchcc occurs. DNS software interprets this as the node went down and deletes all SVCs associated with that node. This will cause calls to be dropped.

Compatibility Matrix

Release 8.4 BPX System F/W Compatibility

BPX Boot Codes PCB Description Rev. Latest F/W Minimum F/W BCC (model B) boot K HBJ HBH BCC3-32 (model C) boot K HCM HCH BCC3-64 (model D) boot K HDM HDJ BCC4 (model E) boot K HEM HEM

BPX F/W PCB Description Rev. Latest F/W Minimum F/W ASI 155 EOL WHC WHB ASI 155 E E WEC WEB ASI-1 2T3/C D UCE UCA ASI-1 2T3/B D UBK UBH BNI 3T3/C F TCM TCK BNI 3E3/B F TCM TCK BNI 155 E E VDP VDN BNI I55 EOL VBP VBN ASM B GAC GAC BXM 4P A MBY MBM BXM 8P A MBY MBM

Release 8.4 IPX/IGX System F/W Compatibility

Boot Codes PCB Description Latest F/W Minimum F/W Comments NPC Boot BAF BAF NPC 32 Boot BBF BBF NPC 64 Boot BCF BCF NPM Boot RAP RAJ NPM 32 Boot RBP RBJ NPM 64 Boot RCP RCN NPM 32B Boot REN REJ NPM 64B Boot RFN RFN

Release 8.4.30 System Content

StrataView Plus Release ID Product Rev. Model Image SV 8.4.12 StrataView Plus 8.4.12 StrataView Plus SCM 8.4.12 SNMP 8.4.12

Hardware Compatibility Matrices

Obtaining Service and Support

Cisco Connection On-line

8.4.30 Version Software Release Notes
Cisco WAN Switching Software

Problems Fixed in Release 8.4.07:

Bug ID

Descriptions

CSCst96798

Switch software sets shelfCnfgRebuildStatus object as REBUILD when switchcc occurs. DNS software interprets this as the node went down and deletes all SVCs associated with that node. This will cause calls to be dropped.

BPX Boot Codes

PCB Description

Rev.

Latest F/W

Minimum F/W

BCC (model B) boot

K

HBJ

HBH

BCC3-32 (model C) boot

K

HCM

HCH

BCC3-64 (model D) boot

K

HDM

HDJ

BCC4 (model E) boot

K

HEM

HEM

Boot Codes

PCB Description

Latest F/W

Minimum F/W

Comments

NPC Boot

BAF

BAF

NPC 32 Boot

BBF

BBF

NPC 64 Boot

BCF

BCF

NPM Boot

RAP

RAJ

NPM 32 Boot

RBP

RBJ

NPM 64 Boot

RCP

RCN

NPM 32B Boot

REN

REJ

NPM 64B Boot

RFN

RFN

StrataView Plus

Release ID

Product

Rev.

Model

Image

SV 8.4.12

StrataView Plus

8.4.12

StrataView Plus SCM

8.4.12

SNMP

8.4.12