Table Of Contents
9.2.47 Version Software Release Notes Cisco WAN Switching System Software
Table of Contents
About the 9.2 Release
Phased Release Strategy
Definitions
Software Release 9.2.47
Software Releases 9.2.31-9.2.47
Software Release 9.2.30
Software Release 9.2.23, 9.2.22, and 9.2.21
Software Release 9.2.20
Software Release 9.2.10
Software Release 9.2.01
Software Release 9.2.00
Clarifications
Special Installation/Upgrade Requirements
General/Upgrade Procedure
Adding NTM Trunk Limitation
Revision Interoperability Supported
Version Compatibility Notes
Control Card Requirements
Control Card Boot Firmware Requirements
Control Card Compatibility Requirements
Control Card Physical Card Upgrade Procedure
Obsoleted
Notes and Cautions
Additional Notes for Release 9.2.47
Additional Notes for Release 9.2.45
Additional Notes for Release 9.2.43
Additional Notes for Release 9.2.41
Additional Notes for Release 9.2
Limitations
Required Workarounds
Additional Documentation
Compatibility Notes
Compatibility Matrix
BPX 8600 Firmware Compatibility
IGX 8400 Firmware Compatibility
MGX 8220 Firmware Compatibility
MGX 8250 1.1.3x Firmware Compatibility
MGX 8850 1.1.3x Firmware Compatibility
BPX 8600 Hardware Compatibility
IGX 8400 Hardware Compatibility
Resolved Anomaly in Release 9.2.47
Anomalies in Release 9.2.45
Known Anomalies in Release 9.2.45
Resolved Anomaly in Release 9.2.45
Anomaly Status Changes in Release 9.2.45
Anomalies in Release 9.2.43
Known Anomalies in Release 9.2.43
Resolved Anomalies in Release 9.2.43
Anomaly Status Changes in Release 9.2.43
Anomalies in Release 9.2.42
Known Anomalies in Release 9.2.42
Resolved Anomalies in Release 9.2.42
Anomalies in Release 9.2.41
Known Anomalies in Release 9.2.41
Resolved Anomalies in Release 9.2.41
Anomalies in Release 9.2.40
Resolved Anomalies in Release 9.2.40
Known Anomalies from Previous Releases Closed in 9.2.40
Resolved Anomalies in Release 9.2.38
Resolved Anomalies in Release 9.2.37
Resolved Anomalies in Release 9.2.36
Resolved Anomalies in Release 9.2.35
Resolved Anomalies in Release 9.2.34
Resolved Anomalies in Release 9.2.33
Resolved Anomalies in Release 9.2.32
Resolved Anomalies in Release 9.2.31
Resolved Anomalies in Release 9.2.30
Resolved Anomalies in Release 9.2.23
Resolved Anomalies in Release 9.2.22
Resolved Anomalies in Release 9.2.21
Resolved Anomalies in Release 9.2.20
Resolved Anomalies in Release 9.2.10
Resolved Anomalies in Release 9.2.01
Additional Deliverables
SNMP MIB
Default Values
BPX 8600 Nodes
IGX 8400 Nodes
UXM-E3
Appendix A: BXM Firmware MFW Release Notes
About the Firmware MFW
Front Cards
Front Card for APS Compatibility
Back Cards
New Features supported in BXM Firmware MFW
New Features supported in BXM Firmware MFV
New Features supported in BXM Firmware MFU
New Features Supported in BXM Firmware MFT
New Features Supported in BXM Firmware MFR
New Features Supported in BXM Firmware MFP
New Features Supported in BXM Firmware MFN
New Features Supported in BXM Firmware MFM
New Features Supported in BXM Firmware MFK
New Features Supported in BXM Firmware MFJ
New Features Supported in BXM Firmware MFH
New Features Supported in BXM Firmware MFF
New Features Supported in BXM Firmware MFE
New Features Supported in BXM Firmware MFD
New Features Supported in BXM Firmware MFC
New Features Supported in BXM Firmware MFB
New Features Supported in BXM Firmware MFA
New Features Supported in BXM Firmware MEC
New Features Supported in BXM Firmware MEB
New Features Supported in BXM Firmware MEA
New Features Supported in BXM Firmware MDA
Special Installation/Upgrade Requirements
Features Obsoleted
Notes, Cautions, and Clarifications
Known Anomalies
Resolved Anomalies in MFW
Resolved Anomalies in MFV
Resolved Anomalies in MFU
Resolved Anomalies in MFT
Resolved Anomalies in MFR
Resolved Anomalies in MFP
Resolved Anomalies in MFN
Resolved Anomalies in MFM
Resolved Anomalies in MFL
Resolved Anomalies in MFK
Resolved Anomalies in MFJ
Resolved Anomaly in MFH
Resolved Anomalies in MFF
Resolved Anomalies in MFE
Resolved Anomalies in MFD
Resolved Anomalies in MFC
Resolved Anomalies in MFB
Resolved Anomalies in MFA
Resolved Anomalies in MEC
Resolved Anomalies in MEB
Resolved Anomalies in MEA
Resolved Anomalies in MDA
Firmware Filenames and Sizes
Appendix B UXM ABL Firmware Release Notes
New Features
Obsolete Features
Compatibility
Resolved Anomaly in this Release
Upgrade Instructions
Notes and Cautions
Boot Code Requirements
Obtaining Documentation
Cisco.com
Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
9.2.47 Version Software Release Notes Cisco WAN Switching System Software
These release notes are part number OL-7173-01 Rev. A0, January 28, 2005.
Table of Contents
About the 9.2 Release
The 9.2 software release supports the Cisco WAN switching products, BPX 8600 series, and IGX 8400 series. This release does not support the IPX switch.
Phased Release Strategy
The MSSBU rollout plans for the 9.2 release is based upon a series of incremental feature releases. This phased feature release strategy is designed to allow the earliest customer availability of key new features, consistent with maintaining high product quality. For the latest status of each 9.2 feature, see below.
The minimum release version noted in the table below represents the minimum switch software version required for each feature. As usual, it is recommended that customers use the most current maintenance releases.
Definitions
Generally Available (GA)
|
Feature is ready for wide deployment with no restrictions. Customers deploying GA features are supported by the Technical Assistance Center (TAC).
|
First Customer Ship (FCS)
|
Feature is available for controlled introduction to selected customers. To trial an FCS feature, please contact your account representative. Customers selected for controlled introduction receive assistance with the test plan review and special support from the New Product Team (NPT) in addition to the normal Technical Assistance Center (TAC) support.
|
The minimum release version noted in the table represents the minimum switch software version required for each feature. It is recommended that customers use the most current maintenance releases.
Product
|
Feature Name
|
FCS/GA
Status
|
Minimum Release
|
IGX
|
Support for UXM XLR card
|
GA
|
9.2.30
|
BPX
|
Support Multiple VSI Partitions
|
GA
|
9.2.30
|
IGX
|
HDM/LDM Control Lead Trap
|
GA
|
9.2.30
|
IGX
|
Support UXM Feeder
|
GA
|
9.2.30
|
IGX
|
SES Feeder to IGX
|
GA
|
9.2.20
|
BPX/IGX
|
A-bit Notification
|
GA
|
9.2.20
|
BPX/IGX
|
Real-Time VBR
|
GA
|
9.2.20
|
IGX
|
Support Enhanced UXM
|
GA
|
9.2.20
|
BPX
|
Support Enhanced BXM
|
GA
|
9.2.20
|
BPX
|
Support for 16K connections
|
GA
|
9.2.10
|
BPX
|
Support for Virtual Switch Interface (VSI) 2.2
|
GA
|
This interface is available in 9.2.10. Use of this interface is dependent upon other products, for example IOS.
|
BPX
|
Support for APS Annex B
|
GA
|
9.2.10
|
IGX
|
Support for UXM VP tunneling
|
GA
|
9.2.10
|
BPX
|
Include SONET line protection: APS on BXM-OC3 and BXM-OC12 (1+1)
|
GA
|
9.2.01
|
BPX
|
Support for Virtual Trunking on the BXM card
|
GA
|
9.2.01
|
BPX
|
Include SONET line protection: APS on BXM-OC3 and BXM-OC12 (2 card, 1:1)
|
GA
|
9.2.00
|
BPX
|
Support for LMI/ILMI on BXM card
|
GA
|
9.2.00
|
BPX/IGX
|
Alarms for all service-affecting events
|
GA
|
9.2.00
|
BPX/IGX
|
Support for feature mismatch on BXM and UXM cards
|
GA
|
9.2.00
|
BPX/IGX
|
Support for Hitless Rebuild including Disable Auto Bus Diagnostics
|
GA
|
9.2.00
|
BPX/IGX
|
Support for IGX and BPX trunk reconfiguration without outage
|
GA
|
9.2.00
|
BPX/IGX
|
Support for Revision Interoperability between 9.1 and 9.2
|
GA
|
9.2.00
|
BPX/IGX
|
Support for UXM and BXM Multilevel Channel Statistics
|
GA
|
9.2.00
|
BPX/IGX
|
Support ports and trunks on the same UXM and BXM cards
|
GA
|
9.2.00
|
IGX
|
Support for ATM Forum Standard Compliant IMA Trunking with UXM Firmware Model B
|
GA
|
9.2.00
|
IGX
|
Support for Virtual Trunking on the UXM card
|
GA
|
9.2.00
|
IGX
|
Support VC traffic shaping on UXM port
|
GA
|
9.2.00
|
IGX
|
Support for Idle code suppression for video on UVM and CVM cards
|
GA
|
9.2.00
|
Software Release 9.2.47
This maintenance release includes all features supported up to Release 9.2.30. The following files are extracted from a TAR file upon upgrading to SWSW Software Release 9.2.47.
Table 1 Release 9.2.47 BPX Files
File Name(s)
|
File Size (bytes)
|
9247B.000 to 9247B.023
|
65536
|
9247B.024
|
53077
|
9247B.img
|
784
|
Table 2 Release 9.2.47 IGX Files
File Name(s)
|
File Size (bytes)
|
9247G.000 to 9247G.026
|
65536
|
9247G.027
|
6056
|
9247G.img
|
784
|
Software Releases 9.2.31-9.2.47
The following maintenance releases include all features supported up to Release 9.2.30: 9.2.31, 9.2.32, 9.2.33, 9.2.34, 9.2.35, 9.2.36, 9.2.37, 9.2.38, 9.2.40, 9.2.41, 9.2.42, 9.2.43, 9.2.45, and 9.2.47.
Software Release 9.2.30
Release 9.2.30 includes all features supported up to Release 9.2.20 and introduces the following additional features:
•
Support for multiple partitions.
•Support for UXM feeder.
•Support for HDM/LDM control lead trap.
•Support for UXM XLR back card.
Software Release 9.2.23, 9.2.22, and 9.2.21
These releases include all features supported up to Release 9.2.20.
Software Release 9.2.20
Release 9.2.20 includes all features supported up to Release 9.2.10 and introduces the following additional features:
•Support for real-time VBR (rt-VBR).
•Support for early A-bit notification. This feature is an enhancement to the early A-bit notification feature in Release 9.1.
•Support the Service Expansion Shelf (SES) feeder to IGX.
•Software support for enhanced BXM and UXM cards.
Software Release 9.2.10
This release includes all features supported up to Release 9.2.01 and introduces the following additional features:
•Support for Virtual Switch Interface (VSI) 2.2.
•Support for 16K connections.
•Support for UXM VP tunneling.
•Support for APS Annex B.
•Support for Multiple Protocol Label Switching (MPLS), MPLS-Virtual Private Network (VPN), and MPLS Class of Service (COS). For more details see Clarifications.
Software Release 9.2.01
This release includes all features supported in Release 9.2.00 and introduces the following additional features:
•Support for virtual trunking on the BXM card.
•Support for SONET line protection: APS on BXM-OC3 and BXM-OC12 (1+1).
Software Release 9.2.00
This release introduces the following features:
•Support for virtual trunking on the UXM card.
•Support for both ports and trunks simultaneously on the same UXM and BXM cards.
•Support for hitless rebuild including Disable Auto Bus Diagnostics.
•Support for UXM and BXM multilevel channel statistics.
•Support for alarms of all service-affecting events.
•Support for revision interoperability between 9.1 and 9.2.
•Support for IGX and BPX trunk reconfiguration without outage.
•Support for ATM Forum Standard Compliant IMA trunking with UXM (IGX 8400) Firmware Model B.
•Support for SONET line protection: APS on BXM-OC3 and BXM-OC12 (2 card, 1:1).
•Support for LMI/ILMI on BXM card.
•Support for feature mismatch on BXM and UXM cards.
•Support for idle code suppression for video on UVM and CVM cards.
•Support VC traffic shaping on UXM port.
•Support for UXM STM-1 electrical back card.
Clarifications
1. The fix for CSCdu50924 has changed the behavior of SWSW with respect to CM parameters 9 (reroute timer) and 10 (reset timer on line fail). Derouted connections are now eligible for routing immediately, irrespective of the values of CM parameters 9 and 10 and the time of the last reroute. This also means that CM parameter 10 is effectively obsolete.
Previously, if CM parameter 9 was set to a value greater than 0 and CM parameter 10 was set to No, a connection would not be eligible for routing until the time specified by CM parameter 10 had passed since its last reroute. This was true even if the connection was derouted and a route was available. Therefore, the goal of the fix to CSCdu50924 is to get derouted connections routed as soon as possible.
2. Release 9.2.31 introduced a new command—cnffdrlmiparms—which makes the feeder LMI timers and counters configurable. This command is currently supported on BPX only and cannot be added in the Job mode.
Usage: cnffdrlmiparms slot.port T393 T394 T396 N394 N395
where slot.port specifies the feeder trunk to configure. The details of the other parameters are as follows:
Timer
|
Description
|
Range (sec.)
|
Default (sec.)
|
T396
|
LMI polling timer
|
5-30
|
10
|
T393
|
SPC STATUS ENQUIRY timer
|
5-30
|
10
|
T394
|
SPC UPDATE STATUS timer
|
5-30
|
10
|
N394
|
Max retry count for SPC STATUS
ENQUIRY/ REPORT procedures
|
1-10
|
5
|
N395
|
Max retry count for SPC UPDATE
STATUS / ACK procedures
|
1 -10
|
5
|
3. In Release 9.2.31 the system parameter 2 (cnfsysparm 2) is changed from "Fail Connections On Communication Break" to "Allow CPU Starvation of Fail Handler."
The old parameter has been removed as it violated the principle of the separating control and data plane. The new parameter allows a new feature to be turned off, which gives CPU to the Fail Handler at the expense of the Transaction Handler in case the Fail Handler does not get scheduled for a long time.
4. Do not mix MEE and MEF (or higher) in Y-red pairs for BXM 2-port group enhanced cards (OC-3 or OC-12 port). addyred will fail if both are in standby mode, or the primary card has been activated with MEF (or higher) and the secondary card has MEE.
5. For the BXM 2-port group, enhanced cards activated with MEF or higher, downrev to MEE will bring the cards into MISMATCH mode. This applies to both single cards and Y-red pairs.
6. Release 9.2.30 introduced four new commands in BPX:
•addctrlr to add VSI capabilities to a trunk interface to which a Feeder of type AAL5 is attached. This command is basically run as the second step in adding a PNNI controller.
•delctrlr to delete VSI capabilities from a trunk interface to which a Feeder of type AAL5 is attached. This command is basically run as the first step in deleting a PNNI controller.
•cnfvsipart to configure VSI partition characteristics. Currently, we can only enable VSI ILMI functionality using this command.
•dspvsipartcnf to display VSI partition characteristics. Currently, this command only displays information about VSI ILMI functionality.
7. There are changes in the following commands starting from Release 9.2.30:
•cnfrsrc
–Allow start VPI = 0 for a VSI partition on a port interface, provided there is only one VSI partition on the port interface.
–Prevent second VSI partition from being enabled on a port interface if the first VSI partition uses a start VPI = 0.
–Prevent a VSI partition from being disabled on a trunk interface if a PNNI controller is attached to the trunk interface controlling partition being disabled.
•cnfport
–Prevent disabling ILMI protocol on a port interface, if a VSI ILMI session is active on a VSI partition on the port interface.
–Prevent configuring ILMI protocol on port interfaces to run on the BCC, if a VSI ILMI session is active on a VSI partition on the port interface.
•cnftrk
–Prevent configuring ILMI protocol on a trunk interface to run on the BCC, if a VSI ILMI session is active on a VSI partition on the trunk interface.
•addshelf
–Prevent adding a feeder to a trunk, if VSI ILMI session is active on a VSI partition on the trunk interface.
8. The multiple partitions introduce two VSI partitions on trunk and port interfaces on the BXM card. One partition can be used for MPLS, and one can be used for PNNI. Virtual Trunk can have only one VSI partition or can be used for AutoRoute, but cannot be used for both VSI and AutoRoute simultaneously. This project introduces six service class templates in addition to the three existing templates.
Even though tag ABR is supported in Service Class Template (SCT), neither the MPLS controller nor the BXM firmware currently support this.
The configurable VPI/VCI introduces 2 new parameters in addctrlr and addshelf commands, through which the user can specify the VPI and VCI of the master-slave control channels.
9. There is a change in reporting of port group numbers in Release 9.2.32. Previous image (MEC) of BXM used to report a 1-port group for the 2-port group cards at the channel statistics level 2 and 3. This made the port belonging to second port group unusable.
For enhanced BXM cards, upgrade to 9.2.30 software first and then burn the BXM card with the MEE or higher firmware, BXM will report 2-port groups for 2-port cards all the time. The smooth transition between the earlier 1-port group and the newly reported 2-port groups also displays the message in dspcd "Inconsistency with logical PG #" (port group number). All earlier software will "mismatch" the card.
If the BXM card is programmed with MEC or earlier firmware revision, the channel statistics for level 2 or 3 will report 1-port group for enhanced BXM cards. Burning an MEE or higher image will result in 2-port groups, but for backwards compatibility the software will not do the recomputation of LCNs based on the new port groups. In its logical database, this will not impact the AutoRoute connections.
For VSI controllers the reported value will be higher than the actual available LCNs. That means a VSI controller may not be able to add connection even though the available connections are non-zero. If the user wishes to remove the above discrepancy, the card must be brought to the standby mode.
Note that the newly configured card or the card in standby mode programmed with MEE or higher image brought to the active state will not have above discrepancy.
10. In BPX nodes that use processor cards with 32 MB of RAM, it is possible to run out of memory in the Hitless Region. This can happen if the node is too heavily configured with cards and connections. The recommendation below should prevent memory aborts.
In nodes that have processor cards with 64 MB of RAM, there should be no Hitless Region memory problem. This is because 64 MB processors contain a second Hitless Region, which is larger than the first.
The following calculation will help prevent memory aborts on BPX processors with 32 MB. For simplicity, the numbers are approximate. It is necessary to add up the number of cards in the node, as well as the number of connections, and make sure that the total does not exceed the recommendation.
During system initialization, roughly 17,100 blocks of the available 40,000 are used for the card database.
In addition, assume that 1500 blocks will be needed for each BXM card that can support 16K connections, which is the more common configuration. Some BXM cards can support 32K connections, and these will need 3000 blocks of the Hitless Region. This chunk of memory is allocated at the insertion of the BXM card and will not be released until a card of different type is inserted.
Also, 300 blocks will be needed for each 1000 via connections on the node. This can be viewed with the user command dspload.
17100 blocks for card database
1500 blocks for EACH BXM that supports 16K conns
3000 blocks for EACH BXM that supports 32K conns
300 blocks for EACH 1000 conns
-----------------------------------------------------------------
40000 blocks maximum total (34000 blocks for 9.2 releases up to 9.2.23)
11. The minimum software required to run MPLS are:
•BPX Switch Software Release 9.2.10 or later
•BXM firmware must be MEA or later
•IOS Software Release 12.0(5)T (refer to IOS Release Note)
•Virtual Switch Interface (VSI) 2.2
The BPX with an external 7x00 label switch controller (router) with Switch Software Release 9.2.10 and IOS Release 12.0(5)T can function as an ATM-LSR. The enhancements to dynamic label switching that was supported in Release 9.1 include support for MPLS Class of Service. The BPX as an ATM-LSR supports the "Multi-Label VC" model to support MPLS Class of Service. Five Qbins (Qbin 10-14) are reserved for MPLS Class of Service. Class-based WFQ is supported on these IP queues.
The BPX can also function as a "P" ATM-LSR in the MPLS-VPN architecture.
Hot redundancy of MPLS connections on the BPX is supported by BXM hot card redundancy. Continuous message forwarding, and keep-alive between the BXM redundant pair ensures the connection continuity on BXM switchover. On failure of a BXM card, the standby card becomes active with the label VCs. Resynchronization between the MPLS label switch controller and the BPX ensures that their databases are in sync.
12. The 16K connections feature increases the number of connections terminating on the BPX switch to 16,000. The count includes connections terminating on BXM or ASI endpoints on cards within the node as well as connections terminating on service modules in the feeder shelves connected to the BPX switch. For example, a Frame Relay connection that originates on an FRSM in an MGX 8220 connected to a BPX counts as one of the 16,000 terminated connections on that BPX.
This feature requires a BCC-3-64 or BCC-4 controller in the BPX as well as Switch Software 9.2.10 or higher.
13. Version 2.2 of the Virtual Switch Interface (VSI) provides the BPX switch with the ability to support multiple network protocols and multiple controllers per switch (for example, MPLS, PNNI, and so on). Switch resources can be dedicated to a specific controller or shared by multiple controllers.
This feature is supported on BXM ports, trunks, and virtual trunks and requires a BCC-3-64 or BCC-4 controller in the BPX as well as Switch Software 9.2.10 or higher and firmware MEA or higher.
Following are the VSI features:
•Support for only one partition, that is, a port or a trunk can be partitioned into one VSI partition along with AutoRoute.
•A Virtual Trunk interface cannot have both VSI and AutoRoute simultaneously. It has to be either VSI or AutoRoute only.
•There are nine Service Class Templates (SCTs) defined. SCT 1 is used for interfaces exclusively for MPLS. SCT 2 and 3 are respectively used for ports and trunk interfaces, which are exclusively used for PNNI. SCT 4 onwards are used for interfaces that are used for both MPLS and PNNI.
•Master Redundancy is supported, that is, multiple controllers can control the same partition.
•Only one controller can be added per trunk interface.
14. The combinations of system limits such as the number of trunks, lines, ports, and connections as well as enabled TFTP interval statistics should be provisioned so that the node has at least 50 percent idle time usage. Use the command dspprfhist to verify.
15. When cost-based routing is used, increasing the cost of a trunk will result in deleting the preferred path on connections in the database if the sum of the preferred path cost exceeds the connection of configured cost. The connections will remain routed on its current path.
16. On the BXM and UXM, for the OC-3 MultiMode Fiber back cards, Y-Redundancy/hot standby is not supported due to hardware restrictions.
17. The trunk reconfiguration feature does not support IMA trunks.
18. An LCN Resynchronization feature was developed to maintain consistency between NPM and UXM connection databases when a switchcc occurs. IGX Software release 9.2.37 or later and UXM firmware Release ABK or later are required to implement this feature.
Special Installation/Upgrade Requirements
This section contains the installation procedures and upgrade requirements.
General/Upgrade Procedure
Note Consult a Support Representative before performing any software upgrade.
The earliest release supported for a graceful upgrade is 9.1.03.
Additional data is transferred from nodes to CWM by Switch Software Release 9.2.x and later. It is recommended that networks with greater than 15 nodes be divided into IP subnets of no more than 15 nodes per subnet. Dividing the nodes ensures that LAN gateway node serves no more than 15 nodes.
The exact number of nodes that can be served by a single gateway depends on the configuration of the nodes. However, the number of nodes in a subnet should not exceed 50 when running release 9.2.x. If too many nodes are served by a single gateway, the gateway node sustains low idle time and intermittent unreachability with other nodes in the network.
For configuration information refer to the Cisco WAN Manager Operations, Release 9.2 documentation located at the following URL:
Switch Software Version 9.2 requires a minimum of MED firmware for BXM Model E non-enhanced cards. MEE is the minimum required firmware for enhanced BXM cards.
Before upgrading to this release when UXM cards are to be used, certain legacy card firmware must be upgraded. See the compatibility matrix for cards affected and the exact versions to be used.
Note Standards-compliant IMA is not compatible with the proprietary IMA protocol used in revision A firmware. Both ends of an IMA trunk must have the same protocol.
To upgrade a UXM card, complete the following steps:
Note This procedure also applies to the UXME card.
Caution Failure to follow this procedure may result in the card not operating. The card should be returned to Cisco if this occurs.
Step 1 Verify the current boot code version.
To run Model B firmware on UXM, the card must be running boot code revision 6 or greater.
Step 2 To determine the boot code running on the card, issue the following command from CLI (user must be logged in as Service level or greater to use this command):
rsh <slot #> sys version
Step 3 Upgrade the UXM boot code if necessary.
The process for loading boot code is identical to the process of loading firmware. The only part that changes is the name of the file.
Note Burning the boot code causes the card to reset.
Step 4 Upgrade the UXM firmware.
Step 5 Use the following command to configure the red alarm in/out values to 1.25/1.5 seconds or greater:
cnftrkparm
When Y-redundant trunks are used, the red alarm in/out values must be configured to 1.25/1.5 seconds or greater. Otherwise, INVMUX failures occur, and trunk failures are observed during a Y-redundancy switchover. These failures are due to the IMA protocol and might cause connections to reroute.
Step 6 Upgrade NPM software to 9.2.
Use the following procedure for upgrading UXM-to-IMATM trunks from proprietary IMA protocol to ATM forum-compliant IMA protocol.
Step 1 Download and burn UXM boot code version 6 or later to all UXMs in the network.
Note After completing Step 1 the UXM cards resets and reroutes traffic to other trunks.
Step 2 To have firmware upgrade on the IGX, issue the following command to disable the UXM from resetting automatically after the firmware is burned in.
cnffunc 15 d
Step 3 On each MGX 8220 equipped with IMATM-B, upgrade the ASC to 5.0.10.
Step 4 Download the Forum Compliant Firmware Version IMATM5.0.10.fw but do NOT reset the IMATM-B card.
Step 5 On each UXM with IMA to be upgraded, burn firmware ABE or later to each UXM with IMA trunks.
Step 6 Simultaneously reset the card at each end of each IMA trunk to minimize trunk outage.
Step 7 Upgrade 9.1 nodes to 9.2 by executing the loadrev and runrev commands.
Step 8 Issue the command cnffunc 15 e after each IGX is upgraded to 9.2.20 or later.
Use the following procedure for upgrading UXM-to-UXM trunks from proprietary IMA protocol to ATM forum-compliant IMA protocol.
Note This procedure also applies to the UXME card.
Step 1 For Y-redundant UXMs, issue the command cnftrkparm 18 100000 100000 prior to this procedure and return to default values after this procedure.
Step 2 Download and burn UXM bootcode version 6 or later to all UXMs in the network. This will cause the card to reset and reroute traffic to other trunks.
Step 3 On IGX to have firmware upgraded, issue command cnffunc 15 d to disable the UXM from resetting automatically after the firmware is burned in.
Step 4 On each IGX-UXM with IMA to be upgraded, burn firmware ABE or later to each UXM with IMA trunks.
Step 5 Simultaneously reset the card at each end of each IMA trunk to minimize trunk outage.
Step 6 Upgrade 9.1 nodes to 9.2 via loadrev and runrev.
Step 7 Issue the command cnffunc 15 e after each IGX is upgraded to 9.2.20 or later.
Use the following procedure for upgrading BXM cards to the 9.2 firmware release for switches running
•9.1 or 9.2 or earlier than 9.2.30 switch software,
•BXM firmware earlier than MEC, and
•BXM OC3/OC12 interface and the BXM is configured to channel statistic level 2 or higher.
To enable BXM cards to utilize 9.2 features, all BXM cards must be upgraded to the 9.2 firmware release.
Perform the following steps to avoid card mismatch for all BXM enhanced cards:
Note For upgrades from 9.1 to 9.2 you must limit the BXM-E card support to 32K connections instead of the default 60K connections.
Step 1 For upgrades from 9.1 to 9.2, ensure the BXM-E card is in standby mode without configurations.
Caution Bringing the card down to standby state is service impacting.
Step 2 Configure the card for channel statistics level 12 by entering the setnovram command.
Step 3 Upgrade BXM firmware to MEC.
Step 4 Upgrade BCC software to 9.2.30 or higher.
Step 5 Upgrade BXM firmware to MEE or higher.
For all other cases, complete the following steps:
Step 1 Upgrade BXM firmware to MED or higher.
Step 2 Upgrade BCC software to 9.2.30 or higher.
Note See the Compatibility Matrix for the exact versions to be used.
Use the following for adding new BCC cards as a part of upgrading to the 9.2 release:
•If new BCC cards are to be installed as part of the upgrade to Release 9.2, then the physical card upgrade procedure described below must be completed as a separate activity from the Switch software upgrade.
–If upgrading to BCC-4 cards on BPX 8600 nodes, complete the software upgrade first, followed by the BCC-4 physical card upgrade. If BCC-4 is already installed then upgrade as normal.
–If any other type of BCC cards are being physically upgraded, complete the physical upgrade of the cards first, followed by the software upgrade.
•Statistics collection must be disabled prior to and during the software upgrade process. The disabling must be done prior to the issuing of the first loadrev command.
•Statistics sampling must be disabled prior to the issuing of the first loadrev command at the start of an upgrade. (Use the service level command off1/off2, turn off line statistic sampling, port statistic sampling, trunk statistic sampling, and connection statistic sampling.)
Note See the Compatibility Matrix for the tested/supported versions of other firmware and software that work with this release.
Complete the following steps for upgrading VSI 1.1 in Release 9.1 to VSI 2.2 in Release 9.2.
Step 1 Upgrade the Tag Switch Controller (TSC).
The TSC is upgraded to the CoS VSI Version Capable Release (IOS 12.XX). This image is VSI bilingual, meaning it understands both VSI Version 1 and Version 2.
Step 2 Upgrade the BXMs.
Upgrade all the BXM cards in the node to Model E, which is VSI Version 2 and CoS capable. After each BXM card is downloaded with the Model E image, it temporarily experiences VSI outage until the BCC software is upgraded. The VSI outage during the upgrade is caused by the Model E firmware not being backward compatible with VSI Version 1 features.
Note From the TSC perspective, after a BXM is upgraded to the Model E image, the interfaces that used to be on the card will "disappear." The TDP sessions that were on the interfaces will be lost. When all the BXMs are upgraded to the Model E while still running Release 9.1 software on the BCC, the node will experience a complete outage of MPLS traffic. AutoRoute will have a hitless upgrade.
Step 3 Upgrade the BCC.
As the BCC is upgraded from software Release 9.1 to the desired 9.2.3x release. The BCC recognizes the Model E BXMs and downloads the VSI partition configuration. This causes the BXMs to issue ifc cfg traps to the TSC, allowing the TSC to rediscover all the MPLS interfaces on the BPX. The TDP sessions are reestablished and MPLS traffic starts flowing again through the BPX.
Note The VSI 1.1 and VSI 2.2 are not interoperable.
Adding NTM Trunk Limitation
An NTM trunk cannot be added between a Release 9.1 node and a 9.2 node.
If an IGX node is upgraded from Release 9.1.x to Release 9.2.23 and above, adding trunk fails because of an incompatibility with the traffic parameters between the two releases. Executing the addtrk command results in one of the following error messages: Abandoned due to trunk parameters conflict or Abandoned because traffic classes conflict.
In an IGX node running Release 9.1 the bits for VBR-rt and VBR-nrt classes are 0 and are not used to verify traffic parameters. In Release 9.2 these bits are set and are checked to verify traffic parameters.
To workaround this limitation, down the trunk and up the trunk again in Release 9.2 so that the bit is set. Then add the two NTM trunks since both nodes are 9.2.
Revision Interoperability Supported
Revision interoperating upgrades are supported, from the 9.1 to 9.2 releases of Switch software, with secondary revision incorporation for network lowest revision. This will lessen the risk of new features being enabled in a mixed network after the downgrade.
A "Secondary Revision" field in the node is used for the determination of the network lowest revision. Previous to this change, software used only the nodes primary revision.
Note Due to interoperability, the lowest revision running on the node has to be Release 9.2 in order for the VBR-rt and VBR-nrt bits to be set. Check that the lowest revision is 9.2.23 by issuing the dsprevs command.
The interoperability functionality uses network lowest revision for:
•Blocking the new feature unless network lowest revision is greater than or equal to the minimum supported revision for the feature
•dspblkdfuncs
Version Compatibility Notes
For a complete list of firmware revisions supported, see the Compatibility Matrix document, which is included in this release package.
This release runs with the following components:
•Any MGX 8220 Release 4.0, 4.1, and 5.0
•Cisco WAN Manager (Cisco StrataView Plus) version 9.2
•CiscoView version 2.00
•UXM model ABJ or later
•BXM model MED or later for non-enhanced BXM cards
•BXM model MEE or later for enhanced BXM cards
Switch Software Release 9.2 is interworking with VNS 3.1.
Switch Software Release 9.2 is not compatible with the following components:
•UXM Firmware Model A.
•BXM Firmware Model C or earlier.
•DAS interworking
Control Card Requirements
All processor cards must be configured with a minimum of 32MB of RAM. This includes BCCs and NPMs. NPMs require at least 1MB of BRAM. To verify the BRAM size on IGX 8400 nodes, use the dspcd command.
Note If any control cards contain less than 32MB of DRAM (these would be NPMs) then they must be replaced with cards containing at least 32MB of DRAM prior to upgrading to Release 9.2. The physical upgrade of the nodes with these control cards must be done according to the upgrade procedure defined as follows.
Control Card Boot Firmware Requirements
As specified next, the correct version of control card (CC) boot firmware must be installed on the cards prior to a software upgrade to Release 9.2.
BCC Type
|
Firmware
|
BCC-32
|
H.B.J
|
BCC-3-32
|
H.C.M
|
BCC-3-64
|
H.D.M
|
BCC-4
|
H.E.M.
|
BCC-4V
|
H.H.M
|
NPM Type
|
Firmware
|
NPM-32
|
R.B.S
|
NPM-64
|
R.C.S
|
NPM-32B
|
R.E.S
|
NPM-64B
|
R.F.S
|
With the new version of NPM boot code (RXS), the boot code upgrading does not require physical card resetting with the following steps:
Step 1 Burn the boot code on the active NPM (1).
Step 2 Execute the switchcc command and wait until the NPM(1) becomes standby. NPM(2) is now active.
Step 3 Execute the resetcd command to reset the standby (resetcd 1 h). Wait until the reset card NPM(1) becomes standby.
Step 4 Burn the boot code on the active NPM(2).
Step 5 Execute the switchcc command and wait until the NPM(2) becomes standby. NPM(1) is now active.
Step 6 Execute the resetcd command to reset the standby (resetcd 2 h). Wait until the reset card NPM(2) become standby.
Control Card Compatibility Requirements
Each redundant pair of BCC cards in a given BPX 8600 node must be of the identical type and memory configuration. That is, for example, if the active card is a BCC-3-32, then so must be the standby. BCC-3 cards with 32MB of RAM cannot be mixed with BCC-3 cards with 64MB of RAM.
Each redundant pair of NPM cards in a given IGX 8400 node must be of the identical type and memory configuration. That is, for example, if the active card is an NPM-32, then so must be the standby. NPM cards with 32MB of RAM cannot be mixed with NPM cards with 64MB of RAM. Also, NPM-64 cards cannot be mixed with NPM-64B cards.
This is a requirement for all software upgrade and downgrade procedures. It does not apply to the physical card upgrade procedure, described in the following section.
Control Card Physical Card Upgrade Procedure
When performing a control card (CC) upgrade, the following procedure must be used. This applies to all processors: BCCs, and/or NPMs.
Step 1 Remove the current standby CC front and back card. (Remove back card only applies to BCC.)
Step 2 Replace with new CC front and back cards. (Replace back card only apply to BCC.)
Step 3 Wait for the standby updates on the newly installed standby CC to complete.
Step 4 Issue a switchcc command to utilize the newly installed CC.
Step 5 Verify that the network is stable.
Step 6 Remove the current standby CC front and back card. (Remove back card only applies to BCC.)
Step 7 Replace with new CC front and back cards that are identical to the current active CC. (Replace back card only apply to BCC)
Step 8 Wait for the standby updates on the newly installed standby CC to complete.
Step 9 The CC physical upgrade is now complete.
Step 10 With the secondary card in the standby state, cause a switchover using the switchcc command. This will test that the hardware is working correctly.
Note After Step 2, the node will contain a mix of an old type CCs and the new type CCs. This condition is permitted only while the standby updates to the new CC are in progress, which will take less than one hour. The time during which this mixture of CC types exists must be kept to a minimum by immediately replacing the second old type CC with the matching one of the new type.
Obsoleted
•Starting from Release 9.2.00, the IPX is no longer supported.
•VSI 1.0 is no longer supported.
•FastPAD is no longer supported.
•The noncompliant IMA trunking (Cisco proprietary) supported in Model A of UXM firmware is not supported in Release 9.2.
Notes and Cautions
This section contains notes and cautions for the SWSW releases.
Additional Notes for Release 9.2.47
None.
Additional Notes for Release 9.2.45
None.
Additional Notes for Release 9.2.43
None.
Additional Notes for Release 9.2.41
None.
Additional Notes for Release 9.2
1. Switch Software Release 9.2 is not compatible with UXM firmware Model A.
2. If attempting to burn UXM firmware Model B into UXM firmware Model A with 9.2 software, the firmware Model B will not be burned into the UXM card due to the incompatibility of software 9.2 and UXM firmware Model A. The UXM has to be returned to Cisco for service.
3. If using MEC or earlier BXM firmware and upgrading to MEE or later, the version of switch software has to be upgraded first so that the enhanced BXM cards will report 2-port groups for 2-port cards all the time. The smooth transition between the earlier 1 port group and the newly reported 2-port groups also displays message in dspcd "Inconsistency with logical PG #" (port group number). All earlier software will mismatch the card. This applies to BXM-OC3 or BXM-OC12 and configured to channel statistic level 2 or higher.
4. Firmware MED and earlier supports APS Redundancy on Legacy BXM only.
5. Because of hardware limitations, BXM hardware is not able to recognize all user-programmed cell transmission rates. Rather only discrete transmission rates can be used instead.
The equation below shows what the BXM hardware actually transmits given a user configured cell rate. The transmitted cell rate is always less than or equal to the configured cell rate. To prevent any cell loss, the transmitted cell rate must be equal to the configured rate. To do so, a cell rate must be chosen from the table below.
The rate table below lists the highest 200 cell rates supported be BXM such that if used, will result in no cell loss (given cell traffic is less than configured cell rate). Additional rates can be calculated using 1470588/[n + (1/256)], where n is an integer.
The logic to calculate the actual cell transmission rate in a BXM card is as follows:
if (configured cell rate == full line cell rate) then
transmitted cell rate = full line cell rate
else
transmitted cell rate = from equation below or from table below
Example:
If a trunk is configured at 100,000 cells per second (cps), the actual transmitted cell rate is then 98,013 cps, any traffic sent over 98,013 cps would be discarded.
If a trunk is configured at 98,013 cps, then the actual transmitted cell rate is 98,013 cps with no cell loss.
Therefore, only rates in the table should be used. Otherwise, cell loss may be experienced. The table will not be exhausted at the end but still go on with the computing from the above equation.
Table 3 BXM Cell Transmission Rates
1464865
|
56552
|
28832
|
19348
|
14559
|
11670
|
9738
|
8355
|
733860
|
54458
|
28278
|
19097
|
14416
|
11579
|
9674
|
8308
|
489558
|
52513
|
27744
|
18852
|
14277
|
11488
|
9611
|
8261
|
367288
|
50703
|
27231
|
18614
|
14139
|
11399
|
9549
|
8215
|
293888
|
49013
|
26736
|
18381
|
14005
|
11311
|
9487
|
8169
|
244938
|
47432
|
26258
|
18154
|
13872
|
11225
|
9426
|
8124
|
209966
|
45950
|
25798
|
17933
|
13743
|
11140
|
9366
|
8079
|
183733
|
44558
|
25353
|
17717
|
13616
|
11056
|
9307
|
8035
|
163327
|
43247
|
24923
|
17506
|
13491
|
10974
|
9248
|
7992
|
147001
|
42012
|
24508
|
17300
|
13368
|
10892
|
9190
|
7948
|
133642
|
40845
|
24106
|
17099
|
13248
|
10812
|
9133
|
7906
|
122509
|
39741
|
23717
|
16902
|
13129
|
10733
|
9077
|
7863
|
113088
|
38695
|
23341
|
16710
|
13013
|
10656
|
9021
|
7822
|
105012
|
37703
|
22976
|
16522
|
12899
|
10579
|
8966
|
7780
|
98013
|
36761
|
22623
|
16339
|
12787
|
10503
|
8912
|
7739
|
91889
|
35864
|
22280
|
16159
|
12677
|
10429
|
8858
|
7699
|
86485
|
35010
|
21947
|
15983
|
12568
|
10355
|
8805
|
7659
|
81681
|
34196
|
21625
|
15812
|
12462
|
10283
|
8753
|
7619
|
77383
|
33419
|
21311
|
15643
|
12357
|
10212
|
8701
|
7580
|
73515
|
32676
|
21007
|
15479
|
12254
|
10141
|
8650
|
7541
|
70014
|
31966
|
20711
|
15318
|
12153
|
10072
|
8599
|
7502
|
66833
|
31286
|
20423
|
15160
|
12053
|
10003
|
8549
|
7464
|
63927
|
30634
|
20143
|
15005
|
11955
|
9936
|
8500
|
7427
|
61264
|
30009
|
19871
|
14853
|
11859
|
9869
|
8451
|
7389
|
58814
|
29409
|
19606
|
14705
|
11764
|
9803
|
8403
|
7352
|
.....
|
|
|
|
|
|
|
|
6. On the BPX with MGX 8220 feeder(s), regardless of the setting of the Node Parameter "42 Enable Feeder Alert," a feeder alert message will be sent to all MGX 8220 feeders immediately before a hitless rebuild takes place. The feeder alert message will temporarily disable the LMI polling from the MGX 8220 feeders. The MGX 8220 polling will resume as soon as the BPX is ready to exchange LMI messages.
7. The amount of traffic allowed on a VP tunneling connection is two-thirds bandwidth of that connection. The minimum bandwidth must be 100 cells per second. For example, a CBR connection with a peak cell rate 1500 cps then can pass traffic up to 1000 cps.
Limitations
1. BME firmware MKA and MKB is not compatible with BPX Switch Software Release 9.2x and later.
2. For Switch Software 9.2, MPLS and PNNI controllers cannot coexist.
3. In Release 9.2.30 and later, nodes might declare a communication break when using the BXM virtual trunking feature. The problem has been observed under the following conditions:
–At least two virtual trunks share a common port at one node, but their remote end points terminate on different nodes.
–The virtual trunks are used to carry networking (rt_op) traffic.
The simplest example follows below:
node_A ------ vtrk ----- node_B -----vtrk -----node_C
On the above diagram, node_B is a virtual trunk share a common port
With this topology, "node_A" sees "node_C" as unreachable and vice-versa; however, "node_A" communicates to "node_B," and "node_B" communicates to "node_C."
•The problem is caused by a misprogrammed trunk networking channel. In the above example, the misprogramming occurs at "node_B." A channel that should be programmed for ingress and egress operation is programmed as egress only.
Workarounds:
–BXM firmware MEH and later contains the fix for this bug (CSCdr51875).
–BXM virtual trunking (no VT wraparound) can still be implemented using Software Release 9.2.20 and higher.
–If virtual trunks are not yet in use, the VT wraparound solution can be implemented in release 9.2.30 and higher (CSCdr51875).
4. When the cnfrsrc command is used to delete VSI partitions on an interface, software does not check if any Soft Permanent Virtual Circuit (SPVC) connections exists on that partition. Even if there are SPVC connections on a partition, the partition can be deleted using the cnfrsrc command. The only protection is that users are provided with a warning when they try to delete the partition.
If there are SPVC connections on a partition and if the partition is deleted, the SPVC connections will be left in a undefined and unrecoverable state. Hence, before deleting a VSI partition, ensure that all the SPVC connections are deleted on that partition.
5. For UVM cards, there will be no new revisions of Model A firmware. When attempting to download Model A firmware to a UVM, software will give the user an error message indicating that the firmware does not match the card type. Note that there is no problem with continuing to use existing UVM cards running the old firmware(CSCdp08741).
6. There is a new traffic class added in Release 9.2.20 that causes a trunk parameter conflict with pre-9.2.20 node. The conflict fails adding trunk between 9.2.20 BTM/ATM and pre- 9.2.20 BTM/ATM.
All ATM traffic classes are set for BTM/ALM trunks and is hidden to the user. The introduction of rt-VBR traffic class in 9.2.20 makes it different from pre-9.2.20 BTM/ALM trunk traffic class. The user can not change the ATM traffic class for BTM/ALM trunk.
This problem exists with a new BTM/ALM trunk on an upgraded 9.2.20 node but does not exist with an upgraded BTM/ALM trunk since the rt-VBR traffic class is not set while upgrading (CSCdm64345).
7. The cloud port to which a virtual trunk is connected should have ILMI polling disabled. Otherwise, it could lead to a virtual trunk being clear on one end and declaring Virtual Trunk Path Failure at the other end (CSCdm52909).
8. In a BPX that contains BCC cards with 64MB, there is no limitation. All 12 available slots can contain BXM or Enhanced-BXM cards.
In a BPX that contains BCC cards with 32MB, a maximum of 10 legacy BXM cards are allowed. If some Enhanced-BXM cards are used in place of BXM, then each Enhanced-BXM will count as two BXM cards.
9. For performance reasons, AIS status of connections is not sent to the standby BCC. After switchcc, it may take a few minutes to update the AIS status of connections. If dspcon does not show the proper status of AIS or the dspalms screen shows an incorrect number of AIS, (after switchcc) wait for few minutes so that the status gets updated. (The dspalms and dspcon commands show the status of AIS.)
10. Hitless rebuild has similar limitations to that of a switchcc and full rebuild:
•On IGX nodes, there is a four second continuity break. (Same as in a switchcc.)
•There might be brief communication breaks with other nodes in the network. This will be logged in the event log of the node. There is no traffic loss or trunk failures. (This is similar to a switchcc and depends highly on the network and number of connections.)
•Some line/trunk cards that are in the standby state may reset during a hitless rebuild.
•The statistics that are collected by the Cisco Wan Manager will not be maintained across a rebuild.
Some will be re-enabled automatically. These include:
•Auto statistics
•Summary statistics
•Real-Time statistics
All other statistics have to be re-enabled for collection after a hitless rebuild takes place. These mainly include the user statistics.
11. UVM cards in Y-redundancy will mismatch if one is burned with Idle Code Suppression Firmware and the other is not.
When installing/burning Idle Code Suppression Firmware on UVM pairs, the Y-redundancy must be removed, firmware in both UVM cards burned, and then the Y-redundancy can be restored.
12. Mismatch is reported when replacing a BXM card with another BXM card that has a different port group, even though both BXM cards have the identical channel number.
13. When upgrading from Release 9.1 to 9.2, the 9.1 statistics on BXM/UXM cards are supported to maintain compatibility. However, once a user configures a statistics level in 9.2, the statistics cannot be configured back to 9.1 statistics.
There is no 9.1 statistics support for BXM/UXM cards that were shipped with 9.2 firmware since the BXM/UXM card has the default level 1 statistics.
Therefore, when using a UXM with 9.2, a user must either:
•Leave the statistics level untouched (this will work for UXM cards upgraded from 9.1)
OR
•Set level 2 on the card
14. The BXM and UXM channel statistics level feature gives these cards the capability of collecting more than four statistics per connection. However, it is the controller card's limitations, available memory, and performance, that indicates how many statistics can actually be collected from the cards and then reported to the Cisco Wan Manager (CWM).
The BCC-3-64 can collect at most three interval statistics per connection when there are 16,000 AutoRoute (AR) connections configured on the node. (Interval statistics are those statistics that are reported to the CWM. They are often referred to as TFTP statistics.)
You can collect approximately 48,000 statistics (3 x 16,000) on the BCC-3-64. This is approximate because there are many variables that will affect this value, such as are peaks enabled, how many buckets are collected, are all connection of the same type, are trunk, line or port statistics enabled, and so on.
With this approximation of 48,000 statistics on the BCC-3-64, this then means that as a rough estimate you could enable 32 statistics on 1,500 connections, 48 statistics on 1,000 connections or nine statistics on 5,000 connections, and so on. The approximation formula being:
max_stats_per_connection = 48,000/number_of_connections
15. In Release 9.1, the UXM card ran a proprietary IMA communication protocol. This protocol matched that used on the MGX 8220 4 IMATM-B cards and hence could be connected together to form a trunk. In Release 9.2, standards-compliant IMA are supported on the UXM card and standards-compliant IMATM-B on MGX 8220 5.0.x must be used to form a trunk. There should be no effect on UXM-IMA trunks connected to other UXM-IMA trunks in 9.1 to 9.2 interoperability mode.
16. The transmit rate on an IGX IMA trunk can be altered at the local node with any trunk outage. It is possible that the transmit rates are different at the two ends of an IMA trunk. After this trunk is deleted, it cannot be added back unless the transmit rates are the same.
17. When doing a flash upgrade from Release 9.1 to 9.2, the software error 1427 may be logged on the BPX/IGX node during a non-graceful upgrade. This error can be ignored since it is harmless to the network (CSCdm14613).
18. Reconfiguring trunk parameters might cause connections to be rerouted if the changed bandwidth load is smaller than what was used by the connections that use the trunk.
19. If LMI/ILMI is provided by the BCC:
The maximum possible number of ports on the BPX 8600 that can be configured with LMI/ILMI enabled is 52. However, each BPX will support up to a total of 16 feeder trunks and each feeder trunk will have LMI enabled. That is, if a BPX 8600 is configured with only two feeder trunks, then only (52 - 2) = 50 ports can have LMI/ILMI enabled.
If LMI/ILMI is provided by the BXM firmware:
•There is no limitation on the number of ports that can have LMI/ILMI enabled.
•When running ILMI on the BXM, ILMI version 3.1 WITHOUT address registration is supported.
20. Virtual Path Connections with cells whose VCI values are above 4095 will be transmitted correctly only if the path is exclusively through BXM trunks and terminate at BXM ports.
21. The feature of CIR=0 for Frame Relay connections is not supported for connections terminating between FRM cards in IGX nodes and FRSM cards in an MGX 8220 shelf.
22. SVC connections are derouted after decreasing the allocated bandwidth (increasing Statistic Reserve). It is the design intent that increasing the statistical reserve will cause SVC conns to derouted and not be rerouted (CSCst92308).
23. For the loadrev operation, it is important that the Cisco Wan Manager/TFTP buffers are maintained at their default size.
24. Due to a hardware limitation, the BNI trunk will send 13-15 percent more traffic than what it is configured for when the trunk is configured for less speed (cps) than the maximum port speed. This is especially important when the BNI trunk is connected to IMATM pairs, which carry less than T3 bandwidth.
25. When using the shift/no-shift feature on a BPX 8600 node's port card, controlled via the cnfport command, the other end of the connection must have the same setting. Otherwise, there will be a loss of continuity.
26. Due to trunk-based loading, any commands having to do with trunk loading and the load model (dspload chklm dsplm, and so on.) need to be done only after waiting a certain period of time. This time is a direct function of the trunk load update interval time (as configurable) plus the conditional update latency time.
27. The external ABR segment control loop on ForeSight (ABRFST) is an option at the user interface. It is supported by UXM-E/BXM-E but is not supported by UXM/BXM hardware. The user should not enable this option on ForeSight connections (CSCdi92451). In any case, there is no coupling between the loops.
28. The interface between a BXM feeder trunk and an MGX 8220 feeder is always considered to be an NNI interface. (CSCdj16808)
29. When adding more than 4000 connections on a BPX node, the VC polling rate must be changed to a higher interval, to accommodate the additional time needed to poll for the statistics for each VC. The cnfsysparm command, parameter 24, must be changed according to the following:
0-3999 connections
|
Polling Rate: 5 Minutes (or higher)
|
4000-7999 connections
|
Polling Rate: 10 Minutes (or higher)
|
> 8000 connections
|
Polling Rate: 15 Minutes
|
30. Given a connection that terminates on an IGX 8400 FRM at one end and an ASI on the other end, tstdelay initiated at the FRM end may not work if the ASI firmware is below the appropriate revision and does not support OAM cells as opposed to supervisory cells. This is because the updated BTM on the IGX will always generate OAM cells. Please check the Compatibility Matrix.
31. Because the detailed card error event log is not retained within BRAM, this information will be lost should a processor rebuild occur. Therefore, when issuing a dspcderrs command on a particular slot, the display will not show the detailed card error information should a rebuild event occur. This functionality has not been modified from previous releases.
32. When a physical-layer failure (for example, LOS) is detected on the BXM, a Major Alarm is generated, and any connection routed over that port is downed (fail state). The software sends a command to the remote end of the connection to generate AIS in the egress direction (CSCdj30543).
Impact:
Since the connection is in a failed state, AIS is generated in the upstream direction (in addition to the downstream direction). Although this does conform to the letter of the I.610 standard, this is not necessarily what a user would expect to see, because it interferes with the RDI response from the end-to-end connection termination point. (A fault in the downstream direction causes a fault in the upstream direction.)
Reason for the current implementation:
The BNI can not generate AIS. If there is a fault at a BNI trunk, the current mechanism is to cause AIS to be generated by the BXM port by downing the connection. Since the BXM can generate only OAM cells from the RCMP, and the RCMP is in the ingress path, the cells must be backward routed to the egress (egress QE). Also, since end-to-end OAM cells are required, the ingress QE must be configured to drop ALL cells in the ingress path. This creates a break in continuity in the opposite direction, and AIS cells must also be generated at the other end of the same connection, in the upstream direction of the original fault.
33. There are problems in the downgrade mechanism that can cause database corruption. If a downgrade is performed immediately after upgrading, the Stby_Info revision fields are not yet filled in on the new active CC. They don't get filled in until there is an upcard response from the new locked CC. This causes a restart instead of a switchcc. If the locked CC is reset, then downgrade immediately, a restart will occur instead of a switchcc. (CSCdj30811).
34. In order to test/simulate the Y-redundant switchover of ASI T3 or E3 pairs the resetcd command must be used, or by pulling out the active card. It will not be correctly simulated by doing a dncd (down card) on the active card. Using dncd will cause cell discards (CSCdj08923).
35. UBR traffic gains an advantage over ABR traffic when UBR and ABR PVCs are combined on the same network. This is because UBR and ABR PVCs share the same Qbin (Class of Service Queue) on the BXM card. ABR PVCs use a flow control mechanism, VSVD, which ensures that traffic sources slow down when the Qbin usage exceeds the EFCI threshold. However, UBR PVCs do not have this throttling mechanism. Therefore, ABR will throttle back whereas UBR will not. This unfair advantage is not considered a problem, since the decision to share a Qbin for ABR and UBR traffic was intentional. Any best-effort service that one would route over UBR can be routed over ABR(VSVD), with the additional benefit of protecting resources in the network. If UBR and ABR PVCs are required then:
Option 1: Consider adding all best-effort PVCs as UBR
Option 2: Isolate the ABR and UBR paths by using cnfpref command to ensure that ABR and UBR PVCs do not share the same queues.
Option 3: To provide UBR service on a connection, rather than setting up a UBR connection, do the following:
Step 1 Set up an ABRSTD connection.
Step 2 Enable VSVD.
Step 3 Disable FCES (Flow Control External Segment).
Step 4 Disable DEFAULT EXTENDED PARAMETERS.
Step 5 Choose policing option "4" to allow access as UBR.1 (PCR policing only). This connection has ABR VSVD in the network and allows UBR.1 access. The MCR for such ABRSTD connection may be set at the minimum acceptable value of 6 cells per second (explained later to do so).
To provide ABR service on a connection, set up an ABRSTD connection, enable VSVD and enable FCES to allow RM cells to be passed to and from customer equipment. The MCR for such ABRSTD connections can be set at any user-desired value.
When the network is experiencing congestion, all the affected ABRSTD connections, regardless of the services (ABR or UBR) they are carrying, will all be throttled back at the VSVD points at the network edge. During network congestion, connections carrying UBR services are virtually stopped (to a throughput of a mere 6 cps) while connections carrying ABR services can send at a much higher, user-desired MCR. This option would avoid that UBR service gains an unfair advantage over ABR service while sharing the same CoS queue.
36. Combining Frame Based Traffic Control (FBTC) and non-FBTC connections within a Class of Service can cause FBTC connections to not receive a fair share of bandwidth. For example, if VBR connections are added at a terminating port, and some of these VBR connections have FBTC enabled while other VBR connections have FBTC disabled, the VBR connections with FBTC disabled may obtain all of the excess bandwidth before the connections with FBTC enabled receive any of the excess bandwidth. The same holds true for ABR or UBR connections. This is relevant only where FBTC and non-FBTC connections share a Qbin, either at a port or at a trunk.
37. The maximum number of VC PARMs supported: 749 for BCC-32 MB, 2,999 for BCC-64 MB. (CSCdj48589).
VC PARMs are Virtual Circuit Parameters combinations/sets. One set of VC Parameter is used for each unique Virtual Circuit that has been provisioned. Identically provisioned VCs (exclusive of end points) use the same set of parameters. Thus, on a 32MB BCC, a total of 749 uniquely configured Virtual Circuits can be provisioned.
38. Care must be taken when changing the Deroute Delay parameter, which is controlled by the cnftrk command. This defaults to zero, but if set to anything but zero, connection rerouting, due to a trunk failure, will be delayed as provided by the parameter.
Required Workarounds
1. When adding a node into an existing network, ensure that its node number is unique prior to a actually adding it into the network. Use the rnmnd command, and renumber the individual node while it is still stand-alone. This will make the joining of this node much simpler, and will avoid the problem of a node renumbering an active network, as described below.
2. There is a problem with node renumbering. Node renumbering (the rnmnd command) should be executed only during a stable network environment and only if absolutely necessary. A stable network environment would be, for example, one in which no connection was added for the past 30 minutes and no topology change was made in the last hour and there are no alarms or node unreachabilities. Node renumbering must be done only when the network is stable to reduce the possibility of certain temporarily blocked messages during the node renumbering process from being delivered to the wrong nodes. This would occur after the completion of the node renumbering process. It is recommended that a node be renumbered prior to being added to the network.
3. The settling time for network-wide updates can take a long time in certain situations. Specifically, the settling time for updates due to network-wide topology changes and connections in a large network when a processor switchover occurs can take a long time. The time is proportional to the number of nodes as well as the number of connections. A general estimate would be 30 seconds per node. During the period of transitions (when the updates are occurring) some network operations such as adding connections might in some cases take somewhat longer to complete.
4. When using Cisco Wan Manager, there could be a problem with communicating with a node that just had a processor switchover. The problem is within the SPARCstation itself and its caching of EtherNet addresses. It can be solved by execution the following command on the workstation as the superuser: # arp -d <node_name>
5. Users may not use the command addcon slot.1-24 v to add 24 voice connections to a CVM/UVM at once. Instead, they must separate this activity into two or more commands, so that no more than 16 connections are added at once. This is an issue only for voice connections. Data connections can be added using the "1-24" syntax. This also applies when the CVM/UVM circuit line is an E1, in which case "1-32" would apply (CSCdj14319).
6. Statistics must be disabled prior to the start of an upgrade, prior to the issuing of the first loadrev command. Statistics should be disabled from the Cisco Wan Manager, which is the Statistics collection manager.
7. Statistics sampling must be disabled prior to the start of an upgrade (using off1/off2), prior to the issuing of the first loadrev command. Statistics sampling state machines should be disabled from the Command Line Interface.
8. When a switchcc is executed on a BPX 8600 configured with two BCC-4 cards and contains a BXM-622 trunk card, there may be a bad clock path problem reported. It is indicated as a Minor Alarm - bad clock path. This is a transitory problem, although the alarm indication persists. To clear this, execute the clrclkalm command.
Additional Documentation
•To take advantage of the dual SIU when upgrading to the BCC-4, the BPX 8600 node must have a new backplane which has dual traces incorporating with the BCC-4.
The command dspbpnv can be issued to verify if the node has the new backplane or the old backplane. The following chart details the bit fields for the BCC Backplane NOVRAM format, the values in bytes numbered 4 and 5 describe the back plane type.
The command cnfbpnv can be used to configure the backplane, if backplane is so enabled.
16-Bit Word
|
Byte # (hex)
|
Contents
|
0
|
0,1
|
Hardware revision
|
1
|
2,3
|
Backplane Type (usually 0x65=101 decimal)
|
2
|
4,5
|
Backplane version (0x0000:old 0x0001:new)
|
3
|
6,7
|
Backplane serial number in ASCII - MSB
|
4
|
8,9
|
Backplane serial number in ASCII - MSB
|
5
|
A,B
|
Backplane serial number in ASCII - LSB
|
6
|
C,D
|
Board FAB number, in ASCII - MSB
|
7
|
E,F
|
Board FAB number, in ASCII - MSB
|
8
|
10,11
|
Board FAB number, in ASCII - MSB
|
9
|
12,13
|
Board FAB number, in ASCII - MSB
|
A
|
14,15
|
Board FAB number, in ASCII - MSB
|
B
|
16,17
|
Board FAB number, in ASCII - LSB
|
C
|
18,19
|
Unused
|
D
|
1A,1B
|
Unused
|
E
|
1C,1D
|
Unused
|
F
|
1E,1F
|
Checksum bytes - Not supported
|
•The peak intervals are controlled to be only those values for which peaks can be accurately collected. The rules for peak intervals are as follows:
–It cannot be 0.
–It must be a multiple of the polling interval.
–It must be a factor of the bucket interval.
–It can be the same as the bucket interval.
•There are additional commands to control trunk and line loopbacks in this release:
–addlnlocrmtlp <trunk> | <line>
On the node on which it is executed, it creates a loopback within the port such that the cells do not leave the card.
–addlnloclp <trunk> | <line>
On the node on which it is executed, it creates a loop such that incoming cells are looped back to the other end.
–dellnlp <trunk> | <line>
Removes the loopback added by either of the above two commands.
•The card synchronization (Hitless-switchcc) feature can be turned on/off using on3/off3 command. For example, enter at the command line:
– on3 4
This will enable the card-synchronization feature.
–off3 4
This will disable the card-synchronization feature.
In order for the feature to work, the line statistics sampling should always be enabled (via on2 1 command) and the front card installed must support the card-synchronization feature. The dspcd command provides an easy way to determine whether the front card supports this new feature. If the front card supports the feature, the following message is shown on the dspcd screen:
Front card supports card synchronization
Additional debug commands are added to allow synchronization between the interface card and the CC database:
–synccd <slot_number>|*
The <slot_number> is for a particular slot that supports the card synchronization feature;
* For all cards that support the card-synchronization feature.
–dspsyncstats <slot_number>|*
This command displays the number of connections reconciled during the synchronization process after a switchcc for different slots.
* For all slots supporting this feature.
Compatibility Notes
For a complete list of firmware revisions supported, see the Compatibility Matrix document, which is included in this release package.
This release will run with Release 4.0.0x, 4.1.0x, or 5.0.0x of the MGX 8220.
Compatibility Matrix
This section contains compatibility information for Release 9.2.47.
BPX 8600 Firmware Compatibility
Table 4 lists the Cisco BPX firmware.
Table 4 Cisco BPX Firmware
PCB Description
|
dspcds Name
|
Card Name in FW Image
|
Model
|
Latest F/W
|
Min F/W
|
BCC boot
|
BCC
|
BCC
|
B
|
HBJ
|
HBJ
|
BCC3-32 boot
|
BCC-3
|
BCC
|
C
|
HCM
|
HCM
|
BCC3-64 boot
|
BCC-3
|
BCC
|
D
|
HDM
|
HDM
|
BCC4 boot
|
BCC-4
|
BCC
|
E
|
HEM
|
HEM
|
BCC4-128 boot
|
BCC-4
|
BCC
|
H
|
HHM
|
HHM
|
ASI 2T3/2E3
|
ASI-T3
|
ASI
|
C
|
UCF
|
UCF
|
ASI 2T3/2E3
|
ASI-E3
|
ASI
|
C
|
UCF
|
UCF
|
ASI-155-E
|
ASI155E
|
ASI-155
|
E
|
WEC
|
WEC
|
ASI-155
|
ASI-155
|
ASI-155
|
H
|
WHC
|
WHC
|
ASM
|
ASM
|
—
|
A
|
GAC
|
GAC
|
BNI-3T3/3E3
|
BNI-T3
|
BNI
|
C
|
TCM
|
TCM
|
BNI-3T3/3E3
|
BNI-E3
|
BNI
|
C
|
TCM
|
TCM
|
BNI-155
|
BNI-155
|
BNI-155
|
B
|
VBR
|
VBR
|
BNI-155-E
|
BNI155E
|
BNI-155
|
D
|
VDR
|
VDR
|
BXM-BME
|
BME
|
BME
|
K
|
n/s
|
n/s
|
BXM-T3-8/12
|
BXM-T3
|
BXM
|
E
|
MEK
|
MEB
|
BXM-E3-8/12
|
BXM-E3
|
BXM
|
E
|
MEK
|
MEB
|
BXM-155-4/8
|
BXM-155
|
BXM
|
E
|
MEK
|
MEB
|
BXM-622/622-2
|
BXM-622
|
BXM
|
E
|
MEK
|
MEB
|
BXM-T3-8E/12E/12EX
|
BXM-T3
|
BXM
|
E
|
MEK
|
MED
|
BXM-E3-8E/12E/12EX
|
BXM-E3
|
BXM
|
E
|
MEK
|
MED
|
BXM-155-4D/8D/4DX/8DX
|
BXM-155
|
BXM
|
E
|
MEK
|
MED
|
BXM-622-2D/DX/2DX
|
BXM-622
|
BXM
|
E
|
MEK
|
MED
|
IGX 8400 Firmware Compatibility
Table 5 lists the Cisco IGX firmware.
Table 5 Cisco IGX Firmware
PCB Description
|
dspcds Name
|
Card Name in Firmware Image
|
Model
|
Latest F/W
|
Min F/W
|
NPM boot
|
NPM
|
NPM
|
A
|
RAS
|
RAR
|
NPM 32 boot
|
NPM
|
NPM
|
B
|
RBS
|
RBR
|
NPM 64 boot
|
NPM
|
NPM|NPM-64
|
C
|
RCS
|
RCR
|
NPM-B 32 boot
|
NPM
|
NPM|NPM-32B
|
E
|
RES
|
RER
|
NPM-B 64 boot
|
NPM
|
NPM|NPM-64B
|
F
|
RFS
|
RFR
|
IGX-ALM/A
|
ALM
|
ALM-A
|
A
|
CAF
|
CAE
|
IGX-ALM/B
|
ALM
|
ALM-B
|
B
|
CBL
|
CBH
|
IGX-BTM/B
|
BTM
|
BTM
|
A
|
IAF
|
IAF
|
IGX-BTM/B
|
BTM
|
BTM
|
B
|
IBL
|
IBL
|
IGX-BTM/B
|
BTM
|
BTM
|
D
|
IDC
|
IDC
|
IGX-CVM-DS0A
|
CVM
|
CVM
|
A
|
DAF
|
DAF
|
IGX-CVM
|
CVM
|
CVM
|
B
|
DBF
|
DBF
|
IGX-CVM-TT
|
CVM
|
CVM
|
C
|
DCA
|
DCA
|
IGX-FRM
|
FRM
|
FRM
|
D
|
FDZ
|
FDZ
|
IGX-FRM-31
|
FRM
|
FRM-31
|
E
|
FEZ
|
FEZ
|
IGX-FRM-2
|
FRM
|
FRM-2
|
F
|
FFD
|
FFD
|
FRM (B)
|
FRM
|
FRM
|
H
|
FHB
|
FHB
|
IGX-FRM
|
FRM
|
FRM
|
J
|
FJB
|
FJA
|
IGX-FRM-31
|
FRM
|
FRM-31
|
K
|
FKB
|
FKA
|
IGX-FTM
|
FTM
|
FTM
|
B
|
JBJ
|
JBJ
|
IGX-FTM
|
FTM
|
FTM
|
C
|
JCB
|
JCB
|
IGX-HDM
|
HDM
|
HDM
|
C
|
SCF
|
SCF
|
IGX-LDM
|
LDM
|
LDM
|
C
|
LCC
|
LCB
|
IGX-NTM
|
NTM
|
NTM
|
E
|
NEK
|
NEK
|
IGX-NTM (B)
|
NTM
|
NTM
|
F
|
NFK
|
NFH
|
IGX-UFM-4C/8C
|
UFM
|
UFM-C
|
A
|
ZAW
|
ZAN
|
IGX-UFM-4C/8C
|
UFM
|
UFM-C
|
B
|
ZBH
|
ZBA
|
IGX-UFM-8C
|
UFM
|
UFM-C
|
C
|
n/s
|
n/s
|
IGX-UFM-U
|
UFMU
|
UFM-U
|
A
|
YAP
|
YAH
|
IGX-UFM-U
|
UFMU
|
UFM-U
|
B
|
YBF
|
YBA
|
IGX-UFM-U
|
UFMU
|
UFM-U
|
C
|
n/s
|
n/s
|
IGX-UVM
|
UVM
|
UVM
|
A
|
DAE
|
DAC
|
IGX-UVM
|
UVM
|
UVM
|
B
|
DBD
|
DBD
|
IGX-UVM
|
UVM
|
UVM
|
C
|
DCA
|
DCA
|
IGX-UVM
|
UVM
|
UVM
|
D
|
DDF
|
DDF
|
IGX-UVM
|
UVM
|
UVM
|
E
|
DEH
|
DEA
|
IGX-UXM
|
UXM
|
UXM
|
B
|
ABL
|
ABJ
|
IGX-UXME
|
UXM
|
UXM
|
B
|
ABL
|
ABJ
|
Note IGX-UVM model E supersedes models A, B, and C firmware. A, B, and C are obsoleted and must not be used.
MGX 8220 Firmware Compatibility
Table 6 lists the Cisco MGX 8220 firmware.
Table 6 Cisco MGX 8220 Firmware
| |
|
5.0
|
4.1
|
4.0
|
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
Latest F/W
|
Min F/W
|
Latest F/W
|
Min F/W
|
ASC F/W
|
ASC
|
5.0.18
|
5.0.10
|
4.1.12
|
4.1.00
|
4.0.21
|
4.0.04
|
ASC Boot
|
ASC
|
1.0.03
|
1.0.01
|
1.0.03
|
4.0.04
|
1.0.01
|
4.0.03
|
ASC/2 FW
|
ASC
|
5.0.18
|
5.0.10
|
4.1.12
|
4.1.00
|
4.0.21
|
4.0.09
|
ASC/2 Boot
|
ASC
|
1.0.03
|
1.0.01
|
1.0.03
|
4.0.04
|
1.0.01
|
4.0.04
|
ASC/2F FW
|
ASC
|
5.0.18
|
5.0.10
|
4.1.12
|
4.1.05
|
4.0.21
|
4.0.21
|
ASC/2F Boot
|
ASC
|
1.0.03
|
1.0.01
|
1.0.03
|
1.0.01
|
1.0.01
|
1.0.01
|
BNM-T3
|
BNM-T3
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
BNM-E3
|
BNM-E3
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
BNM-155
|
BNM-155
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
FRSM-4T1
|
FRSM-4T1
|
4.0.24
|
4.0.19
|
4.0.24
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM-4E1
|
FRSM-4E1
|
4.0.24
|
4.0.19
|
4.0.24
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM-4T1-C
|
FRSM-4T1-C
|
4.0.24
|
4.0.19
|
4.0.24
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM-4E1-C
|
FRSM-4E1-C
|
4.0.24
|
4.0.19
|
4.0.24
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM Boot
|
FRSM-4T1
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
FRSM Boot
|
FRSM-4E1
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
FRSM Boot
|
FRSM-4T1-C
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
FRSM Boot
|
FRSM-4E1-C
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
SRM T1E1 (B)
|
SRM-T1E1
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
SRM 3T3
|
SRM-3T3
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
n/a
|
CESM-4T1
|
CESM-4T1
|
4.0.18
|
4.0.15
|
4.0.18
|
4.0.11
|
4.0.15
|
4.0.04
|
CESM-4E1
|
CESM-4E1
|
4.0.18
|
4.0.15
|
4.0.18
|
4.0.11
|
4.0.15
|
4.0.04
|
CESM Boot
|
CESM-4T1
|
4.0.01
|
4.0.01
|
4.0.01
|
4.0.00
|
4.0.01
|
4.0.00
|
CESM Boot
|
CESM-4E1
|
4.0.01
|
4.0.01
|
4.0.01
|
4.0.00
|
4.0.01
|
4.0.00
|
CESM-8T1
|
CESM-8T1
|
5.0.15
|
4.1.05
|
4.1.10
|
4.1.00
|
n/s
|
n/s
|
CESM-8E1
|
CESM-8E1
|
5.0.15
|
4.1.05
|
4.1.10
|
4.1.00
|
n/s
|
n/s
|
CESM-8 Boot
|
CESM-8T1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.1.00
|
n/s
|
n/s
|
CESM-8 Boot
|
CESM-8E1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.1.00
|
n/s
|
n/s
|
AUSM-4T1
|
AUSM-4T1
|
4.0.22
|
4.0.19
|
4.0.22
|
4.0.13
|
4.0.19
|
4.0.04
|
AUSM-4E1
|
AUSM-4E1
|
4.0.22
|
4.0.19
|
4.0.22
|
4.0.13
|
4.0.19
|
4.0.04
|
AUSM Boot
|
AUSM-4T1
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
AUSM Boot
|
AUSM-4E1
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
4.0.00
|
FRSM-8T1
|
FRSM-8T1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM-8E1
|
FRSM-8E1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.13
|
4.0.19
|
4.0.04
|
FRSM-8T1 Boot
|
FRSM-8T1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
FRSM-8E1 Boot
|
FRSM-8E1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
AUSM-8T1
|
AUSM-8T1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.14
|
4.0.20
|
4.0.04
|
AUSM-8E1
|
AUSM-8E1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.14
|
4.0.20
|
4.0.04
|
AUSMB-8T1
|
AUSMB-8T1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.19
|
4.0.20
|
4.0.19
|
AUSMB-8E1
|
AUSMB-8E1
|
5.0.16
|
5.0.10
|
4.0.25
|
4.0.19
|
4.0.20
|
4.0.19
|
AUSM-8T1E1 Boot
|
AUSM-8T1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
AUSM-8T1E1 Boot
|
AUSM-8E1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
AUSM-8T1E1 Boot
|
AUSMB-8T1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
AUSM-8T1E1 Boot
|
AUSMB-8E1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.00
|
FRSM-HS1
|
FRSM-HS1
|
5.0.15
|
4.0.16
|
4.0.21
|
4.0.11
|
4.0.16
|
4.0.04
|
FRSM-HS1/B
|
FRSM-HS1/B
|
5.0.15
|
4.0.16
|
4.0.21
|
4.0.11
|
4.0.16
|
4.0.04
|
FRSM-HS1 Boot
|
FRSM-HS1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.00
|
1.0.01
|
4.0.00
|
FRSM-HS1 Boot
|
FRSM-HS1/B
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.00
|
1.0.01
|
4.0.00
|
FRSM-HS2
|
FRSM-HS2
|
5.0.14
|
5.0.10
|
n/s
|
n/s
|
n/s
|
n/s
|
FRSM-HS2 Boot
|
FRSM-HS2
|
1.0.01
|
1.0.01
|
n/s
|
n/s
|
n/s
|
n/s
|
IMATM
|
IMATM-T3T1
|
n/s
|
n/s
|
4.0.23
|
4.0.13
|
4.0.19
|
4.0.04
|
IMATM
|
IMATM-E3E1
|
n/s
|
n/s
|
4.0.23
|
4.0.13
|
4.0.19
|
4.0.04
|
IMATM
|
IMATMB-T1
|
5.0.15
|
5.0.10
|
4.0.23
|
4.0.13
|
4.0.19
|
4.0.04
|
IMATM
|
IMATMB-E1
|
5.0.15
|
5.0.10
|
4.0.23
|
4.0.13
|
4.0.19
|
4.0.04
|
IMATM Boot
|
IMATM-T3T1
|
n/s
|
n/s
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.01
|
IMATM Boot
|
IMATM-E3E1
|
n/s
|
n/s
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.01
|
IMATM Boot
|
IMATMB-T1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.01
|
IMATM Boot
|
IMATMB-E1
|
1.0.02
|
1.0.01
|
1.0.02
|
4.0.01
|
1.0.01
|
4.0.01
|
MGX 8250 1.1.3x Firmware Compatibility
Table 7 lists the Cisco MGX 8250 firmware.
Table 7 Cisco MGX 8250 Firmware
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
PXM1
|
PXM-1
|
1.1.34
|
1.1.32
|
PXM1-2-T3E3
|
PXM1-2T3E3
|
1.1.34
|
1.1.32
|
PXM1-4-155
|
PXM1-4OC3
|
1.1.34
|
1.1.32
|
PXM1-1-622
|
PXM1-OC12
|
1.1.34
|
1.1.32
|
MGX-SRM-3T3/C
|
SRM-3T3
|
n/a
|
n/a
|
AX-CESM-8E1
|
CESM-8E1
|
10.0.22
|
10.0.21
|
AX-CESM-8T1
|
CESM-8T1
|
10.0.22
|
10.0.21
|
MGX-AUSM-8E1/B
|
AUSMB-8E1
|
10.0.22
|
10.0.21
|
MGX-AUSM-8T1/B
|
AUSMB-8T1
|
10.0.22
|
10.0.21
|
MGX-CESM-T3
|
CESM-T3
|
10.0.22
|
10.0.21
|
MGX-CESM-E3
|
CESM-E3
|
10.0.22
|
10.0.21
|
AX-FRSM-8E1/E1-C
|
FRSM-8E1
|
10.0.22
|
10.0.21
|
AX-FRSM-8T1/T1-C
|
FRSM-8T1
|
10.0.22
|
10.0.21
|
MGX-FRSM-HS2
|
FRSM-HS2
|
10.0.22
|
10.0.22
|
MGX-FRSM-2CT3
|
FRSM-2CT3
|
10.0.22
|
10.0.22
|
MGX-FRSM-2T3E3
|
FRSM-2T3
|
10.0.23
|
10.0.22
|
MGX-FRSM-2T3E3
|
FRSM-2E3
|
10.0.23
|
10.0.22
|
MGX-FRSM-HS1/B
|
FRSM-HS1/B
|
10.0.22
|
10.0.21
|
MGX-VISM-8T1
|
VISM-8T1
|
2.1.(1)
|
1.5.05
|
MGX-VISM-8E1
|
VISM-8E1
|
2.1.(1)
|
1.5.05
|
MGX-RPM-128M/B
|
RPM
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
MGX-RPM-PR
|
—
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
CWM
|
—
|
10.4.10
|
10.4
|
MGX 8850 1.1.3x Firmware Compatibility
Table 8 lists the Cisco MGX 8850 firmware.
Table 8 Cisco MGX 8850 Firmware
PCB Description
|
CW2000 Name
|
Latest F/W
|
Min F/W
|
PXM1
|
PXM-1
|
1.1.34
|
1.1.32
|
PXM1-2-T3E3
|
PXM1-2T3E3
|
1.1.34
|
1.1.32
|
PXM1-4-155
|
PXM1-4OC3
|
1.1.34
|
1.1.32
|
PXM1-1-622
|
PXM1-OC12
|
1.1.34
|
1.1.32
|
MGX-SRM-3T3/B
|
SRM-3T3
|
n/a
|
n/a
|
MGX-SRM-3T3/C
|
SRM-3T3
|
n/a
|
n/a
|
AX-CESM-8E1
|
CESM-8E1
|
10.0.22
|
10.0.21
|
AX-CESM-8T1
|
CESM-8T1
|
10.0.22
|
10.0.21
|
MGX-AUSM-8E1/B
|
AUSMB-8E1
|
10.0.22
|
10.0.21
|
MGX-AUSM-8T1/B
|
AUSMB-8T1
|
10.0.22
|
10.0.21
|
MGX-CESM-T3
|
CESM-T3
|
10.0.22
|
10.0.21
|
MGX-CESM-E3
|
CESM-E3
|
10.0.22
|
10.0.21
|
AX-FRSM-8E1/E1-C
|
FRSM-8E1
|
10.0.22
|
10.0.21
|
AX-FRSM-8T1/T1-C
|
FRSM-8T1
|
10.0.22
|
10.0.21
|
MGX-FRSM-HS2
|
FRSM-HS2
|
10.0.23
|
10.0.22
|
MGX-FRSM-2CT3
|
FRSM-2CT3
|
10.0.23
|
10.0.22
|
MGX-FRSM-2T3E3
|
FRSM-2T3
|
10.0.23
|
10.0.22
|
MGX-FRSM-2T3E3
|
FRSM-2E3
|
10.0.23
|
10.0.22
|
MGX-FRSM-HS1/B
|
FRSM-HS1/B
|
10.0.22
|
10.0.21
|
MGX-VISM-8T1
|
VISM-8T1
|
2.1.(1)
|
1.5.05
|
MGX-VISM-8E1
|
VISM-8E1
|
2.1.(1)
|
1.5.05
|
MGX-RPM-128M/B
|
RPM
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
MGX-RPM-PR
|
—
|
12.1(5.3)T_XT
|
12.1(5.3)T_XT
|
CWM
|
—
|
10.4.10
|
10.4
|
BPX 8600 Hardware Compatibility
Table 9 lists the Cisco BPX hardware.
Table 9 Cisco BPX Hardware
Card Type
|
Part Numbers
|
Latest H/W
|
Min. H/W
|
Controller Cards
|
BPX-BCC-32M (Non-Orderable)
|
73-213840-00
|
P
|
A
|
BPX-BCC-64M (Non-Orderable)
|
800-04008-04
|
A
|
A
|
BPX-BCC-BC (Non-Orderable)
|
73-211380-00
|
D
|
A
|
BPX-BCC-3-32M (Non-Orderable)
|
800-04004-04
|
R
|
J
|
BPX-BCC-3-64M
|
73-3720-02
|
R
|
J
|
BCC-3BC
|
800-02916-01
|
E
|
A
|
BPX-BCC4V
|
800-03580-06
|
E
|
C
|
BPX-BCC4V/B
|
800-06483-02
|
C
|
A
|
Alarm Group
|
BPX-ASM
|
800-04009-01
|
C
|
A
|
BPX-ASM-BC
|
73-211910-00
|
C
|
A
|
ASM-LM
|
800-211910-10
|
B
|
A
|
BroadBand Switch Group
|
BPX-BXM-T3-8
|
800-02777-07
|
H
|
A
|
BPX-BXM-E3-8
|
800-02779-07
|
H
|
A
|
BPX-BXM-T3-12
|
800-02776-07
|
H
|
A
|
BPX-BXM-E3-12
|
800-02778-07
|
H
|
A
|
BPX-T3/E3-BC
|
73-2759-02
|
A
|
A
|
BPX-BXM-155-8
|
800-02664-07
|
H
|
B (C for APS)
|
BPX-MMF-155-8-BC
|
800-03255-01
|
B
|
A
|
BPX-SMF-155-8-BC
|
800-03257-01
|
B
|
A
|
BPX-SMFLR-155-8-BC
|
800-02593-02
|
B
|
A
|
BPX-BXM-155-4
|
800-02666-07
|
H
|
B (C for APS)
|
BPX-MMF-155-4-BC
|
800-03256-01
|
B
|
A
|
BPX-SMF-155-4-BC
|
800-03258-01
|
B
|
A
|
BPX-SMFLR-155-4-BC
|
800-02594-02
|
B
|
A
|
BPX-BXM-622
|
800-02646-10
|
L
|
D (E for APS)
|
BPX-BXM-622-2
|
800-02638-10
|
L
|
D (E for APS)
|
BPX-622-2-BC
|
73-2884-01
|
D
|
A
|
BPX-SMF-622-BC
|
800-03249-01
|
C
|
A
|
BPX-SMF-622-2-BC
|
800-03251-01
|
C
|
A
|
BPX-SMFLR-622-BC
|
800-03250-01
|
C
|
A
|
BPX-SMFLR-622-2-BC
|
800-03252-01
|
D
|
A
|
BPX-XLR-622
|
800-02738-01
|
C
|
A
|
BPX-XLR-622-2
|
800-02739-01
|
C
|
A
|
BPX-BME
|
800-02855-04
|
B
|
A
|
BPX-BME-OC12
|
73-2469-07
|
F
|
A
|
BPX-BXM-E-T3-8E
|
800-03933-02
|
A
|
A
|
BPX-BXM-E-E3-8E
|
800-03928-02
|
A
|
A
|
BPX-BXM-E-T3-12E
|
800-03931-02
|
A
|
A
|
BPX-BXM-E-E3-12E
|
800-03929-02
|
A
|
A
|
BPX-BXM-E-T3-12EX
|
800-03934-02
|
A
|
A
|
BPX-BXM-E-E3-12EX
|
800-03930-02
|
A
|
A
|
BPX-BXM-E-155-4D
|
800-03094-02
|
A
|
A
|
BPX-BXM-E-155-4DX
|
800-03093-02
|
A
|
A
|
BPX-BXM-E-155-8D
|
800-03092-02
|
A
|
A
|
BPX-BXM-E-155-8DX
|
800-03091-02
|
A
|
A
|
BPX-BXM-E-622-DX
|
800-03151-02
|
A
|
A
|
BPX-BXM-E-622-2D
|
800-03150-02
|
A
|
A
|
BPX-BXM-E-622-2DX
|
800-03149-02
|
A
|
A
|
RDNT-SMF-155-4R
|
800-03677-01
|
J
|
A
|
RDNT-SMF-155-8R
|
800-03679-01
|
K
|
A
|
RDNT-LR-155-8R
|
800-03678-01
|
J
|
A
|
RDNT-LR-622-2R
|
800-03676-01
|
F
|
A
|
RDNT-SMF-622R
|
800-03675-01
|
F
|
A
|
RDNT-SMF-622-2R
|
800-03674-01
|
J
|
A
|
BPX-T3/E3
|
800-03058-02
|
E
|
A
|
BPX-E3-BC
|
73-213070-01
|
E
|
A
|
BPX-MMF-2-BC
|
73-214290-00
|
D
|
A
|
BPX-SMF-2-BC
|
73-216270-00
|
D
|
A
|
BPX-SMFLR-2-BC
|
73-216270-01
|
D
|
A
|
BPX-STM1-EL-4
|
800-03716-02
|
A
|
A
|
BNI-3-T3/C
|
800-02858-02
|
A
|
A
|
BNI-3-E3/C
|
800-02859-02
|
A
|
A
|
SMF-LM-OC3
|
800-216270-10
|
C
|
A
|
SMF-LM-OC3-LR
|
800-216270-11
|
C
|
A
|
MMF-LM-OC3
|
800-214290-10
|
B
|
A
|
LM-3T3
|
800-213070-10
|
D
|
A
|
LM-3E3
|
800-213070-11
|
D
|
A
|
IGX 8400 Hardware Compatibility
Table 10 lists the Cisco IGX hardware.
Table 10 Cisco IGX Hardware
Card Type
|
Part Numbers
|
Latest H/W
|
Min. H/W
|
* Note Below
|
Controller Cards
|
IGX-NPM-32
|
73-2894-01
|
W
|
A
|
—
|
IGX-NPM-64
|
73-2895-01
|
W
|
A
|
—
|
IGX-NPM-32B
|
73-2554-04
|
L
|
A
|
—
|
IGX-NPM-64B
|
73-2363-02
|
C
|
A
|
—
|
IGX-SCM
|
73-3341-01
|
Y
|
A
|
Revision X or later for nodes with UXM IMA trunks
|
Alarm Group
|
IGX-ARM
|
73-218230-00
|
B
|
A
|
—
|
BC-512011
|
73-212360-00
|
D
|
A
|
—
|
Trunk Group
|
|
|
|
—
|
IGX-NTM
|
73-2296-04
|
E
|
A
|
—
|
BC-6271A-TI
|
73-207380-00
|
M
|
A
|
—
|
BC-6171A-E1
|
73-207370-01
|
P
|
A
|
—
|
BC-6083A-SR
|
73-208540-00
|
J
|
A
|
—
|
BC-550150-Y1
|
73-210820-01
|
D
|
A
|
—
|
IGX-BTM/B
|
73-3005-02
|
B
|
A*
|
"*Show AIT H/W Rev, BTM(B)=AIT+ACM1"
|
ACM1
|
73-2921-03
|
W
|
A
|
—
|
BC-571110A-T3
|
73-2879-01
|
L
|
A
|
—
|
BC-571210A-E3
|
73-2679-01
|
K
|
A
|
—
|
BC-571310A-E2
|
73-215940-00
|
D
|
A
|
AIT BC HSSI/E2
|
BC-571410A-HSSI
|
73-216370-00
|
A
|
A
|
AIT GIM HSSI
|
IGX-ALM/A
|
73-2558-03
|
J
|
A
|
—
|
IGX-ALM/B
|
73-2558-03
|
J
|
A
|
—
|
BC-UAI-1T3
|
73-217040-00
|
C
|
A
|
—
|
BC-UAI-1E3
|
73-2986-01
|
E
|
A
|
—
|
IGX-UXM
|
73-2511-03
|
D
|
A
|
—
|
BC-UAI-4-155-SMF
|
73-2703-03
|
D
|
A
|
—
|
BC-UAI-4-155-MMF
|
73-2705-03
|
D
|
A
|
—
|
BC-UAI-2-155-SMF
|
73-2699-03
|
C
|
A
|
—
|
BC-UAI-6-T3
|
73-2952-02
|
A
|
A
|
—
|
BC-UAI-3-T3
|
73-2954-02
|
A
|
A
|
—
|
BC-UAI-6-E3
|
73-2953-02
|
A
|
A
|
—
|
BC-UAI-3-E3
|
73-2955-02
|
A
|
A
|
—
|
BC-UAI-8-E1-BNC
|
73-2932-02
|
C
|
A
|
—
|
BC-UAI-4-E1-BNC
|
73-3061-01
|
C
|
A
|
—
|
BC-UAI-8-T1-DB15
|
73-2941-02
|
C
|
A
|
—
|
BC-UAI-8-E1-DB15
|
73-2942-02
|
C
|
A
|
—
|
BC-UAI-4-T1-DB15
|
73-3059-01
|
C
|
A
|
—
|
BC-UAI-4-E1-DB15
|
73-3060-01
|
C
|
A
|
—
|
BC-UAI-4-STM1E
|
73-3364-02
|
A
|
A
|
—
|
Port Group
|
IGX-FTM
|
73-2519-01
|
M*
|
A*
|
"*Show FTC H/W Rev, FTM=FTC+ACM1A"
|
ACM1A
|
73-2930-03
|
W
|
A
|
—
|
BC-6351A-V35
|
73-213240-00
|
E
|
A
|
FPC-V.35
|
BC-6352A-T1
|
73-213420-00
|
C
|
A
|
FPC-T1
|
BC-6353A-E1
|
73-213410-00
|
B
|
A
|
FPC-E1
|
BC-6354A-X21
|
73-214120-00
|
C
|
A
|
FPC-X21
|
IGX-HDM
|
73-2853-02
|
A
|
F
|
"*Show SDP H/W Rev, HDM=SDP+ACM2"
|
ACM2
|
73-2922-03
|
T
|
A
|
—
|
BC-5082A-V35
|
73-2450-01
|
K
|
A
|
—
|
BC-5083A-RS449
|
73-204850-00
|
V
|
A
|
—
|
BC-5084B-RS232
|
73-2723-01
|
W
|
A
|
—
|
IGX-LDM
|
73-207250-00
|
K
|
A
|
"*Show LDP H/W Rev, LDM=LDP+ACM1A"
|
BC-5286A-RS232
|
73-207180-01
|
L
|
A
|
LDI-4RS232
|
BC-5287A-RS232
|
73-207180-00
|
L
|
A
|
LDI-8RS232
|
IGX-CVM-DSOA
|
73-3002-02
|
D
|
A*
|
"*Show CDP H/W Rev, CVM=CDP+ACM1A"
|
IGX-CVM-T1EC
|
73-3003-03
|
E
|
A*
|
"*Show CDP H/W Rev, CVM=CDP+ACM1A"
|
IGX-CVM-E1EC
|
73-209660-00
|
H*
|
A*
|
"*Show CDP H/W Rev, CVM=CDP+ACM1A"
|
BC-6271A-TI
|
73-207380-00
|
M
|
A
|
—
|
BC-6171A-E1
|
73-207370-01
|
P
|
A
|
—
|
BC-550100-J1
|
73-210820-00
|
C
|
A
|
—
|
IGX-FRM
|
73-2517-03
|
N
|
A
|
—
|
IGX-FRM-31
|
73-2517-03
|
N
|
A
|
—
|
IGX-FRM-2
|
73-2519-01
|
M*
|
A*
|
"*Show FRP H/W Rev, FRM-2=FRP+ACM1A"
|
BC-6251B-V35
|
73-3253-01
|
M
|
A
|
FRI-4V.35-2
|
BC-6254A-X21
|
73-211440-00
|
H
|
A
|
FRI-X.21
|
BC-6355A-X21
|
73-214120-01
|
C
|
A
|
FRI-2X21
|
IGX-UFM-4C
|
73-2531-05
|
N
|
A
|
—
|
IGX-UFM-8C
|
73-2531-05
|
N
|
A
|
—
|
BC-UFI-8T1-DB15
|
73-2444-02
|
D
|
A
|
—
|
BC-UFI-8E1-DB15
|
73-2445-02
|
D
|
A
|
—
|
BC-UFI-8E1-BNC
|
73-2449-02
|
D
|
A
|
—
|
IGX-UFM-U
|
73-2349-04
|
D
|
A
|
—
|
BC-UFI-12V35
|
73-2711-01
|
D
|
A
|
—
|
BC-UFI-12X21
|
73-2712-01
|
D
|
A
|
—
|
BC-UFI-4HSSI
|
73-2693-01
|
C
|
A
|
—
|
IGX-UVM
|
73-2361-04
|
K
|
A
|
—
|
BC-UVI-2E1EC
|
73-2420-01
|
B
|
A
|
—
|
BC-UVI-2T1EC
|
73-2373-01
|
C
|
A
|
—
|
BC-UVI-2J1EC
|
73-2374-01
|
A
|
A
|
—
|
Resolved Anomaly in Release 9.2.47
Table 11 describes the resolved anomaly in Release 9.2.47.
Table 11 Known Anomalies in Release 9.2.47
Bug ID
|
Description
|
CSCea41956
|
Standby BCC status became Cleared in the cause of SWLOG 586.
|
Anomalies in Release 9.2.45
This section describes the known and resolved anomalies and the anomaly status changes in Release 9.2.45.
Known Anomalies in Release 9.2.45
Table 12 lists the known anomalies for this release.
A more in-depth discussion is available in the release note enclosure of the problem record in Bug Navigator.
Table 12 Known Anomalies in Release 9.2.45
Bug ID
|
Description
|
CSCdp48861
|
Symptom: The customer may notice slow UI response or a difficulty logging into the node using the normal VT session. The dspprfhist command shows high RT usage in the TRNS process. The statistics show high RT usage by state machine 55 (0x33).
Conditions: This is due to statistics updates for voice connections. It may be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs).
Workaround: The command off1 17 can be performed. Issuing this command stops the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats.
If you must collect statistics, limit the number of statistics. Frame Relay statistics are collected at 5-minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1-minute intervals. However, the following statistics are reported at 3-second intervals:
•Seconds V.25 Modem On
•Seconds DSI Enabled
•Seconds Off-Hook
•Seconds In Service
|
CSCdr05291
|
Symptom: switchIfService must be specified to delete feeder trunks, but not routing trunks.
Conditions: This requirement confuses CiscoView users.
Workaround: Use the CLI commands to delete feeder trunks.
|
CSCdr45021
|
Symptom: SCT 1 is that default SCT that is reserved for MPLS. When an SES trunk is provisioned with the default SCT not changed to SCT 3, the trunk fails to come up.
Conditions: None.
Workaround: Make sure that the SES uplink uses SCT 3 as the service class template.
|
CSCdu03108
|
Symptom: Software error 1427 logged on BPX node.
Conditions: This issue occurs when you upgrade from Release 9.1.19 to 9.2.3D (prior to Release 9.2.38). In this particular case, the node that logs the 1427 error is sending conditional updates to a node which upgrades during the process.
Workaround: None.
|
CSCdt07203
|
Symptom: The hitless rebuild log filled up due to repeated failed switchccs.
Conditions: A bad standby BCC is required. The node must be running at least 9.2.
Workaround: Clear the hitless log with the command dsphitless c. Or, switchcc less often, so the hitless rebuild log entries have a chance to age out of the log.
|
CSCdu03108
|
Symptom: Software error 1427 logged on BPX node.
Conditions: This issue occurs when upgrading from release 9.1.19 to 9.2.3D (pre 9.2.38). In this particular case, the node logging the 1427 error is sending conditional updates to a node which upgrades during the process.
Workaround: None.
|
CSCdu38434
|
Symptom: Back card revision is shown when the card is absent.
Conditions: This bug is a base line issue that is applicable to all switch software revisions.
Workaround: None.
|
CSCdu45358
|
Symptom: The switchover occured on BPX node when the active card was pulled out. The empty slot for this card was shown in the CLI, but the Network Browser was showing that the active card was still present.
Conditions: None
Workaround: None
|
CSCdv33406
|
Symptom: While the APS(1+1) and the loop clock was configured to the BXM cards, the loop clock seemed to be released automatically upon execution of the switchyred command.
Condition: APS 1+1 setup was present, and switchyred was executed.
Workaround: Manually set the loop clock to NO once, and then set it back to YES again.
|
CSCdv33753
|
Symptom: On BPX nodes the following observations were made after a fall back from 9.3.30 to 9.2.34:
•BPX node logged SWSW error 9000: APS 1+1 trk was in LOS, BXM card was in mismatch.
•BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
Conditions:
1. Network was being prepared for SWSW upgrade from 9.2.34 to 9.3.30 with UXM FW A.C.E, BXM FW M.F.25 at the time.
2. A script was run on all nodes to set parameters for upgrades, check databases, and do network captures.
3. SWSW 9.3.30 was loaded on the standby CC of all nodes (routing and feeder) using loadrev.
4. A runrev 9.3.30 was executed on each (node by node) at 10-15 minute intervals apart.
5. After all nodes (routing and feeder) were upgraded to SWSW 9.3.30, no events were taking place for 30 minutes.
6. A script was run to set the parameters after a node upgrade (for example, turning on statistics).
7. BXM FW M.F.25 was loaded on all nodes and burned on all BXM cards without any problems.
8. UXM FW A.C.01 was loaded on all nodes and burned on all UXM cards at the same time, which yielded no problems.
9. Network was allowed to settle for a long time due to rerouting until zero errors were in network and traffic resumed.
10. At this point the upgrade was successful.
11. A fall back to 9.2.34 was conducted on the entire network using the command: runrev 9.2.34 *. This command unlocked the standby CC and rebuilt the databases using the 9.2.34 BRAM.
12. After the network fallback, the network was allowed to settle over night.
13. After the fallback the network was running SWSW 9.2.34, UXM FW A.C.01, and BXM FW M.F.N.
14. While checking the network health in the morning, a number of problems were observed.
15. Symptoms on BPX nodes were narrowed to observation bpx01 and bpx05:
a. BPX node logged SWSW error 9000: APS 1+1 trunk was in LOS, BXM card was in mismatch.
b. BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
|
CSCdv33753 (continued)
|
16. After DE investigation, the trigger of problems on all BPX nodes was attributed to SWSW error 9000 exception. This exception was caused by the CBUS message 0x60 (delete connections) to the BXM card. In the message, the start and end LCNs are specified to delete a range of connections. However, that start LCN is greater than the end LCN which is incorrect. Therefore, the BXM card sends an error to the BCC and logs the SWSW error 9000.
17. After a resetcd on the mismatched BXMs, the BXMs would recover.
Workaround: None.
|
CSCdw27395
|
Symptom: The following error message displays while adding an NTM_SR trunk: "Abandoned because remote node Transmit Rate setting is different."
Conditions:
1. When the 2048 kbps NTM-SR trunk is decreased to a data rate of 1024 kbps (or any lower data rate, for example, 1536), the data rate changed back to 2048 kbps using cnftrk x.
2. The trunk was added back in the network to see the error message.
3. The NTM-FW is NK02 and SWSW 9.3.4 I 4. This problem was seen on both Y-red and non-Yred cards for V.35 and X.21 interfaces.
Workaround: Decrease the data rate of the trunk (after deleting it) on both sides of the trunk (on igx5/21 and igx7/4). The corruption is done on both the sides, so the database sync up and the trunk can be added.
|
CSCdx20323
|
Symptom: swerr752 is logged on BPX when upgrade BXM fw to MF14.
Conditions: Upgrade BXM fw to MF14 on BPX.
Workaround: Unknown.
|
CSCdx27113
|
Symptom: Customer experienced Seconds in Service for the Frame Relay connections. Sometimes the connection reports more than 100% in service. For example, the value of Seconds in Service for one hour shows 3601 seconds.
Conditions: None.
Workaround: None.
|
CSCdx66192
|
Symptom: After a PVC comes out of an A-bit fail, SWSW does not send a connection alarm message (40, 17, 3, 1, 3) with AIS clear in the NNI Status Bit map to CWM. This failure causes the CWM to consider the connection with end-to-end status as AIS.
Conditions: This symptom occurs very intermittently, and the conditions are not known.
Workaround: Another event to trigger the update (such as the NNI status of the PVC going back to A-bit fail and clear) would normally clear this condition.
|
CSCdy51577
|
Symptom: The trunk parameters could not be modified using the job.
Condition: When more than one virtual trunk exists on a physical interface, configuring the trunk parameters on any one of these virtual trunks fails in the job mode.
Workaround: Configure the virtual trunk through CLI.
|
CSCea33846
|
Symptom: From 9.2.35, the following two points on cross point are not tested by tstber.
•Active BCC -> Active BCC
•Active BCC -> Standby BCC
Conditions: None
Workaround: Use the tstber m command. The point of Slot 7 to 8 is tested by this command.
See the following example:
tstber m 7 8 0 2 1 20 n
where:
•m = Manual
•7 = Primary slot
•8 = Secondary slot
•0 = Destination port
•2 = Qbin number
•1 = Destination channel
•20 = B-frames to send
•n = Stop on errors
|
CSCea55566
|
Symptom: After a switchcc on an IGX, most if not all trunks report large amounts of COMM FAILs using the dsptrkerrs command. The log does not indicate any COMM breaks.
Conditions: IGX node is running 9.2.41 SWSW under normal load and condition is reporting large amounts of COMM FAILs after a switchcc is issued.
Note The errors only seem to occur during the instant the switchcc is in progress. The errors do not continue to increment once the switch is complete.
Workaround: None
|
CSCee39134
|
Symptom: Connections are in loop on a particular port, both VC and VP. No chance to delete with normal CLI, need to patch memory or delete/add the connection back.
Conditions: BPX network is running 9.2.41 during normal operation. No trigger was found so far.
Workaround: Delete and re-add the connection or patch memory for each connection.
|
CSCee68430
|
Symptom: ABR STD PVC (channel) level statistics (dspchstathist) are reporting over PCR utilization in 9.2.36 SWSW for user and TFTP defined cell transmission statistics over a 15 minute bucket. Statistics shown by the switch CLI command, dspchstats, do not show cells being sent over PCR transmission.
The following statistics are affected:
•48—Cells Transmitted to Network
•49—Cells Received from Network
Conditions: This issue occurs with high PVC bandwidth utilization.
Workaround: None.
Further Problem Description: Use the following commands to see problem:
•cnfchstats <pvc> 49 15 E 60 4 Y
•cnfchstats <pvc> 48 15 E 60 4 Y
•dspchstathist <pvc> 48 USER 15
•dspchstathist <pvc> 49 USER 15
The 15 minute samples must not exceed (pcr * 1800 seconds).
|
CSCin16665
|
Symptom: Software error 3041 is generated after BXM-OC12 card was pulled out and reinserted. Connection database was corrupted.
Conditions: Some DAX PVCs existed on the cards between lines 1 and 2.
Workaround: None.
|
|
|
|
|
|
|
|
|
CSCin17623
|
Symptom: Configured preferred path gets reset to Not Configured.
Conditions: This symptom occurs while changing the trunk cost of a trunk.
Workaround: None.
|
|
|
|
|
|
CSCin17893
|
Symptom: Software logged errors (52, 516, 1120, 518, 1125, 502, 589, 504, and 505) on the node during a graceful upgrade from 9.2.38 to 9.2.4J.
Conditions: This issue occurs with graceful upgrades from 9.2.38 to 9.2.4J.
Workaround: None.
|
|
|
|
|
|
Resolved Anomaly in Release 9.2.45
Table 13 lists the resolved anomaly in this release.
Table 13 Resolved Anomaly in Release 9.2.45
Bug ID
|
Description
|
CSCed45736
|
Suddenly, all BXM and Standby BCC are removed.
|
Anomaly Status Changes in Release 9.2.45
Table 14 lists the anomaly status changes in this release.
Table 14 Anomaly Status Changes in Release 9.2.45
Bug ID
|
Description
|
CSCdk22430
|
Status Change: Closed
Symptom: Checksum word 15 of backplane nvram is not recalculated when words 0-14 are updated using cnfbpnv.
Conditions: This bug was observed with BPX 9.1.01.
Workaround: No workaround is available at this time.
|
CSCdk83372
|
Status Change: Duplicate of CSCdt52981
Symptom: While attempting to download switch software to a node, the dspdnld screen shows the download progressing and then suddenly stop and begin the download anew. No messages, which describe the nature of the problem, are logged in the event log (dsplog). The output from the tftpstats, dspilacc, or dsppna commands do not describe the problem.
Conditions: The background conditions that cause the process to fail are unknown.
Workaround: None.
Further Problem Description: This DDTs report was raised to address the need for further debugging/logging output to diagnose these file load failure issues. Without further information no judgment as to the actual root cause of the failure can be determined.
|
CSCdm22426
|
Status Change: Closed
Symptom: While using jobs to down or up the connection based on a job trigger, the job fails if dspbob is executed while the control signal toggles.
Conditions: This issue was observed with IGX 8.2.56.
Workaround: Retrigger the job after executing the dspbob command.
|
CSCdm47794
|
Status Change: Duplicate of CSCdz30108
Symptom: The holdover clock locks at 4.9 ppm on a BXM SRM-1 line when the input clock increases beyond 5 ppm. When the input clock comes back down even to 0 ppm, the holdover clock stays at 4.9 ppm and never recovers.
Conditions: This issue occurs on a BPX running 9.1.10 with a BXM line card 4 port, MBY firmware, and STRM-1 4 port back card.
Workaround: Issue the resetcd command after the input clock falls below 4.9 ppm to clear the holdover problem.
|
CSCdp44912
|
Status Change: Closed
Symptom: Upgrade from IGX 9.1.04 to 9.1.16 causes UXM Y-red card to go into mismatch.
Conditions: These are the same as the symptom.
Workaround: Issue the delyred command to avoid this condition.
Further Problem Description: This problem is an isolated VC shaping upgrade mechanism.
|
CSCdr25278
|
Status Change: Closed
Symptom: The SUT and EMS are not indicating LOS as per UNI 3.1.
Conditions: None.
Workaround: None.
|
CSCdr55714
|
Status Change: Duplicate of CSCdr69455
Symptom: ILMI state of a port on an MGX and BPX are mismatched. While the MGX side shows up and normal, BPX side shows disabled.
Conditions: None.
Workaround: None.
|
CSCds81526
|
Status Change: Closed
Symptom:
1. The BPX and IGX nodes were loaded to their connections limit.
2. The dncon COS 0 i was issued on bpx03.
3. It took more that 2.5 hours to down about 70% of 16K connections (performance issue).
4. When the connections were downed, the master side and the slave side of the connections were showing down state which is correct.
5. Then, the upcon COS 0 command was issued to up all downed connections. The command was issued on a BPX node.
6. After CPU idle time reached 70%+ (steady-state) network wide, the master side of any connection is upped correctly (OK state). However, the slave side of the connection is still in down state (it should be in up state as well).
7. The problem is the upcon network messages were not propagated to the slave-side of the connection. The result is in spite of issuing upcon the master-side of the connection is upped, but the slave-side of the connection is still in down state.
8. This condition means upcon finite state machines could be timing out, or handling of such an inconsistent state under heavy loading still needs to be accounted for.
Conditions:
1. Almost all 9.2.34 + 9.2.23 SWSW and SWFW features were provisioned.
2. The nodes were loaded to their limit with maximum terminating connections, VTs, and so forth.
3. Topology is of a tiered network with MGX 8220 and IGX feeders, MPLS LSCs and Less, and SES PNNI controllers.
Frequency: Intermittent.
Steps to re-create the problem: It is unclear whether or not it is reproducible.
Workaround: Issue the upcon command for each connection one by one, which is not efficient.
|
CSCdt07203
|
Status Change: Resolved; Not resolved in this release
Symptom: The hitless rebuild log filled up due to repeated failed switchccs.
Conditions: A bad standby BCC is required. The node must be running at least 9.2.
Workaround: Clear the hitless log with the command dsphitless c. Or, switchcc less often, so the hitless rebuild log entries have a chance to age out of the log.
|
CSCdt55864
|
Status Change: Closed
Symptom: The Cisco WAN Manager's Statistics Collection Manager cannot parse the TFTP statistics file received from the IGX node.
Conditions: This problem only occurs when the IGX node has FastPad connection enabled, and is collecting TFTP statistics on those connections.
Customer Impact: When this problem occurs the customer is not able to collect TFTP interval statistics from the IGX node.
Workaround: There is no work around for collecting the FastPad connection statistics. However, if you disable statistics collection on the FastPad connections, you can collect all of the other statistics.
Further Problem Description: When writing the variable key length for the various FastPad connection types, an extra byte is added. This byte throws off CWM parsing. The parser has no way of recovering. Therefore, the entire statistics file is discarded as corrupted or bad.
|
CSCdu03108
|
Status Change: Unreproducible
Symptom: Software error 1427 logged on BPX node.
Conditions: This issue occurs when upgrading from release 9.1.19 to 9.2.3D (pre 9.2.38). In this particular case, the node logging the 1427 error is sending conditional updates to a node which upgrades during the process.
Workaround: None.
|
CSCdu38434
|
Status Change: Resolved; Not resolved in this release
Symptom: Back card revision is shown when the card is absent.
Conditions: This bug is a base line issue that is applicable to all switch software revisions.
Workaround: None.
|
CSCdw27395
|
Status Change: Resolved; Not resolved in this release
Symptom: The following error message displays while adding an NTM_SR trunk: "Abandoned because remote node Transmit Rate setting is different."
Conditions:
1. When the 2048 kbps NTM-SR trunk is decreased to a data rate of 1024 kbps (or any lower data rate, for example, 1536), the data rate changed back to 2048 kbps using cnftrk x.
2. The trunk was added back in the network to see the error message.
3. The NTM-FW is NK02 and SWSW 9.3.4 I 4. This problem was seen on both Y-red and non-Yred cards for V.35 and X.21 interfaces.
Workaround: Decrease the data rate of the trunk (after deleting it) on both sides of the trunk (on igx5/21 and igx7/4). The corruption is done on both the sides, so the database sync up and the trunk can be added.
|
CSCdx20323
|
Status Change: Resolved; Not resolved in this release
Symptom: The swerr752 is logged on the BPX when upgrading BXM FW to MF14.
Conditions: This issue occurs when upgrading BXM FW to MF14 on BPX.
Workaround: Unknown.
|
CSCdx62131
|
Status Change: Duplicate of CSCdr85197
Symptom: In a large network scenario using the standard (non concurrent) AutoRoute algorithm, trunks have failed. After they recover, some connections fail to route.
Conditions: When two nodes select the same random back off timer, this symptom can be verified by using nwtrace. Both nodes sw181 and sw155 were backing off for the same amount of time. The random backoff algorithm has to be enhanced to overcome this situation.
Workaround: Disable CM and enable CM (off1 11, on1 11).
|
CSCdx87582
|
Status Change: Closed
Symptom: Injecting errors at a rate of 10-3 into one line of a six-line IMA group on a UXM card causes the line to be declared in Major Frame Bit Error in the dspphyslnerrs output.
However this line is not removed from the UXM IMA group, which causes traffic passing over the trunk to error. Increasing the error injection rate to 10-2 causes the line to declare a Major Loss of cell. Then, the line is removed from the IMA group, and bandwidth is reduced.
PHYSLN Type Current Line Alarm Status TRK
3.1 E1/30 Clear - OK 3.1(6)
3.2 E1/30 Clear - OK 3.1(6)
3.3 E1/30 Clear - OK 3.1(6)
3.4 E1/30 Clear - OK 3.1(6)
3.5 E1/30 Clear - OK 3.1(6)
3.6 E1/30 Major - Frames Bit Errors 3.1(6)
31.1 T1/24 Clear - OK 31.1
32.1 T3/636 Clear - OK 32.1
32.2 T3/636 Clear - OK 32.2
32.3 T3/636 Clear - OK 32.3
Last Command: dspphyslns
TRK Type Current Line Alarm Status Other End
.1(6) E1/177 Clear - OK xx/3.1(6)
31.1 T1/24 Clear - OK xxx/10.1
32.1 T3/636 Clear - OK xx/12.1
32.2 T3/636 Clear - OK x/1.7
32.3 T3/690 Clear - OK xxx/9.1
Last Command: dsptrks
Conditions: This issue occurred in tests performed with 9.2.38 SWSW and ABR firmware on the UXM-E.
Workaround: Current workaround is to down the line, or remove it from the group until errors clear.
|
CSCdy06091
|
Status Change: Closed
Symptom: Combining is not working correctly for NTS traffic.
Conditions: Combining is set to 1 for NTS traffic, so one FastPacket exists only in one cell. However, this condition only works in one direction.
Workaround: The problem appears to be caused by a particular trunk in the network. Reroute the connection away from each trunk one at a time until to problem trunk is located, and the connection is routed away from it.
|
CSCdy51577
|
Status Change: Resolved; Not resolved in this release
Symptom: The trunk parameters using the Job could not be modified.
Condition: When more than one virtual trunk exists on a physical interface, configuring the trunk parameters on any one of these virtual trunks fails in the Job mode.
Workaround: Configure the virtual trunk through CLI.
|
CSCin17429
|
Status Change: Closed
Symptom: Tx/Rx cell statistics parameters are disabled for channels terminating on AIS-OC3 interface.
Condition: None.
Workaround: None.
|
|
|
|
|
|
CSCin17623
|
Status Change: Resolved; Not resolved in this release
Symptom: Configured preferred path gets reset to Not Configured.
Condition: This symptom occurs while changing trunk cost of a trunk.
Workaround: None.
|
|
|
|
|
|
Anomalies in Release 9.2.43
This section lists the known and resolved anomalies and the anomaly status changes in Release 9.2.43.
Known Anomalies in Release 9.2.43
Table 15 lists the known anomalies for this release.
A more in-depth discussion is available in the release note enclosure of the problem record in Bug Navigator.
Table 15 Known Anomalies in Release 9.2.43
Bug ID
|
Description
|
CSCdk22430
|
Symptom: Checksum word 15 of backplane nvram is not recalculated when words 0-14 are updated using cnfbpnv.
Conditions: This bug was observed with BPX 9.1.01.
Workaround: No workaround is available at this time.
|
CSCdk83372
|
Status Change: Duplicate of CSCdt52981.
Symptom: While attempting to download switch software to a node, the dspdnld screen shows the download progressing and then suddenly stop and begin the download anew. No messages, which describe the nature of the problem, are logged in the event log (dsplog). The output from the tftpstats, dspilacc, or dsppna commands do not describe the problem.
Conditions: The background conditions that cause the process to fail are unknown.
Workaround: None.
Further Problem Description: This DDTs report was raised to address the need for further debugging/logging output to diagnose these file load failure issues. Without further information no judgment as to the actual root cause of the failure can be determined.
|
CSCdm22426
|
Status Change: Closed
Symptom: While using jobs to down or up the connection based on a job trigger, the job fails if dspbob is executed while the control signal toggles.
Conditions: This issue was observed with IGX 8.2.56.
Workaround: Retrigger the job after executing the dspbob command.
|
CSCdm47794
|
Status Change: Duplicate of CSCdz30108
Symptom: The holdover clock locks at 4.9 ppm on a BXM SRM-1 line when the input clock increases beyond 5 ppm. When the input clock comes back down even to 0 ppm, the holdover clock stays at 4.9 ppm and never recovers.
Conditions: This issue occurs on a BPX running 9.1.10 with a BXM line card 4 port, MBY firmware, and STRM-1 4 port back card.
Workaround: Issue the resetcd command after the input clock falls below 4.9 ppm to clear the holdover problem.
|
CSCdp44912
|
Status Change: Closed
Symptom: Upgrade from IGX 9.1.04 to 9.1.16 causes UXM Y-red card to go into mismatch.
Conditions: These are the same as the symptom.
Workaround: Issue the delyred command to avoid this condition.
Further Problem Description: This problem is an isolated VC shaping upgrade mechanism.
|
CSCdp48861
|
Symptom: The customer may notice slow UI response or a difficulty logging into the node using the normal VT session. The dspprfhist command shows high RT usage in the TRNS process. The statistics shows high RT usage by state machine 55 (0x33).
Conditions: This is due to statistics updates for voice connections. It may be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs).
Workaround: The command off1 17 can be performed. Issuing this command stops the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats.
If you must collect statistics, limit the number of statistics. Frame Relay statistics are collected at 5-minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1-minute intervals. However, the following statistics are reported at 3-second intervals:
•Seconds V.25 Modem On
•Seconds DSI Enabled
•Seconds Off-Hook
•Seconds In Service
|
CSCdr05291
|
Symptom: switchIfService must be specified to delete feeder trunks, but not routing trunks.
Conditions: This requirement confuses CiscoView users.
Workaround: Use the CLI commands to delete feeder trunks.
|
CSCdr25278
|
Symptom: The SUT and EMS are not indicating LOS as per UNI 3.1.
Conditions: None.
Workaround: None.
|
CSCdr45021
|
Symptom: SCT 1 is default SCT reserved for MPLS. When an SES trunk is provisioned, if the default SCT is not changed to SCT 3, trunk will fail to come up.
Conditions: None.
Workaround: Make sure that SES uplink uses SCT 3 as service class template.
|
CSCdr55714
|
Symptom: ILMI state of a port on an MGX and BPX are mismatched. While the MGX side shows up and normal, BPX side shows disabled.
Conditions: None.
Workaround: None.
|
CSCds81526
|
Status Change: Closed
Symptom:
1. The BPX and IGX nodes were loaded to their connections limit.
2. The dncon COS 0 i was issued on bpx03.
3. It took more that 2.5 hours to down about 70% of 16K connections (performance issue).
4. When the connections were downed, the master side and the slave side of the connections were showing down state which is correct.
5. Then, the upcon COS 0 command was issued to up all downed connections. The command was issued on a BPX node.
6. After CPU idle time reached 70%+ (steady-state) network wide, the master side of any connection is upped correctly (OK state). However, the slave side of the connection is still in down state (it should be in up state as well).
7. The problem is the upcon network messages were not propagated to the slave-side of the connection. The result is in spite of issuing upcon the master-side of the connection is upped, but the slave-side of the connection is still in down state.
8. This condition means upcon finite state machines could be timing out, or handling of such an inconsistent state under heavy loading still needs to be accounted for.
Conditions:
1. Almost all 9.2.34 + 9.2.23 SWSW and SWFW features were provisioned.
2. The nodes were loaded to their limit with maximum terminating connections, VTs, and so forth.
3. Topology is of a tiered network with MGX 8220 and IGX feeders, MPLS LSCs and Less, and SES PNNI controllers.
Frequency: Intermittent.
Steps to re-create the problem: It is unclear whether or not it is reproducible.
Workaround: Issue the upcon command for each connection one by one, which is not efficient.
|
CSCdt07203
|
Symptom: The hitless rebuild log filled up due to repeated failed switchccs.
Conditions: A bad standby BCC is required. The node must be running at least 9.2.
Workaround: Clear the hitless log with the command dsphitless c. Or, switchcc less often, so the hitless rebuild log entries have a chance to age out of the log.
|
CSCdt55864
|
Symptom: The Cisco WAN Manager's Statistics Collection Manager cannot parse the TFTP statistics file received from the IGX node.
Conditions: This problem only occurs when the IGX node has FastPad connection enabled, and is collecting TFTP statistics on those connections.
Customer Impact: When this problem occurs the customer is not able to collect TFTP interval statistics from the IGX node.
Workaround: There is no work around for collecting the FastPad connection statistics. However, if you disable statistics collection on the FastPad connections, you can collect all of the other statistics.
Further Problem Description: When writing the variable key length for the various FastPad connection types, an extra byte is added. This byte throws off CWM parsing. The parser has no way of recovering. Therefore, the entire statistics file is discarded as corrupted or bad.
|
CSCdu38434
|
Symptom: Back card revision is shown when the card is absent.
Conditions: This bug is a base line issue that is applicable to all switch software revisions.
Workaround: None.
|
CSCdu45358
|
Symptom: The switchover occured on BPX node when the active card was pulled out. The empty slot for this card was shown in the CLI, but the Network Browser was showing that the active card was still present.
Conditions: None
Workaround: None
|
CSCdv33406
|
Symptom: While the APS(1+1) and the loop clock was configured to the BXM cards, the loop clock seemed to be released automatically upon execution of the switchyred command.
Condition: APS 1+1 setup was present, and switchyred was executed.
Workaround: Manually set the loop clock to NO once, and then set it back to YES again.
|
CSCdv33753
|
Symptom: On BPX nodes the following observations were made after a fall back from 9.3.30 to 9.2.34:
•BPX node logged SWSW error 9000: APS 1+1 trk was in LOS, BXM card was in mismatch.
•BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
Conditions:
1. Network was being prepared for SWSW upgrade from 9.2.34 to 9.3.30 with UXM FW A.C.E, BXM FW M.F.25 at the time.
2. A script was run on all nodes to set parameters for upgrades, check databases, and do network captures.
3. SWSW 9.3.30 was loaded on the standby CC of all nodes (routing and feeder) using loadrev.
4. A runrev 9.3.30 was executed on each (node by node) at 10-15 minute intervals apart.
5. After all nodes (routing and feeder) were upgraded to SWSW 9.3.30, no events were taking place for 30 minutes.
6. A script was run to set the parameters after a node upgrade (for example, turning on statistics).
7. BXM FW M.F.25 was loaded on all nodes and burned on all BXM cards without any problems.
8. UXM FW A.C.01 was loaded on all nodes and burned on all UXM cards at the same time, which yielded no problems.
9. Network was allowed to settle for a long time due to rerouting until zero errors were in network and traffic resumed.
10. At this point the upgrade was successful.
11. A fall back to 9.2.34 was conducted on the entire network using the command: runrev 9.2.34 *. This command unlocked the standby CC and rebuilt the databases using the 9.2.34 BRAM.
12. After the network fallback, the network was allowed to settle over night.
13. After the fallback the network was running SWSW 9.2.34, UXM FW A.C.01, and BXM FW M.F.N.
14. While checking the network health in the morning, a number of problems were observed.
15. Symptoms on BPX nodes were narrowed to observation bpx01 and bpx05:
a. BPX node logged SWSW error 9000: APS 1+1 trunk was in LOS, BXM card was in mismatch.
b. BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
|
CSCdv33753 (continued)
|
16. After DE investigation, the trigger of problems on all BPX nodes was attributed to SWSW error 9000 exception. This exception was caused by the CBUS message 0x60 (delete connections) to the BXM card. In the message, the start and end LCNs are specified to delete a range of connections. However, that start LCN is greater than the end LCN which is incorrect. Therefore, the BXM card sends an error to the BCC and logs the SWSW error 9000.
17. After a resetcd on the mismatched BXMs, the BXMs would recover.
Workaround: None.
|
CSCdw27395
|
Symptom: The following error message displays while adding an NTM_SR trunk: "Abandoned because remote node Transmit Rate setting is different."
Conditions:
1. When the 2048 kbps NTM-SR trunk is decreased to a data rate of 1024 kbps (or any lower data rate, for example, 1536), the data rate changed back to 2048 kbps using cnftrk x.
2. The trunk was added back in the network to see the error message.
3. The NTM-FW is NK02 and SWSW 9.3.4 I 4. This problem was seen on both Y-red and non-Yred cards for V.35 and X.21 interfaces.
Workaround: Decrease the data rate of the trunk (after deleting it) on both sides of the trunk (on igx5/21 and igx7/4). The corruption is done on both the sides, so the database sync up and the trunk can be added.
|
CSCdx20323
|
Symptom: The swerr752 is logged on the BPX when upgrading BXM FW to MF14.
Conditions: This issue occurs when upgrading BXM FW to MF14 on BPX.
Workaround: Unknown.
|
CSCdx27113
|
Symptom: Customer experienced Seconds in Service for the Frame Relay connections. Sometimes the connection reports more than 100% in service, for example, the value of Seconds in Service for one hour shows 3601 seconds.
Conditions: None.
Workaround: None.
|
CSCdx62131
|
Symptom: In a large network scenario using the standard (non concurrent) AutoRoute algorithm, trunks have failed. After they recover, some connections fail to route.
Conditions: When two nodes select the same random back off timer, this symptom can be verified by using nwtrace. Both nodes sw181 and sw155 were backing off for the same amount of time. The random backoff algorithm has to be enhanced to overcome this situation.
Workaround: Disable CM and enable CM (off1 11, on1 11).
|
CSCdx66192
|
Symptom: After a PVC comes out of and A-bit fail, SWSW does not send a connection alarm message (40, 17, 3, 1, 3) with AIS clear in the NNI Status Bit map to CWM. This failure causes the CWM to consider the connection with end-to-end status as AIS.
Conditions: This symptom occurs very intermittently, and the conditions are not known.
Workaround: Another event to trigger the update (such as the NNI status of the PVC going back to A-bit fail and clear) would normally clear this condition.
|
CSCdx87582
|
Symptom: Injecting errors at a rate of 10-3 into one line of a six-line IMA group on a UXM card causes the line to be declared in Major Frame Bit Error in the dspphyslnerrs output.
However this line is not removed from the UXM IMA group, which causes traffic passing over the trunk to error. Increasing the error injection rate to 10-2 causes the line to declare a Major Loss of cell. Then, the line is removed from the IMA group, and bandwidth is reduced.
PHYSLN Type Current Line Alarm Status TRK
3.1 E1/30 Clear - OK 3.1(6)
3.2 E1/30 Clear - OK 3.1(6)
3.3 E1/30 Clear - OK 3.1(6)
3.4 E1/30 Clear - OK 3.1(6)
3.5 E1/30 Clear - OK 3.1(6)
3.6 E1/30 Major - Frames Bit Errors 3.1(6)
31.1 T1/24 Clear - OK 31.1
32.1 T3/636 Clear - OK 32.1
32.2 T3/636 Clear - OK 32.2
32.3 T3/636 Clear - OK 32.3
Last Command: dspphyslns
TRK Type Current Line Alarm Status Other End
.1(6) E1/177 Clear - OK xx/3.1(6)
31.1 T1/24 Clear - OK xxx/10.1
32.1 T3/636 Clear - OK xx/12.1
32.2 T3/636 Clear - OK x/1.7
32.3 T3/690 Clear - OK xxx/9.1
Last Command: dsptrks
Conditions: This issue occurred in tests performed with 9.2.38 SWSW and ABR firmware on the UXM-E.
Workaround: Current workaround is to down the line, or remove it from the group until errors clear.
|
CSCdy06091
|
Symptom: Combining is not working correctly for NTS traffic.
Conditions: Combining is set to 1 for NTS traffic, so one FastPacket exists only in one cell. However, this condition only works in one direction.
Workaround: The problem appears to be caused by a particular trunk in the network. Reroute the connection away from each trunk one at a time until to problem trunk is located, and the connection is routed away from it.
|
CSCdy51577
|
Symptom: The trunk parameters using the Job could not be modified.
Condition: When more than one virtual trunk exists on a physical interface, configuring the trunk parameters on any one of these virtual trunks fails in the Job mode.
Workaround: Configure the virtual trunk through CLI.
|
CSCin16665
|
Symptom: Software error 3041 is generated after BXM-OC12 card was pulled out and reinserted. Connection database was corrupted.
Conditions: Some DAX PVCs existed on the cards between lines 1 and 2.
Workaround: None.
|
|
|
|
|
|
|
|
|
CSCin17429
|
Symptom: Tx/Rx cell statistics parameters are disabled for channels terminating on AIS-OC3 interface.
Condition: None.
Workaround: None.
|
|
|
|
|
|
CSCin17623
|
Symptom: Configured preferred path gets reset to Not Configured.
Condition: This symptom occurs while changing trunk cost of a trunk.
Workaround: None.
|
|
|
|
|
|
CSCin17893
|
Symptom: Software log observed on the node while graceful upgrade from 9.2.38 to 9.21.4J (errors: 52, 516, 1120, 518, 1125, 502, 589, 504, and 505).
Conditions: Graceful upgrade from 9.2.38 to 9.2.4J.
Workaround: None.
|
|
|
|
|
|
Resolved Anomalies in Release 9.2.43
Table 16 lists the resolved anomalies in this release.
Table 16 Resolved Anomalies in Release 9.2.43
Bug ID
|
Description
|
CSCdx67113
|
Wrong parameter passed to send_pdu_to_ip() function from ilmi_hdlr.
|
|
|
|
|
|
CSCdy62028
|
PXM (feeder) node update status to IGX causes Frame Bit errors.
|
|
|
|
|
|
|
|
CSCdz07944
|
HDM connections report failed after upgrading to 9.2.42.
|
|
|
|
|
|
|
|
|
|
Anomaly Status Changes in Release 9.2.43
Table 17 lists the status changes for known anomalies in this release.
Table 17 Anomaly Status Changes in Release 9.2.43
Bug ID
|
Description
|
CSCdr55714
|
ILMI state mismatched in BPX display. Duplicated of CSCdr69455.
|
CSCdt55864
|
Statistics file key size for FastPads is incorrect. Closed.
|
CSCdu38434
|
Network Browser shows back card revision for the absent backcards as EW by default. Resolved.
|
CSCdw27395
|
Cannot ADDTRK after changing CNFTRK NTM-SR trk from 2048 kbps to lower value. Resolved.
|
CSCdx20323
|
752 logged when FW upgraded. Resolved for future release.
|
CSCdx66192
|
Incorrect robust msg (40,17,3,1,3) received. Unreproducible.
|
CSCdy51577
|
cnftrk fails in the job mode when multiple virtual trunks exist. Resolved for future release.
|
CSCin16665
|
SWERR 3041 occurs after BXM card pullout. Unreproducible.
|
|
|
|
|
|
|
|
|
CSCin17429
|
ASI-OC3 does not have enough channel statistics parameters (only AIS/FERF available). Closed.
|
|
|
|
|
|
CSCin17623
|
Configuring trunk cost resets the preferred path of the connections on BPX. Resolved for future release.
|
|
|
|
|
|
CSCin17893
|
SW err 52,516,1120,518,504,505,1125,589 while upgrading from 9238-924J. Unreproducible.
|
|
|
|
|
|
Anomalies in Release 9.2.42
This section lists the known and resolved anomalies and the anomaly status changes in Release 9.2.42.
Known Anomalies in Release 9.2.42
Table 18 lists the known anomalies for this release.
Table 18 Known Anomalies in Release 9.2.42
Bug ID
|
Description
|
CSCdk22430
|
Status Change: Closed
Symptom: Checksum word 15 of backplane nvram is not recalculated when words 0-14 are updated using cnfbpnv.
Conditions: This bug was observed with BPX 9.1.01.
Workaround: No workaround is available at this time.
|
CSCdk83372
|
Status Change: Duplicate of CSCdt52981.
Symptom: While attempting to download switch software to a node, the dspdnld screen shows the download progressing and then suddenly stop and begin the download anew. No messages, which describe the nature of the problem, are logged in the event log (dsplog). The output from the tftpstats, dspilacc, or dsppna commands do not describe the problem.
Conditions: The background conditions that cause the process to fail are unknown.
Workaround: None.
Further Problem Description: This DDTs report was raised to address the need for further debugging/logging output to diagnose these file load failure issues. Without further information no judgment as to the actual root cause of the failure can be determined.
|
CSCdm22426
|
Status Change: Closed
Symptom: While using jobs to down or up the connection based on a job trigger, the job fails if dspbob is executed while the control signal toggles.
Conditions: This issue was observed with IGX 8.2.56.
Workaround: Retrigger the job after executing the dspbob command.
|
CSCdm47794
|
Status Change: Duplicate of CSCdz30108
Symptom: The holdover clock locks at 4.9 ppm on a BXM SRM-1 line when the input clock increases beyond 5 ppm. When the input clock comes back down even to 0 ppm, the holdover clock stays at 4.9 ppm and never recovers.
Conditions: This issue occurs on a BPX running 9.1.10 with a BXM line card 4 port, MBY firmware, and STRM-1 4 port back card.
Workaround: Issue the resetcd command after the input clock falls below 4.9 ppm to clear the holdover problem.
|
CSCdp44912
|
Status Change: Closed
Symptom: Upgrade from IGX 9.1.04 to 9.1.16 causes UXM Y-red card to go into mismatch.
Conditions: These are the same as the symptom.
Workaround: Issue the delyred command to avoid this condition.
Further Problem Description: This problem is an isolated VC shaping upgrade mechanism.
|
CSCdp48861
|
Symptom: The customer may notice slow UI response or a difficulty logging into the node using the normal VT session. The dspprfhist command shows high RT usage in the TRNS process. The statistics shows high RT usage by state machine 55 (0x33).
Conditions: This is due to statistics updates for voice connections. It may be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs).
Workaround: The command off1 17 can be performed. Issuing this command stops the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats.
If you must collect statistics, limit the number of statistics. Frame Relay statistics are collected at 5-minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1-minute intervals. However, the following statistics are reported at 3-second intervals:
•Seconds V.25 Modem On
•Seconds DSI Enabled
•Seconds Off-Hook
•Seconds In Service
|
CSCdr05291
|
Symptom: switchIfService must be specified to delete feeder trunks, but not routing trunks.
Conditions: This requirement confuses CiscoView users.
Workaround: Use the CLI commands to delete feeder trunks.
|
CSCdr25278
|
Symptom: The SUT and EMS are not indicating LOS as per UNI 3.1.
Conditions: None.
Workaround: None.
|
CSCdr45021
|
Symptom: SCT 1 is default SCT reserved for MPLS. When an SES trunk is provisioned, if the default SCT is not changed to SCT 3, trunk will fail to come up.
Conditions: None.
Workaround: Make sure that SES uplink uses SCT 3 as service class template.
|
CSCdr55714
|
Symptom: ILMI state of a port on an MGX and BPX are mismatched. While the MGX side shows up and normal BPX side shows disabled.
Conditions: None.
Workaround: None.
|
CSCds81526
|
Status Change: Closed
Symptom:
1. The BPX and IGX nodes were loaded to their connections limit.
2. The dncon COS 0 i was issued on bpx03.
3. It took more that 2.5 hours to down about 70% of 16K connections (performance issue).
4. When the connections were downed, the master side and the slave side of the connections were showing down state which is correct.
5. Then, the upcon COS 0 command was issued to up all downed connections. The command was issued on a BPX node.
6. After CPU idle time reached 70%+ (steady-state) network wide, the master side of any connection is upped correctly (OK state). However, the slave side of the connection is still in down state (it should be in up state as well).
7. The problem is the upcon network messages were not propagated to the slave-side of the connection. The result is in spite of issuing upcon the master-side of the connection is upped, but the slave-side of the connection is still in down state.
8. This condition means upcon finite state machines could be timing out, or handling of such an inconsistent state under heavy loading still needs to be accounted for.
Conditions:
1. Almost all 9.2.34 + 9.2.23 SWSW and SWFW features were provisioned.
2. The nodes were loaded to their limit with maximum terminating connections, VTs, and so forth.
3. Topology is of a tiered network with MGX 8220 and IGX feeders, MPLS LSCs and LERs, and SES PNNI controllers.
Frequency: Intermittent.
Steps to re-create the problem: It is unclear whether or not it is reproducible.
Workaround: Issue the upcon command for each connection one by one, which is not efficient.
|
CSCdt07203
|
Symptom: The hitless rebuild log filled up due to repeated failed switchccs.
Conditions: A bad standby BCC is required. The node must be running at least 9.2.
Workaround: Clear the hitless log with the command dsphitless c. Or, switchcc less often, so the hitless rebuild log entries have a chance to age out of the log.
|
CSCdt55864
|
Symptom: The Cisco WAN Manager's Statistics Collection Manager cannot parse the TFTP statistics file received from the IGX node.
Conditions: This problem only occurs when the IGX node has FastPad connection enabled, and is collecting TFTP statistics on those connections.
Customer Impact: When this problem occurs the customer is not able to collect TFTP interval statistics from the IGX node.
Workaround: There is no work around for collecting the FastPad connection statistics. However, if you disable statistics collection on the FastPad connections, you can collect all of the other statistics.
Further Problem Description: When writing the variable key length for the various FastPad connection types, an extra byte is added. This byte throws off CWM parsing. The parser has no way of recovering. Therefore, the entire statistics file is discarded as corrupted or bad.
|
CSCdu38434
|
Symptom: Back card revision is shown when the card is absent.
Conditions: This bug is a base line issue that is applicable to all switch software revisions.
Workaround: None.
|
CSCdu45358
|
Symptom: The switchover occured on BPX node when the active card was pulled out. The empty slot for this card was shown in the CLI, but the Network Browser was showing that the active card was still present.
Conditions: None.
Workaround: None.
|
CSCdv33406
|
Symptom: While the APS(1+1) and the loop clock was configured to the BXM cards, the loop clock seemed to be released automatically upon execution of the switchyred command.
Condition: APS 1+1 setup was present, and switchyred was executed.
Workaround: Manually set the loop clock to NO once, and then set it back to YES again.
|
CSCdv33753
|
Symptom: On BPX nodes the following observations were made after a fall back from 9.3.30 to 9.2.34:
•BPX node logged SWSW error 9000: APS 1+1 trk was in LOS, BXM card was in mismatch.
•BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
Conditions:
1. Network was being prepared for SWSW upgrade from 9.2.34 to 9.3.30 with UXM FW A.C.E, BXM FW M.F.25 at the time.
2. A script was run on all nodes to set parameters for upgrades, check databases, and do network captures.
3. SWSW 9.3.30 was loaded on the standby CC of all nodes (routing and feeder) using loadrev.
4. A runrev 9.3.30 was executed on each (node by node) at 10-15 minute intervals apart.
5. After all nodes (routing and feeder) were upgraded to SWSW 9.3.30, no events were taking place for 30 minutes.
6. A script was run to set the parameters after a node upgrade (for example, turning on statistics).
7. BXM FW M.F.25 was loaded on all nodes and burned on all BXM cards without any problems.
8. UXM FW A.C.01 was loaded on all nodes and burned on all UXM cards at the same time, which yielded no problems.
9. Network was allowed to settle for a long time due to rerouting until zero errors were in network and traffic resumed.
10. At this point the upgrade was successful.
11. A fall back to 9.2.34 was conducted on the entire network using the command: runrev 9.2.34 *. This command unlocked the standby CC and rebuilt the databases using the 9.2.34 BRAM.
12. After the network fallback, the network was allowed to settle over night.
13. After the fallback the network was running SWSW 9.2.34, UXM FW A.C.01, and BXM FW M.F.N.
14. While checking the network health in the morning, a number of problems were observed.
15. Symptoms on BPX nodes were narrowed to observation bpx01 and bpx05:
a. BPX node logged SWSW error 9000: APS 1+1 trunk was in LOS, BXM card was in mismatch.
b. BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
|
CSCdv33753 (continued)
|
16. After DE investigation, the trigger of problems on all BPX nodes was attributed to SWSW error 9000 exception. This exception was caused by the CBUS message 0x60 (delete connections) to the BXM card. In the message, the start and end LCNs are specified to delete a range of connections. However, that start LCN is greater than the end LCN which is incorrect. Therefore, the BXM card sends an error to the BCC and logs the SWSW error 9000.
17. After a resetcd on the mismatched BXMs, the BXMs would recover.
Workaround: None.
|
CSCdw27395
|
Symptom: The following error message displays while adding an NTM_SR trunk: "Abandoned because remote node Transmit Rate setting is different."
Conditions:
1. When the 2048 kbps NTM-SR trunk is decreased to a data rate of 1024 kbps (or any lower data rate, for example, 1536), the data rate changed back to 2048 kbps using cnftrk x.
2. The trunk was added back in the network to see the error message.
3. The NTM-FW is NK02 and SWSW 9.3.4 I 4. This problem was seen on both Y-red and non-Yred cards for V.35 and X.21 interfaces.
Workaround: Decrease the data rate of the trunk (after deleting it) on both sides of the trunk (on igx5/21 and igx7/4). The corruption is done on both the sides, so the database sync up and the trunk can be added.
|
CSCdx20323
|
Symptom: The swerr752 is logged on the BPX when upgrading BXM FW to MF14.
Conditions: This issue occurs when upgrading BXM FW to MF14 on BPX.
Workaround: Unknown.
|
CSCdx27113
|
Symptom: Customer experienced Seconds in Service for the Frame Relay connections. Sometimes the connection reports more than 100% in service, for example, the value of Seconds in Service for one hour shows 3601 seconds.
Conditions: None.
Workaround: None.
|
CSCdx62131
|
Symptom: In a large network scenario using the standard (non concurrent) AutoRoute algorithm, trunks have failed. After they recover, some connections fail to route.
Conditions: When two nodes select the same random back off timer, this symptom can be verified by using nwtrace. Both nodes sw181 and sw155 were backing off for the same amount of time. The random backoff algorithm has to be enhanced to overcome this situation.
Workaround: Disable CM and enable CM (off1 11, on1 11).
|
CSCdx66192
|
Symptom: After a PVC comes out of and A-bit fail, SWSW does not send a connection alarm message (40, 17, 3, 1, 3) with AIS clear in the NNI Status Bit map to CWM. This failure causes the CWM to consider the connection with end-to-end status as AIS.
Conditions: This symptom occurs very intermittently, and the conditions are not known.
Workaround: Another event to trigger the update (such as the NNI status of the PVC going back to A-bit fail and clear) would normally clear this condition.
|
CSCdx87582
|
Symptom: Injecting errors at a rate of 10-3 into one line of a six-line IMA group on a UXM card causes the line to be declared in Major Frame Bit Error in the dspphyslnerrs output.
However this line is not removed from the UXM IMA group, which causes traffic passing over the trunk to error. Increasing the error injection rate to 10-2 causes the line to declare a Major Loss of cell. Then, the line is removed from the IMA group, and bandwidth is reduced.
PHYSLN Type Current Line Alarm Status TRK
3.1 E1/30 Clear - OK 3.1(6)
3.2 E1/30 Clear - OK 3.1(6)
3.3 E1/30 Clear - OK 3.1(6)
3.4 E1/30 Clear - OK 3.1(6)
3.5 E1/30 Clear - OK 3.1(6)
3.6 E1/30 Major - Frames Bit Errors 3.1(6)
31.1 T1/24 Clear - OK 31.1
32.1 T3/636 Clear - OK 32.1
32.2 T3/636 Clear - OK 32.2
32.3 T3/636 Clear - OK 32.3
Last Command: dspphyslns
TRK Type Current Line Alarm Status Other End
.1(6) E1/177 Clear - OK xx/3.1(6)
31.1 T1/24 Clear - OK xxx/10.1
32.1 T3/636 Clear - OK xx/12.1
32.2 T3/636 Clear - OK x/1.7
32.3 T3/690 Clear - OK xxx/9.1
Last Command: dsptrks
Conditions: This issue occurred in tests performed with 9.2.38 SWSW and ABR firmware on the UXM-E.
Workaround: Current workaround is to down the line, or remove it from the group until errors clear.
|
CSCdy06091
|
Symptom: Combining is not working correctly for NTS traffic.
Conditions: Combining is set to 1 for NTS traffic, so one FastPacket exists only in one cell. However, this condition only works in one direction.
Workaround: The problem appears to be caused by a particular trunk in the network. Reroute the connection away from each trunk one at a time until to problem trunk is located, and the connection is routed away from it.
|
CSCdy51577
|
Symptom: The trunk parameters using the Job could not be modified.
Condition: When more than one virtual trunk exists on a physical interface, configuring the trunk parameters on any one of these virtual trunks fails in the Job mode.
Workaround: Configure the virtual trunk through CLI.
|
CSCin16665
|
Symptom: Software error 3041 is generated after BXM-OC12 card was pulled out and reinserted. Connection database was corrupted.
Conditions: Some DAX PVCs existed on the cards between lines 1 and 2.
Workaround: None.
|
|
|
|
|
|
|
|
|
CSCin17429
|
Symptom: Tx/Rx cell statistics parameters are disabled for channels terminating on AIS-OC3 interface.
Condition: None.
Workaround: None.
|
|
|
|
|
|
CSCin17623
|
Symptom: Configured preferred path gets reset to Not Configured.
Condition: This symptom occurs while changing trunk cost of a trunk.
Workaround: None.
|
|
|
|
|
|
CSCin17893
|
Symptoms: Software log observed on the node while graceful upgrade from 9.2.38 to 9.21.4J (errors: 52, 516, 1120, 518, 1125, 502, 589, 504, and 505).
Conditions: Graceful upgrade from 9.2.38 to 9.2.4J.
Workaround: None.
|
|
|
|
|
|
Resolved Anomalies in Release 9.2.42
Table 19 lists the resolved anomalies in this release.
Table 19 Resolved Anomalies in Release 9.2.42
Bug ID
|
Description
|
CSCdw80264
|
10 hop cons fail to route when resources available.
|
CSCdx55308
|
Slow rerouting time in mixed pre and post 9.3.30 network, bad sequence #.
|
CSCdx63511
|
Download Aborted logged and UXM to failed status when burnfwrev to AC27.
|
CSCdv23693
|
CBR traffic dropped when background test is executed.
|
CSCdw07452
|
31 voice channels are send to cwm for CVM T1 card.
|
CSCdw28930
|
External clock switch due to clock master node switchcc.
|
CSCdw63725
|
Connection requires 11 hops to route fail to report as failure & CPU idle low.
|
CSCdw75500
|
swerr 5050 generated upon cba_verify after deleting vp-tunneling daxcon.
|
CSCdx06654
|
line/trk recovered even the active APS line has LOS.
|
CSCdx08838
|
IGX reports PRI Loss (CLOCK) when deleting line clock source.
|
CSCdx10874
|
Enabling LMI on VSI feeder causes unreachable (always) + comm-fail(9340).
|
CSCdx17933
|
Dangling VLCONs and inconsistent trunk loading/conid.
|
|
|
|
|
|
|
|
|
CSCdx29500
|
BPX clock does not go to Tracking mode if current clock source is on port 1.
|
|
|
|
|
|
CSCdx29539
|
dsppwd presents security problems; uses clear text format.
|
|
|
|
|
|
CSCdx36217
|
connection continuously re-routes after active CC fails with swerr 47.
|
|
|
|
|
|
CSCdk37976
|
No alarm when active BCC-32 backcard removed.
|
|
|
|
|
|
|
CSCdk49036
|
Multiple errors with cnftrk during Job Addition.
|
|
|
|
|
|
CSCdm19518
|
Pref routes are not displayed correctly by cnfpref and dsprts.
|
|
|
|
|
|
|
|
CSCdm31682
|
cnfchvcq for ALM-A connections wont allow user to maximize 16000 cell buffer.
|
|
|
|
|
|
|
|
|
|
CSCdm36300
|
Bogus error message received when try to addcon with non-existing trunk number.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdr08809
|
dspstbyclk shows LOS on a good external clock source.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdr26161
|
Resetcd h of UXM during burnfwrev leaves card in burnfw state.
|
|
|
|
|
|
CSCdt22924
|
Lines configured as clock source goes to bad clock source after dncd/upcd.
|
|
|
|
|
|
|
|
CSCdt98231
|
swerr 9098 logged after reinsert back card for VSI part deletion.
|
|
|
|
|
|
CSCdv78268
|
Cnftrkparm on NTS Queue Depth Rejected with Unrelated Range Check.
|
|
|
|
|
|
|
CSCdw25128
|
HCS Correctable error (Stat 55) was not shown when errors were injected.
|
|
|
|
|
|
CSCdw40180
|
IGX minor topo conflict (dspds).
|
|
|
|
|
|
|
|
|
|
|
CSCdw58091
|
Cpu usage is... message is not logging after graceful upgrade and switchcc.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdw74266
|
cnfport allowed on UFMU secondary card.
|
|
|
|
|
|
|
|
|
|
CSCdw78620
|
Software error 75 logged on BPX.
|
|
|
|
|
|
CSCdw83716
|
UBUs mistakenly assigned to UFMU.
|
|
|
|
|
|
CSCdw84340
|
dsputl command does not work for UVM/CVM connections.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdw90487
|
SWLOG 1423 generated on executing dsprtcache (detailed) command.
|
CSCdw92030
|
Port speeds above 6144 Kbps on UFMU-HSSI are reported incorrectly to CWM.
|
|
|
|
|
|
CSCdw92576
|
line keeps going in and out of alarm.
|
CSCdw94435
|
dclk output doesn't get updated.
|
CSCdx02074
|
Be, Bc values are getting incorrectly set upon addcon.
|
CSCdx04153
|
Frame relay conns using wrong load type, with cnfcon.
|
CSCdx31537
|
dspcons shows invalid DSP Fl alarm on one end after communication break.
|
CSCdx49193
|
CWM local/remote IBS reversed fro FRM-FRSM8 ATFST connection.
|
CSCdx57483
|
Removed ASM card on a BPX cage displayed as Empty Reserved for BCC.
|
CSCdx83934
|
Asynch EIA lead (cmi_lead_mon) upgrade issues when upgrading to 9230 and 93x.
|
CSCdy01237
|
Default Gateway IP address changes automatically.
|
CSCdy03630
|
wrongly sends objects in bps format when tstber is executed.
|
CSCdy13533
|
Some BPX nodes in network don't sync up with CWM.
|
Anomalies in Release 9.2.41
This section lists the known and resolved anomalies and the anomaly status changes in Release 9.2.41.
Known Anomalies in Release 9.2.41
Table 20 lists the known anomalies in SWSW Release 9.2.41.
Table 20 Known Anomalies in Release 9.2.41
Bug ID
|
Description
|
CSCdk22430
|
Status Change: Closed
Symptom: Checksum word 15 of backplane nvram is not recalculated when words 0-14 are updated using cnfbpnv.
Conditions: This bug was observed with BPX 9.1.01.
Workaround: No workaround is available at this time.
|
CSCdk91790
|
Symptom: SWSW system idle time is below 30% when more than 10 UVMs are activated.
Conditions: SWSW polls each activated UVM for modem status every 1 second for each port. SWSW also spends time processing the responses of the modem polling.
When many UVMs are activated, the modem polling handling consumes a lot of system time and resources (buffer queue), which affect system performance.
UVM FW has supported asynchronous event to report modem event. SWSW needs to stop polling modem status if the FW in UVM supports the asynchronous event.
Workaround: Use cnfnodeparm 46 to increase polling timer to improve system performance.
Further Problem Description: None.
|
CSCdm22426
|
Status Change: Closed
Symptom: While using jobs to down or up the connection based on a jobtrigger, the job fails if dspbob is executed while the control signal toggles.
Conditions: This issue was observed with IGX 8.2.56.
Workaround: Retrigger the job after executing the dspbob command.
|
CSCdp98648
|
Symptom: Equipment Manager cannot tell the different between BXM legacy or enhanced version.
Workaround: Log into the BPX node, and execute dspcd XX to determine the number of channel support. The enhanced version of the BXM card has 61K channels, and the BXM card has less than 61K channels.
|
CSCdr05291
|
Symptom: Problems deleting feeder trunks via SNMP or CiscoView
Conditions: switchIfService still must be specified to delete feeder trunks but not routing trunks.
Workaround: Use the CLI commands to delete feeder trunks.
|
CSCdr26161
|
Symptom: burnfwrev on a UXM card says "Already burning firmware. Try again later" for a long period of time (more than 10 minutes) if the UXM card is reset during the burnfw process (after the download is complete and after the Burn Addresses stop updating).
lasalle VT StrataCom IGX 8420 9.2.3j June 12 2000
11:32 GMT
Firmware Size Status UXM-A.B.08 1196 K Burning
into slot 10 (59 lives)
File Address Length CRC Burn Address 10
BFCB0000 10000 4991784B BFCC0000 11
BFCC0000 10000 FF48BE27 BFCD0000 12
BFCD0000 10000 109BDBAA BFCE0000 13
BFCE0000 10000 4C9E590D BFCF0000 14
BFCF0000 10000 ABD1A902 BFD00000 15
BFD00000 10000 A2EB42FB BFD10000 16
BFD10000 10000 F541AA3E BFD20000 17
BFD20000 10000 6DA680B5 BFD30000 18
BFD30000 AC35 CB571C12 BFD3AC35
Last Command:burnfwrev A.B.08 10 c
Already burning firmware. Try again later Next Command:
Conditions: Reset must be done after all burn addresses are updated.
Workaround: Do not reset the card during burnfw process.
|
CSCdr45021
|
Symptom: SCT 1 is the default SCT reserved for MPLS. When an SES trunk is provisioned and if the default SCT is not changed to SCT 3, the trunk will fail to come up.
Conditions: None.
Workaround: Ensure that SES uplink uses SCT 3 as service template class by changing the default SCT used before provisioning the trunk.
|
CSCds47671
|
Symptom: dspcurclk displays incorrect trunk numbers in the clock path.
eg. z5b 7--30z2a 24-- 9.1z3b
This should be 24.1 (the port is missing)
Conditions: You need the following clock path in dspcurclk for this problem to surface
destination IGX slot ------ slot via node slot.port ----- source node (IGX/IPX)
Workaround: None. This is a display issue only.
Further Details: The display attempts to display the port on the via trunk before it is properly set.
|
CSCdt07203
|
Symptom: The hitless rebuild log filled up due to repeated failed switchccs.
Conditions: A bad standby BCC is required. The node must be running at least 9.2.
Workaround: Clear the hitless log with the command dsphitless c. Or, switchcc less often, so the hitless rebuild log entries have a chance to age out of the log.
|
CSCdt22924
|
Symptom: Bad clock source during dn/upcd.
Condition: dncd/upcd causes the clock failure "Minor bad clock source".
Workaround: clrclkalm will clear the clock failure.
|
CSCdt43014
|
Symptom: SWLOG error 557 on BPX node occurs when deleting connections.
Conditions: BPX 9.3.11 MGX:1.1.32.
Workaround: None.
|
CSCdt55864
|
Symptom: The Cisco WAN Manager's Statistics Collection Manager cannot parse the TFTP statistics file received from the IGX node.
Conditions: This problem only occurs when the IGX node has FastPad connection enabled, and is collecting TFTP statistics on those connections.
Customer Impact: When this problem occurs the customer is not able to collect TFTP interval statistics from the IGX node.
Workaround: There is no work around for collecting the FastPad connection statistics. However, if you disable statistics collection on the FastPad connections, you can collect all of the other statistics.
Further Problem Description: When writing the variable key length for the various FastPad connection types, an extra byte is added. This byte throws off CWM parsing. The parser has no way of recovering. Therefore, the entire statistics file is discarded as corrupted or bad.
|
CSCdt66696
|
Symptoms: BTM-E3 backcard is displayed as AIT-E3 in CLI.
Conditions: BTM-E3 backcard is displayed as AIT-E3 in CLI.
Workaround: None. Ignore the display.
|
CSCdu15686
|
Symptom: Internal port diagnostics fails for V35/X21 ports. use "tstport" command.
After the above test, card goes to "Active-F" state as seen in "dspcds".
Conditions: The above problem is seen only when port is configured as DCE and not seen with DTE ports.
This condition was tested with UFMU F/W version YAM and YAN, and the same problem occured.
Workaround: None. The loopback test can only be initiated from a DTE port.
|
CSCdu16679
|
Symptom: Virtual trunk does not process traps received from ATM cloud, for example, when the associated cloud VPC goes down.
Conditions:
1. ILMI protocol for the virtual trunk is running on the BCC (BNI virtual trunk).
AND
The cloud port is NOT a BPX/IGX OR BPX/IGX with ILMI running on the BXM/UXM.
OR
2. ILMI protocol for the virtual trunk is running on the BXM or UXM.
AND
ILMI on the cloud port is running on the BCC/NPM of a BPX/IGX.
Workaround:
If ILMI is running on the BCC at the virtual trunk end (BNI virtual trunk), use the following workarounds:
•If the ATM cloud is a BPX/IGX, make the protocol run on the BCC/NPM.
•If the ATM cloud is not a BPX/IGX, there is no workaround. However, the ILMI implementation on virtual trunk will find the VPC status using GET_REQUEST.
For BXM virtual trunks and for UXM virtual trunks with protocol on the card, use the following workarounds:
•If the ATM cloud is a BPX/IGX, make the protocol to run on the card.
•If the ATM cloud is not a BPX/IGX, there should be no problem. The trap is recognized and processed.
|
CSCdu45358
|
Symptom: The switchover occured on BPX node when the active card was pulled out. The empty slot for this card was shown in the CLI, but the Network Browser was showing that the active card was still present.
Conditions: None.
Workaround: None.
|
CSCdu61769
|
Symptom: HDM connection bouncing since 9.2.38 SWSW Release. Lead RxD (pin 3) is bounced from Idle state to active state with high frequency (once or twice every second).
Conditions: This symptom happens when the connection rate is below 64K.
Workaround: Upgrade connection to 64K.
Further Problem Description: None.
|
CSCdu64553
|
Symptom: CLP 1 tagged traffic in a multi-vc environment cannot be differentiated from CLP 0 with the present default drop method on TAGCOS Qbins, EPD.
Conditions: EPD is the configured default. To differentiate CLP 1 marked traffic, CLP hysteresis instead should be configured.
Workaround: No workaround.
Further Problem Description: None.
|
CSCdp48861
|
Symptom: The customer may notice slow UI response or a difficulty logging into the node using the normal VT session. The dspprfhist command shows high RT usage in the TRNS process. The statistics shows high RT usage by state machine 55 (0x33).
Conditions: This is due to statistics updates for voice connections. It may be seen on nodes with a high number of voice cards and voice connections (IGX with CVMs and/or UVMs).
Workaround: The command off1 17 can be performed. Issuing this command stops the collection of voice connection statistics (for all connections, not just voice), as well as the operation of the debug command dspchstats.
If you must collect statistics, limit the number of statistics. Frame Relay statistics are collected at 5-minute intervals (configurable up to 15 minutes). Most voice statistics are reported at 1-minute intervals. However, the following statistics are reported at 3-second intervals:
•Seconds V.25 Modem On
•Seconds DSI Enabled
•Seconds Off-Hook
•Seconds In Service
|
|
|
|
|
|
|
|
|
CSCdr35223
|
Symptom: In 9.2.3z the aps dsptrks shows a communication failure when it has LOS.
Conditions: When active APS line is in LOS, do a switchapsln with option 4 to switch from protection line to working line. This switch will cause the trunk to fail. In 9.2.3z this condition shows that the trunk fails due to a communication failure.
Workaround: None.
|
|
|
|
|
|
CSCdr98080
|
Symptom: Software log 3052, 3017, and 362 were observed on a BPX node during switchcc.
Conditions: The above software log may occur on a BPX node during switchcc or node rebuild. The cause is still under investigation. The occurrence of this problem is rare.
Workaround: None.
|
|
|
|
|
|
CSCds16693
|
Symptom: Software log 1012 occurred on BPX when deleting a bundle of connections.
Conditions: The above software log may occur on an BPX node. The cause is still under investigation.
Workaround: None.
|
|
|
|
|
|
CSCds19443
|
Symptom: Software log 3017 occurred on a BPX node BXM feeder trunk.
Conditions: The above software log may occur on a BPX node. The cause is still under investigation.
Workaround: None.
|
|
|
|
|
|
|
CSCds57315
|
Symptom: Communication break observed between IGX feeder and IGX routing node following addshelf.
Conditions: Observed with IGX 9.2.23 and UXM FW CA19.
Workaround: No workaround available at this time.
|
|
|
|
|
|
CSCds68083
|
Symptom: After BCC rebuilt, PVCs are not programmed in standby BXM for Y-red and APS 1+1.
Conditions: This symptom occurs with SWSW 9.2.32.
Workaround: Reset standby BXM after BCC is rebuilt will reprogram all PVCs in the standby BXM.
Further Problem Description: After BCC is rebuilt, tstconseg will log swerr 9082.
|
|
|
|
|
|
|
|
CSCds81526
|
Status Change: Closed
Symptom:
1. The BPX and IGX nodes were loaded to their connections limit.
2. The dncon COS 0 i was issued on bpx03.
3. It took more that 2.5 hours to down about 70% of 16K connections (performance issue).
4. When the connections were downed, the master side and the slave side of the connections were showing down state which is correct.
5. Then, the upcon COS 0 command was issued to up all downed connections. The command was issued on a BPX node.
6. After CPU idle time reached 70%+ (steady-state) network wide, the master side of any connection is upped correctly (OK state). However, the slave side of the connection is still in down state (it should be in up state as well).
7. The problem is the upcon network messages were not propagated to the slave-side of the connection. The result is in spite of issuing upcon the master-side of the connection is upped, but the slave-side of the connection is still in down state.
8. This condition means upcon finite state machines could be timing out, or handling of such an inconsistent state under heavy loading still needs to be accounted for.
Conditions:
1. Almost all 9.2.34 + 9.2.23 SWSW and SWFW features were provisioned.
2. The nodes were loaded to their limit with maximum terminating connections, VTs, and so forth.
3. Topology is of a tiered network with MGX 8220 and IGX feeders, MPLS LSCs and LERs, and SES PNNI controllers.
Frequency: Intermittent.
Steps to re-create the problem: It is unclear whether or not it is reproducible.
Workaround: Issue the upcon command for each connection one by one, which is not efficient.
|
|
|
|
|
|
|
|
|
|
CSCds81894
|
Problem:
1. When SWSW 9.3.1j is downloaded to bpx02 by doing a loadrev, download to the active card's ROM is successful.
2. Then, SWSW is copied to the RAM of the standby card. The problem is when the download is in progress as seen by using "dspdnld" command. The download process will terminate and restart downloading SWSW into the RAM after about 12 to 13 blocks have been downloaded.
3. This problem has been observed many times
Symptom:
1. During the standby cards RAM being updated to the 12th or sometimes to the 13th block, the download process terminates and restarts.
2. This process can go into a loop for a long time
Setup:
1. Almost all 9.2.34+9.2.23 SWSW and SWFW features were provisioned.
2. The nodes were loaded to their limit with max terminating conns, VTs, and so forth.
3. Topology is of a tiered network with MGX 8220 and IGX feeders, MPLS LSCs and LERs, and SES PNNI controllers.
Conditions: Most of the configurable elements such as number of connections, number of trunks, and so forth were loaded to the switch limit.
Frequency: Reproducible.
Steps to recreate the problem: Do a loadrev in upgrades network node bpx02.
Workaround: Awaiting DE to be assigned to resolve the problem.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdv33753
|
Symptom: On BPX nodes the following observations were made after a fall back from 9.3.30 to 9.2.34:
•BPX node logged SWSW error 9000: APS 1+1 trk was in LOS, BXM card was in mismatch.
•BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
Conditions:
1. Network was being prepared for SWSW upgrade from 9.2.34 to 9.3.30 with UXM FW A.C.E, BXM FW M.F.25 at the time.
2. A script was run on all nodes to set parameters for upgrades, check databases, and do network captures.
3. SWSW 9.3.30 was loaded on the standby CC of all nodes (routing and feeder) using loadrev.
4. A runrev 9.3.30 was executed on each (node by node) at 10-15 minute intervals apart.
5. After all nodes (routing and feeder) were upgraded to SWSW 9.3.30, no events were taking place for 30 minutes.
6. A script was run to set the parameters after a node upgrade (for example, turning on statistics).
7. BXM FW M.F.25 was loaded on all nodes and burned on all BXM cards without any problems.
8. UXM FW A.C.01 was loaded on all nodes and burned on all UXM cards at the same time, which yielded no problems.
9. Network was allowed to settle for a long time due to rerouting until zero errors were in network and traffic resumed.
10. At this point the upgrade was successful.
11. A fall back to 9.2.34 was conducted on the entire network using the command: runrev 9.2.34 *. This command unlocked the standby CC and rebuilt the databases using the 9.2.34 BRAM.
12. After the network fallback, the network was allowed to settle over night.
13. After the fallback the network was running SWSW 9.2.34, UXM FW A.C.01, and BXM FW M.F.N.
14. While checking the network health in the morning, a number of problems were observed.
15. Symptoms on BPX nodes were narrowed to observation bpx01 and bpx05:
a. BPX node logged SWSW error 9000: APS 1+1 trunk was in LOS, BXM card was in mismatch.
b. BPX node logged SWSW error 9000: BXM card mismatch, VT failure.
|
CSCdv33753 (continued)
|
16. After DE investigation, the trigger of problems on all BPX nodes was attributed to SWSW error 9000 exception. This exception was caused by the CBUS message 0x60 (delete connections) to the BXM card. In the message, the start and end LCNs are specified to delete a range of connections. However, that start LCN is greater than the end LCN which is incorrect. Therefore, the BXM card sends an error to the BCC and logs the SWSW error 9000.
17. After a resetcd on the mismatched BXMs, the BXMs would recover.
Workaround: None.
|
CSCdv50311
|
Symptom: With 1E-3 errors injected on a BXM T3 trunk, connections do not re-route.
Conditions: The bit errors are randomly injected throughout the entire bit stream at a rate of 1e-3.
Workaround: None.
|
|
|
|
|
|
CSCdv91546
|
Symptom: Tstdelay failed in many connections on BPX with nrt-vbr type. tstdelay 3.1.1.100 Test delay timed out Next Command.
Conditions: BPX SWSW 9.2.32.
Workaround: None.
Further Problem Description: Built a new connection with the same path and tstdelay passed.
|
|
|
|
|
|
|
|
CSCdw07452
|
Symptom: 31 entries are there for T1 CVM card on IGX Node.
Conditions: In CM GUI equipment selector.
Workaround: Do not make connections on line > 24.
|
|
|
|
|
|
CSCdw18589
|
Symptom: In 9.2.34 when the physical interface for a virtual trunk is used as a network clock source, the source associates itself with the first virtual trunk on the interface. Should that trunk fail, the clock source fails and the system will search for a new source.
In this configuration, you are not allowed to set PASS SYNC to YES on the first virtual trunk (which is correct). However, you can set the virtual trunk for PASS SYNC YES. By setting PASS SYNC to yes on any other virtual trunk on the interface, the PASS SYNC is set to YES on all of the virtual trunks - even the first one which is associated with the clock source. Having a trunk as a clock source and setting it to PASS SYNC YES is an unsupported configuration.
In 9.3.30 the situation is slightly different in that a change made to any of the virtual trunks does not affect the first virtual trunk, which has the clock association. The problem is that if the first virtual trunk fails, the clock source associates itself with the second virtual trunk. If PASS SYNC were set to YES on that trunk, problems would result.
Conditions: Enabling PASS SYNC to YES on any virtual trunk (other than the first one) causes PASS SYNC to be set to YES on all virtual trunks associated with the interface - even the one tied to the clock source.
Workaround: If the physical interface for a virtual trunk is used as a clock source, do not set PASS SYNC to YES on any of the virtual trunks associated with the interface.
|
|
|
|
|
|
|
CSCdw28930
|
Symptom: When the highest number node switched BCC (the clock master node), the other nodes with external clock source switch its clock source.
Conditions: The highest number node (clock master) switch its BCC.
Workaround: None.
|
|
|
|
|
|
CSCdw51777
|
Symptom: When routing CGW connections over UXME trunk, discards are observed on Frame Relay endpoints. An FRM to BXM connection discards on the FRM at egress. An FRM to UFM connection shows discards on both the FRM and UFM at egress. FRM to FRM connections used so far have not shown any discards.
Topology of shortest hop connection is
8.9.100 NODE A 19.1----5.1 NODE B 6.1----11.9 NODE C 13.2.198.288 FRM-31-------UXME----UXME-------UXME---BXM---------BXM
Observations are connection when routed over this path shows discards on egress of FRM at NODEA none at NODE C. Trkstats on NODE C 11.9 clean Trkstats on NODE B 5.1 clean Trkstats on NODE B 6.1 clean Trkstats on NODE A 19.1 CGW Abrt Frms & Bad CRC32 Rx from Line. Channel statistics on UXM trunk show no discards FRM shows large number of discards.
Trunk 19.1----5.1 bert tested error free and is over straight cable between two co-located nodes. Cable and UXME cards (front and back) have already been replaced. Switchcc performed on NODE A & B Trunk has been deleted/added without result.
If connection rerouted so that it takes a different path between NODE A and NODE B but still passes over the other trunks then the discards stop.
Conditions: SWSW on both the IGX and BPX's is 9.2.38 FRM-31 are Running Model K rev B UXM-E's are Running Model B rev J BXM's are running Model F rev C.
Workaround: Only workaround is to reroute the connections off this trunk.
|
|
|
|
|
|
|
|
|
|
|
CSCdw58091
|
Symptom: Cpu usage is... message is not logging after graceful upgrade and switchcc.
Conditions: switchcc and graceful upgrade triggers the problem.
i8430-2a TN StrataCom IGX 8430 9.2.40 Jan. 8 2002
08:28 EST
Active 0 500780000 -20 500760000 -40 500
Snapshot Current
Proc RT HSds LSds RT HSds LSds RT HSds LSds
IDLE 85 14 0 85 8 0 85 4 0
RSRC 1 60 0 1 55 0 1 55 0
CBUS 0 420 0 0 422 0 0 416 0
NETW 0 17 0 0 15 0 0 13 0
TRNS 3 144 0 3 138 0 3 125 0
FAIL 2 0 0 2 0 0 2 0 0
SNMP 0 0 0 0 0 0 0 1 0
PROT 0 0 0 0 0 0 0 0 0
TXIO 0 0 0 0 0 0 0 0 0
ILMI 0 0 0 0 0 0 0 0 0
SUMM 4 1 0 3 1 0 3 1 0
The "dspprfhist" command will show the idle time for the switch. One tick is about equal to 1 second. You can use the "f" and "b" keys to move (f)orward or (b)ackward in the history.
i8430-2a TN StrataCom IGX 8430 9.2.40 Jan. 8 2002
08:30 EST
Smpl 0 1 2 3 4 5 6 7 8 9
10 11 Tick 0 -20 -40 -60 -80 -100 -120 -140 -160
-180 -200 -220
IDLE 85.3 85.1 85.1 84.6 85.1 85.5 85.4 85.3 85.3 85.3
84.9 84.9 RSRC 1.3 1.3 1.3 1.4 1.3 1.3 1.2 1.3
1.3 1.2 1.3 1.4 CBUS 0.8 0.9 0.9 0.9 0.8 0.8 0.9
0.8 0.8 0.8 0.8 0.9 NETW 0.1 0.2 0.2 0.2 0.2 0.2
0.1 0.2 0.2 0.1 0.2 0.1 TRNS 4.0 4.0 3.9 4.0 3.9
3.9 3.9 3.9 3.9 3.9 3.9 4.0 FAIL 2.9 3.0 2.9 2.9
2.9 2.8 3.0 2.8 2.8 2.9 2.9 3.0 SNMP 0.8 0.7 0.8
0.8 0.7 0.9 0.7 0.9 0.8 0.8 0.8 0.7 PROT 0.6 0.5
0.7 0.6 0.6 0.6 0.6 0.7 0.7 0.6 0.8 0.6 TXIO 0.4
0.3 0.4 0.3 0.3 0.3 0.3 0.2 0.2 0.2 0.3 0.2 ILMI
0.0 0.0 0.1 0.1 0.1 0.0 0.0 0.1 0.0 0.1 0.1 0.0
SUMM 3.7 4.0 3.8 4.3 4.0 3.6 3.9 4.0 4.0 4.2
4.2 4.2
Last Command:dspprfhist
Workaround:
1. Rebuild the node by resetting the active card.
2. Send an event TO2 to self test state machine by using following command:
sthevt 53 242
Further Problem Description: There should also be a message logged when the CPU util drops below 50%. This is also not logged.
Pay close attention to the difference between IDLE time and CPU usage. CPU usage = 100 - IDLE time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdw68758
|
Symptom: SNMP channel counter statistics are not being updated.
Conditions: This problem occurs when SNMP channel counter statistics are collected, but interval statistics are not enabled.
Workaround: Enable at least 1 interval statistics on each connection.
Further Problem Description: The code will not cause a channel statistics poll to be generated unless:
1. At least1 interval statistics exist.
OR
2. The card supports AIS polling.
OR
3. The command [dspchstats] is invoked on the connection.
Poll for summary and SNMP channel statistics irrespective of whether interval statistics are enabled.
However, an old issue existed when the BPX increased to 4k connections where the summary statistics functionality reduced from all connections to only a subset of connections because of memory limitations. This problem has to be investigated to see if it is relevant to this issue.
|
|
|
|
|
|
|
|
|
|
CSCdw76695
|
Symptom: Software error 327 appears on multiple nodes after upgrade. Due to BTM trunks not supporting CGW connections.
Conditions: Large IGX/BPX network. Only happens on upgrade.
Workaround: Delete and re-add trunks.
|
|
|
|
|
|
CSCdw83475
|
Symptom: tstdelay is inconsistent when run from IGX on a connection between IGX and the MGX 8250 feeder. It is longer and varies anywhere between 10 - 40ms. tstdelay at the MGX is consistent and much lower:~4ms.
Conditions: Can be environment with minimal traffic. Reproduced in lab with 9.3.35 and 1.1.41.
Workaround: No known workaround.
|
|
|
|
|
|
CSCdw83716
|
Symptom: When adding the first connection to a UFMU port, the error message "Insufficient TDM bandwidth available" is properly displayed when there isn't enough UBUs available. However, the IGX will allocate all available UBUs, even when there are not enough, when attempting to add the connection. The IGX will not de-allocate them upon failure of the connection to add.
Conditions: This symptom only happens when the amount of UBUs available are less the number of UBUs required. Under this circumstance, this condition is always present.
Workaround:
Prior to Release 9.1:
1. Remove all connections from the port in question - delcon.
2. Reconfigure that port's "Configured Clock" to a very small number (e.g. 1024) - cnfport.
3. Add a connection from that port to another existing port - addcon d. delete that connection from step "c" - delcon.
Releases 9.1 and up:
1. If there are existing ports/connections on the card in question, follow "Pre 9.1" procedure.
2. If it is the only port on that card. a. remove all connections from the port in question - delcon b. remove the UBUs assigned to that card - setlogubus <cd #> 0
Further Problem Description:
Background: The IGX will assign the UBUs based on the "Configured Clock" of the port ONLY when the first connection is added. Inversely, the UBUs will ONLY be de-allocated when the last connection of the port is deleted.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdw83716 (continued)
|
You might have this problem when 100% of the UBUs (or bus bandwidth) are allocated. This problem can be checked two different ways:
1. Use the command "dspbuses" and look for "(100%)" Allocated:
----------------------------------------------------------------------
i8430-1a TN Cisco IGX 8430 9.3.35 Feb. 26 2002
18:36 GMT
Bus Info
Bus Bandwidth usage in Fastpackets/second (Snapshot)
Allocated = 1168000 (100%) <-----HERE**************************
Available = 0 ( 0%)
Bus A:Active - OK Bus B:Standby - OK
Last Command:dspbuses
--------------------------------------------------------------------------------
or
2. Use the command dspubus s (9.1 and up) to see if 0 UBUs are
available:(There is no equivalent command for pre 9.1.)
----------------------------------------------------------------------
i8430-1a TN Cisco IGX 8430 9.3.35 Feb. 26 2002
18:38 GMT
UBU Usage Summary Snapshot
1 2 3 4 5 6 7 Page
1234567890123456789012345678901234567890123456789012345678901234567890123 1
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 2
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 3
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 4
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 5
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 6
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 7
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx 8
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Total numbers of allocated UBUs = 584 Total numbers of available UBUs = 0
<-----HERE**************************
Last Command: dspubus s --------------------------------------------------------------------------------
Also, if your UFMU is in standby (dspcds) and you see that UBUs are assigned to that card, you may have hit this bug.
Use the command "dspubus <card #>" (9.1 and up) to verify:
--------------------------------------------------------------------------------
i8430-1a TN Cisco IGX 8430 9.3.35 Feb. 26 2002 18:42 GMT
UBU Data Base for logical UFMU card in slot 17 - 48 UBUs allocated ^^ ^^ ^^
************** This will not be 0 ----------/\
1 2 3 4 5 6 7 Page
1234567890123456789012345678901234567890123456789012345678901234567890123 1
.......................................x....x....x....................... 2
.x....x...........x....x.........x...................x....x.............. 3
..........x....x...........x....x.........x..............x....x....x..... 4
.........x..............x................x....x.........x................ 5
........x........................x....x....x...........x................. 6
.......x....x.........x....x.........x.........x................x........ 7
................x....x.........x....x.........x....x....x................ 8
...............x....x.........x....x....x........................x.......
Last Command:dspubus 17
--------------------------------------------------------------------------------
In Pre 9.1, the only command is "dspbuses", and you will have to scroll through all the pages looking for your card and card number.
|
CSCdw92576
|
Symptom: Line keeps going in and out of alarm.
Conditions: This symptom occurs after changing the line framing from ESF to D4.
Workaround: None.
|
|
|
|
|
|
Resolved Anomalies in Release 9.2.41
Table 21 lists the resolved anomalies in Release 9.2.41.
Table 21 Resolved Anomalies in Release 9.2.41
Bug ID
|
Description
|
CSCdk80460
|
cnflnsigparm is used to change signalling parameters for entire node. These changes are not being reflected in the line 2 of a UVM.
|
|
|
|
|
|
|
CSCdm12850
|
Implementation of the idle time has a defect. Idle time can be under-reported or cpu consumption over reported.
|
CSCdp04164
|
When IGX DC voltage is greater that 56V, an alarm is generated and fills the event log.
|
CSCdr34820
|
Under certain conditions more than one connection appears to be on the same DSP.
|
CSCdr64816
|
The voiceEndptTable returns offHook for all channels. This symptom is seen even if the correct status is displayed in the 'dspconst' command on the switch.
|
CSCdr76559
|
If LMI gets removed from a port and then re-added, any connection status changes that happen while the port had no LMI will not get sent when LMI is reestablished.
|
CSCds03159
|
BCC-4 logs multiple 1011 aborts when it is removed.
|
CSCds37220
|
When a trunk with APS is looped or is experiencing SF or SD alarms is present and a switchcc occurs, the status of the standby APS line becomes "APS Deactivated". This symptom is just a display issue. Traffic is unaffected.
|
CSCdt96187
|
VSI/AR Connections fail on a BPX after switchyred.
|
CSCdu34126
|
Line cable length gives five options when configuring a trunk or line on a UXM T3/E3 card. However only three different values are actually displayed.
|
|
|
|
|
|
CSCdu36770
|
9.2.00—May experience route failure.
9.3.30
1. Only 7 routes running concurrently. The CLI command [dsprrst] is showing extremely large values for the fields:
Max Secs To Perform Route Avg Secs To Perform Route, and Avg Secs To Route a Conn.
The CLI command [dsprrst t] is showing an extremely large value for the field:"E"
2. The 8th route allocates a master route. This is a relatively rare as it is hard for a node to reach real 8 routing concurrency. The routing timer system will pause a while or for a very long time.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdu40956
|
cbrt command displays obsolete options "a" and "l".
|
|
|
|
|
|
CSCdu42714
|
Feeder trunks are not blocked for atmPortStatTable, atmPortTable, and atmPortQueueTable. This problem only exists in BPX.
For atmPortStatTable, the problem exists with the GET operation.
For atmPortTable, the problem exists with both the SET and GET operations.
For the atmPortQueueTable, the problem exists with SET, GET, and WALK operations.
|
|
|
|
|
|
|
|
|
|
|
CSCdu43858
|
In a BCC-4, if a hitless rebuild is performed, the prompt indicates that the card is BCC-3 instead of a BCC-4.
|
|
|
|
|
|
CSCdu46642
|
UXM E1/T1 IMA trunks do not have the correct allocation of DS0s after a trunk reconfiguration.
|
|
|
|
|
|
|
CSCdu50924
|
Random failure of cons all over the network. No trunk or line failures reported. It took approximately 15 minutes to reroute.
|
|
|
|
|
|
CSCdu53235
|
Software error 2051 was logged, but not every file collection. The separation of the swerrs may be days or weeks. There may not be any statistics activity at the time the files were logged (no statistics enabled or disabled, and no objects (connections, lines, trunks, ports, or physical lines) added or deleted.
|
|
|
|
|
|
|
|
|
CSCdu53606
|
The CLI dspload cannot display loads for particular IMA trunk configuration.
|
|
|
|
|
|
CSCdu54291
|
The CLI dsptrks shows a feeder trunk is Clear and also displays the Other End info even though that feeder trunk has been deleted on BPX side.
|
|
|
|
|
|
|
|
|
CSCdu55421
|
Software error 1415 is logged when the CLI command [cnfpref] is invoked in a Cost-Based Routing network.
|
|
|
|
|
|
|
CSCdu55802
|
If we do a rebuild on a BPX node with firmware image present in its PCC space, after rebuild dspfwrev shows "Configuration image present". This is incorrect. 'dspcnf' screen shows correct message "Reserved for firmware image"
|
|
|
|
|
|
CSCdu55966
|
Every 10 seconds a software error 111 or 190 is logged.
|
|
|
|
|
|
|
|
|
CSCdu57647
|
When the system fails to find the lowest cost path, it reverts back to hop based routing to find a path that meets the cost. The following is the impact:
|
|
|
|
|
|
|
|
|
CSCdu58349
|
After an IGX/BPX boots up and a snmpwalk is issued from an SV+, the sysUpTime shows 497 days. After about 30 minutes this restarts from ZERO.
|
|
|
|
|
|
|
|
|
CSCdu59784
|
Route Cost field is not displayed properly in the dspcon screen due to line overflow.
|
|
|
|
|
|
CSCdu75709
|
Port data base, for serial cards, is not getting cleared in the Informix database after card removal and downing last port.
|
|
|
|
|
|
CSCdu84891
|
The symptoms are different between 9.3.30 and earlier releases.
|
|
|
|
|
|
|
|
|
CSCdu85897
|
swerr 136 is logged on IGX feeder node. This is not service impacting.
|
|
|
|
|
CSCdu88501
|
Software Error 925 logged and filled up the log entries when switchcc. The slot has a UVM Card.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
CSCdv03346
|
This is a interface problem.
|
|
|
|
|
CSCdv03399
|
When CLI changes the cell routing option of a ATM connection, the changes is not sent to the CWM. - CWM does not reflect the new changes.
|
|
|
|
|
|
CSCdv03428
|
An snmpwalk on the following objects gives wrong values: sonetIfType slotFrontQueue slotFrontLnFormat slotFrontChCount slotBackLnFormat slotBackSonetMode slotCardTrunkPorts
|
|
|
|
|
|
CSCdv04095
|
Software error 26 is observed when a mib walk is done on the BPX node when a card is down.
|
|
|
|
|
|
CSCdv07491
|
The cnfqbin (BPX only) and cnfsnmp (BPX & IGX) commands are available at a Level 6 User ID and should not be available to a user with that low level of authorization.
|
|
|
|
|
|
CSCdv08233
|
User is unable to access LAN gateway node without using hipri login. The node may experience resource aborts (3000000, 1000, or 52). The dspprf displays show very high real-time utilization in the NETW and PNAD processes, and memory accumulation in the PROT processes.
|
|
|
|
|
|
CSCdv08861
|
Software error 9000's flooding the software error log.
|
|
|
|
|
|
CSCdv10468
|
lm3 abort, Card errs, SW errs 1000 after "addcon".
|
|
|
|
|
|
CSCdv12786
|
Total reserved VSI bw on a BXM card can exceed the backplane speed.
|
|
|
|
|
|
|
CSCdv13914
|
The dspconcnf command shows "EDP" instead of "EPD" for the EPD threshold.
|
|
|
|
|
|
CSCdv16069
|
Line functions listed below accept feeder trunks as input causing error or aborts while they should be rejecting and displaying an appropriate error message. Symptoms although a little different are present in both 9.3 and 9.2 releases.
|
|
|
|
|
|
|
|
|
|
|
CSCdv18027
|
Login stalls for 30 seconds or more.
|
|
|
|
|
|
|
|
CSCdv24220
|
ddcuse command does not display anything.
|
|
|
|
|
|
CSCdv26618
|
User has HDM-HDM connections in a 9.2.36 network. On the preferred route, IGX-BPX-BPX-IGX, the connections are fine. On an alternate route, IGX-IGX- BPX-IGX, the connections lose sync. No errors are seen on the IGX or BPX nodes.
|
|
|
|
|
|
|
|
|
|
CSCdv27309
|
When a user adds a preferred path to a connection that has an active reroute timer, the connection is not selected for routing until the timer expires. The user may think it is a bug if the timer is set to 15 minutes.
|
|
|
|
|
|
|
|
CSCdv30106
|
TX Clp x DSCD stats display is missing from the dspchstats screen.
|
|
|
|
|
|
CSCdv31936
|
VP-Tunneling connection addition fails with the message, "Local channel unavailable".
|
|
|
|
|
|
CSCdv34258
|
IGX card attributes added after 9.2.35 may not be correctly initialized on the standby NPM when upgrading from a release pre 9.2.35 to a later 9.2 release or 9.3. These attributes are:- VSI Signal QBIN card attributes - CRC-4 configuration card attribute - LCN Resync card attribute.
Abort 1000003 on the standby NPM.
|
|
|
|
|
|
CSCdv34568
|
The switch does not send a port robust message with the updated port speed when the cell framing is changed to HEC mode on a BXM-T3 card.
|
|
|
|
|
|
|
|
CSCdv35146
|
2 minute data hit occured after issuing a switchyred on a BXM.
|
|
|
|
|
|
|
|
|
|
CSCdv35295
|
When on the switch CLI, a port in UFM card on IGX is shown as Failed, on CWM CiscoView, the port shows as Active and its color is Green.
|
|
|
|
|
|
CSCdv36176
|
Service impacting commands are allowed to be run on the standby controller card. There is no indication via VT that we are logged on to the standby CC.
|
|
|
|
|
|
|
|
CSCdv37628
|
The following events are logged during a switchcc. 1.Polling type changed to 2 2.Polling type changed to 1.
|
|
|
|
|
|
CSCdv42399
|
Unable to add an APS line of a trunk back after deleting it.
|
|
|
|
|
|
CSCdv43983
|
If the switchyred command is configured in a job (addjob) for a pair of BXM cards and there is an active VSI partition on the BXM, the switchyred will not take place when the job executes.
|
|
|
|
|
|
CSCdv45621
|
The headings for the [dsprf] command indicate "active" even when the command is invoked from the standby controller.
|
|
|
|
|
|
CSCdv55045
|
When the standby BCC is not available, the CBUS test display in dspselftst shows "Not Run" as it should. However, the Time shows a negative number and the "No Run" stat is not incremented.
|
|
|
|
|
|
|
|
CSCdv57337
|
The node aborts with software error 1000003 when running the cnfport command in syntax mode (addjob/editjob) and the command is waiting for the user to enter the card type.
|
|
|
|
|
|
|
|
|
|
|
|
CSCdv58954
|
dsplogcd displays port status as ACTIVE but on dspports or dspport, the port status is FAILED.
|
|
|
|
|
|
CSCdv63422
|
Addcon does create a connection when an ATM class of service with UBR parameters is specified.
|
|
|
|
|
|
CSCdv65620
|
With a E1 trunk added between IGXs using BTM cards, it is not possible to use the command cnftrk to modify any trunk parameters.
|
|
|
|
|
|
|
|
|
|
CSCdv68775
|
Using "dm" to view the SVC Hash Table protection padding shows that the padding has been corrupted, 30 bytes from the start of the pad. The corruption pattern is "01 00 C0". The protection pad was added as part of CSCdr91680 to protect the SVC Hash Table from a possible overwrite from a preceding structure. This possible overwrite has been confirmed.
|
|
|
|
|
|
|
|
|
CSCdv76336
|
The Major and Minor error rate values of 'cnflnalm 35' on IGX and 'cnflnalm 36' on BPX are different from rate values of other similar alarms.
|
|
|
|
|
|
CSCdv78776
|
After a full rebuild, the dsptrkutl command will block forever if stats are not ready.
|
|
|
|
|
|
CSCdw01948
|
Connections are unable to route over cell (UXM) cards. The dcba (display cell bus address usage) shows that there are no available cell bus channels, though the number of via connections is less than the maximum.
|
|
|
|
|
|
CSCdw11872
|
In networks of 223 nodes there is a possibility that a memory overwrite could occur and that data could be overwritten (corrupted). This could have unexpected results, including the possibility of an abort.
|
|
|
|
|
|
CSCdw15064
|
'addloclp' does not work for connection end points on BPX-BXM ports. The display shows that the connection is looped, but internally the system does not add the loop.
|
|
|
|
|
|
CSCdw16041
|
The cnfbusbw command does not work properly in a job. It will execute during the addjob.
|
|
|
|
|
|
|
|
|
CSCdw23663
|
Job Lock Timeout value was NOT initialized properly. The value showed 0 by default but some nodes have a non-zero value and can NOT do cnfnodeparm to change to 0.
|
|
|
|
|
|
|
|
CSCdw32857
|
When configuring IMA Protocol on a single T1 Trunk, user is required to reduce the Receive Rate to enable IMA. After that, the IMA 1xT1 trunk stays with T1/22 DS0s.
|
|
|
|
|
|
|
|
CSCdw34453
|
dsptrkstats/clrtrkstats on downed BNI card produced a software log 8096.
|
|
|
|
|
|
|
|
CSCdw39995
|
The dspapsln shows wrong line is active compared with rsh from FW.
|
|
|
|
|
|
|
|
CSCdw43792
|
No UAS statistics are collected when a line or trunk is in alarm.
|
|
|
|
|
|
|
|
|
|
|
|
CSCdw52505
|
Data connections which use the timestamped queue intermittently lose synchronization. The following connection types are affected:
•Isochronous HDM connections.
•Non-isochronous data connections configured for less than 100% utilization (DFM enabled).
|
|
|
|
|
|
CSCdw55317
|
No slot alarms are declared on the BPX, even though dspbxmsloterrs shows a lot of errors being reported by the card.
|
|
|
|
|
|
CSCdw58129
|
Slot 6 bxm card went into mismatch after swsw upgrade.
|
|
|
|
|
|
|
CSCdw58704
|
Software errors 502, 589, and 504 are logged from the SNMP process. The software error log may be filled with these errors. The "dspprf m t" command may show memory accumulation in the SNMP process.
|
CSCdw71912
|
dsptrkutl shows non-existent connections.
|
CSCdw79108
|
BPX node with 9.1.3A fails to sync to CWM station with 10.4.01 on it. The "dspsv3 <LCB #> display shows that the robust updates are sent up to the circuit line updates, but the trunk updates are not completed. The "dsprobst" display shows the robust messages are sent, but are timing out while waiting for an acknowledgment.
|
Anomalies in Release 9.2.40
This section lists the resolved anomalies and the anomaly status changes in Release 9.2.40.
Resolved Anomalies in Release 9.2.40
Table 22 lists the resolved anomalies in Release 9.2.40.
Table 22 Resolved Anomalies in Release 9.2.40
Bug ID
|
Description
|
CSCdr58334
|
Swerr 503 logged intermittently in extremely busy network.
|
CSCdr83230
|
Software errors 9093 and 9093 logged on IGX node.
|
CSCdr91680
|
1000003 abort in SNMP process while traversing SVC hash table. The hash table is traversed to add, delete, or find an SVC.
|
CSCdr95566
|
During BPX upgrade from 8.4.21 to 9.1.21, on 3 parameter 1 "Stby Heap memory init" was set to enabled.
|
CSCds26907
|
snmpwalk on BPX trunk connected to MGX reports trunk port off by 1.
|
CSCds52009
|
Empty slot reads reserved for BCC-3 when a BCC-4 is removed.
|
CSCds57049
|
Card in active-F status when 2 or more lines of the card are in major alarm.
|
CSCds62123
|
In the customer's network, the CNFCMB value for NTS is set to approximately 170 to allow lower speed NTS connections (g729a without VAD) to place two FastPackets in each ATM cell. This causes about 21 milliseconds of additional delay in each direction, or about 42 milliseconds or round-trip delay. This added delay is causing the echo.
|
CSCdt12153
|
IGX commands cnffrcls and cnfcon allow user to configure ECN threshold to be greater than VCQ depth.
|
CSCdt39231
|
Memory accumulation occurs after using TFTP to upload firmware.
|
CSCdt39873
|
LMI and ILMI port stats are collected incorrectly when the secondary card of a Y-red pair is active on an IGX.
|
CSCdt40533
|
If we put a dnld.fw/dnld.sw file without the path name a 1M3 abort is logged.
|
CSCdt45926
|
SW error 9098 is logged after the BCC is hitless rebuilt.
|
CSCdt60246
|
IGX feeder or SES has persistent local abit failure.
|
CSCdt73112
|
dspcurclk display is not correct on BPX.
|
CSCdt82310
|
When a Virtual Trunk (VT) is upped on a BNI-OC3 interface, it comes up with the default of 1459 connection channels (Maximum is 1459 * 11 VTs = 16049 LCN). When the VT is re-configured to increase the LCN number, SwSw does not allow to configure more than the following value [3836 - channels in use by the other VT's of the same port].
|
CSCdt89196
|
Switch is low on memory.
|
CSCdt90475
|
The cnfcon command cannot be added into job (using addjob or editjob command) in IGX.
|
CSCdt92054
|
The dspcd command shows the Line Mode on a UXM-OC3 briefly and then it is blanked out. After dspcd is executed and screen updates occur, some lines on the right hand side of the display appear to be briefly blanked out, then re-written.
|
CSCdt92193
|
VPC connections may not get bundled while routing
|
CSCdt93721
|
An extra character ("E" for E1 cards and "T" for T1 cards) is displayed between the "Config" word and the line format (T1 or E1) in the dsptrk and cnftrk screens
|
CSCdt96759
|
OAM Rx State of AIS/RDI for a local connection is not updated correctly.
|
CSCdt97285
|
In strata.mib atmEndptSubType var has atfst value as (6) but is not defined in description following as other sub-types. need MIB update.
|
CSCdu07360
|
VC shaping is blocked on the CLI interface. But using the SNMP interface, VC shaping field in the atmTrunks MIB can be set, which thus causes the card to be programmed for VC shaping in trunks.
|
CSCdu18109
|
Slot 32 cons of remote IGX appear on slot 15 (on the BPX) after inter-release upgrades.
|
CSCdu19452
|
The Standby NPM may abort logging SW Error 1000003 when "clrphyslnerrs" is entered.
|
CSCdu19705
|
Software Error 614s are logged and two connections are auto-deleted when configurations are restored with about 800 connections or more on IGX nodes.
|
CSCdu20243
|
AIS is not generated on a downed connection.
|
CSCdu20347
|
dlm screen gets overwritten.
|
CSCdu24322
|
Network Browser (NWB) of Cisco WAN Manager (CWM) displays BXM for BXM-T3-8E and BXM-E3-8E cards.
|
CSCdu25344
|
Software error (error code 9082) logged on IGX.
|
CSCdu25641
|
Adding a UVM(CVM) to FTM connection causes data base corruption and the connection is deleted after switchcc. Symptoms of the corruption are as follows:
•Multiple software errors (code 384) logged at slave node when adding CVM-FTM or UVM-FTM connections.
•Some of the FTM endpoints terminate on non-existent FTM ports.
•Software errors are seen at the slave node of a UVM-FTM or CVM-FTM connection after a CC switch. Software errors of type 614, 961, 372, and 384 may be observed.
|
CSCdu27936
|
ILMI does not work on BXM virtual trunks. ILMI does not work on UXM virtual trunks, if the protocol in enabled on card.
|
CSCdu28559
|
With 2-segment SIW-T connection from AXIS/FRSM to BXM Port on same BPX, return traffic is dropped to FRSM. Traffic is marked as non-compliant on BXM port and dropped. Connection is ABRFST type.
|
CSCdu35011
|
Cannot configure framing to OFF for UFM-C line.Software does not allow CRC to be disabled.
|
CSCdu35456
|
Low IDLE time on CWM gateway node. The dspprfhist command shows real-time usage increases in the NETW and PROT processes after CWM is enabled. The nwstats command show "Rx Buff Full" discards and very high Rx messages with function code 0x E1 (messages to CWM). The "dspsvmsg 2" will show a large number of robust trunk updates relative to other types of robust updates.
|
CSCdu38022
|
IGX commands cnffrcls and cnfcon allow user to configure ECN threshold to be greater than VCQ depth.
|
CSCdu40248
|
After upgrading from 9.1.19 to 9.2.36, the dsptrkutl command gives inaccurate information for virtual trunks.
|
CSCdu49568
|
The following commands cause an abort (1M3 swerr) when they are executed with an address of the format slot.start_port-end_port.
|
CSCdu52374
|
dsplmistats command cant be used by users with privilege 1-6.
|
CSCdu61462
|
Software error 2099,2057,894 logged on igx nodes
|
CSCdu70098
|
A Software error 55 is logged when a BXM card that has a line interface on it is reset or downed.
|
CSCdu77043
|
When adding lines to uxm IMA group, trunk goes into inverse mux failure and connections fail. They don't reroute as the other end of the connection says ok.
|
CSCdu82392
|
ChState and OE ChState are wrong in dcct display.
|
CSCdv01127
|
dsptech command shows incorrect values for FDR parameter, shows as feeders attached even though there are no feeders connected to the node.
|
Known Anomalies from Previous Releases Closed in 9.2.40
Table 23 lists the known anomalies in previous Switch Software deliveries that are resolved or closed in Release 9.2.40.
Table 23 Closed or Resolved Anomalies from Previous Releases
Bug ID
|
Description
|
CSCdk45222
|
This problem does not exist in 9.2.
|
CSCdm01239
|
This problem was fixed in the first release of 9.2.
|
CSCdm60702
|
Given the automatic recovery and the implementation of hitless rebuild in 9.2 and removal of many bus error triggers, this issue will not be addressed at this time. This bug has been closed.
|
CSCdm60707
|
Given the automatic recovery and the implementation of hitless rebuild in 9.2 and removal of many bus error triggers, this issue will not be addressed at this time. This bug has been closed.
|
CSCdp98648
|
This is currently in the 'I' state requesting more information from the submitter.
|
CSCdr25275
|
This has been closed with the recommendation that the customer submit a PER.
|
CSCdr25281
|
This has been closed with the recommendation that the customer submit a PER.
|
CSCdr75042
|
This bug has been closed and the issue addressed by modifying ABR-related flow control parameters.
|
CSCds33823
|
This has been closed as unreproducible.
|
CSCds34151
|
This bug has been closed and PER# 2699 has been opened for this issue.
|
CSCds57049
|
This is fixed in 9.2.40.
|
CSCdt16892
|
This bug is in the `C' (Closed) state because it works as designed.
|
CSCdt26312
|
This was closed as a duplicate of CSCdk48180 which was fixed in 9.2.38.
|
CSCdt62019
|
This was fixed in CWM 9.2.09
|
CSCdt97285
|
This is fixed in 9.2.40
|
CSCdu25641
|
This is fixed in 9.2.40
|
Resolved Anomalies in Release 9.2.38
Table 24 lists the resolved anomalies in Release 9.2.38 Switch Software.
Table 24 Resolved Anomalies in Release 9.2.38
Bug ID
|
Description
|
CSCdj38754
|
E3 trail trace string is not transmitted by lines on BXM-E3 cards.
|
CSCdj75848
|
dsppwr shows all power supplies as "AC Failed."
|
CSCdk48180
|
The bcc card is WDT reset and suddenly logs swerr52.
|
CSCdk77478
|
SNMP walk for statistics causes excessive card polling
|
CSCdm87370
|
swerr 526 occurs when command cnfchfax issued on IGX.
|
CSCdm94164
|
swerr 3028 logged after 9.2.2U upgrade
|
CSCdp49466
|
swerr 529 logged on BPX as a result of tstcon fault isolation.
|
CSCdp57264
|
ILMI manages to work only on one subinterface
|
CSCdp66407
|
dspchstats may display truncated value for Avg. CPS if cells exceed 21474836.
|
CSCdr33931
|
When active APS line in Yellow, Trunk is OK, but CWM is not informed.
|
CSCdr42274
|
Dspload doesn't display all existing trunks
|
CSCdr84212
|
BXM connection to slot 32 on a remote IGX is reported as being terminated on slot 15
|
CSCds05558
|
dspportcnf displays terminal port information instead of Frame Relay data.
|
CSCds07518
|
SNMP authentication error format non standard -- HPOV cant recognize
|
CSCds41674
|
dsppwr displays incorrect information in 9.1.22 with IGX8 nodes
|
CSCds84776
|
APS 1:1 line experiences a SigDegrade BER alarm that never clears.
|
CSCds88886
|
Flash type information for BXM card is only accessible through the rsh command.
|
CSCds89384
|
swerr 56 logged while running jobs for dncd/upcd with y-redundancy on HDM cards.
|
CSCdt06177
|
User viewing actual bit rate per sec rather than the 100's of bits per second per the MIB.
|
CSCdt12153
|
cnffrcls and cnfcon allow ECN threshold to be greater than VCQ depth.
|
CSCdt12595
|
swerr 527 logged when winkstart enabled for CVM-E1, Model B, FW rev D cds
|
CSCdt19038
|
Trunk or line fails when APS line redundancy is deleted
|
CSCdt24951
|
TFTP stat files not created but the CLI command dspstatparms shows stats enabled.
|
CSCdt31369
|
When tstber terminates before it is finished, BCC crosspoint test may log swerr 55.
|
CSCdt34566
|
BPX command tstber always reports that the BCC crosspoint test is active.
|
CSCdt35616
|
The dspstatsinfo command does not tally ports that are in the LOOPED state.
|
CSCdt39500
|
swerr 526 (NEG_FILL_REQ) occurs when doing dsptrkerrs/dsplnerrs/clrtrkerrs
|
CSCdt42261
|
Errors are recorded on the now active line and not the standby line.
|
CSCdt48334
|
dsprevs considers 'Secondary Loaded' revision to select the 'Lowest revision running in network'
|
CSCdt58349
|
The IGX or BPX node logs a swerr 516 or aborts with an error code of 1m3 (1000003)
|
CSCdt64027
|
Physical trunks on a BPX are defaulting to trunks that do not route the clock.
|
CSCdt66302
|
uptrk, hitless rebuild or switchcc clears Virtual trunk path fail momentarily
|
CSCdt66348
|
After adding VBR VP Tunneling conn IGX logs multiple 1000003 aborts
|
CSCdt89968
|
Channel statistics 42,43 are not valid for UFM card connections
|
CSCdt90019
|
FTM to FRM (either side can be master) will get auto deleted after an upgrade
|
CSCdt98295
|
Warning message for exceeding port bandwidth after switchcc
|
Resolved Anomalies in Release 9.2.37
Table 25 lists the resolved anomalies in the 9.2.37 Switch Software release.
Table 25 Resolved Anomalies in Release 9.2.37
Bug ID
|
Description
|
CSCdk48068
|
Unable to copy UVM FW DCA, DDA & DEC over trunks with getfwrev
|
CSCdk62907
|
Unable to disable telnet access using the off2 command.
|
CSCdp34465
|
dspcd on BME slot shows line type twice for BME card name.
|
CSCdr17998
|
9082 occurs when adding a UBR connection on an ASI
|
CSCdr20915
|
The defect of the option type of resetcd
|
CSCdr25253
|
No AIS-P alarm reported when Path AIS is sent from upstream equipment
|
CSCdr25273
|
AIS-L alarm is not properly propagated
|
CSCdr25275
|
RFI-L alarm not properly detected
|
CSCdr51769
|
dspqbinstats show negative values
|
CSCdr57396
|
Dereferencing uninitialized pointer
|
CSCdr64541
|
Negative Value in the Real Time Counters (Cbrctxl:-1728314534)
|
CSCds15146
|
dspclksrcs does not display correctly when cancelled and more screens
|
CSCds16812
|
Trunk Channel programmed with wrong values on BXM, UXM.
|
CSCds18089
|
cnfapsln uses incorrect term for SD BER
|
CSCds20977
|
Signal Degrade cleared in internal BXM states. SWSW still shows Signal Degrade.
|
CSCds24390
|
con_verify command should be restored in 9.2 and 9.3
|
CSCds47570
|
Modify the incorrect SCR value range (7-1412832) to (6-1412832).
|
CSCds52967
|
Secondary clocks hidden on dspclksrcs when a 34th primary is added.
|
CSCds59200
|
swlog378 logged while trying to copycons from the trunk card to UXM-T3 ca
|
CSCds61240
|
Connections added on BPX displays Unknown Response (17)
|
CSCds64587
|
copycons allows ATFX conns on FRM (doesn't support ATFX conns)
|
CSCds66268
|
copycons does not generate warning messages
|
CSCds66861
|
Inconsistent via conns routed over UXM trunk once gateway conn limit r
|
CSCds69729
|
tstconseg - Abort flag option does not work
|
CSCds72447
|
Cost-based route recovery allows route to exceed conn cost cap
|
CSCds75109
|
Negative numbers output on upstats command
|
CSCds75929
|
dspctrlrs output in BPX does not wraparound and the output is truncate
|
CSCds82339
|
Upgrade/switchcc on IGX may cause < 10% IDLE time for a long time
|
CSCds84556
|
Extra control characters to printf cause L in dsppwr screen
|
CSCds86393
|
SES-FDR:CDerrors Record Wraparound function does not work
|
CSCds88748
|
Software does not set LCN resync Bit during upgrade with upgraded firm
|
CSCds89338
|
Prefer path connection routed with negative load.
|
CSCdt01430
|
NWIP traffic is not delivered, other CC traffic is delivered as expected
|
CSCdt04146
|
SWSW error 923 was logged on BPX node
|
CSCdt04849
|
SW dnld should be blocked if fw download is going on
|
CSCdt04852
|
CWM: backcard removal info not updated, active empty card not removed
|
CSCdt15193
|
CLI rsh will cause node to abort (3m) if invoked when all memory area
|
CSCdt24344
|
Stby Bus Errors was being counted after the card failure
|
CSCdt24454
|
A Minor Alarm isn't flagged on your screen for a card failure
|
CSCdt35981
|
UXM-OC3 card shows Active-F, dspcd shows PLN Loopback Test Intermittently
|
CSCdt37502
|
FTM connections auto delete after switchcc
|
CSCdt49018
|
Node re-numbering from 39 causes IGX aborts and comm. break
|
CSCdu12537
|
Software error (error code 256) logged on BPX
|
Resolved Anomalies in Release 9.2.36
Table 26 lists resolved anomalies in the 9.2.35 Switch Software release.
Table 26 Resolved Anomalies in Release 9.2.36
Bug ID
|
Description
|
CSCdr82206
|
NPM in slot 2 may not be able to communicate with UXM
|
CSCds87060
|
Non-gateway LCN maybe assigned where gateway LCN is needed.
|
Resolved Anomalies in Release 9.2.35
Table 27 lists the resolved anomalies in Release 9.2.35 Switch Software.
Table 27 Resolved Anomalies in Release 9.2.35
Bug ID
|
Description
|
CSCdk19709
|
BPX may sync a neighbor test in error and report a suspected BCC failure
|
CSCdm07982
|
ALM/B and NTM reset with hardware errors after UFM card fails
|
CSCdm12139
|
Packet_line table not updating Bursty_a_load, Bursty_b_load
|
CSCdm42912
|
SNMPProxyAgent fails on SET of PrefRoute with 10 hops (switch rejects)
|
CSCdm60699
|
Async updates are sent incorrectly when VCQueue fills up.
|
CSCdp51531
|
Software log 21(9082) occurs when UBR con added and one of the endpoints is ASI-155
|
CSCdp53419
|
UXM trunk LCN verification not performed on card configuration
|
CSCdp56458
|
Software error 34 occurs when entering a three-part ASI address for many different UI commands
|
CSCdp73084
|
upport, dnport, cnfport do not show port speed due to screen overwrite
|
CSCdr03517
|
Info Bus A Reports 1 Error(s) (CNTL) logged frequently with LCC LDM FW
|
CSCdr53669
|
SLT:ILMI is not disabled after changing virtual trunk to line port.
|
CSCdr55450
|
Flood of swlog 992 kills ILMI task on BCC making all MGX 8220 unreachable
|
CSCdr58956
|
10 hop connection only adds in one direction with cost-based routing
|
CSCdr65152
|
MIB variables not incrementing for fpTrkStatsEntry variables
|
CSCdr68507
|
dsplog shows wrong VPI/VCI when port loopback deleted
|
CSCdr70919
|
Interface Shelf Major alarm logged when changing protocol to run on BXM card
|
CSCdr71482
|
dsptrkstats tx and rx load percentage incorrect, sometimes greater than 100%
|
CSCdr71781
|
Auto Memory reserved is not set to zero (swerr 3000) after upln on BXM-E
|
CSCdr72296
|
snmp walk on shelfslotinfotable causes swerr 26 when UXM is missing a back card
|
CSCdr73183
|
111 when 23 ifcs (trk/prt) on a BXM slot, 23+ causes trunk/port statistic loss
|
CSCdr73442
|
Deleting a simulated AAL5 feeder causes 1M3 abort and swerrs 513, 589 and 502
|
CSCdr74031
|
cnfcmb parameters changes on IGX when adding BPX to network
|
CSCdr74447
|
VC Depth does not get set to the correct value during addition of PVC
|
CSCdr74841
|
Display Routing Table Contents does not work
|
CSCdr74919
|
bnni lights do not go out after a dntrk
|
CSCdr75723
|
Software error 938 PNA_SEND_ERR when lan default gateway is set to zero.
|
CSCdr76988
|
Rounding problem in calculating UBU on dspbusbw
|
CSCdr78202
|
Software error 1120 logged during upgrading from 9.3.1T to 9.3.1V
|
CSCdr78391
|
Software error 3074 when upgrading from 931T to 931V
|
CSCdr78404
|
UVM has excessive delay for g729 conn which route on uxme 2Mbps virtual trunk
|
CSCdr79123
|
During routing delay of path may be calculated incorrectly
|
CSCdr79195
|
Too many connections could be packed by pack_conns()
|
CSCdr80522
|
Investigate user commands included HIPRI login for problem caused by Pause_proc
|
CSCdr80662
|
Some connection parameters are reset to default on rebuild/switchcc
|
CSCdr81947
|
dspselftst stopped working due to fragmented dynamic memory
|
CSCdr82470
|
Port loopback for the local slave end of a daxcon fails
|
CSCdr83296
|
VSI partition addition, dntrk or cnftrk on virtual trunk causes unreachability
|
CSCdr85197
|
The random() function is deterministic
|
CSCdr86188
|
AIS generates bit set for slave end of ATM daxcon with line in LOS
|
CSCdr86717
|
Mismatched back cards are allowed in a Y-red configuration
|
CSCdr91284
|
Two software errors 997s are logged after addtrk <vtrk>
|
CSCdr92045
|
Communication failure on trunks creates software error 1417.
|
CSCdr95419
|
delapsln executes without confirmation
|
CSCdr95576
|
Software error 327 with switchcc and failed connections
|
CSCdr95604
|
Allow IGX transmit rate to change locally for an added trunk.
|
CSCdr95788
|
Enhancement for signalling Qbin support
|
CSCdr96358
|
Last line of dsptech is writing into the border
|
CSCdr96513
|
The first interface upped on BXM/UXM has an incorrect maximum discard threshold.
|
CSCdr98681
|
cnftrk on BTM or ALM causes software error 923
|
CSCds00854
|
Software error 1427 is generated.
|
CSCds01587
|
Switch sending cells rx/tx statistics as 0 to CWM
|
CSCds02627
|
cnfqbin cannot use the default discard threshold.
|
CSCds02931
|
ILMI interval statistics are not collected.
|
CSCds03275
|
No trunk statistics are collected for last slot of IGX. Caused by CSCdm04491 fix
|
CSCds05668
|
Node goes into degraded mode after upgrading from 931Y to 931b
|
CSCds07761
|
SLT: Software error 103 UBU allocation errors
|
CSCds08777
|
Incorrect card/image accepted in tftp request. Missing Cmi_fwdl_prefix.
|
CSCds08808
|
Changing trunk rate using cnftrk overwrites BXM OC-12/T3/E3 with OC-3 Q depths
|
CSCds09778
|
BXM:CBR traffic drops as trunk Qbin bandwidth does not change with connection. reroute/dncon/upcon
|
CSCds12523
|
LMI Interval statistics are not collected.
|
CSCds13718
|
Incompatibility between Switch Software Release 9.2.23 and BXM firmware MF27.
|
CSCds16795
|
Incorrect programming of ingress/egress MCR on a terminating UXM trunk
|
CSCds17902
|
Software errors 532 & 538 found on BPX
|
CSCds22399
|
dspcon shows error of connection does not exist when dspcons shows all connections
|
CSCds22519
|
Software error 9082 logged for UXM when NPM resetcd
|
CSCds31978
|
Inconsistent via connections routed over UXM trunk once gateway connection limit is reached.
|
CSCds32831
|
dsptrkstats on down BNI card produces software log 8096
|
CSCds35608
|
UXM is not configurable to NON-CRC-4 mode.
|
CSCds36582
|
BCC Clock failure not processed by switch software during switchcc
|
CSCds39545
|
dspfdr does not display the VSI channels correctly.
|
CSCds43387
|
Software error 1128 on executing dspbuses when standby bus is failed
|
CSCds50411
|
delyred executes without confirmation
|
Resolved Anomalies in Release 9.2.34
Table 28 lists resolved anomalies in Release 9.2.34 Switch Software.
Table 28 Resolved Anomalies in Release 9.2.34
Bug ID
|
Description
|
CSCdk55887
|
dspport command moved from user-level-6 to user-level-2 in 8.1
|
CSCdm13655
|
VC bw parameter is not reused (initialized differently during upgrade vs. provision)
|
CSCdp50091
|
data_channel table not updating with 9.1.15 switch software
|
CSCdp67775
|
BPX does not clear last user request after SF switch
|
CSCdp93955
|
Swlog 532 when doing a snmpwalk on the node
|
CSCdr08430
|
Non TS queue size not saved in bram; also strange queue size behavior
|
CSCdr09440
|
ASI Qbin config lost when programming 2ndary card in Y-Red set
|
CSCdr11698
|
TS cell discards on Virtual Trunks with overbooked f/relay traffic
|
CSCdr11823
|
BCC tstber channel could use VPI that is in the VSI range
|
CSCdr15924
|
Failure to receive proper traps w/ 2+ CWMs pointing to same network
|
CSCdr20925
|
Connection data stops when reverted to primary in Y-red
|
CSCdr21739
|
Node hung up and lost access after deleting trunk.
|
CSCdr22568
|
ILMI Disable Command not sent to BXM FW when ILMI is disabled on a port
|
CSCdr23432
|
Switch aborts when cnfport command is issued.
|
CSCdr25318
|
UFMU port reports active state when the back card is missing
|
CSCdr27853
|
cnfcmparm 9 (reroute timer) should be defaulted to 3 seconds
|
CSCdr32789
|
Gateway LCNs are not getting updated if the other end is BXM and cnfrsrc done at BXM
|
CSCdr33428
|
UXM number of channels mismatch after card rebuild
|
CSCdr36808
|
SESSLT:SPVC reroute failed due to cross commit fail but PXM, BXM have RSRC
|
CSCdr36819
|
Message 0x53 not sent when dntrk/deltrk is done on Egress/Ingress side
|
CSCdr38707
|
SLT: Total VSI min. bw > 1412830 should not be allowed on BPX.
|
CSCdr41814
|
Prevent AR/VSI conflicts for VPIs used by Feeders for LMI/IP - SNMP changes
|
CSCdr48340
|
dspnw on a nw with IMA virtual trunks causes swerr 1423 or 1M3
|
CSCdr49264
|
Add rt-vbr connection via CWM, CLI shows nrt-vbr and snmpget shows as rt-vbr
|
CSCdr49301
|
PVC does not route after preferred is not available
|
CSCdr51105
|
Software error 30 is logged while UXM is inserted
|
CSCdr56249
|
Transition counter stats (LOS) not updated when line goes into alarm
|
CSCdr58725
|
Selftests: Freq.value of < 40seconds causes consistent resetting of UXM cards
|
CSCdr64725
|
MIB variable switchIfOperStatus reports up when a trunk is actually added
|
CSCdr67236
|
SES have stats file 1 hour ahead of bpx stats file even time are same
|
CSCdr75146
|
Connections will not route due to lack of LCNs as seen in constats command
|
CSCdr79123
|
During routing delay of path may be calculated incorrectly
|
Resolved Anomalies in Release 9.2.33
Table 29 lists the resolved anomalies in Release 9.2.33 Switch Software.
Table 29 Resolved Anomalies in Release 9.2.33
Bug ID
|
Description
|
CSCdj14920
|
Unable to clrcnf on BPX node whose number is > 63
|
CSCdm04491
|
Swerr 921 flooding
|
CSCdm13655
|
VC bw parm is not reused (initialized differently during upgrade vs. provision).
|
CSCdm29466
|
Cannot addtrk on the VSI network because of VPC conid mismatch
|
CSCdm31518
|
"Active CC failure (EEPROM, SAR) and standby unlock or reseat causes rebuild."
|
CSCdm38578
|
Echo Negotiation for telnet between AIX and BPX
|
CSCdm48790
|
SIU phase errors from all BXM cards in a node
|
CSCdm69629
|
Different values of statistical reserve for dsptrkcnf and dspload
|
CSCdm88055
|
Job run job experienced failed
|
CSCdp20486
|
UXM IMA physical line alarms are not sent to SV+
|
CSCdp50871
|
UP/Down Line on ALM-A behaves erratically.
|
CSCdp53961
|
Control card mastership error not properly detected by software
|
CSCdp58131
|
SNMP get function in atmTrunkStatsTable
|
CSCdp62387
|
APS Clear Trap 20100 does not distinguish various types of clear events.
|
CSCdp68440
|
Swerr 961(BAD_LCN_SPECIFIED) found after dnport/dnln
|
CSCdp72012
|
Swerr 129 (BAD_TYPE_LOGGED) found at BPX2
|
CSCdp73065
|
Background Tst card errors on active. Card has state ACTIVE-F w/ss
|
CSCdp73606
|
Port LED remains on when line is downed on UXM.
|
CSCdp78731
|
LCN and VPC conid count is not sending correctly in TBL
|
CSCdp83180
|
Swerr 614 AUTO_DEL_LCON and 612 AUTO_DEL_VC upon fallback from 9.3.0L
|
CSCdp83902
|
UVM Line pass through does not work on the second physical line on UVM
|
CSCdp87624
|
Autodel trunk when rebuilding a port with 32 vtrks
|
CSCdp93368
|
When up a line then switch software seems to program all cons on that card
|
CSCdp93728
|
Summary statistics overflow is not detected correctly for Port and VI stats
|
CSCdp94039
|
Swlog 2000 occurs when snmpwalk on an IGX node
|
CSCdp95286
|
Cross point failures on the bcc.
|
CSCdp95807
|
Robust object message for vtrunks appears to be reporting wrong channel count
|
CSCdp96768
|
VSI and SVC bandwidth is not eliminated while configuring egress hpqbn b/w.
|
CSCdp98970
|
VT session timeouts on particular page when running dsprts
|
CSCdp99622
|
"Burn UXM/FW using C-bus, gets aborted"
|
CSCdp99780
|
Inhibit line loop diagnostics for IMA line/trunk
|
CSCdr00360
|
A Tstdelay command cannot run while card is initilized
|
CSCdr04828
|
IP relay channel is not getting deprogrammed when AAL/5 feeder is deleted
|
CSCdr06086
|
A dsp_pa_fail0 switch statement falls through when it should not.
|
CSCdr06280
|
Conditional update should not be integrated for a trunk between T1 and E1
|
CSCdr08084
|
A 62 message is not send on addyred if the secondary card is running self-test
|
CSCdr08231
|
A clrtrkstats does not clear Trunk Qbin statistics
|
CSCdr08952
|
A addloclp on BNI feeder connection aborts a node under certain circumstances
|
CSCdr10473
|
A swerr 1012 (BAD_RS_NCHANS) occurs after hitless rebuild
|
CSCdr11310
|
Configure LMI on UXM port causing swerr 987
|
CSCdr11823
|
A non-Fatal card error occurs on red. BXM during PXM1 upgrade. Refer to bug CSC46785
|
CSCdr11837
|
The maximum channel limit for dspchoid command is incorrect
|
CSCdr12300
|
Switch MIB is inconsistent with the CLI
|
CSCdr14544
|
PNNI VPI.VCI 0.18 is blocked when path 0 is built on BXM.
|
CSCdr14558
|
Switch software updates wrong port DB and robust message after Y-Red UFM switch over.
|
CSCdr14935
|
Unable to add UFM UXM connections from UFM side and there is corruption of Be Bc.
|
CSCdr17056
|
Provide UNKNOWN state for serialPortLeadState
|
CSCdr19348
|
NTS connections get bit errors when Frame Relay bursts fill up trunk capacity
|
CSCdr20760
|
Incorrect prompt while deleting a trunk on IGX UXM card
|
CSCdr21739
|
Node hung up and lost access after deleting a trunk.
|
CSCdr26582
|
CD error after issuing a addctclr command (SLT)
|
CSCdr30234
|
Available Conids gets updated only on the nodes connected by the trunk.
|
CSCdr32875
|
"int_all_usr_updt, trkchans: kicks of reroute only for trunks attached locally."
|
CSCdr41370
|
Dspchstat from Port counter slowly ramps-up to send rate
|
Resolved Anomalies in Release 9.2.32
Table 30 lists resolved anomalies in Release 9.2.32 Switch Software.
Table 30 Resolved Anomalies in Release 9.2.32
Bug ID
|
Description
|
CSCdk03916
|
Trunk information is inconsistent
|
CSCdr26613
|
"When active APS line has YEL, trunk fails."
|
CSCdr35085
|
Switchcc cannot be cancelled when updates pending
|
Resolved Anomalies in Release 9.2.31
Table 31 lists the resolved anomalies in Release 9.2.31 Switch Software.
Table 31 Resolved Anomalies in Release 9.2.31
Bug ID
|
Description
|
CSCdk15523
|
"Integer overflow results in computation in get_bc, get_be funcs"
|
CSCdk22052
|
Switchcc event logged under trapd.log when the command is cancelled
|
CSCdk45354
|
No data continuity between UVM & HDM for nx64 connection
|
CSCdk60213
|
HDM data errors with 1152 kb/s connections on 9.1.06
|
CSCdm10213
|
After upgrade or switchcc in 9.1, extra connections may appear
|
CSCdm20593
|
Switch software should not allow an ATFR connection between two UXMs
|
CSCdm26083
|
Dsptrkbob causes swerr 30 and 923 when performed on sec Y-Red card
|
CSCdm46032
|
SNMP identifies ALM/A line as ATM trunk
|
CSCdm47765
|
VT cause memory leak
|
CSCdm68968
|
"VC-Q depth setting at default value, Connection Manager, IGX, routing and feeder node"
|
CSCdm75577
|
UFM-C to BXM SIW/NIW connection discards 100% cells at BXM on BPX if the connection is between UFM-C on IGX to BXM on BPX.
|
CSCdm77271
|
Incorrect modem upgrade support
|
CSCdm87788
|
Unable to add connection with maximum rate on BXM-T3 port with direct mapping
|
CSCdm91529
|
"Screen flicker on dspnds, with more than 2 columns nodes"
|
CSCdp07967
|
Statistics files updating standby cause standby to hang in update state
|
CSCdp09854
|
The value for maximum pvc bw in rsrc partition displays wrong value
|
CSCdp15350
|
SNMP GET-NEXT does not work for frLportStatTable
|
CSCdp20534
|
Uninitialized variable in get_rrt_space() function
|
CSCdp27598
|
Disabling and enabling echo canceller produces Channel Pair Problem
|
CSCdp32245
|
BXM-OC3 DX performance monitoring is not implemented Bellcore 253 Sec 6.2.2.
|
CSCdp32422
|
addlnlocrmtlp does not loop traffic properly in APS 1+1 cross over circuit
|
CSCdp32490
|
Secondary CC went from UPGRADED to STANDBY after pull/reinsert CC-backcard
|
CSCdp32760
|
Updates/Upgrades of circuit lines can cause a memory leak on the standby
|
CSCdp32823
|
IGX FAIL handler causes high CPU utilization
|
CSCdp34687
|
BPXs running 9.2.22 experiences commBreak every 5 seconds and cleared.
|
CSCdp34935
|
connCurrRouteDesc description inconsistent with code
|
CSCdp35155
|
LDM cderrs and card failed in 9.2.3M
|
CSCdp37572
|
Addcon command does not include connection display
|
CSCdp39883
|
Con with 1/101 VPI/VCI added at BXM fdr trunk caused UNRCH of its fdr
|
CSCdp41410
|
Modem Silence duration can be set to a maximum of only 5.1 seconds
|
CSCdp42776
|
Cannot configure BXM port by runjob command
|
CSCdp43913
|
Dsprsrc displays confusing information about Topo Discovery
|
CSCdp45833
|
SVC deletions are sometimes incomplete (swerr 332 with FFF1)
|
CSCdp47053
|
ALM/B Y-Red does not work for upgrade 8.5.09->9.1.15->9.2.23
|
CSCdp47428
|
IFC failed when shelf is re-added (with 2 partition)
|
CSCdp47479
|
Unable to configure feeder LMI timers
|
CSCdp48792
|
"The dsplog/trapd show the APS alarm cleared, but dspapsln is in LOS"
|
CSCdp48797
|
All connection parms go to 0 when change vc q depth
|
CSCdp49215
|
Addtrk on Y-red card causes swerr 9082
|
CSCdp49860
|
Dncon causes other connections to be downed
|
CSCdp49951
|
BPX hanging up with TUNL task using up to 60% CPU RT
|
CSCdp50593
|
Updated information PNNI ctrlr not sent after addctrlr command
|
CSCdp51318
|
No alarm of the APSLN in dsplog/dspapsln after Signal Degrade/Failure
|
CSCdp52802
|
UVM ports do not pass data due to stuck CCS conditioning
|
CSCdp53212
|
Dspload from IGX on a remote BPX with trunk no.> 8 is not allowed
|
CSCdp53891
|
Addloclp and addrmtlp command causes yellow alarm on UVI interface
|
CSCdp54106
|
"BCC switchcc causes Comm failure, telnet failure"
|
CSCdp54803
|
BCC switches over when standby is in update statistic with bad Spurious Int
|
CSCdp55388
|
Dspchuse shows wrong number for max PVC configured.
|
CSCdp55442
|
Addjob/editjob and cnfport corrupts memory or can cause a 1M3 abort
|
CSCdp58545
|
Distortion on UVM-to-CVM connections routed on UXM Trunks when VAD Threshold reached.
|
CSCdp58869
|
Unintelligent response from cnfcon command
|
CSCdp59960
|
UVM does not send yellow alarm to PBX when it receives a yellow alarm from PBX
|
CSCdp61539
|
"Networking channel deletion problem for Transparent, Blind and Inter-nodal"
|
CSCdp64345
|
Virtual trunk in comm fail is chosen by route or after hitless rebuild
|
CSCdp65187
|
Multiple switchyred within 10 seconds causes line to go in LOS for APS
|
CSCdp66930
|
No failed traps for user lockout but traps for BPX lockout
|
CSCdp69003
|
"Decrease Comm Brk clear, reroute and recondition time after rebuild"
|
CSCdp69582
|
Unable to switchyred on upgrade from BXM to BXM-E due to Qbin size mismatch
|
CSCdp70093
|
Failure configuring VSI ILMI gives error message Unknown error for LCN un avail.
|
CSCdp70295
|
"UNI port MIB should show range 1-255, not"
|
CSCdp73719
|
ILMI on card can be disabled through SNMP even if VSI ILMI enabled.
|
CSCdp76840
|
Resetcd on Active should warn when standby is still in PRGM mode.
|
CSCdp79429
|
Dspselftst shows test attempts incrementing yet Status always shows Not Run
|
CSCdp79560
|
TFTP Channel Stats are not reported correctly
|
CSCdp79719
|
Cnftrk on an IMA trunk shows negative transmit trunk rate!
|
CSCdp82720
|
Y-red: standby UXM does not take over when FW is burned on active card
|
CSCdp84848
|
Dsplogcd for a VSI trunk attempts to use an uninitialized pointer
|
CSCdp85171
|
Flood of HW failure messages from BXM caused node rebuild
|
CSCdp85238
|
Alarm are not getting updated when delapsln and switchyred/resetcd is done.
|
CSCdp86269
|
Trunks and LNs on aps cds go into LOS and never recover during gr253 -> ITUT.
|
CSCdp90123
|
Cnftrk for a vtrk on an OC12 interface gives a line coding prompt
|
CSCdp90130
|
Cnfrsrc shows more bandwidth than the physical maximum for a feeder.
|
CSCdp98715
|
Swlog 514 and 589 when doing dncon.
|
CSCdr00072
|
Using unintialized num_ports variable in av_bkcd()
|
Resolved Anomalies in Release 9.2.30
Table 32 lists the resolved anomalies in Release 9.2.30 Switch Software.
Table 32 Resolved Anomalies in Release 9.2.30
Bug ID
|
Description
|
CSCdk36040
|
"Trap 20004-wrong value for varbind trapCardType, FRP back card"
|
CSCdk53336
|
Tstdelay not working on non-enhanced ASI-155
|
CSCdk87939
|
Dspchcnf shows inconsistent information after upgrade to 9106
|
CSCdm05502
|
Need cnfuvmchparm parameters 8 and 9 to configure UVM echo cancelers
|
CSCdm19532
|
A-bit status not propagating through network changing from NNI to UNI port
|
CSCdm19535
|
Channel program problems for BXM virtual trunks
|
CSCdm24140
|
Delcon on IGX causes IDLE RT to drop
|
CSCdm31990
|
CVM cbus message (0xA0) is not delivered when the secondary card is active.
|
CSCdm42254
|
When user ID is deleted subsequent users are reported one off.
|
CSCdm53182
|
Swerr 923 logged when dsptrkred command is used.
|
CSCdm65380
|
Allow conids lower than 4096 for VT wraparound
|
CSCdm72719
|
Unable to add BNI VT over ASI port in some cases
|
CSCdm74224
|
Unable to configure a port on OC-3 card when others are already configured.
|
CSCdm85764
|
"IGX node logging constant swerr 2051, TFTP_FILE_SIZE_ERR"
|
CSCdm85783
|
Five connections were deleted. software errors 614/612/534 were logged during a full rebuild
|
CSCdm86633
|
Swerr 332 (BD_XLAT_INDX) and 325 (BD_XLATDB_REF) on VNS SVCs
|
CSCdm88262
|
Able to add atfr DAX conns from frm.xx - uxm.xx with pcr < 50 and policing: on.
|
CSCdm91238
|
SWerr 2003 is seen during a switchcc
|
CSCdm91631
|
During ungraceful upgrade from 9.1 to 9.2, some BW PARMS can become allocated
|
CSCdm92021
|
Error_slot were used instead of next_slot when checking next_slot parity error.
|
CSCdm92790
|
Voice and NTS IGX traffic is serviced in VBR Q of BXM
|
CSCdm93670
|
Cannot configure 2 OC3 trunk has 7K PVCs
|
CSCdm93701
|
PVC shows inconsistent prefer route information
|
CSCdm94587
|
Swerr 532 and 923 when deltrk of trunk on downed card
|
CSCdp00060
|
Swerr 526(NEG_FILL_REQ)
|
CSCdp01511
|
FRM - FRM, 2 seg. conn has cbr traffic type
|
CSCdp02203
|
Could not add 3 seg. FR-FR connection from CM GUI (FRM - FRSM)
|
CSCdp03317
|
VT Path Failure condition remains after the downed VPC in the cloud
|
CSCdp04213
|
Software error 3025 gets logged thrice, when do a walk on atmPortStatLmiStatAc.
|
CSCdp05149
|
1 mil 2 abort after full rebuild on N33
|
CSCdp06823
|
SW9082 after switchcc and tstconseg
|
CSCdp08636
|
BPX node showing a trunk connected to itself instead of MGX feeder
|
CSCdp11851
|
CMUP timeouts have to be increased to avoid thrashing
|
CSCdp12024
|
BPX sends wrong error messages to CWM
|
CSCdp12505
|
Memory should be moved from Pool Region to Hitless Region
|
CSCdp14002
|
Trunk fail/repair resets Concentric Comm Break Clearing etc.
|
CSCdp15671
|
Software error 105
|
CSCdp15712
|
Can not add con with certain VPI.VCI value
|
CSCdp16760
|
SWERR 3033 seen on BPX nodes
|
CSCdp16891
|
SWERR 532 seen on BPX nodes
|
CSCdp17303
|
Lines do nor show up in CWM 9.2.06M for certain BXM-E3/T3
|
CSCdp18093
|
Continuous BUS A|B Reports PRI LOSS (Clock) log messages when primclksrc = VT
|
CSCdp18160
|
False NNI failure indication at IGX FDR endpoint
|
CSCdp20894
|
Addlnloclp/dellnlp causes trunk Mgr Ret Yel and LOF (RED)
|
CSCdp20961
|
Swerr 5019 occured during loadrev and runrev 9.2.3F
|
CSCdp21688
|
Sec BXM card goes in mismatch during upgrade(9.1-9.2) when cards not in service.
|
CSCdp21803
|
Trapd log reports event trap on wrong node
|
CSCdp23116
|
"Continuous hitless rebuilds, if 1st abort is before hitless pointer"
|
CSCdp23196
|
Swerr 1101 (BAD_EVENT_TYPE) logged.
|
CSCdp23410
|
UXM physical trunks with VPI of 0 does not work
|
CSCdp24319
|
Dspcon for atfst connections does not display all parameters on second page
|
CSCdp24366
|
get_trunk() does not properly handle physical slot/logical slot mapping
|
CSCdp25420
|
A line which is upped can be configured as an IMA trunk
|
CSCdp25685
|
Software error 1012 logged upon a delshelf on a VSI trunk
|
CSCdp26827
|
Swerr 9082 logged for the nrtVBR conn 3.4.255.32852
|
CSCdp27775
|
Unable to add IGX feeder
|
CSCdp30654
|
LCN allocation issue with crosspoint test
|
CSCdp31596
|
IGX 9.2.22 NTM does not support FST in traffic class failing addtrk
|
CSCdp32058
|
Send CM update responses to unreachable nodes
|
CSCdp32815
|
Dspvsipartinfo display hangs; an issue for automating the testing
|
CSCdp34188
|
No continuity on a con routed over a BXM FDR to a IGX feeder
|
CSCdp35713
|
Channel for NW use counted twice
|
CSCdp39714
|
Move disabling of VPC conns upgrade to 9.2.30 from 9.2.23
|
Resolved Anomalies in Release 9.2.23
Table 33 lists the resolved anomalies in Release 9.2.23 Switch Software.
Table 33 Resolved Anomalies in Release 9.2.23
Bug ID
|
Description
|
CSCdm64323
|
Swerr 3005 BAD_DEFAULTS seen on two BPX nodes.
|
CSCdp25375
|
Abort does not cause hitless rebuild or switchcc (full rebuild instead)
|
Resolved Anomalies in Release 9.2.22
Table 34 lists the resolved anomalies in Release 9.2.22 Switch Software.
Table 34 Resolved Anomalies in Release 9.2.22
Bug ID
|
Description
|
CSCdp04046
|
Increase cm update time-out from 30 seconds to 90 seconds
|
CSCdp05661
|
Node is unreachable from one side but the route is fine
|
CSCdp10383
|
Tftp file stats for PHYSLINE object reports all ports as zero
|
Resolved Anomalies in Release 9.2.21
Table 35 lists the resolved anomalies in Release 9.2.21 Switch Software.
Table 35 Resolved Anomalies in Release 9.2.21
Bug ID
|
Description
|
CSCdj57458
|
Reduce privilege level for dspqs command
|
CSCdj79112
|
BXM does not allow SCR/CIR less than 50cps/19.2kbps
|
CSCdk26279
|
Block a user from disabling CAC override if ATM port is over subscribed
|
CSCdk34722
|
Enable EPD configuration on all BXM queues. Allow clp-lo > clp-hi. (UXM)
|
CSCdm06156
|
Sim-fdrs on BNIs are unreachable after rebuild, bad loopback rebuild
|
CSCdm19696
|
BME port configure is blocked need to set CAC override and shift on/off
|
CSCdm36041
|
When active BCC backcard is removed, no info to dsplog
|
CSCdm38356
|
100% Cell Loss on ALM/A VPCs (GW_TYPE_CELL_VPC) routed over ALM/B trunks
|
CSCdm40129
|
Crosspoint test failing on some BXM trunk test cases
|
CSCdm46335
|
Swerr 9091 on BPX node due to a tstdelay failure
|
CSCdm46537
|
Addcon does not check egress load with cac override disable and %util enable
|
CSCdm47933
|
Output of dspnds -d is larger than screen and columns wrap around
|
CSCdm51607
|
Print function is not working correctly (format issue)- ok 8.4 & broke
|
CSCdm52681
|
Switchyred causes data transfer stops for 1 to 4 minutes
|
CSCdm58441
|
Dcdrtbl on UXM card logs a BAD_CD_TYPE (55) swerr
|
CSCdm58804
|
Swerr 8096 logged on IST n/w for nightly jobs
|
CSCdm60541
|
Software error 919 (BAD_SVR_CNTR_PTR) was logged on BPX node in IST n/w
|
CSCdm61885
|
During a burnfwrev in a UXM card, it does not shows as program
|
CSCdm62078
|
Swerr 986 occured during cnftrk virtual trunk
|
CSCdm63072
|
Software errors 31 and 52 with addlocrmtlp where remote end is BPX feeder
|
CSCdm63583
|
DSPCONS -FABIT sometimes shows A-bit status incorrectly as UNUSED
|
CSCdm64034
|
Hitless rebuild count is not getting incremented
|
CSCdm64066
|
Tstdelay on the UXM conn fails reporting with state table hung
|
CSCdm64811
|
APS: switchyred causes LOS for 10 seconds
|
CSCdm65813
|
APS: switch back to working line incorrectly.
|
CSCdm68729
|
AIS getting generated on remotely looped back connections
|
CSCdm70167
|
Software error 104 after loading 9.2.2L
|
CSCdm71616
|
Cannot delete link from UXM-IMA virtual trunk
|
CSCdm73852
|
Feature mismatch may not be working for 1 port group BXM cards
|
CSCdm74630
|
Swerr 1415 logged in BPX
|
CSCdm76753
|
Shorten the error string displayed for supported load types for trunk
|
CSCdm76881
|
"Addyred not possible when upgrading from 8.4.21 to 9.1 or 9.2, in on"
|
CSCdm77070
|
Alarm-a line VPC mode can be changed when there are VPC cons on it!
|
CSCdm77509
|
AXIS feeder shows incorrectly as a MGX feeder
|
CSCdm80991
|
Unable to add conns using CM GUI with BPX 9.2.20 & MBE firmware
|
CSCdm83096
|
Failed to addyred on LDM: RCMP entries mismatch
|
CSCdm89320
|
BPX lmi messages to AXIS shelf do not contain correct I.E.
|
CSCdp05584
|
During 9.1->9.2 upgrade, user connection channels are allocated for cc traffic
|
CSCdp05865
|
BXM-E3/T3 cards show up as wrong card on SV+
|
Resolved Anomalies in Release 9.2.20
Table 36 lists the resolved anomalies in Release 9.2.20 Switch Software.
Table 36 Resolved Anomalies in Release 9.2.20
Bug ID
|
Description
|
CSCdk33999
|
Connections automatically removed, SWERR 532 BAD_LCD_INDEX,SWERR 590 SEND_FAIL
|
CSCdk34492
|
SNMP Agent - Wrong value returned for atmOtherEndptDesc
|
CSCdk85811
|
LAN fuse failed on NPM
|
CSCdk89665
|
Cannot configure line framing and signalling to NONE on UFM-C
|
CSCdk93626
|
Minimum MCR range is different in CLI & strata.mib
|
CSCdm00711
|
Hardware watchdog on NPM-32 when SNMP community strings configured
|
CSCdm08324
|
BXMs enables a BNIs CRXL statistic
|
CSCdm27574
|
Remove and reinsert Tx Fdr Trk cable causes connection failure.
|
CSCdm27726
|
CD errors: N. Fatal from 0x17: 0x25010022 0x0 0x22af 0x1 logged on BXM
|
CSCdm32599
|
NPM not recognizing traps with BXM ILMI at the cloud
|
CSCdm41637
|
Cnfpref buffer too short to load many 10 pref routes
|
CSCdm43422
|
Switch software does not dsptrkutl for NTM trunk
|
CSCdm43783
|
Swerr 55 occured after loadrev 9.2.1C in graceful upgrades
|
CSCdm44536
|
Swerr 532 & 55 cause by dcdrtbl on BXM & BNI trunks
|
CSCdm50232
|
Swerr 2000 logged on the node when trunk parameter is displayed through CiscoView
|
CSCdm50251
|
BPX: Port Real-Time Counters show incorrect values
|
CSCdm50372
|
Axis shelves report LMI failure when do hitless rebuild.
|
CSCdm51357
|
Swerr 121 on l3a(IGX)
|
CSCdm52990
|
Node experiences repeated abort 3M and 1M3 due to flooding on LMI channel
|
CSCdm53035
|
"Non-added trunks, the queue depth value should be changed with the line rate."
|
CSCdm53119
|
Swerr 129 is logged when dspswlog s command is executed on BPX node p6b
|
CSCdm53126
|
User ID updates do not stop if all nodes have invalid password for a user
|
CSCdm53376
|
Statistical trunk errors are not reported under dsptrkerrs
|
CSCdm54117
|
Swerr 9082s were logged at IST node igxr5
|
CSCdm56012
|
New versions of enhanced BXM card types need to be sent to SV.
|
CSCdm57535
|
Atmportstatmap_Table not getting initialized for ATM_PORT_STAT_BCM_RX_OFFSET
|
CSCdm58398
|
The trunk speed shown for dsptrkstats is incorrect
|
CSCdm59091
|
LDM & CVM conns cannot be modified by SV+ after upgrade
|
CSCdm59267
|
Additional ATM con subtypes need to be sent to SV+
|
CSCdm59268
|
Transaction handler sometimes is very busy on IGX
|
CSCdm61126
|
BPX reports incorrect status when burning firmware failed
|
CSCdm62548
|
Swerr 2085 occurs during a regression test.
|
CSCdm63487
|
Cnftrk does not prompt for Header Type: field
|
CSCdm63889
|
BCC reseated and remained in an update stage after BXMMEA upgrade
|
CSCdm64045
|
Software errors 886 and 2071 on image upgrade
|
CSCdm65060
|
Could not build a UNI IMA Group between IMATM and IGX UXM
|
CSCdm65089
|
Continuous PRI Clock loss messages in LOG
|
CSCdm65104
|
HDM failed the testcon command if its back card is configured as DTE
|
CSCdm66452
|
Tstber in manual mode stops receiving after nearly 1 1/2 hours.
|
CSCdm67094
|
Cnfasm is very detached from ASM functionality
|
CSCdm67130
|
ABR class of service is delayed from trunks
|
CSCdm67358
|
502/589/504/3m/1m3 and standby continuously WDTs
|
CSCdm68678
|
IMA virtual trunk configuration display will log swer 633 (LN_CNFG_DSP_OVFLW)
|
CSCdm69180
|
Cnftrk on UXM fdr trunk should be blocked if new LCNs are < used lcns
|
CSCdm69421
|
Traffic type displayed on cnftrk is not cleaned up correctly.
|
CSCdm69834
|
Default service template while upgrading from 9.1x to 9.2x
|
CSCdm72193
|
Unable to add UXM trunk
|
Resolved Anomalies in Release 9.2.10
Table 37 lists the resolved anomalies in Release 9.2.10 Switch Software.
Table 37 Resolved Anomalies in Release 9.2.10
Bug ID
|
Description
|
CSCdk21358
|
Front cards do not refresh if back cards are removed.
|
CSCdk26240
|
AIS transitions are not counted
|
CSCdk29716
|
Three-way PVC on frame relay connections after switchover
|
CSCdk33721
|
Swerr 614 is logged while doing a graceful upgrade
|
CSCdk51121
|
Dsplnalmcnf does not include trunks alarm configuration
|
CSCdk51259
|
slotBackNumPort is valid only for UXM and BXM cards
|
CSCdk55034
|
E3 BIP8 alarm error threshold is not triggered at 10E-3
|
CSCdk65743
|
Watchdog in VT_1 task (split off from CSCdk63204)
|
CSCdk69040
|
Adding cons to full port gives wrong return message
|
CSCdk77005
|
IGX16 logged 1000003 w/ SNMP process
|
CSCdk87933
|
"During SAR flood testing, some connections were autodelete"
|
CSCdm02272
|
BPX went into DEGRADED mode when cmd DSPLOGCD was initiated
|
CSCdm04372
|
Wrong atmPortIfType is returned for BXM-T3 card
|
CSCdm04812
|
Dspstatsinfo is counting feeder connections
|
CSCdm14446
|
No continuity for 3-byte frames routed over a UXM trunk
|
CSCdm18555
|
Need to redesign RCMP mismatch algorithm to allow use upgrade/downgrade card.
|
CSCdm19544
|
BPX 9.2 dspchstats does not show RX AIS
|
CSCdm24031
|
Burning old BXM FW to enhanced card will kill the card.
|
CSCdm29600
|
"After non graceful upgrade, swerrs 374, 752, Abort 1000003, can not add conns."
|
CSCdm36631
|
T3 trunk modification generates APS(OC3) traps
|
CSCdm37694
|
RtOp ran before ch clean up after 9.1.09 - 9.2.ja gracefully upgraded on UX
|
CSCdm37802
|
Swerr 706 in IGX feeder
|
CSCdm39210
|
Cnfcdaps causes a discrepancy between card attribute table and LCCB
|
CSCdm39227
|
CAC does not function correctly on a UXM port
|
CSCdm39836
|
Mib lacks definition for 8 port BNC connector card uaie1
|
CSCdm39871
|
MIB variable slotCardBackRev returns EW while it shows in CLI for ARM.
|
CSCdm40006
|
Add UXM/BXM VT to dspblkdfuncs and block in mixed NW
|
CSCdm40707
|
Swerr 4229 occurred after switchcc on BPX node
|
CSCdm41274
|
"Delyred logged swerr 514, 589, 143"
|
CSCdm41406
|
CPU usage above threshold message when do switchcc on 12000 conn node.
|
CSCdm41415
|
Dsptrkcnf/cnftrk does not show maximum channels for BNI trunks
|
CSCdm41881
|
"Swerr 514,589,502 logged on STBY BCC in l5b"
|
CSCdm42754
|
"Abort 2M when redundant CC, TFTP stats enabled, and a hitless is done"
|
CSCdm43471
|
SV+ can not see switch software 9.1.09 IGX-IGX FR Conns
|
CSCdm44056
|
APS Annex B switch software modifications
|
CSCdm44387
|
Swerr 1433 reported after switchcc
|
CSCdm44587
|
Swerr 29 BAD_PORT_NUM is reported on BPX node
|
CSCdm44973
|
Cnflnalm display shows alarm information on the wrong line of screen (after modifying)
|
CSCdm45274
|
Unable to configure Max LCNS to 32K on BXM-622-2DX card.
|
CSCdm45592
|
2068s and 504s flood log if statistics enabled before and after a hitless rebuild.
|
CSCdm45812
|
Block APS switching from standby to active line.
|
CSCdm45889
|
Swerrs 509 & 101 in IST n/w
|
CSCdm46095
|
Swerror 526 on adding or deleting APS lines
|
CSCdm46601
|
Software error 116 (BAD_OBJ_RESP) on statistic queries
|
CSCdm46790
|
"Memory leak in TRNS, SWERR 501, ABORT 3M, adaptive voice BW update msg leak."
|
CSCdm47814
|
Software error 9000 happens when UXM is activated in middle of its self-test
|
CSCdm48694
|
Robust card object message does not give Y redundancy information
|
CSCdm49385
|
Continuous hitless rebuild in case of abort
|
CSCdm49988
|
BXM card mismatch after upgrading from 9.109 to 9.2.01
|
CSCdm51212
|
3M Abort on BPX91 in IST n/w
|
CSCdm54599
|
UXM-FRM conns do not have continuity after a graceful upgrade (9.1.11->9.2.1K)
|
CSCdm54814
|
"549, 886 and 2071 occur on a rebuild, 928 on upping line"
|
Resolved Anomalies in Release 9.2.01
Table 38 lists the resolved anomalies in Release 9.2.01 Switch Software.
Table 38 Resolved Anomalies in Release 9.2.01
Bug ID
|
Description
|
CSCdj15839
|
False power supply over voltage or under voltage alarms reported
|
CSCdj31366
|
Clrcnf command to have explicit double warning message.
|
CSCdk21503
|
Swerr 921 on node n1a in 9.1 SLT n/w
|
CSCdk28204
|
Swerr 526 happened after switchcc on sw79
|
CSCdk29850
|
protocol_type column in frp table returns wrong number for IPX switch problem.
|
CSCdk32046
|
Cnfclnsigparm option 9 should not apply to FRM/FRP/UFM-C lines
|
CSCdk40766
|
Multiple upgrade/downgrade messages sent by switch software cause modem upgrade failure.
|
CSCdk47079
|
SW ERR 1000003 while running dth
|
CSCdk52672
|
Added PVCs after switchcc is auto-deleted.
|
CSCdk56688
|
Hipri error message problem
|
CSCdk69440
|
IGX running swsw 9.1.04 has dspprf IDLE at 30% when adding UVM cards
|
CSCdk69498
|
Incorrect A-bit status in FR NNI link
|
CSCdk72199
|
IMA trunk load db not updating after trunk failure
|
CSCdk74438
|
Addcon does not work with job (job does not take 8/8 options)
|
CSCdk82927
|
Slow TCP / Telnet response & disconnects on LAN pt after upgrade to NPM64
|
CSCdk83511
|
Correlation tag not checked at BPX Port
|
CSCdk87005
|
Avoid satellite *s needs extra parameters with an addcon
|
CSCdk91395
|
Vague error message when attempting to reconfigure remote PCR > T1/E1 port speed
|
CSCdk92892
|
The FTMs bandwidth is not configured when a FAX session is complete
|
CSCdm05373
|
Incorrect UVM channel configuration used
|
CSCdm07825
|
2065 caused when enabling invalid statistics configuration (fix is known)
|
CSCdm10020
|
Shelf alarm is unreachable on BPX (9.1) with IGX feeder graceful upgrade 9.1.08-9.
|
CSCdm13012
|
Can upped 31 vtrk and 1 port on a BXM. Card reported missing after down
|
CSCdm15043
|
Dangling LCNs might happen under some conditions.
|
CSCdm16904
|
"SWSW repeatedly reprograms same connections, nonstop in a loop, on UXM"
|
CSCdm17109
|
Software error 526 (NEG_FILL_REQ) occurred on IGX node
|
CSCdm20480
|
Card shows standby while cons are in the card
|
CSCdm20716
|
"Switchcc causes swerr 331 if on1 16, some reroutes if any VPC cons"
|
CSCdm22316
|
VSI feeder endpoint connections traffic are not mapping the vpi/vci correctly.
|
CSCdm23206
|
Cnfcon faces problem in accepting TCRR value through command line.
|
CSCdm23489
|
Swerr 514 is logged on bpx01 in upgrades testing
|
CSCdm23669
|
"921s filled software error log, appears to be related to a trunk deletion."
|
CSCdm24282
|
LM3 caused by cnfch command
|
CSCdm25268
|
LMI is still in loop on bpx/axis after upgrade
|
CSCdm25595
|
Dspcons shows PVCs but dspcon does not on BPX
|
CSCdm26897
|
Free the memory for IP relay message.
|
CSCdm27681
|
Y-red UXM/IMA back cards came up as mismatch after a graceful upgrade 9.1.09-9.2.0N
|
CSCdm28561
|
"4225,614,534,612, 4208, 3058 logged on switchover, stolen log end is root cause."
|
CSCdm28721
|
Swerr 532 in l5b
|
CSCdm29043
|
Potential for card errors with add_cd_red_cons() function.
|
CSCdm29706
|
Ports cannot configure HCF shift on/off w/out deleting connections
|
CSCdm30018
|
Trunk Cell routing restriction is not prompted any more for ATM conn.
|
CSCdm30262
|
Incorrect logic for VTs in g_ima_grp_member()
|
CSCdm30359
|
Failed to add daxcon path connection due to incorrect VPI checking.
|
CSCdm30608
|
Software error 55 after addalmslot 16
|
CSCdm31674
|
Yellow alarm line conditioning for T1 lines
|
CSCdm32384
|
Node rebuild on BPX caused comm fail.
|
CSCdm33967
|
After upgrade 9.1.09 to 9.2.00 trunks went comm. failure and then OK
|
CSCdm34282
|
Dbs_Pre_9110 not initialized properly in Root()
|
Additional Deliverables
SNMP MIB
The SNMP IGX/BPX switch SNMP MIB is being provided with the delivery of Release 9.2.47 Switch Software. The MIB is in standard ASN.1 format and is located in the ASCII text files agent.m, ilmi.m, ilmi_ctl.m, ilmiaddr.m, switch.m, swtraps.m, and errors.m which are included in the same directory as the Switch Software images. These files may be compiled with most standards-based MIB compilers.
Switch MIB changes of Release 9.2
The following Switch MIB changes were introduced since Release 9.2.00. The changes include Obsolete objects, Modified objects, and New objects:
switchIfTable
New objects:
switchIfCtrlVPI
switchIfCtrlVCIStart
Modified objects:
switchIfEntry
switchIfScTmpltId
atmPortTable:
New objects:
atmPortHcfShift
Modified objects:
atmPortEntry
atmPortMetro
atmPortQueueTable:
Modified objects:
atmPortQueueType
atmPortQueueDepth
connTable:
Modified objects:
connCurrRouteDesc
connPrefRouteDesc
atmEndptTable:
New Objects:
atmEndptOeOamStatus
Modified objects:
atmEndptDesc
atmOtherEndptDesc
atmEndptSubType
atmEndptMCR
atmBwClassTable:
Modified objects:
atmBwClassConType
The following objects are associated with the switchShelf configuration branch.
New objects:
shelfCnfgFBTC
shelfCnfgSerialLeadTypeIndex
shelfCnfgSerialLeadMonitorTimer
shelfCnfgSystemTime
shelfSlotInfoTable:
Modified objects:
slotBackType
slotFrontNumPort
slotBackSonetMode
slotCardMinBusUBU
sonetIfTable:
Modified objects:
sonetIfType
sonetStatsTable:
New objects:
sonetStatsYelTcs
sonetStatsLocs
sonetStatsLops
sonetStatsPthAis
sonetStatsPthYels
sonetStatsSecBip8s
sonetStatsLnBip24s
sonetStatsLnFebes
sonetStatsPthBip8s
sonetStatsPthFebes
sonetStatsSecBip8Es
sonetStatsLnBip24Es
sonetStatsLnFebeEs
sonetStatsPthBip8Es
sonetStatsPthFebeEs
sonetStatsSecBip8Ses
sonetStatsSecSefs
sonetStatsLnBip24Ses
sonetStatsLnFebeSes
sonetStatsPthBip8Ses
sonetStatsPthFebeSes
sonetStatsLnUas
sonetStatsLnFarendUas
sonetStatsPthUas
sonetStatsPthFarendUas
sonetStatsHcsCrtblErrEs
Modified objects:
sonetStatsEntry
atmTrunks table:
Modified objects:
atmTrkType
atmTrkTrafCls
rsrcPartiTable:
New objects:
rsrcPartiVsiIlmiEnable
Modified objects:
rsrcPartiEntry
rsrcPartiVsiVpiEnd
serialPortTable:
New objects:
serialPortLeadState
Modified objects:
SerialPortEntry
serialPortLeadState
Default Values
This section contains default values for the BPX and IGX nodes.
BPX 8600 Nodes
The default values for BXM and Enhanced-BXM cards are the same.
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:19 GMT
System-Wide Parameters
1 Max Time Stamped Packet Age (msec) ................................ 32
2 Allow CPU Starvation of Fail Handler .............................. No
3 Max Network Delay for 'v' connections (msec)....................... 14
4 Max Network Delay for 'c' connections (msec)....................... 27
5 Max Network Delay for 't' & 'p' connections (msec)................. 14
6 Max Network Delay for 'a' connections (msec)....................... 27
7 Max Network Delay for High Speed Data connections (msec)........... 32
8 Max Network Delay for CDP-CDP 'v' connections (msec)............... 64
9 Max Network Delay for CDP-CDP 'c' connections (msec)............... 64
10 Max Network Delay for CDP-CDP 't' & 'p' connections (msec)......... 64
11 Max Network Delay for CDP-CDP 'a' connections (msec)............... 64
12 Max Network Delay for CDP-CDP High Speed Data connections (msec)... 64
13 Enable Discard Eligibility......................................... No
14 Use Frame Relay Standard Parameters Bc and Be...................... No
15 Max Local Delay for Interdom CDP-CDP 'v' conns (msec).............. 27
16 Max Local Delay for Interdom CDP-CDP 'c' conns (msec).............. 27
17 Max Local Delay for Interdom CDP-CDP 't' & 'p' conns (msec)........ 27
18 Max Local Delay for Interdom CDP-CDP 'a' conns (msec).............. 27
19 Max Local Delay for Interdom CDP-CDP High Speed Data conns (msec).. 27
20 Max Local Delay for Interdom High Speed Data conns (msec).......... 28
21 FastPAD Jitter Buffer Size (msec)................................. 15
22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm . 0
23 Enable Connection Deroute Delay feature............................ No
24 Interval Statistics polling rate for ATM VCs....................... 5
25 Interval Statistics polling rate for ports on IPX/IGX 8400 nodes... 5
This Command: cnfsysparm
node VT StrataCom BPX 8620 9.2.41 Aug. 13 2001 19:11 PST
1 Update Initial Delay [ 5000] (D) 16 Stats Memory (x 100KB) [ 132] (D)
2 Update Per-Node Delay [30000] (D) 17 Standby Update Timer [ 10] (D)
3 Comm-Break Test Delay [30000] (D) 18 Stby Updts Per Pass [ 50] (D)
4 Comm-Break Test Offset [ 10] (D) 19 Gateway ID Timer [ 30] (D)
5 Network Timeout Period [ 1700] (D) 20 GLCON Alloc Timer [ 30] (D)
6 Network Inter-p Period [ 4000] (D) 21 Comm Fail Delay [ 60] (D)
7 NW Sliding Window Size [ 1] (D) 22 Nw Hdlr Timer (msec) [ 50] (D)
8 Num Normal Timeouts [ 7] (D) 23 SAR CC Transmit Rate [ 560] (D)
9 Num Inter-p Timeouts [ 3] (D) 24 SAR High Transmit Rate [ 280] (D)
10 Num Satellite Timeouts [ 6] (D) 25 SAR Low Transmit Rate [ 56] (D)
11 Num Blind Timeouts [ 4] (D) 26 SAR VRAM Cngestn Limit [ 7680] (D)
12 Num CB Msg Timeouts [ 5] (D) 27 SAR VRAM Cell Discard [ 256] (D)
13 Comm Fail Interval [10000] (D) 28 ASM Card Cnfged [ Y] (Y/N)
14 Comm Fail Multiplier [ 3] (D) 29 TFTP Grant Delay (sec) [ 1] (D)
15 CC Redundancy Cnfged [ Y] (Y/N) 30 TFTP ACK Timeout (sec) [ 10] (D)
31 TFTP Write Retries [ 3] (D) 46 Max Htls Rebuild Count [ 100] (D)
32 SNMP Event logging [ Y] (Y/N) 47 Htls Counter Reset Time[ 1000] (D)
33 Job Lock Timeout [ 60] (D) 48 Send Abit early [ N] (Y/N)
34 Max Via LCONs [50000] (D) 49 Abit Tmr Multiplier M [ 0] (D)
35 Max Blind Segment Size [ 3570] (D) 50 Abit Tmr Granularity N [ 3] (D)
36 Max XmtMemBlks per NIB [ 3000] (D) 51 FBTC with PPDPolicing [ N] (Y/N)
37 Max Mem on Stby Q (%) [ 33] (D) 52 Num Chgs per ILMI Trap [ 5] (1/5)
38 Stat Config Proc Cnt [ 1000] (D)
39 Stat Config Proc Delay [ 2000] (D)
40 Enable Degraded Mode [ Y] (Y/N)
41 Trk Cell Rtng Restrict [ Y] (Y/N)
42 Enable Feeder Alert [ N] (Y/N)
43 Reroute on Comm Fail [ N] (Y/N)
44 Auto Switch on Degrade [ Y] (Y/N)
45 Max Degraded Aborts [ 100] (D)
This Command:cnfnodeparm
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:20 GMT
Index Status Function
1 Enabled Automatic TRK Loopback Test on Local/Remote Alarms
2 Enabled User Command Logging
3 Enabled Automatic Card Reset on Hardware Error
4 Enabled Card Error Record Wraparound
5 Disabled Card Test After Failure
6 Disabled Download From Remote Cisco StrataView Plus
7 Disabled Logging of conn events in local event log
8 Disabled Logging of conn events in Cisco StrataView Plus event log
9 Disabled Force Download From a Specific IP address
This Command: cnffunc
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:20 GMT
Index Status Function
1 Disabled Configuration Save/Restore
2 Enabled ForeSight
3 Disabled Multiple VTs (1 session enabled)
4 Disabled Virtual Trunks
5 Enabled ABR standard with VSVD
This Command: cnfswfunc
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:20 GMT
Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -
Type Freq Enable Inc Thresh Timeout Enable Inc Thresh
---- ----- -------- ------- ------- ------- -------- ------- -------
BCC 1600 Enabled 100 300 800 N/A 100 300
ASM 300 Disabled 100 300 60 N/A 100 300
BNI-T3 300 Enabled 100 300 150 N/A 100 300
BNI-E3 300 Enabled 100 300 150 N/A 100 300
ASI-E3 900 Enabled 100 300 800 Enabled 100 300
ASI-T3 900 Enabled 100 300 800 Enabled 100 300
ASI-155 900 Enabled 100 300 800 Enabled 100 300
BNI-155 300 Enabled 100 300 150 N/A 100 300
BXM 4000 Enabled 100 300 3000 Enabled 100 300
This Command: cnftstparm
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:20 GMT
1 Normalization Interval [ 2] (D)
2 Max Number To Normalize [ 5] (D)
3 Normalization Logging [ No]
4 Settling Interval [ 4] (D)
5 Minimum Open Space [ 1000] (D)
6 Normalization Priority [ Load]
7 Load Sample Period [ 4] (D)
8 Maximum Routing Bundle [ 90] (D)
9 Reroute Timer [ 0] (secs)
10 Reset Timer on Line Fail [ Yes]
11 Max Down/Up Per Pass [ 50] (D)
12 Down/Up Timer [30000] (msecs)
13 Max Route Errs per cycle [ 50] (D)
14 Time between Rrt cycles [ 5] (mins)
15 Max. Rrt Err cycles [ 10] (D)
16 Routing pause timer [ 0] (msecs)
17 Max msgs sent per update [ 10] (D)
18 Send SVC urgent msg [ No]
19 Max SVC Retry [ 0] (D)
20 Wait for TBL Updates [ 70] (100 msecs)
21 Max Derouting Bndl (0=all)[ 500] (D)
22 Enable Cost-Based Routing [ No]
23 Enable Route Cache Usage [ No]
24 Use Delay for Routing [ No]
25 # of reroute groups used [ 50] (D)
26 Starting size of RR grps [ 0] (CLU)
27 Increment between RR grps [ 100] (CLU)
This Command: cnfcmparm
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:21 GMT
1 Rmt Blk Freq (msec) [ 100] 16 FW Dnld Msgs/Block(dec) [ 4]
2 Rmt Blk Size (hex) [ 400] 17 Flash Write TO(msec) [ 16000]
3 Lcl Blk Freq (msec) [ 100] 18 Flash Erase TO(msec) [ 100]
4 Lcl Blk Size (hex) [ 400] 19 Erase Verify TO(msec) [ 16000]
5 Image Req Freq (msec) [ 10000] 20 Standby Flash TO(sec) [ 300]
6 Dnld Req Freq (msec) [ 10000] 21 Lcl Flash Init TO(msec) [ 1000]
7 Session Timeout (msec) [ 30000] 22 Flsh Write Blk Sz (hex) [ 10000]
8 Request Hop Limit (dec) [ 1] 23 Flsh Verfy Blk Sz (hex) [ 400]
9 Crc Throttle Freq (dec) [ 5000] 24 Chips Per Write/Erase [ 1]
10 Crc Block Size (hex) [ 400]
11 Rev Change Wait(dec) [ 0]
12 CCs Switch Wait(dec) [ 1000]
13 Lcl Response TO(msec) [ 5000]
14 Rmt Response TO(msec) [ 20000]
15 FW Dnld Block TO(msec) [ 50]
This Command: cnfdlparm
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:21 GMT
1. Logout Time ........... 20 minutes
2. VT Logout Time ........ 4 minutes
3. Prompt Time ........... 60 seconds
4. Command Time .......... 3 minutes
5. UID Privilege Level ... 6
6. Input Character Echo .. Enabled
7. Screen Update Time .... 10 seconds
This Command: cnfuiparm
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:21 GMT
Function Number Status Function Number Status
Background Upcard 1 Enabled Conn Stat Sampling 15 Enabled
Background Updates 2 Disabled Neighbor Update Errs 16 Disabled
Standby Terminal 3 Enabled
Memory Protection 4 Enabled
Comm Break 5 Enabled
Comm Fail Test 6 Enabled
CRC Test 7 Enabled
Bus Fail Detection 8 Enabled
Line Diag 9 Enabled
Clock Restoral 10 Enabled
Cm_Rerouting 11 Enabled
Clock Routing 12 Enabled
Dynamic BW Allocation 13 Enabled
Modem Polling 14 Enabled
This Command: on1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:21 GMT
Function Number Status Function Number Status
Line Stat Sampling 1 Enabled Robust Alarm Updates 15 Enabled
Statistical Alarm 2 Enabled Realtime Counters 16 Enabled
Job Ready Checker 3 Enabled LAN Interface 17 Enabled
Configuration Backup 4 Enabled Update Standby Stats 18 Enabled
Standby Update 5 Enabled Telnet Access 19 Enabled
Downloader 6 Enabled Junction ID 20 Enabled
Cm Updates 7 Enabled Mult SV+/Routing Node 21 Disabled
Topo/Stat Updates 8 Enabled Simulated Fdr Trks 22 Disabled
Card Statistical Alms 9 Enabled Deroute Delay 23 Enabled
Card Stat Sampling 10 Enabled Auto Renum Fail Recov 24 Enabled
Address Validation 11 Enabled Card Simulation Tool 25 Disabled
ASM Stats Polling 12 Enabled
Port Stat Sampling 13 Enabled
Robust Updates 14 Enabled
This Command: on2
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:21 GMT
Function Number Status
Region memory init 1 Disabled
Trace Msg Sent 2 Disabled
Multi-DB Stby Updates 3 Enabled
Trace Conv Msg 4 Disabled
This Command: on3
BNI-T3
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 3.1 Config T3 [96000 cps] BNI-T3 slot: 3
Transmit Rate: 96000 VPC Conns disabled: --
Protocol By The Card: -- Line framing: PLCP
VC Shaping: -- coding: --
Hdr Type NNI: -- recv impedance: --
Statistical Reserve: 1000 cps cable type:
Idle code: 7F hex length: 0-225 ft.
Connection Channels: 1771 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: -- HCS Masking: Yes
SVC Channels: 0 Payload Scramble: No
SVC Bandwidth: 0 cps Frame Scramble: --
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 3.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 3.1 Parameters
1 Q Depth - rt-VBR [ 242] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 8878] (Dec)
4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)
5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)
8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 3.1
BNI-E3
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 4.1 Config E3 [80000 cps] BNI-E3 slot: 4
Transmit Rate: 80000 VPC Conns disabled: --
Protocol By The Card: -- Line framing: --
VC Shaping: -- coding: --
Hdr Type NNI: -- recv impedance: --
Statistical Reserve: 1000 cps cable type:
Idle code: 7F hex length: 0-225 ft.
Connection Channels: 1771 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: -- HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: --
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 4.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 4.1 Parameters
1 Q Depth - rt-VBR [ 202] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 8978] (Dec)
4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)
5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)
8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 4.1
BXM-T3
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 5.1 Config T3 [96000 cps] BXM slot: 5
Transmit Rate: 96000 VPC Conns disabled: No
Protocol By The Card: No Line framing: PLCP
VC Shaping: No coding: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: 0-225 ft.
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: No
SVC Bandwidth: 0 cps Frame Scramble: --
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 5.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 5.1 Parameters
1 Q Depth - rt-VBR [ 242] (Dec) 15 Q Depth - CBR [ 400] (Dec)
2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [10000] (Dec)
4 Q Depth - BData A [ 8000] (Dec) 18 Low CLP - CBR [ 60] (%)
5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 80] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)
8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 5.1
BXM-OC12
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:22 GMT
TRK 6.1 Config OC12 [1412679cps] BXM slot: 6
Transmit Rate: 1412830 VPC Conns disabled: No
Protocol By The Card: No Line framing: STS-12C
VC Shaping: No coding: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: Yes
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 6.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:23 GMT
TRK 6.1 Parameters
1 Q Depth - rt-VBR [ 3533] (Dec) 15 Q Depth - CBR [ 1200] (Dec)
2 Q Depth - Non-TS [ 5297] (Dec) 16 Q Depth - nrt-VBR [10000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [40000] (Dec)
4 Q Depth - BData A [40000] (Dec) 18 Low CLP - CBR [ 60] (%)
5 Q Depth - BData B [40000] (Dec) 19 High CLP - CBR [ 80] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)
8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 6.1
BNI-155-OCS
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:23 GMT
TRK 11.1 Config OC3 [353207cps] BNI-155 slot: 11
Transmit Rate: 353208 VPC Conns disabled: --
Protocol By The Card: -- Line framing: STS-3C
VC Shaping: -- coding: --
Hdr Type NNI: -- recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: --
Connection Channels: 16050 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: -- HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: Yes
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 11.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:23 GMT
TRK 11.1 Parameters
1 Q Depth - rt-VBR [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - nrt-VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [15463] (Dec)
4 Q Depth - BData A [ 1000] (Dec) 18 Low CLP - CBR [ 100] (%)
5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 100] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 100] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 100] (%)
8 Red Alm - I/O (Dec) [ 2500 / 10000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 10000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 30] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 11.1
BXM-E3
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:23 GMT
TRK 12.1 Config E3 [80000 cps] BXM slot: 12
Transmit Rate: 80000 VPC Conns disabled: No
Protocol By The Card: No Line framing: --
VC Shaping: No coding: --
Hdr Type NNI: Yes recv impedance: --
Statistical Reserve: 1000 cps cable type: --
Idle code: 7F hex length: 0-225 ft.
Connection Channels: 256 Pass sync: No
Traffic:V,TS,NTS,FR,FST,CBR,N&RT-VBR,ABR Loop clock: No
SVC Vpi Min: 0 HCS Masking: Yes
SVC Channels: 0 Payload Scramble: Yes
SVC Bandwidth: 0 cps Frame Scramble: --
Restrict CC traffic: No Virtual Trunk Type: --
Link type: Terrestrial Virtual Trunk VPI: --
Routing Cost: 10 Deroute delay time: 0 seconds
Last Command: dsptrkcnf 12.1
node TN StrataCom BPX 8620 9.2.41 Aug. 13 2001 16:23 GMT
TRK 12.1 Parameters
1 Q Depth - rt-VBR [ 202] (Dec) 15 Q Depth - CBR [ 400] (Dec)
2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - nrt-VBR [ 5000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [10000] (Dec)
4 Q Depth - BData A [ 8000] (Dec) 18 Low CLP - CBR [ 60] (%)
5 Q Depth - BData B [ 8000] (Dec) 19 High CLP - CBR [ 80] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - nrt-VBR [ 60] (%)
7 Max Age - rt-VBR [ 20] (Dec) 21 High CLP - nrt-VBR [ 80] (%)
8 Red Alm - I/O (Dec) [ 2500 / 15000]22 Low CLP/EPD-ABR [ 60] (%)
9 Yel Alm - I/O (Dec) [ 2500 / 15000]23 High CLP - ABR [ 80] (%)
10 Low CLP - BData A [ 100] (%) 24 EFCN - ABR [ 20] (%)
11 High CLP - BData A [ 100] (%) 25 SVC Queue Pool Size [ 0] (Dec)
12 Low CLP - BData B [ 25] (%)
13 High CLP - BData B [ 75] (%)
14 EFCN - BData B [ 30] (Dec)
This Command: cnftrkparm 12.1
IGX 8400 Nodes
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:56 GMT
System-Wide Parameters
1 Max Time Stamped Packet Age (msec) ................................ 32
2 Allow CPU Starvation of Fail Handler .............................. No
3 Max Network Delay for 'v' connections (msec)....................... 14
4 Max Network Delay for 'c' connections (msec)....................... 27
5 Max Network Delay for 't' & 'p' connections (msec)................. 14
6 Max Network Delay for 'a' connections (msec)....................... 27
7 Max Network Delay for High Speed Data connections (msec)........... 32
8 Max Network Delay for CDP-CDP 'v' connections (msec)............... 64
9 Max Network Delay for CDP-CDP 'c' connections (msec)............... 64
10 Max Network Delay for CDP-CDP 't' & 'p' connections (msec)......... 64
11 Max Network Delay for CDP-CDP 'a' connections (msec).............. 64
12 Max Network Delay for CDP-CDP High Speed Data connections (msec)... 64
13 Enable Discard Eligibility......................................... No
14 Use Frame Relay Standard Parameters Bc and Be...................... No
15 Max Local Delay for Interdom CDP-CDP 'v' conns (msec).............. 27
16 Max Local Delay for Interdom CDP-CDP 'c' conns (msec).............. 27
17 Max Local Delay for Interdom CDP-CDP 't' & 'p' conns (msec)........ 27
18 Max Local Delay for Interdom CDP-CDP 'a' conns (msec).............. 27
19 Max Local Delay for Interdom CDP-CDP High Speed Data conns (msec).. 27
20 Max Local Delay for Interdom High Speed Data conns (msec).......... 28
21 FastPAD Jitter Buffer Size (msec)................................. 15
22 Number of Consecutive Invalid Login Attempts to Cause Major Alarm . 0
23 Enable Connection Deroute Delay feature ........................... No
24 Interval Statstics polling rate for ATM/Frame Relay VCs............ 5
25 Interval Statistics polling rate for ports......................... 5
This Command: cnfsysparm
node TRM StrataCom IGX 8420 9.2.41 Aug. 13 2001 18:42 PST
1 Update Initial Delay [ 5000] (D) 16 CC Redundancy Cnfged [ Y] (Y/N)
2 Update Per-Node Delay [30000] (D) 17 MT3 Pass Through Relay [ Y] (Y/N)
3 Comm-Break Test Delay [30000] (D) 18 Nw Pkt Tx Rate (pps) [ 500] (D)
4 Comm-Break Test Offset [ 10] (D) 19 Stats Memory (x 100KB) [ 130] (D)
5 Network Timeout Period [ 1700] (D) 20 Standby Update Timer [ 10] (D)
6 Network Inter-p Period [ 4000] (D) 21 Stby Updts Per Pass [ 100] (D)
7 NW Sliding Window Size [ 1] (D) 22 Gateway ID Timer [ 30] (D)
8 Num Normal Timeouts [ 7] (D) 23 GLCON Alloc Timer [ 30] (D)
9 Num Inter-p Timeouts [ 3] (D) 24 Comm Fail Delay [ 60] (D)
10 Num Satellite Timeouts [ 6] (D) 25 Nw Hdlr Timer (msec) [ 100] (D)
11 Num Blind Timeouts [ 4] (D) 26 CBUS Delay (msec) [ 20] (D)
12 Num CB Msg Timeouts [ 2] (D) 27 SNMP Event logging [ Y] (Y/N)
13 Comm Fail Interval [10000] (D) 28 TFTP Grant Delay (sec) [ 1] (D)
14 Comm Fail Multiplier [ 3] (D) 29 TFTP ACK Timeout (sec) [ 10] (D)
15 Temperature Threshold [ 50] (D) 30 TFTP Write Retries [ 3] (D)
31 FRP Link Status Alarm [ Y] (Y/N) 46 Modem polling timer [ 1] (D)
32 Job Lock Timeout [42405] (D) 47 Verify CBA for non-FRP [ N] (Y/N)
33 Max Via LCONs [20000] (D) 48 Send Abit early [ N] (Y/N)
34 Max Blind Segment Size [ 3570] (D) 49 Abit Tmr Multiplier M [ 0] (D)
35 Max XmtMemBlks per NIB [ 3000] (D) 50 Abit Tmr Granularity N [ 3] (D)
36 Max Mem on Stby Q (%) [ 33] (D) 51 Num Chgs per ILMI Trap [ 5] (1/5)
37 Trk Cell Rtng Restrict [ Y] (Y/N)
38 Stat Config Proc Cnt [ 1000] (D)
39 Stat Config Proc Delay [ 2000] (D)
40 Enable Degraded Mode [ Y] (Y/N)
41 Enable Rrt on Comm Fail[ N] (Y/N)
42 Auto Switch on Degrade [ Y] (Y/N)
43 Max Degraded Aborts [ 100] (D)
44 Max Htls Rebuild Count [ 100] (D)
45 Htls Counter Reset Time[ 1000] (D)
This Command:cnfnodeparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:57 GMT
Index Status Function
1 Enabled Automatic CLN/PLN Loopback Test on Local/Remote Alarms
2 Enabled FDP Loopback button
3 Enabled User Command Logging
4 Enabled Automatic Card Reset on Hardware Error
5 Enabled TXR Model D Download
6 Enabled Card Error Record Wraparound
7 Disabled Card Test After Failure
8 Disabled Download From Remote Cisco StrataView Plus
9 Disabled Logging of conn events in local event log
10 Disabled Logging of conn events in Cisco StrataView Plus event log
11 Disabled Logging SVC Connection Events
12 Disabled Force Download From a Specific IP address
13 Disabled CDP WinkStart Signalling
14 Enabled Logging of Bus Diagnostic Events in local event log
15 Enabled Automatic Card Reset after Burnfw for CBI cards
This Command: cnffunc
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:57 GMT
Index Status Function
1 Disabled Data Frame Multiplexing
2 Disabled Adaptive Voice
3 Enabled Frame Relay
4 Disabled Configuration Save/Restore
5 Disabled ForeSight
6 Disabled Frame Relay Network-to-Network Interface
7 Disabled Multiple VTs (1 session enabled)
8 Disabled Interface Shelf
9 Enabled Virtual Trunks
10 Disabled ABR standard with VSVD
This Command: cnfswfunc
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:57 GMT
Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -
Type Freq Enable Inc Thresh Timeout Enable Inc Thresh
---- ----- -------- ------- ------- ------- -------- ------- -------
PSM 300 Enabled 100 300 31 N/A 100 300
HDM 300 Enabled 100 300 80 Enabled 100 300
LDM 300 Enabled 100 300 80 Enabled 100 300
NTM 300 Enabled 100 300 31 N/A 100 300
FRM 300 Enabled 100 300 80 Enabled 100 300
MT3 300 Enabled 100 300 50 N/A 100 300
CVM 300 Enabled 100 300 300 N/A 100 300
NPM 180 Enabled 100 300 120 N/A 100 300
ARM 300 Enabled 100 300 60 N/A 100 300
BTM 300 Enabled 100 300 120 N/A 100 300
FTM 300 Enabled 100 300 80 Disabled 100 300
UFM 300 Enabled 100 300 80 Enabled 100 300
This Command: cnftstparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:57 GMT
Card Test - - - - - - Self Test - - - - - - - - - Background Test - - -
Type Freq Enable Inc Thresh Timeout Enable Inc Thresh
---- ----- -------- ------- ------- ------- -------- ------- -------
UFMU 300 Enabled 100 300 80 Enabled 100 300
ALM 300 Enabled 100 300 120 N/A 100 300
UVM 300 Disabled 100 300 60 N/A 100 300
UXM 300 Enabled 100 300 800 Enabled 100 300
This Command: cnftstparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:57 GMT
1 Normalization Interval [ 2] (D)
2 Max Number To Normalize [ 5] (D)
3 Normalization Logging [ No]
4 Settling Interval [ 4] (D)
5 Minimum Open Space [ 1000] (D)
6 Normalization Priority [ Load]
7 Load Sample Period [ 4] (D)
8 Maximum Routing Bundle [ 90] (D)
9 Reroute Timer [ 0] (secs)
10 Reset Timer on Line Fail [ Yes]
11 Max Down/Up Per Pass [ 50] (D)
12 Down/Up Timer [30000] (msecs)
13 Max Route Errs per cycle [ 200] (D)
14 Time between Rrt cycles [ 5] (mins)
15 Max. Rrt Err cycles [ 1] (D)
16 Routing pause timer [ 0] (msecs)
17 Max msgs sent per update [ 10] (D)
18 Send SVC urgent msg [ Yes]
19 Max SVC Retry [ 0] (D)
20 Wait for TBL Updates [ 70] (100 msecs)
21 Max Derouting Bndl (0=all)[ 500] (D)
22 Enable Cost-Based Routing [ No]
23 Enable Route Cache Usage [ No]
24 Use Delay for Routing [ No]
25 # of reroute groups used [ 50] (D)
26 Starting size of RR grps [ 0] (CLU)
27 Increment between RR grps [ 100] (CLU)
This Command: cnfcmparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:58 GMT
1 Rmt Blk Freq (msec) [ 100] 16 FW Dnld Msgs/Block(dec) [ 4]
2 Rmt Blk Size (hex) [ 400] 17 Flash Write TO(msec) [ 16000]
3 Lcl Blk Freq (msec) [ 100] 18 Flash Erase TO(msec) [ 100]
4 Lcl Blk Size (hex) [ 400] 19 Erase Verify TO(msec) [ 16000]
5 Image Req Freq (msec) [ 10000] 20 Standby Flash TO(sec) [ 300]
6 Dnld Req Freq (msec) [ 10000] 21 Lcl Flash Init TO(msec) [ 1000]
7 Session Timeout (msec) [ 30000] 22 Flsh Write Blk Sz (hex) [ 10000]
8 Request Hop Limit (dec) [ 1] 23 Flsh Verfy Blk Sz (hex) [ 400]
9 Crc Throttle Freq (dec) [ 5000] 24 Chips Per Write/Erase [ 1]
10 Crc Block Size (hex) [ 400]
11 Rev Change Wait(dec) [ 0]
12 CCs Switch Wait(dec) [ 1000]
13 Lcl Response TO(msec) [ 5000]
14 Rmt Response TO(msec) [ 30000]
15 FW Dnld Block TO(msec) [ 50]
This Command: cnfdlparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:58 GMT
1. Logout Time ........... 20 minutes
2. VT Logout Time ........ 4 minutes
3. Prompt Time ........... 60 seconds
4. Command Time .......... 3 minutes
5. UID Privilege Level ... 6
6. Input Character Echo .. Enabled
7. Screen Update Time .... 10 seconds
This Command: cnfuiparm
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:58 GMT
Function Number Status Function Number Status
Background Upcard 1 Enabled Dynamic BW Allocation 15 Enabled
Background Updates 2 Disabled Modem Polling 16 Enabled
Standby Terminal 3 Disabled Conn Stat Sampling 17 Enabled
Memory Protection 4 Enabled SVC Del Bgnd Updates 18 Disabled
Comm Break 5 Enabled FastPAD Test 19 Enabled
Comm Fail Test 6 Enabled Neighbor Update Errs 20 Disabled
BRAM Memory Protect 7 Enabled
CRC Test 8 Enabled
CDT Clock Test 9 Enabled
Bus Fail Detection 10 Enabled
Line Diag 11 Enabled
Clock Restoral 12 Enabled
Cm_Rerouting 13 Enabled
Clock Routing 14 Enabled
This Command: on1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:58 GMT
Function Number Status Function Number Status
Line Stat Sampling 1 Enabled LAN Interface 15 Enabled
Statistical Alarm 2 Enabled Update Standby Stats 16 Enabled
Job Ready Checker 3 Enabled EIA Monitoring 17 Enabled
Configuration Backup 4 Enabled Telnet Access 18 Enabled
Standby Update 5 Enabled Junction ID 19 Enabled
Downloader 6 Enabled Mult SV+/Routing Node 20 Enabled
Cm Updates 7 Enabled Feeder with NW Trunks 21 Disabled
Power Supply Monitor 8 Enabled Multiple Fdr Trunks 22 Disabled
Topo/Stat Updates 9 Enabled Simulated Fdr Trks 23 Disabled
CDP/CIP Sig. Polling 10 Enabled Auto Renum Fail Recov 24 Enabled
Port Stat Sampling 11 Enabled IGX - ACM Selftest 25 Enabled
Robust Updates 12 Enabled Card Simulation Tool 26 Enabled
Robust Alarm Updates 13 Enabled Major Alarm on NNI 27 Disabled
Realtime Counters 14 Enabled Deroute Delay 28 Enabled
This Command: on2
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:58 GMT
Function Number Status
Region memory init 1 Disabled
Trace Msg Sent 2 Disabled
Multi-DB Stby Updates 3 Enabled
AIT/BTM/ALM 32h Ext2 4 Enabled
Card Synchronization 5 Disabled
Loop Access Dev Init 6 Disabled
Auto allocate UXM UBU 7 Disabled
Trace Conv Msg 8 Disabled
Automatic Cbus Diags 9 Disabled
CBUS Flood Protection 10 Enabled
This Command: on3
NTM-E1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 3 Config E1/32 [10666 pps] NTM slot:3
Line DS-0 map: 0-31
Pass sync: Yes
Loop clock: No
Statistical Reserve: 600 pps
Routing Cost: 10
Idle code: 54 hex
Restrict PCC traffic: No
Link type: Terrestrial
Line coding: HDB3
Line CRC: No
Line recv impedance: 75 ohm + gnd
Traffic: V,TS,NTS,FR,FST
Deroute delay time: 0 seconds
Last Command: dsptrkcnf 3
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 3 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ N/A]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 28] 32 BDataA [ 600]
13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 40] 33 BDataB [ 600]
14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2632] 34 HighPri[ 100]
This Command: cnftrkparm 3
NTM-T1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 4 Config T1/24 [8000 pps] NTM slot:4
Line DS-0 map: 0-23
Pass sync: Yes
Loop clock: No
Statistical Reserve: 600 pps
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: D4
Line coding: B8ZS
Line cable type: ABAM
Line cable length: 0-133 ft.
Traffic: V,TS,NTS,FR,FST
Deroute delay time: 0 seconds
Last Command: dsptrkcnf 4
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 4 Parameters:
1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ N/A]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 22] 32 BDataA [ 600]
13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 30] 33 BDataB [ 600]
14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2648] 34 HighPri[ 100]
This Command: cnftrkparm 4
NTM-SR
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 5 Config SR/30 [10000 pps] NTM slot:5
Subrate interface: X.21
Subrate data rate: 1920 kbps
Pass sync: No
Loop clock: Yes
Statistical Reserve: 600 pps
Routing Cost: 10
Restrict PCC traffic: No
Link type: Terrestrial
Traffic: V,TS,NTS,FR,FST
Deroute delay time: 0 seconds
Last Command: dsptrkcnf 5
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 5 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - rt-VBR (D) [ N/A] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ N/A] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ N/A]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ N/A] 21 BDataA [ 128] 23 BDataA [ 128]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ 128] 24 BDataB [ 128]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ N/A] 10 BDataA [ N/A] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ N/A] 11 BdataB [ N/A] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ N/A] 15 BDataA [ N/A] 29 rt-VBR [ 27] 32 BDataA [ 600]
13 Non TS [ N/A] 16 BDataB [ N/A] 30 Non TS [ 37] 33 BDataB [ 600]
14 TS [ N/A] 17 HighPri[ N/A] 31 TS [ 2636] 34 HighPri[ 100]
This Command: cnftrkparm 5
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 16:59 GMT
TRK 6.1 Config OC3 [353207cps] UXM slot:6
Transmit Trunk Rate: 353208 cps Connection Channels: 256
Rcv Trunk Rate: 353207 cps Gateway Channels: 200
Pass sync: Yes Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Loop clock: No Frame Scramble: Yes
Statistical Reserve: 1000 cps Deroute delay time: 0 seconds
Header Type: NNI VC Shaping: No
VPI Address: 1 VPC Conns disabled: No
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: STM-1
HCS Masking: Yes
Payload Scramble: Yes
Last Command: dsptrkcnf 6.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 6.1 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 10000] 18 Red Alm-In/Out (D) [ 2500/ 10000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 1952] 15 BDataA [10000] 29 rt-VBR [ 1952] 32 BDataA [10000]
13 Non TS [ 2925] 16 BDataB [10000] 30 Non TS [ 2925] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
TRK 6.1 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 6.1
UXM-E3
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 7.1 Config E3/530 [80000 cps] UXM slot:7
Transmit Trunk Rate: 80000 cps Payload Scramble: Yes
Rcv Trunk Rate: 80000 cps Connection Channels: 256
Pass sync: Yes Gateway Channels: 200
Loop clock: No Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Statistical Reserve: 1000 cps Deroute delay time: 0 seconds
Header Type: NNI VC Shaping: No
VPI Address: 1 VPC Conns disabled: No
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: HEC
Line cable length: 0-225 ft.
HCS Masking: Yes
Last Command: dsptrkcnf 7.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 7.1 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 443] 15 BDataA [10000] 29 rt-VBR [ 443] 32 BDataA [10000]
13 Non TS [ 662] 16 BDataB [10000] 30 Non TS [ 662] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
This Command: cnftrkparm 7.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 7.1 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 7.1
UXM-T1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 8.1 Config T1/24 [3622 cps] UXM slot:8
IMA Group Member(s): 1 Line coding: B8ZS
Retained links: 1 Line cable type: ABAM
Transmit Trunk Rate: 3622 cps Line cable length: 0-131 ft.
Rcv Trunk Rate: 3622 cps HCS Masking: Yes
Pass sync: Yes Payload Scramble: No
Loop clock: No Connection Channels: 256
Statistical Reserve: 600 cps Gateway Channels: 200
Header Type: NNI Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
VPI Address: 1 IMA Protocol Option: Disabled
Routing Cost: 10 IMA Max. Diff. Dly: 200 msec.
Idle code: 7F hex IMA Clock Mode: CTC
Restrict PCC traffic: No Deroute delay time: 0 seconds
Link type: Terrestrial VC Shaping: No
Line framing: ESF VPC Conns disabled: No
Last Command: dsptrkcnf 8.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 8.1 Parameters:
1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 22] 15 BDataA [10000] 29 rt-VBR [ 21] 32 BDataA [10000]
13 Non TS [ 30] 16 BDataB [10000] 30 Non TS [ 28] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
This Command: cnftrkparm 8.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 8.1 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 8.1
UXM-E1/30
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:00 GMT
TRK 9.1 Config E1/30 [4528 cps] UXM slot:9
Line DS-0 map: 1-15,17-31 Line coding: HDB3
IMA Group Member(s): 1 Line CRC: Yes
Retained links: 1 Line recv impedance: 120 ohm
Transmit Trunk Rate: 4528 cps HCS Masking: Yes
Rcv Trunk Rate: 4528 cps Payload Scramble: Yes
Pass sync: Yes Connection Channels: 256
Loop clock: No Gateway Channels: 200
Statistical Reserve: 600 cps Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Header Type: NNI IMA Protocol Option: Disabled
VPI Address: 1 IMA Max. Diff. Dly: 200 msec.
Routing Cost: 10 IMA Clock Mode: CTC
Idle code: 54 hex Deroute delay time: 0 seconds
Restrict PCC traffic: No VC Shaping: No
Link type: Terrestrial VPC Conns disabled: No
Last Command: dsptrkcnf 9.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 9.1 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ N/A]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 27] 15 BDataA [10000] 29 rt-VBR [ 26] 32 BDataA [10000]
13 Non TS [ 37] 16 BDataB [10000] 30 Non TS [ 36] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
This Command: cnftrkparm 9.1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 9.1 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 9.1
BTM-T3
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 11 Config T3/3 [1000 pps] BTM slot:11
Transmit Trunk Rate: 96000 cps HCS Masking: Yes
Rcv Trunk Rate: 1000 pps Payload Scramble: No
Pass sync: Yes Traffic: V,TS,NTS,FR,FST
Loop clock: No Deroute delay time: 0 seconds
Statistical Reserve: 1000 pps
Header Type: STI
Gateway Type: BAM
VPI Address: 0
VCI Address: 0
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line cable length: 0-225 ft.
Last Command: dsptrkcnf 11
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 11 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ 30] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ 100] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ 100] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ 100] 10 BDataA [ 100] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ 75] 11 BdataB [ 25] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 4] 15 BDataA [ 2264] 29 rt-VBR [ 532] 32 BDataA [ 2264]
13 Non TS [ 3] 16 BDataB [ 2264] 30 Non TS [ 795] 33 BDataB [ 2264]
14 TS [11365] 17 HighPri[ 100] 31 TS [10045] 34 HighPri[ 100]
This Command: cnftrkparm 11
BTM-E3
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 12 Config E3/3 [1000 pps] BTM slot:12
Transmit Trunk Rate: 80000 cps HCS Masking: Yes
Rcv Trunk Rate: 1000 pps Payload Scramble: Yes
Pass sync: Yes Traffic: V,TS,NTS,FR,FST
Loop clock: No Deroute delay time: 0 seconds
Statistical Reserve: 1000 pps
Header Type: STI
Gateway Type: BAM
VPI Address: 0
VCI Address: 0
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line cable length: 0-225 ft.
Last Command: dsptrkcnf 12
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 12 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ 30] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ 100] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ 100] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ 100] 10 BDataA [ 100] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ 75] 11 BdataB [ 25] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 4] 15 BDataA [ 2264] 29 rt-VBR [ 443] 32 BDataA [ 2264]
13 Non TS [ 3] 16 BDataB [ 2264] 30 Non TS [ 662] 33 BDataB [ 2264]
14 TS [11365] 17 HighPri[ 100] 31 TS [10267] 34 HighPri[ 100]
This Command: cnftrkparm 12
BTM-HSSI
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:01 GMT
TRK 13 Config HSSI/3 [1000 pps] BTM slot:13
Clock Rate: 50840000 bps Line cable length: 0-225 ft.
Transmit Trunk Rate: 111491 cps HCS Masking: Yes
Rcv Trunk Rate: 1000 pps Payload Scramble: No
Pass sync: No Traffic: V,TS,NTS,FR,FST
Loop clock: No Deroute delay time: 0 seconds
Statistical Reserve: 1000 pps
Header Type: STI
Gateway Type: BAM
VPI Address: 0
VCI Address: 0
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Last Command: dsptrkcnf 13
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:02 GMT
TRK 13 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ 30] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - Rx_Space (%) [ 100] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ 100] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP (%) Tx High CLP (%) Tx Low CLP (%)
8 BDataA [ 100] 10 BDataA [ 100] 25 BDataA [ 100] 27 BDataA [ 100]
9 BDataB [ 75] 11 BdataB [ 25] 26 BDataB [ 75] 28 BDataB [ 25]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 4] 15 BDataA [ 2264] 29 rt-VBR [ 617] 32 BDataA [ 2264]
13 Non TS [ 3] 16 BDataB [ 2264] 30 Non TS [ 922] 33 BDataB [ 2264]
14 TS [11365] 17 HighPri[ 100] 31 TS [ 9833] 34 HighPri[ 100]
This Command: cnftrkparm 13
UXM-T1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:13 GMT
TRK 8.4 Config T1/24 [3622 cps] UXM slot:8
IMA Group Member(s): 4 Line coding: B8ZS
Retained links: 1 Line cable type: ABAM
Transmit Trunk Rate: 3622 cps Line cable length: 0-131 ft.
Rcv Trunk Rate: 3622 cps HCS Masking: Yes
Pass sync: Yes Payload Scramble: No
Loop clock: No Connection Channels: 256
Statistical Reserve: 600 cps Gateway Channels: 200
Header Type: NNI Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
VPI Address: 1 IMA Protocol Option: Disabled
Routing Cost: 10 IMA Max. Diff. Dly: 200 msec.
Idle code: 7F hex IMA Clock Mode: CTC
Restrict PCC traffic: No Deroute delay time: 0 seconds
Link type: Terrestrial VC Shaping: No
Line framing: ESF VPC Conns disabled: No
Last Command: dsptrkcnf 8.4
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:13 GMT
TRK 8.4 Parameters:
1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ 2.0]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 22] 15 BDataA [10000] 29 rt-VBR [ 21] 32 BDataA [10000]
13 Non TS [ 30] 16 BDataB [10000] 30 Non TS [ 28] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
This Command: cnftrkparm 8.4
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:14 GMT
TRK 8.4 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 8.4
UXM-E1
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:14 GMT
TRK 9.4 Config E1/30 [4528 cps] UXM slot:9
Line DS-0 map: 1-15,17-31 Line coding: HDB3
IMA Group Member(s): 4 Line CRC: Yes
Retained links: 1 Line recv impedance: 120 ohm
Transmit Trunk Rate: 4528 cps HCS Masking: Yes
Rcv Trunk Rate: 4528 cps Payload Scramble: Yes
Pass sync: Yes Connection Channels: 256
Loop clock: No Gateway Channels: 200
Statistical Reserve: 600 cps Traffic:V,TS,NTS,FR,FST,CBR,N&RVBR,ABR
Header Type: NNI IMA Protocol Option: Disabled
VPI Address: 1 IMA Max. Diff. Dly: 200 msec.
Routing Cost: 10 IMA Clock Mode: CTC
Idle code: 54 hex Deroute delay time: 0 seconds
Restrict PCC traffic: No VC Shaping: No
Link type: Terrestrial VPC Conns disabled: No
Last Command: dsptrkcnf 9.4
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:14 GMT
TRK 9.4 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - rt-VBR (D) [ 20] 19 Tx Max Age - rt-VBR (D) [ 20]
3 Rx EFCN - BdataB (D) [ 20] 20 Tx EFCN - BdataB (%) [ 20]
4 Gateway Efficiency (D) [ N/A]
5 EFCN - Rx Space (D) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP/EPD- Rx_Space (%) [ N/A] 21 BDataA [ N/A] 23 BDataA [ N/A]
7 High CLP - Rx_Space (%) [ N/A] 22 BDataB [ N/A] 24 BDataB [ N/A]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
8 BDataA [ 80] 10 BDataA [ 60] 25 BDataA [ 80] 27 BDataA [ 60]
9 BDataB [ 80] 11 BdataB [ 60] 26 BDataB [ 80] 28 BDataB [ 60]
Receive Queue Depth (D) Transmit Queue Depth (D)
12 rt-VBR [ 27] 15 BDataA [10000] 29 rt-VBR [ 26] 32 BDataA [10000]
13 Non TS [ 37] 16 BDataB [10000] 30 Non TS [ 36] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
This Command: cnftrkparm 9.4
node TN StrataCom IGX 8420 9.2.41 Aug. 13 2001 17:14 GMT
TRK 9.4 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 nrt-VBR[ 5000] 39 nrt-VBR[ 5000]
37 ABR [20000] 40 ABR [20000] 47 ABR [ 20] 48 ABR [ 20]
Rx High CLP (%) Rx Low CLP/EPD(%) Tx High CLP (%) Tx Low CLP/EPD(%)
41 CBR [ 80] 44 CBR [ 60] 49 CBR [ 80] 52 CBR [ 60]
42 nrt-VBR[ 80] 45 nrt-VBR[ 60] 50 nrt-VBR[ 80] 53 nrt-VBR[ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 9.4
Appendix A: BXM Firmware MFW Release Notes
This section contains information about the BXM firmware MFW.
About the Firmware MFW
BXM firmware version MFW supports all existing interfaces and models of BXM hardware. The tables in this section outline various levels of hardware revisions supported for BXM firmware version MFW.
Front Cards
Table 39 lists the front cards that support MFW firmware.
Table 39 Front Cards Supported by MFW Firmware
Model Number
|
Description
|
FW model
|
HW Rev
|
FW Rev
|
BXM-155-4
|
4 port OC3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-155-8
|
8 port OC3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-622
|
1 port OC12 Line Module (Front Card)
|
F
|
D
|
MFW
|
BXM-622-2
|
2 port OC12 Line Module (Front Card)
|
F
|
D
|
MFW
|
BXM-T3-8
|
8 port T3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-T3-12
|
12 port T3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-E3-8
|
8 port E3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-E3-12
|
12 port E3 Line Module (Front Card)
|
F
|
B
|
MFW
|
BXM-155-8DX
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-8D
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-4DX
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-4D
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-2DX
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-2D
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-DX
|
1 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-T3-12EX
|
12 port T3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-T3-12E
|
12 port T3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-T3-8E
|
8 port T3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-E3-12EX
|
12 port E3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-E3-12E
|
12 port E3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-E3-8E
|
8 port E3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
Front Card for APS Compatibility
Table 40 lists the front cards that support APS with MFW firmware.
Table 40 Front Cards Supporting APS with MFW Firmware
Model Number
|
Description
|
FW model
|
HW Rev
|
FW Rev
|
BXM-155-4
|
4 port OC3 Line Module (Front Card)
|
F
|
C
|
MFW
|
BXM-155-8
|
8 port OC3 Line Module (Front Card)
|
F
|
C
|
MFW
|
BXM-622
|
1 port OC12 Line Module (Front Card)
|
F
|
E
|
MFW
|
BXM-622-2
|
2 port OC12 Line Module (Front Card)
|
F
|
E
|
MFW
|
BXM-155-8DX
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-8D
|
8 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-4DX
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-155-4D
|
4 port OC3 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-2DX
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-2D
|
2 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
BXM-622-DX
|
1 port OC12 Line Module (Front Card)
|
F
|
A0
|
MFW
|
Back Cards
Table 41 lists the back cards that are supported by MFW firmware.
Table 41 Back Cards Supported by MFW Firmware
Model Number
|
Description
|
HW Rev
|
FW Rev
|
MMF-155-4
|
4 port multi-mode fiber back card
|
A
|
na
|
MMF-155-8
|
8 port multi-mode fiber back card
|
A
|
na
|
SMF-155-4
|
4 port single-mode fiber intermediate-reach back card
|
A
|
na
|
SMF-155-8
|
8 port single-mode fiber intermediate-reach back card
|
A
|
na
|
SMFMR-155-4
|
4 port single-mode fiber long-reach back card
|
A
|
na
|
SMFMR-155-8
|
4 port single-mode fiber long-reach back card
|
A
|
na
|
SMF-622
|
1 port intermediate-reach OC12 back card
|
A
|
na
|
SMF-622-2
|
2 port intermediate-reach OC12 back card
|
A
|
na
|
SMFMR-622
|
1 port long-reach OC12 back card
|
A
|
na
|
SMFMR-622-2
|
2 port long-reach OC12 back card
|
A
|
na
|
XLR-622
|
1 port extra long-reach OC12 back card
|
A
|
na
|
XLR-622-2
|
2 port extra long-reach OC12 back card
|
A
|
na
|
BPX-T3/E3-12
|
12 port T3/E3 back card
|
A
|
na
|
BPX-T3/E3-8
|
8 port T3/E3 back card
|
A
|
na
|
RDNT-LR-622-2
|
2 port long-reach OC12 redundant back card
|
A
|
na
|
RDNT-SM-622-2
|
2 port intermediate reach OC12 redundant back cards
|
A
|
na
|
RDNT-SM-622
|
1 port intermediate reach OC12 redundant back cards
|
A
|
na
|
RDNT-LR-155-8
|
8 port long-reach OC3 redundant back cards
|
A
|
na
|
RDNT-SM-155-4
|
4 port intermediate-reach OC3 redundant back cards
|
A
|
na
|
RDNT-SM-155-8
|
8 port intermediate-reach OC3 redundant back cards
|
A
|
na
|
New Features supported in BXM Firmware MFW
Bug fixes only.
New Features supported in BXM Firmware MFV
VC merge support added.
New Features supported in BXM Firmware MFU
•Virtual trunk oversubscription.
•VC shaping.
New Features Supported in BXM Firmware MFT
Bug fix only. This image includes a fix for the bug CSCdw54957.
New Features Supported in BXM Firmware MFR
Bug fix only.
New Features Supported in BXM Firmware MFP
Configurable number of ILMI traps.
New Features Supported in BXM Firmware MFN
•F4-F5 Mapping on ports and F4 AIS detection on virtual trunks.
•Support for E2E tstpingoam.
•Support for O.151 OAM standard.
New Features Supported in BXM Firmware MFM
Bug fix only.
New Features Supported in BXM Firmware MFK
LCN CAC with policing parameters set by PNNI controller. (See Notes, Cautions, and Clarifications).
New Features Supported in BXM Firmware MFJ
Bug fix only.
New Features Supported in BXM Firmware MFH
•Dynamic partitioning feature is supported on BXM card by default. Remote shell feature through the BCC CLI provides a mechanism to turn off this feature.
•SPVC feeder support.
New Features Supported in BXM Firmware MFF
Use of separate qbin to guarantee bandwidth resources for the control channels of VSI controllers.
New Features Supported in BXM Firmware MFE
Bug fix only.
Note Support for APS 1:1 added for VSI.
New Features Supported in BXM Firmware MFD
Bug fix only.
New Features Supported in BXM Firmware MFC
•Support for SES (PNNI controller).
•BootCore enhancement to support multi-vendor flash-SIMMs.
•A 1 msec granularity for tstdelay measurement.
New Features Supported in BXM Firmware MFB
•Multiple VSI (2.2) partition feature. Three partitions are supported.
•Hitless connection density upgrade for BXM.
•SCR and PCR policing at less than 50 CPS for T3/E3 BXMs.
•Control traffic shaping.
New Features Supported in BXM Firmware MFA
Multiple VSI (2.2) partition feature. (two partitions)
Note First release in MF branch of firmware.
New Features Supported in BXM Firmware MEC
There is no new feature in release MEC.
New Features Supported in BXM Firmware MEB
There is no new feature in release MEB.
New Features Supported in BXM Firmware MEA
•VSI version 2.2 (single partition).
•ITUT Annex B and configurable signal degrade (SD) and signal failure (SF) thresholds for SONET linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).
The current default thresholds are
BIP count
|
Condition
|
10-4
|
SF detected
|
10-5
|
SD detected & SF clear
|
10-6
|
SD clear & SF clear
|
New Features Supported in BXM Firmware MDA
•Virtual trunking.
•BXM multi-level channel statistics.
•SONET linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).
•Card based LMI and ILMI.
•Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. See Special Installation/Upgrade Requirements.
Special Installation/Upgrade Requirements
This section contains additional installation and upgrade requirements.
APS Issues
Upgrading from MEK and lower firmware to MFW when feeder trunks are utilized with APS while the BPX node does not have APS requires the following procedure:
Step 1 Change the MGX Release 1 feeder to use APS1+1 unidirectional AND disable K1K2 processing (may need to delete and then add back APS). On the BPX temporarily configure to use unidirectional mode.
Step 2 After MGX Release 1 dspapsln shows both lines OK, delete the APS line on the BPX.
Step 3 Proceed to upgrade the BXM cards as if YRED.
Step 4 After both cards are MFW, add back the APS on the BPX.
Step 5 Reconfigure both MGX Release 1 and BPX to use the appropriate APS configurations.
BXM cards with MCB/MDA firmware or later can be smoothly migrated to the MFA or above version of firmware by using Y-cable redundancy.
To upgrade a BXM card pair in Y-red configuration, complete the following steps:
Step 1 Upgrade the standby card with the MFA or above firmware version. Wait for all of the configuration to be downloaded into the card.
Step 2 Do a switchyred to switch to the card with firmware MFA or above version.
Step 3 Burn the other card with the desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.
Step 4 If BCC SWSW version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Stats, go directly to MFC or above versions from MCC.
For APS (1+1) MEx or MFA image versions are not to be treated as compatible with MFx (minus MFA) image versions. During an upgrade procedure from MEx or MFA image to MFx (minus MFA) image, both cards must be upgraded to the MFx (minus MFA) image with minimal interval between them.
The incompatibility is due to APS intercard messages from one end not being recognized by the other end. See bug CSCdu67053 for the symptoms caused by this incompatibility.
Intra-MFx (minus MFA) and intra-MEx upgrades are compatible.
Channel Statistics Issues
While upgrading from firmware, on OC3, 1 port OC12 BXM cards, if stats level on BXM is greater than 1, use one of the following upgrade procedures listed below.
Upgrade from firmware revision MEA or higher.
Step 1 Upgrade SWSW to 9.2.30 or higher.
Step 2 Upgrade the firmware to MFW.
Upgrade from firmware revision lower than MEA. This procedure avoids card mismatch.
Step 1 Upgrade firmware to MEC.
Step 2 Upgrade the SWSW to 9.2.30 or higher revision.
Step 3 Upgrade the firmware to MFW.
A firmware burn must not be interrupted. A card reset in the middle of burn firmware results in the BXM being maintained in the core state (identified by blinking yellow LED) or failed state (identified by a solid red LED). In this case the dspcds screen reports the card as FAILED. This state can be recovered by reburning the firmware into the card.
Features Obsoleted
The following features have been obsoleted:
1. VSI 1.0 is obsoleted by VSI 2.2 in the MDA release onwards.
2. From versions MFJ to MFN channel statistics level 0 is no longer supported for BXM-155-4, BXM-155-8, BXM-622, BXM-622-2, BXM-T3-8, BXM-T3-12, BXM-E3-8, BXM-E3-12 models. In MFN onwards conditional support for stats level 0 is revoked. See the Notes, Cautions, and Clarifications section point 13 for more details.
3. In all other models channel statistics level 0 is supported by all firmware versions (BXM-155-8DX, BXM-155-8D, BXM-155-4DX, BXM-155-4D, BXM-622-2DX, BXM-622-2D, BXM-622-DX, BXM-T3-12EX, BXM-T3-12E, BXM-T3-8E, BXM-E3-12EX, BXM-E3-12E, BXM-E3-8E).
Notes, Cautions, and Clarifications
1. BXM Model F firmware is intended for use with 9.3 switch software. BXM Model F firmware may be used to upgrade BXMs during the upgrade process from SWSW Release 9.2 to 9.3. BXM Model F firmware has not been tested for compatibility with SWSW Releases 8.4, 8.5, and 9.1. It is compatible with IOS version 12.05t2 or greater for MPLS.
2. M.F.E is a not on CCO as it is an SES specific release.
3. Protection Switching based on BER on BXM may not comply to standards. The GR-253 and ITU-T G.783 requires that switching be completed within 60 msec from the time the error starts. BXM is unable to detect BER threshold crossing until the next poll, which occurs every 250 msec. Thus, switching time may be up to 250 msec under certain circumstances.
4. In APS 1+1 default configuration, both back card LEDs show green when primary card is active and selection is from PROT line. When primary card is active and it is selecting from PROT, PROT backcard should be green, since it is carrying traffic. WORK backcard should also be green since that is the physical path for the primary (and active) card to pass traffic. Backcard LED green means the backcard is directly or indirectly carrying traffic, and pulling the backcard causes traffic disruption (CSCdm53430).
5. In APS 1+1 default configuration and a manual W->P is on and a switchyred is issued, a manual W->P event is logged. By default, on switchyred the new active card comes up in "clear" state. But in this case since there is a manual W->P on, the APS line switches to PROT and the switching is logged (CSCdm53404).
6. In APS 1+1 default configuration if the selected line is PROT and last user request is clear and a switchyred is issued, line switches to WORK. If the last user request is "clear", full automatic APS switching is in effect with the working line being active by default. When there is no last user switch request to switch to any particular line, the working line becomes active. (CSCdm53420)
7. When APS Annex B is added to local end which has the secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If the secondary card is active, do a switchyred to make the primary card active. Then, add APS Annex B (CSCdm46359).
8. MFK and above versions support LCN CAC for Class of Services. The controller reserves some LCNs for control VC as default. These reserved LCNs cannot be used by any Class of Service in MFT. If all the LCNs for the partition have been used in a version earlier than MFK after the MFT version is updated in the switch, some connections may not be added. These connections try to use LCNs reserved for control VC which is not allowed. Configure more LCNs for the partition to make sure enough LCNs exist for all the connections.
9. The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.
10. APS 1:1 is not supported for VSI in versions before MFE. (Bug CSCdp42996) APS 1:1 should not be configured on ports intended to be used by PNNI or MPLS as after switchover traffic flow is stalled on the protection line for releases before MFE. However, in MFE and above, this problem is fixed.
11. Total bandwidth allocated to all VSI partitions on a BXM should not be more that OC12 rate, 1412832 cps. BCC SWSW allows users to configure more than OC12 rate, in which case all the PNNI connection commit requests are NACKed by BXM.
12. In firmware versions prior to MFF signaling bandwidth for an SES controller was not guaranteed. In MFF and above the signaling Qbin feature has been added (with SWSW 9.3.10 and above and SES image 1.0.10 and above) to guarantee signaling bandwidth.
13. Statistics level 0 for legacy BXM cards was obsoleted in Model F releases until MFN. However, in version MFP and above conditional support statistics level 0 for legacy cards is revoked. Statistics level 0 is not supported if VSI configurations exist on the card.
If a card was configured with statistics level 0 with VSI enabled in a previous release of firmware (Model C or E), upgrading to MFP or above revisions causes a mismatch on legacy cards. To avoid impacting VSI operations, reconfigure the card to statistics level 1 or above before upgrading.
Note BXME (enhanced cards) support all statistics levels unconditionally with all valid configurations, models, and releases.
14. Starting with MFP through this release of MFW, changes to the alarm handling have been implemented. Excessive BIP-8 error rates (10-3) which escalate into unavailable seconds (UAS) now report to SWSW as red alarms. Therefore, SWSW fails these connections and initiates trunk rerouting.
Note This feature is not active when APS is configured and enabled. However, an exposure might occur in configurations where APS is not enabled, on alternate trunk routes that do not exist, or on UNI ports. Because this feature is not configurable users who do not want this behavior should not upgrade to MFP through MFW. Instead, Users should wait for a subsequent SWSW BXM FW release in which this feature can be turned on and off (default is off) via CLI.
Known Anomalies
Table 42 lists the known anomalies for the BXM firmware.
Table 42 Known Anomalies in MFW Firmware
Bug ID
|
Description
|
Apply to SES
|
CSCdw16017
|
Symptom: Traffic is only seen on the ingress of the master and slave nodes.
Condition: This problem is triggered by a network condition that causes the VPC to reroute. VPC experiencing this problem have been ABRSTD with VSVD enabled one megabits or larger VPC connections.
Workaround: Uping and downing the connection clears the problem.
|
No
|
CSCdx28781
|
Symptom: When inserting BIP-8 from an ADTECH test set into a OC-3 or OC-12, it is failing all connections and sending an AIS back to the test set. The proper response is only to send a FEBE back to the test set disconnected and reconnected to BXM with MEE.
Condition: Tested with 9.3.4P and MF14 (BETA TB) and results are the same as MFP.
Workaround: Unknown
|
No
|
CSCdx52484
|
Symptom: CBR traffic got dropped on ENNI link on BPX side where there is congestion.
Condition: resetcd of BXM can solve the problem.
Workaround: Unknown.
|
No
|
CSCdx72292
|
Symptom: BPX not allowing SES to cross-commit SPVCs
Conditions: SWSW 9.3.40 and BXM FW MF17 with 12000 SPVCs routed between two BPX/SES nodes only half are routed the rest are NACK'ed.
Workaround: There are two ways to work around:
1. When the sum of the policy parameter (% of the partition minimum bandwidth reserved for each service of class) is reaching 100% (PNNI partition only), provide at least 20 cells of common pool using cnfrsrc command.
For example:
•the max bandwidth of partition 1 is X
•and min bandwidth of partition 1 is Y
•the max bandwidth of partition 2 is W
•and min bandwidth of partition 2 is Z
Make sure that max (X, W, Y+Z) should be greater than Y+Z+20. Here, the total bandwidth allocated to that interface = max (X,W,Y+Z), the common pool for that interface = max (X, W, Y+Z) - (Y + Z).
2. When the common pool resulted from the cnfrsrc is zero, try to reduce the sum of the policy parameter (% of partition minimum bandwidth for each class of service) to less than 100% for PNNI partition.
|
Yes
|
CSCdy16927
|
Symptom: BXM LMI clears Abit alarms on SPVC feeder after switchcc or switchyred.
Conditions: SPVC feeder1 === BPX1/SES1=== BPX2/SES2 === SPVC feeder
**
1. The connection segment in the BPX/SES network is down.
2. The corresponding segment in the SPVC feeder is in Abit alarm.
3. After a switchcc or a BXM switchyred on BPX1, the BXM LMI session at "**" tells SPVC feeder1 to clear the Abit alarm on the segment corresponding to the downed VSI connection in the BPX/SES network.
Workaround: None.
|
Yes
|
Resolved Anomalies in MFW
Table 43 lists the resolved anomalies in MFW firmware.
Table 43 Resolved Anomalies in MFW Firmware
Bug ID
|
Description
|
CSCdw80712
|
Symptom: 1:1 APS allows manual/forced switchapsln P->WLine.
Conditions:
1. 1:1 APS with Bi-Dir configured; remote is AXSM/B.
2. Manual switchaps W->PLine from AXSM/B.
3. Forced switchaps P->WLine from BXM.
Workaround: None.
|
CSCdx45385
|
Symptom: BXM did not update SES with the latest available cos level LCN when there is cnfrsrc LCN resources (LCN) change on this partition (part_min_lcn, part_max_lcn).
Conditions:
1. A PNNI partition has been configured with some connections up. dsppnportrsrc reports the correct available lcn for each cos level.
2. Do cnfrsrc on this partition, to change the min_lcn and max_lcn at partition level. The available lcn at cos level in SES dose not get updated.
Workaround: Add a con or down a con to trigger the update.
|
CSCdx55794
|
Symptom: BXM incorrectly sends back LMI version 4 to IGX AAL5 feeder, while it does not support LMI version 4.
Conditions:
1. IGX AAL5 feeder is added to a BXM feeder trunk in the BPX.
2. IGX feeder LMI is running LMI version 4, and talk to BXM LMI.
Workaround: None.
|
CSCdx56537
|
Symptom: Setting cnftrkparm 9 2500/15000 causes trunk failure.
Conditions: BXM running MFU firmware. Found in lab environment but likely to also be found in a live network if these trunk parm values are used and the trunk passes over another medium such as a TDAX or SDH backbone.
Workaround: Set cnftrkparm 9 2500/10000 which is the default for STM1. Do not use the values 2500/15000 for cnftrkparm 9. Tests have yet to show if this would effect other values but default settings have been confirmed problem free.
|
CSCdx59080
|
Symptom: Customer is performing tests of MFU firmware prior to deployment in live network and has found that when a BXM trunk is configured for loop clock yes at both ends it remains in a "Looped Back" state when the BXM is reset by command "resetcd ? h".
Conditions: BXME trunk needs to be configured for loop clock yes and the BXM card be reset. Tests showed that causing a LOS or resetting the card again would not recover the trunk.
Workaround: Issue cnftrk and change none of the parameters by stepping through them.
|
CSCdy01870
|
Symptom: SIMBA reset card errors logged due to PRFD Pending Errors
Conditions: BXM image MEE and SWSW image 9.3.00
Workaround: None.
|
CSCdy01951
|
Symptom: Unnecessary alarms are triggered when BXM sends slot errors to SWSW.
Conditions: The FW adds all slot errors before sending them to BCC. There are situations when the number of traffic related slot errors will trigger unnecessary alarms on SWSW. These alarms will be suppressed.
Workaround: None.
|
CSCdy05515
|
Symptom: Current BXM firmware only support a few stats counters. In order to enhance customer operation and maintenance capability, a few new stats counters have been added. The detail description about the new created stats and associated CLI cmd and MIB can be found in the latest VSI document. See DDTS case CSCdy05597 (SES and Mibs).
Conditions: All previous FW do not support the new connection stats.
Workaround: Not applicable.
|
CSCdy13987
|
Symptom: Newly added routed SPVC carries counter values of previously deleted SPVC.
Conditions: Delete routed SPVC. Then re-add the SPVC with same VPI/VCI values.
Workaround: Problem is fixed in MFW (MF20).
|
CSCdy75277
|
Symptom: pnport stuck in down state
Conditions: Configure PNNI trunk between SES and MGX 8850 (PXM45) using automation script PROU001.
Workaround: Unknown.
|
Resolved Anomalies in MFV
Table 44 lists the resolved anomalies in MFV firmware.
Table 44 Resolved Anomalies in MFV Firmware
Bug ID
|
Description
|
CSCdr55738
|
Symptom: Switchyred on APS 1+1 trunks is taking longer than 250 msec
Condition: Performed switchyred on APS 1+1 with SWSW 9.3.10 and BXM FW MF17
Workaround: Unknown
|
CSCds20584
|
Symptom: BW change by cnftrk command does not change ER stamping BW.
Condition: When the AR ABR STD connection is programmed and the bw of trunk is changed by the cnftrk command. The changed BW does not take effect.
Workaround: Manually reset the card.
|
CSCdu09831
|
Symptom: APS fails when working backcard (active or standby) is removed from chassis when working front card is active.
Conditions: The working front card has to be the active card when working backcard is removed. This occurs when APS 1+1 ITUT non-revertive bi-directional configuration SWSW 9.2.34BXM fw MFJ.
Workaround: In operational situations always have the protecting front card and protecting backcard as active. Any failures will then switch ok and either backcard can be swapped while protecting front card is active.
|
CSCdv86732
|
Symptom: Incorrect values for Path Unavailable Seconds statistics are displayed under dspplyslnstathist. The displayed counts maybe higher than expected. For example, over a 900 second period, 910 Path UAS counts may be displayed.
While Path UAS stats are referred to specifically, other duration statistic counts could be affected as well.
Conditions: The problem occurs under the following conditions:
•BXM line or trunk
•The line or trunk is in major alarm (e.g. LOS, AIS, YEL)
•Statistics are collected on the line or trunk to report the duration of the alarm condition (e.g. UAS).
•The automatic trunk/line loopback test is disabled using the cnffunc command.
Workaround: None
|
CSCdw06552
|
Symptom: Conns should stop passing traffic when dnpnport on UNI port on SES.
Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node.
Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX 8850 (PXM45) node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic.
When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells.
Workaround: Unknown.
|
CSCdw21798
|
Symptoms: Forced switchapsln when secondary section has failed is accepted.
Condition: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1.
Workaround: Unknown
|
CSCdw51601
|
Symptom: dspportstats on BXM shows Rx as Zero even the port has traffic passes in both directions.
Condition: Not every single port has this problem. However we found multiple cards in the customer network have this issue. All the problem ports are T3 ports.
Workaround: None
|
CSCdw81944
|
Symptom: APS switch options 4,5,6 should not be allowed on AnnexB protocol.
Conditions: Upon switchapsln options 4, 5, 6.
Workaround: Unknown
|
CSCdw83849
|
Symptom: APS 1+1 configured between AXSM/B and BXM running ITU-AnnexB protocol:
APS Lockout request (on BXM) doesn't keep selector position.
Conditions: APS Setup: MGX8850 (AXSM/B) ----> BPX (BXM)
APS 1+1, AnnexB Trigger:
1. On AXSM/B, apply APS force switch from Working section 1 (WS1) to WS2
2. On BXM, apply lockout request, selector switches to WS1 which is incorrect. Lockout should indeed freeze selector position to WS2 in this scenario.
Workaround: Unknown
|
CSCdw94327
|
Symptom: With 1:1 configuration; either WL or PL in LOS, BPX always sends RDI-P to AXSM/B.
Conditions:
1. Configured Intra 1:1 APS.
Forced switchaps W->PLine for both APS lines. Active on Plines.
2. Removed the WL-Rx from remote ends.
Active stayed on PLines, both lines in Minor alarms. Remote node receives RDI-P on the failed line.
Workaround: Unknown
|
CSCdx05529
|
Symptom: Removing cable on protection line followed by switchyred card on remote node cause remote Yel major alarm on the trunk.
Conditions: It only happened with ITUT protocol with APS 1+1 mode
Workaround: Unknown
|
CSCdx29896
|
Symptom: VrmRetLcnResources CD error logged on BXM
Conditions: Run AutoRoute/MPLS/PNNI on BPX network. Three partitions (2 MPLS, 1 PNNI) are on an interface with a VC Merge Parent connection
Workaround: Unknown
|
CSCdx32780
|
Symptom: Card went to Failed state during normal operation with card error "rt_task.c 1258 Task low on real time, SRCID = 4"
Conditions: SWSW 9.3.36 SPVC connections. BXM FW MFU
Workaround: Unknown
|
CSCdx49312
|
Symptom: SES cannot add PVC with PCR = linerate
Condition: With old ses image and BXM image ses doesn't allow to add connection and cli will reject.
Workaround: Use BXM MFV and related SES image (1.1.79).
|
CSCdx52531
|
Symptom: APS standby CD to active but no response to BCC after reset active BXM
Conditions: Enable VSI partition for MPLS and with APS configuration on BXM on BPX
Workaround: Manually reset BXM.
|
CSCdx69563
|
Symptom: Continuous 105 and CD errors logged on BXM cause spvc down on SES
Conditions: Configure 100K SPVC on BPX with SES
Workaround: Unknown
|
CSCdx73291
|
Symptom: Fatal card error happened on BXM card in slot 9 after doing a full hitless rebuild on node. The card error should be a Non Fatal card error.
Conditions: A full hitless node rebuild was done on a node with many connections. This problem is related to a temporary HDLC queue overflow and should not be a fatal error.
Workaround: Unknown
|
CSCin03340
|
Symptom: BXM sends ILMI trap with incorrect number of PVCs
Conditions: The SWSW 9.3.40 feature "configurable number of changes per ILMI trap" needs support from the FW when ILMI is run by the card.
Workaround: Unknown
|
Resolved Anomalies in MFU
Table 45 lists the resolved anomalies in MFU firmware.
Table 45 Resolved Anomalies in MFU Firmware
Bug ID
|
Description
|
CSCdt90381
|
Symptom: A small outage (approx 10 msec) occurs on VPCs terminating/originating on BXM.
Condition: This will occur only during hitless rebuild.
Workaround: None
|
CSCdu21825
|
Symptom: The WINGZ shows the RX Network stat as zero even when data flows through the network.
Conditions: Occurs only on a BPX-SES Network.
Workaround: The data at the CLI shows the correct statistics, For right now the cli data can be used instead of WINGZ. Or Use MFU or later image.
|
CSCdu71237
|
Symptom: BXM card did not automatically switch to standby card
Condition: When Non Fatal Error "0xc000002" occurred on BXM trunk card and the traffic worsened.
Workaround: None
|
CSCdv31049
|
Symptom: BXM sets K1 Tx to Force Switch instead of Reverse Request even though remote had already been sending a Force Switch. BXM, however, maintains the correct line.
Condition: Remote end already had a Force Switch to Working line in effect, and local BXM receives a user command to do a Force Switch to the Protection line.
Workaround: Clear the BXM Force switch command.
|
CSCdv89925
|
Symptom: ACR is only 10 when VC shaping is enabled for UBR con
Condition: Trunk VC Shaping feature on BXM card is configured between two nodes. UBR connections are routed between the nodes.
Workaround: None
|
CSCdv77996
|
Symptom: dspapsln reports wrong info w.r.t. aps when one of the yred cards is out.
Conditions: This bug fix is available in firmware release MFR, but swsw bug fix should be there in order to have the complete solution.
SWSW bug: CSCdw35862 9.3.30 MJ01
Further Problem Description: When one card of aps pair is removed, then reset dspapsln shows lines as ok. Should show card failed or missing.
|
CSCdw06552
|
Symptom: Conns should stop passing traffic when dnpnport on UNI port on SES.
Conditions: There were some SPVC connections including double-ended and single-ended SPVC connections between SES and MGX 8850 (PXM45) node. Both UNI ports were connected to Adtech tester. Executed dnpnport on UNI port on SES, all the connections went to AIS state on MGX Release 2 node. Started passing traffic on all those connections, the AIS state was cleared on all the connections, though AIS was still sent out from SES side, but the other end could not distinguish OAM cells from the data traffic.
When pnport is down, the connection on that interface should be programmed to set Inhibit Rx Data or send AIS out the UNI port, and stop passing traffic into the network, so that the other end can interpret OAM cells.
Workaround: None
Note This is a partial fix and relies on a SES DDTS CSCdv48496 for resolution.
|
CSCdw21798
|
Symptoms: Forced switch when secondary section has failed is accepted.
Condition: APS AnnexB between MGX 8850 (PXM45) and BPX (OC12), remove Tx and Rx cables on working section 1.
Work around: None
|
CSCdw25074
|
Symptom: When inserting 1E-03 errors into the whole frame of STM-4 trunk 3.1 (errors inserted in the direction A to B) BPX A becomes unreachable i.e. cannot telnet to BPX A. VT to A from another BPX times out and there's an HPOV event stating that the link is down to A.
The other nodes in the network remain reachable. BPX node log shows that the BCC has a suspected failure (Which indicates corruption of the BCC self test)a few minutes after inserting the errors into the trunk at B.
Removing the errors from the trunk results in BPX becoming reachable. Same problem seen with the other BCC active. This is consistently reproducible. If reroutes on another trunk (e.g. trk 1.1) are taking place when the errors are being inserted into trk 3.1, the connections (which are pref 'd' onto trk 1.1) remain derouted until the errors are removed from trk 3.1.
Conditions: Errors inserted at 10 -3 in one direction from A to B cause A to go unreachable. Found in lab environment running 9.2.38 with MFN firmware on 155 and 622 optical card types.
Workaround: DNTRK to force a reroute.
|
CSCdw53395
|
Symptoms: Traffic disrupted in the via node. No ais is propagated to other master end if slave end port is down.
Conditions: mostly when MGX 8850 (PXM45) is connected to SES.
Workaround: None
|
CSCdw54957
|
Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX45
Conditions: 9.3.3i MFR
Workaround:
Further Problem Description: When there is a congestion on MGX egress port, MGX 8850 (PXM45) sets EFCI=1 for all SPVCs/xpvcs on that port to the downstream.
|
CSCdw62999
|
Symptom: BPX sends a wrong value for K1
Condition: APS interop testing between BPX and AXSM/B OC-3.
Workaround: None
|
CSCdw63238
|
Symptom: BXM sends RDI trap to SES which does a dnpnport
Conditions: Config is bxm uni with aps 1+1, SW 9.3.35, FW MFR, SES SW 1.1.71.
Workaround: None
|
CSCdw75999
|
Symptom: Dspconstats on an SES CLI for an SPVC connection shows that clp0 discards and clp1 discard counts are interchanged.
Conditions: SES 1.0(14), BXM FW MFR
Discards due to the policing action are reported incorrectly in dspconstats cmd. Discards due to congestion are reported correctly.
Workaround: None
Update BXM FW to MFU or later.
|
CSCdw88723
|
Symptom: Say BXM1 is a BME card. BXM2 is normal BXM card running fw image MFC-MFT. Multicast root connection runs from BXM2 to BXM1 and fans out to other connections at BXM1 port 2. We will see high number of ingress cell discards on the root connection at BXM2.
Condition: BXM2 running f/w image between MFC to MFT
Workaround: None. Use firmware image MFU or later on BXM2.
|
Resolved Anomalies in MFT
Table 46 lists the resolved anomalies in MFT firmware.
Table 46 Resolved Anomalies in MFT Firmware
Bug ID
|
Description
|
CSCdw54957
|
Symptom: ENNI change EFCI to 0 when receive EFCI =1 from MGX45.
Conditions: SWSW: 9.3.3i, BXM FW: MFR
When there is a congestion on MGX egress port, MGX45 sets EFCI=1 for all SPVC's/xpvc's on that port to the downstream.
Workaround: None
|
Resolved Anomalies in MFR
Table 47 lists the resolved anomalies in MFR firmware.
Table 47 Resolved Anomalies in MFR Firmware
Bug ID
|
Description
|
CSCdv90721
|
Symptom: The prevalent symptom is Tx BIP 16 and B-Frame Parity slot errors on BXM-622 or BXM-155 cards. Occasional SIU Phase and Rx BIP 16 errors may also occur on BXM-622 and BXM-155 cards depending on the severity of the problem.
Conditions: Can occur with any version of BXM firmware on BXM-622 or BXM-155 cards. The aggregate cell transfer rate of the BXM card is 1,412,832 cells/second so the problem can occur on BXM-622 or BXM-155 cards even if the load on each line is well below line rate. The problem occurs during oversubscription when multiple high speed cards have traffic destined for a particular card through the switching fabric.
Workaround: To solve the BCC-4 software error 742 problem upgrade switch software to 9.1.22, 9.2.31, 9.3.00 or later.
|
CSCdw16362
|
Symptom: The BXM card changed the state from active to empty for a particular slot and failed to communicate with the BCC.
Condition: Switch software was upgraded for the particular BXM and statistics were enabled before the current state. Now the particular slot is in empty state although both front and back cards are present for the slot.
This loop happened because of spvc statistics task. It happens when new spvc_config_stats command comes in the vsi message with more than currently configured stat ids. Due to this the data base will be updated. During this update some flag was not set properly and it leads to a loop.
Workaround: Not known other than the physical removal of the card. Or, use MFR or later images.
|
CSCdm50659
|
Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms.
Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable.
Workaround: Lowering the alarm threshold for MAJOR and MINORHCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR.
These thresholds are as low as they can be set currently.
|
CSCdt82384
|
Symptom: APS trunk built on bxm-155-4d. sf and sd thresholds set to 5 and UNI-direction non-revertive switching with cnfapsln.
Random logic errors inserted into the working pair of the trunk to observe protection switch at sf threshold.
Good switch at 1 in 103 and 105 but when 1 in 104 inserted trunk goes unstable repeatedly switching from working to protection and vice versa.
Trunk continues to toggle until errors removed.
Conditions: BXM-155 enhanced cards using APS card cage and injecting 10^4 error rate into one of the working lines.
Workaround:
|
Resolved Anomalies in MFP
Table 48 lists the resolved anomalies in MFP firmware.
Table 48 Resolved Anomalies in MFP Firmware
Bug ID
|
Description
|
CSCds47753
|
Symptoms: Card error will happen in standby "VrmDekConnEndPoint Try to delete".
Condition: When standby syncs up with active, it tries to delete a not existing connection.
Workaround: The card error indicates that there is a invalid try of deleting a non-existing connection. It should not create any problem in existing or new connection.
|
CSCds75845
|
Symptom: There is no ER stamping cell generated from BPX in SES environment. Although, CI is set to be off and ER is on by using cnfabrparam, CI cells are still observed where there is congestion.
Condition: When the connection is routed by PNNI (created by using SES controller.)
Workaround: No workaround
|
CSCdt55356
|
Symptom: After configured status of all nni links to dwon at SES node svcpop2, then configured all links up. while the 100k SPVC connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by itself.
Condition: MGX nodes p2spvc4 and p2spvc3(via node) both have standalone PXM45-B card.
Initially 100K spvc connections have been established between p2spvc4 and SES node svcpop2 end points.
Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.
|
CSCdu21842
|
Symptom: ILMI does not report correct status of the ATM PVCs when Protocol by card is enabled.
Conditions: When a BPX is connected to a router through a BXM card and ILMI Protocol is run by the card.
Workaround: None.
|
CSCdu04976
|
Symptom: Around 200 SPVCs stuck in Rx ais after resetting BCC.
Conditions: Resetting the BCC during resync with a SES controller causes this problem as the AIS bit-map is cleared.
PXM: 1.1(50.100)A1
BXM: MF15
SWSW: 9.3.3E
Workaround: Unknown
|
CSCdu29758
|
Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value.
Conditions: The first couple of loopback cells received have incorrect VCI values.
BXM=MFJ, BPX 9.2.31
BXMa-BPX==BPX-BXMb<-> ADTECH (OAM F4Loopback)
Workaround: None
|
CSCdu63175
|
Symptom: LOF and Bert_SD alarm uncleared on BXM
Conditions: 1+1 aps with bi-dir on BPX and MGX
Workaround: switchcdred/switchyred on BXM
|
CSCdu89263
|
Symptom: When running XLMI on a BXM port which is connected to an AXSM enni port, BXM XLMI sending slot 0 and incorrect port number in the node status msg.BXM XLMI is configured with polling disabled.
Condition: Running XLMI and disable the polling.
Workaround: Enable the polling, then disable it.
|
CSCdv18519
|
Symptom: In reading MF* BXM MFM fw release notes, it was discovered the Stats collection level 0 is no longer supported in MFM and beyond. Ie, Stats level 0 supports 32k cons stats level 1 16k cons.
Condition: 9.3.3V
MF21
Workaround: See MFM release notes Stat level 0 no longer supported on Legacy BXM cards.
|
CSCdv21924
|
Symptom: By running XLMI, when the NodeStatus message didn't get ack back, it would retry every T396 (polling timer), instead of using the correct T393 timer.
Condition: When XLMI is configured and link/line is down. XLMI NodeStatus retry mechanism kicks in. But a wrong timer T396 was used for retrying interval.
Work around: It won't cause any service interrupting or deteriorating and it won't show up under normal operating condition. If a specific NodeStatus retry interval is really needed, one can configure T396 to that value temporarily before the fix is in.
|
CSCdv21999
|
Symptom: BXM sends a port failure VSI msg to the controller after switchyred.
Conditions: Under yred configuration, and running LMI on PNNI port on this card. Switchyred so the standby card become active and the port on standby card from failure state to OK.
Workaround: None
|
CSCdv32466
|
Symptom: A enni port is still showing as failed after switchyred when it becomes OK.
Conditions: Yred and APS 1+1 are configured. XLMI is runng on the enni port. On the previous active card, the port was in a fail state. When the failure got recovered very quick during the switchyred, BXM missed the OK report to BCC, so BCC still shows this port as fail state.
SW and FW version: 9.3.30 MF25
Workaround: None
|
CSCdv43448
|
Symptom: The command dsppnports shows the port in "LostConnectivity" state.
Condition: Disable ilmi on bpx using cnfvsiif
Work Around: Reset the card. This problem happens only in MFN due to the chkin done in Aug 13 2001. Or use Firmware image newer than MFN.
|
CSCdv52437
|
Symptom: Comm Failure after Working line experiences "Remote Yellow"
Conditions: APS 1+1 bidirectional mode GR-253 and ITU After remote experiences LOS on Protection line, the local active Working line will have a Remote Yellow alarm. This alarm eventually causes a Communications failure, and traffic will be rerouted.
Workaround: Use unidirectional mode
|
CSCdv57400
|
Symptom: Customer removes commands under ATM interface or tears vc down and up again the router will send two traps to the BXM VSI port but only looks like it is re-acting to the first trap hence the remote router will receive AIS and then transmit RDI. The connection will never come out of this state unless the remote end from the SES is bounced.
Conditions: Must be attached to a PNNI VSI port on the BXM.
Workaround:
1. Switch ILMI off on the port.
2. Disable oam-manage on the routers.
|
CSCdv58157
|
Symptom: On BXM switchover, the VSI abr VP falls to MCR.
Condition: BXM FW up to MFN (MF30). Standby BXM should collect this VP abr connection during initial data transfer phase. ie. Standby BXM is inserted later than active card or is reset after connection provisioning. Check with 'rsh slot# sabre GetSabreParams sabre# lcn#' and look for 'Path con' field. Switchover to stdby in this case will cause the problem.
Workaround: Reassert/resync all the connections. Use firmware later than MFN.
|
CSCdv62493
|
Symptom: BXM does not send Node status counters to BCC
Conditions: XLMI is running on card
Workaround: None. This is an enhancement.
|
CSCdv66806
|
Symptom: Dax conn does not get rerouted if added when slave interface is down; and later when slave interface is brought back up.
Condition: This is applicable only for dax conns on SES - not on MGX2.
Workaround: Delete and re-add the dax conn when the slave interface is up - it will get routed.
|
CSCdv86166
|
Symptom: A feeder trk shows UNREACHABLE after switchyred, while it was actually uprunning without any communication problem.
Condition: When running FDR-LMI in a yred pair, the FDR trunk was in a fail state. After switchyred, the FDR trunk changed its state to be OK, however, dspnode still shows this fdr trk was in the UNREASHABLE state.
Workaround: No service impact, though the fdr trk shows as unreachable. To get the correct state, reset the card.
|
Resolved Anomalies in MFN
Table 49 lists the resolved anomalies in MFN firmware.
Table 49 Resolved Anomalies in MFN Firmware
Bug ID
|
Description
|
CSCds08461
|
Symptoms: Incorrect operations (SF_LOW sent) after detecting mode mismatch
Conditions: BXM configured as APS 1+1 Bidirectional mode, and is attached to a node configured as 1+1 Unidirectional.
Workaround: Manual administrative intervention to synchronize both nodes to the appropriate mode.
|
CSCds53524
|
Symptom: SWLOG error 109 on BPX
Conditions: SWSW 9.3.10, Cards: BXM 155
While adding connections between BPX nodes found a swlog 109
Workaround: Under Investigation
|
CSCds78285
|
Symptom: Connections in failed or BuildingVC state.
Conditions: CAC policy was not downloaded to some of the BXMs.
Workaround: None
|
CSCds91102
|
Symptom: BXM card interfaces went into provisioning state
Conditions: BXM card was reset and pxm did a resync
Workaround: None
|
CSCdt35547
|
Symptom: Cell drops at a cbr connection when a cbr connection and an abr connection are congested at an enni trunk
Conditions: When congestion exists at an enni trunk in a AR/PNNI hybrid network.
Workaround: No workaround
|
CSCdt38471
|
Symptoms: The available BXM TCB buffer went down to zero and the card got stuck.
Conditions: This happened in the 100k SPVC devtest setup. The problem can be reproduced by performing switchyred on two BXM redundancy cards.
Workaround: The reasons to cause TCB buffer leakage were found. Furthermore, the holes in the firmware code have been sealed. The fix will be included in the firmware releases MFM or later.
|
CSCdt41728
|
Symptoms: Card error VrmRetLcnResources was observed
Conditions: This bug is reproduced in 100K network when port 1.2 of orses7, which is connected to adtech is seeing temporary LOS. This happened when Adtech is power cycling. Also 1.2 is the end point of 6666 routed SPVCs.
Workaround: No workaround
|
CSCdt53756
|
Symptom: SES had huge CDV value compared to MGX 8850 R2.
Conditions: Always occurs
Workaround: None
|
CSCdt55356
|
Symptom: After configured status of all nni links to dwon at SES node svcpop2, then configured all links up. while the 100k spvc connections are derouting and rerouting. at bxm, slot 11, 12, 13 and 14 are reset by itself.
Conditions: MGX nodes p2spvc4 and p2spvc3(via node) both have standalone PXM45-B card. Initially 100K spvc connections have been established between p2spvc4 and SES node svcpop2 end points.
Workaround: It was found that a deadlock in the firmware code (SC_task and device's driver). In order to solve the problem, mutual-exclusion semaphore is selected for QE, SABRE, SIMBA and RCMP instead of binary semaphore.
|
CSCdt68427
|
Symptom: After dellp is done traffic isn't right when VP connection and cnfln VC shaping enable.
Conditions: A dellp was done on a VP with VC shaping enabled.
Workaround: None
|
CSCdu08104
|
Symptom: AR connections don't pass traffic or some links be in comm fail condition.
Conditions: The intermediate devtest release for VC-merge project had a problem. On downloading this image would some time bring down the trunk.
Workarounds: There are no known workarounds.
|
CSCdu12049
|
Symptom: BXM Card switches on Nortel exercising to test APS Link. This happens everytime test is completed.
Conditions: BXM card is not reacting to K1 bits correctly.
Workaround: There are no known workarounds.
|
CSCdu20728
|
Symptom: One end of the trunk experiences unbalanced Rx/Tx high priority cells in dspqbinstats. Any CBR traffic on the trunk will not be seen in the CBR QBIN stats.
Conditions: Unknown
Workaround: None yet.
|
CSCdu22039
|
Symptom: F4 F5 Code mapping modifications
Conditions: None
Workaround: None
|
CSCdu23725
|
Symptom: Attempt to configure the booking factor on a UNI port failed. Err msg: "ERROR: Switch Response returned Failure".
Conditions: The conditions for the error is unknown since the CAC feature on the UNI port hasn't been studied before and there were many activities such as addcon, cable failure prior the problem detected.
Workaround: Unknown
|
CSCdu26023
|
Symptom: When PNNI&MPLS partitions are configured in a interface with no common pool of bandwidth, only one of the partition will be working fine and the other partition will not come up.
Conditions: When PNNI&MPLS is configured in a interface with no common pool of bandwidth, due to the rounding up of the bandwidth for each service type in PNNI by policy parameters, the total bandwidth of a partition, resulted from adding bandwidths of all service types, will go beyond the max bandwidth of both partitions. Because of this, only the first partition will succeed and the other partition will be rejected by cac.
Workaround: Provide at least 20 cells of common pool using cnfrsrc command.
|
CSCdu29758
|
Symptom: After power cycle BXM card send the OAM F4 Segment loopback from ADTECH test equipment to BXM received a different VCI value.
Conditions: BXM=MFJ, BPX 9.2.31
Setup BXMa-BPX==BPX-BXMb<-> ADTECH (OAM F4Loopback)
Workaround: None
|
CSCdu44350
|
Symptom: Although equipment is NOT connected to PROT Line, Standby Line Alarm Status is OK on dspapsln. This symptom appears when CDERR is logged at timing of addapsln.
Conditions: Standby line is not connected to equipment.
Workaround: None
|
CSCdu48766
|
Symptom: VI programming on enhanced cards is improper.
Conditions: Virtual Trunks were Dropping all cells
Workaround: None
|
CSCdu50129
|
Symptom: While cwm coldstart then down two links with 32K connections at orses2 nodes. cwm can not sync up with orses2 node any more and stuck in mode 2.
Condition: There are 50K spvc dax connections at node orses2.
Workaround: CWM needs to coldstart again.
|
CSCdu59151
|
Symptoms: APS commands switchapsln F/M on PXM fails.
Condition: BXM running devtest image MF20 with APS configured as ITU-T Annex A and the remote node is any box that strictly adheres to G.783 Annex A, specifically regarding not sending "mode" bits.
Workaround: Don't use devtest image MF20 for ITUT Annex A.
|
CSCdu59240
|
Symptom: Alarms on 1:1 APS BPX side uncleared after 1:1 aps back to Bi-dir on MGX side
Conditions: 1:1 aps with bi-dir on BPX and 1:1 aps with uni-dir on MGX
Workaround: Unknown.
|
CSCdu62336
|
Symptom: Code clean-up
Conditions: None
Workaround: Unknown.
|
CSCdu67053
|
Symptom: When BXM OC-3 card was downgraded from M.F.21 to M.E.K continuous card errors were being logged.
Condition: M.E.K. FW was burned on the standby card that was configured for Y-Red and had APS 1+1 lines configured with traffic.
Workaround: Use matching firmware versions on YRED pair.
|
CSCdu75130
|
Symptom: Active card in the y-red pair continuously Making the connections.
Resource usage in active and standby card differs.
Conditions:
1. Active card up & running
2. Intracard connections between two interfaces on the same BXM.
3. Booking factor less that 100% on above interfaces.
4. Stdby card is inserted at this time.
Workaround: Resetting both the active and sdtby cards at the same time.
|
CSCdu82229
|
Symptom: ILMI polling when "Protocol by Card" is configured to "Yes" is inconsistent and unpredictable.
Conditions: When ILMI is running on card and its peer is running version 3.0/3.1, the polling interval timer was set with wrong value, which was the 1/5 of the configured polling interval. For correct behavior, refer to SCM note of this bug.
Workaround: Use OAM instead of ILMI
|
CSCdu87060
|
Symptom: pnport on SES goes into building vc state.
Condition: Change the signalling vpi using cnfpnportsig.
Workaround: Reset the bxm card.
|
CSCdu88418
|
Symptom:
1. After SwSw upgrade from 9.2.34 -> 9.3.3W, BXME OC-12 card with APS 1+1 setup logged swsw err. 105 and card errs.
2. This problem have been observed several times before.
Conditions: This event happened after SWSW upgrade.
Workaround: Need DE input.
|
CSCdv08977
|
Symptom: Unable add PNNI VSI connections on a y-red BXM pair when upgraded from BXM to BXM-E. Standby card not in SYNC with active card. Policy parameters for the first interface/partition on the active card missing.
Condition: BXM FirmWare MFN and before. Any Sw/Sw supporting hot upgrade on BXM. Upgrade procedure is followed to upgrade a y-red pair of BXM from BXM to BXM-E cards. Note that the policy params for the first interface/partition on the active card are messed up. If this interface has booking factor less than 100% then above defect will surface.
Workaround: Resetting both the BXM cards after upgrade. OR -- Use MFN or later BXM FW before upgrade and on enhanced cards.
|
CSCdv17853
|
Symptom: Fix compiler warnings
Condition: None
Workaround: None
|
CSCdv18775
|
Symptom: BXM card err. "ilmi_task.c 323 pIlmiWd: SoItcSend Failed (currsize 500)"
Conditions:
1. This problem occurs after burning BXM FW MF21 -> MJ04
2. It occurs after switchyred
3. It occurs after rerouting of connections
Workaround: Need a fix from BXM FW DEs
|
CSCdv30471
|
Symptoms: Active and Standby card do not sync up in terms on number of connections. VSI yred pair.
Conditions: FW image prior to MFN. When VSI partition 3 is used by controller.
Workaround: Do not use partition 3.
|
CSCdv30755
|
Symptom: Traffic discontinuity on SPVC connections on consecutive switch-yreds on BXMs.
Condition: To begin with BXM with UNI interfaces should have de-routed connections which are later routed properly. This can happen during initial provisioning of the SPVCs or on re-routing the conns after trunks (NNI) go down and up.
Two or more consecutive switchovers on the BXMs hosting UNI interfaces (persistent endpoints of SPVCs).
Workarounds:
1. Reroute/resync all the connections and reset the stdby card once active card has all conns.
2. Do no do BXM switchovers more than once.
3. Reset standby card before doing the first switchover.
|
Resolved Anomalies in MFM
Table 50 lists the resolved anomalies in MFM firmware.
Table 50 Resolved Anomalies in MFM Firmware
Bug ID
|
Description
|
CSCdr16007
|
Symptom: ILMI trap atmfVccChange returns invalid agent-addr (48.48.48.48), while the correct one shall be (0.0.0.0). "ERROR Invalid agent-addr".
Conditions: The error happens during adding or deleting connections.
Workaround: None
|
CSCdr44694
|
Symptom: ILMI trap atmfVccChange returns incomplete information. "variable-bindings (none)".
Conditions: The error happens during adding or deleting connections.
Workaround: None
|
CSCds06835
|
Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk.
Conditions: CC traffic is passed across virtual trunks.
Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.
|
CSCds74110
|
Symptom: The second leaky bucket doesn't adhere to the leaky bucket algorithm.
When testing a VBR connection on a BXM-E3 you can burst over the expected value for the connection.
Conditions: A connection can exceed his calculated burst size for a VBR connection.
Workaround: There is no workaround.
|
CSCds75477
|
Symptom: When a delay of over 200ms is introduced to a trunk with a Addtech tester, 75% of the time the tstdelay result gives a reading lower than the actual RTD. ie we would expect over 400ms but get 150ms.
Conditions: The tstdelay test reports inaccurate results.
Workaround: None
|
CSCdt21547
|
Symptom: There is no command available to clear SPVC statistics on SES controller.
Conditions: SPVC statistics cannot be cleared via SES
Workaround: None
|
CSCdt36060
|
Symptom: The tstdelay command intermittently fails.
Conditions: Tstdelay intermittently failed when BPX is configured as a segment endpoint for VCC and VPC established between a MGX abd BPX
Workaround: None
|
CSCdt43471
|
Symptom:
1. Card errors of "Non Fatal Error id: 0x12000003"
2. Unknown vpi/vci in dsptrkstats and dspportstats
Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs.
Workaround: None
|
CSCdt44670
|
Symptoms: The available BXM TCB buffer went down to zero and the card got stuck.
Conditions: This happened in the 100k SPVC devtest setup. The problem can be reproduced by performing "switchyred" on two BXM redundancy cards.
Workaround: None
|
CSCdt45820
|
Symptom:
1. Card errors of "Non Fatal Error id: 0x12000003"
2. Unknown vpi/vci in dsptrkstats and dspportstats
Conditions: Enhanced BXM cards with 1 port group and supports greater than 32K LCNs.
Workaround: None
|
CSCdt45966
|
Symptom: Resync process starts and SPVC connections are re-asserted on BXM switch over.
Condition: Intra-slave (DACS) SPVC connections are conditioned (AIS/Abit generation) due to external factors.
Workaround: None
|
CSCdt46282
|
Symptom: On SPVC connection CDVT programmed is not observed when testing.
Conditions: When user tries to set up the CDVT value to less than 10ms due to a bug in the firmware BXM uses the value 250ms.
Workaround: Use values above 10ms.
|
CSCdt48062
|
Symptom: Ports remain in "provisioning" state on SES.
Condition: Enabling /disabling the partitions on BXM interfaces (specially on engineering BXM images after MFJ between MF08 to MF12)
Workaround: Do not re-enable the partition after disabling it. BXM need to be reset if re-enabled configuration has to take effect.
|
CSCdt58185
|
Symptom: The CESM-E8 dropped cells after 1/2 hrs. (Seeing the clock synchronization problem.
Conditions: When selecting a clock from the trunk or passing the sync along the trunk. BXM-OC3-D or DX (enhanced) card did not behave properly.
Workaround: Use any other type of BXM card except for the BXM-OC3 enhanced.
|
CSCdt78404
|
Symptom: 70K SPVCs stuck in Rx side AIS after resetsys/switchcc on PXM overnight.
Conditions: SPVCs stuck in AIS state
Workaround: Reset BXM card.
|
CSCdt75817
|
Symptom: Asymmetric ABRSTD connections using VSVD will not ramp up ACR to higher than the lower PCR setting.
Conditions: It happens when an asymmetric ABR connection is added or modified.
Workaround: The problem was identified as incorrect programming SABRE chip and has been fixed in MFM or later FW.
|
CSCdt80542
|
Symptom: BXM does guarantee at least mcr value on abr connection on a congested port.
Condition: Traffic was pumped on a congested port having abr conns.
Workaround: Unknown.
|
CSCdt88482
|
Symptom: The available TX cell rate is lot smaller than available RX cell rate. The available TX cell rate for signalling is a huge negative number
Condition: 100K spvc connections have been established between MGX and BPX nodes.
Workaround: Reset BXM card
|
Resolved Anomalies in MFL
Table 51 lists the resolved anomalies in MFL firmware.
Table 51 Resolved Anomalies in MFL Firmware
Bug ID
|
Description
|
CSCds15145
|
Symptom: Max BW could be configured as less than Min.
Conditions: This might happen as the policy parameter might not be checked for the consistency.
Workaround: Do not configure Max below min.
|
CSCds06835
|
Symptom: Nodes become unreachable if CC traffic traverses to the destination node via a UXM-BXM virtual trunk.
Conditions: CC traffic is passed across virtual trunks.
Workaround: Change the trunk configuration with cnftrk command to restrict CC traffic on virtual trunks.
|
CSCds75221
|
Symptom: When Issuing the command "dspconstats" for abr or ubr connection it does not report the CLP0 and CLP1 correctly.
Conditions: Statistics for abr and ubr not updated.
Workaround: None
|
CSCdt38554
|
Symptom: After executing resetsys on the node(svcpop2) pxm1 cards. there
are two ports stuck in building vc.
Conditions: The node(svcpop2) has 100k routed spvc connections.
Workaround: Unknown
|
CSCdt45966
|
Symptom: Checksum calculation is not correct in BXM.
Conditions: Connection conditioning via bulk set cmd.
Workaround: Uppnport/dnpnport on UNI and NNI port and do switchyred to kick resync.
|
CSCdt48062
|
Symptom: Port gets stuck in building VC state.
Conditions: Connection admission control.
Workaround: Establish connections of various service type and bandwidth requirements.
|
Resolved Anomalies in MFK
Table 52 lists the resolved anomalies in MFK firmware.
Table 52 Resolved Anomalies in MFK Firmware
Bug ID
|
Description
|
CSCdt21322
|
Symptom: BXM load info returned to controller is wrong when maxbw set to 0.
Conditions: Reproducible
Workaround: None.
|
CSCdp16050
|
Symptom: maxvc functionality for CAC not working
Conditions: reproducible
Workaround: None.
|
CSCdt04632
|
Symptoms: For a vsi partition, the reporting available number of LCN is greater than the maximum number of LCN configured for that partition.
Conditions: When the port group unused LCN is less than the maximum LCN configured for the partition and the unused LCN for the port group plus the LCN that still left from the reserved (min-curr) is greater than the max of the partition.
Work around: None.
|
CSCds85653
|
Symptom: BXM card error of "cb_if.c 1588 CbCoreTxEvent(): Failed core_cbmsg_put: return.
Conditions: Continually doing switchcc with large amounts of AR/SPVC connections
Workaround: Reset BXM card
|
CSCds76142
|
Symptom: BXM card shows standby-failed status
Condition: Download firmware on standby card
Workaround: Reset BXM card.
|
CSCds65105
|
Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'.
Conditions: DAX conn from BXM-622 port 1-2 on the same node with ADTECH generate traffic.
Workaround: None
|
CSCdr19696
|
Symptom: User never gets to know when the line is out of SD/SF condition. both the aps lines always show in OK state in dspapsln.
Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition.
Workaround: Use rsh command to get all the aps line's status.
|
Resolved Anomalies in MFJ
Table 53 lists the resolved anomalies in MFJ firmware.
Table 53 Resolved Anomalies in MFJ Firmware
Bug ID
|
Description
|
CSCds61912
|
Symptom: After downloading new firmware(MF30), card in failed state.
Conditions: Downloading MF30 firmware release.
Workaround: Don't use MF30 which is a development release between MFH and MFJ.
|
CSCds11506
|
Symptom: Min guaranteed cell rate shows a cell less than configured.
Conditions: Setting min BW to say 3333334 and policy BW% to 5859
Workaround: Increase the minBW by few cells.
|
CSCdr19696
|
Symptom: User never gets to know when the line is out of SD/SF condition. Both the aps lines always show in OK state in dspapsln.
Conditions: APS Line switches to stby line because of SD/SF condition. dspapsln will still show OK for both the lines. This way, user will never get to know when this line has come out of SD/SF condition.
Workaround: Use rsh command to get all the aps line's status.
|
CSCds32845
|
Symptom: Connection commits rejected with reason 'no resources even when resources are actually available.
Conditions: Enabling/disabling a virtual trunk.
Workaround: Resetting the BXM after disabling a VT on any interface on the card.
|
CSCds37237
|
Symptom: When upgrade BXM firmware image to BXMMFH from images between BXMMFC-BXMMFF, if the network migration flag was enabled in a card before the upgrading, then after burning the new image to the card, the network migration flag becomes disabled mistakenly.
Conditions: The problem only happens to the card whose previous image is BXMMFC-BXMMFF, and the network migration flag was enabled before upgrading, and BXMMFH has to be the new image.
Workaround: Upgrading to image BXMMFH+ (not including BXMMFH), will not have any problem. network migration flag is always enabled, and no user command available any more to disable it.
Only for the situation you need to upgrade image to BXMMFH and your card's previous images is BXMMFC-BXMMFF, you may see the problem. The workaround is, issue either the "rsh <slot> cdcfg network dis" command before the upgrading, or "rsh <slot> cdcfg network ena" after the upgrading, to enable the network migration flag on BXMMFH.
|
CSCds59710
|
Symptom: Loss of traffic on a VPC connection added with VPI=0.
Conditions: SWSW: 9.3.10
BXM FW: MFF
The port on which the VPC connection has been added has a VSI ctrlr attached to it and the Ctrlr is usingVPI=0 and VCI=x for its signalling channel.
Workaround: If a VPC connection exists with VPI=0, on the port to which a Ctrlr is to be added, configure the signallingchannel on the controller side to use a VPI other than 0.
|
CSCds63578
|
Symptom: SW errors 105 logged on BXM while adding VSI connections. Subsequent card errors saying CB_TASK restarted.
Conditions: This error sometimes happen when a VSI partition is enabled/disabled many times.
Workaround: Reset the BXM.
|
CSCds65105
|
Symptom: When pumping the ATM CBR traffic at the rate over = of port line rate (BXM-622), at the egress 'dspchstats' shown the number of cells 'From Network' twice larger than 'To Port'.
Conditions: DAX conn from BXM-622 port 1-2 on the same node with ADTECH generate traffic.
Workaround: None
|
CSCds67854
|
Symptom: SPVC cannot be routed over the virtual trunk even when enough bandwidth and lcn are available. Routed connections discard some traffic.
Conditions: Routing connections of different service types over the virtual trunks.
Workaround: None.
|
CSCds04137
|
Symptom: Channels remain mismatch after lockout is cleared
Conditions: In ITU-T Annex B protocol for APS, when a condition causes a switch to occur while a lockout request is present, the channel change will not resynchronize even after the lockout is cleared.
Workaround: No
|
CSCds53645
|
Symptom: ABR connections (PNNI) not programmed properly for redundant slave.
Conditions: Switchyred. When connection is added, redundant card is not there and inserted at later stage.
When connection is added, no redundant config, addyred at later stage.
Workaround: None
|
Resolved Anomaly in MFH
Table 54 lists the resolved anomaly in MFH firmware.
Table 54 Resolved Anomaly in MFH Firmware
Bug ID
|
Description
|
CSCds14495
|
Symptom: Dynamic Partitioning and SPVC AIS generation would not work on a card until a rsh command is issued to enable the network migration flag and reset the card.
Conditions: When a card comes up and has never enabled the network migration flag for life time.This network migration flag is used for enabling dynamic partitioning and SPVC AIS, status report generations. By default, the flag is disabled.
Workaround: Use the "rsh <slot> cdcfg netmig en/dis" command to enable/disable the flag, then reset the card once in a lifetime.
|
Resolved Anomalies in MFF
Table 55 lists the resolved anomalies in MFF firmware.
Table 55 Resolved Anomalies in MFF Firmware
Bug ID
|
Description
|
CSCds08448
|
Symptom: ERS (explicit rate stamping) is working only first virtual trunk and NOT for subsequent VTs (standard ABR)
Conditions: When ERS is enabled on a card basis using "cnfabrparm", the mapping is done on a port-by-port basis. The port_vi is used but for virtual trunks, this mapping does not hold true. Need to change the mapping to the physical port.
Workaround: On any physical port, just set up one virtual trunks. Or a physical trunk. Multiple VTs on the same physical port will cause a problem.
|
CSCdr79610
|
Symptom: Change booking factor for a class of service, get rejected.
Conditions: When there are some connections established, and some of the class of service have used bandwidth exceeding their reserved, change booking factor for any class of the service may get rejected.
This is because it fails the check which should only be called when cos_min_bw in the policy parameters is changed. This check should not be called when booking factor is changed.
Workaround: Disable that partition, change the booking factor, then enable the partition again. Or keep the used_bw for all cos under teh cos_min_bw, you will be able to change booking factor freely.
|
CSCdr76334
|
Symptom: Connect OC3 port on BXM with 7200 router, connect 2 OC3 ports back to back. enable ILMI on router, and ILMI, protocol on card cnfrsrc VSI part 1 disable NebDiscovery on ports.when running cnfnodeparm 56 0|1 and With VSI disabled, peer info is transmitted to peer. delcntrl, and cnfrsrc deleting VSI partition, fails to disable Peer information as well.
Conditions: ilmi_enable_from_contrl bit was not cleared when delctrlr, or vsi partition deleted, thus vsi code kept issuing get requests and responding to peer information.
In AR/VSI hybrid networks, and for backward compatibility either BXMs w/o NebDisc, or swsw versions. Topo traps are not sent to downrev'd swsw versions, and are controllable by sw software for versions including the feature.
Code was added to properly support disabling of VSI functionality using delctrlr or cnfrsrc @ Bcc in addition to existing dnpnport @ the vsi controller. support for backrev'd cards added, and corrections to logic in Ilmi FSM state machine to properly send TopoTrap to BCC.
Workaround: None
|
CSCdr79936
|
Symptom: Stats files not generated/missing on some 15 minutes intervals.
Conditions: When system time is changed at 15 minutes boundaries.
Workaround: Minimize system time and card config changes.
|
CSCdr83144
|
Symptom: Card error of:
Description: 'N. Fatal from 0x17: 0x25120075 0x809b5f90 0x367e 0x1
Conditions: switchyred, switchcc or reset PXM when there are spvc connections with stats enabled.
Workaround: None
|
CSCds11484
|
Symptom: Available cell rate reported by BXM is incorrect.
Conditions: Sum of the minimum bandwidths of all the interfaces on a BXM reaches OC12.
Workaround: Reduce minimum BW on all interfaces by half.
|
CSCdr89217
|
Symptom: Software Error Log of 9098
Conditions: cnfrsrc of partition 3 using MEB firmware
Workaround: None
|
CSCdr89966
|
Symptom: Card Error of 0x41030006
Conditions: PXM controller is upgraded/re-booted
Workaround: None
|
CSCdp89085
|
Symptoms: The total call count becomes negative on the BXM interface. However, this problem has not been reproducible.
Conditions: If this problem happens, the following card error is displayed:
'vsi_rsrc_pfns.c 483 VrmRetLcnResources 3, 16316'
Workaround: A related bug CSCdr86894 which reported an incorrect number of total call counts, has been found to be the result of an uninitialized variable in vsi_rsrc_conn_pfns.c: VrmRsrcClrRCMP().
The debugging information embedded in this function may be helpful in verifying the negative call count problem if it is reproduced.
|
Resolved Anomalies in MFE
Table 56 lists the resolved anomalies in MFE firmware.
Table 56 Resolved Anomalies in MFE Firmware
Bug ID
|
Description
|
CSCdp05098
|
Symptom: Cell discards occur for ABRFST/ABRSTD conns when the traffic burst is greater than the MBS
Conditions: This occurs when the traffic burst size is fixed to 140000 cells at 70000 cps. The conn are configured with PCR=72000/72000, MBS=1000/1000 and ICR 7200/7200. This is the expected behavior since the configured MBS < the actual burst size.
Workaround: Increase the MBS and ICR using cnfcon.
|
CSCdr59731
|
Symptom: Port 11.1 is connected to 11.2 and ILMI are up and running on both ports. Enable neighbor discovery on 11.1, then 11.2.
The 0x71 responses/traps from BXM fw is not predictable. At least two variations are observed:
1. port 11.2 has it's neighbor's info but port 11.1 doesn't.
2. both port 11.1 and 11.2 only know the IP addresses of their neighbors. The Neighbor's IFName are missing.
Problem was observed in MF17, but code changes in more recent builds had already repaired the problem.
Conditions: When ILMI session restarts, remnants of IfName, IpAddr from previous session left. Clr/reset IfName,IpAddr in MIB, on ILMI session restart In FMSStart, pIlmiProcessFsmStart() calls a new function IlmiClrPeerAndSendTopoTrap(pcb_ptr->session_id)
|
CSCdr79936
|
Symptom: Stats files not generated/missing on some 15 minutes intervals.
Conditions: When system time is changed at 15 minutes boundaries.
Workaround: Minimize system time and card config changes.
|
CSCdm16800
|
Symptom: Card error 0xc000007 appears in the card error log.
Conditions: This error indicates that an unknown type of cell which is not expected has arrived in the egress QE.
Workaround: Engineering has done in-depth investigation into this case. We are convinced the problem does not affect user traffic or the node in any other way. Therefore, the symptom will not be reported as a card error. The fix has been incorporated into MEE firmware.
|
CSCdp22930
|
Symptom: N/A
Conditions: cbus rd/wr operations set up in the PUUMBA chip when performing cbus rcv/xmit.
Workaround: None
|
CSCdp74680
|
Symptom: Even if the interface is in LOS, the spvc's do not generate ingress AIS into the network.
Conditions: Connection is added after the interface goes into LOS.
Workaround: None
|
CSCdr44250
|
Symptom: Private image did not allow as many OAM cells to flow as public image.
Conditions: This occurred by undoing a hardware fix in a private image.
Workaround: This was never introduced into the Public view and no workaround is required.
|
CSCdr45986
|
Symptoms: Standby and active block checksum value do not match and resync happens on switchover.
Conditions: When active card has many spvc connections derouted it happens.
Workaround: None.
|
CSCdr71473
|
Symptom: Unreachable BXM, sw errors and cd errors on the BPX.
Conditions: LMI is enabled when controller either slow to respond or un-reachable.
Workaround: Disable LMI.
|
CSCdp97307
|
Symptoms: When executed "rsh <slot> vsi cm VsiIs " without parameter. The card will crash.
Conditions: Always.
Workaround: Pull out the card and reinsert.
|
CSCdr86894
|
Symptoms: Many ports have VC failure because BXM has no resource to build the CVC.
Conditions: Intermittent
Workaround: Reset BXM card.
|
CSCdr57712
|
Symptom: Multi_partition fails to report all virtual trunks.
Conditions: In case of virtual trunks with different partition.
Workaround: Reset the BXM card.
|
CSCdr77238
|
Symptom: Switch General Info does not contain bulk set capability bit. With newer images of PXM bulk set will not work with BXM images prior to MFD.
Conditions: PXM Images later than 07/06/2000 contains logic to identify the bulk set capability of the slave. BXM images prior to 07/06/2000 will not have this bit set because it is newly introduced parameter in VSI spec.
Workaround: No workaround. Need to upgrade to MFD.
|
Resolved Anomalies in MFD
Table 57 lists the resolved anomalies in MFD firmware.
Table 57 Resolved Anomalies in MFD Firmware
Bug ID
|
Description
|
CSCdr29278
|
Symptom: Originally the card used to get frozen not responding to any request from the controller, as the TCB database was corrupted. But it has been protected now. But whenever a null pointer is being inserted into the TCB list a card error is being flagged. It is a harmless card error (not service affecting)
Conditions: The cause is unknown.
Workaround: None.
|
CSCdp63445
|
Symptom: ABR and UBR connections loose traffic when VC shaping is turned on.
Conditions: Enabling of VC shaping on port terminating ABR and UBR connections.
Workaround: Leave VC shaping disabled.
|
CSCdr30454
|
Symptom: Connections (LCNs) can not satisfied because of insufficient memory
Conditions: When channel stat level is set to 0
Workaround: Use chan stat level (cnfcdparm) 1, 2 or 3
|
CSCdr14247
|
Symptom: The correct state of an SPVC is not reflected in connection bulk traps for large number of connections (> 1000). Sometimes Connection states keep toggling between AIS and CLR state when the conns are actually in AIS state
Conditions: AIS cells generated by the RCMP on different connections arrive too close to each other in the same second. This sudden burst of cells overwhelm the Class of service buffers (QBINs) in the Egress direction and get discarded. This causes remote end of the trunk to detect a loss of AIS cells and declare connection a CLR.
Workaround: None
|
CSCdr40204
|
Symptom: Service rate for VBR traffic when WFQ is enabled is at SCR (instead of PCR) even when there is no congestion for enhanced cards (1210 QE & Sabre)
Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level.
Workaround: None. Has been fixed.
|
CSCdr42885
|
Symptom: All the ports on a BXM slave go into provisioning state.
Conditions: Controller looses communication with the BXM. This happens when AAL5 driver in the BXM mal-functions and does not free the message buffers of the application processes (ILMI/VSI etc). Eventually BXM runs out of message buffers.
Workaround: Reset the BXM card.
|
CSCdr49056
|
Symptom: Invalid Part id in SPVC stats after controller is added.
Condition: This problem happens when SFM receives the vsi message before adding the controller. This is possible to happen when there is a delay between 52 and 61 message. Since 52 add the control vc it will receive the frame and give it SFM task. But SFM won't have any information for that partition and will report the error saying that invalid partition. Since this is possible to happen as per design, the card is removed now.
|
CSCdr40234
|
Symptom: Service rate for UBR traffic when WFQ is enabled much lower than PCR even when there is no congestion for enhanced cards (1210 QE & Sabre)
Conditions: For enhanced cards, when WFQ is enabled, the local congestion is monitored at the Egress side by the hardware. In order to do this, a few variables that need to be initialized. There were some problems with the initialization routine, causing inaccurate tracking of the congestion level.
Workaround: None. Has been fixed.
|
CSCdr49060
|
Symptom: When doing a cnfcon for ABR connection, service rate drops to MCR rate even when there is no congestion. This is when WFQ is enabled and the inherent VSVD is not used.
Conditions: There are a certain parameters associated with WFQ that are required in order for WFQ to work. However, for ABR connections, when a cnfcon is done, once it is detected that VSVD is not enabled, the structure (Sabre rate RAM) which holds all these parameters is cleared out. This would cause WFQ not to operate properly.
Workaround: No need. Fix is done.
|
CSCdr43012
|
Symptom: All the ports on a BXM slave go into provisioning state.
Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck.
Workaround: Reset the BXM card.
|
CSCdr52195
|
Symptom: All the ports on a BXM slave go into provisioning state.
Conditions: Controller looses communication with the BXM as AAL5 driver in BXM gets stuck.
Workaround: Reset the BXM card.
|
CSCdr36963
|
Symptom: When PNNI controller goes down then comes up, it couldn't establish its control call to the BXM partition, thus VC failure is displayed in PNNI controller for that partition.
Conditions: This problem only happens under the following conditions:
1. The policy parameters for the partition have been configured as nonzero at some of the class of service,i.e. the reserved minimum bandwidth of some class of service are nonzero.
2. Delete/disable that partition. BXM suppose to release all resources. However, it only released resources at partition level, but leave the reserved resources at cos level unchanged. As result, when this partition is enabled again, the internal CAC calculation at partition level became negative. That caused the first control call setup request fail.
Workaround: Reset the BXM card will clear the VC failure.
|
CSCdr33867
|
Symptom: Connect OC3 port on BXM with 7200 router, enable ILMI on router, and ILMI, protocol on card and Neighbor Discover, Object 0x31, Peer's IfName is not null terminated.
Conditions: Some peer.ifName's are null terminated, some aren't a PDU containing valid nonzero length peer.ifName doesn't always include '\0'; and is stored accordingly in the MIB. added a test if peer.ifName is non-zero in length, and isn't null terminated, concatenate the '\0'char and bump peer.ifNameLen++ count Added logic CbIlmiStatsReport, ilmi_proc.c pIlmiFsmGetResponseEventAtS3, pIlmiFsmGetResponseEventAtS9, ilmi_fsm_evt.c to ensure TopoTrap, and ILMIStats report are correctly formatted.
Workaround: None
|
CSCdp48306
|
Symptom: On NNI side, when cross connect is established with VPI>1000 (0x3e8) the first nibble is getting chopped off and traffic is flowing on VPI 0xe8 due to bad programming of connection.
Conditions: This happens if on NNI side VPI > 0xff.
Workaround: None.
|
CSCdr51875
|
Symptom: Virtual Trunking causing Unreachability
Conditions: At least two virtual trunks share a common port at one node, but their remote endpoints terminate on different nodes.
The virtual trunks are used to carry networking (rt_op) traffic.
The simplest example follows below:
node_A ---- vtrk ---- /---- vtrk ---- node_C
/
/
node_B
(vtrks share common port)
With this topology, "node_A" sees "node_C" as unreachable and vice-versa; however, "node_A" communicates to "node_B", and "node_B" communicates to "node_C".
Workaround: Customers who are already using VT wraparound should continue to do so under 9.2.3x until the fix is available.
BXM virtual trunking (no VT wraparound) can still be implemented using software release 9.2.2x.
If virtual trunks are not yet in use, the VT wraparound solution can be implemented in release 9.2.3x.
|
CSCdr57805
|
Symptom: Card errors show up indicating "CB_TASK is ready"
Conditions: CB_TASK gets busy processing VSI messages and this causes root task to incorrectly assume that CB_TASK is not in a sane state. Actually a firmware change incorrectly reduced the polling interval by the root task such that it was polling the states of tasks sooner than it is supposed to.
Workaround: None. Ignore these card errors as these are benign.
|
CSCdr56931
|
Symptom: After resetsys on PXM or bouncing the feeder/control port or reset of BXM card, some virtual trunks go into vc failure/building vc state.
Conditions: Resetting PXM or pulling out the cable connecting the BXM feeder port to the controller or resetting the BXM cause the interface set policy parameters to be sent to the BXM. This cause ingress BW to be recomputed. CB_TASK passes VI numbers 0 to 31 to the CAC module which expects the range 0 to 15. This caused the problem by overindexing the CAC structures.
Workaround: None
|
CSCdr59241
|
Symptom: Building VC status on UNI ports after repeated enabling/disabling of partition with the control port
Conditions: Controller does not send policy parameters for control port upon enabling of partition. When disabling partition, COS max bandwidth was zeroed out. With no policy parameters from which to obtain the new values, COS max bandwidth is stuck at zero; thus not allowing ant control to be established.
Workaround: Older PXM image does send policy parameters even for the partition with the control port. Control port does not require policy parameters to be sent from controller. Default it to the max bandwidth configured for the partition.
|
CSCdr51970
|
Symptom: Change CAC policy parameters will cause the available BW for some cos to be negative.
Conditions: Current implementation does not validate the CAC policy parameter change. It will always take the value. However, in some cases, improper policy parameters change will cause the avail_bw at cos level go negative. In this particular scenario, the current used bandwidth of a cos is equal to its reserved minimum bandwidth.Then the user changed the policy parameter to make this cos min_bw to smaller number. Now current_used_bw for this cos is greater than its reserved, and it has to obtained bw from the common pool to maintain its currently used bw. However, the user changed the policy parameter again, to increase the reserved bw for another cos, which caused the common pool to be zero.Therefore, by normal calculation, the previous cos avail_bw becomes to negative. Decreasing cos_min_bw to be less than it is currently used_bw is an invalid operation and should get rejected, otherwise it will mess up the CAC.
Workaround: Delete some connections to release bandwidth before decreasing cos minimum bandwidth.
|
CSCdr66273
|
Symptom: The encoding is in the reverse of the expected value by UNI4.0 spec.
Conditions: STD ABR connections.
Workaround: No workaround.
|
Resolved Anomalies in MFC
Table 58 lists the resolved anomalies in MFC firmware.
Table 58 Resolved Anomalies in MFC Firmware
Bug ID
|
Description
|
CSCdp63445
|
Symptom: ABR and UBR connections loose traffic when VC shaping is turned on.
Conditions: Enabling of VC shaping on port terminating ABR and UBR connections
Workaround: Leave VC shaping disabled.
|
CSCdr11396
|
Symptom: Data transfer has affected while running OAM loopback
Conditions: All user data is dropped when send in 960 cps of oam.
Workaround: None
|
CSCdp11511
|
Symptom: BPX treats segment oam loopback different from end-to-end oam loopback cells.
Conditions:
Workaround:
|
CSCdr13208
|
Symptom: BXM CD errors while running OAM cells.
Conditions: One PVC has 2880 cps of data and 960 cps of oam cells. Another PVC has 2880 cps of data and 960 cps of oam cells.
Workaround: None
|
CSCdr13196
|
Symptom: BPX reports SWERR 105.
Conditions: SWERR105 logged while running OAM loopback test
Workaround: None reset the BXM card.
|
CSCdr13182
|
Symptom: tstdelay/tstcon/tstconseg for all PVCs on that card will fail.
Conditions: When user sending in >= 960 cps of oam loopback cells
Workaround:
|
CSCdr13151
|
Symptom: dspportstats always show Tx port = 0
Conditions: Sending in >= 960 cps of oam loopback cells.
Workaround:
|
Resolved Anomalies in MFB
Table 59 lists the resolved anomalies in MFB firmware.
Table 59 Resolved Anomalies in MFB Firmware
Bug ID
|
Description
|
CSCdm52254
|
Symptom: Random BIP-8 errors show up on T3 when running in direct map (HEC) mode. There is no such thing as a BIP-8 error in the direct map mode. But this counter should report 0 in this mode.
Conditions: This is totally random due to the fact that an uninitialized (don't care) counter variable is accumulated in every poll period. This counter is not even read from hardware in the HEC mode.
Workaround: Ignore BIP-8 errors when the T3 trunks are configured in the HEC mode.
|
CSCdm62817
|
Symptom: tstconseg command sometimes does not work.
Conditions: Execute tstconseg multiple times with high loop count (10).
Workaround: None
|
CSCdm84853
|
Symptom: BW reported via interface load info is erroneous.
Conditions: When Forward & Backward BW for VSI connections is different.
Workaround: None
|
CSCdm92931
|
Symptom: APS line switchover occurs upon card removal when lockout is set.
Conditions:
Workaround: None Upgrade to MEF or newer version of firmware.
|
CSCdp20848
|
Symptom: SF switchover doesnot occur after dncd/upcd execution on Annex B 1+1 APS.
Conditions: When the dncd command is executed, SWSW sends 0x27 CBUS message. The handler for this message was putting the lines in loopback and shutting down the laser. Also it was changing the line state in SoCdDown() to DOWN state. This caused subsequent upcd (0x05/0x04) message to re-initialize the lines disabling the S/UNI interrupts in the process.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp24224
|
Symptom: WTR does not occur after LOS recovery on protection line
Conditions: The meaning of primary and secondary channels were changed immediately upon switchover instead of waiting for the expiry of WTR. This caused the clearing of the failure to be accounted against the secondary channel and thus there was no WTR. Fixed by introducing a Preparation switch mode where-in the current active channel will remain as the secondary until a WTR occurs or a primary section mismatch pre-empts that state. At the expiry of WTR, the preparation switch mode is complete and the current active channel becomes the primary.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp25130
|
Symptom: APS Non-revertive bidirectional feature.
Conditions: Resolved
Workaround: None
|
CSCdp25220
|
Symptom: Avail Buffer on BXM = 0 on LVC flapping for xtag interfaces
Conditions: Same as CSCdp58969. During this condition AAL5 driver doesn't release the transmission buffer.
Workaround: None. Upgrade to/MEF or newer versions of firmware
|
CSCdp28931
|
Symptom: No RDI-P generated when loss of Cell Delineation occurs.
Conditions:
Workaround:
|
CSCdp32646
|
Symptom: WTR Timer does not work and reversion occurs during SF switchover.
Conditions: Added a preparation switch mode where the current active channel is the secondary channel. At the expiry of WTR, the secondary channel is changed to the become the primary channel.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp35156
|
Symptom: BPX APS reverts back to the working line before WTR time has expired
Conditions: TR was being pre-empted by a spurious SD condition. Fixed by setting the right thresholds for SF/SD based on BER.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp38148
|
Symptom: Resetcd slot 11 on BPX causes local APS switching.
Conditions: Re-impose the selector and bridge states on both ACTIVE and STANDBY cards after Y-red switchover, re-discover the line states and re-execute and external requests.Also include a STABILITY timer before the line state is processed.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp39723
|
Symptom: Aps not functioning in 9.2.21 w/FW ME18@sprintf for Bidirectional w/Nonrevertive
Conditions: Reversion was happening due to spurious SF/SD events.Fixed by setting the right values for SF/SD thresholds.
Workaround: None.Upgrade to MEF or newer version of firmware
|
CSCdp46399
|
Symptom: Need a documentation explains how to setup port groups for FW MEF (me26).
Conditions:
Workaround: No known workaround.
|
CSCdp49640
|
Symptom: When FCES feature enable on BXM NNI data transfer stops.
Conditions: The ABR parameters like NRM,CRM,FRTT,MCR,ICR were not getting programmed when the FCES is turned on using th cnfcon command.Adding the Connection with the FCES enabled behaved properly.
Workaround: None
|
CSCdp49749
|
Symptom: Node unreachable after resetting two nodes in the network.
Conditions: When combus message 0x52 is sent down to BXM, we were not handling the case when message says activate the lcn, but delete the vpi-vci pair specified in the command.
Workaround: None.Upgrade to MFB.
|
CSCdp57596
|
Symptom: CB_TASK on BXM goes into deadlock state causing VSI session to be lost
Conditions: This happens when both Ingress and Egress qe semaphore is taken by IDLE_TASK and it never released in an error condition.
Workaround: None. Upgrade to MEF or newer versions of firmware.
|
CSCdp58969
|
Symptom: cb_get.c CB_VPC_STATUS_POLL SoItcSend Failed upon VSI Failure
Conditions: When VSI receives and transmits lot of vsi message AAL5 drive will get into deadlock problem if it had missed a DMA interrupt.
Workaround: None. Upgrade to MEF or newer version of firmware
|
CSCdp59328
|
Symptom: EPD bit was not set for interslave control vc.
Conditions: When vsi get congestion (same as CSCdp58969).
Workaround: None. Upgrade to/MEF or newer versions of firmware.
|
CSCdp59727
|
Symptom: Addlnlocrmt causes node unreachable.
Conditions:
Workaround: Reset the BXM card.
|
CSCdp59729
|
Symptom: addlnlocrmt causes node unreachable.
Conditions: addlnlocrmtlp causes node unreachable even though there are other parallel trunks.
Workaround: No known workaround.
|
CSCdp60696
|
Symptom: Both lines fail when only one line in alarm.
Conditions: After the standby card comes out of reset, its S/UNI states are not reliable for a period of 1.5 seconds and the S/UNI reports LOS clear on the WORK line. This gets conveyed to the active card and then the Manual switch gets priority and becomes the current local request. This causes a switch back to WORK. When the active card's S/UNI monitors the WORK line, it discovers that the line is in LOS and immediately switches back. The oscillations continue and the line goes into LOCKOUT due to excessive switching. In the Lockout mode only the WORK line is active and thus the defect.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp62213
|
Symptom: Switching from bi-dir to uni-dir mode APS generates APS architecture mismatch error
Conditions: When APS pair is configured from bi-dir mode to uni-dir mode the other side indicates APS architecture mismatch error, and then the other side is also configured from bi-dir mode to uni-dir mode, the APS architecture mismatch error does not clear.
Workaround: Delete APS and then add APS again - it defaults to uni-dir.
|
CSCdp65320
|
Symptom: Need a trap when BPX puts APS in lockout
Conditions: Send the traps in the right sequence. First send the Lockout trap and then the failed to switch trap if there is a switch attempt while lockout is in effect.
Workaround: None.Upgrade to MEF or newer version of firmware
|
CSCdp67673
|
Symptom: dspapsln does not show ARCH_MIS any more.
Conditions: dspapsln does not show ARCH_MIS when caused for the second time on the same trunk.
Workaround: No known workaround
|
CSCdp79156
|
Symptom: TDP signalling cross connect VSI request rejected by BXM
Conditions: If BPX is configured with trunks and virtual trunks the virtual trunks are initialized properly with qbin size.
Workaround: None.Upgrade to MEF or newer version of firmware
|
CSCdp84386
|
Symptom: Connectivity w/BXM lost due to missing DMA completion interrupts
Conditions: Aal5 driver will be in deadlock and never transmits and receives.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp86147
|
Symptom: The removal of Rx cable of APS trunk leading to loss of Frm and Prot Sw Byt Fail.
Conditions: While removing the Rx cable of APS working line (configured to trunk) working line goes to Loss of Frm and dsptrks shows the trunk in alarm. After connecting cable back the APS Alarm status shows "Prot Sw Byt FAIL".
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp89972
|
Symptom: Node rebuild caused 3 BXM cards failed.
Conditions: Moved the allocation and initialization of the Connection database to the SoCoEnterStandby function instead of in the 0x50 handler (SoCdUp).
Workaround: None.Upgrade to MEF or newer version of firmware.
|
CSCdp92916
|
Symptom: Commands executed on stdby card affect APS line.
Conditions: Series of commands executed in stdby card affects APS line.
Workaround: None.Upgrade to MEF or newer version of firmware.
|
Resolved Anomalies in MFA
Table 60 lists the resolved anomalies in MFA firmware.
Table 60 Resolved Anomalies in MFA Firmware
Bug ID
|
Description
|
CSCdk42527
|
Symptom: Rx Queue becomes full after LOS on the feeder trunk.
Conditions: After LOS condition on the feeder trunk.
Workaround: Reset the feeder trunk.
|
CSCdk80483
|
Symptom: TX cell loss counts in dsptrkerrs increase continuously.
Conditions: When there is trunk configured.
Workaround: None.
|
CSCdk81384
|
Symptom: BXM slot errors keeps on incrementing on a BCC3 node, but the reading of 'EAP ARFD' should only be interpreted when using the dual receiver feature on a BCC4 node.
Conditions: BXM slot errors on a BCC3 node.
Workaround: None
|
CSCdm04312
|
Symptom: The problem is a false failure is declared against the SIMBA Multicast Record RAM.
Conditions: The problem occurs when Self Test is activated against a Y-Redundant pair of BME Cards (BXM-622 cards loaded with the multicast BME firmware) that have more than 1000 connections programmed through them.
Workaround: Disable Self Test via the cnftstparm command.
|
CSCdm09295
|
Symptom: Reconfig of FCES from enable to disable does not work, as a result traffic burst is restricted to MCR.
Conditions: Every time changing an existing connection from FCES enable to disable.
Workaround: Delete the connection and add back a new one with FCES disable.
|
CSCdm09882
|
Symptom: Log non fatal message related to the RCMP errors.
Conditions: It is mainly seen in the heat chamber.
Workaround: Please make sure the TEST FREQUENCY and TIMEOUT variables under cnftstparm for BXM are set to 4000/3700 level.
|
CSCdm16505
|
Symptom: AIS not sent on VP ABRFST/ABRSTD connection.
Conditions: LOS on trunk between 2 nodes.
Workaround: None
|
CSCdm31923
|
Symptom: AIS/YEL alarm doesn't go away even after the alarm is clear from the other end.
Conditions: It happens on the E3 when the LOOP TIME parameter is set to YESin the trunk or line configuration.
Workaround: None
|
CSCdm39186
|
Symptom: Card fatal error occurred when running in standby mode under the heat condition. As a result, the card reset periodically.
Conditions: Card running in standby mode under heat condition
Workaround: None
|
CSCdm50659
|
Symptom: Trunk alarms are not generated when random bit errors are injected onto a trunk using an Adtech Sx14 test set at a rate of 10E-3. There are trunk statistics generated but no trunk alarm because the statistics that cause alarms on do not meet the threshold for MAJOR or MINOR alarms.
Conditions: This was generated in a lab environment with test equipment that was set to inject bit errors randomly through the entire bandwidth. Some HCS errors were generated as well as Path unavailable and Path Farend unavailable.
Workaround: Lowering the alarm threshold for MAJOR and MINOR HCS errors can help to generate a trunk alarm. Use the cnflnalm command and modify the Hcserr alarm thresholds to .01 for MAJOR and .0001 for MINOR. These thresholds are as low as they can be set currently.
|
CSCdm52585
|
Symptom: DspVsiPartInfo shows very large Available LCN field.
Conditions: When the sum of min-lcns is greater than the max(max lcns) on a port group.
Workaround: None.
|
CSCdm53420
|
Symptom: switchyred causes APS line to switch when last user request is clear.
Conditions: APS 1+1 configuration. The protection line was active and the "last user switch request" was clear. When a switchyred was performed, APS line switched to working line active
Workaround:
|
CSCdm61493
|
Symptom: When BIP8 errors are received on an E3 line or trunk at a rate of 10E-3, the line or trunk will not declare any alarm.
Conditions: When high rates of BIP8 errors are received.
Workaround: None.
|
CSCdm73220
|
Symptom: Trunks or Virtual Trunks does not allow traffic going through.
Conditions: SWSW 9.1 with ME level of firmware. Trunks or VTs configured on BXM/BXM-E.
Workaround: None
|
CSCdm81534
|
Symptom: ICR of abrfst on BXM-155 falls down to MCR after resetcd.
Conditions: Change the ICR after resetcd before start sending traffic.
Workaround: None
|
CSCdm92916
|
Symptom: Operational commands (dncd, resetcd, remove) on standby card impact active APS line. When active line is PROT line and a switchover of cards occur, WORK line becomes active line on the newly active cards.
Conditions: APS 1+1 Annex B and PROT is active line. switchyred or resetcd on the active card causes line to switchover from PROT to WORK.
Workaround: None
|
CSCdm92931
|
Symptom: APS line switchover occurs upon card removal/insertion when lockout is set
Conditions: When Lockout is set, removing/inserting the card makes it happen.
|
CSCdm93274
|
Symptom: OC3 back card LED is wrong after reset/pull cards.
Conditions: Multiple APS lines on a card and perform switchyred when Working line is active and Secondary card is active.
Workaround: None.
|
CSCdp11025
|
Symptom: Use the "dspapsln" to get the screen to display apsln status.When the working line is taken out the LOS appears on the working line. When the protection line is taken out both the working and protection display LOS. When the protection line is put back in the LOS/Alarms on the protection should clear. They do not.
Conditions: Physically remove and add the rx or both rx and tx lines as follows:
1. Remove the working line.
2. Remove the protection line.
3. Add the protection line back.
Workaround: None
|
CSCdp17741
|
Symptom: 2-portgroup card reports 1 port group at the channel stats level 2 and 3.
Conditions: When channel stats level 2 or 3 are configured on BXm-622-2 port and BXM-155 reports only one port group.
Workaround: Auto Route connections are not affected by this. But for VSI connections there is no work around.
|
CSCdp18840
|
Symptom: The CBR.2 Calls do not pass traffic above 50 Cells/second.
Conditions: VSI controller establishes CBR.2 connection and it does not fill in the PCR field.
Workaround: Fill the PCR value also with the CR value.
|
CSCdp22930
|
Symptoms: Intlock missing for rd/wr operation
Workaround: Reassert intLock on commbus ISR to prevent SCC access from getting interrupted.
|
CSCdp31325
|
Symptom: UBR cells are policed unnecessarily below PCR.
Conditions: Always.
Workaround: None.
|
CSCdp32853
|
Symptom: The BXM enhanced cards keep getting reset and card errors are logged and node may go into degraded mode, when command "addapsln slot1.port1 slot2.port2 1" is issued.
Conditions: BXM enhanced OC3 cards with 4 port and FW rel earlier that M.E.22/M.F.09.
Workaround:
1. Do not addapsln on second port onwards for BXM-E OC3 4 port card.
OR
2. Replace the BXM-E 4 port card with 8 ports card.
|
CSCdp33894
|
Symptom: Standby APS line shows status as Path AIS upon switchyred or on APS switchover on LOS.
Conditions: switchyred on APS, the prot. line report Path AIS.
Workaround: None. Upgrade to ME26/MED or later versions of BXM firmware.
|
CSCdp36155
|
Symptom: BXM-E OC3/OC12 does not show supporting APS HW 1+1 in dspcd command and otherwise also.
Condition: BXM-E OC3/ OC12 card with HW rev < 'C'.
Workaround: None.
|
CSCdp36324
|
Symptom: Last user request affects switching on BPX.
Conditions:
Workaround:
|
Resolved Anomalies in MEC
Table 61 lists the resolved anomalies in MEC firmware.
Table 61 Resolved Anomalies in MEC Firmware
Bug ID
|
Description
|
CSCdm66131
|
Symptom: After addapsln trunk goes to LOS
Conditions: Both ends have secondary card active, add aps 1+1 to one end, then add aps to the other end, the trunk sometimes goes into LOS.
Workaround:
|
CSCdm64366
|
Symptom: APS 1+1 manual switch sometimes does not work after a while after several manual switch and auto switch.
Conditions: Secondary card is active and several manual switch and auto switches are performed.
Workaround:
|
CSCdm62809
|
Symptom: APS 1+1 bidirectional non-revertive switches back to working line when line condition clears on working.
Conditions: APS 1+1 configured in bi-direction non-revertive mode.
Working line is in LOS, current active line is protection, clear LOS on working line.
Workaround:
|
CSCdm69974
|
Symptom: Card errors (0x25170076) occur when only one Virtual Trunk is configured in a physical port.
Workaround:
|
CSCdm65813
|
Symptom: APS switches back o working line incorrectly.
Conditions: Switch sequence W->P, P->W and then W->P, then cause LOS on WORK line and put the cable back, APS switches to Working line.
Workaround:
|
CSCdm77212
|
Symptom: When addshelf command is executed, it comes back with a communication breakdown.
Conditions: Channel level stats is set to 0 so that BXM reports wrong max channels.
Workaround:
|
CSCdm74316
|
Symptom: Re-adding VSI shelf does not work until a resetcd is executed on the LSC control port.
Conditions: Load information on an interface is 4 bytes more that MAX_VSI_MSG.
The message gets dropped on BXM, so VSI controller is in discovery state forever.
Workaround:
|
CSCdm75722
|
Symptom: No control VC after BXM is reset.
Conditions: When resync request comes down from the VSI controller with 19 checksum blocks, the length check done on BXM does not include padding.
Workaround:
|
CSCdm74968
|
Symptom: 0B card error causing BXM to reset.
Conditions: Over night jobs running on controller cards.
Workaround:
|
CSCdp02190
|
Symptom: tstdelay timed out when going through BNI trunk.
Conditions: More that 12 VTs on an interface causes wrong port-vi mapping while considering STI_SHIFT/NO_SHIFT from 13 th VT/port onwards.
Workaround:
|
CSCdm78335
|
Symptom: dspvsistatus rarely shows the VSI programming status as Done.
Conditions: Primary and secondary port has two different VPI range.
Workaround:
|
CSCdm26752
|
Symptom: Card errors continuously logged with "SoItcSend failed" message.
Conditions: RAS oam_lpbk is on and switchyred is executed several times in a job.
Workaround:
|
CSCdm93839
|
Symptom: Card resets on receiving oam loopback cells at high rate.
Conditions: oamlpbk is enabled with high oam traffic on large number of connections.
Workaround:
|
CSCdm52254
|
Symptom: BIP-8 code errs occurs on routing trunks
Conditions: T3 card used in HEC mode can randomly have this problem.
Workaround:
|
CSCdm44183
|
Symptom: BXM-155 4DX was not able to recover after resetting the card.
Conditions: Traffic is sent at a rate >= 383 cps on a terminated connection on BXM-E card and then card is reset.
Workaround:
|
CSCdm90997
|
Symptom: BXM-E trunk and port stats are always zero in TX direction.
Conditions: Port terminated on BXM-E card or trunk passing through BXM-E card.
Workaround:
|
CSCdm80991
|
Symptom: Unable to add 3 segment connections using CM GUI.
Conditions: Feeder connected to BXM card of BPX routing node and for, BXM trunk configuration, ILMI/LMI protocol is enabled as CARD based.
Workaround:
|
CSCdm82688
|
Symptom: Traffic Shaping problems with VT with and without rap around solution.
Conditions: Large deviations in CDV values.
Workaround:
|
CSCdm94372
(See explanation below.)
|
Symptom: Trunks sometimes drop cbr traffic.
Conditions: If a trunk is configured to full line rate on BXM cards, then traffic is dropped.
Workaround:
|
CSCdp00063
|
Symptom: Node unreachability is experienced on VTs (virtual trunks).
Conditions: Multiple VTs are configured on a trunk interface of the BXM/BXM-E.
Workaround: Configure only one VT per trunk interface.
|
Logic to Calculate Actual Cell Transmission Rate in a BXM card (CSCdm94372):
if (configured cell rate == full line cell rate) then
transmitted cell rate = full line cell rate
else
transmitted cell rate = from equation below or from table 1
For example:
If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is then 98,013 CPS any traffic sent over 98,013 CPS would be discarded.
Only rates in the table or computed from the equation should be used. Otherwise, cell loss may be experienced.
1464865
|
56552
|
28832
|
19348
|
14559
|
11670
|
9738
|
8355
|
733860
|
54458
|
28278
|
19097
|
14416
|
11579
|
9674
|
8308
|
489558
|
52513
|
27744
|
18852
|
14277
|
11488
|
9611
|
8261
|
367288
|
50703
|
27231
|
18614
|
14139
|
11399
|
9549
|
8215
|
293888
|
49013
|
26736
|
18381
|
14005
|
11311
|
9487
|
8169
|
244938
|
47432
|
26258
|
18154
|
13872
|
11225
|
9426
|
8124
|
209966
|
45950
|
25798
|
17933
|
13743
|
11140
|
9366
|
8079
|
183733
|
44558
|
25353
|
17717
|
13616
|
11056
|
9307
|
8035
|
163327
|
43247
|
24923
|
17506
|
13491
|
10974
|
9248
|
7992
|
147001
|
42012
|
24508
|
17300
|
13368
|
10892
|
9190
|
7948
|
133642
|
40845
|
24106
|
17099
|
13248
|
10812
|
9133
|
7906
|
122509
|
39741
|
23717
|
16902
|
13129
|
10733
|
9077
|
7863
|
113088
|
38695
|
23341
|
16710
|
13013
|
10656
|
9021
|
7822
|
105012
|
37703
|
22976
|
16522
|
12899
|
10579
|
8966
|
7780
|
98013
|
36761
|
22623
|
16339
|
12787
|
10503
|
8912
|
7739
|
91889
|
35864
|
22280
|
16159
|
12677
|
10429
|
8858
|
7699
|
86485
|
35010
|
21947
|
15983
|
12568
|
10355
|
8805
|
7659
|
81681
|
34196
|
21625
|
15812
|
12462
|
10283
|
8753
|
7619
|
77383
|
33419
|
21311
|
15643
|
12357
|
10212
|
8701
|
7580
|
73515
|
32676
|
21007
|
15479
|
12254
|
10141
|
8650
|
7541
|
70014
|
31966
|
20711
|
15318
|
12153
|
10072
|
8599
|
7502
|
66833
|
31286
|
20423
|
15160
|
12053
|
10003
|
8549
|
7464
|
63927
|
30634
|
20143
|
15005
|
11955
|
9936
|
8500
|
7427
|
61264
|
30009
|
19871
|
14853
|
11859
|
9869
|
8451
|
7389
|
58814
|
29409
|
19606
|
14705
|
11764
|
9803
|
8403
|
7352
|
Resolved Anomalies in MEB
Table 62 lists the resolved anomalies in MEB firmware.
Table 62 Resolved Anomalies in MEB Firmware
Bug ID
|
Description
|
CSCdm50469
|
Symptom: Software error 105 and mallet card errors happened continuously.
Conditions: When jobs that cause reroutes of connections (e.g. switchcc, hitless rebuild) are run for a long time, sometimes BXM card freezes with malloc card errors and software error 105.
Workaround: None
|
CSCdm50723
|
Symptom: After deleting APS, switchyred causes temporary LOS when the other end still has APS.
Conditions: One end has APS 1+1, other end was added with APS 1+1 and line is up between the two ends. Then APS is deleted from one end. The primary card is active on non APS end. On switchyred on the non APS end there is a temporary LOS. If APS was never added to one end, then switchyred does not result in temporary LOS.
Workaround: Instead of deleting APS first and then doing a switchyred, do a switchyred first and then delete APS. This does not result in temporary LOS.
|
CSCdm63038
|
Symptom: BXM card fails with breakpoint error.
Conditions: When tx cell rate of a trunk is reduced to zero, BXM card fails with break point error (division by zero).
Workaround: None
|
Resolved Anomalies in MEA
Table 63 lists the resolved anomalies in MEA firmware.
Table 63 Resolved Anomalies in MEA Firmware
Bug ID
|
Description
|
CSCdm09882
|
Symptom: Log non fatal message related to RCMP errors.
Conditions: It is mainly seen in the heat chamber.
Workaround: None
|
CSCdm18186
|
Symptom: AIS status could be randomly be displayed in dspcon
Conditions: When the connection AIS signal is constantly changing, the dspcon/dspchstats OAM status will not be accurate for all the connections on the card.
Workaround: None
|
CSCdm26380
|
Symptom: Software error 9098 occured during switchyred BXM
Conditions: This problem occurs on cards with the APS channels halved option set and then doing a cnfrsrc on a port that belongs to the second port group. Note that this fix will cause a card mismatch on active cards with channel halved option turned on.
Workaround: None
|
CSCdm31923
|
Symptom: AIS/YEL alarm doesn't go away even after the alarm is clear from the other end.
Conditions: It happens on the E3 when the LOOP TIME parameter is set to YES in the trunk or line configuration.
Workaround: None
|
CSCdm37519
|
Symptom: Trunks go to Communication Fail after burning firmware.
Conditions: When MC10 is burnt into BXM-OC12 with trunks.
Workaround: None
|
CSCdm37709
|
Symptom: APS line fails to clear channel mismatch after lockout.
Conditions: Bi-direction APS 1+1. Local end has locked out of protection set. Then WORK cable is pulled out on local end to cause LOS. Lockout is then cleared and then the WORK cable is put back. This causes a channel mismatch on the far end and the mismatch never clears.
Workaround: None
|
CSCdm38647
|
Symptom: This bug has been fixed in MEA such that the firmware reports the correct number of port groups. The side effect of this fix is that the Switch Software could mismatch the BXM card. If there is a card mismatch then down all the lines/trunks on the card and up them again.
Conditions: When the user loads the MEA firmware on the BXM card running MDA with APS halved channeled enabled, then the card will come up in mismatched state.
Workaround: None
|
CSCdm46658
|
Symptom: switchapsln command does not work for APS AnnexB line.
Conditions: Annex B configuration if hitless rebuild is done when active line is PROT, then switchapsln does not work after hitless rebuild.
Workaround: None
|
Resolved Anomalies in MDA
Table 64 lists the resolved anomalies in MDA firmware.
Table 64 Resolved Anomalies in MDA Firmware
Bug ID
|
Description
|
CSCdm38647
|
Symptom: MDA fw may report incorrect number of port-groups when APS channels are set to halved.
Conditions: When user attempts to add all the channels available on the card on one port-group, it may be allowed even though the BXM may not have enough memory to support it. Also, this may cause a mismatch state when MDB firmware is burnt.
Workaround: Down all the line/trunks on the card and up them again.
|
CSCdm23713
|
Symptom: VI numbers are not modified by firmware.
Conditions: When one or more trunks are failed in the network, there may be a combreak in the network.
Workaround: Set all the Virtual trunks to restrict CC traffic.
|
CSCdm23827
|
Symptom: APS alarm may clear on switchyred.
Conditions: After a switchyred, an existing a LOS/LOF alarm may get cleared. This will only happen when the line has switched to protection before the card switchover is performed.
Workaround: None
|
CSCdm23752
|
Symptom: BXM fw does not allow a networking channel on VTs to configured for egress only.
Conditions: BXM fw allowed configuration of networking channel to be bidirectional only.
Workaround: None
|
Firmware Filenames and Sizes
The following list contains the firmware file information.
Filename
|
Size
|
BXMMFW.000
|
65536
|
BXMMFW.001
|
65536
|
BXMMFW.002
|
65536
|
BXMMFW.003
|
65536
|
BXMMFW.004
|
65536
|
BXMMFW.005
|
65536
|
BXMMFW.006
|
65536
|
BXMMFW.007
|
65536
|
BXMMFW.008
|
65536
|
BXMMFW.009
|
65536
|
BXMMFW.010
|
65536
|
BXMMFW.011
|
65536
|
BXMMFW.012
|
65536
|
BXMMFW.013
|
65536
|
BXMMFW.014
|
65536
|
BXMMFW.015
|
65536
|
BXMMFW.016
|
65536
|
BXMMFW.017
|
65536
|
BXMMFW.018
|
65536
|
BXMMFW.019
|
65536
|
BXMMFW.020
|
65536
|
BXMMFW.021
|
65536
|
BXMMFW.022
|
65536
|
BXMMFW.023
|
65536
|
BXMMFW.024
|
65536
|
BXMMFW.025
|
45744
|
BXMMFW.026
|
14
|
BXMMFW.027
|
2
|
BXMMFW.IMG
|
784
|
BXMMFW.img
|
784
|
Appendix B UXM ABL Firmware Release Notes
ABL is a new firmware release for the UXM card on IGX. Firmware is the same for UXM and UXM-E cards.
New Features
Flash memory drivers are upgraded to support more flash memory vendors so that more flash manufacturers can be used to source components.
Obsolete Features
None.
Compatibility
Software
|
ABL firmware is compatible with Switch Software 9.1 and 9.2
|
Hardware
|
ABL is compatible with UXM and UXM-E model H/W all models.
|
Previous Versions of UXM Firmware
|
On IMA trunks this version is not compatible with UXMs Model B firmware versions ABA to ABD.
On IMA trunks Model B firmware (AB*) is not compatible with model A (AA*) because model B is Standards compliant and model A is not. So IMA trunks must be upgraded together.
|
Resolved Anomaly in this Release
Table 65 lists the resolved anomaly in ABL firmware.
Table 65 Resolved Anomaly in ABL Firmware
Bug ID
|
Description
|
CSCds08193
|
Symptom: Although the trunk operates fine, the dspportstats will show the old delay value even though the actual delay on the line is different. IMA trunk statistics will not show the correct delay value when the delay is toggled rapidly.
Condition: Whenever the delay is changed rapidly on one of the links in an IMA group the dspportstats on that trunk is not updated. The errors seen are related to the SX/12 tester operation. No errors are seen when the SX/13 is used.
Workaround: Change the delay with gaps of approximately a minute between changes.
|
Upgrade Instructions
Upgrade boot code to boot 07 before upgrading to ABL.
Notes and Cautions
This firmware enables flash components from multiple new vendor to be used. Previous versions of firmware cannot write on to these new devices. For new cards with the flash devices from new vendors, firmware cannot be downgraded to versions prior to ABL. If this is attempted, burnfwrev will fail leaving firmware revision ABL in the flash.
Boot Code Requirements
Boot Code revision boot_07 is needed for the ABL release.
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation DVD
Cisco documentation and additional literature are available in a Documentation DVD package, which may have shipped with your product. The Documentation DVD is updated regularly and may be more current than printed documentation. The Documentation DVD package is available as a single unit.
Registered Cisco.com users (Cisco direct customers) can order a Cisco Documentation DVD (product number DOC-DOCDVD=) from the Ordering tool or Cisco Marketplace.
Cisco Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
Cisco Marketplace:
http://www.cisco.com/go/marketplace/
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Ordering tool:
http://www.cisco.com/en/US/partner/ordering/
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, USA) at 408 526-7208 or, elsewhere in North America, by calling 1 800 553-NETS (6387).
Documentation Feedback
You can send comments about technical documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — security-alert@cisco.com
•Nonemergencies — psirt@cisco.com
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one that has the most recent creation date in this public key server list:
http://pgp.mit.edu:11371/pks/lookup?search=psirt%40cisco.com&op=index&exact=on
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Obtaining Technical Assistance
For all customers, partners, resellers, and distributors who hold valid Cisco service contracts, Cisco Technical Support provides 24-hour-a-day, award-winning technical assistance. The Cisco Technical Support Website on Cisco.com features extensive online support resources. In addition, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not hold a valid Cisco service contract, contact your reseller.
Cisco Technical Support Website
The Cisco Technical Support Website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, 365 days a year, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support Website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco TAC engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco TAC engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
CCSP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, SwitchProbe, TeleRouter, The Fastest Way to Increase Your Internet Quotient, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0501R)
Copyright © 2005, Cisco Systems, Inc.
All rights reserved.
