Cisco MGX 8800 Series Switches

Table Of Contents

Release Notes for Cisco WAN MGX 8850 Switch Software Release 2.0.14

Contents

Introduction

PNNI Features in Release 2.0.14

System Requirements

Hardware Supported

AXSM Cards

PXM45 Cards

Software Compatibility

Compatibility Matrix

Release 2.0.14 System Content

Additional Deliverables for Release 2.0.14

Upgrading to a New Software Release

Upgrading PXM45 Boot and Runtime Images from 2.0.12/2.0.13 to 2.0.14

Upgrading AXSM Boot and Runtime Images from 2.0.12/2.0.13 to 2.0.14

New and Changed Information

New CLI Commands

Changed CLI Commands

addcon

clrxbaralms

dspalm

dspalms

dspapsln

dspapslns

dspln

dsplns

dspxbaralms

saveallcnf

New Features in Release 2.0.14

Obsoleted Features in Release 2.0.14:

Installation Notes and Cautions

Limitations and Restrictions

Important Notes

BITS Clock Source Configuration

APS Management Information

Recommendations

Documentation Correction — Feeder Configuration

Known Anomalies in Release 2.0.14

Problems Fixed in Release 2.0.14

Known Anomalies found In Previous Releases

Problems Fixed in Release 2.0.13

Problems Fixed in Release 2.0.12

Problems Fixed in Release 2.0.11

Problems Fixed in Release 2.0.10

Problems Fixed in Release 2.0.02

Related Documentation

Obtaining Documentation

World Wide Web

Documentation CD-ROM

Ordering Documentation

Documentation Feedback

Obtaining Technical Assistance

Cisco.com

Technical Assistance Center

Contacting TAC by Using the Cisco TAC Website

Contacting TAC by Telephone

Service and Support

Release Notes for Cisco WAN MGX 8850 Switch Software Release 2.0.14

---

Contents

---

Introduction

These release notes describe the PNNI features, system requirements, upgrade procedures, command Line Interface (CLI) changes, and limitations that apply to Release 2.0.14. These notes also contain Cisco support information. Follow-on releases are planned to add new features, and can be found in the Marketing Road Map.

PNNI Features in Release 2.0.14

Defined by the ATM Forum for ATM networks, PNNI provides a dynamic routing protocol, is responsive to changes in network resource availability, and scales to very large networks.

PNNI includes two categories of protocols. PNNI defines a protocol for distributing topology information between switches and clusters of switches. This information is used to compute paths through the network. PNNI topology and routing are based on a well-known link-state routing technique.

PNNI also defines a second protocol for signaling, that is, message flows used to establish point-to-point connections across the ATM network. This protocol is based on the ATM Forum UNI 4.0 signaling, with mechanisms added to support source routing, crankback, and alternate routing of call setup requests in case of connection setup failure. Whereas the UNI signaling protocol distinguishes between the user and network sides of a connection, PNNI is a symmetrical protocol.

PNNI provides dynamic ATM routing with quality of service (QoS) support as defined by the ATM Forum. PNNI uses link-state and source-state route technology, supports aggregation for private ATM addresses and links between switches, and can scale the network and its performance by means of configuring PNNI peer groups and hierarchical levels. A key feature of the PNNI mechanism is its ability to automatically configure itself in networks in which the address structure reflects the topology.

The functions of the PNNI routing protocol include:

•Hello protocol (allows adjacent switches to exchange topology information)

•PTSE (PNNI Topology State Elements) database synchronization and management

•PTSE flooding

•Address summarization and advertisement

•Link and nodal aggregation

•Pre-computation of routing tables

•Quality of Service (QoS) based routing

•Multiple Routing Metrics

•Discovery of neighbors and link status

•Synchronization of topology databases

•Load balancing on equal cost paths

•Load balancing on parallel links

•Load balancing with redundant addresses

•Alternate paths

These PNNI features are supported in Release 2.0 of the MGX:

•UNI 3.0/3.1

•PNNI 1.0 Single Peer Group

•ILMI 4.0

•Point to point ATM SVCC and SVPC

•Support for ABR, CBR, VBR, rt-VBR, and UBR

•Alternate call routing (see separate feature description)

•On demand call routing (see separate feature description)

•Native E.164 and AESA (E.164, ICD, DCC) [formerly NSAP] address format

•Enhanced CAC with per service class policy parameter (see separate feature description)

•Per class of service overbooking

•Congestion control (see separate feature description)

•PNNI connection and path trace

•OAM fault management

•Address filtering (see separate feature description)

•Intelligent CAC (see separate feature description)

•Call processor redundancy

PNNI networks are highly resilient due to their ability to quickly reroute connections around failed network elements, and to update routes and network topology based upon availability of network resources. Connections will generally route quickly using pre-computed routing tables, but in the case of congestion or during a network failure, on-demand routes will be calculated for connections.

System Requirements

This section describes the hardware supported in this release and the software compatability requirements.

Hardware Supported

The following table lists support hardware for Release 2.0.14:

Model	800 Part Number	Revision
PXM45	800-06147-07	A0
PXM45/B	800-09266-03	A0
PXM-UI-S3	800-05787-02	A0
PXM-HD	800-05052-03	A0
AXSM-1-2488	800-05795-05	A0
SMFSR-1-2488	800-05490-05	A0
SMFXLR-1-2488	800-05793-05	A0
SMFLR-1-2488	800-06635-04	A0
AXSM-16-155	800-05776-06	A0
AXSM-4-622	800-05774-09	A0
AXSM-16-T3/E3	800-05778-08	A0
SMFIR-2-622	800-05383-01	A0
SMFLR-2-622	800-05385-01	A0
SMB-8-T3	800-05029-02	A0
SMB-8-E3	800-04093-02	A0
MMF-8-155	800-04819-01	A0
SMFIR-8-155	800-05342-01	A0
SMFLR-8-155	800-05343-01	A0
APS RDNT CON	800-05307-01	A0

AXSM Cards

The AXSM card is a double-height ATM service module that is compatible with release 2.0 and later PXM45 based versions of the MGX switch. The AXSM card uses the serial line traces on the MGX chassis to access the 45Gbps crosspoint fabric of the PXM45 card and the STRATM48 ASIC technology to accommodate a full duplex throughput of OC48c/STM16.

The AXSM card provides ATM switching and line functionality, and is compatible with the feature set of the BXM card on the BPX, the UXM card on the IGX, and the AUSM card of the MGX 8850 Release 1. Other Cisco ATM platforms and other ATM manufacturers' equipment have proven to be compatible.

Line Interfaces for the AXSM Cards

The AXSM cards supported in this relase can provide the following types of line interfaces:

•T3/E3

8 ports per back card, 2 back cards per double height slot

G.703/Accunet Conformance

•OC3c/STM1

G.703/GR-253 Conformance

8 optical ports per back card, 2 back cards per double height slot

MMF, SMF intermediate and long reach

4 port Electrical back card

•OC12c/STM4

G.703/GR-253 Conformance

2 optical ports per back card, 2 back cards per double height slot

SMF intermediate and long reach

•OC48c/STM16

G.703/GR-253 Conformance

Single optical port back card, one back card per double height slot

SMF Short, long and extra-long reach

ATM Layer Information

The AXSM cards supported in this relase provide the following ATM features:

•Usage policing supported on all interfaces except OC48c/STM16

•T3 interfaces support both PLCP and direct cell mapping

•64 Logical interfaces — ports, trunks, or virtual trunks (future)

•16 Class of Service queues for each class of service

•Supports independent queues for each ATM class of service

Network Management Features

The AXSM cards supported in this relase provide the following network management features:

•OAM functionality per ITU-T I.610

•Fault management — AIS/RDI at F4 and F5 flow

•User selectable continuity checking at connection endpoints

•Loopback diagnostics

•Automatic alarm generation and propagation for interface failures

The AXSM card offers a complete ATM feature set and allows the MGX 8850 to scale to the core of service provider networks from the T3/E3 edge to the OC48c core. Full line rate is achieved through the use of the serial line traces on the MGX 8850 platform. The entirely standards-based design and connection protocols enable installation into any existing network, as well as building new ATM infrastructures.

PXM45 Cards

The PXM45 card is a 45-Gbps processor switch module. The architecture of the PXM45 card contains the CellBus fabric that is used in the current PXM-1 card, but adds the functionality of a 45-Gbps crosspoint switching capacity. This allows for the use of the serial line broadband cards (AXSM) in the MGX 8850. The PXM45 card provides a Stratum3 central clocking circuit conforming to GR-1244 and G.813 specifications. This is an improvement over the Stratum4-based PXM-1 design.

Reliability, Availability and Serviceability Features

The PXM45 card is designed to operate with another PXM45 card in a redundant configuration. There are two dedicated slots in the MGX 8850 (double height slots 7 and 8) that house the PXM45 card. Highlights of the reliability, availability and serviceability (RAS) features are listed below:

•Switchover from active to standby is designed to result in no cell loss with the exception of cells that are physically on the fabric at the time of the swap.

•In-band arbitration/grant mechanism ensures that service module failure does not stop traffic flow

•Hardware design ensures that if one or both hard disks fail, the cards will still pass traffic with no interruption, although provisioning could be suspended.

•MTBF Goal is calculated using a 99.9999% availability model which assumes two PXM45 cards in a system. This was calculated at greater than 100,000 hours.

Software Compatibility

This section describes the software and SNMP MIBs that are provided with Release 2.0.14.

Compatibility Matrix

The following compatibility matrix lists the software that is compatible for use in a switch running Release 2.0.14 software.

Board Pair	Boot Software	Minimum Boot Software	Runtime Software	Latest Software Version	Minimum Software Version
PXM45, PXM45/B	pxm45_002.000.014.000_bt.fw	2.0.14	pxm45_002.000.014.004_mgx.fw	2.0.14	2.0.14
AXSM-1-2488	axsm_002.000.014.000_bt.fw	2.0.14	axsm_002.000.014.004.fw	2.0.14	2.0.14
AXSM-16-155
AXSM-4-622
AXSM-16-T3/E3

Cisco MGX 8850 Release 2.0.14 interoperates with CWM 10.4.

Cisco MGX 8850 Release 2.0.14 supports feeder connections from Cisco MGX 8850 Release 1.1.32. Please see the 1.1.32 Release Notes for feeder feature issues.

Cisco MGX 8850 Release 2.0.14 operates with CiscoView 5.2 (package 4.43).

Release 2.0.14 System Content

The following software files are supplied with the 2.0.14 release:

•Boot software

–axsm_002.000.014.000_bt.fw

–pxm45_002.000.014.000_bt.fw

•Runtime software

–axsm_002.000.014.004.fw

–pxm45_002.000.014.004_mgx.fw

Additional Deliverables for Release 2.0.14

The SNMP MIB for this release is mibs2014.

Upgrading to a New Software Release

This section contains installation and upgrade instructions. For complete details, refer to the MGX 8850 Switch Software Configuration Guide, part 78-12629-01, which describes the installation of software Release 2.0.12 and higher.

---

Tips Before upgrading, turn off PXM45 online diagnostics. There was a problem (CSCdt46582) where the AXSM card reset during a switchcc. This problem has been fixed with this release, Release 2.0.14.

---

---

Note In this release, you can upgrade the boot or runtime software on only one AXSM card at a time. (See CSCdt51884) For example, you cannot start a burnboot command on one AXSM card if the burnboot command is still operating on another AXSM card.

---

When upgrading your node, upgrade the software in the following order:

---

Step 1 PXM45 boot software

Step 2 PXM45 runtime software

Step 3 AXSM boot software

Step 4 AXSM runtime software

---

The following sections describe how to upgrade PXM45 and AXSM cards.

Upgrading PXM45 Boot and Runtime Images from 2.0.12/2.0.13 to 2.0.14

The following procedure is for redundant PXM45 cards.

---

Step 1 Copy files to the switch.

Step 2 On the standby card, type sh to go to the shellconn.

Step 3 Issue the sysBackupBoot command. This will reboot the standby card

Step 4 Hit return when prompted to do so to stop auto-boot, then issue the command sysPxmRemove().

Step 5 Issue the sysFlashBootBurn <"filename"> command, where filename includes the full path.

sysFlashBootBurn "C:FW/pxm45_002.000.014.000_bt.fw"

- enter "y" to confirm

Step 6 Reset the standby card by issuing the reboot command. Wait until the standby card goes to the Standby/Active state.

Step 7 Enter the switchcc command. When the former active card comes up standby, upgrade its boot code by following steps 2 - 6 above.

Step 8 Use the loadrev command to load the Release 2.0.14 software on the standby card (this command is executed on the active PXM45 card):

loadrev <slot number> <version>

For example: loadrev 7 2.0(14.4)

Step 9 After the standby card comes back up with the new image in the Standby/Active state, use the runrev command to load the Release 2.0.14 software on the active card. This command will bring your original standby card to active state.

runrev <slot number> <version>

For example: runrev 8 2.0(14.4)

Step 10 After the redundant card comes up in the Standby/Active state, issue the command commitrev to commit your node to the current release. Once commitrev is issued, abortrev is no longer valid. Note, you should issue the commitrev before provisioning any more connections.

commitrev <slot number> <version>

For example: commitrev 8 2.0(14.4)

---

The following procedure is for non-redundant PXM45 cards.

---

Step 1 Copy files to the switch.

Step 2 On the PXM45 card, type sh to go to the shellconn.

Step 3 Issue the sysBackupBoot command. This will reboot the standby card

Step 4 Hit return when prompted to do so to stop auto-boot, then issue the command sysPxmRemove().

Step 5 Issue the sysFlashBootBurn <"filename"> command, where filename includes the full path.

sysFlashBootBurn "C:FW/pxm45_002.000.014.000_bt.fw"

- enter "y" to confirm

Step 6 Reset the card by issuing the reboot command. Wait until the card goes to the Active state.

Step 7 Use the loadrev, runrev, and commitrev commands to load the Release 2.0.14 software on the card.Once commitrev is issued, abortrev is no longer valid. Note, you should issue the commitrev before provisioning any more connections

loadrev 7 2.0(14.4)

runrev 7 2.0(14.4) 

commitrev 7 2.0(14.4)

---

Upgrading AXSM Boot and Runtime Images from 2.0.12/2.0.13 to 2.0.14

The following procedure is for redundant AXSM cards.

---

Step 1 Copy files to the switch.

Step 2 To upgrade the AXSM boot code, issue the burnboot command. For example:

burnboot <AXSM slot> 2.0(14)

Step 3 To upgrade redundant AXSM cards with the new runtime image, issue the loadrev command for the standby card.

loadrev <slot number> <version>

For example: loadrev <AXSM slot> 2.0(14.4)

Step 4 After the standby AXSM card comes back up in standby mode, issue the runrev command for the active card

runrev <slot number> <version>

For example: runrev <AXSM slot> 2.0(14.4)

Step 5 After the AXSM card comes back up in standby mode, issue the commitrev command for the AXSM cards.

For example: commitrev <AXSM slot> 2.0(14.4)

Repeat these steps for all redundant AXSM cards.

---

The following procedure is for non-redundant AXSM cards.

---

Step 1 Copy files to the switch.

Step 2 To upgrade the AXSM boot code, issue the burnboot command. For example:

burnboot <AXSM slot> 2.0(14)

Step 3 To upgrade non-redundant AXSM cards with the new runtime image, issue the loadrev, runrev and commitrev commands for each AXSM card.

For example:

loadrev <AXSM slot> 2.0(14.4)

runrev <AXSM slot> 2.0(14.4) 

commitrev <AXSM slot> 2.0(14.4)

Repeat these steps for all non-redundant AXSM cards.

---

New and Changed Information

This section describes new and changed commands in release 2.0.14.

New CLI Commands

The following new CLI commands have been added to 2.0.14:

•dsppathtracenode, which displays the configuration created with pathtracenode

•dsppathtraceport, which displays the configuration created with pathtraceport

•dsppathtraceie, which displays the configuration created with pathtraceie

Changed CLI Commands

The following sections describe CLI commands that have changed in this release.

addcon

The addcon error message that appears when provisioning an SPVC to use a previously configured (duplicate) vpi and vci has been changed from "ERROR: No Such Connection endpoint present" to "ERROR: Specified vpi/vci not available."

clrxbaralms

The clrxbaralms command has been removed. It is a duplicate of clrxbaralm.

dspalm

The dspalm command has been modified to display an additional row of alarm information. For example:

APS Alarm State: Major 

The Alarm State will be same as that shown for dsplns. For non-APS lines, the alarm state is "N/A" The rest of the Alarm values shown apply to the 'Active Line'.

dspalms

The display for the dspalms commands is similar dspalm.

dspapsln

The dspapsln command needs to be entered with both the WLineID and the PLineId. The 'Alarm' shown is not an integrated alarm but is for the LineId that was entered. The 'Alarm' will now show the following are the alarm levels:

•SF-L : signal fail low

•SF-H : Signal fail High

•SD-L : signal degrade low

•SD-H : signal degrade High

•PSBF : Protection Switch Byte Failure

•MIS : Directional mismatch, Architure mismatch, or Channel mismatch (Note that although this is configuration mismatch. APS should still function properly)

•OK : No Alarm

The Alarm states shown are independent of the APS line 'cross.'

---

Note During an AXSM card switch over, there might be a brief period during which MIS is reported. This means the APS operation has gone to 1+1 unidirection mode temporarily.

---

dspapslns

The dspapslns command previously reported two alarm states: OK and ALM. This command now shows the same alarm levels as the updated dspapsln command. The alarms shown are independent of the APS line 'cross.'

dspln

The dspln command displays an 'Alarm' column that shows the integrated alarm status for the APS line pair. It only shows line level alarms. The possible levels are:

•Critical -- If Active line is in Alarm

•Major -- If non-active line is in Alarm

•None -- If both lines are free of line level alarms

•N/A -- If there is no APS configuration on this line

dsplns

The dsplns command displays ths same alarm status as dspln.

dspxbaralms

The dspxbaralms command has been removed. It is a duplicate of dspxbaralm.

saveallcnf

The saveallcnf command response has changed to the following:

Unknown.7.PXM.a > saveallcnf -v

The 'saveallcnf' command can be time-consuming. The shelf 

must not provision new circuits while this command is running.

Do not run this command unless the shelf configuration is stable 

or you risk corrupting the saved configuration file.

ATTENTION PLEASE NOTE: 

The save command will only store the 

2 most recent saved files in C:/CNF directory. 

If you have 2 or more files already saved in C:/CNF, 

the older ones will be deleted by the current save, 

keeping the 2 most recent.

saveallcnf: Do you want to proceed (Yes/No)? y

New Features in Release 2.0.14

There are no new features in this release.

Obsoleted Features in Release 2.0.14:

No features are obsoleted in this release.

Installation Notes and Cautions

•If any AXSM cards remain in INIT state and the PXM45 standby card is reset, the PXM45 standby card will not transit back to standby. This is a DB server limitation.

•(CSCdt05425) If the active AXSM has some non-default interface policy configured, then the standby card might not be in sync with the active card. This will also affect the upgrade of the cards to the new version. The user will have to follow the procedure for a non-graceful upgrade for the new version.

If the default interface policy is being used, then the redundancy/graceful upgrade is possible.

The redundancy/upgrade will also work if the interface policy is configured for 3 or fewer ports (as the interface policy for 4 or more ports does not get synced to standby).

Note that AXSM Redundancy works after the customer has upgraded to 2.0.12. The AXSM Redundancy problem only exists in versions 2.010 and 2.0.11.

•When removing AXSM redundancy (delred), you must remove the Y-red cables before issuing the delred command.

•On feeder trunks, tstdelay works only when the OAM cells are disabled on the segment endpoints. To disable OAM cells, use the following procedure:

---

Step 1 dpnport <portid>

Step 2 cnfpnportsig <portid> -cntlvc ip

Step 3 cnfoamsegep <portid> no

Step 4 uppnport <portid>

---

•(CSCdt09949) Currently the CLI command addchanloop does not store the connection loop state as persistent data. As a result, this loop (ingress and egress) state of a connection will be lost after the following operations:

–resetcd

–resetsys

–dncon followed by upcon

–controller resync (dnport followed by upport)

–switchredcd

–reroute (dnport)

•PNNI default minimum VCI is 35 unless changed explicitly. The reason for the default is to reserve VCI=32-34 for other control purposes such as MPLS and NCDP. For users who would like to add an MPLS controller in future releases of the Cisco MGX 8850 switch, it is highly recommend to set the minimum vci value to be 35 or more for all partitions on the port where the MPLS partition will be added. By doing so, the TDP signaling VC for MPLS will be established automatically on 0/32.

•By default, 900 cps and 543 cps will be reserved for the SSCOP and PNNI signalling VCs, respectively, even when you disable SSCOP and PNNI. These values are configurable through the cnfpnctlvc command.

•The database stores the backplane serial number and back card serial numbers. Therefore if cards are moved from one node to another, the console will display "SHM Alert!! Alert!!." In this situation follow these steps:

---

Step 1 Enter shmFailDisplay. A display table will show that BRAM is not native.

Step 2 Enter shmFailRecoveryHelp. This will indicate that to "Ignore Nativity and Rebuild from Disk" the command to use is shmRecoverIgRblDisk.

Step 3 Enter shmRecoverIgRbldDisk.

---

•Do not execute delcontroller when connections or ports still exist. If you do enter delcontroller and later want to recover the connections, you must re-added the controller using addcontroller and reset the AXSM cards or the entire node (otherwise ports remain in provisioning state). There is now a warning about the impact of the command when there are existing connections or ports.

•(CSCds70478) Currently, Humvee error reporting is turned off for the AXSM cards. They are however logged.

•Analysis of the code has identified a situation which has a low probability of occurring and in fact has not been encountered in any test scenarios to date. This caution and associated workaround is provided as a precautionary measure.

When the link bandwidth for SPVC connections is reaching full capacity, thus minimal bandwidth is available for new SPVC connections, there is a condition which can be encountered where, the initial software check believes there is sufficient bandwidth for the new SPVC connection; however, the final software confirmation for available bandwidth may be rejected because there is no bandwidth available. If this problem occurs, the system will recover when the PNNI updates are refreshed. (This will happen at the default time of 30 minutes.) The user can recover from this problem by making the administrative weight of that link very high to reduce the usage of that link.

•To replace one type of AXSM front card with another type, all connections, partitions, and ports must be deleted, and all lines must be brought down. If an AXSM card fails, the same type of AXSM card must be installed in that slot so that communications can be resumed or so that the configuration can be changed to prepare for a new card type.

Limitations and Restrictions

The following are known limitations or restrictions for this release:

•The maximum number of logical interfaces (physical trunks, virtual trunks, logical ports) supported in Release 2.0 baseline (2.0.10-2.0.14) with PXM45 and PXM45/B is 99.

In future releases of MGX 8850 with PXM45/B, the maximum number of logical interfaces supported will be 3199. The PXM45 module will always support a maximum of 99 logical interfaces.

The maximum number of signalling interfaces in Release 2.0 and future releases of MGX 8850 is 99. Signalling interfaces are those running a protocol such as PNNI, IISP, AINI or supporting SVC/SVP.

Interfaces on standby or redundant cards are not counted.

•APS working line must be 1 line lower than the protection line. For example, 1 is the working link and 2 is the protection line. Having 1 as the protection and 2 as the working line is not allowed.

•If the destination address is reachable through both IISP and PNNI links on the same node, ABR connections will not route. The current routing algorithm will always choose IISP links over PNNI links because it is local. Since IISP does not support ABR connections, the connection setup will fail.

•A port or card SCT can be changed while connections are present in this release. However, if the SCT change affects active connections, those connections will be rerouted.

•(CSCds41609) Connection statistics at CLI and Bucket level is not available in AXSM-1-2488 cards. However, connection debug statistics are available in all types of cards.

•When CWM is use to manage the network, the IP address 10.0.x.x cannot be used as the LAN address (lnPci) for the switch.

•If you would like to add an MPLS partition on a port where other partitions have already been added and the minimum vci value is 32, you have two options:

–After the MPLS controller is added, explicitly add the TDP sig vc using a vpi/vci pair within its partition's resource range.

–Do a dnport and cnfpart to move the minimum vci to 35 for all partitions on the port.

•(CSCdr15911) Changing or reseating an AXSM OC48 back card several times may sometimes cause the front card to reset and interrupt service. The PhyTask also gets suspended. To avoid this problem, try not to reseat the back card too often. If the front card does not start when the switch power is turned on, try to reseat the front and back card to bring up the system.

Important Notes

The following sections provide additional information on BITS clock source configuration, APS operation in this release, and recommendations for setting the control VC parameters.

BITS Clock Source Configuration

The Cisco MGX 8850 Software Configuration Guide incorrectly lists four port numbers for the two BITS clock ports on the back of the PXM-UI-S3 card. During configuration (using the cnfclksrc command), the correct port number to use for the upper clock port is 35. The correct port number for the lower clock port is 36.

APS Management Information

The following tips apply to the use of the dspapsbkplane command and the APS connector which is sometimes call a back plane. The APS connector must be installed to enable intercard APS.

•The dspapsbkplane command shows whether the APS connector is plugged in properly. It should be used only when the standby card is in Ready state. When the standby card is booting or fails, intercard APS cannot work properly and this command displays "NOT ENGAGED."

•APS must be configured on a line pair before the dspapsbkplane command can display the APS connector status. If APS is not configured on a line, the dspapsbkplane command displays the message "Aps Line Pair does not exist."

•The dspapsbkplane ccommand needs to be executed on both the active & standby cards to ensure that APS connector is engaged properly. This command can show different values for each of the two cards, which indicates the APS connector is seated properly on one card but not on the other.

•The APS connector status is the same for all lines in a single bay. This is because the APS connector interconnects two back cards within the same bay. To check the APS status for an AXSM card that hosts ports in the upper and lower bays, you must enter the dspapsbkplane command twice, once for a line in each bay.

---

Caution When using intercard APS, ensure the APS connector is correctly installed. Refer to the "APS Backplane" section in Chapter 4 of the "Cisco MGX 8850 Hardware Installation Guide." This guide is part number 78-10351-04, and can be ordered from Cisco Marketplace or downloaded from http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/20x/hig/index.htm. After you install the assembly, verify that the APS connector is properly installed by using the new CLI command dspapsbkplane.

---

---

Note (CSCdu19732) If there are APS configurations on a card and some lines are disconnected, avoid performing switchredcd, front card removal, or back card removal. Before removing an active front card or back card, which results in a card switch over, switch cards with the switchredcd command.

---

Recommendations

Cisco Systems recommends you apply the default values for PCR, SCR, etc. to the Control VC. If the values are decreased to a low value, there is a chance that the control VC (SSCOP or PNNI) will not come up. Note that you must use the SCT files released with 2.0.11 (number 2 and 3, which are included in the 2.0.14 release) for the control VC feature.

Documentation Correction — Feeder Configuration

In the Cisco MGX 8850 Software Configuration Guide, Chapter 4, Step 2 in the Feeder Configuration Quickstart incorrectly states that an IP address must be entered with the cnfpnportsig command to support CWM management. The correct syntax for the command is:

pop20two.7.PXM.a > cnfpnportsig <portid> -cntlvc ip

The ip component of the command should be entered as shown above. Do not replace this component with an IP address.

Known Anomalies in Release 2.0.14

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

Bug ID	Description
S1 Bugs
CSCdt27029	Symptom: AXSM switch over and PXM45 switch overs when AXSM cards inserted. Condition: AXSM cards were reseated. Workaround: UNKNOWN
CSCdt28983	Symptom: APS switching does not meet Signal Degrade Threshold requirements for switching. Condition: Errors were injected at the threshold levels specified for Signal Degrade conditions to be reported. Workaround: UNKNOWN
CSCdt54958	Symptom: OC12 p-p jitter amplitude exceeded the 0.10 UI pp. Condition: Unknown Workaround: None
CSCdt76379	Symptom: Connections went into conditioning state after a switchcc was executed. Condition: switchcc was executed after PXM45s were replaced. Workaround: UNKNOWN
CSCdt77590	Symptom: Large number of connections went into mismatch due to cross-commit failure. Condition: switchredcd was executed. Workaround: UNKNOWN
CSCdt79310	Symptom: dsppnportrsrc command for the port shows MinTx Cellrate and Min Tx Cell rate same as the Max Tx Cell rate for each service category. Condition: When partition minimum bandwidth is configured the same as the partitions maximum bandwidth and when the interface policy is not applied in the service module (AXSM). Workaround: cnfpnportcac for the port again will fix it.
CSCdt80857	Symptom: Failed to cc to active AXSM card on a redundant AXSM pair. Condition: Not known Workaround: Reset the card.
CSCdu12856	Symptom: 1000+ SPVCs failed during a 2.0.12-2.1.00 upgrade. Condition: burnboot procedure was executed on standby PXM45 and switchcc was then executed. Workaround: UNKNOWN
CSCdu15569	Symptom: APS working lines and protection lines in alarm. Condition: Removing the front card. Workaround: None
CSCdu16640	Symptom: Traffic loss, PNNI links resetting. Condition: Problem is caused by hardware failure. Workaround: switchcc may help if load sharing is not enabled.
S2 BUGS
CSCdr89521	Symptom: dspcon shows routing cost = 0. Condition: This will happen after swithcc on connections that are not rerouted. Workaround: Do a dncon or rrtcon.
CSCdr91301	Symptom: Upon AXSM reset, ILMI on some ports on the said AXSM may go into "disabled" state. Condition: This is a very rare situation and has been observed twice in the past six months of testing. Workaround: Bring down the port and then bring it back up.
CSCds24362	Symptoms: Occasionally, when bringing down a UNI port (dnport) on AXSM followed by upport, some VSIErr are displayed on the AXSM console. Conditions: (1) In a three-node (NODE_EP1, NODE_VIA, NODE_EP2) network, nodes are connected linearly (e.g., two trunks connecting NODE_EP1 and NODE_VIA, three trunks connecting NODE_VIA and NODE_EP2). (2) A connection is established from NODE_EP1 to NODE_EP2. (3) dnport on the UNI on NODE_EP1. (4) upport on the UNI on NODE_EP1. At this time, some vsierr might be displayed on the AXSM console. Workaround: None.
CSCds74270	Symptom: When performing Bulk Sync (when standby AXSM first arrives), some VsiErrs were observed on the active AXSM and the standby AXSM might not have all the connections. Conditions: This happens when intraslave connections (between two ports) were added on the AXSM. If one of the ports was admin downed followed by inserting or resetting the standby AXSM. WorkAround: Initiate another Bulk Sync (by resetting the standby AXSM) after the port is upped.
CSCdt05371	Symptom: Traps were not generated for hard disk failure during fault insertion testing. Condition: Hard disk failure was simulated on modified PXM45s. Workaround: UNKNOWN
CSCdt05378	Symptom: Switchover to faulty standby PXM45 allowed during fault insertion testing. Condition: Hard disk failure was simulated on the standby PXM45. Workaround: UNKNOWN
CSCdt05383	Symptom: PXM45 switchover did not occur when hard disk failure simulated on active PXM45 during fault insertion testing. Condition: Hard disk failure was simulated on active PXM45. Workaround: UNKNOWN
CSCdt05385	Symptom: No alarms reported when hard disk failure on active PXM45. Condition: Hard disk failure was simulated on active PXM45. Workaround: UNKNOWN
CSCdt05387	Symptom: Hexadecimal characters appeared on telnet session and access to system via telnet and console port access was then lost. Condition: Hard disk failure was simulated on active PXM45. Workaround: UNKNOWN
CSCdt06427	Symptom: OC12 AXSM card does not declare receiving incoming RDI-P alarm. Condition: When OC12 line is receiving RDI-P. Workaround: No workaround.
CSCdt09931	Symptom: After switchcc, newly active PXM45 goes onto internal oscillator. Condition: External bits input is used for both primary and secondary clock sources. Workaround: UNKNOWN
CSCdt09949	Symptom: Channel loops are randomly being knocked down. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt13133	Symptom: Device driver core dumps recorded on PXM45. Condition: Nodes had experienced power outages the previous day, and had to have their PXM45s reseated as part of the recovery process. Workaround: UNKNOWN
CSCdt14045	Symptom: After AXSM card reset, data transfer stopped and LCNs could not be accessed via tstdelay and dspvsicons commands. Condition: Spontaneous AXSM card reset. Workaround: UNKNOWN
CSCdt19813	Symptom: Software error reset core dumps observed on PXM45. Condition: Cyclic switchcc commands and fault insertion tests were being performed. Workaround: UNKNOWN
CSCdt20397	Symptom: PXM45 failed its nativity check. Condition: Can't give up mastership Fault Insertion test was being conducted. Workaround: UNKNOWN
CSCdt20435	Symptom: PXM45 failed its nativity check. Condition: Can't give up mastership Fault Insertion test was being conducted. Workaround: UNKNOWN
CSCdt21157	Symptom: SPVC did not connect even when crankback occurred. Condition: Crankback occurred after a connect was issued by the destination node, and a VPI mismatch condition was detected by the originating node. Workaround: UNKNOWN
CSCdt25070	Symptom: Node alarms and traps are not generated on High Speed serial link errors. Condition: High Speed serial link error injected during Fault Insertion Testing. Workaround: UNKNOWN
CSCdt29629	Symptom: APS switching is blocked for 1+ minute after alarm cleared. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt30131	Symptom: Incoming RDI-L, RDI-P not declared and cleared within 100usec. Condition: Incoming AIS-L. Workaround: UNKNOWN
CSCdt30132	Symptom: RDI-L and RDI-P clear times are greater than 100usec. Condition: LOS is cleared. Workaround: UNKNOWN
CSCdt30133	Symptom: RDI-L and RDI-P clear times are greater than 100usec. Condition: LOF is present and then cleared. Workaround: UNKNOWN
CSCdt30134	Symptom: LOS alarm condition is displayed during LOF. Condition: dspalms and dspalmcnt show LOS condition. Workaround: UNKNOWN
CSCdt30135	Symptom: OC12 line code violations do not increment. Condition: Incoming B2 errors. Workaround: UNKNOWN
CSCdt30137	Symptom: OC12 incorrectly generates RDI-L and RDI-P. Condition: B2 errors are received. Workaround: UNKNOWN
CSCdt30140	Symptom: RDI-L and RDI-P clear times after LOF cleared greater than 100usec. Condition: LOF condition has been cleared. Workaround: UNKNOWN
CSCdt30142	Symptom: OS reports Line AIS, Section LOS, LOF and Path RDI. Condition: Incoming LOF condition. Workaround: UNKNOWN
CSCdt33442	Symptom: AXSM OC12 does not report LOCD alarm. Condition: When cell delineation is lost on incoming OC12 SONET signal. Workaround: No workaround.
CSCdt38180	Symptom: Trunk port counters resetting while channel counters overflowing. Condition: It seems that the "Arrival of CLP0 Cells" counters of the channel count are saturating at 32-bit level and giving that reading. But the trunk port counters may be resetting at some point which explains why the trunk port numbers are less than the channel counter numbers. Workaround: UNKNOWN
CSCdt38630	Symptom: Configure an intercard APS with the working line index on the active card and the protection line index on the standby card. Let us have the working line as the active line to begin with. Now perform a switchapsln so that the protection line is active. At this point, the active card is working off the protection line (which is physically connected to the standby's back card) and vice versa. Now, pull out the working line (which is the line going to the back card of the active AXSM). Notice that the standby AXSM's LED goes RED. This is because the standby card is "tuned" to the working line. However, this is confusing to the user because it gives a false impression that the line connected to the standby AXSM has failed. Condition: As explained above. Workaround: The user needs to be aware that in an intercard APS case where the active AXSM is working off a line which is physically connected to the standby's back card and vice versa, the LED reports may be misleading.
CSCdt39409	Symptom: AXSM card is in failed state. Condition: Downloading of AXSM image to AXSM card is not successful. Workaround: None
CSCdt43267	Symptom: Active PXM45 card in slot 7 was not responding and showed a major alarm with red LED. Removed the card and the standby card in slot 8 became active. Condition: Unknown Workaround: Unknown
CSCdt44635	Symptom: Watchdog timeout reset core dump observed on PXM45. Condition: Customer was executing Fault Insertion testing. Workaround: UNKNOWN
CSCdt45669	Symptom: PNNI neighbor PTSE database synchronization and other problems after flash failure test during Fault Insertion testing. Condition: Flash failure test was being conducted. Workaround: UNKNOWN
CSCdt47634	Symptom: Statistics files are being generated on the switch, though statistics collection is disabled on CWM. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt49664	Symptom: Device driver error core dumps. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt51104	Symptom: Burning backup boot to PXM45 flash causes the system to hang when the flash device is not working. Condition: Bad flash device causes the system to hang while the flash is being programmed. Workaround: none
CSCdt51174	Symptom: Card stuck in programming due to momentary flash failure. Condition: Inserted flash failure by changing the switch 2-8 to ON position. Workaround: Unknown
CSCdt53631	Symptom: LOF criteria is not met per R5-225, for AXSM OC12 interface. Condition: OOF condition is cleared at the presence of three consecutive error free patterns rather than two. Workaround: UNKNOWN
CSCdt53844	Symptom: PXM45 did not switchover and all cards went into a continuous reset, during Fault Insertion testing. Condition: QE0 failure test was being conducted. Workaround: UNKNOWN
CSCdt53886	Symptom: Reset type and reset reason observed by user did not match Cisco report. Condition: PCI bus error Fault Insertion tests were being conducted. Workaround: UNKNOWN
CSCdt53888	Symptom: No indication for PCI bus error on active PXM45. Condition: PCI bus error fault insertion testing was being conducted. Workaround: UNKNOWN
CSCdt53893	Symptom: Alarm reporting different for PCI bus errors on standby vs. active PXM45. Condition: PCI bus error Fault Insertion Testing was being conducted. Workaround: UNKNOWN
CSCdt53957	Symptom: Changing IP address of node caused standby PXM45's ethernet interface to go active. Condition: Single IP address scheme is being used. Workaround: UNKNOWN
CSCdt55216	Symptom: Loss of activity messages are logged in the event log for the Priority 1 clock source when secondary clock source is configured. Condition: Secondary clock source is configured; both primary and secondary clock sources are external BITS 1 and 2 inputs. Workaround: UNKNOWN
CSCdt56749	Symptom: Master end of routed connections shows OK, but slave end shows Condn. Condition: N/A Workaround: None
CSCdt58810	Symptom: EPD/PPD value defaulted to disable in SCTs. Condition: None Workaround: Create new SCT via CWM with EPD/PDD enabled.
CSCdt60594	Symptom: QE48 SAR error messages and memory block assignment messages observed in error and event log files. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt60669	Symptom: Node rebuild occurred when switchcc was executed during Fault Insertion testing. Condition: QE1 failure test was being conducted. Workaround: UNKNOWN
CSCdt60672	Symptom: QE1 failure not recorded during Fault Insertion Testing. Condition: QE1 failure testing was being done. Workaround: UNKNOWN
CSCdt60673	Symptom: Faulty card did not go into continuous reset during QE1 failure. Condition: QE1 failure testing was being undertaken. Workaround: UNKNOWN
CSCdt60675	Symptom: PXM45 did not switchover on LAN port failure. Condition: Fault Insertion Testing was being conducted. Workaround: UNKNOWN
CSCdt60679	Symptom: No indications presented to user when LAN port failure on standby PXM45. Condition: Fault Insertion Testing was being conducted. Workaround: UNKNOWN
CSCdt60681	Symptom: No access to node via LAN. Conditions: LAN port has hardware failure. Driver does not detect and request processor switch over. Workaround: None. Could use IP Connectivity interface for management as the primary. If not, a manual switchover or rebuild is required.
CSCdt60692	Symptom: No indication provided via event log or alarm reporting for crossbar failure. Condition: Crossbar Failure Insertion tests were being conducted. Workaround: UNKNOWN
CSCdt60693	Symptom: Serial Link Path failure (Severity 7) is not logged into the event log. Condition: Serial Link Path Failure Insertion tests were being conducted. Workaround: UNKNOWN
CSCdt60694	Symptom: Inconsistent alarm reporting in case of Serial Link Path Failure (should be Major). Condition: Serial Link Path Failure Insertion tests were being conducted. Workaround: UNKNOWN
CSCdt60696	Symptom: Faulty card did not go into continuous reset when encountering parity error on internal Utopia bus on the Active PXM45. Condition: Utopia bus failure testing was being undertaken on the PXM45. Workaround: UNKNOWN
CSCdt61546	Symptom: Faulty card did not go into continuous reset when encountering parity error on internal Utopia bus on the active PXM45. Condition: Utopia bus failure testing was being undertaken on the PXM45. Workaround: UNKNOWN
CSCdt61572	Symptom: LAN port spurious interrupt insertion not being logged in the event log. Condition: LAN port spurious interrupt insertion tests were being conducted. Workaround: UNKNOWN
CSCdt61581	Symptom: Faulty card did not go into continuous reset during Utopia bus parity error failure. Condition: Utopia bus parity error fault insertion was being undertaken. Workaround: UNKNOWN
CSCdt61599	Symptom: Different level of alarm reported by dspxbaralm and dspswalms. Condition: When there is crossbar errors. Workaround: None.
CSCdt61616	Symptom: When dspswalms is used, crossbar fabric alarms are displayed with slot numbers, but they should not be associated with any slot number. Condition: Whenever dspswalms is used, the above problem is seen. Workaround: none
CSCdt63170	Symptom: Resource allocation after the AXSM gets reset. Condition: Resource usage on the endpoint of the NNI link is different. Workaround: None
CSCdt64155	Symptom: During AXSM card switchover, when a line on the previous card is in alarm, but on the new active has the alarm cleared, then CWM does not get updated with the new 'clear' alarm state. Condition: During AXSM card switchover, when a line on the previous card is in alarm, but on the new active has the alarm cleared. Workaround: NONE
CSCdt66910	Symptom: When tertiary is uploading statistics files from AXSMs, some files are missed as they don't exist on the AXSM anymore. Condition: This happens after the maximum number of files have been accumulated on the AXSM. Since all files (not currently being uploaded and created since 15mins) are deleted. Workaround: UNKNOWN
CSCdt67109	Symptom: Wrong value of summary address gets assigned. Condition: 1)When ever the length of PNNI summary address (entered with the command) is less than the length provided in the same command, the wrong value gets entered. 2)When length of summary address and mentioned length are same but length is an odd multiple of 4 (e.g 12). Workaround: !) Keep the length of the PNNI summary address (entered with the command) larger than the length mentioned in the same command. 2) Keep the length as multiple of 8 and keep the length of the PNNI summary address (entered with the command) same as the length mentioned in the same command.
CSCdt67113	Symptom: Wrong value of summary address gets assigned. Condition: 1)When ever the length of PNNI summary addr(entered with the command) is less than the length provided in the same command, the wrong value gets entered. 2)When length of summary address and mentioned length are the same but the length is an odd multiple of 4 (e.g 12). Workaround: !) Keep the length of the PNNI summary address (entered with the command) larger than the length mentioned in the same command. 2) Keep the length as multiple of 8 and keep the length of the PNNI summary address (entered with the command) the same as the length mentioned in the same command.
CSCdt71637	Symptom: Card reset with software reset reason. (Core dump happened.) Condition: SnmpSA task got suspended causing card to reset. Workaround: None
CSCdt74168	Symptom: Syntax information for routeAdd and routeDelete are missing. Condition: Just execute any of the commands. Workaround: Not known
CSCdt78006	Symptom: Connections temporarily went into mismatch condition. Condition: switchcc was executed. Workaround: UNKNOWN
CSCdt80060	Symptom: Connections remains in temporary failure after pulling out and plugging in the cables of PNNI link and PNNI link recovered. Conditions: unknown. Workaround: unknown.
CSCdt83432	Symptom: PNNI link on OC48 AXSM card stayed in oneWayInside status. Conditions: Unknown Workaround: NONE
CSCdt87101	Symptoms: The call does not go through with exclusive VPCI and any VCI set in a setup from an NNI link. If only cnfpnportrange is used to configure max and min VPI to 0. Condition: The call goes through if the max and min VPI is configured to 0 on the line card but does not go through if done by cnfpnportrange on PXM45. Workaround: Configure max and min vpi on the line card rather than on the controller if the peer NNI node is sending setup with exclusive VPCI and any VCI with VPCI equal to 0.
CSCdt88532	Symptom: APS line went to protect after clearing it under a scenario. Conditions: Change mode when active line is protection line. Workaround: Execute a clear instruction after the cnfapsln command.
CSCdt94483	Symptom: dsppnports shows 3 more DAX connecctions after switchredcd. Condition: This could happen if there are some failed connections before switchredcd. Workaround: None
CSCdt94790	Symptom: CWM didn't receive trap 60901(cwBulkFileCreationStarted) or 60902(cwBulkFileCreationDone) which causes CWM not able to sync up. Conditions: The switch generates excessive traps which cause some lost traps. There is also a bug(CSCds87127) in the switch that traps are not sent when the trap client in the wrong state. Workaround: There is no workaround on the switch. But the node might sync up by doing manual sync up with CWM.
CSCdt97193	Symptom: When the card gets reset, the core may be dumped regardless of the reason the card got reset. This might result in failure of restoreallcnf if the card or system got reset due to restoreallcnf. Condition: The core mask is never initialized on the card and it may have some uninitialized value which triggers core dump unnecessarily. Workaround: Use the following CLI command to check the core dump mask: - core mask Use the following CLI commands to set the core dump to default: - core enable - core mask default This will install the default core dump mask.
CSCdt97273	Symptom: This exhibits a weird symptom by which the working line gets the message sent from the far end. Condition: This can cause an incorrect line pair to be configured when the far end configuration is set. Workaround: Delete and readd the line pair. This has been observed ONLY once.
CSCdu01923	Symptom: dspnni-path command output does not seem to be correct. Condition: This command continues to show a precomputed path that has exhausted LCNs. Workaround: UNKNOWN
CSCdu03161	Symptom: VBR.2 connections for both rt and nrt types are allowing more CLP1 cells than should be. Condition: This could potentially result in network congestion. Workaround: unknown
CSCdu05507	Symptom: SSCOP stayed in reset state for PNNI link. Also ILMI did not come up different port of the same card. Condition: After the changing the cable on the card. Workaround: Not Known
CSCdu06781	Symptom: Back-to-back forced/manual (W->P followed by P->W) APS switch was permitted when the latter external user request is initiated from the remote end. Condition: Check for remote request of equal priority is not in place. Workaround: None
CSCdu07255	Symptom: APS protection line temporarily going into alarm. Condition: Issue the switchredcd command. Workaround: Unknown
CSCdu09353	Symptom: APS Service Switch request propagates to all bays in APS pair. Condition: switchapsln command supplied with service switch set to 1. Workaround: Apply switchapsln command per port instead of service switch.
CSCdu09724	Symptom: Connection commit failure reported on the standby AXSM. Condition: During bulkSync, if controller performs massive deroute or reroute activity on the active AXSM, the connection request forwarded to standby may fail. Workaround: None.
CSCdu10670	Symptom: Doing multiple rrtcon caused pep's fsm timer stop on PXM45. Conditions: Connection stayed in fail status and couldn't be rerouted. Workaround: None
CSCdu10677	Symptom: dspln shows critical alarm, but dspapsln shows OK. Condition: None. Workaround: switchredcd will recover it.
CSCdu10731	Symptom: switchredcd results in line alarm. Condition: switchredcd causes both lines to go into alarm. Workaround: NONE
CSCdu11686	Symptom: APS lines: disconnected the cable on working line, then switchredcd, most of the time, when the standby card came up, both the working and protect lines were in alarm, and pnport/PNNI link were down. Conditions: This is the double fault APS issue, and it interrupts traffic. Workaround: None
CSCdu12278	Symptom: Event log reports IOV buffer allocation error messages. Condition: Large number of reroutes and crankbacks occurred in the network around this time, due to dangler SPVCs and removal of OC48 trunks. Workaround: UNKNOWN
CSCdu13182	Symptom: SPVC state shows "IF FAIL." Condition: In a network with both DSLAM6130 and Cisco MGX 8850, the SPVCs are in "IF FAIL" state when the DSLAM6130 is rebooted. However, they stay in that state even after the DSLAM6130 comes back. Workaround: dnport followed by upport on the interface where the connection failed.
CSCdu13529	Symptom: APS switched protection line to working line. Condition: Issue the switchredcd command or remove and reinstall the back card. Workaround: Unknown
CSCdu14779	Symptom: Standby PXM45 card keeps giving the qcPurgeVc fail error message. Condition: Not Known. Login to standby PXM45 card and message keeps popping out. Workaround: Not Known
CSCdu14812	Symptom: Node gives many card errors during normal operation. Condition: Normal operation. Workaround: N/A
CSCdu14884	Symptom: dsplog on active PXM45 hangs. Condition: dspcderrs indicates tLOGD is hanging on a semapahore. Workaround: UNKNOWN
CSCdu15589	Symptom: After pulling out APS protection line back card, all protection lines go in alarm with signal low failures. Condition: AXSM OC12 secondary front card is active and primary front card is in standby. Working line is active on upper and lower bay back cards. Workaround: Delete and re-add APS lines.
CSCdu15613	Symptom: Traffic is discarded above Peak Cell Rate CLP = 0 instead of tagging. Condition: Traffic is pumped with PCR equals to the PCR CLP=0+1 (Adtech) connection. Workaround: On CBR.3 SVC connection, pump traffic at or below the rate set PCR CLP=0.
CSCdu15972	Symptom: Critical alarm seen on the other end after reinsertion of backcard . Condition: Removal and reinsertion causes critical alarm on the other side. Workaround: None
CSCdu16674	Symptom: After OC48b back card is removed and inserted, port stays in down state. Condition: Line and port are upped, local loopback is turned on, back card is physically removed, and back card is reinserted. Line is up, local loopback is up, port is operationally down. Workaround: Delete and re-add local loopback.
CSCdu17989	Symptom: OC3 intracard APS switch took about 24 seconds to switch from working line to protection line or from protection line to working line by cable failure. Conditions: Same problem happened on intercard to intracard APS lines. This was only seen on OC3 cards. Workaround: Unknown
CSCdu18026	Symptom: Traffic loss during protection to working while standby card is in active is way above standard. Condition: Standby card should be active and create scenario for protection to working switching on OC3 1+ 1. Workaround: N/A
CSCdu19301	Symptom: Connection failing after rerouting. Condition: Ingress CAC failure. Workaround: None
CSCdu19732	Symptom: switchredcd results in line switching. In the case of APS, with the working line removed, a switchredcd would cause the far end to switch back to the working line. Condition: Data loss as a result of switchredcd. Workaround: Do not remove the lines when switching cards.
CSCdu20428	Symptom: VSI master fills PCR(0) instead of PCR(0+1). Condition: Whenever CBR.3 cross commits are commited. Workaround: None
CSCdu20841	Symptom: New SPVC calls fail with a reason of unallocated number. Condition: Create two IISP trunks and then change the configuration to PNNI. The IISP static addresses are not flushed. Workaround: Unknown
CSCdu21330	Symptom: Using CWM, the customer can not see the LAN IP address. Conditon: Unknown Workaround: Unknown
CSCdu21576	Symptom: Under some conditions (during rebuild of the node or card), some of the provisioned connections do not get programmed on the AXSM (possibly because of a problem with the PNNI controller). This would cause a traffic outage on the AXSMs. However, this condition should have been detected at the AXSM and the dspcons should declare "mismatch" on those connections. This functionality was broken under some circumstances. This bug fix is meant to address this problem Condition: Happens usually during a node or card rebuild. Workaround: None.
CSCdu21603	Symptom: AXSMs get reset on enabling online diagnostics. Condition: On issuing a "cnfdiagall enable disable" command, all the standby AXSMs get reset. Workaround: None.
CSCdu23683	Symptom: Load balancing is not done on a 36 Node Mesh. Condition: Unknown: Workaround: Unknown
CSCdu24019	Symptom: Connection in MISMATCH. Condition: Issue switchredcd,then dnpnport, and then uppnport. Workaround: Unknown
S3 BUGS
CSCds11868	Symptom: Active PXM45 in ACTIVE-F state and standby PXM45 keeps getting reset. Conditions: Use DIP switch to inject fault to QE chip on active PXM45 and see standby PXM45 getting reset and active PXM45 in active-f state. Workaround: None Further Problem Description: This is a test on special card with a DIP switch and cannot happen on the field.
CSCds17719	Symptom: No access to node via LAN. Conditions: LAN port has hardware failure. Driver does not detect and request processor switchover. Workaround: None. Could use IP connectivity interface for management as the primary. If not, a manual switchover or rebuild is required.
CSCds27446	Symptoms: When performing SPVC reroute and switchover on the UNI (master side) at the same time, connection delete may fail on the standby. After switchover, if the same connection is recommitted, VSIErr will be observed on the AXSM console. Conditions: (1) In a three-node (NODE_EP1, NODE_VIA, NODE_EP2) network, nodes are connected linearly (e.g., two trunks connecting NODE_EP1 and NODE_VIA, three trunks connecting NODE_VIA and NODE_EP2). (2) A connection is established from NODE_EP1 to NODE_EP2. (3) dnpnport on one of the NNI on NODE_VIA. (4) switchredcd on the UNI (master side of the connection) on NODE_EP1. (5) When everything is rerouted, perform a switchredcd on the same UNI. Sometime later, some VsiErr are observed on the AXSM console. Workaround: Do not perform switchover while rerouting or derouting connections.
CSCds42201	Symptom: Standby PXM45 card is in continuous reset loop, and all AXSM cards in the shelf are either in Failed state or in reset loop. Condition: Injecting a hardware failure on SRAM component of active PXM45 card manually. Workaround: None
CSCds42505	Symptom: No Major alarm is displayed against AXSM card in card alarms when the card is in Failed state. Condition: Injecting a hardware failure on SRAM component of active PXM45 card manually. Workaround: None
CSCds43093	Symptom: switchcc allowed to be executed when the standby PXM45 card has a hardware failure. Condition: Injecting a hardware failure on SRAM component of standby PXM45 card manually. Workaround: Do not execute switchcc.
CSCds43124	Symptom: Standby PXM45 card hardware failure is not reported correctly. Condition: Injecting a hardware failure on SRAM component of standby PXM45 card manually. Workaround: None
CSCds43165	Symptom: Active and standby PXM45 card hardware failure is not reported in the event log. Condition: Injecting a hardware failure on SRAM component of either active or standby PXM45 card manually. Workaround: None
CSCds43554	Symptom: No error log is seen about the BRAM component failure. Condition: Injecting a hardware failure on BRAM component of active PXM45 card manually. Workaround: None
CSCds43560	Symptom: PXM45 card status LED is green, when the card is continuous reset loop. Condition: Injecting a hardware failure on BRAM component of active PXM45 card manually. Workaround: None
CSCds43563	Symptom: Sometimes, dtandby PXM45 card goes to Failed state. Condition: Injecting a hardware failure on SRAM component of dtandby PXM45 card manually. Workaround: None
CSCds67426	Symptoms: Two PXM45 nodes. One end has primary and secondary clock configured (first node) and the other end clocking sources (second node) have been reseated. The first node is up before the second node. The PXM45 resync clocks will get NAK from AXSM card. This will cause clock configuration status to be "not configured." A4A.7.PXM.a > dspclksrc Primary clock type: generic Primary clock source: 6:1.1:1 Primary clock status: not configured Primary clock reason: no clock signal Secondary clock type: generic Secondary clock source: 6:1.2:2 Secondary clock status: not configured Secondary clock reason: no clock signal Active clock: internal clock source switchover mode: non-revertive Conditions: Anomaly has only occurred after performing resetsys on two nodes at the same time. Workaround: Reconfigure the clocks with cnfclksrc commands.
CSCds73435	Symptom: Residual database information causes AXSM card state to be interpreted incorrectly. An AXSM card inserted into this slot with the residual database may not successfully come up. Condition: Residual database on the disk can be introduced if the active PXM45 card or hard disk is replaced with an older card or hard disk that has old data on it. Workaround: Before replacing an active PXM45 front card or hard disk, make sure that there is a saved configuration for that node. After replacing the active PXM45 front card or disk, restored the saved configuration. To determine if there is residual data on a PXM45 hard disk, after the node comes up, perform a list file command (for example, ll) on the D:/DB2 directory. For every slot that is reserved, there should be a corresponding subdirectory for that reserved slot (e.g. SL7), if there are extra subdirectories for non-reserved slot, these are for residual databases.
CSCds80479	Symptom: HMM DEV ERROR STATE messages are reported in the event log for PXM45 and AXSM cards. Condition: This node has experienced data discards and a card reset on one of the AXSM cards. Workaround: Not known
CSCds87534	Symptom: After switchcc, an AXSM card enters critical alarm state, and subsequently the entire node goes into critical alarm. Condition: The problem occurs on a fully loaded chassis with a large number of connections (around 18 K connections on the AXSM card). Workaround: NONE. The problem disappears after resync is completed (within 1/2 hour in this case).
CSCds87811	Symptom: Errors logged from the shelf manager after a loadrev on active card. Condition: The error is logged after a loadrev operation on the active card. Workaround: Unknown
CSCds89138	Symptom: Adtech/Telecordia SSCOP test release version 1.1.1, Adtech version 3.01 running under Adtech Test Suite Manager version 3.0 is failing 102 out of 128 test cases configured. Condition: Test suites are failing. Workaround:
CSCdt03600	Symptom: Nwbrowser does not show any hardware related information on AXSM card. Condition: Every time. Workaround: No workaround.
CSCdt05372	Symptom: Popup messages appeared on CLI. Condition: Hard disk failure was simulated during fault insertion testing. Workaround: UNKNOWN
CSCdt05704	Symptom: Receiving UNEQ-P does not cause generation of RDI-P in AXSM OC3. Condition: When UNEQ-P is received. Workaround: No workaround.
CSCdt05732	Symptom: UNEQ-P alarm is not detected and shown by AXSM card. Condition: When UNEQ-P alarm is received. Workaround: No workaround.
CSCdt06410	Symptom: During LOS condition, LOF, AIS-L and RDI-P are seen with dspalm command. Condition: When line encounters LOS. Workaround: Ignore all other alarms if LOS is present.
CSCdt07370	Symptom: Command output of a shellcon command popped up on the telnet session of a user who had not executed the command. Condition: display_queue_stats was executed on a separate telnet session. Workaround: UNKNOWN
CSCdt09412	Symptoms: AXSM switchover causes all PNNI links on this AXSM to go to attempt. Condition: Do AXSM switchover. Work around: Waiting for resync
CSCdt10623	Symptom: Core dump occurred on one of two PXM45s. Condition; When user enters core command on active PXM45 to display core dump. Workaround: None.
CSCdt14012	Symptom: dsppnport shows its ILMI state to be undefined. Condition: This happened on a node that was experiencing spontaneous AXSM resets. Workaround: UNKNOWN
CSCdt14687	Symptom: addlnloop command is not allowed on AXSM lines that have APS enabled. Condition: APS is enabled. Workaround: UNKNOWN
CSCdt15584	Symptom : CLI operational error messages are displayed on all terminals. Condition : Other terminals are logged into the same node and they are in same card level. Workaround : If you need to avoid these messages, coordinate with other users so that only one person logs into a card at a time.
CSCdt16223	Symptom: Doing a loadrev, followed by a resetsys causes error logs. Condition: loadrev followed by a resetsys on a single PXM45. This is not a service affecting bug. Workaround: Unknown
CSCdt23369	Symptom: cnfcon on maxcost with 2147483648 (0x80000000) to 4294967295 (0xFFFFFFFF) will round it down to 2147483647 (0x7FFFFFFF). Condition: When the maxcost of the connection is changed. Workaround: When connection is initially added, don't specify maxcost value. The default is -1, which translates to 0xFFFFFFFF. If it is changed, it will be bound to the range of 0 to 2147483647. The only way to have maxcost set to 0xFFFFFFFF is to delete and re-add the connection with default value.
CSCdt24846	Symptom: Backup boot on standby PXM45 checks for file size alignment after downloading file from active PXM45. Condition: When runtime file from active PXM45 gets downloaded and its size is not 8 bytes align, errors get displayed on console port. Workaround: None
CSCdt29562	Symptom: Large number of alarm traps #60110, #60109, and #60108 are generated. Condition: APS switching was being performed. Workaround: UNKNOWN
CSCdt30144	Symptom: Investigation into issue of APS oscillations. Condition: Intermittent failures on APS lines. Workaround: UNKNOWN
CSCdt32198	Symptom: dsperr on non-PXM45 slot provide incorrect information. Condition: dsperr currently provides proper information only when it is executed on PXM45 slot. When it is executed on the AXSM slot, the information seems incorrect. Work around: None. Additional Information: The information is actually correct. CA/TAC needs to do the following to read the dsperr information: 1. FTP the error log file to a UNIX workstation as explained below: For an error with E:xxxXX number on slot Y, FTP the file: C:/LOG/slotY/errorXX.log (XX are the last 2 digits of E:xxxXX number, and Y should be preceded by 0 if Y is single digit). For example, FTP "C:/LOG/slot07/error94.log" if you are interested in say, error 23394 on slot 7. 2. Use "dsperr2" tool on the UNIX workstation to display the error. If the binary image running on the shelf is say, pxm45_002.001.050.000-D_mgx, use the command: dsperr2 error94.log pxm45_002.001.050.000-D_mgx to display the correct trace information.
CSCdt32277	Symptom: core command causes Tlb Exception in the 'tDbgCmdTsk.' Conditions: This happens when a core is created due to an unknown reset reason. The reset reason is shown as '(null)' in the output of the command. This condition was seen by engineering when debugging core feature itself. Workaround: None.
CSCdt33839	Symptom: After setrev to downgrade from 2.1.x to 2.0.x, we see checksum mismatches between the PXM45 and AXSM. Condition: With node running 2.1.x, used setrev to fall back to 2.0.(11.3) and then used setrev to upgrade to 2.0(12.0).This is not service affecting. Workaround: None
CSCdt39878	Symptom: APS CLI error messages gives prints system level error messages. Condition: Error conditions on CLI command like wrong parameter etc. Workaround: none
CSCdt41608	Symptom: Console port baud rate is not shown correctly using the dspserialif command. Condition: User sees a "0" baud rate when executing dspserialif command. Terminal server connects to console port fine with a baud rate of 9600. A cnfserialif is then executed to set the port to 9600. A subsequent execution of dspserialif then shows the value correctly as 9600. Workaround: Use cnfserialif.
CSCdt42037	Symptom: Terminal monitoring from console port can be turned off without verifcation to user. Condition: User unknowingly struck control-s key sequence and blocked out CLI monitoring from console port. This was interpreted as a problem with the console port or connecting hardware by mistake. Workaround: None
CSCdt42130	Symptom: Switch driver error messages appeared in the event log. Condition: AXSM cards were reseated. Workaround: UNKNOWN
CSCdt43304	Symptom: Inconsistent line alarm reporting. Condition: switchcc and switchredcd executed with an LOS condition on one line. Workaround: UNKNOWN
CSCdt44269	Symptom: Commands dspcds and dspcdalms do not seem to be showing corresponding output. Condition: User executing dspcds sees major and minor alarms on AXSM service modules. Subsequent execution of dspcdalms does not quantify alarms. Workaround: None
CSCdt44298	Symptom: dspcd output showed the failed reason is UNDECODED. Condition: When the card is in failed state. Workaround: None
CSCdt45566	Symptom: dspalms showed unterminated interfaces that were in admin down state to be in LOS, LOF state Condition: Lines had been put in admin up while still unterminated, and then put into admin down state. Workaround: UNKNOWN
CSCdt48906	Symptom: Popup messages on user sessions. Condition: OC48 cards were removed and inserted. Workaround: UNKNOWN
CSCdt49074	Symptom: Event log entries indicating software exception errors, followed by task deletion messages. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt50790	Symptom: No CLI command to clear the channel count. Condition: No CLI command to clear the channel count. Workaround: None
CSCdt51824	Symptom: Lost telnet session. Condition: Removed and reinserted APS enabled AXSM card several times. Workaround: UNKNOWN
CSCdt52074	Symptom: Line failure alarms did not get logged at user severity levels in event log. Condition: Line failure alarm. Workaround: UNKNOWN
CSCdt52180	Symptom: Popup message after a resetcd was executed on an AXSM. Condition: AXSM card was reset. Workaround: UNKNOWN
CSCdt52340	Symptom: Confusing error message when conntrace fails. Condition: conntrace was run from the slave end. Workaround: UNKNOWN
CSCdt52467	Symptom: dsplns, dspports, and dspcons commands on standby AXSM do not show correct status. Condition: AXSM is standby in a Y-cabled redundant pair. Workaround: UNKNOWN
CSCdt53574	Symptom: Incorrect usage statement is presented to user for addport command. Condition: addport command with invalid parameters is used. Workaround: UNKNOWN
CSCdt53589	Symptom: addpart usage statement is incorrect. Condition: addpart command is executed with invalid parameters. Workaround: UNKNOWN
CSCdt53847	Symptom: Popup messages : DMA currently active appear on telnet sessions. Condition: QE0 Fault Insertion tests were being conducted. Workaround: UNKNOWN
CSCdt53883	Symptom: Err: Card reset/removed/failed popup messages appeared. Condition: QE0 failure test was being conducted. Workaround: UNKNOWN
CSCdt53892	Symptom: HMM device event failure message appeared in event log without slot #. Condition: PCI bus Error Fault Insertion Testing was being conducted. Workaround: UNKNOWN
CSCdt53946	Symptom: Event log messages for VC lookup failed observed. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt53948	Symptom: CTC app event handler failed messages observed in event log. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt53951	Symptom: PNNI rebuild failure messages observed in event log. Condition: Switchover was executed. Workaround: UNKNOWN
CSCdt53954	Symptom: halfLeg removal failed messages are observed in event log. Condition: UNKNOWN Workaround: UNKNOWN
CSCdt54410	Symptom: sr_proto_unblock_app:Failed allocating resource IpcMessage Err=0x26037 message appears in event log. Condition: Messages were logged against an AXSM after 2.0.11 upgrade. Workaround: UNKNOWN
CSCdt54906	Symptom: OC3/OC12 J1 byte does not provide trace patch to FE NE. Condition: Unknown Workaround: Unknown
CSCdt55552	Symptom: Sev 4 error logs appeared in event log while doing switchcc. Conditions: Performing switchcc Work Around: unknown
CSCdt56557	Symptom: At high PCR or SCR values, if using CBR or VBR policing respectively, the percent of cells allowed through is greater then desired. Condition: Cells should not be passing through. Workaround: Unknown
CSCdt58452	Symptom: Wrong default value for minbw in cnfpnportcac. Condition: Execute cnfpnport and look for the syntax. Workaround : N/A
CSCdt59168	Symptom : upln on E3 AXSM displays unnecessary messages. Condition: upln for the first time on that bay (E3 back card). Workaround: N/A
CSCdt59880	Symptom: Line information is incorrect when inserting both T3 and E3 back cards in the same slot. Condition: Inserting T3 and E3 back cards in the same slot. Workaround: None.
CSCdt60282	Symptom: FTP activity not recorded in the log (enhancement). Condition: 2.0.13. Workaround: None
CSCdt60620	Symptom: Port error message popped up on both the PXM45 and the AXSM. Condition: dspcon was issued on te PXM45 with incorrect port number. Workaround: UNKNOWN
CSCdt61384	Symptom: dspalm and dspalms gives Unknown alarm while on the other end, the line is clear. Conditions: Unknown Workaround: Unknown
CSCdt63895	Symptom: addred command is executed on AXSMs of differing code levels with no warning to the user. Condition: 2.0.13. Workaround: Unknown.
CSCdt64338	Symptom: Command addaddr does not take "-redistribute" as an option. Condition: Attempt to add static address. Workaround: Use "-redst" instead of "-redistribute" as the option.
CSCdt65763	Symptom: dspcons gave wrong information which is inconsistent with what dspcon showed. Conditions: None Work Around: Unknown
CSCdt67109	Symptom: Wrong value of summary address gets assigned. Condition: 1> When ever the length of PNNI summary address (entered with the command) is less than the length provided in the same command, the wrong value gets entered. 2> When length of summary addrress and mentioned length are same but length is an odd multiple of 4 (e.g 12). Workaround: 1> Keep the length of the PNNI summary address (entered with the command) larger than the length mentioned in the same command. 2> Keep the length as multiple of 8 and keep the length of the PNNI summary address (entered with the command) same as the length mentioned in the same command.
CSCdt67125	Symptom: dsppnni-reachable-addr displays the port id as the "logical number" and not as a phsyical port id. Condition: When dsppnni-reachable-addr lcommand is used. Workaround: UNKNOWN.
CSCdt67997	Symptom: It takes 10 minutes to reset AXSM card after QE48 is disabled. Condition: QE48 is disabled. Workaround: None.
CSCdt69425	Symptom: Min/max rate parameter MIB objects to be removed. Condition: 2.0.13. Workaround: Unknown.
CSCdt69489	Symptom: Some of the events logged to BRAM are not visible on standby card. Conditions: None Workaround: BRAM events are sent over to the standby card at recurring intervals.
CSCdt70145	Symptom: A new SNMP feature is requested, similar to switchapsln. Condition: We do not support the switchredcd or the resetcd commands/requests from SNMP. CLI switchapsln falls into such same category. However, this feature makes sense and is valid. Currently, we are waiting guidance from marketing team on supporting this feature. Workaround: None.
CSCdt74745	Symptom: A line is missing in dsplns output. Condition: This happens sometimes when a user does restoreallcnf on a T3E3 card. Workaround: None
CSCdt76508	Symptom: AXSM does not have any commands to show port, feeder and channel alarms. Condition: Always true. Workaround: Use existing commands to debug.
CSCdt77833	Symptom: Changing IP interfaces to 0.0.0.0 is not allowed. Condition: Attempt to delete the IP address. Workaround: Deleting an interface is done using the default IP address of 192.0.0.0. Setting an interface to have this address will cause it's disk configuration to be deleted after the next system reboot.
CSCdt78030	Symptom: An invalid port id is shown in the output of dsppnni-reachable-addr local: aquaman.8.PXM.a > dsppnni-reachable-addr local scope............... 0 port id.............4294967295 <==== Incorrect. Conditions: Reproducible. Workaround: None. Further Problem Description: The value '4294967295' is 0xFFFFFFFF is an invalid Logical Interface Number.
CSCdt78111	Sympton: GREEN LED remains on after succession of commands: upln, cnfln (plcp), and dnln on AXSM-T3E3. Condition: Green LED should not remain on after dnln command is issued. Worakaround: Issue upln, dnln.
CSCdt78112	Symptom: dnallports will stops all traffic flow, and this bug is a request for a new CLI feature that will forewarn the user when he or she downs all ports. Condition: Users issue dnallports command. Workaround: UNKNOWN
CSCdt78174	Symptom: Request new command to provide mapping between LIN (=ifIndex) and physical descriptor. 16979970 <=> 3:1.2:2 Conditions: Reproducible. Workaround: N/A
CSCdt83334	Symptom: Add slave end on a node. Attempt to add slave connection on remote end with the NSAP address obtained from local node. Condition: Attempt to add slave connection with -slave option. Workaround: Only add master connections with slave option.
CSCdt83936	Symptom: IPC does not have ipcHelp command at the shell. Condition: None. Workaround: None.
CSCdt84148	Symptoms: Switch fails sometimes when the operating mode is bi -directional. Conditions: APS switchover fails. Workaround: To provision 1+1 uni direction on at least one side.
CSCdt86885	Symptom: Booking factor set by CWM does not create a log entry. It creates a two line message on the screen. Condition: 2.0.13 and CWM 10.4 FCS Patch 1. Workaround: Unknown.
CSCdt88618	Symptom: Pop up messages on CLI screen. Condition: Router end of SVC releases before PXM45 end. Workaround: N/A
CSCdt89189	Symptom: Port in Building VC after cnfpnportcac command. Condition: Bring down the port on AXSM and run cnfpnportcac command on PXM45. Workaround: Bring up the port on AXSM.
CSCdt89547	Symptom: Line LOS alarm on line in local loopback does not clear. Condition: When back card is removed and re-inserted (line RX is not connected), for OC48 card only. Workaround: dellnloop and addlnloop again.
CSCdt90814	Symptom: "0" is not printed in the dsppnni-ptse -detail true. Condition: Whenever an address is added with format of 0x as the last two digits the "0" is not printed in the dsppnni-ptse -detail true. Workaround: None.
CSCdt91163	Symptom: AXSM2 takes long time to detect serial link failure and thus may have some cell loss. Condition: Serial link error injected during Fault Insertion Testing. Workaround: None
CSCdt93436	Symptom: SPVC connections are not getting rerouted completely. 8k out of 40k SPVC connections are in failed state with no route to destination when display a specific failed connection. Condition: When it happened, the two parallel PNNI links are available. One was occupied with the max number (31998) of connections that it can hold. The other PNNI link has no single connection on it but the link resource is enough. The customer did 120 times of reset on one of the via nodes before this problem happened. Workaround: resetsys and the connections will get rerouted with load balancing.
CSCdt93571	Symptom: AXSM OC12 has an alarm integration problem. Conditon: AXSM OC12 card doesn't report type of alarms but line shows a major alarm. Workaround: unknown
CSCdt95907	Symptom: CLI enhancment to provide one command to show amount of bandwidth available and overbooking factors. Condition: 2.0.13 code. Workaround: Use all CLI commands.
CSCdt98355	Symptom: According to one of the customers, the following objects are not being utilized in the ATM virtual interface MIB: caviStatEgressEntry and caviStatIngressEntry. Condition: The port level statistics can only come from the QE, and the QE does not collect OAM, RM and EFCI detail. Some of them may be configured to have valid values, however it would be limited to debug statistics that have a limited number of ports and connections that may be enabled at one time. So, the answer is that those objects that are hardcoded to 0, should be unsupported. Following objects are unsupported instead of value of 0: caviEgrRMCells caviEgrXmtEFCICells caviEgrRcvEFCICells caviEgrXmtOAMCells caviIngXmtOAMCells Workaround: None.
CSCdu00369	Symptom: Manual switch to working line from protection line does not work. Condition: APS had been configured between MGX and BPX. LOS was created on working line and then cleared. Workaround: UNKNOWN
CSCdu00571	Symptom: commitrev allowed to execute when upgrades have failed. Condition: Execute on standalone card before the card gets to the active state. Workaround: Watch the card state and the state of the upgrades before executing the commands.
CSCdu00601	Symptom: Need to change module ID for path trace log and impose no limit. Condition: 2.0.13. Workaround: Unknown.
CSCdu01877	Symptom: delallcon command should prompt for confirmation before execution. Condition: Execute command on the interface with large number of connections. Workaround: Use caution when executing this command.
CSCdu07085	Symptom: Working line is showing critical alarm, but dspalm shows LOF. Condition: None. Workaround: None.
CSCdu07891	Symptom: Locally switched connections take in-ordinate amount of time to come up after software upgrade from 2.0(10.2) to 2.0(13.2). Condition: Locally switched connections still show "fail" after all routed connections have rerouted up to 30 minutes after upgrade following this procedure. MGX-PXM45 running 2.0(10.2) is upgraded directly to 2.0(13.2) with the following procedure: 1)On stby PXM45, sh, sysBackUpBoot, sysFlashBootBurn "C:/FW/pxm45_002.000.013.000_bt.fw" and reboot (standby now running on 2.0(13) boot and 2.0(10.2) FW). switchcc (repeat procedure on NOW standby PXM45) On all AXSMs, setrev <slot> 0.0. On active PXM45, setrev <active slot> 2.0(13.2) (node now running on 2.0(13)). On all AXSMs burnboot <slot> 2.0(12) (allow card to come up active/failed status) setrev <slot> 2.0(13.2). Workaround: Command rrtcon on the failed local connection may bring connection up.
CSCdu07915	Symptom: Working connections can indicate erroneous alarm "E-AisRdi" on working connections after AXSM OC-3 back card has been removed and reinserted with neighboring back card with APS connector present. Condition: Neighboring 8 port OC-3 backcards with APS backplane present are removed as a set and reinserted. APS is not activated. Some connections may show alarm as "E-AisRdi" using the command 'dspcons -filt 2' on the active AXSM. This alarm indicates receipt of an Alarm Indication Signal from the opposite end of the connection, however no corresponding alarm exists at the other end and the connection is passing cells between the end devices. Workaround: Leaving standby side in place and secured, remove the active side, reinsert and secure screws. Some or all alarms may clear.
CSCdu07958	Symptom: Cannot run command 'optrt' if scheduled route optimization is configured. Condition: Message: "ERROR: Route optimization already enabled on this port, disable first (using cnfrteopt) to use force reroute (optrte)" appears when running optrte command if scheduled route optimization is present as displayed with the command dsprteoptcnf. Workaround: Remove scheduled optimization with command cnfrteopt <portid> disable, run optrte, and re-config scheduled route optimaztion if required with desired options in cnfrtopt.
CSCdu08187	Symptom: switchapsln 1 (clear) gives wrong error message by saying switch failed when actually the switching was finished successfully when either the working line or the protection line was in alarm. Condition: This happens all the time. Workaround: Unknown
CSCdu08445	Symptom: dsplog shows uninitialized string associated with the working line index when Protection Switch Byte Failure (PSBF) events occur. Condition: APS failure event occurs associated with PSBF. Workaround: None.
CSCdu11618	Symptom: Trying to crankback at the destination end for a SPVC slave. Conditions: If there is a problem with connection establishment at the destination node, currently we crankback for SPVC connections at the destination. Workaround: Unknown
CSCdu13084	Symptom: SignalFailLowPriority does not clear for long time. Condition: SignalFailLowPriority shows up for long time with dspapsln. Workaround: Unknown
CSCdu13862	Symptom: Ports, partitions, and connection configuration appeared on a previously empty and unconfigured slot when an AXSM card was inserted. Condition: 2.0.13. Workaround: Unknown.
CSCdu14157	Symptom: cnfclkrsc display does not show the portid option. Condition: On issuing a cnfclkrsc command, the parameters for portid are shown, but the option <portid> is not shown. Workaround: None.
CSCdu15380	Symptom: Changing max threshold below a certain value in cosb results in buffer overrun. Condition: 2.0.13 , and 2.1 code Workaround: Increase threshold value >= 16.
CSCdu15428	Symptom: The "Noncompliant cells" counter in dspchancnt display is populated even when using SCT3 which disables Policing. Condition: Use SCT3 on AXSM and pass traffic. The "Noncompliant cells" counter value in dspchancnt command display increases continously. Workaround: None.
CSCdu15566	Symptom: Protection line is in alarm when it is OK on APS line redundancy testing. Condition: AXSM OC12 secondary front card is active, primary front card is in standby. On back card, upper and lower bay working lines are active. Workaround: Delete and re-add APS redundancy.
CSCdu15997	Symptom: Dspcons and dspcon on AXSM gave wrong information about the connection after multiple switchredcd on AXSM T3/E3 cards. Conditions: The information the AXSM gave was not consistent with what the PXM45 gave. Workaround: Unknown
CSCdu16002	Symptom: Alarm integration problem on AXSM OC12. Condition: Reading from dad shows alarm not displayed in dspln and dspalms. Workaround: Unknown
CSCdu16107	Symptom: Restting the active front card in 1+1 APS pair disengages the APS connector. Condition: Resetting the active card in an APS pair. Workaround: Use ATGetState.
CSCdu16505	Symptom: When line has APS-configured, delport goes through even though the line is upped. Condition: APS is configured on line containing the port. Workaround: No workaround
CSCdu17588	Symptom: pathtrace information does not appear to be logged to dsplog. Condition: 2.0.13 Workaround: Unknown.
CSCdu17785	Symptom: diagdebug command doesn't give error message for wrong parameters. Condition: Execute diagdebug command with out of range parameter or insufficient argument. Workaround: make sure the arguments are correct.
CSCdu21599	Symptom: Connections are not committed by the controller. Condition: Unknown Workaround: Unknown
CSCdu22025	Symptom: dspconalarms command to be introduced on AXSM CLI. Condition: None, because the requested command is a new one. Workaround: None.
CSCdu22981	Symptom: dspapsln command doesn't give details of MIS status. Condition: When the APS line go to different mismatch status. Workaround: N/A

Problems Fixed in Release 2.0.14

The following is the list of known problems fixed in Release 2.0. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S1 Bugs
CSCds79775	Symptom: Card getting reset or losing the ingress bandwidth. Condition: Connection deletes or deroutes. Workaround: None
CSCds83769	Symptom: SCM retry messages on screen and all AXSMs and standby PXM45s in failed state. Condition: qe overflow problem. Workaround: None
CSCdt11833	Symptom: Standby controller card goes to failed state. Condition: Upon performing loadrev after a clrcnf. Workaround: Do a setrev on slot 14 (for SES) or slot 32 (for MGX 8850) with version number 0.0.
CSCdt16078	Symptom: SPVCs derouted on newly active PXM45 card. Condition: This problem is found after runrev. Workaround: Waiting for all the connections to be rerouted.
CSCdt29711	Symptom: Adding and deleting APS line on a NNI port caused it to go to building VC state. Condition: The port is stuck in building VC state and the signalling type is changed from NNI to UNI. Workaround: None. Additional Information: To recover from the problem, execute dnpnport followed by uppnport.
CSCdt34683	Symptom: Standby PXM45 resets. Condition: Execute the runrev command on a single AXSM. Workaround: None
CSCdt36063	Symptom: dsppnports CLI on PXM45 card does not show the output. Condition: On executing dsppnports on PXM45 card, pnCcb task got suspended. Workaround: None
CSCdt40241	Symptom : Traffic does't flow out of E3 back card. Condition : E3 backcard defaults to loopback upon upln. WorkAround : None.
CSCdt40350	Sympton: On a AXSM bring up, the corresponding PNNI ports may show "provisioning." Condition: When AXSM comes up, the VSIS may not be able to have the ports added properly if the fault management task comes up before CEMA. This would cause the VSIS not reporting those ports to the PNNI controller. WorkAround: None
CSCdt40561	Symptom: The port on which SPVCs were provisioned ran out of bandwidth during a card rebuild scenario. It is unclear at this point as to why this happened. It has something to do with the non-default booking factor provisioned on the controller. After resetting the card, the problem did not reappear. Condition: This problem was observed when upgrading the AXSM from 2.0(11.3) to 2.0(12.0). Workaround: Reboot both the active and standby AXSM to force a rebuild. In case of a non-redundant configuration, reboot the non-redundant AXSM.
CSCdt43391	Symptom: Data transfer interrupted when switchredcd executed. Condition: switchcc and switchredcd executed with an LOS condition on one APS line. Workaround: UNKNOWN
CSCdt46582	Symptom: AXSM underwent a software error reset. Condition: switchcc was executed on PXM45. Workaround: UNKNOWN
CSCdt55035	Symptom: NNI port stuck in admin state up and interface state down. IFC_DOWN. Condition: After configure pnportcac bookfactor to 20% for T3 trunk. Workaround: Disable VSI partition on BXM and then re-enable it.
CSCdt57525	Symptom: APS protecion channel stuck in signal fail. Condition: Remove and insert of back card caused protection channel to stick in "signal fail." Workaround: resetcd on active AXSM.
CSCdt70757	Symptom: SPVC connections did not route after node upgrade. Condition: Upgrading the node. Workaround: None
CSCdt72750	Symptom: Standby AXSM stuck in INIT state. Repeated resets of the standby card does not help getting the problem resolved. Condition: Specific events causing this condition unknown. Sometimes, when the standby reboots it gets stuck in Init. Workaround: Need to reboot both the active and standby cards.
CSCdt72786	Symptom: Pnports stayed in building VC/VC failure after upgrading the AXSM bootcode. Condition: After upgrading the AXSM bootcode from 2.0(27) to 2.0(42) the pnports remained at building VC status. Workaround : None
CSCdt74499	Symptom: Node started rejected CLI commands. Condition: Execute commands dsppnports and dsppnni-link Workaround: None
CSCdt75070	Symptom: Standby card goes Init state after upgrading the bootcode and active AXSM card stays at Active-F state. Condition: Upgraded the AXSM boot code from 2.0(27) to 2.0(42). Workaround: Remove the front and back cards and re-insert them.
CSCdt79058	Symptom: Standby card goes Init state and Active AXSM card stays at Active-F state. Condition: Upgraded the AXSM boot code from 2.0(27) to 2.0(42). Workaround: Remove the front and back cards and re-insert them.
CSCdt80435	Symptom: pnCcb causes system reload on processing crankbacks with max_crankbacks value changed by configuration on ports. Conditions: If the max_crankback configured on the egress port is less than what is configured on the ingress port on which the SVC trying to crankback was setup. Workaround: Keep the max_crankback same in the node, or keep the egress max_crankback value more than ingress side.
CSCdt80677	Symptom: Nativity check is skipped on power up. Condition: Node reboot, bring up of any controller card as active. Workaround: None.
CSCdt80845	Symptom: PNNI link went to 'building vc' failure right after changing cables. Conditions: unknown Workaround: Unknown
CSCdt83293	Symptom: Card configuration is not restored after a clrallcnf with restoreallcnf. Condition: Did a clrallcnf on the node and did a restoreallcnf, and the configuration is not restored as the card on which the saveallcnf and restoreallcnf was done came up as standby instead of active mode. Workaround: None
CSCdt85664	Symptom: Standby AXSM of a redundant AXSM-OC3 pair alternates between BOOT & INIT mode after a burnboot process and never comes active. Also the standby PXM45 reset and remained in INIT mode for a long time before coming to standby again. Condition: Using the burnboot command. Workaround: Unknown
CSCdt87745	Symptom: When cong_display command is executed "outStanding status enquiry congestion" is persistently on. Condition: An edge node that had SPVC connections routed via this node was rebooted. Workaround: None.
CSCdt89498	Symptom: Load exception error occured which changed the PXM45 to Fail state which resulted on PXM45 to oscilate between two PXMs. Condition: Performed switchcc on one node. This happens when there are SPVC provisioned on the IISP port and there are active SPVC calls going through the IISP link. Workaround: Remove SPVC endpoints on the IISP port.
CSCdt89629	Symptom: Upgrade to image causes system reload while the new image is trying to go active. Conditions: This happens when the interfaces keep on going up and down rapidly during congestion and a lot of connection status enquires are taking place. Workaround: Unknown
CSCdt90817	Symptom: Port stuck in building VC state. Condition: Egress connection ID programming failure. Workaround: None
CSCdt95005	Symptom: Some of the lines display a signal failure. Condition: Any switches thereafter will not work. Workaround: Do a lockout of protection line and then clear it. (Or) Configure at least one side as 1+1 uni directional.
CSCdu04511	Symptom: The node was completly hosed and no one could log in. Condition: When there are very few resources during a crankback, the alternate routing also cranks back, resulting in a recursive crankback. During this operation, there is a memory leak and over period of time the system runs out of memory. Workaround: switchcc to the standby if available. If its a standalone node, no workaround except to go around the reason for crankback.
CSCdu06060	Symptom: switchredcd causes both cards to reset and stay in "Init" state for about 30 minutes before they come back. Condition: Doing switchredcd a number of times on AXSM redundant pair with APS and ILMI enabled will reproduce the problem. Workaround: None.
CSCdu06062	Symptom: Port went to "building vc" state. Condition: Large number of connections routed through the trunk. dnpnport and uppnport. Workaround: N/A
CSCdu17620	Symptom: PNNI tries to route a new call using a VPI/VCI pair that has already been assigned to an active call over the PNNI trunk. Condition: UNKNOWN Workaround: resetsys would have to be issued to clear this condition.
S2 Bugs
CSCdp48234	Symptom: When a user polls the switch using CWM, 'cwspOperUniType' returns 'zero', this value is not part of the enum defined for this MIB variable. Condition: When 'clock only' ports are added to the controller, these ports are displayed as part of dsppnports command. The sub-agent also returns these ports to a user polling the switch. Since these ports are not 'pnports', the values of the variables associated with these ports are not correct. Workaround: There is no work around for this right now.
CSCdr15911	Symptom: Changing the back card may sometimes cause the front card to reset and cause loss of service. It may occasionally be difficult to bring up the AXSM card. Conditions: This problem happens occasionally when someone reseats the back card several times, the front card is reset. It is also observed that during power on/off testing, sometimes the PhyTask got suspended. Workaround: Try not to reseat the back card too often. If the front card gets stuck during the power-on, try to reseat the front and back card to bring up the system.
CSCds68426	Symptom : Sometimes, after non-graceful upgrade, some DAX SPVP stayed in failed state. Condition : Occurs sometimes after a non-graceful upgrade which accompanies a system reboot. Happens for DAX connections. WorkAround : None But dncon and upcon will recover the connection.
CSCds74316	Symptoms The dsplog command displays 0.0.0 for protection line id when the APS pair is deleted. Conditions Not all of the APS events show proper protection line index. Some are printed with 0.0.0 as index. Workaround: None
CSCds74565	Symptoms: PNNI node name displayed in dsppnni-node is not the same as command prompt node name. Conditions: When the newly configured node name is a matching prefix of the old stored node name, the new node name was not written to the disk. So the PNNI node name won't show the correct node name. Workaround: Clear the old node name by typing a completely different node name and then try the new node name.
CSCds86694	Symptom: When resetcd command was given, unexpected system reload was observed. Condition: unknown. Work Around: Unknown.
CSCds89730	Symptom: Upon trap verification, cwCardIngSctFileAlarm (60358) does not provide correct value for cmIngressFileId varbind. Conditions: User generated trap by configuring the card SCT with an invalid/missing ID using the command (cnfcdsct 56, where 56 is the invalid SCT ID) User then checked CWM GUI OV Event Browser window for traps and expanded varbinds. Workaround: UNKNOWN
CSCds89819	Symptom: Customer reports excessive and varied traffic restore time with redundant AXSM card resets. Condition: Excessive and varied traffic restore is observed when a redundant APS connected nni link experiences card switchovers. Traffic restore over the link is ranging from 25 Milliseconds all the way up to one (1) second. Workaround: None
CSCdt02295	Symptoms: The J0/Z0 bytes are incorrect when the mode is SONET. Condition: None Work around: None.
CSCdt02323	Symptoms: The J0/Z0 bytes in the recd. SONET frame are not correct. Condition: None Workaround: None.
CSCdt02690	Symptom: Start sync, End Sync and APS Line Pair Sync with standby in progress popup messages appear at the cli prompt on a telnet session. Condition: switchredcd command is executed Workaround: N/A Additional Information: All popup messages have been removed by default. If you want to trace them, you can turn trace on for VSIS and EM popup messages or enhance the trace level for APS popup messages
CSCdt05429	Symptom: Node alarms reported on 2.0.10.2 and 2.0.11.3 nodes with switching alarms being the source Condition: Xbarerrcnts observed on one node, none observed on the other node. Workaround: UNKNOWN
CSCdt07085	Symptom: SPVCs stayed in conditioning state Condition: The node terminating the master end of one of the two failed SPVCs was rebuilt Workaround: UNKNOWN
CSCdt07366	Symptom: The pnport on the local side goes to vc building state and SSCOP is in unknown state. The remote node shows that pnport is up and the pnni-link is in attempt state. Condition: The pnport which has Y-red configured goes to building vc state. The SSCOP is in the unknown state on the local side. The condition occurred with switchcc after the Y-red is deleted. Workaround: Bringing the pnport down (dnpnport) and up (uppnport) the pnport come out from the vc building state.
CSCdt07644	Symptom: Clock alarms for primary clock remain persistent Condition: Both primary and secondary clock sources (external bits clocks) were failed. Secondary and then primary clock sources were restored in that order Node continued to show clock alarm for the primary clock, even though the clock status was ok. Workaround: UNKNOWN
CSCdt07691	Symptom: Severe clocking events are shown as info type of events Condition: Configuring clock sources and failing the clock sources Workaround: None
CSCdt07730	Symptom: dspclkalms command shows the wrong clock source to be in alarm - secondary instead of primary Condition: External bits inputs are used for both primary and secondary Secondary clock source is failed first, then primary clock source. Secondary clock source is then restored. A minor clock alarm is reported for the secondary clock source instead of the primary. Workaround: UNKNOWN
CSCdt08059	Symptom: Telnet daemon allowed user access into switch without authentication Condition: Node was reset by resetting both active and standby PXMs, or by power cycle Workaround: UNKNOWN
CSCdt11521	Symptom: vsiProcessVxlCommitRsp: no leg, but has Pep error message keep pop up on PXM Condition: Reset multiple AXSM cards Wrok around: it'll stop generate error message after AXSM comes up
CSCdt12043	Symptom : After multiple switchcc failed to telnet to a node. Condition : Disk IP address not configured for LAN (lnPci0). During switchover, no ARP broadcast sent to declare new IP address <--> MAC address mapping. Workaround: Make sure the Disk IP address (lnPci0) of this node is configured.
CSCdt12816	Symptoms: Adtech conformance tests for SSCOP give an inconclusive result Condition: The Adtech does not expect a response to BGREJ pdu in idle state Workaround: Unknown
CSCdt14860	Symptom: dsplog shows some event log are getting dropped Condition: This occurs when the same event is generated multiple times in a short period of time. The default interval is1 tick = 1/100 second Workaround: None
CSCdt19797	Symptom: After setrev to downgrade from 2.1.x to 2.0.x we see checksum mismatches between the PXM45 and AXSM. Condition: With node running 2.1.x used setrev to fall back to 2.0.(11.3) and then used setrev to upgrade to 2.0(12.0).This is not service affecting. Workaround: None
CSCdt19936	Symptom: Port stuck in building vc Condition: Power off/on or reset node Work around: Issue dnpnport portID then uppnport portID command
CSCdt20459	Symptom: Crossbar fabric and card crossbar alarms reported Condition: 'Can't give up mastership' fault insertion tests were being conducted Workaround: UNKNOWN
CSCdt22626	Symptom: CAC is set for ABR for 2%. Have 2 connections big PCR CBR connection and ABR connection. If CBR is routed first, then ABR con is not able to route. Condition: ABR connection is not routed due to no bandwidth although PNNI has enough bandwidth Work Around: dncon on the CBR connection rrtcon on abr upcon on the CBR connection
CSCdt23284	Symptom: Dax connections go into failed state. Condition: When upgraded from 2.1(0.15) to 2.1(0.30). Workaround: Down one of the PNNI port and up again.
CSCdt27655	Symptom: The Cumulative RM fixed round trip time parameter (octet 9) is not included in the ABR setup parameter. Condition: When initiating an SPVC ABR call, the cumulative RM FRTT octet is not included in the ABR setup parameter. Workaround: None.
CSCdt29610	Symptom: Last user request field implementation needs to be understood Condition: UNKNOWN Workaround: UNKNOWN
CSCdt31293	Symptoms: Able to add 2 master to the same slave endpoint for dax connections. Also, this will lead to dspcons mess-up Conditions: add slave endpoint add master endpoint to slave endpoint nsap address add another master endpoint (with different vpi vci) to the same slave endpoint nsap address and vpi vci Work Around: None
CSCdt31803	Symtom: Bulk configuration file keeps growing. Condition: When SNMP manager tries to save SNMP config file, it loops on MIB walk Workaround: Delete all connections with vci=65535
CSCdt34888	Symptom: VBR3 and UBR2 routed SPVC connection remain in FAIL state. Dspcon on that connection shows "Unsupported combination of traffic parameters" as the Last Fail Cause. Condition: If frame discard is requested on the VBR3 or UBR2 SPVC connections (via addcon/cnfcon), then these connections fail to route. Workaround: Do not program frame discard on pep (addcon/cnfcon with frame discard disable).
CSCdt37525	Symptom: cli command dnpnport/uppnport of nni port timeout. pnRedman was busy sending to standby while the standby is in failed status showing in dspcds. syncRam shouldn't allow application (pnRedman) to send to standby when standby is in failed status. Condition: The MGX(p2spvc4) node has a 100k SPVC routed connections. Workaround: unknown
CSCdt38260	Symptom: pnport went into vc failure state Condition: setrev was executed on AXSM Workaround: None
CSCdt38626	Symptom: dspapslns shows wrong info Condition: when crossover happens Workaround: none.
CSCdt38628	Symptom: dspbecnt shows wrong info. Condition: Always. Workaround: None.
CSCdt38632	Symptom: Syntax for the command routeNetAdd failed Condition: At the cli prompt type the command Workaround: None
CSCdt41415	Symptom: The port stays in AutoConfig. Condition: Somehow the Qe48 hardware get stuck and ILMI (or any other app using Qe48_sar) cannot send PDUs. reasons could as follows: There were some known issue (before metal fix) in Qe48sar that if a Cell is there for extraction, the software has to extract the cell first and then do any other thing as hardware statem/c will be stuck till then.in the present images cell_extraction is done on ISR. this can mean that HW failed to raise a ISR when cell came in or software got the ISR but failed to clear the cell injection. Workaround: first we need to confirm that its same problem. we can find out by using "dspilmicnt " on cli and qe48sarStatsShow on shell. 1)run qe48sar_cell_extract_from_hw on the shell. 2)reset the card
CSCdt41939	Symptom: Connections as displayed by CWM are incomplete. Modifications on the connections don't show up on the CWM GUI. Connections exist on the switch and don't show up in CWM. Conditions: This can happen when there is a high volume of traps, for example when a script is being run to delete a large volume of connections. Workaround: A configuration upload could be done to correctly synch the CWM with the switch after the script has finished. Another work around is, if a user need to add/delete more than 1000 connections at one time, he/she should pace the SPVC connections add/delete rate to avoid trap overflow. The recommanded rate is 1 connection/sec. Further Problem Description: When there is a high volume of traps, especially on an SES node, traps can be silently discarded by the switch after a burst of about 1000 traps has been generated on a given card.
CSCdt41956	Symptom: SAR frame transmit failed and ssiFrameXmt failed error messages are recorded in event log Condition: Switchcc executed every 8 min Workaround: UNKNOWN
CSCdt43371	Symptom: switchredcd caused pnport to fail temporarily Condition: One of the APS lines was in LOS Workaround: UNKNOWN
CSCdt43448	Symptom: from dsppnports, there are failed three SPVC connections at both orion node (svcpop2) and mgx node(p2spvc4). Condition: Both Orion node svcpop2 and MGX node p2spvc4 have redundancy cards and multiple PNNI interfaces. About 99K SPVC connections are configuredand routed on the node. Upgraded the FW to 1.1(50.44)A and system went to reset. After reset system, the SPVC connections start to reroute. Once finished rerouting, there are still three connections failed. Workaround: UNKNOWN
CSCdt43629	Symptom: Sev 4 'Nodal data in disk mismatch with RAM data' message appears in event log Condition: Clock sources were deleted or re-added and switchcc executed Workaround: None
CSCdt43638	Symptom: cnfapsln on protection line doesn't change all the parameters. Condition: Configure intra card 1+1 APS and attempt to configure the parameters on Protection line. Workaround: N/A
CSCdt44343	Symptom: Event log files are not ordered in chronological order Condition: on a redundant node, as a card comes up in standby mode. The file number sequence is off. Workaround: none.
CSCdt45544	Symptom: issued a switchcc, display log shows error,scmproccardinsertremovemsg unknown slot 23. Condition: Customer did a switchcc, dsplog shows this error. 08-00137 02/06/2001-18:09:43 SCM-5-UNKNOWN_VALUE tSCM 0x8022442c <scmProcCardInsertRemoveMsg> unknown slot 23 - 24 dropped Workaround: None
CSCdt45643	Symptom: Route Op Start/Stop messages are dropped incorrectly. Condition: None Workaround: None
CSCdt47978	Symptom: dbgcon command is available at cli level and should be removed Condition: Not applicable Workaround: UNKNOWN
CSCdt48479	Symptom: Policing does not work with ABR CDVT. Condition: Policing works with all traffic classes except ABR. Changing CDVT does not change anything. Workaround: None
CSCdt53257	Symptom : Execute testdelay on a connection for multiple times. Condition: On SPVC connection execute tstdelay multiple times. Workaround: For successful tstdelay we need to try few times.
CSCdt56312	Symptom: APS switching fails intermittently. Sometimes APS won't switch back from P-W, sometimes APS switched okay but fasle alarm message was display "Warning:Switch Unsuccessful on Line: Due To Some Unknown Reason." Condition: switchapsln manual(W-P) then Force(P-W) Workaround: None
CSCdt57738	Symptom: IP Connectivity to the node fails.Any new ports will not have their Control VCs coming up. Condition: The VCM VC Table incorrectly shows no more free entries. This causes all new Control VC Allocation to fail. Workaround: None
CSCdt57775	Symptom: CLI does not warn users that port policy configuration changes made via the cnfpnportcac command will apply to existing connections Condition: cnfpnportcac command is used when connections have already been provisioned Workaround: UNKNOWN
CSCdt59596	Symptom: Trap 60078 (cwCoreCardSwitch) was sent with cwTrapSlotNumber and cwTrapIndex in reversed order so old active slot number would be wrong. Conditions: The trap is sent after a PXM45 switchover. Workaround: None.
CSCdt60315	Symptom: dspalmcnt does not count number of RcvRai alarms on ds3 card. Condition: If phycally there is remote alram indication (Rai) shown in dspalm -ds3 dspalmcnt will not show the count increase. Workaround: None.
CSCdt66184	Symptom: addcon, dspcons, dspcon, delcon, cnfcon are only available at the CISCO_GP access level. Condition: Commands are available on AXSMS. Workaround: You must log in as cisco to access these commands.
CSCdt67969	Symptom: PXM45A resets from init state. Condition: When resetsys was given on the node. Workaround: None.
CSCdt68712	Symptom: Virtual trunks on AXSM T3 card were not coming up even the relative spvp connections were added and out of alarm. Conditions: did not find similar problem on AXSM OC3 card Work Around: None
CSCdt74986	Symptom: Added two DAX SPVCs thru CLI, slot 1 interface 1 & 3. Line 1 has local loop and Addtech testset is Connected on line 3. Line 1 & 3 do not have any alarms but SPVCs are showing E-AisRdi alms. One shows alarm on interface 1 & the other on interface 3. Addtech is not Transmitting any data on line 3. Conditions: The dax connection is: 1.3.97.97 to 1.1.97.97. The reason that 1.1.97.97 is in E-AIS/RDI alarm is because 1.3.97.97 is incorrectly generating seg AIS towards the ingress direction. Currently, we suspect that the AXSM made the decision to generate AIS because the use of un-initialized information in the database. Workaround: None
CSCdt75047	Symptoms: During switchcc, the ATM interface loses connectivity to router. Condition: First router entry in IPCONN database is null. Workaround: Before switchover, make sure first router entry in not null. To do this: 1. delete any router entry 2. re-add any router entries
CSCdt75586	Symptom: Control VC stays in attempt states. QE SAR shows discards/errors on the GLCN. Condition: We suspect that QE VC queue is not purged when the connection is deleted. It causes the cell memory leak in QE. Pretty soon the cell memory will reaches the threshold so the incoming cell will get discarded. Workaround: switchover to standby
CSCdt79124	Symptom: Crankback IE not sent to the originating node when max_crankback is changed by configuration on the via node. Conditions: This happens when the egress max_crankback value and ingress max_crankback value differ on the via node. Workaround: keep ingress and egress max_crankback values same on the ports on the via node.
CSCdt79166	Symptom: Runrev on a AXSM blocked after loadrev with reason that there have been disk updates. Condition: Upgraded an OC12 card with approximately 50VTs and feeder connected. Workaround: Reset the Standby card or abort the revision and attempt upgrades again.
CSCdt79397	Symptom: Rerouting of connections causes messages to be logged under SPVCM_INFO Conditions: rerouting of connections Workaround: None
CSCdt79626	Symptom: One will see following line repeatedly 5.1.2 not W nor P-Line for 0x81918a88 Condition: switchredcd was executed Workaround: logout from the session and login again.
CSCdt82186	Symptom: Rerouting of connections using rrtcon causes some connections to take a long time to reroute. Conditions: rerouting of connections using rrtcon Workaround: None
CSCdt82767	Symptom: Connection still exists on the port that was admin down on AXSM (i.e., dnport). Condition: When dnport command is issued, AXSM should delete all connections on that interface. However, while deleteing the connection, if any error occur to a particular connection, the function exits prematurely leaving the rest of the connection undeleted. Workaround: None.
CSCdt83138	Symptom: During resync, RM connection delete may fail. Condition: When processing the resync end command, if a "to be deleted" connection is in CmtPendCd state, the RM delete may fail because TCB was not updated properly. Workaround: None.
CSCdt85824	Symptom: The connections go into fail state. Condition: After performing numerous dnport/upport/switchredcd on a AXSM, the connections may go into fail state. Workaround: None.
CSCdt91237	Symptom: As per design, the dspln shows "major" just to alert the user that one of line is bad. But it is not service affecting. Traffic is flowing. Condition: None. Workaround: None.
CSCdt95478	Symptom: Intraslave connection commit failed. Condition: When committing a connection from (A,0) to (A,B) where A and B are endpoints on the same card, if commit B failed, the hardware programming are not always backout properly (i.e., a dangling egress conn id of B may be left in the hardware). Workaround: Perform a switchover if standby AXSM is available.
CSCdt96877	Symptom: On an OC-48 card with Y-red cable configured with links, without APS, a switchred from the primary to secondary card, whereby causing the secondary card to go active, would cause the link to go down. This only occurs when the mini-backplane is installed. Conditon: The condition or result of this is that the link would go down. Workaround: Remove the mini-backplane if there is no APS configured.
CSCdu00244	Symptom: Connection delete failed on standby Condition: When massive connection deroute/reroute take places at the same time when standby is comming up, connection delete on standby may fail due to Ingress conn id delete failure. Workaround: None.
CSCdu00540	Symptom: When dspapsbkplane command is used Condition: Sometimes the command does not display the correct value when the line is in alarm Workaround: None
CSCdu05612	Symptom: Connection delete failure was reported on AXSM. Condition: When connection deroute fails for a given endpoint, subsequent connection delete on the endpoint may also fail, leading to VSI/RM connection info mismatch. Workaround: None.
CSCdu06158	Symptom: Connection commit failure is reported by AXSM. Condition: When derouting a connection, if the controller deroute by setting the PRI endpoint to NULL (i.e., from (A, B) to (0, B)), the connection deroute may fail. Workaround: None.
CSCdu12506	Symptom: All interrupt are disabled while adding intra-card APS lines. Conditions: Under this situation, if config the apsln to be bi-directional, it still operates at uni-directional mode, and if the other end added as inter-card APS line, sometimes, both forced and manually switchapsln do not work. Workaround: Developers are working on this problem.
CSCdu14323	Symptom: Connection deroute fails on the AXSM. Condition: When controller deroute a connection in the commit pending on committed state (i.e., when controller deroute a connection BEFORE it receives a response from the slave for the previous connection commit on the same endpoint), the connection deroute request may fail. Workaround: None.
S3 Bugs
CSCdp55031	Symptom: When "clrpncon" command is used to clear a SVC connection, The release cause is sent as #31 (normal unspecified) instead of #16 (call clearing) Condition: clrpncon command executed on a port, vpi, vci or for all SVC connections on that port. Workaround: None.
CSCds10778	Symptom: Standby PXM45 gets reset by Active PXM. Condition: Rerouting is going on massive scale, we have SPVC journaling also at the same time and user executes provisioning commands which requires disk writes and standby journaling updates. At that time sometimes standby is reset by active pnRedman. WorkAround: When massive rerouting is going on avoid too many provisioning commands on the system.
CSCds15154	Symptoms: Port goes into Building VC. Conditions: When configuring the signaling parameters for a given port. If sigvci and rccvci have been changed and then brought back to their default values of 5 and 18 respectively, the port may go to Building VC occasionally. Workaround: Down the port and up the port should bring the port to UP again.
CSCds58912	Symptom: CC alarm is not always reported. Condition: Enabling and Disabling CC multiple times on a connection may cause the CC alarm not to be reported. Workaround: None.
CSCds62761	Symptoms: SPVC are allowed to be added on failed PNNI interface Conditions: addcon on failed PNNI interface Workaround: Don't add SPVC on failed PNNI interface
CSCds69631	Symptom: Debug messages are displayed as Error messages in log file Condition: With ABR calls and vsvd 0 Workaround: none
CSCds72852	Symptom: The PNNI would find the AXSM "inactive" Condition: When a controller is added, then deleted, followed by switchcc and addcontroller on the new PXM. WorkAround: Delete the controller and add it again.
CSCds76238	Symptom: A Major Clock Alarm is raised to indicate the fact that the Network Synchronization clock for that node is in the Holdover mode after deleting all configured clock sources for that node. Condition: This condition can occur after a user deletes all configured clock sources on the node. Workaround: None.
CSCds76964	Symptom: The display of the address filter does not contain the address in some cases. Condition: This problem will arise when combinations involving prefixes, * or addresses beginning with ... are entered. The filtering action will take place correctly. However, the display is not correct. Workaround: None.
CSCds77014	Symptom: When working line cable is pulled and active line switches to protection line, "dspapsln" command "Alarm State" shows "Clear" even if "Working Line Pending Request" shows "SignalFailLowPriority". Condition: Working line fails. Workaround: "Working Line Pending Request" is correct. Ignore "Alarm State".
CSCds80500	Symptom: ABR SPVC is not placed into failed state when the master and slave ends of the connection do not have matching PCR values Condition: The master end of the ABR SPVC does not have the same values for local and remote PCR as the slave end of the SPVC Workaround: UNKNOWN
CSCds82523	Symptom: Customer sees the following error after adding redundancy of AXSM cards. 07-21921 11/29/2000-20:10:22 IFM-4-ERROR E:07216 pnCcb 0x8056e0b4 PnNet/IFM/ifcProcessIfcFailedTrap:Cannot find 0x10c1801Interface in Func tree Condition: The problem comes when deleting certain ports on AXSM card and then adding redundancy AXSM card immediately. The problem also happens when we delpart & delport on AXSM card and immediately remove this AXSM card. Workaround: We don't suggest doing delpart & delport on the AXSM card which will be added as the redundancy AXSM to another AXSM card.
CSCds86837	Symptoms: dsperrs on PXM45 displays pnCallaudit error entry when burning new boot on the card. Condition: The error is logged while burning the new boot on the PXM45 card. Workaround: Unknown
CSCds86986	Symptoms: AXSM switchover cause all PNNI links on this AXSM go to attempt. Condition: This problem occurred after resetting an AXSM non-redundant card and followed by several (some times up to 10) consecutive AXSM switchovers on redundant AXSM pairs on other slots of the same node. Work around: Do not do consecutive AXSM switchovers. If the problem occurs, the periodic resync between PNNI controller and AXSM will recover the failure.
CSCds87038	Symptom: dspdiagcnf, dspdiagerr and dspdiagstatus commands do not break after 24 lines. Condition: Normal Operation Workaround: None
CSCds89157	Symptom: Diagnostics tests configured with cnfdiag and shown with dspdiagstat do not show passed diagnostics tests. Output only shows number of test interations and failed results. Condition: Customer configured diagnostics tests using cnfdiag. Test results were then viewed with dspdiagstat. Results did not adequately show the passed cases. Only number of iterations and failures are shown in the output. Workaround:
CSCds89750	Symptom: Upon trap verification, cwChanAdd (60301) does not provide correct value for cwaChanVpcFlag varbind. Conditions: User was adding a slave connection from CLI with the following command: addcon 3 99 99 cbr1 s User then checked CWM GUI OV Event Browser window for traps and expanded varbinds. Workaround: UNKNOWN
CSCds90459	Symptom: Event log has error messages like the following: 05-00017 12/12/2000-17:20:11 SSI-4-TMRCANCELINV E:05246 APSTask 0x80152bbc SSI Timeout event not found in ssiTaskTimeoutCancel. TmoFunc=0x8027aee8, key=5. Condition: Happens when APS is configured. Workaround: None.
CSCds91308	Symptom: Screen output of dspcd command executed on AXSM card does not break after 24 lines, providing an option to quit or continuing viewing display output of the command Condition: dspcd command is executed on AXSM card Workaround: UNKNOWN
CSCds91402	Symptom: APS mini-backplane warning message displayed after APS was deleted and the mini-backplane was removed. Condition: Installed the mini-BP, added APS line. Deleted the APS line, removed the mini-BP. Workaround: None.
CSCdt02028	Symptom: The event log entry is misleading when SSCOP is disabled. Condition: disablesscop command executed on a port. Workaround: None.
CSCdt04611	Symptom: Copychan command used to build 1000 connections at a time appears to be causing the ethernet interface to hang. Condition: Ethernet chip appears to freeze. User loses connectivity to the switch. Workaround: Possibly a PXM45 switchover may resolve the ethernet connectivity issue.
CSCdt04649	Symptoms: Both Pxms in the node failed to come up. The shmFailDisplay() command shows the fail reasons to be: BRAM and Disk are declared as Non-Native. The log will show the following entry: 07-00016 12/21/2000-10:50:27 SHM_-4-NOVRAM_FAIL ShelfMgr 0x803038b8 SHM ERR: NOVRAM Info Read failed for device: Back Plane, slot: 0 To display the log in the ShellConn prompt, type: sysEventDisplay "" Conditions: On a node powerup or node reset scenario, the active PXM45 failed to read its NOVRAM. Workaround: If both PXM45 cards are inserted, remove one of them, and reset the other card, try to see if this card will come up. If not, try the same procedure on the other card. If both attempts failed, try swapping the 2 cards and repeat the above procedure. Also, check to make sure that all front and back cards in the shelf are seated securely.
CSCdt04929	Symptom: Number of channels allowed on 'copychan' command should be limited to 20 channels. The system does not give error message when more than 20 channels are entered. Condition: Currently, copychan command allows user to enter a large number of channels to be copied at one time. This may cause some side effect such as ethernet interface hangs if SNMP trap manager is enabled. Another side effect is that not all channels are saved on the disk. Workaround: Do not copy more than 20 channels at a time.
CSCdt05432	Symptom: dspxbaralm and dspxbaralms commands have same functionality. Condition: Use of cli Workaround: UNKNOWN
CSCdt05434	Symptom: dspcon command presented an error message on cli Condition: It was executed on a standby AXSM card Workaround: UNKNOWN
CSCdt05929	Symptom: Tstsdelay on popeye2 should be blocked for the connection which terminates on a feeder node. Condition: tstdelay command on a popeye2 node. Workaround: No workaround. Make sure that the connection doesn't terminate on a feeder.
CSCdt06379	Symptoms: When "clralmcnt" command is executed, the Path RDI and Path AIS count do not clear. Conditions: When line receives RDI-P or AIS-P. Workaround: To find out RDI-P and AIS-P count increment between "dspalmcnt" commands, need to remember the RDI-P and AIS-P count of last dspalmcnt.
CSCdt08776	Symptom : After switchred on AXSM, dsplog shows that call to ctcAppActiveReadyconfirm() fails Condition: The first call to the function goes through but the second call fails but the second call is not required anywyas. Workaraound : This is not a service affecting bug.
CSCdt09608	Symptom: There are a couple of symptoms can be resulted from this ddts: a) Setting MIB variables cwaChanMaxCost, cwaChanCDV, cwaChanCTD, cwaChanRemoteCDV, cwaChanRemoteCTD on a slave endpoint fails. b) CWM sync up will fail because of these set failures. Condition: The failure happens when users try to set above MIB variables on a slave endpoint. These variables should only be set on a master endpoint. Workaround: When setting these MIB variables or using corresponding CLI command "addcon", the user should always follow these rules: a) from SNMP, cwaChanCDV and cwaChanRemoteCDV should always be set to the same value. b) from SNMP, cwaChanCTD and cwaChanRemoteCTD should always be set to the same value. c) from CLI, the parameters 'lcdv' and 'rcdv' of the 'addcon' command should always be set to the same value. d) from CLI, the parameters 'lctd' and 'rctd' of the 'addcon' command should always be set to the same value. e) do not set above variables on a slave endpoint either from CLI or SNMP.
CSCdt11521	Symptom: vsiProcessVxlCommitRsp: no leg, but has Pep error message keep pop up on PXM Condition: Reset multiple AXSM cards Workaround: It'll stop generate error message after AXSM card comes up
CSCdt11860	Symptom: When PXM45 boot up, it displays the PXM45 card banner instead of the product MGX8850 or MGX8950 banner. Condition: PXM45 card banner does not correctly represent the product name. Workaround: none
CSCdt12510	Symptoms: Intuitive error message when connection is added on an existing endpoint Conditions: When connection is added on an existing end point Workaround: Don't try to add a connection on an axisting end point
CSCdt13022	Symptom: Interface go down after deleting AXSM redundancy Condition: Delete AXSM T3/E3 redundancy Workaround: Remove standby AXSM Y-cable before delete AXSM redundancy
CSCdt14083	Symptom: CLI commands provide no functionality: cnfnddebug and dspnddebug. Conditions: UNKNOWN. Workaround: UNKNOWN.
CSCdt14160	Symptom: Today when a connection is deleted from the proxy slave, we do not know how the connection is deleted (resync, or explicit VSI Delete) Condition: Timing problem or deleted due to slave resync, or the unbind msg never send to the application by PNNI. Workaround If the connection is deleted, but the LCN is still bounded. There is no way to reused this GLCN. The only way to correct this is through PNNI resync.
CSCdt14390	Symptom: CLI cnfspvcprfx is confusing cnfspvcprfx [-prfx] where -prfx is mandatory not optional the bracket should be removed Condition: do either cnfspvcprfx -prfx 20bytes address or cnfspvcprfx -prfx default Work Around: cnfspvcprfx -prfx default
CSCdt15540	Symptom: 3 segment ABR foresight connections across MGX8850 2.0 network always has middle segment part with ICR = PCR on feeder side. Condition: When creating 3 segment abr-foresight across MGX8850 2.0 network. Workaround: Go through CLI to fix ICR value.
CSCdt15653	Symptom: Erroneous values shown for tstdelay result when con segment enpoint in place on via node. Condition: SPVC configured accross three nodes and connection segment endpoint is configured on intermediate via node. Result of tstdelay is over 100% higher value with intermediate connection segment enpoint in place as opposed to when it is not in place. Workaround: None
CSCdt16522	Symptom: Multiple .zip files are being retained in C:/CNF dir. However, according to design, only the 2 most recent files should be retained in C:/CNF. Condition: On issuing a saveallcnf through SNMP or CLI Workaround: manually delete any old .zip files that are not required.
CSCdt22576	Symptom: cnfpart is allowed when port is up. Condition: user initaited cli command Workaround: Do not do cnfpart when port is up.
CSCdt23352	Symptom: Error message indicating incorrect syntax or illegal option values are used is presented when upln is issued. Condition: Line is already up Workaround: UNKNOWN
CSCdt23408	Symptom: dspsscops command output appears on all telnet sessions open to switch Condition: dspsscops command was executed only on one of the telnet sessions Workaround: UNKNOWN
CSCdt24006	Symptom: Non service impacting Event Logs should lower the severity. Condition : Perform resetsys on the node Workaround : none
CSCdt24861	Symptom: SM card goes to contious reboot when downloading image Condition: This happens if the checksum of the image is incorrect or the image size is larger or the image is just corrupted. The card will come up and then reset again due to invalid image without a warning or error log. Workaround: Download a valid image to the disk and the card.
CSCdt30583	Symptom : Commands parameters that require an unsigned intrange do not have a valid type. Condition : Whenever the need for such a parameter is identified Workaround : This problem has been fixed. A new type has been introduced.
CSCdt31261	Symptom: Commands dspcds and dspcdalms do not seem to be showing corresponding output. Condition: User executing dspcds sees major and minor alarms on AXSM service modules. Subsequent execution of dspcdalms does not quantify alarms. Workaround: None
CSCdt31371	Symptom : System level error messages displayed on terminal Condition : Standby card get rebooted Workaround : N/A
CSCdt32558	Symptom: The message displayed is : " ATMC-4-INTERNAL_ERROR Start Bitmap Null" Condition: During call journaling, before updating the call on stdby side,it will check if there is a VpiVci bitmap created on stdby side. If bitmap is not found, the above information will be displayed and won't affect the call updating to the standby card. Workaround: None
CSCdt33174	Symptom: After formatting the PXM45 hard disk, the "sysVersionSet" command returns an error about not being able to open C:/SHMDB/forced_version Condition: 2.0.12 code was used Workaround: Before issuing the "sysVersionSet" command, create a /SHMDB directory and FTP the four files from a working node's /SHMDB directory on to the node.
CSCdt33280	Symptom : Configuration of APS fornon existent AXSM card did not block Condition: Attempt to configure APS line of non existant AXSM from an AXSM. Workaround : N/A
CSCdt33765	Symptom: When the PXM45/AXSM cards reboot, boot code clears the caches instead of flushing them to DRAM. This operation destroys the data got modified in the caches that has not been written to memory. Condition: Checking the coredump shows that the core image does not represent the actual image in memory. Workaround: None
CSCdt42209	Symptom: CUT: (cuts) failed to schedule time in cutsProcessAckRecv event log message was recorded Condition: None Workaround: None
CSCdt44241	Symptom: Commands dspcds and dspcdalms do not seem to be showing corresponding output. Condition: User executing dspcds sees major and minor alarms on AXSM service modules. Subsequent execution of dspcdalms does not quantify alarms. Workaround: None
CSCdt45149	Symptom: cnfln syntax does not include e3 options Condition: Issue the cnfln command Workaround: Check documentation.
CSCdt48901	Symptom: ILMI disabled messages are printed in the event log for all ports where ILMI is not configured Condition: Switchcc is executed Workaround: UNKNOWN
CSCdt51884	Symptom: Mutliple Upgrades can take place at the same time Condition: Issue loadrev on a set of cards and then do it on the other set Workaround: Do not upgrade multiple cards at the same time. Multiple upgrades is not a recommended upgrade procedure.
CSCdt52092	Symptom: 'Call failure due to crankback max attempts reached' message appears in event log Condition: This message appears even for SPVC crankbacks Workaround: UNKNOWN
CSCdt52557	Symptom: APS has a failure, but is not shown in the APS Trouble mask in dspapsln Condition: unknown Workaround: look at event log to see correct APS state.
CSCdt53956	Symptom: dsprevs command shows garbage for non-existent cards Condition: UNKNOWN Workaround: UNKNOWN
CSCdt58380	Symptom : Core dump flag should be set to the default value of 0x262ee if it is having a value of "0". Condition : Unknown. But value can be set from software. Workaround : None.
CSCdt58554	Symptom: APS Event log is not clear enough to debug Condition: APS events workaround: look at existing APS event log.
CSCdt59151	Symptom: agent capability mib shows incorrect access to mib objects Condition: usage of this mib Workaround: know correct access levels and avoid invalid access to mib objects
CSCdt60607	Symptom: Need warning message to user to continue before executing switchredcd command. Condition: None Workaround: Unknown.
CSCdt62511	Symptoms: PXM45 shows a major clock alarm when running on internal clock. Condition: Delete the primary BITS clock with a major alarm, the alarm does not go away though the node is now running on internal clock. Workaround: Go to shellcon and enter command: clkmgrAlarmClear (0x29004)
CSCdt69477	Symptom: Access levels to be changed as appropriate for the listed commands. Condition: Access levels can be realized by logging in with different login levels. Depending on the Access Levels, the applicable commands will be visible. Workaround: None.
CSCdt75339	Symptom: Release-complete cause code gives wrong cause value when the number of crankbacks hits the max_crankback limit. Conditions: total releases processed is max_crankbacks +1 but we only check for max_crankback number of crankbacks. Workaround: Unknown
CSCdt78905	Description : VSI Master AVL Tree of interfaces does not match that maintained by Interface Manager. Symptom: Congestion Manager (CCM) logs error during congestion detection and abatement. Workaround: None.
CSCdt79048	Symptom: T310 timer range is not correct for PNNI1.0 signalling using cnfsig. Condition: User cannot configure T310 timer per Q.2931 specified range. Workaround: None
CSCdt79632	Symptom: Dsplog displays unreadable working line index. Condition: PSB Irrelevant event occurred Workaround: None
CSCdt80847	Symptom: Results from vsiCksmBlkCmp command is seen on Stdby instead of active. Condition: When vsiCksmBlkCmp command is issued on the active, the result is shown only on the standby, which is annoying. Workaround: Open a window for both active and standby. Issue the command on active and observe the result on standby.
CSCdt89348	Symptom: dspapslns and dspapsln shows ALM or OK. It would be useful for the user if it is displays more granular level i.e SF-L, SF-H etc.. Condition: None. Workaround: None.
CSCdt89848	Symptom: Irrelevant error message pops up when a APS line is added. Condition: On AXSM CLI, add a APS line. A error message pops up. Workaround: None.
CSCdu06112	Symptom: delapsln is executed and the command fails due to some reason. APS tries to log the trace but the logging causes the 'Tlb Exception' Condition: unknown Workaround: None.
CSCdu23970	Symptom: When dspapsbkplane is executed on the standby card it shows an error: "Standby card is Not Ready." Condition: Always Workaround: Try executing the command in Active card only. If the ACtive card shows the backplane state as "ENGAGED", then theer is a high probability that the backplane is ENGAGED.

Known Anomalies found In Previous Releases

The following anomalies were identfied in previous releases. There bugs were either closed, determined not to be a problem, duplicated to another bug, or marked as un-reproducible. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

CSCdr15133	Duplicate of CSCdr20887 conDelError when SPVCs are de-routed due to dnpnport*25k*
CSCdr15197	Un-reproducible IPC buffer memory leak during swichcc with 10K SPVC &1k SVC *BLOCK*
CSCdr19636	Verified in 2.0.02 dspalm and dspln cmds show diff alarm status
CSCdr20887	Un-reproducible AXSM: vsi error - Cant delete VC entry
CSCdr22569	Verified in 2.0.01 80 abr failed to route in parallel link situation (SLT)(BLOCK)
CSCdr35241	Un-reproducible AXSM vsiErr 0x502a: Connection reserve failure *25K*
CSCdr43257	Duplicate of CSCdr26669 ORIONSLT:3000 SPVCs fail to reroute even though resources are available
CSCdr19861	Un-reproducible Vsi Err found after one trunk (OC48) down and cnfilmi on the other
CSCdr26669	Un-reproducible H-link associated with a PNNI port missing from the PTSE db.*25K*
CSCdr28772	Un-reproducible ORIONSLT:Many ilmi ports on other cards go down after reset BXM
CSCdr31492	Un-reproducible SPVCs fail to connect after AXSM (UNI side) reboot while deroute*25K*
CSCdr47777	Junked Sonet layer doesn't recover if either of AXSM/BXM (OC3) is rebooted
CSCdr78943	Junked (001206) Interface Policy CAC defects
CSCdr86343	Junked (000801) Failure reason for intf operation trap is wrong
CSCdr87314	Duplicate of 89804 AXSM1(OC3) w/10K connections got reset after establishing signaling
CSCdr89382	Duplicate of 93447 9512 went down. SSCOP switching bet. reset & establish. after reset sys.
CSCdr89804	Junked(000817) OC12 failed keeps pumping ipc message allocate error streams
CSCdr93317	Closed Multiple tasks hanged on mutex semaphore, block cli and shellconn
CSCdr94471	Closed -- not a problem.
CSCds03683	Un-reproducible dsppnni-node does not show the node name
CSCds06186	Duplicate of CSCds58912 en/dis/enabling of cc on con does not result in alarm.
CSCds14824	Un-reproducible upgrade:setrev on PXMs cause endpoint local nsap address corruption
CSCds15089	Closed -- not a problem.
CSCds15159	Duplicate of CSCds28333: Crossbar errors are observed after switchcc, which is fixed in 2.0.11
CSCds16742	Duplicate of CSCds27372, which is fixed in 2.0.11
CSCds17859	This bug is now assigned by the CWM group
CSCds18690	Duplicate of CSCds23525: SLT-sw:PNNI link stays in attempt state, which is fixed in 2.0.11.
CSCds19282	Un-reproducible Sysbootchange Init Parameters Corrupted
CSCds20287	Un-reproducible CLI gets Hang while switching to the AXSM1 card
CSCds20318	Duplicate of CSCds23518: SLT-sw:AXSMs reset due to sar error, which is fixed in 2.0.11
CSCds20527	Duplicate of CSCds87902 - this is a CWM bug.
CSCds21342	Closed -- not a problem.
CSCds22604	Duplicate of CSCds45453: AXSM: stdby axms card keeps rebooting due to syncRamError -- which is fixed in 2.0.11
CSCds22824	Duplicate of CSCds26981: SSI DIO: Recover from task deleted while accessing a file, which is fixed in 2.0.11
CSCds22862	Un-reproducible cc to AXSM OC48 slot with AXSM-Yred fails & exit user from telnet ss.
CSCds22946	Un-reproducible AXSM-RED: AXSM PXM45 db mismatch causes reroute fail (AXSM-RED-DF)
CSCds23335	Duplicate of CSCds26981: SSI DIO: Recover from task deleted while accessing a file, fixed in 2.0.11
CSCds23586	Duplicate of CSCds00727: Discrepancy in card state between CLI cmd prompt and dspcds output
CSCds23866	Duplicate of CSCds04573: AXSM-red:OC48 failed after switchcc on PXM,Hello msg miss, fixed in an earlier release.
CSCds24168	Closed -- some of the hardware was missing.
CSCds24320	Un-reproducible axsmred:All VTs go down after swithcc on PXM
CSCds24905	Duplicate of CSCds46551: axsmred:Number of SPVCs do not match between crossing ports.
CSCds28506	Un-reproducible SLT-sw: Tlb load exception at task pnCcb
CSCds30648	Un-reproducible Redundant PXM45 remained in i-state after node reboot
CSCds31341	Closed - not a problem
CSCds31775	Un-reproducible AXSM1(T3/E3) keeps resetting.
CSCds32464	Closed -- incorrect connections were being used on the modems
CSCds33133	Duplicate of CSCds04573: AXSM-red:OC48 failed after switchcc on PXM,Hello msg miss, fixed in an earlier release.
CSCdt35423	Un-reproducible pnports went down after PXM45 runrev during 2.0.12 upgrade
CSCds35707	Un-reproducible SLT: Cause RcvCount XmtCount repetitively displayed.
CSCds35713	Un-reproducible DAX connections stayed in conditioning after interface recovered
CSCds38742	Closed - not a problem
CSCds43545	Duplicate of CSCds90343 Residual Connection OAM Traffic After Con Deletion -fixed in 2.0.12.
CSCds43553	Closed - not a problem.
CSCds43557	Duplicate of CSCds33855 Corruption of event log file
CSCds45450	Un-reproducible PXM45 fails to go standby
CSCds46455	Un-reproducible Switchcc caused standby PXM45 and all AXSM to fail.
CSCds46524	Un-reproducible All ports on an AXSM in provisioning state.
CSCds52922	Closed - not a problem.
CSCds54248	Closed - problem with the hardware.
CSCds54390	Un-reproducible axsmred:SPVCs stop rerouting - SAR Tx Errors
CSCds54794	Un-reproducible axsmred:sscop state not stable after adding APS line.
CSCds56802	Un-reproducible axsmred:Database mismatch between standby and active PXM
CSCds57354	Un-reproducible Card Summary displays incorrect details
CSCds63689	Un-reproducible Core dump - watchdog timeout reset
CSCds63724	Un-reproducible Upg:upgrade AXSM cause one nni port go to building vc.
CSCds63745	Closed - not a problem
CSCds64302	Duplicate of CSCds68882 Upg:AXSM switchover cause Tlb load exception on both redundant cards - fixed in 2.0.11
CSCds65195	Closed - user error.
CSCds66741	Duplicate of CSCds65320 Slots show alarms in dspcd after switchcc - fixed in 2.0.11.
CSCds67334	Closed - not a problem.
CSCds68209	Un-reproducible Upg:PXM45 crash after burn boot code on single PXM
CSCds71721	Closed - not a problem
CSCds74175	Duplicate of CSCdt38628 dspbecnt shows wrong info for an APS line - fixed in 2.0.14
CSCds74268	Un-reproducible AXSM spontaneously reset
CSCds74746	Closed - not a problem.
CSCds79327	Un-reproducible emVsiRamHwRsrcPart error on standby AXSM
CSCds80370	Un-reproducible CBR SPVC discarding 50 % of its data
CSCds80406	Un-reproducible AXSM spontaneously reset during data transfer tests
CSCds84734	Un-reproducible PXMB:standby PXM45b reset several times then comes up after restsys
CSCds87811	Un-reproducible UPG-dt:Loadrev cause error log on the active PXM45 card.
CSCds90296	Closed - not a problem.
CSCds90463	Un-reproducible Upg:EM database consistency error during AXSM resync
CSCds92690	Closed - not a problem.
CSCdt06919	Duplicate of CSCdt14045 ERR:Could not get LCN and data txfer stops after AXSM reset problem
CSCdt06424	Un-reproducible OC12 AXSM does not implement REI-L (M1) byte
CSCdt07611	Duplicate of CSCds03436 call to remove () file-1-01-Gen-080220001615 failed - fixed in 2.0.12
CSCdt07751	Un-reproducible After upgrading the node to Dec 19 image pnports in building VC
CSCdt08067	Closed - Spurious environmental alarms for DC supply reported
CSCdt09263	Duplicate of CSCdt08530 Adding 1:1 APS line between wrong ports does not give proper error - fixed in 2.0.13
CSCdt09827	Closed - not a problem.
CSCdt10244	Duplicate of CSCdt43371 OC48 APS switchapsln/switchred get chan mismatch/sig fail low - fixed in 2.0.14
CSCdt10300	Closed - not a problem
CSCdt11867	Un-reproducible - Several ports go to ilmi query after PXM45 switch over
CSCdt11967	Duplicate of CSCdt07366 Pnport goes to building vc state after del. Y-red and PXM45 switchover - fixed in 2.0.14
CSCdt13711	Un-reproducible - After powercycle the node got reset again
CSCdt14012	Closed - not a problem.
CSCdt15030	Un-reproducible - Switch sends trunk major alarm trap even though the trunk is ok
CSCdt26085	Un-reproducible - BPX interop- APS alarms do not clear when alram is removed
CSCdt28974	Closed - mini backplane was inserted incorrectly
CSCdt30112	Duplicate of CSCdt79626 SLT: OC12 1+1APS not W nor P-line displayed repeatively
CSCdt32565	Closed - not a problem.
CSCdt39357	Closed - not a problem.
CSCdt39405	Duplicate of CSCdt58554 Modify APS Event Log to make it more user-friendly.
CSCdt40961	Duplicate of CSCdt56312 APS intermittently fails to switching on OC48/OC3 (BI&NREV)
CSCdt41914	Closed - not a problem.
CSCdt42113	Moved to MGX1.
CSCdt43365	Closed - not a problem.
CSCdt44057	Closed - not a problem.
CSCdt47065	Duplicate of CSCdt56312 APS intermittently fails to switching on OC48/OC3 (BI&NREV)
CSCdt48530	Closed - not a problem.
CSCdt49516	Duplicate of CSCdt93669 - CWM bug
CSCdt58411	Closed - not a problem.
CSCdt60674	Duplicate of CSCdt41956 SAR failure/ssiFrameXmt failure error msgs in event log on switch
CSCdt61271	Closed - not a problem.
CSCdt66253	Junked - not a problem.
CSCdt67807	Duplicate of CSCdt57525 APS OC3 back card remove/insert caused protection chan stuck signal fail
CSCdt68993	Duplicate of CSCdt43371 switchredcd caused pnports to fail temporarily
CSCdt76337	Closed - not a problem.
CSCdt78433	Duplicate of CSCdt40561 SPVCs failed after upgrade due to cross-commit fail - fixed in 2.0.14

Problems Fixed in Release 2.0.13

The following is the list of known problems that are fixed in Release 2.0.13. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S2 Bugs
CSCdt02690	Symptom: Start sync, End Sync and APS Line Pair Sync with standby in progress popup messages appear at the cli prompt on a telnet session. Condition: When switchredcd command is executed Workaround: None
CSCdt09459	Symptom: Unable to 'cc' to active AXSM card. Condition: When user enters 'cc' command to initiate session to an active standby card, the following error occurs: Err: Unable to contact process in specified slot It is noticed that there are some minor HW alarm on the Humvee device with this problem occurs. This problem occurs once during testing. Workaround: None. AXSM card must be reset in order to recover from this failure.
CSCdt20186	Symptom: Connection cannot be set up. Condition: When a Generic Identifier Transport IE of an invalid length (more than 33 bytes including the IE header) is received, the whole message is discarded. Therefore, connection cannot be set up. Workaround: Avoid sending Generic Identifier Transport IE of invalid length.
CSCdt30096	Symptom: SPVCs were stuck in mismatch condition. Condition: Associated pnport was stuck in provisioning state Workaround: UNKNOWN
S3 Bugs
CSCds90459	Symptom: Event log has error messages like the following: 05-00017 12/12/2000-17:20:11 SSI-4-TMRCANCELINV E:05246 APSTask 0x80152bbc SSI Timeout event not found in ssiTaskTimeoutCancel. TmoFunc=0x8027aee8, key=5. Condition: Happens when APS is configured. Workaround: None.
CSCdt08530	Symptom: Attempt to add 1:1 apsline between wrong ports doesn't give cause of failure. Condition: Normal Workaround: N/A
CSCdt32121	Symptom: Presence of APS mini-backplane installed in MGX node cannot be found with runtime CLI. Condition: Customer cannot find APS mini-backplane by execution of CLI commands. MGX switch must be physically inspected to determine presence of mini-backplane. Workaround: This in an enhancement.

Problems Fixed in Release 2.0.12

The following is the list of known problems that are fixed in Release 2.0.12. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S1 Bugs
CSCds46636	Symptom: When a large number of connections get into alarm (like AIS) there is flood of activity on the cPro task, which also happens to handle the provisioning activity. When there is a simultaneous provisioning activity going on in the card, the task stalls because of a deadlock over resources. This is a very rare occurrence, but when this happens all conn. related CLI hangs. Solution: The provisioning activity is separated from the alarm handling activity using two different tasks. Workaround: None Frequency: One time occurrence.
CSCds55470	Symptom: PXM45 crashes after booting. Normally it is attributed to the telnet daemon task. Conditions: LAN boot IP address has not been configured. Workaround: From console, stop PXM45 in image startup at the prompt: Press [Enter] to skip initialization... Execute following commands: bootChange (setup inet address for lan) sysCardInit (bring the reset of image up) Once card is completely up, from cli re-execute bootChange command.
CSCds64523	Symptoms: After adding a port and a partition on the AXSM card, the pnport status shows "building vc" instead of "up". Conditions: (1) On AXSM card, perform addport and addpart. (2) On PXM, perform dsppnport, and the pnport status for the newly added port shows "building vc" forever because the control vc committing fails on the AXSM card. Workaround: None.
CSCds65556	Symptoms: The controller was out of memory and restarted. Conditions: Seems a rare scenario caused probably due to links repeatedly going up and down resulting in deroute plus reroute of 50000 SPVCs. Workaround: None.
CSCds73043	Symptom: Task suspends during its sync process. Condition: Sending a single buffer to peer under ipcMblk resource constrain might cause an exception since syncRam tries to access the memory which is taken by other task already. Workaround: None
CSCds84187	Symptom: After loadrev standby PXM45 keeps resetting Conditions: 1. forced download was ON or standby PXM45 did not have correct image file and 2. running an old boot code that does not have a fix for CSCds85557 Workaround: abortrev to bring up standby to old release. Make sure forced download is OFF
CSCds85557	Symptoms: Standby card continuously reset. Condition: When operator replaces the standby card with a PXM45 which has some upgrade configuration. Workaround: Execute "sysClrallcnf" on standby PXM45 only.
CSCds90529	Symptom: SSCOP links go to Release/Reset state causing all the connections to be rerouted/derouted or stay in fail state. Condition: SSCOP and PNNI links could be reset or released due to errors while re synchronization is happening. The connections are being removed from the Service Module (AXSM) causing SSCOP and PNNI failures. Workaround: Downing the port and upping the port again may resolve this problem.
CSCds92652	Symptom: Active AXSM card of a redundant AXSM pair got stuck in Init state after abortrev Condition: The other AXSM card of the pair failed to come up after a runrev was executed. An abortrev was then executed which caused both cards to get stuck in Init state. Workaround: reset both cards by using resetcd. Reset the primary first then reset secondary. If they are still stuck in init state, reset both again but now reset secondary first.
CSCdt04166	Symptom: AXSM card is restarted due to software exception. Condition: The AXSM card with 50 VTs resets due to the exception of the VSI slave task Workaround: None (Nothing at this point of time, may be reduce the ILMI links)
CSCdt04834	Symptoms: Some or all cards in the node failed to come up. The log shows the following errors: 01-00005 12/21/2000-16:38:42 DB2C-5-DBCLNT_CTCAPI dbClnt 0x8017063c Error 0 on call to ctcCntrLSlotNumGet 01-00006 12/21/2000-16:38:43 TRAP-5-TRAPCL_INVSLOT trapClTask 0x802831b4 Invalid Controller logical slot in "Trap Client Resolve Server Name" Conditions: Configuring the Node Name through the SNMP interface causes the PXM45 logical slot number to be changed to zero. Workaround: Do not use SNMP (e.g. CWM) to configure a node's name. Use the CLI cnfname command instead.
CSCdt05425	Symptom: A number of connections on an AXSM card went into Mismatch state. Condition: AXSM pair was upgraded from 2.0.10.2 to 2.0.11.3 Workaround: None
S2 Bugs
CSCdr50289	Symptom: XBAR plane available Multicast event buffer got corrupted. Condition: When XBAR plane available multicast is generated, which happens after standby inserted. Workaround: None.
CSCdr90786	Symptom: When a Primary Clock Source is intentionally deleted with the 0delclksrc command a clock alarm is reported by the dspndalms and the dspclkalms command that states that the Primary clock source is lost. Conditions: This symptom will occur when a Primary clock source is intentionally deleted with the delclksrc command. If a primary clock source is lost i.e becomes unlockable or has loss if signal; without user intervention then this alarm is reported as expected and that symptom is not an error. Workaround: None.
CSCds28502	Symptom: Given that the maximum number of users is 50 (3 default users + 47 users). If CLI command 'adduser' is used to add a total of 50 users on the active card, only the first 49 users will appear on the standby card. And if switchover or the standby card is being reset at this time, the standby card will fail to transition from INIT to STANDBY; 'ctcShow' shows cliRat is CTC_APP_INIT_DONE while the other applications are CTC_APP_STBY_READY. Furthermore, if FTP to the active card, the 50th or last user on the list will be deleted. Condition: Switchover, reset standby card, or FTP. (see above for more details) Workaround: Have at most 49 users; delete an user and reset the standby card.
CSCds36438	Symptom: Standby card does not come up after a restoreallcnf. Conditions: The database for the Standby card is corrupted. Workaround: Perform sysClrallcnf on the standby card. Frequency: One time occurrence.
CSCds41624	Symptom: After DS3 line was configured to PLCP and local loopback has been added, the line does not come up in clear state. Condition: When there is a PLCP failure, it should clear the DSX3NonTcaAlmMap bit so that the above symptom doesn't happen. Workaround: None.
CSCds47626	Symptoms: After running script to create 50K SPVC connections, there are some connections in FAIL state. dspcon on PXM45 show Last Fail Cause to be "no route to destination" on one end and "Cross Commit Failed" on the other end. Conditions: (1) In a three-node (NODE_EP1, NODE_VIA, NODE_EP2) network, nodes are connected linearly (e.g., two trunks connecting NODE_EP1 and NODE_VIA, three trunks connecting NODE_VIA and NODE_EP2). (2) Run script to create 50K connections from NODE_EP1 to NODE_EP2. (3) Some connections might failed to route. Workaround: none.
CSCds53634	Symptom: When a line on an OC-3 MMF back card of AXSM is down (using dnln) the laser is not turned off. The other end of the line does not declare LOS. Condition: This happens on all OC-3 MMF back cards of AXSM. This is a hardware issue and the investigation is in progress to determine the root cause. Workaround: None
CSCds54440	Symptoms: Some connections are not passing traffic. Conditions: Multiple service modules are reset one after another Workaround: Down and up the affected connections
CSCds54946	Symptom: VP Connections are slow to route Condition: There is no reroute handling of SPVCs & SPVPs. The reroute could have failed at the HALF commit if the connections was not previously deleted at the AXSM, due to last deroute failure. In this case, resources (vpi/vci) are not released. The VPI/VCI will stay in use. WorkAround: After sometimes, RESYNC detects the error and connection is cleaned up at the AXSM.
CSCds57511	Symptom: Active PXM45 may loose communication with all other cards on the shelf. All the links may go down. Conditions: This could happen during high activity on the PXM45 QE1210 sar, typically during resetsys of the node or resetsys of neighboring nodes. Workaround: Switchcc on the active PXM.
CSCds60742	Symptom: Seen log entries about time of date change for standby PXM45 periodically. Conditions: Normal operation Workaround: None.
CSCds61188	Symptom: After switchover from standby to active, the port rate of Resource Manager database is not the same as displayed by "dspport" or "dspports" command. This can cause Resource Manager to reject command that depends on available port bandwidth while the user think the bandwidth resource is OK from dspport. Condition: No noticeable condition. IPC failure has probably happened between Equipment Manager and VSI slave. Workaround: Use cnfport to force new min/max rate after previously standby card is active.
CSCds61193	Symptom: After switchover from standby to active, the newly active AXSM card does not report back card as unreserved to Shelf Manager when the last line of bay is downed (i.e. all lines on the bay is downed). When any line of bay is upped again, AXSM does not report back card as reserved to Shelf Manager. The Shelf Manager thinks the back card is reserved all the time. Condition: AXSM switchover occurs when at least one line on a bay is upped. Workaround: No workaround. Most likely, this effect is not noticed by user.
CSCds62771	Symptoms: Connection stays fail after port is down and now is up. Conditions: addcon when port is down then up the port within 2 minutes may result in connection stays fail (con in CALL_INITIATED state but not in any queue) Work Around: switchcc
CSCds63497	Symptom: TLB exception on one of the ftp tasks. Conditions: Noticed only once - on a heavy loaded system. On the PXM45 card only. Workaround: If redundancy is enabled, conduct a switchover. On a standalone card, you would need to reset the system. When the exception happens, one of the 4 ftp tasks on the PXM45 will no longer be available to process requests. Frequency: One time occurrence.
CSCds63635	Symptom: It takes a long time for some connections to route. Condition: When some parallel trunks have an insignificant reduction in bandwidth, so that PNNI does not distribute an updated PTSE. The master node continues to choose these trunks (equal to or greater than 3) and the connection cranks back 3 times, after which the same trunks are chosen again. After 30 minutes the PTSE update clears this problem. WorkAround: None
CSCds64258	Symptom: tstdelay and tstconseg takes an order of 2ms longer in some connection configurations. Condition: This occurs with tstdelay on dax connections. It also occurs with tstconseg that have ports physically looped back to another port on the same card. Workaround: None.
CSCds64282	Symptoms: One end of the dax conn doesn't show alarm, when a down port is executed on the other end. Conditions: When a dnport is executed, the other end of DAX connections doesn't go into alarm. Workaround: None.
CSCds66595	Symptom: cnfpasswd command does not sync up the standby card with the new password data. The data syncs on switchover, however if logging into the Stby PXM, the old password is still required. Condition: The problem is reproducible and occurs each time that cnfpasswd command is executed. Workaround: Until a switchover, the old password must be used to log into the standby PXM.
CSCds68426	Symptom: Sometimes, after non-graceful upgrade, some DAX SPVP stayed in failed state. Condition: Occurs sometimes after a non-graceful upgrade which accompanies a system reboot. Happens for DAX connections. WorkAround: None. Additional Information: dncon and upcon will recover the connection.
CSCds69511	Symptoms: SVC Based RCC in MPG networks will not get rerouted if the service class NRT VBR is not available. Conditions: If the service class NRT VBR is not available on a node in a different peer group or if the bandwidth in the service category is not enough for SVC Based RCC, the SVC Based RCC will not get routed on another service category. Workaround: There is no workaround to this situation except to make sure that NRT VBR is available on all nodes with the required bandwidth
CSCds69515	Symptoms: The Routing failure cause code sent in the Signaling Release message is always Destination Unreachable. Conditions: When Signaling on the source node or entry border node (in case of Multi Peer Group) has a problem in routing a call in the network, the cause code will always be returned as Destination Unreachable even though the cause for the routing failure might be different. Workaround: There is no workaround to this situation. The Release will not carry the right cause code.
CSCds69518	Symptoms: SVC Based RCC cannot be established on ABR service category. Conditions: When the service categories NRT VBR, RT VBR and CBR are available, PNNI tries to setup the SVC Based RCC with ABR as Service Class. But ABR call will fail at the source node or next node due to invalid IE contents. Workaround: There is no workaround to this situation.
CSCds69984	Symptom: Memory leakage in ILMI. Condition: This problem is seen when there is lot of ILMI activity. One way is to configure 60 VNNIs. dnallports followed by upallports will reproduce the problem. Workaround: None.
CSCds72034	Symptoms: SPVC connections are in AIS Conditions: Pull out and put back the cable on an UNI port Workaround: down and up the UNI port using dnpnport and uppnport cmd on PXM
CSCds74162	Symptom: Unable to create APS lines from CiscoView Condition: Condition was caused by an internal error in the code generated by SNMP research. After modifying this portion of the code (see SCM-note), the problem was cleared. Workaround: None.
CSCds74195	Symptom: clrchancnts command does not clear all the counts. Condition: Pass traffic so that the counters accumulate some counts and then stop the traffic. Now execute "clrchancnts" followed by dspchancnt. Ideally, the counters should show zero as there is no traffic. But the counters show some values. Workaround: Use clrchancnts after dspchancnt. The values will be cleared.
CSCds74267	Symptom: AXSM card did not come up after reset, log shows "failed to download image... reason SHM_DNLD_RMT_OPEN_FAILED" Conditions: Card was reset many times while downloading image. Workaround: Switch to standby PXM45 if available See CSCds72007 and make sure that forced download is not ON.
CSCds74270	Symptom: When performing Bulk Sync (when standby AXSM card first arrives), some VsiErrs were observed on the Active AXSM card and the standby AXSM card might not have all the connections. Conditions: This happens when intraslave connections (between two port) were added on the AXSM card. If one of the port was admin downed followed by inserting/resetting the standby AXSM card. WorkAround: Initiate another Bulk Sync (by resetting the standby AXSM card) after the port is upped.
CSCds74565	Symptoms: PNNI node name displayed in dsppnni-node is not the same as command prompt node name. Conditions: When the newly configured node name is a matching prefix of the old stored node name, the new node name was not written to the disk. So the PNNI node name won't show the correct node name. Workaround: Clear the old node name by typing a completely different node name and then try the new node name.
CSCds75107	Symptom: No access to node via ATM interface Conditions: Node SVC appears to be setup and running. From routers point of view, the SVC is not established, though. Workaround: Reset the SVC on the node. svcifconfig atm0 router <atm-addr> reset
CSCds77137	Symptom: Connection is not routed with master state as down vsi half and not in any queue and admin is up. Condition: dncon, upcon, rrtcon while there are lots of connection in the routing queue Work around: do another dncon and upcon
CSCds78209	Symptom: Adtech tester (or any CPE) sees CRC errors in half the ilmi PDUs in receives. Condition: qe48sar chip which does the SAr for ilmi connection, has PCI read problem. It sends multiple copies of same data, one correctly and others with no CRC field set. Workaround: This problem doesn't effect the normal working of ilmi, expect we may have problems or end up wasting some amount of bandwidth.
CSCds79085	Symptom: When a dsppnports CLI command is executed, the interface is in the state "building-vc". Condition: Multiple AXSM switchovers led to the problem. Workaround: Once the interface is in "building-vc" state, it can be got oper-up by doing a "dnpnport" followed by "uppnport".
CSCds79424	Symptom: Port stuck in building-vc. Condition: A card is pulled out and put back-in. Workaround: 1. Down the port and up it again, OR, 2. Pull out the card and put it back-in.
CSCds81546	Symptom: what happens with this problem is that on APS line, we transmit node status but the feeder don't see or response it back. So feeder status on our side is ADMINSTATUS = UP, OPERATION = DOWN, when you dnlmi and uplmi, the feeder status shows ADMIN=UP, OPER = UP, which is not correct. In addition, the feeder statistics show LMI is constantly transmitting DEGRADE msg. Condition: This happens when the OPER=DOWN, and you dnlmi and uplmi. The solution is when you uplmi, currently we assume the feeder is up automatically which is not correct. So we will assume the link is down, and it will discover the feeder through the node status. Workaround: Don't dnlmi and uplmi if the Feeder OPER=DOWN on AXSM side.
CSCds81990	Symptom: Upon trap verification, cwAtmIfSctFileAlarm (60356) does not provide correct value for caviFileId varbind. Conditions: User was configuring port i/f and sct from CLI. cnfport -if 22 -sct 99 User then checked CWM GUI OV Event Browser window for traps and expanded varbinds. Workaround: UNKNOWN
CSCds82333	Symptom: Call is released on one node but does not get released on the peer. Condition: Caused when lot of status enquiry happens when the nodes are highly congested. This happens very rarely. Workaround: clearing the connection manually.
CSCds83535	Symptom: visErr 0x9002 and 0x9003 timer delete error is display on AXSM Condition: PXM45 switchover might trigger AXSM send trap to controller but using incorrect timer value. Workaround: None
CSCds84546	Symptom: dsppnni-link doesn't take physical port id with subslot 2. Condition: Pass node index and physical port id (with subslot 2) to dsppnni-link to display nni link information. Workaround: None.
CSCds84573	Symptom: The GUI (CiscoView) and CLI command have inconsistent behavior for addport operation. The CLI did the IfNum checking within the addport command and echo the error message, but the GUI (CiscoView) just ignore the IfNum range checking. Solution: The CLI interface specific range checking for IfNum parameter has been removed. Instead the IfNum range checking common to both CLI and GUI has been added. Now the CLI and GUL share the same IfNum range checking behavior. Workaround N/A
CSCds86265	Symptom: summary display of tasks is awkward to get from CLI Conditions: Always Workaround: dsptask 1 2
CSCds87073	Symptom: Memory Block Error messages for an AXSM card appeared in the event log after a switchcc was executed. Condition: A switchcc was executed. Workaround: UNKNOWN
CSCds87127	Symptom: No SNMP response or lost traps after switchcc is executed on the redundant node. Condition: When user executed switchcc on a node that has redundant PXM, the standby PXM45 will become active but any communication with the switch via SNMP will not get any response. Or the standby PXM45 that become active might dropped the first few traps because it couldn't transition fast enough. The above problems above are very rare. Workaround: None
CSCds88236	Symptoms: The SSCOP reset happens after switch over to standby and connections get derouted. Conditions: During any resync failures on control VCs in the active, the standby doesn't know the failure and doesn't unbind on the LCNs. This causes an inconsistency with the VSI proxy and causes SSCOP to go down during switchover. Workaround: There is no workaround to this situation.
CSCds89112	Symptom: SPVC connection failed to come up after power cycle Condition: Slave connection has not been released while master still try to reestablish the call Workaround: Do PXM45 switchover using switchcc
CSCds89750	Symptom: Upon trap verification, cwChanAdd (60301) does not provide correct value for cwaChanVpcFlag varbind. Conditions: User was adding a slave connection from CLI with the following command: addcon 3 99 99 cbr1 s User then checked CWM GUI OV Event Browser window for traps and expanded varbinds. Workaround: UNKNOWN
CSCds90005	Symptoms: When SONET line medium is changed using "cnfln -sonet x.x -slt x" command, these error messages appear sometime: 0x82c7394c PhyTask 97 0x80373184 OC3 Board: unsupported timing source value... Condition: No special condition. This error occurrence is intermittent. Workaround: No workaround.
CSCds90091	Symptom: Card Number [8]: prompt presented on telnet session. Condition: This prompt is presented when user first telnets into node. It is a prompt that allows the user to log into a specific slot. Workaround: Hit carriage return to go to the default slot.
CSCds90343	Symptom: OAM traffic exists for deleted connections on ports. Condition: Customer added 240 SPVCs via cli and deleted the connections using CWM 10.3 connection manager. OAM traffic was present on the ports that previously had the connections after deletion. Execution of dspcons did not show any connections on cards. Execution dspvsicons did show existence of connections. Workaround: None
CSCdt00600	Symptom: Port go to building vc. Condition: This is found in MGX 8850 shelf, single AXSM reset (either runrev or reset cd or pull out/in the AXSM card) will cause port go to building vc. Work around: dnpnport / uppnport
CSCdt03684	Symptom: A pnport was stuck in building VC, preventing SVCs and new SPVCs from getting routed. Condition: An upport/dnport was executed on an AXSM port to get rid of some phony e-ais/rdi alarms Workaround: UNKNOWN
CSCdt04580	Symptom: Node shows PXM45/B card as mismatch when inserted as Standby card. Condition: PXM45A card is Active and PXM45/B card is inserted as Standby. Workaround: None.
CSCdt06911	Symptom: The pnport both side of the pnni-link goes to attempt state. The SSCOP on both sides is in established state. On one node the pnport goes to attempt state and link shows no remote node with remote node id 0:0:00.0000__. The other node pnni-link shows that the remote node is different than the node where this node is connected physically. There are no alarms etc on any of the pnport, SSCOP, port of the line of both nodes. Condition: The PNNI port goes into attempt when a delred, addred is followed very quickly by a switchcc. Workaround: The pnni-link remained in the attempted state forever. Then ppnport was brought down and up again. Recovery: By disabling the PNNI node using cnfpnni-node disable and re-enabling it the link can be brought up. This is NOT service affecting.
CSCdt07011	Symptom: addapsln allow user add 1+1 APS when working and protection line are in same AXSM card Condition: To add 1+1 apsln on intra card Workaround: To avoid this problem, user option 2 instead of 1 while adding APS line
S3 Bugs
CSCdp43597	Symptom: Confusing trap sent when voltage is above threshold. Condition: When DC voltage is above threshold an event is logged that specifies an "Above threshold" alarm. However, a "Below threshold" trap is generated. Workaround: None
CSCdr50889	Symptom: -dsplns command accepts junk as input parameter. Condition: dsplns command takes no parameters. Enter junk after dsplns on command prompt. It is accepted. dspports command is working fine. Workaround: None
CSCdr52270	Symptom: When a DAX connection is added among different interface ports and the same AXSM card, dnport and then upport on one end of the SPVC connection will cause connection checksum mismatch alarm instead of conditioned alarm. Condition: None Workaround: Problem is resolved. If it happens on earlier release, dnport and then upport on both connection endpts will bring it back to normal.
CSCdr69957	Symptom: Addition of New SPVCs are allowed even when number of configured VCCs exceeded Negotiated maxVccs value. Condition: When ILMI is enabled and negotiated mxVccs or maxVpcs are less than configured value. Addition of SPVC or SPVP are allowed. Workaround: NONE
CSCdr77019	Symptom: Memory allocation failure detected in statistics region on the PXM45 card. This is the SNMP region - region2. Conditions: On multiple resets on a specific AXSM card in the system, we might get into a situation where we are losing memory per AXSM reset on the PXM45 card. Workaround: None. Additional Information: In such cases, conduct a switchover to the other PXM45 card in the shelf. If you have a single PXM, reset the card. Note: conducting a reset on the PXM45 card will cause service outage.
CSCdr77941	Symptom: Debugging 'printf' messages are displayed. Condition: These messages are not meaningful to users and they occur, for example, when CLI commands are entered with invalid parameters. Workaround: No known workaround.
CSCdr88980	Symptom: SFrame tic lock errors are generated and the planes are not able to recover. Condition: At PXM45 shell, issue "xbarPxmPioSerClkEnable" or "debugger" Workaround: Issue xbarSFrameResync(xbarPslot, plane) at PXM45 shell to resync. each plane manually.
CSCds01758	Symptom: An incorrect error message is displayed on the CLI when the setrev command is issued. Condition: When attempting to do a setrev on an empty slot, an error message is displayed to indicate the file does not exist. This happens because the card type in the slot cannot be determined (slot is empty). Workaround: None
CSCds03436	Symptom: Call to remove a statistics file fails and an event is logged. This is an intermittent problem. Condition: Remove fails because for a 15 minute bucket interval, there are two files generated. As they have the same name (same interval), the file gets overwritten and there is only one file in memory. Two entries are registered for the same file as it was generated twice. For the first entry, remove is successful. For the second entry, remove fails. The cause of this problem is that there is a syncing problem with the ticks and the system clock time. Even though timeout happens after the specified number of ticks, the system time shows a lesser time. Workaround: None.
CSCds05239	Symptom: If quit in previous display for dspsarcnt - after that time, if dspsarcnt is done - no output is seen on the screen. The prompt is returned back. Condition: Happens every time user quits out of display of dspsarcnt. If however user does not quit - but types CR - then the problem is not seen. Workaround: Do not type quit during display of dspsarcnt.
CSCds06083	Symptoms: addport, addpart, delport or delpart commands can be rejected Condition: Vastier port data structure is not initialized at the time of port configuration, this causes garbage to be present in the port data structure, which sometimes turns out that the VSICore thinks that clock is configured, even though it was not. Workaround: None
CSCds11605	Symptoms: When adding connections right after performing a switchcc, occasionally, VSIErr 0x9003 is displayed on the AXSM console even though all connections are successfully added. Please note that this VSIErr is non-service affecting. Conditions: (1) In a three-node (NODE_EP1, NODE_VIA, NODE_EP2) network, nodes are connected linearly (e.g., two trunks connecting NODE_EP1 and NODE_VIA, three trunks connecting NODE_VIA and NODE_EP2). (2) Connections are established from NODE_EP1 to NODE_EP2. (3) perform a switchcc on NODE_EP1. (4) Right after the switchcc, add SPVCs on the UNI at NODE_EP1. Occasionally, VSIErr 0x9003 is displayed on the AXSM console even though all connections are successfully added. Workaround: Do not add connections right after performing switchcc. Wait for about 0.5 to 1 minute.
CSCds15141	Symptom: After the AXSM card resets due to watchdog timeout, You enter "dspcd n" command from the PXM45 console for the AXSM card in slot n shows UNKNOWN REASON reset reason. Condition: This is due to an invalid reset reason provided by the boot software from the AXSM card to the "dspcd n" command of the PXM. We modify the boot software for the AXSM card to provide the appropriate reset reason to the PXM45 during the AXSM power up. With this fix, you enter "dspcd n" command from the PXM45 for an AXSM card in slot n, the console displays the correct reset reason for the AXSM card instead of UNKNOWN REASON ass seen before. Workaround: none
CSCds15997	Symptom: When user does an addpart with a partition id > 5, the front end accepts the command but is never applied to the internal data structures. Condition: The internal data structures of RM had restricted the number of partitions to 5 (to conserve memory). The partition id mapped one to one with the partition index in the internal RM data structures. Since the partition id is restricted internally, there is no point in allowing for a larger value of partition id in the CLI/SNMP interface. Workaround: Do not provision partitions with partition id > 5.
CSCds16572	Symptom: AXSM card reboots and is stuck in failed state. Conditions: Trying to burn non-existent boot code. Workaround: None.
CSCds17159	Symptom: The data transfer fails in MGX 8850 node for data option with aesa_ping command Condition: This is caused when LCN binding is done before adding the LCN to LCN table. Workaround: None.
CSCds17564	Symptom: On execution of dsperr command using the "-en <errornumber>" option, data can be displayed for a different error number. Conditions: Execution of "dsperr -en <errornum> -sl <slotnumb>" where the shelf has experienced at least 100+ errors logged. Workaround: This indicates that the error files, 100 per card, have been overwritten due to the numerous errors being logged by the card. The workaround would be to catch the error as early as possible by doing the dsperr command.
CSCds20339	Symptom: When "cnfcdsct" command is executed with ports present, the error message is "conns are still present" instead of "down all ports before configuring card SCT". Condition: When "cnfcdsct" is called with any port in "upport" state. Workaround: Ignore "conns are still present". Go ahead and down all ports before calling "cnfcdsct".
CSCds25447	Symptom: There should be no visible symptoms for this bug. This bug is raised purely for code maintainability purposes. Condition: Not applicable. Workaround: Not applicable.
CSCds25483	Symptom: An active call which receives a Release-Complete message will fail to release the call in a particular case. Condition: This case may occur when a badly formatted Release-Complete message is received when the call is active. The data structures associated with the call will remain intact causing a dangling connection. The state of the call will erroneously show N0 state. Subsequent receipt of a Release message will also fail to clear the call fully. Workaround: The audit task which runs in the background periodically will clear the dangling connection.
CSCds26619	Symptom: When resetsys, dsplog -mod CC shows CC-4-SCALING and "active call already exist" in standby Condition: It happens with redundancy node that does resetsys Workaround: none
CSCds27960	Symptom: When working line cable is pulled and active line switches to protection line, "dspapsln" command "Alarm State" shows "Clear" even if "Working Line Pending Request" shows "SignalFailLowPriority". Condition: Working line fails. Workaround: "Working Line Pending Request" is correct. Ignore "Alarm State".
CSCds29751	Symptom: In a multi node setup, a call cannot be established fully. Before it is established, it gets released from the network. Condition: The CONNECT messages are not arriving in time for the call to be set up. Workaround: None.
CSCds30477	Symptoms: addaddr takes address matching host address. Conditions: Adding ATM address using addaddr. WorkAround: delete uni address matching host address and add unique address.
CSCds32847	Symptoms: When user not specify a CBR connection's CTD/CDV value, it shows in PXM45 as N/A while -1 in AXSM. Conditions: When you provision the CBR connection without specify CTD/CDV values. Workaround: Provision with CDV/CTD values.
CSCds33218	Symptom: TLB exception caused by a an invalid parameter. This causes an event to be logged and the interrupted FTP request must be retried. Condition: An ftp request is interrupted during logout. Workaround: None.
CSCds33855	Symptoms: Event log header in the event log being created is not complete. Cannot read logs from that file. Conditions: When a event log file is being created, PXM45 has been reset. Workaround: Event logs can be read on redundant PXM45 card.
CSCds35438	Symptom: The PXM45 and AXSM card does not support netmask for the IP of the ethernet device. When you issue bootChange command, the "inet on ethernet (e)" field can be entered with the following format: inet on ethernet (e) : a.b.c.d:ffff0000 a,b,c,d have value from 0 to 255. ffff0000 is the netmask which is not saved to Non-volatile storage device. When you entered the IP and netmask as shown above, the PXM45 or AXSM card cannot boot from network on the next power up because an invalid netmask (not the one you entered) is used. We allocate a portion of the Non-volatile storage device for software to store the netmask. And also software to validate the netmask you entered before save to Non-volatile storage device. This insure successful boot from network for the PXM45 and AXSM card. Condition: none Workaround: Do not enter netmask during bootChange
CSCds40655	Symptom: 1. For some successfully routed calls the Master end showed Last Fail cause as Invalid while the slave end showed SPVC Established. 2. No information on how the last fail cause field is being populated. Condition: None Work Around: None
CSCds43034	Symptom: A message appeared on the console when AXSM card is in Failed state. Condition: Injecting a hardware failure on SRAM component of Active PXM45 card manually. Workaround: None
CSCds45296	Symptom: dspconinfo was showing x lines of wrong state with x down SPVCs. This was happening because dspconinfo was not handling downed connections. So handling of downed connections will eliminate the problem. Condition: When ever there was downed connections and dspconinfo was executed, the Wrong state string used to appear. Work Around : None
CSCds45411	Symptoms: Address search fail errors are sometimes seen in the following setup... 1. NNI ports on different AXSM cards connected back to back with ILMI enabled on both ports. 2. One of the AXSM cards has a redundancy setup and the error messages are seen on that card. Conditions: The error messages are seen in the following cases 1. The port is downed (dnport). 2. The AXSM card is switched (switchredcd) 3. The peer AXSM card is reset. The address tables on the active and standby cards don't get synched up when a new address is added. As a result when an address has to be deleted it is sometimes not found on the standby. This problem does not affect the ILMI servicing any way because when an AXSM card switchover occurs the resynch process synchs up the address tables on the standby card. Workaround: None
CSCds53634	Symptom: When a line on an OC-3 MMF back card of AXSM is down (using dnln) the laser is not turned off. The other end of the line does not declare LOS. Condition: This happens on all OC-3 MMF back cards of AXSM. This is a hardware issue and the investigation is in progress to determine the root cause. Workaround: None.
CSCds54873	Symptom: After the AXSM switch over, if there were ilmi sessions been enabled, you will see a few ilmi messages. Condition: The data pane switch over faster than control pane, so we will start getting ilmi PDU on the newly Active going card just before the card goes to Active Ready. The message indicate them. Workaround: None
CSCds55631	Symptom: Whenever a port state changes - the change is not recorded in the event log. Condition: All port state changes. Workaround: None.
CSCds55684	Symptom: Message on AXSM console, RCV_DISP_TSK Rcvfailed due to length err msg. Condition: This is a harmless error that may occur anytime. Caused by a cell lost in the maintenance cell bus. Message will be retried. Workaround: None
CSCds55940	Symptom: Card alarm is generated when core redundancy is lost. Condition: Even when core redundancy is disabled using cnfndparms. Workaround: None
CSCds56244	Symptoms: The cause code in the Release message will not carry QOS unavailable when the end to end CDV or CTD fails Conditions: Whenever a call is initiated with an end to end CTD or CDV value which cannot be supported on the node, the routing failure cause code will be only Destination Unreachable. Workaround: Unknown.
CSCds57341	Symptom: Axsm may consider Multiple Bit error as One Bit error (CRC-8 is not sufficient to detect/correct One bit error) and tries to correct that. So it will come up with wrong VPI/VCI. If VPI/VCI are configured then data will be sent to the wrong destination. If VPI/VCI is not configured, dsplncnt will show invalid VPI/VCI. Condition: In the device configuration HEC is enabled to detect and correct one bit error. Workaround: Now HEC is disabled in device configuration. If problem persists then do the following at DIP, if available dad write 0x60= 5
CSCds58507	Symptom: dpscd and dspcds do not indicate upgrade status for the cards being upgraded Conditions: Initiate upgrades on a card set and use the dspcd/dspcds. The card show normal card states. Work Around: Look at the Prim/Sec/Current revision using the dspcd for each cards.
CSCds58799	Symptom: dsppnni-link command takes logical port as the input argument. Condition: It is the syntax for this command. Workaround: None. Use dsppnport <port> to get the logical port id.
CSCds58912	Symptom: CC alarm is not always reported. Condition: Enabling and Disabling CC multiple times on a connection may cause the CC alarm not to be reported. Workaround: None.
CSCds59341	Symptom: AXSM "dspcd" command always show reset reason as "On Power up". Condition: No special condition. Workaround: Ignore AXSM dspcd reset reason.
CSCds60757	Symptom: Crossbar alarm is observed. The alarm can be displayed using the CLI command dspswalm. Conditions: When switch cards (XM60, or PXM45) reset, transient Crossbar errors are present. After the switch cards come up, the error counters should stop incrementing (dspxbarerrcnt). Prior to the revision 2.0.12, the error thresholds are set low. Therefore, a false crossbar alarm might be triggered during switch card reset. The alarm can be ignored as long as the crossbar error counts are not incrementing continuously. This might be observed during upgrade because switch cards are reset during upgrade. In the revision 2.0.12 or later, the error thresholds are set properly. Work Around: None.
CSCds61205	Symptom: On a T3/E3 front card, it is possible to do an upln without a back card. The line would default to T3 mode. This causes confusion with the SHM which is not aware of the back card type until the user inserts a card. Condition: Stated above in symptom. Workaround: Do not "upln" on a T3/E3 AXSM card without inserting its T3/E3 back card.
CSCds62345	Symptom: System runs out of memory due to a memory leak. Condition: In rare cases, when we try to send out a SETUP message, we could have a situation where a packet is held up and never freed. Workaround: None.
CSCds63066	Symptom: One or more AXSM cards fail to come up while Standby PXM45 is coming up. Conditions: When an AXSM card is coming up while Standby PXM45 is coming up, the applications fail to complete the initialization on the AXSM card. This results in AXSM card failing to come up. Workaround: Reset the failed AXSM cards once the Standby PXM45 is READY.
CSCds63506	Symptom: No defect will be exposed to user. Condition: Not applicable. Work around: Not applicable.
CSCds63743	Symptom: popup of some messages interfere with the scripts. Non service affecting. Condition: Issuing the command switchredcd Workaround: None
CSCds64292	Symptom: When you issue sysBackupBoot from VxWorks shell of PXM45 card (pxm45>), the card reboot and then prompt the following: Press Return key stop auto-boot, d and Return for Diag... 5 This provides you the options to run (1) boot from LAN, (2) diagnostic, (3) backup boot. Condition: This condition occur to provide more boot options during development. Workaround: None
CSCds64751	Symptom: When you issue a bootChange command on the PXM45 or AXSM card and enter boot information, with the ethernet IP contains netmask as shown: inet on ethernet (e) : a.b.c.d:fff00000 The netmask field is not saved to non-volatile storage device. Therefore, The next time the PXM45 or AXSM card power up, the netmask is lost. We allocate non-volatile storage device to store netmask after you do the bootChange command so that it is available on the next card power up. This software release requires a requisite release which initializes the netmask field in the Non-volatile storage to a valid netmask value. Condition: none Workaround: Do not enter netmask during bootChange.
CSCds65569	Symptom: Unexpected popup messages are show on the AXSM console by default. Condition: Using the command cnfcdsct. Workaround: N/A
CSCds65600	Symptom: "CM_ASYNC_API: force resync start" msg being displayed on the console Condition: Whenever the force resync kicks in. Workaround: None.
CSCds66485	Symptom: dspchancnt gives wrong error message. Condition: dspchancnt on a admin down or oper down interface gives a misleading error message. It does not reflect the current state of the interface. Workaround: None.
CSCds66753	Symptom: When you issue bootChange command and enter the boot information for PXM45 or AXSM card, only a portion of the netmask information is saved to non-volatile storage device. The board network interface remains operational because a copy of the information you entered is saved in RAM. Only the copy saves in non-volatile storage device have incomplete netmask information. Each times the PXM45 or the AXSM card power up or reset, the boot information is retrieved from non-volatile storage device is with an invalid netmask. Thus, the board network interface becomes non-operational. We now allocate a portion of the non-volatile storage device sufficient to store the complete netmask information. Before we can use that portion of the non-volatile storage device, we initialize it to a valid netmask value. Condition: none Workaround: do not enter netmask during bootChange.
CSCds69631	Symptom: Debug messages are displayed as Error messages in log file Condition: With ABR calls and vsvd 0 Workaround: none
CSCds71026	Symptoms: aesa_ping setup timing out even after receiving connect. Condition: caused by getting wrong index variable. Workaround: Unknown
CSCds72007	Symptom: The AXSM cards always download the firmware image from the Active PXM45 disk. Conditions: If the node was previously running 2.0.2.x and upgraded to 2.0.10.x or later, the AXSM cards always get downloaded the firmware image from the Active PXM45 disk even though the AXSM cards have the image in their Flash. Workaround: Use the shell command gShmForcedSwDnldSet (<slot>, 0), where 'slot' is the physical slot number of the AXSM card, to enable AXSM card download the image from its Flash.
CSCds73161	Symptom: On Standby side some times we do see Trf Param: Broken link error in event log. No other functional effects Condition: This happens when sometimes traffic index is journaled to standby before traffic parameters. This should not have and side effect at all and act-stdby should be in sync. This is just a confusing error message and need not to worry. WorkAround: None
CSCds73759	Symptom: After APS is deleted, the previous working line shows "major" alarm state in dsplns command, but no obvious alarm in dspalm command. Condition: APS is deleted when the working line is in no alarm state but the working line is in critical alarm state. Unfortunately, the dsplns command does not show the separate alarm state of working and protection line, the two alarm states are combined to form a "major" alarm state. dspapslns should shown working line as "OK" and protection line as "ALM". Workaround: Do something that can change the alarm state of the line. For example pull the line out and in, or used loop command.
CSCds74043	Symptom: XBAR planes are shut down automatically. This can be displayed using the CLI command dspxbar. Condition: When the auto shut-down feature is enabled with the CLI command cnfxbarmgmt and XBAR errors are present. Sometimes, transient XBAR errors can also trigger XBAR plane shut down. The auto shut-down feature is not supported in 2.0x releases. The feature will be blocked in the release 2.0(12) in CLI. Workaround: Always disable the feature in 2.0x releases.
CSCds74734	Symptom: After using Esc Ctrl 2 to raise the priority of cli, and the session ended to restore the lower priority of cli, one of the tasks remained at a higher priority. This is only visible through "dsptask 1 2" cli command or through the shellconn "i" command. Condition: On the debug console only after raising the priority of cli using the Esc Ctrl 2 sequence. Workaround: There is no workaround. This will not cause a problem.
CSCds78275	Symptom: On the PXM45 console, user see SHM BRAM Checksum Error Condition: During bringup of a fresh PXM45 card with a different release than the existing database version. Workaround: None
CSCds79948	Symptom: The errno value for event logging by QE48SAR_EVENT was always -1. Condition: Enable event logging for QE48SAR_EVENT and check the log generated. Instead of displaying a meaningful errno, a "-1" was displayed always. Workaround: None.
CSCds80408	Symptom: cnfndparms CLI command for some options may prompt for value range but that is not the correct range for an option. Conditions: CLI command cnfndparms Workaround: Look at the help for an option to select value.
CSCds82118	Symptom: Control chars in file names' are printed as is during listing of the files. Condition: Accidental creation of file(s) with control characters in its (their) name(s). Workaround: None.
CSCds82216	Symptom: file descriptor is leaked Conditions: Any time an ftp session to the switch is rejected because the maximum session count has been reached Workaround: Don't open more than 4 ftp sessions at one time
CSCds83255	Symptom: No tracing of card-to-card multicast messages Conditions: Performing link trace on a slot. Do not see the multicast messages sent to that slot. Workaround: None.
CSCds83659	Symptom: When you dspcons on AXSM card, you will see a partial number of connections ended by a connection of vpi=4095 and vci=65535. Condition: This problem is reproducible and happens in any condition. Workaround: If the connection of vpi=4095 and vci=65535 is deleted, dspcons works okay then.
CSCds84064	Symptom: When connection is deleted from the feeder side. dspcons on AXSM card shows the connection as Abit Alarm but no AIS is generated towards the CPE. Condition: If feeder connection is deleted, AXSM card shows Abit alarm. But Abit alarm can be generated due to different reasons too. So from AXSM point of view, we cannot say for sure that connection is deleted from feeder. Workaround: Do a dspcons on feeder side and verify that the particular connection does not exist. The fix does not affect the existing behavior. But after this fix, AXSM card will generate AIS towards CPE on receiving a deletion D-bit from feeder. A bit alarm will be seen on the connection as before.
CSCds86283	Symptom: dsprevs shows current revision for empty slot Condition: After AXSM and PXM45 card removable, issue dsprevs command Work around: None
CSCds86860	Symptom: tSyncRamDb error logged in error file while burning new boot on the PXM45 card. Condition: This condition occurs when a new boot is burnt on the PXM. Workaround: Unknown.
CSCds87038	Symptom: dspdiagcnf, dspdiagerr and dspdiagstatus commands do not break after 24 lines. Condition: Normal Operation Workaround: UNKNOWN
CSCds87474	Symptom: Telneting from one node to other node causes displacement of command prompt. It is not service impacting error. It is just a display issue. Condition: Using CLI 'telnet' command to telnet from one node to another node. Workaround: No known workaround.
CSCds87628	Symptom: Fan tray alarms not reported correctly. Condition: User execution of dspenvalms clearly shows that there are no fan trays present, yet it is not being reported as an alarm. Traps are also not being sent to CWM appropriately. Workaround: None
CSCds88098	Symptoms: When svcifconfig atm0 local 47.0091.8100.5670.0101.0101.0101.0101.0101.0101.01 it gives ERR: svcifconfig: local AESA not in DOWN state (UP) for atm0 Condition: After giving svcifconfig atm0 local 00.0000.0000.0000.0000.0000.0000.0000.0000.0000.00 dspsvcif atm0 is in Up state. Then when svcifconfig atm0 local 47.0091.8100.5670.0101.0101.0101.0101.0101.0101.01 it gives ERR: svcifconfig: local AESA not in DOWN state (UP) for atm0 Workaround: Issue commands to disable and then enable SVC connections on interface to clear condition: ipifconfig atm0 nosvc ipifconfig atm0 svc
CSCds88721	Symptoms: When system rebooted without any fan trays, no alarms or traps generated. Condition: Both fan trays are uncabled or physically removed. Workaround: None
CSCds91241	Symptom: When there is an active PXM45 in the shelf and you insert a PXM45/B into the same shelf. The active PXM45 receive card type from the inserted card as PXM45 and not PXM45/B. Condition: none Work-around: none, code fix in place.
CSCdt00594	Symptom: When Injecting LOF from an OmniBer Test set. Initial dspalm -sonet 1.6 shows Section Alarm State: LOF. This is fine. However, when clearing the LOF on the OmniBer, it still shows LOF when entering the command "dspalm -sonet 1.6" Condition: The cause of the problem was due to the fact that when LOF is cleared, there were still no messages being sent to EM to update the change of the status. Workaround: The fix was implemented in the file, "sonet_line.c" in the section where it sends a message "RED_ALM_CLEAR_EVT". Instead of the "and" condition, the conditional checking should have been "ORed".

Problems Fixed in Release 2.0.11

The following is the list of known problems that are fixed in Release 2.0.11. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S1 Bugs
CSCdr70497	The active PXM45 card takes over 10 minutes to present the login prompt, and meanwhile, the standby PXM45 is reset multiple times automatically.
CSCds07776	The Standby AXSM/PXM45 fails to come up and is put in FAILED state.
CSCds16063	SPVCs do not get routed.
CSCds22416	The problem will cause UBR calls to fail
CSCds24309	Switchred repeatedly will cause one of the APS sides to have the following configuration J1.3.AXSM.a > dspapsln 3.1.5 Working Index : 3.1.5 Protection Index : 4.1.5 Provisioned Arch : 1+1 Provisioned Direction : bi Operational Arch : 1+1 Operational Direction : bi Active Line : working WTR(min) : 5 SFBer 10^-n : 3 SDBer 10^-n : 5 Revertive : Yes Last User Switch Req : ForcedW->P Bridge State : WChan Bridged Selector State : Selector Released Protection Line Pending Request : SignalFailLowPriority Working Line Pending Request : None APS Trouble Mask : ProtectionSwitchingByte,ModeMismatch Bit Map Req Field Chan Field Transmit K1 0xc0 Sig Fail Low Null Channel Receive K1 0x20 Reverse Request Null Channel Current Request 0xc0 Sig Fail Low Null Channel Bit Map Chan Field Arch Field Dir Mode Field Transmit K2 0x5 Null Channel 1+1 BI Receive K2 0xd Null Channel 1:1 BI Alarm State Clear
CSCds24374	The card goes to Failed state after 3 SW/HW error resets, with reason SHM_CDF_MAX_RESETS_REACHED.
CSCds26049	Standby Card in continuos reset with HW monitor task crashing with TLB exception
CSCds28030	CWM will not be able to read the SCT file from the disk.
CSCds33324	PNNI can't detect bad clock source.
CSCds34606	switchredcd <from-slot> <to-slot> with large and invalid value for from or to slots would cause PXM45 to crash then switchover.
CSCds34659	Shelf Manager task got suspended.
CSCds34714	After executing a "resetsys" command, on a system with 12 standalone (non redundant) AXSM cards and 2 PXM45 cards (slot 7 and 8), the ACTIVE PXM45 card coming up (after the resetsys) might experience going into an ACTIVE-F state. This will cause a switchover to the other PXM45 card as soon as the other PXM45 card is available (i.e. gone to STANDBY state).
CSCds37401	In a redundancy configuration, repeated valid and/or invalid addred/delred commands may corrupt the back card type. This will be seen in dspcd in AXSM or PXM. Subsequent valid addred commands will be rejected because of back card type mismatch.
CSCds40915	pnCcb task gets suspended
CSCds44402	After a switchredcd, newly active card could not become active ready (see i at CLI prompt) and both cards in redundant pair get reset after a about 5 minutes.
CSCds45313	Active PXM45 card got soft failure (Active-F) when using CLI command of "dspcds". Standby PXM45 card is also not coming up. The system will come up the error message like pnRedman task is running away CPU.
CSCds46519	ilmi task crashs and card may reset.
CSCds47673	On the affected interface PNNI protocol will be in "ATTEMPT" state and no connections can be routed over this trunk. SSCOP protocol on an affected interface will show "RESET" state. On a PNNI link either PNNI or SSCOP or both might be impacted.
CSCds50617	The Standby PXM/AXSM card fails to come up.
CSCds51901	Floating point exception and system gets reloaded automatically.
CSCds52919	PXM45 could crash due to SAR Link list access invalid Pointer. This problem is caused by the changed in CSCds38562, where we cleanup the HUMVEE ILT and ELT table entry The ILT table is not protected so ILT table could delete more than once, once by proxy slave and another by PNNI, when they unbind the GLCN.
CSCds56700	In a single PXM45 node, after runrev is done the PXM45 card resets 2 times and comes back in the older revision
CSCds57024	The SSCOP is not in Established state or the PNNI link is not up and running though the port status as seen on the controller shows as up and good. The Control VC connections are missing on either or both the slave cards.
CSCds63376	Axsm card resets while attempting to read sct file.
CSCds64807	After you add the connections, then you change the number of LCNs in your partition, if the number of the connections is more than LCN number, some of the connections would be failed. If you reset the Service module, the connections failed routing may be no deterministic. That is, before routed connection may be failed while some failed connections may be successfully routed.
CSCds65556	The controller was out of memory and restarted.
CSCds68882	When upgrading from 2.0.10 or earlier AXSM image to 2.0.11 image, both active and standby can get reset.
CSCds71908	When you enter sysBackupBoot at the command shell prompt pxm45> of a standby PXM45 (where two PXM45 cards installed in the shelf) or from an active PXM45 (where only one PXM45 installed in the shelf), the command prompt does not come back. Furthermore, the PXM45 does not get into backup boot.
CSCds76260	Traps are not being received from the switch. Some traps are getting lost - or no traps are being delivered.
S2 Bugs
CSCdr50503	Command Line Interface (either via a telnet session or via the console port) will hang indefinitely using lkup "bit"'m
CSCdr78869	Events of type "CHUNKNOTOWNER" are logged in the event log.
CSCdr89686	Upon deletion of a secondary clock source with the primary clock source already bad, the node tries to lock to the Primary (even though it is bad.)
CSCdr94471	Standby PXM45 card gets reset 3 times and stays in Failed state.
CSCds01593	After issuing an "upln" or "dnln" command, the CLI prompt does not appear to be displayed.
CSCds08941	While performing SPVC deroute (initiated at NODE_VIA, the AXSM card in node NODE_EP1 (AXSM card slot 2) showed IPC allocation failure.
CSCds09512	AIS is not generated when dnport issued on AXSM card
CSCds09604	On an initial boot up of two AXSM cards. After both cards are booted, redundancy is added. Then you add APS for the intercard case. With this scenario, the trap generates 60126 when the fiber is already moved prior to adding APS. 60126 implies APS Redundancy Alarm.
CSCds09708	SNMP GETs on the following variables:
CSCds12955	Calls not routed after setrev
CSCds13444	The following message is generated in the event log: 08-06262 08/23/2000-15:06:51 SYS-3-RUNAWAYTASK E:02239 tRootTask 0x80132248 Task 0x3f008c[tTnInTsk01] is running away on CPU - logging task.
CSCds13984	addlnloop command is getting executed when addln is entered. The parser does not check for the exact command entered. The nearest match is returned.
CSCds14832	Two nodes (Feeder and another with T3 line, line type PLCP) are interconnected to each other, upon disconnection of T3 RX/TX cable and reconnecting back, AXSM T3 line showed RcvRAI alarm. Feeder side showed communication Failure.
CSCds16776	The conn pending congestion counter shows negative values.
CSCds17876	The node allows SPVCs with VCI less than 32 to be added.
CSCds18258	Some connections are not able to reroute, reroute is not even being attempted; i.e. connections are not routed.
CSCds18328	The switch has changed the default value of SvccVci from 32 to 35. This has not been reflected in the MIB variable 'cwspMinSvccVci' in "CISCO-WAN-SVC-MIB.my".
CSCds19314	The dsppnports on PXM45 will show ilmi state as autoconfig but AXSM is in UpandNormal state or on PXM45 ilmi will be showed as disable when it was really enabled on AXSM.
CSCds20504	This behavior is seen when the APS operates in bidirectional mode. The side which sees a channel mismatch failure will go to the selector released state. The other side remains in the protection line selected state.
CSCds23341	Vsierr 0xe007,... is displayed on the screen
CSCds23518	Cell bus connection between PXM45 and AXSM card is lost, AXSM card is reset.
CSCds23525	Pnni-link port is in attempt state.
CSCds23579	Occasionally, when downing a UNI port (dnport) on AXSM card after dnpnport and uppnport on the PXM, some VSIErr are displayed on the AXSM console.
CSCds24399	switchredcd following by a switchcc could make the old active service module stuck in boot state _ the old standby service module is OK and in active state.
CSCds25413	In a node with thousands of SPVC calls, deroute of calls followed by a reroute is very slow.
CSCds25534	Connections are not able to route due to running out of trk vpi/vci even vpi/vci should not be running out
CSCds26981	The AXSM card fails to come up as ACTIVE. After 3 attempts, it is put in FAILED state.
CSCds28316	A nni port with ilmi on is stuck in auto cfg.
CSCds28453	When a dncon / upcon is performed on an endpoint, the connections' upload counter is not updated. Use dspcons to see the upload counter.
CSCds28520	OC48 Card CLI hangs, and one cannot execute any commands.
CSCds30075	The PSB condition caused by any condition other than the invalid code is cleared even though the PSB condition has not disappeared.
CSCds30425	An AXSM card may be reset immediately after a PXM45 switchover.
CSCds30710	Standby OC-48 card stuck in reset init state.
CSCds30721	LCN resource not available and connection commit keep failing
CSCds31496	Root task could not delete a suspended task.
CSCds32205	User adds feeder on an interface on which connections exist
CSCds32276	No immediate symptom. Over time when many addapsln/delapsln/dspapsln commands have been executed, we may get IPC message allocation errors.
CSCds32318	Line shows that there are some statistical alarms, although, the line has no defects. There are no adverse effects of this.
CSCds32413	After a addred or switchredcd, there may be alarms on some channels in the Active AXSM card.
CSCds34183	The symptom is that the VSICore and RM database are not in sync. The vsicore indicates the connection is in committed state, and RM is in reserved state.
CSCds34687	The VPI range will be 0-255 for NONE port even the AXSM port is a NNI. This blocks the user to use the VPI bigger than 256.
CSCds35591	swichred on PXM, standby becomes active, reset the newly standby PXM,
CSCds35710	In a node with thousands of calls, we see that the unacknowledged status enquiry counter is beyond the threshold value. This is seen using the command dspintfcongcntr for a particular interface.
CSCds36145	Getting incremental RAM Sync send error after line/port/partition commands are executed. See description for display details.
CSCds36182	During AXSM switchred, previously standby card gets PHYTask exception while transitioning to active. Ports go into provisioning state.
CSCds36677	After AXSM card sends a passup command to the controller, the message counter doesn't increment for the passup cmd message.
CSCds37301	ports in standby card stay in "vc failure"
CSCds37761	The Active PXM45 gets a software exception and resets unexpectedly when a file is transferred onto the Active PXM45 using FTP.
CSCds38135	dspenvalms shows DC Level outside of threshold range, but no node alarm generated
CSCds38320	Some SPVC connections will not be routed and stays in fail state
CSCds38562	Two GLCN programs the same ELT Entry in HUMVEE. HUMVEE will indicates ELT Mismatch, no traffic will be passing through.
CSCds39375	A nni port has a vpi range of (0-255) available instead of the complete range (0-4095).
CSCds41314	Alarms show up in dspcdalms <slot> for the standby card after a switchred.
CSCds41496	Resources are not updated for a trunk even after connections have routed along them. This is visible in the dsppnportrsrc command. Connections may not route along expected paths.
CSCds41592	Before switchcc, take the physical connection out (ex. 3:1.1:1). dspclksrc Primary clock source: 3:1.1:1 Primary clock status: bad Primary clock reason: no clock signal Secondary clock type: generic Secondary clock source: 14:1.1:1 Secondary clock status: ok Secondary clock reason: locked Active clock: secondary source switchover mode: non-revertive After switchcc Primary clock source: 3:1.1:1 Primary clock status: bad Primary clock reason: not configured Secondary clock type: okay Secondary clock source: 14:1.1:1 Secondary clock status: not configured Secondary clock reason: okay Active clock: internal clock source switchover mode: non-revertive
CSCds41617	Receive RAI count is not cleared by clralmcnt command.
CSCds41628	Power supply failure does not generate a node alarm.
CSCds41931	Connection routing failure due to AvCR being zero on PNNI link that previously was out of LCNs.
CSCds42022	Trap 60004 cwShelfRestart was not received after a node reset from CLI "resetsys" command.
CSCds44016	When SPVCs are tunneled through an DAX-SVP connecting two VTs configured with different VPIs, the connection will not be accepted.
CSCds45150	Port gets stuck in down in progress.
CSCds45453	Standby AXSM card gets reset multiple times before it becomes standby ready
CSCds46551	When a large number of IISP trunks are configured on the node and a switchover is attempted, system goes into busy state.
CSCds47500	No event logging is done for APS.
CSCds47575	Any command on the PXM45 that accesses the disk will pause for a couple of minutes and displays nothing. Also, any file transfer to the PXM45 disk will fail. Also, an AXSM card fails to load an SCT file and uses default traffic parameters.
CSCds50779	Some connections are derouted and rerouted continuously.
CSCds51173	In a MGX 8850 node, we might have a case where traffic on an SPVC DAX connection cannot be passed though the connection is in OK state on the PXM.
CSCds52449	Configuration on active AXSM card is destroyed.
CSCds52468	The ILMI address will not be sent to PNNI for advertisement.
CSCds52601	With T3 back card, "addport" or "cnfport" commands fail with min/max port rate at max T3 cell rate (96000 for PLCP mode, 104268 for ADM mode). "dsplns" does show the lines as T3 lines and not E3.
CSCds52916	VTs are still up even when the uni endpoints on spvp tunnel are brought down.
CSCds53212	Active and Standby system were out of sync with each other from PNNI controller point of view. Active side of controller doesn't know that standby is exist.
CSCds54891	Previously standby AXSM card cannot transition to active ready state after switchred is performed.
CSCds55452	The problem was handling crankback when VP resources are not available.
CSCds55584	SPVC connections FAILED to route. the Last Fail Cause to be Call Rejected.
CSCds57279	No traffic passes, PNNI link does not come up, when NNI trunk is configured with a minimum Vpi greater than 255 over an OC48 line.
CSCds57791	Failure to configure the clock source.
CSCds58806	The problem was an unexpected routing failure where some calls never get routed.
CSCds61572	When "dsplns" or "dspln" is executed, there is a "?" in the Frame Scramble field. The line does not come out of alarm by adding physical loopback on back card or terminal loopback with "addlnloop" command. Resetting card does not get rid of problem. "dspcds" on PXM45 shows "Active-F" for the slot.
CSCds62686	Some of the ports are in Building VC state after one of the service module cards are reset.
CSCds63119	When SHM could not update its database to standby PXM, SHM just logs an error. It should reset standby PXM45 to recover.
CSCds72181	When the active PXM45 powers up, it stays at the pxm45> prompt with an error message printed saying SHM_BRAM_VER_MISMATCH.
S3 Bugs
CSCdr45241	Selecting the front card for testing based in the command syntax given by diagnostics produced an "Invalid syntax" message.
CSCdr45875	Even with "pagemode off" in effect some CLI command output still pause in the middle with the prompt "Press <CR> to continue, Q<CR> to quit:"
CSCdr86751	AXSM card does not detect loss of cell delineation (LOCD), therefore not generating RDI as a result.
CSCdr91962	No mechanism to clear a portion of a node's configuration.
CSCdr95809	When a command name is abbreviated, the prompt is issued, "Do You Want To Proceed". without including the full command name.
CSCds05064	Revereved back card alarm missing alarm persists.
CSCds05178	Under certain situations, the restoreallcnf may fail and the node's configuration is not restored.
CSCds12357	pnCcb takes too much (75-85%) CPU time
CSCds13955	The dspcds, dspcd and dspcdalms do not show the same alarm information.
CSCds15147	The connection summary information displayed by command dsppnport wraps after 80 columns (the output exceeds 80 columns).
CSCds16241	output from CLI command dsptasks scrolls off screen
CSCds16452	dspnodalcongth/cnfnodalcongth: some keyword does not match. The threshold names in these commands were different. For consistency and documentation purpose, the threshold names were made same.
CSCds17195	dsppncon command displays SCR and MBS values for CBR and UBR calls.
CSCds17592	Configuration commands cnfspvcprfx cnfilmienable cnfnodalcongth cnfabrtparmdft cnfrrtparm execution is allowed on standby card.
CSCds21295	dsplog -task dbClnt will show error sometimes during switchcc of two MGX 8850 PXM45 cards.
CSCds21451	User is allowed to add feeder on a VNNI trunk.
CSCds26368	AXSM card remains in Init state.
CSCds26640	cannot configure the clock sources.
CSCds27986	When "dspapsln" command is executed using protection line ID as input, the working line ID is same as protection line.
CSCds31066	Risky commands such as shutdisk are available and are not needed.
CSCds31146	No mechanism to display current community string value.
CSCds32730	Programming the backplane NOVRAM on an MGX 8950 backplane fails with a write error.
CSCds33798	On a resetsys, the event was not logged indicating the command and username.
CSCds33824	Currently when we try to delete clock, it is an implicit set. This will take longer for the clock manager to re-lock the clock source.
CSCds34234	When PNNI controller sends a msg which is not recognized by the slave, we send a general Response error msg to the controller. Within the response msg, there is slaveCode which VSI Slave copy the msg header sent. Since the Msg header contains LLC-SNAP header, so VSI Slave copy that as well. But PNNI controller don't interpret SNAP Header.
CSCds34340	When you give incorrect value for the line option, it complains about incorrect value for the following option instead. There is no destructive effect of this error.
CSCds35712	PNNI link is in attempt state.
CSCds37762	After executing addlnloop command on AXSM card - the event is not recorded in event log.
CSCds40637	SNMP responses and SNMP traps being sent out the incorrect network interface.
CSCds43543	When a switchcc is executed, the following messages appear on the console port of the PXM45 that transitions from standby to active: go_active, sync_flag=1 SPVC transiting from Standby to Active
CSCds43550	Pop up messages were seen during configuration of SPVC with cnfcon command Install has both Legs A(1011801,13,102) and (10c1801,0,42)Configuration successful
CSCds44287	No particular symptom. AXSM Diagnostic may cease to run.
CSCds48531	This was noticed in a customer beta trial. The dspcons on AXSM does not show any alarm. However the dspcdalm <slot> on the PXM45 would display chan alarms for that particular slot. This would translate to a node level alarm in the system;
CSCds48589	Multiple switchred can trigger XBAR remap twice error. The error is also reported to alarm manager. "Card Crossbar" major alarm will be registered.
CSCds49105	Taking the standby PXM45 from one node and placing into the standby of another node can cause the LAN interface of the old node to become disabled.
CSCds51524	The different values of K1 when doing switchred and when removing cards is cleared when the redundant card comes up.
CSCds51688	dspcdalms shows alarms for a card in a particular slot (reported by the card) and dspslotalms shows alarms for the slot reported by the shelfmanager.
CSCds57341	Axsm may consider Multiple Bit error as One Bit error(CRC-8 is not sufficient to detect/correct One bit error) and tries to correct that. So it will come up with wrong VPI/VCI. If VPI/VCI are configured then data will be sent to the wrong destination. If VPI/VCI is not configured, dsplncnt will show invalid VPI/VCI.

Problems Fixed in Release 2.0.10

The following is the list of known problems that are fixed in Release 2.0.10. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S1 Bugs
CSCdr70591	The SRCV task in AXSM gets an address exception.
CSCdr74831	Receive 60905 or 60904 trap as soon as CWM requests for a config upload file.
CSCdr87841	Vsi master fails to recover on trying to commit a connection on an existing vpi/vci.
CSCdr88211	PXM45 fails to send config message to slave.
CSCdr89807	Configure an address filter and associate it with a port. Do not have any addresses added to the filter. Make incoming and outgoing SVC/SPVC calls through the port. System may restart.
CSCdr99509	SNMP MIB Walk fails even though the cards are in active state.
CSCds01070	CWM did not receive trap 60901 to let CWM know that File creation has been started.
CSCds03375	Cpro shows status indicating AIS state when no AIS state exists.
CSCds05585	When addpart or and "set partition" type command is executed for VT (VNNI) ports, AXSM card gets SW exception and resets.
CSCds07804	The problem is an unexpected system reload.
CSCds09032	When connection reroute is triggered from CWM, the operation would fail
CSCds09374	When pulling out an active AXSM, PXM45 goes into reset
CSCds24374	The card goes to Failed state after 3 SW/HW error resets, with reason SHM_CDF_MAX_RESETS_REACHED. These three resets have to be within a period of 100 hours.
S2 Bugs
CSCdp73120	When adding asymmetric connections, meaning local traffic parameters are different from remote traffic parameters, AXSM card doesn't handle it correctly. Inconsistent traffic load info will be seem be doing dsppnportrsrc.
CSCdr50497	dspsct command does not display proper information.
CSCdr71440	Currently, if a SHM/CTC message protocol timeout occur, only an error is logged. The card will eventually be reset. The timeout for this may be up to 1.5 hours. If the protocol error occurred during a node power up against an AXSM card, the AXSM will be stuck in the INIT state; in addition, the STANDBY PXM45 card may be affected by this, and may get stuck in the INIT state also.
CScdr74604	On one of the nodes in a devtest network, a few connections were reporting an egress AIS alarm even though the connection was perfectly passing traffic. This gave a false impression of failure to the user.
CSCdr74850	Trap managers don't see any trap for PXMs switch over.
CSCdr75239	During the powering up of a standby PXM, the disk is marked "disk not ready" temporarily while the disk sync is being performed. During this time, the Disk Not Ready alarm is reported under the slot alarm category. There is also an alarm category called disk alarms which is not being utilized at the moment. Thus the disk alarms count is shown as zero.
CSCdr75434	Some SPVCs will appear as failed even though the connections are active
CSCdr77408	uni or nni port state goes up and down intermittently.
CSCdr77525	To reproduce this problem, 1. add a partition, and PXM45 cli> cnfpnportcac port-id cbr -minbw 50 AXSM sh> rmPartDtlInfoShow. 2. AXSM cli> cnfpart.... -emin 100000 3. AXSM sh>rmPartDtlInfoShow will shows the interface policy info in each cos has been reset to wrong values.
CSCdr82076	dspcdalms command does not break after 24 lines to give user an option to either continue display or quit.
CSCdr85279	SVC connection is constantly torn down and rebuilt. This causes intermittent outages between node and CWM.
CSCdr86184	Applications complaining about IPC message allocation failures due to IPC message leak.
CSCdr86324	Standby card will be waiting in Init state
CSCdr86680	Event log entries indicating IPCONN could not send message to vcid 0.
CSCdr89700	When dspswalms/dspslotalms commands are used to display alarms, displays are inconsistent when there are alarms present compared to when they aren't present.
CSCdr90786	When a Primary Clock Source is intentionally deleted with the delclksrc command a clock alarm is reported by the dspndalms and the dspclkalms command that states that the Primary clock source is lost.
CSCdr91277	A redundancy-deleted trap is sent with secondary slot number set to zero.
CSCdr93427	The Cross bar status displayed by the command dspxbarstatus does not reflect the correct status.
CSCdr93676	getone on an instance of caviStatEgressTable object does not return the value.
CSCdr94049	The message "Function ssiTaskDelay called by ISR." may appear in the dsplog output.
CSCdr94469	Message Of IPC Allocation failure seen on the console
CSCdr94654	Event log messages are not generated.
CSCdr96243	After about 75 (out of the 100) ports issued the above error message, PXM45 would temporarily lock up (for about 40 sec) and then continue.
CSCdr97659	For a Service Module that supports master agent/subagent agent architecture, its subagent MIBs need to be un-registered from the master agent when it is removed, reset, failed, switchredcc, etc. Otherwise, MIB walk will hang/timeout since the master agent sees the registered subagent MIBs and continue to send requests to a Service Module that may be physically removed, failed, or rebooted/reset and did not come back up successfully.
CSCdr97665	Failure condition for addred/delred from CWM will always indicate a general error.
CSCdr99149	Frame discard field comes as 0 when it is disabled. It should be 2.
CSCds01843	Link goes down and up when ilmi is enabled in IISP
CSCds02379	After a setrev or a soft reset, a NOVRAM will be corrupted. The specific symptom is a failure of the checksum verification.
CSCds03654	When the networking controller NAKs a connection provisioning request (due to lack of resources/invalid parameters), the proper error string is not presented to the user. This happens only when using the CWM.
CSCds03787	User can't modify cdvt of slave endpoint of dax con. Also, in the case of MGX 8850 node, when user modifies cdvt of master endpoint of dax con, the slave endpoint then is assigned cdvt = -1.
CSCds03927	setrev causes a card reset regardless of card state when the command is issued at the CLI prompt. Card will become unusable during the burnboot since the flash is corrupted.
CSCds03954	When user enters the command "dspvsicons -cksm 0" the CLI task would take an exception.
CSCds04883	The trap oid for cwIfIndex is wrong.
CSCds05071	MIB Requests(Get,Set, Get-next) comeback with NO SUCH INSTANCE error.
CSCds06500	1. When adding signalling channel, ingress ecr is not calculated. 2. After change booking factor, only ingress card load changes, ingress part load stay the same.
CSCds07835	OC12 card result in wrong cell delineation because of the wrong C2 byte configuration.
CSCds09194	If tstdelay is not successful for a given connection, then all subsequent attempts for performing tstdelay on that connection will fail with the reason "test in progress".
CSCds09375	When pulling out an active AXSM, PXM45 goes into reset
CSCds10319	There was buffer overflow in one of trace msgs. if the attachment point change doesn't happen, then ilmiTask will be fine. The ilmiTask fails only when it tries to print an error message.
CSCds10564	When connections enter into "mismatch" state on the AXSM, alarm traps are generated to the CWM to indicate this. Also an alarm file on the card should be updated to indicate this failure condition. This did not happen.
CSCds11187	Operational status of Protection line is not displayed correctly
CSCds13606	SSI event logged as EVENT_ERROR with stack trace of event.
CSCds13978	dspcd and dspcds show a card is in failed state but no alarm is raised.
CSCds14777	Update port sig parameters when the port status is up, it will cause the inconsistence in information display between the dsppnport and dsppnportsig.
CSCds16773	Standby PXM45 fails to come up after a PXM45 switchover or new Standby PXM45 insertion.
CSCds18258	Some connections are not able to reroute, reroute is not even being attempted; i.e. connections are not routed.
CSCds19129	Calls with AAL parameter IE octet 12.1 (i.e. partially filled cells method) set to 0 are rejected.
CSCds22540	When performing SPVC reroute and switchover the UNI (master side) at the same time, connection delete may fail on the standby. After switchover, if the same connection is recommitted, VSIErr will be observed on the AXSM console.
CSCds22868	Provision SPVCs through an IISP link. On repeated setup and release of SPVCs, it was noticed that the user side IISP had some connection data structures which were not getting cleared when the call was released.

Problems Fixed in Release 2.0.02

The following is the list of known problems that are fixed in Release 2.0.02. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.

Bug ID	Description
S1 Bugs
CSCdr22185	VsiErr message with a string explaining the error such as "Interslave timeout" and others get displayed; these messages are indications of a recoverable condition and are not meant to be displayed.
CSCdr23168	Resetting the AXSM UNI card in the edge node while the PNNI is establishing connections on it might intermittently cause the tVsiSlave task to crash on the AXSM UNI when it eventually comes up.
CSCdr27919	Performing PXM45 switchover while derouting 25k SPVCs by downing one of the nni port in the edge node might intermittently cause a lot of vsierrs (0xcoo3, 0x5011...etc) to be displayed on the corresponding UNI AXSM on the same node, and may even cause its tVsiSlave task to stop working which may results system reload.
CSCdr34387	A few SPVCs are not seen after resetsys. Not all SPVCs on any one interface have been lost.
CSCdr36772	Bucket statistics file name has incorrect file name.
CSCdr36954	VC Failure due to insufficient LCNs used up by the user connections. The port stays in VC failure forever.
CSCdr37025	Some of the provisioning command operation does not get reflected on standby and disk.
CSCdr37302	Unable to ping/telnet to the node intermittently.
CSCdr38809	After restoring the configuration using restoreallcnf command, and controller card switchover happened, the some of the SPVC end points may be missing and/or the attributes of some of the VCs may be changed.
CSCdr39120	Reset of AXSM cards and switchover will cause SPVC to reroute.
CSCdr40126	If there are more than 31K connections on a single AXSM in a VIA node, the connections on the AXSM are not deleted when PNNI deroute the connection.
CSCdr40620	NO SPVCS. After PXM45 rebuild some interfaces might disappear. WITH SPVCS Every time PXM45 card (both cards in case of redundancy) is rebooted, Node cannot come up. pnRedman may be in exception.
CSCdr43586	'ssiIpcMessageAllocate fails' appears on screen periodically.
CSCdr43665	The call does not routing with VPI/VCI assignment error.
CSCdr45695	Could not run "dspln", dspports, etc. Could not walk mib tables.
CSCdr46104	Exception in pnCcb task causing the active processor to reset.
CSCdr47782	Standby PXM45 reloads
CSCdr47834	Connection add / delete problems when number or connections is around 30,000+. Possible error message includes, delete failure, non-existing ConnID entry.
CSCdr47947	After resetting the AXSM (UNI) card in endnode, and performed PXM45 switchover while the port is still in down in progress, once the AXSM card is up, and all uni ports are in "up" state, vsi error 0x502a (connection reserve failure) are observed.
CSCdr50312	Standby card will be reset and come back in the higher revision (2.0(1)). The card will then transition to the failed state.
CSCdr55652	provision the SPVC, the conn is ok but the cell dropped.
CSCdr56267	Standby PXM45 waits indefinitely in INIT state.
CSCdr61082	The applications on Active PXM45 fail to communicate with other applications on the same card and other cards due to lack of IPC message buffers.
CSCdr61204	dspcds will show that the card is in the BOOT state.
CSCdr67620	Intermittently, AXSM cards will get reset due to MCAST_MSG_LOSS.
CSCdr71695	Node and card redundancy configuration is lost.
CSCdr73806	dspcds and many other CLI commands will not work.
CSCdr75500	SPVCs will fail to route.
CScdr78831	After clrallcnf, access to the node via TCP/IP makes connection to the standby card rather than the active.
CSCdr80279	When a VPC connection is added a connection add trap is sent to the CWM. In this trap a MIB object cwaChanVpcFlag is set to indicate if the connection is a VPC or a VCC. This was erroneously set to indicate VCC instead of a VPC.
CSCdr80807	System restarts.
CSCdr82611	When a large number of endpoints are provisioned and if all of them had statistics collection enabled, then it is impossible to login or cc to the AXSM card.
CSCdr82868	IP connectivity cannot be established and remains in SETUP state.
CSCdr85316	IP connectivity setup fails with cause ATM_CAUSE_VPCI_UNAVAIL (35).
CSCdr87319	PNNI Link might occasionally go down or remain in oneWayInside/Attempt state. Connections may reroute on any other available trunk or stay derouted in case no other trunk is available.
S2 Bugs
CSCdr25037	Many [vsierr] messages and [egress ConnID add failure] messages are reported by the trunk card on NODE_EP1 while the rebooted UNI card does NOT have error messages.
CSCdr27033	Clock source does not revert back to primary bits clock when revertive mode enabled. This can also appear in the form that clock is not switched to a valid clock source that should have a good clock signal. What is really the case is that the clock source has been previously declared as unusable/unlockable by the clock source manager. This clock source will not be chosen again until after clock source reconfiguration.
CSCdr27718	The SSCOP, PNNI protocol states would not be in Established state, two-way inside respectively. The protocol PDUs will be discarded at SAR level.
CSCdr28033	When performing dnpnport on a certain ports with SPVC connections which has statistics enabled, some dal/statistics error are observed on the UNI AXSM side.
CSCdr28767	The SSCOP, PNNI protocol states would not be in Established state, two-way inside respectively. The protocol PDUs will be discarded at SAR level.
CSCdr29013	Much lower via node reroute rate when attempting to reroute SPVCs at a higher call rate than nodal setup msg congestion threshold value.
CSCdr32624	Any operation involved in file creation or file opening on the Active controller card will start failing continuously.
CSCdr34225	Cell drops are noticed on OC3 with default line rate.
CSCdr34707	Calls will not go through.
CSCdr34851	After addpart with incorrect parameters, the partition gets added on AXSM, but dsppnports on PXM45 either doesn't show the port, or it shows the IF status as provisioning. After delpart, dsppnports shows the IF status up for the port on the PXM45, although dspparts on the AXSM doesn't show the partition anymore. There is no error message displayed.
CSCdr36903	ILMI fails to transition to a steady state and PNNI ports may not come up. As a calls might fail to route or use another available heathy trunk.
CSCdr39329	Few connections will be in fail state at one end point (either master end or slave end)
CSCdr39684	Cannot display link selection configured on PNNI port.
CSCdr39892	The symptoms of this problem is that all traffic that is coming into the AXSM card is being discarded. Specifically, ingress traffic does not go into the switch planes and since the queues in the QE48 gets full, the incoming traffic reaches the maximum cell threshold and all cells are discarded.
CSCdr40167	User see sometimes SPVC fail to route SPVC connection on AXSM card resets
CSCdr40333	User did not have the granularity to find out why the clock when bad.
CSCdr40484	User did not have the granularity to find out why the clock when bad.
CSCdr40821	Some SPVC connections are in AIS-FAIL in standby
CSCdr41012	Ports go to Down in Progress after Reset/Downing the AXSM. This is due to failure to resync the connections.
CSCdr41170	After changing T3 line framing mode from ADM to PLCP, continuous vsi error messages are reported on ASXM.
CSCdr41708	After the switchover, the new active PXM45 still shows that the above inserted back cardback card is still missing. This will eventually cause an extra switchover when a healthier standby PXM45 is ready.
CSCdr42075	port(s) in "vc failure"
CSCdr43945	One can exceed the peak cell rate up to line rate thereby starving all resources to other connections. This is due to the fact that OAM and RM cells do not get policed.
CSCdr44255	Svc call on uni port getting released.
CSCdr44537	The connection does not pass the data traffic.
CSCdr44566	Dax connections are in FAIL state
CSCdr44741	An unsupported card will stay in the Boot state, and the standby PXM45 will stay in the Init state.
CSCdr45063	The address or address prefix associated with a PNNI node at a lowest level peer group, if not summarized by any of the default or configured summary address, may sometimes be failed to be advertised across the peer group boundary even when its advertising scope is wide enough.
CSCdr45896	The problem is not observable, but the problem can be identified/observed when the traffic parameters are verified by doing "dalConnParamsShow" after de-routing the connections from one trunk to another on a different card
CSCdr45962	Some SPVC connections are in AIS-FAIL in active PXM45 after switchover
CSCdr46262	When switchover occurs, all the master / slave endpoints are attempted to route / half commit, and it will hit congestion, which will not recover dspnodalcongflags will show connpendingflg set to TRUE.
CSCdr46770	The clock is marked as unclockable.
CSCdr46945	The PNNI main task is looping when calling pnni_delete_db_ptse() for a horizontal link.
CSCdr47590	After Switchover Standby(newly active) doesn't have the same number of SPVCs as Active had before.
CSCdr47916	Connection may not be routed on best path.
CSCdr47931	System allows calls to use VPI/VCI below the provisioned minimum value.
CSCdr48075	CWM has difficulty understanding the contents of a SNMP trap when retrieved from the RTM MIB.
CSCdr49287	Connection resync will be stuck in one place and so connections will be mismatched between controller and slave
CSCdr49592	A user adds a connection without specifying mbs/cdvt, this programs the hardware with values that are shown by dspmbsdft/dspcdvtdft. But when user does "dspcon", the value shown for both mbs/cdvt is -1.
CSCdr50477	The addcontroller command fails.
CSCdr50497	dspsct command does not display proper information.
CSCdr51668	1.switch gives status.14.0000000000000 as the response to getnext request on netprefix 2.get negative number in ILMI PDUs from HP test
CSCdr52913	While the node is running, a couple of error messages are shown in the log. When Line Failure occurs, it was not identified by an easily understandable message, the line that failed was not printed.
CSCdr53438	cnfchan on slave dax con for cc enable, PNNI controller doesn't send vsi msg to SM
CSCdr53470	SPVCs will fail to route.
CSCdr54146	Calls will not get routed through the nodes in the network.
CSCdr54798	When 2 mandatory events were sent to the children at the same time, the RAT only kept the last one.
CSCdr55821	Certain connection will not establish. If you can trace the signaling message, you'll see the switch received connect and sends status message with cause 100 (invalid IE contents).
CSCdr55832	See the following misleading messages: "+bad length+" and "Send Status Enquiry"
CSCdr55928	AXSM STM1 card will not handle over 32K connections.
CSCdr56173	SPVP connection(s) are not allowed.
CSCdr56897	Resetting the UNI AXSM on the edge node of a three node network with 50K+ connections may cause the tVsiSlave task cpu utilization to go above 90% for a few seconds after it comes up.
CSCdr57071	Bad IPC messages detected caused by unreported SAR CRC errors. Unexplained behavior or errors in the shelf.
CSCdr57276	SHM FAILURE ALERT message is displayed on the console
CSCdr58626	See a continuous Trap messages indicating IPC memory leaks.
CSCdr59353	The dspclksrc command shows inaccurate clock information
CSCdr59423	Switchcc results in clk switch to priority 0 msg.
CSCdr59709	No event logs when there is a PXM45 switchover.
CSCdr60068	If a resetsys or a switchcc is preformed on the PXM, a core dump would be preformed during the boot of the formerly active PXM45 card. When the core dump logs are observe the reason would be a device driver error.
CSCdr62126	clralmcnt doesn't clear LOS/LOF alarm counters.
CSCdr63104	dspcdstatus shows "No Alarms" for PXM45/any inapplicable slots. When slot number is not specified, it defaults to PXM45 slot.
CSCdr64230	In a multi slave system with combined DAX & routed cons (50K), pnccb task is suspended when reset of the uni-AXSM card is followed by DAX con being modified (committed).
CSCdr64564	When the optional parameter, shelf #, was provided in the CLI commands, the commands fail.
CSCdr65883	If the active PXM's disk is not synced (e.g. not all data on the disk is valid), the node is allowed to come up. This will result in lost of database configuration.
CSCdr66184	DAX connections are not in AIS when connection is down
CSCdr66781	dspcdalms shows alarms whereas dspcdstatus does not.
CSCdr66802	switchcc generates a syntax error message inappropriately
CSCdr67264	When a connection (which is in alarm) gets cleared of all the alarms, a connActive trap is sent to the CWM. This trap contains a bit map of conn. alarms in a mib object cwaChanAlarmStatus. When all the connection alarms clear this bitmap takes a value of zero. This was not documented in the MIB. Hence the confusion.
CSCdr71350	CLI dsppnni-path displays node name incorrectly
CSCdr72570	Some connections exhibit unexpected behavior such as "cannot resolve passthru".
CSCdr72621	Some connections exhibit unexpected behavior (see related bug CSCdr72621) such as "ERR: Could not resolve passthro id" when "dspcon" is executed on some connections.
CSCdr73169	SNMP MIB Walk or Sending Traps results in failure(Event Log contains this information)
CSCdr73423	When the cnfpasswd command is executed, and the enter key is hit twice, (instead of actually entering in a new password), the password is set to the defaults.
CSCdr75227	dsplns will show "other" for Medium LineType instead of "ShortSMF" etc.
CSCdr76402	Board (e.g. PXM45) fails to boot and issues a NOVRAM checksum error.
CSCdr78869	Events of type "CHUNKNOTOWNER" are logged in the event log.
CSCdr80772	Log does not report successful switching of clock source.
CSCdr81154	dsppnport does not show active connections after dnpnport on a UNI port.
CSCdr83752	? is taken as the node name and modified the node name to?

Related Documentation

This section lists documentation related to the installation and operation of the MGX 8850 Release 2 switch and associated products in a Cisco WAN switching network. Table 1 lists the product documentation for the MGX 8850 Release 2 switch.

These documents can be ordered or downloaded. Both procedures are described later in this document.

Table 1 MGX 8850 Switch Release 2.1 Related Documentation

Documentation	Description
Cisco MGX 8850 Routing Switch Hardware Installation Guide, Release 2	Provides a detailed description for installing the MGX 8850 switch in a restricted access location.
Cisco MGX 8850 Routing Switch Command Reference, Release 2	Describes and lists the user-accessible command line interface (CLI) for the MGX 8850 switch.
Cisco MGX 8850 Routing Switch Software Configuration Guide, Release 2	Describes how to configure the MGX 8850 switch to operate as an ATM core switch or as an ATM edge switch.
Cisco MGX 8850 Routing Switch Software Release Notes, Release 2	Describes new features and limitations for the software. Maintenance releases are supported with additional release notes.

Additional documentation for the Cisco WAN Manager (CWM) network management system that works with the MGX 8850 Release 2 switch is listed at our web site.Platform-Specific Documents

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

•http://www.cisco.com (for example, as of this printing, MGX 8850 documentation is located at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8850/index.htm)

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

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

Documentation CD-ROM

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

Ordering Documentation

Cisco documentation is available in the following ways:

•Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/cgi-bin/order/order_root.pl

•Registered Cisco.com users can order the Documentation CD-ROM through the online Subscription Store:

http://www.cisco.com/go/subscription

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

Documentation Feedback

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

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

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

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

We appreciate your comments.

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

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

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

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

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

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

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

•P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

•P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

•P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

•P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

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.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.

AccessPath, AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.

All other brands, names, or trademarks mentioned in this document or Web site are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0104R)

Copyright © 2001, Cisco Systems, Inc.
All rights reserved.