|
|
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
This is the second release of BPX SES PNNI. New features will be added in subsequent releases.
SES PNNI 1.0 is compatible with the BPX 8600 series software release 9.2.33, and is connected to the BPX 8600 series switch via a BXM-155 (or T3/E3) port configured as a trunk. Redundant SES systems contain two controller cards which offer APS protection on the ports connecting to the BPX.
The SES is a VSI (Virtual Switch Interface) controller which provides a BPX 8600 series wide-area switch the capability to create Switched Virtual Circuits (SVCs) and Soft Permanent Virtual Circuits (SPVCs) using the UNI and PNNI protocols. One SES is required per BPX 8600 series node that will be originating, transporting, or terminating SVC/SPVC connections. The SES is offered in redundant or non-redundant configurations.
As networks grow in size, PNNI becomes a critical element in the ability to scale a network. PNNI provides a standard, interoperable, and scalable method to grow PVC (SPVC) networks to very large sizes. In addition, applications such as voice, video, and LAN required WAN switches to provide dynamic connection capabilities in the form of SVCs. The SES provides the BPX 8600 series switch with a centralized and highly reliable processor for establishing SPVCs and SVCs in both BPX 8600 series networks and in mixed vendor environments. The BPX 8600 series switch with SES (Release 1.0) supports the following standards:
N/A
N/A
This section provides instructions for loading the runtime images from 1.0.00 to 1.0.01.
For Redundant Systems, follow these steps:
Step 1 Upgrade the standby PXM1 boot code. (It should now have the 1.0.00 runtime image with the 1.0.01 boot image)
Step 2 Reset the active card. It now comes up as the standby card.
Step 3 Upgrade the boot image on the standby card.
Step 4 On the Active card, use the setrev command to load the 1.0.01 release:
Step 5 setrev <slot number> <primary version> <secondary version>
Step 6 For example: setrev 1 1.0(1) 1.0(1)
For non-redundant systems, follow these steps:
Step 2 Login to the shell using the sh command.
Step 3 At the shell, run the revChgIgnoreStandby command.
Step 4 Return to the CLI, by typing the command cc 1.
Step 5 At the CLI, use the setrev command to load the 1.0.01 release.
For example, assuming the card is in slot 2:
setrev 2 1.0(1) 1.0(1)
After approximately 90 seconds the system will reboot with the new image.
For detailed information on how to upgrade backup boot etc, refer to the SES Configuration Guide.
In reference to Cisco SES PNNI Controller Software Configuration Guide Release 1.0, May 2000, Chapter 8 "SES PNNI Controller Setup and Initial Configuration", the following changes need to added to the "Bring Up the SES PNNI Controller" section (on page 8-14):
1. Between step 1 and step 2, add one more step to configure the uplink to be a trunk Service Class Template. Do cnfvsiif slot.port 3.
2. For original step 2, cnfrsrc command must avoid using VPI=3 for VSI partition. The valid Start/End VSI VPI can be either 1/2 or 4/4095.
For detailed procedure changes, please see the on-line SES PNNI Controller Software Configuration Guide at:
http://www.cisco.com/univercd/cc/td/doc/product/wanbu/ses/pnnicnf/index.htm
SES PNNI consists of the following software:
For further information on BPX SWSW 9.2.33 release, please see the release notes located on CCO.
In addition, the following bug CSCdr67236 was found on the 9.2.33 release that is only applicable to the SES PNNI release. The information on CSCdr67236 is as follows:
:
| Bug ID | Description |
CSCdr67236
| Symptom: BXM card's system time is not sync with network time. Condition: Occurs when there is a change in network time (Via the cnfdate command) and there is no ESP feeder on the node (this is obsoleted in 9.2). When there is a change in network time, sw sends "time change event" (0x0a/0x50) if there is an ESP feeder on the node. Workaround: Resetting the BXM card triggers a 0x50 message from sw. Please note that this event is a service effecting one. For redundant BCC configurations, the switchcc command insures that a 0x50 message is sent to all the BXM cards after a switchover. This syncs up the time between the BPX and the BX |
For further information on the BXM card, please see Appendix A. Note, the SES PNNI 1.0.01 is compatible with MFD BXM (See Table 1 for more information.)
Release 1.0.01of the SES has the following limitations:
N/A
SES PNNI | BXM Firmware |
SES PNNI 1.0.00 | MFC |
SES PNNI 1.0.01 | MFD |
OC3 Combinations (Shipping/Customer Configurations) | ||||
No. | Description | Front Card (PXM) | PXM UI Back Card | PXM Uplink Back Card |
1 | MMF OC3 | SES-PXM-CNTL-4-155 (with 4 port OC3) P/N 800-06454-01 or later | PXM-UIA Rev: 05 or later | MMF-4-155 Rev: 09 or later |
2 | SMF-OC3, Intermediate Range | SES-PXM-CNTL-4-155 (with 4 port OC3) P/N 800-06454-01 or later | PXM-UIA Rev: 05 or later | SMFIR-4-155 Rev: 09 or later |
T3/E3 Combinations (Shipping/Customer Configurations) | ||||
No. | Description | Front Card (PXM) | PXM UI Back Card | PXM Uplink Back Card |
1 | T3 | SES-PXM-CNTL-2T3E3 (with 2 port T3E3) P/N 800-06699-01 | PXM-UIA Rev: 05 or later | BNC-2T3 Rev: 03 or later |
2 | E3 | SES-PXM-CNTL-2T3E3 (with 2 port T3E3) P/N 800-06699-01 | PXM-UIA Rev: 05 or later | BNC-2E3 Rev: 03 or later |
The following is the list of known anomalies in this SES PNNI delivery. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator.
The following bugs are applicable on to the PXM1 software:
| Bug ID | Description |
|---|---|
S1 BUGS |
|
None | None |
S2 BUGS |
|
CSCdr46210 | Symptoms: CLI sessions do not respond. Ctrl-@ on console gets CLI to respond. dsplog shows SYS-3-STARVETASK for the CLI Cmd Tasks (tDbgCmdTsk or tTnCmdTskXX) and/or CLI In tasks (tDbgInTsk or tTnInTskXX). Conditions: Unknown Workaround: None |
CSCdr50433 | Symptoms: During SNMP operation, sometimes an SNMP request timeout would occur. Conditions: It is observed this condition is usually associated with heavy load on the switch as well as with network congestion. Workaround: None |
CSCdr59624 | Symptoms: Active PXM card in the SES-Controller node resets sometimes and dsplog will show a "FAT_HW_MSTRSHIP" log with message "Local Card Lost H/W Mastership unexpectedly..". Conditions: A SES node is connected via a trunk to BPX and all the BXM cards on BPX are pulled out and put back in. Workaround: Currently there is no workaround available for this. |
CSCdr62399 | Symptoms: When a pnni command is executed when the cli is displaying the prompt indicating that the cli is in the init state, it can cause the cli command task for that session to get a task exception. Conditions: When the cli is displaying the prompt with a ".i", for example: hostname.7.pxm.i> it means that the system is still booting up. Some commands are currently not blocked in this state. Workaround: Do not issue configuration commands until the cli issues the prompt: hostname.7.pxm.a> |
CSCdr63110 | Symptoms: Port status is UP but the calls are not routed on that port configured as trunk. Conditions: The problem has occurred once only while upgrading the old image with the new one. The trunks had ILMI configured. Workaround: Down the port and up the port. |
CSCdr63396 | Symptoms: Mismatch in number of spvcs on active and standby. Error log on the active says there is a null pep for some record. Conditions: resetsys did not work properly. One time occurrence. WorkAround: Do manual reload of system or resetsys again.
|
CSCdr66271 | Symptoms: Active calls were not released Conditions: Resetcd on feeder BXM card. Workaround: None. |
CSCdr68627 | Symptoms: Port/ports on a node stays in building VC. Conditions: The problem occurs once when BXM and PXM software are upgraded simultaneously. Workaround: Reload the BXM card(s), which is having the port(s) stuck in building VC. |
CSCdr70711 | Symptoms: Interfaces remain in Down State though interface is physically up and ILMI on the interface is also up. Conditions: This has been observed only once and happened when BPX-SES was undergoing overnight script based testing. As part of the test, the following sequence of operations were being performed continuously: Step 1 Down all ports. Step 2 Wait for 5 minutes. Step 3 Perform PXM switchover. Step 4 Wait fro 5 minutes. Step 5 Up all ports. Step 6 Wait for 30 minutes. Step 7 Perform PXM switchover. Step 8 Repeat the above sequence 1 -7. Workaround: None |
CSCdr73156 | Symptoms: Ports stay in "VC Failure" after simultaneous switchcc on BPX(BCC) and SES(PXM1). Conditions: Switchcc is performed on both BPX(BCC) and SES(PXM1) at the same time and repeatedly. The control VCs do not get any bandwidth to establish the connections and they stay in "VC failure". Workaround: None. |
CSCdr74764 | Symptoms: Some ports stuck in vc failure Conditions: The sequence is: Step 1 All the BXM cards, including the one having the feeder is pulled out Step 2 Wait for 30/35 seconds Step 3 All the BXM cards pressed-in (energized again). The problem occur once only but could not reproduce the same in subsequent retries. Workaround: None. |
CSCdr74981 | Symptoms: SLT - SSCOP&PNNI down on a port after switchover Conditions: One time occurrence. Not a reproducible problem. Waiting for a reoccurrence. Workaround: None. |
CRCdr79202 | Symptoms: Created PVC's with VPI = 0 and VCI = 7, 17, 27, 37, 47, 57, 67 and only the first connection showed up on the switch. All of the connections got created though. Conditions: Any time PVCs are created with VPIs set to 0. Workaround: Turn on service template 3 for a feeder trunk. This turns policing off for all the SPVC terminating on it.
|
S1 BUGS:
| Bug ID | Description |
|---|---|
S1 BUGS |
|
CSCdr28772 | Symptom: Some pnni ports with ILMI on go down temporarily and come up. The calls are derouted and rerouted back. Conditions: This happens on a large network which has 50k spvc endpoints. The node has at least 14 trunks spread across 6 BXM cards. Pull out one of the cards and re-insert the card. Workaround: None. |
CSCdr40383 | Symptom: The exception log from crash is lost from dsperr after system reset. Condition: Task monitor automatically resets a card when it crashes. Workaround: None. |
CSCdr45402 | Symptom: In some rare situation, vsi congestion bit was set. This resulted in the number of connections fail to route. Condition: Unknown. Workaround: None. |
CSCdr45891 | Symptom: 1K call drop after unplugging the active PXM card. Condition: The connection pending counter was 1532 (threshold is 500). This was due to message drops on the SIGAPI Epid. Workaround: None. |
CSCdr46104 | Symptom: Exception in pnCcb task causing the active processor to reset. Condition: Observed on derouting and rerouting SPVCs over an IISP link. Workaround: None. |
CSCdr46257 | Symptom: SPVCs are getting rerouted on different NNI ports. They are released and then gets routed on different port. Condition: If we do many (>4) consecutive switchovers then sometime this happens. WorkAround: Please avoid doing more than 3-4 consecutive switchovers or overnight switchovers. |
CSCdp93160 | Symptom: When errors are injected on the working line, the working line status changes from OK to an alarm state (depending on the bit-error rate, the state could be SigF, ALM or some other state). The protection line should still be OK and APS should switch to the protection line. If CSCdp93160 (this bug) happens, the errors injected on the working line also show up on the protection line, causing its status to change from OK to one of SigF, ALM or other similar alarm states. Therefore, the APS sub-system (wrongly) thinks that both lines are in error and switches back and forth between the two as and when it finds the protection line toggling between OK and alarm states. Due to this, traffic may be impacted. Condition: Unknown. Workaround: None. |
S2 BUGS |
|
CSCdr42002 | Symptom: If the lkup command is left at the prompt Type <CR> to continue, Q<CR> to stop: when the session times out or if ctl-C is hit when the lookup command is at this prompt then the terminal port may become locked and unusable. Condition: Unknown Workaround: Do not leave the CLI session idle while executing lkup and do not use ctl-C to exit from a lkup command. No other known workarounds. |
CSCdr43767 | Symptom: Crash of Trap Server task (trapSvrTask) on the SES-PXM. Condition: This problem occurs when there are more the 10K SPVCs setup and the BXM is unplugged. The problem is intermittent. Workaround: Do not unplug the BXM cards during operation. |
CSCdr45917 | Symptom: In some rare situation, SPVCs connections are getting dropped. This resulted in the number of connections do not match at nodes and specifically at both ends of the links. Condition: Unknown. WorkAround: None. |
CSCdr46108 | Symptom: Node stopped responding on quitting dspnni-ptse. The CLI was unavailable for typing any further commands. Condition: This one time occurrence was on a PNNI node attached to a RADCOM simulator that simulates around 100 PNNI nodes and links. The node had 5 IISP links. Workaround: None. |
CSCdr47016 | Symptom: Some spvc connections can not be added back after deletion Condition: Delete large spvc connection and re add same set of connections Workaround: None |
CSCdr47505 | Symptom: After repeated switchovers, few connections may re-route along other links. The connections and the link do recover. This is because SSCOP on a link with connections routed on it may go to Reset state temporarily and come back up. Condition: Repeated switchovers at around one per 30 minutes. WorkAround: None |
CSCdr47657 | Symptom: Rarely some SPVC connections can not be added back after deletion. Condition: Delete large SPVE connection and re-add same set of connections. Workaround: None. |
CSCdr47720 | Symptom: SPVC_ERROR "receiveReleaseComplete: null svc or softVcInfo" seen in system error log. Condition: Observed while derouting and rerouting SPVCs over IISP links by downing and upping IISP links. Workaround: None |
CSCdr47782 | Symptom: Standby PXM reloads Condition: When there is too much traffic going on to standby from Active, sometimes connection path gets congested and it may take more than 5 sec. WorkAround: None |
CSCdr47903 | Symptom: Runtime image corrupted when FTPing; PXM pair has some boot IPaddr. Condition: Unknown. Workaround: None. |
CSCdr47937 | Symptom: CWM shows connection as OK after upload. Condition: After doing an upload. Workaround: Query for chan state. |
CSCdr47997 | Symptom: Task tDbgOutTsk is suspended after you down and up the PNNI link many times. Condition: Unknown. Workaround: None. |
CSCdr48012 | Symptom: System switchover after cannot access shell mode for a while. Condition: Unknown. Workaround: None. |
CSCdr48230 | Symptom: Trunk port goes into building VC when you run the cnfrsrc command. Condition: Unknown. Workaround: None. |
CSCdr48427 | Symptom: PNNI trunk in ILMI Query after burning FW. Condition: Unknown. Workaround: None. |
CSCdr48563 | Symptom: Ports in Provisioning state with active calls. Condition: Congestion caused by faulty feeder trunk. This is a very infrequent. Workaround: None. |
CSCdr48832 | Symptom: PNNI database took too long to update after down/up link (SLT). Condition: Unknown Workaround: None. |
The SES PNNI Controller MIB is being provided with the delivery of Release 1.0.00 of the SES PNNI Controller software on CCO. The MIB is in standard ASN.1 format and is included in the same directory where the SES PNNI Controller software is located within CCO. The SNMP SES PNNI Controller MIB file can be compiled with most standards-based MIB compilers.
Refer to Appendix E, SNMP Management Information Base, in the BPX SES PNNI Controller Software Configuration Guide, Release 1.0.01 for a description of the MIBs supported by the SES PNNI controller.
There have been no changes.
For service and support for a product purchased from a reseller, contact the reseller. Resellers offer a wide variety of Cisco service and support programs, which are described in the section "Service and Support" in the information packet that shipped with your chassis.
 |
Note If you purchased your product from a reseller, you can access Cisco Connection On-line (CCO) as a guest. CCO is Cisco Systems' primary, real-time support channel. Your reseller offers programs that include direct access to CCO's services. |
For service and support for a product purchased directly from Cisco, use CCO.
Cisco Connection Online (CCO) is Cisco Systems' primary, real-time support channel. Maintenance customers and partners can self-register on CCO to obtain additional information and services.
Available 24 hours a day, 7 days a week, CCO provides a wealth of standard and value-added services to Cisco's customers and business partners. CCO services include product information, product documentation, software updates, release notes, technical tips, the Bug Navigator, configuration notes, brochures, descriptions of service offerings, and download access to public and authorized files.
CCO serves a wide variety of users through two interfaces that are updated and enhanced simultaneously: a character-based version and a multimedia version that resides on the World Wide Web (WWW). The character-based CCO supports Zmodem, Kermit, Xmodem, FTP, and Internet e-mail, and it is excellent for quick access to information over lower bandwidths. The WWW version of CCO provides richly formatted documents with photographs, figures, graphics, and video, as well as hyperlinks to related information.
You can access CCO in the following ways:
For a copy of CCO's Frequently Asked Questions (FAQ), contact cco-help@cisco.com. For additional information, contact cco-team@cisco.com.
|
Note If you are a network administrator and need personal technical assistance with a Cisco product that is under warranty or covered by a maintenance contract, contact Cisco's Technical Assistance Center (TAC) at 800 553-2447, 408 526-7209, or tac@cisco.com. To obtain general information about Cisco Systems, Cisco products, or upgrades, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com. |
BXM Firmware version M.F.D. supports all the existing interfaces and models of BXM hardware. Following table outlines various levels of hardware revisions supported for BXM firmware version M.F.D.
| Model Num | Description | FW model | HW Rev | FW Rev |
|---|---|---|---|---|
BXM-155-4 | 4 port OC3 Line Module (Front Card) | F | B | MFD |
BXM-155-8 | 8 port OC3 Line Module (Front Card) | F | B | MFD |
BXM-622 | 1 port OC12 Line Module (Front Card) | F | D | MFD |
BXM-622-2 | 2 port OC12 Line Module (Front Card) | F | D | MFD |
BXM-T3-8 | 8 port T3 Line Module (Front Card) | F | B | MFD |
BXM-T3-12 | 12 port T3 Line Module (Front Card) | F | B | MFD |
BXM-E3-8 | 8 port E3 Line Module (Front Card) | F | B | MFD |
BXM-E3-12 | 12 port E3 Line Module (Front Card) | F | B | MFD |
BXM-155-8DX | 8 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-8D | 8 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-4DX | 4 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-4D | 4 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-622-2DX | 2 port OC12 Line Module (Front Card) | F | A0 | MFD |
BXM-622-2D | 2 port OC12 Line Module (Front Card) | F | A0 | MFD |
BXM-622-DX | 1 port OC12 Line Module (Front Card) | F | A0 | MFD |
BXM-T3-12EX | 12 port T3 Line Module (Front Card) | F | A0 | MFD |
BXM-T3-12E | 12 port T3 Line Module (Front Card) | F | A0 | MFD |
BXM-T3-8E | 8 port T3 Line Module (Front Card) | F | A0 | MFD |
BXM-E3-12EX | 12 port E3 Line Module (Front Card) | F | A0 | MFD |
BXM-E3-12E | 12 port E3 Line Module (Front Card) | F | A0 | MFD |
BXM-E3-8E | 8 port E3 Line Module (Front Card) | F | A0 | MFD |
| Model Num | Description | FW model | HW Rev | FW Rev |
|---|---|---|---|---|
BXM-155-4 | 4 port OC3 Line Module (Front Card) | F | C | MFD |
BXM-155-8 | 8 port OC3 Line Module (Front Card) | F | C | MFD |
BXM-622 | 1 port OC12 Line Module (Front Card) | F | E | MFD |
BXM-622-2 | 2 port OC12 Line Module (Front Card) | F | E | MFD |
BXM-155-8DX | 8 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-8D | 8 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-4DX | 4 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-155-4D | 4 port OC3 Line Module (Front Card) | F | A0 | MFD |
BXM-622-2DX | 2 port OC12 Line Module (Front Card) | F | A0 | MFD |
BXM-622-2D | 2 port OC12 Line Module (Front Card) | F | A0 | MFD |
BXM-622-DX | 1 port OC12 Line Module (Front Card) | F | A0 | MFD |
| Model Num | Description | HW Rev | FW Rev |
|---|---|---|---|
MMF-155-4 | 4 port multi-mode fiber back card | A | na |
MMF-155-8 | 8 port multi-mode fiber back card | A | na |
SMF-155-4 | 4 port single-mode fiber intermediate-reach back card | A | na |
SMF-155-8 | 8 port single-mode fiber intermediate-reach back card | A | na |
SMFLR-155-4 | 4 port single-mode fiber long-reach back card | A | na |
SMFLR-155-8 | 4 port single-mode fiber long-reach back card | A | na |
SMF-622 | 1 port intermediate-reach OC12 back card | A | na |
SMF-622-2 | 2 port intermediate-reach OC12 back card | A | na |
SMFLR-622 | 1 port long-reach OC12 back card | A | na |
SMFLR-622-2 | 2 port long-reach OC12 back card | A | na |
XLR-622 | 1 port extra long-reach OC12 back card | A | na |
XLR-622-2 | 2 port extra long-reach OC12 back card | A | na |
BPX-T3/E3-12 | 12 port T3/E3 back card | A | na |
BPX-T3/E3-8 | 8 port T3/E3 back card | A | na |
RDNT-LR-622-2 | 2 port long-reach OC12 redundant back card | A | na |
RDNT-SM-622-2 | 2 port intermediate reach OC12 redundant back cards | A | na |
RDNT-SM-622 | 1 port intermediate reach OC12 redundant back cards | A | na |
RDNT-LR-155-8 | 8 port long-reach OC3 redundant back cards | A | na |
RDNT-SM-155-4 | 4 port intermediate-reach OC3 redundant back cards | A | na |
RDNT-SM-155-8 | 8 port intermediate-reach OC3 redundant back cards | A | na |
None
None
The following new features are supported in BXM Firmware MFC:
The following new features are supported in BXM Firmware MFB:
The following new feature is supported in BXM Firmware MFA:
There is no new feature in release MEC
There is no new feature in release MEB
The following new features are supported in BXM Firmware MEA:
| BIP count | Condition |
|---|---|
10^-4 | SF detected |
10^-5 | SD detected & SF clear |
10^-6 | SD clear & SF clear |
The following new features are supported in BXM Firmware MDA:
BXM cards with M.C.B/M.D.A firmware or later can be smoothly migrated to the M.F.A or above version of firmware by using y-cable redundancy. To upgrade a BXM card pair in y-red configuration, first upgrade the standby card with the MFA or above firmware version and wait for all the configuration to be downloaded into the card. Do a switchyred to switch to the card with firmware M.F.A or above version and burn the other card also with desired version MFA or above firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.
If BCC swsw version is 9.1.18 and dspnovram shows 0 or 4 for Number of Channel Stats it should be OK to go directly to MFC or above versions directly from MCC.
The following features are obsolete in 9.0.01:
Switch Software should be upgraded to 9.2.30 or higher. Upgrade the firmware to MFD. When upgrading the firmware from a revision lower than MEA, the firmware should be upgraded to MEC. Follow these steps:
Step 1 upgrade the swsw to 9.2.30 or higher revision
Step 2 upgrade the firmware to MFD to avoid the card mismatch.
Step 3 Burn firmware should not be interrupted. Card resets in the middle of burn firmware will result in the BXM being maintained in the core state (Identified by blinking yellow LED), or failed state (Identified by a solid red led). In this case the dspcds screen will report the card as FAILED. This state can be recovered by reburning the firmware into the card.
Step 4 Protection Switching based on BER on BXM may not comply to standards. The GR-253 & ITU-T G.783 requires that switching be completed within 60 msec from the time the error starts. BXM is unable to detect BER threshold crossing until the next poll, which occurs every 250 msec. Thus, switching time may be up to 250 msec under certain circumstances.
Step 5 In APS 1+1 default configuration, both backcard LEDs show green when primary card is active and selection is from PROT line. When primary card is active and it is selecting from PROT, PROT backcard should be green, since it is carrying traffic. WORK backcard should also be green since that is the physical path for the primary (and active) card to pass traffic. So backcard LED green means the backcard is directly or indirectly carrying traffic and pulling the backcard will cause traffic disruption. (CSCdm53430)
Step 6 In APS 1+1 default configuration and a manual W->P is on and a switchyred is issued, a manual W->P event is logged. By default, on switchyred the new active card comes up in "clear" state. But in this case since there is a manual W->P on, the APS line switches to PROT and the switching is logged. (CSCdm53404)
Step 7 In APS 1+1 default configuration if the selected line is PROT and last user request is clear and a switchyred is issued, line switches to WORK. If the last user request is "clear", full automatic APS switching is in effect with the working line being active by default. When there is no last user switch request to switch to any particular line, the working line will become active. (CSCdm53420)
Step 8 When APS Annex B is added to local end which has the Secondary card active, the APS trunk goes into Comm Failure for few seconds and then clears. If Secondary card is active, then do a switchyred to make Primary card active and then add APS Annex B. (CSCdm46359)
The following is the list of known anomalies for the BXM firmware:
CSCdp05098 | Symptoms: 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 connections 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. |
CSCdr27107 | Symptoms: Connection DB discrepancies between Y-red BXMs. Conditions: When resetcd is executed on active card, database might be in a transient state and the two cards should converge after the reset is completed. Workaround: None |
CSCdr36808 | Symptoms: SPVC reroute fails even there are still some resources. Conditions: Intermittent Workaround: None |
CSCdr43015 | Symptoms: Card error 0x12000003 logged continuously as RCMP lookup fails. Condition: Happened once, reason unknown Workaround: None. |
CSCdr43455 | Symptoms: Card errors after the Yred switchover. Conditions: This happens during the transition from active to stdby after the switchover. It doesn't affect any connection Workaround: It doesn't affect any connection. |
CSCdp67546 | Symptoms: On the same error, dspapsln shows error messages different if the remote connected to POPEYE VS BPX. Condition: Configure APS to bi-direction and the other end as UNI on both the POPEYE and BPX node. Workaround: None |
CSCdp67775 | Symptoms: APS does not clear last user request after SF switch. Conditions: Jan 1999 edition of GR-253-CORE (issue 2, Revision 2, section 5-92 which supersedes the document you are quoting) Workaround: None. |
CSCdp05098 | Symptoms: 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 connections 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. |
CSCdr42996 | Symptoms: APS 1:1 does not support VSI. Configured port experiences traffic loss on switchover. Conditions: Always. Workaround: None |
CSCdr29278 | Symptoms: 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). Condition: The cause is unknown. Workaround: None |
CSCdp63445 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 | Symptoms: All the ports on a BXM slave go into provisioning state. Condition: 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 | Symptoms: Invalid Part id in SPVC stats after controller is added. Conditions: 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. Workaround: None |
CSCdr40234 | Symptoms: 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 | Symptoms: 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: None |
CSCdr43012 | Symptoms: 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 | Symptoms: All the ports on a BXM slave go into provisioning state. Conditions: Controller loses communication with the BXM as AAL5 driver in BXM gets stuck. Workaround: Reset the BXM card. |
CSCdr36963 | Symptoms: 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: 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. 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 | Symptoms: 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 | Symptoms: 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 | Symptoms: Virtual Trunking causing Unreachability Conditions:
node_A ---- vtrk ---- /---- vtrk ---- node_C / / node_B (vtrks share common port)
Workaround:
|
CSCdr57805 | Symptoms: 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 |
CSCdr56931 | Symptoms: 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 over-indexing the CAC structures. Workaround: None |
CSCdr59241 | Symptoms: 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 | Symptoms: 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 | Symptoms: The encoding is in the reverse of the expected value by UNI4.0 spec. Conditions: STD ABR connections. Workaround: None |
Bugs Fixed in MFC
CSCdp63445 | Symptoms: 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 | Symptoms: Data transfer has affected while running OAM loopback. Conditions: All user data is dropped when send in 960 cps of oam. Workaround: None |
CSCdp11511 | Symptoms: BPX treats segment oam loopback different from end-to-end oam loopback cells Workaround: None |
CSCdr13208 | Symptoms: 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 | Symptoms: BPX reports SWERR 105 Conditions: SWERR105 logged while running OAM loopback test Workaround: None |
CSCdr13182 | Symptoms: tstdelay/tstcon/tstconseg for all PVCs on that card will fail. Conditions: When user sending in >= 960 cps of oam loopback cells Workaround: None |
CSCdr13151 | Symptoms: dspportstats always show Tx port = 0 Conditions: Sending in >= 960 cps of oam loopback cells Workaround: None |
The following bugs are fixed in MFB:
CSCdm52254 | Symptoms: 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. |
CSCdp58969 | Symptoms: 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. |
CSCdp57596 | Symptoms: CB_TASK on BXM goes into deadlock state causing VSI session to be lost. Conditions: This happens when both Ingress and Egress queue semaphore is taken by IDLE_TASK and it never released in an error condition. Workaround: None |
CSCdp25220 | Symptoms: 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 |
CSCdp59328 | Symptoms: EPD bit was not set for interslave control vc Conditions: When vsi get congestion (same as CSCdp58969) Workaround: None |
CSCdp92916 | Symptoms: Commands executed on standby card affect the APS line. Conditions: Series of commands executed in stdby card affects the APS line. Workaround: None
|
CSCdp39723 | Symptoms: Aps not functioning in 9.2.21 w/FW ME18@sprintf for Bidirectional with Nonrevertive. Condition: Reversion was happening due to spurious SF/SD events.Fixed by setting the right values for SF/SD thresholds. Workaround: None |
CSCdp20848 | Symptoms: SF switchover does not 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 |
CSCdp24224 | Symptoms: 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 |
CSCdp32646 | Symptoms: 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 |
CSCdp35156 | Symptoms: 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 |
CSCdp60696 | Symptoms: 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 |
CSCdp65320 | Symptoms: 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 |
CSCdp25130 | Symptoms: APS Non-revertive bidirectional feature. Condition: Resolved Workaround: None |
CSCdp79156 | Symptom: TDP signalling cross connect VSI request rejected by BXM. Condition: If BPX is configured with trunks and virtual trunks the virtual trunks are initialized properly with qbin size. Workaround: None |
CSCdp62213 | Symptoms: Switching from bi-direction APS to un-directional APS generates mismatch err Conditions: The alarms generated while the line was in bi-dir mode was not cleared when it was changed to uni-dir mode. Fixed by clearing all alarms when re-configuring the lines. Workaround: None |
CSCdp89972 | Symptoms: 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 |
CSCdp86147 | Symptoms: 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 |
CSCdp84386 | Symptoms: Connectivity w/BXM lost due to missing DMA completion interrupts. Conditions: Aal5 driver will be in deadlock and never transmits and receives. Workaround: None |
CSCdp38148 | Symptoms: Resetcd slot 11 on BPX causes local APS switching. Conditions: Re-impose the selector and bridge states on both ACTIVE and STANDBY cards after a 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 |
CSCdm92931 | Symptoms: APS line switchover occurs up on card removal when the lockout is set. Workaround: None |
CSCdp49749 | Symptoms: Node unreachable after resetting two nodes in the network. Workaround: None |
CSCdp49640 | Symptoms: 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 |
CSCdm62817 | Symptoms: tstconseg command sometimes does not work. Conditions: Execute tstconseg multiple times with high loop count (10). Workaround: None |
CSCdm84853 | Symptoms: BW reported via interface load info is erroneous. Conditions: When Forward & Backward BW for VSI connections is different. Workaround: None |
CSCdp62213 | Symptoms: 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 |
CSCdp59729 | Symptoms: addlnlocrmt causes node unreachable. Conditions: addlnlocrmtlp causes node unreachable even though there are other parallel trunks. Workaround: None |
CSCdp67673 | Symptoms: 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: None |
CSCdp46399 | Symptoms: Need a documentation explains how to setup port groups for FW MEF (me26). Workaround: None |
CSCdp49749 | Symptoms: 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 |
CSCdp28931 | Symptoms: No RDI-P generated when loss of Cell Delineation occurs. Workaround: None |
CSCdp59727 | Symptoms: Addlnlocrmt causes node unreachable. Workaround: Reset the BXM card |
The following bugs are fixed in MFA:
CSCdm53420 | Symptoms: 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: None | ||||||
CSCdm93274 | Symptoms: 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 | ||||||
CSCdm04312 | Symptoms: 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. | ||||||
CSCdm50659 | Symptoms 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. | ||||||
CSCdm50659 | Symptoms: 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. | ||||||
CSCdk42527 | Symptoms: Rx Queue becomes full after LOS on the feeder trunk. Conditions: After LOS condition on the feeder trunk Workaround: Reset the feeder trunk | ||||||
CSCdm16505 | Symptoms: AIS not sent on VP ABRFST/ABRSTD connection. Conditions: LOS on trunk between 2 nodes. Workaround: None | ||||||
CSCdm81534 | Symptoms: ICR of abrfst on BXM-155 falls down to MCR after resetcd. Conditions: Change the ICR after resetcd before start sending traffic Workaround: None | ||||||
CSCdm61493 | Symptoms: 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 | ||||||
CSCdk81384 | Symptoms: 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 | ||||||
CSCdk80483 | Symptoms: TX cell loss counts in dsptrkerrs increase continuously. Conditions: When there is trunk configured. Workaround: None | ||||||
CSCdm04312 | Symptoms: 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 | Symptoms: Reconfiguration 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. | ||||||
CSCdm39186 | Symptoms: 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 | ||||||
CSCdm09882 | Symptoms: 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. | ||||||
CSCdm31923 | Symptoms: 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 | ||||||
CSCdm92916 | Symptoms: 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 | Symptoms: APS line switchover occurs upon card removal/insertion when lockout is set. Conditions: When Lockout is set, removing/inserting the card makes it happen. Workaround: None | ||||||
CSCdm52585 | Symptoms: 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. | ||||||
CSCdp18840 | Symptoms: The CBR.2 Calls do not pass traffic above 50 Cells/second. Condition: VSI controller establishes CBR.2 connection and it does not fill in the PCR field. Workaround: Fill the PCR value as lo with the CR value. | ||||||
CSCdp17741 | Symptoms: 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. | ||||||
CSCdp22930 | Symptoms: Intlock missing for rd/wr operation. Workaround: Reassert intLock on commbus ISR to prevent SCC access from getting interrupted | ||||||
CSCdp33894 | Symptoms: 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. | ||||||
CSCdp36324 | Symptoms: Last user request affects switching on BPX. Workaround: None | ||||||
CSCdp31325 | Symptoms: UBR cells are policed unnecessarily below PCR. Conditions: Always. Workaround: None. | ||||||
CSCdp36155 | Symptoms: BXM-E OC3/OC12 does not show supporting APS HW 1+1 in dspcd command and otherwise also. Conditions: BXM-E OC3/ OC12 card with HW rev <'C' Workaround: None. | ||||||
CSCdp32853 | Symptoms: The BXM enhanced cards keep getting reset and card errors are logged and node may go into degraded mode, when the following command is issued: addapsln slot1.port1 slot2.port2 1 Conditions: BXM enhanced OC3 cards with 4 port and FW rel earlier that M.E.22/M.F.09 Workaround: Do one of the following:
| ||||||
CSCdp17741 | Symptoms: 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. | ||||||
CSCdp11025 | Symptoms: 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:
Workaround: None | ||||||
CSCdm73220 | Symptoms: 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 |
The following bugs are fixed in MEC
CSCdm66131 | Symptoms: After addapsln trunk goes to LOS Conditions: Both ends have secondary card active, add aps 1+1 to one end, then add aps to the other end, the trunk sometimes goes into LOS. Workaround: None |
CSCdm64366 | Symptoms: APS 1+1 manual switch sometimes does not work after a while after several manual switch and auto switch. Conditions: Secondary card is active and several manual switch and auto switches are performed. Workaround: None |
CSCdm62809 | Symptoms: APS 1+1 bidirectional non-revertive switches back to working line when line condition clears on working. Conditions: APS 1+1 configured in bidirection non-revertive mode. Working line is in LOS, current active line is protection, clear LOS on working line. Workaround: None |
CSCdm69974 | Symptoms: Card errors (0x25170076) occur when only one Virtual Trunk is configured in a physical port. Workaround: To avoid this situation, configure at least 2 virtual trunks on any physical port that you have VTs on. It is imperative to configure the VTs one directly after the other. |
CSCdm65813 | Symptoms: APS switches back o working line incorrectly. Conditions: Switch sequence W->P, P->W and then W->P, then cause LOS on WORK line and put the cable back, APS switches to Working line. Workaround: None |
CSCdm77212 | Symptoms: 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: For previous releases the stats level for oc3 card should not be 0 level. |
CSCdm74316 | Symptoms: 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, So the message gets dropped on BXM, so VSI controller is in discovery state forever. Workaround: None |
CSCdm75722 | Symptoms: No control VC after BXM is reset. Conditions: When resync request comes down from the VSI controller with 19 checksum blocks, the length check done on BXM does not include padding. Workaround: None |
CSCdm74968 | Symptoms: 0B card error causing BXM to reset Conditions: Over night jobs running on controller cards. Workaround: None |
CSCdp02190 | Symptoms: tstdelay timed out when going through BNI trunk Conditions: More that 12 VTs on an interface causes wrong port-vi mapping while considering STI_SHIFT/NO_SHIFT from 13 th VT/port onwards. Workaround: None |
CSCdm78335 | Symptoms: dspvsistatus rarely shows the VSI programming status as Done. Conditions: Primary and secondary port has two different VPI range. Workaround: None |
CSCdm26752 | Symptoms: Card errors continuously logged with "SoItcSend failed" message. Conditions: RAS oam_lpbk is on and switchyred is executed several times in a job. Workaround: Turn off oam loopback through cnfoamlpbk command. |
CSCdm93839 | Symptoms: Card resets on receiving oam loopback cells at high rate. Conditions: oamlpbk is enabled with high oam traffic on large number of connections. Workaround: Ignore BIP-8 errors when the T3 trunks are configured in the HEC mode. |
CSCdm52254 | Symptoms: BIP-8 code errs occurs on routing trunks. Conditions: T3 card used in HEC mode can randomly have this problem. Workaround: None |
CSCdm44183 | Symptom: BXM-155 4DX was not able to recover after resetting the card Condition: Traffic is sent at a rate >= 383 cps on a terminated connection on BXM-E card and then card is reset. Workaround: None |
CSCdm90997 | Symptoms: BXM-E trunk and port stats are always zero in TX direction. Conditions: Port terminated on BXM-E card or trunk passing through BXM-E card. Workaround: None |
CSCdm80991 | Symptoms: 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: Before adding Feeder shelf to BXM trunk, configure BXM trunk (using the cnftrk command) with "Protocol by the Card" as NO and then, add shelf. If you want card based ILMI/LMI, run cnftrk again to reconfigure option. If you have already added a shelf to the BXM trunk, and the ILMI/LMI protocol is card based from very beginning, follow these steps: Step 1 set the "Protocol by the Card" parameter as NO. Step 2 reconfigure the trunk.back to card based protocol. |
CSCdm82688 | Symptoms: Traffic Shaping problems with VT with and without wraparound solution. Conditions: Large deviations in CDV values Workaround: The workaround in FW is to always round the ICG up to the nearest integer, which will result in a large granularity of the shaped rates (especially at the higher rates), but will ensure that the transmit rate is always less than or equal to the configured rate. transmit rate = 1470588 / round_up_integer(1470588/configured rate) |
CSCdm94372 (see explanation below) | Symptoms: Trunks sometimes drop cbr traffic. Condition: If a trunk is configured to full line rate on BXM cards, then traffic is dropped Workaround: None |
CSCdp00063 | Symptoms: 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 is as follows (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
If a trunk is configured at 100,000 CPS, the actual transmitted cell rate is 98,013 CPS. Any traffic sent over 98,013 CPS would be discarded. Therefore, 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 |
The following is the list of bugs fixed in release MEB:
CSCdm50469 | Symptoms: Software error 105 and malloc 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 | Symptoms: 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. Condition: When tx cell rate of a trunk is reduced to zero, BXM card fails with break point error (division by zero). Workaround: None |
The following is the list of bugs fixed in release MEA:
CSCdm09882 | Symptoms: Log non fatal message related to RCMP errors. Conditions: It is mainly seen in the heat chamber. Workaround: None |
CSCdm18186 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 | Symptoms: Trunks go to Communication Fail after burning firmware. Conditions: When MC10 is burnt into BXM-OC12 with trunks. Workaround: None |
CSCdm37709 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 |
The following is the list of bugs fixed in release MDA:
CSCdm38647 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 | Symptoms: 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 |
BXMMFD.000 65536
BXMMFD.001 65536
BXMMFD.002 65536
BXMMFD.003 65536
BXMMFD.004 65536
BXMMFD.005 65536
BXMMFD.006 65536
BXMMFD.007 65536
BXMMFD.008 65536
BXMMFD.009 65536
BXMMFD.010 65536
BXMMFD.011 65536
BXMMFD.012 65536
BXMMFD.013 65536
BXMMFD.014 65536
BXMMFD.015 65536
BXMMFDMFD.016 65536
BXMMFD.017 65536
BXMMFD.018 65536
BXMMFD.019 65536
BXMMFD.020 65536
BXMMFD.021 31008
BXMMFD.022 14
BXMMFD.023 2
BXMMFD.IMG 784
BXMMFD.img 784
Posted: Tue Jul 18 17:14:31 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.