|
|
Cisco documentation and additional literature are available in a CD-ROM package, which ships with your product. The Documentation CD-ROM, a member of the Cisco Connection Family, is updated monthly. Therefore, it might be more current than printed documentation. To order additional copies of the Documentation CD-ROM, contact your local sales representative or call customer service. The CD-ROM package is available as a single package or as an annual subscription. You can also access Cisco documentation on the World Wide Web at http://www.cisco.com, http://www-china.cisco.com, or http://www-europe.cisco.com.
If you are reading Cisco product documentation on the World Wide Web, you can submit comments electronically. Click Feedback in the toolbar, select Documentation, and click Enter the feedback form. After you complete the form, click Submit to send it to Cisco. We appreciate your comments.
The 9.2.10 software release supports the Cisco WAN switching products (including the Cisco BPX 8600 series switches and the Cisco IGX 8400 series switches, but not the IPX narrowband switches). It is recommended for networks with IGX 8400 series switches or mixed networks with IGX 8400 series switches and BPX 8600 series switches.
Including all features supported in release 9.2.01 and release 9.2.00 and introducing the following additional features:
1. Support for Virtual Switch Interface (VSI) 2.2
2. Support for 16K connections
3. Support for UXM VP tunneling
4. Support for APS Annex B
5. Support for Multiple Protocol Label Switching (MPLS); MPLS-Virtual Private Network (VPN); and MPLS-Class Of Service (COS) - See clarifications section for more details.
Including all features supported in release 9.2.00 and introducing the following additional features:
1. Support for Virtual Trunking on the BXM card
2. SONET line protection: APS on BXM-OC3 and BXM-OC12 (1+1)
Software release 9.2.00 introduced the following features:
1. Support for Virtual Trunking on the UXM card
2. Support for both ports and trunks simultaneously on the same UXM and BXM cards
3. Support for Hitless Rebuild including Disable Auto Bus Diagnostics
4. Support for BXM Enhanced Multi-Level Channel Statistics
5. Alarms for all service affecting events
6. Supports revision interoperability between 9.1 and 9.2
7. Supports trunk reconfiguration without outage
8. Supports ATM Forum Standard Compliant IMA with UXM (IGX 8400) Firmware Model B
9. Includes SONET line protection: APS on BXM-OC3 and BXM-OC12 (1+12 card, 1:1)
10. Support for LMI/ILMI on BXM card
11. Supports feature mismatch on BXM and UXM cards
12. Support for Idle code suppression for video on UVM and CVM cards
13. Supports VC traffic shaping on UXM ports
1. The minimum software required to run MPLS are:
2. 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 a 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.
3. The UXM VP (Virtual Path) tunneling feature provides the ability to encapsulate VPCs (Virtual Path Connections) within a VCC (Virtual Circuit Connection) through a public network that does not support Virtual Paths.
4. Automatic Protection Switching (APS) provides a network element the ability to detect a failed working line and switch the service to a spare (protection) line. 1+1 APS pairs a protection line with each working line. 1:n APS provides one protection line for every n working lines. 9.2.10 adds support for APS 1+1 Annex B redundancy which can be configured for bi-directional operation and non-revertive switching.
5. Version 2.2 of the VSI (Virtual Switch Interface) provides the BPX switch with the ability to support multiple network protocols and multiple controllers per switch (e.g., MPLS, PNNI, etc.). 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 and firmware MEA.
Following are the VSI features:
6. The combinations of system limits such as number of trunks and number of connections should be provisioned so that the node has at least 50% idle time usage. Use the command dspprfhist to verify.
7. This release does not support the BPX Early Abit Notification on connection deroute feature that was supported in release 9.1.07.
8. When cost based routing is used, increasing the cost of a trunk may result in deleting the preferred path on connections in the database if the sum of the preferred path cost exceeds the actual sum of cost. The connections will not be derouted and routed.
9. On the BXM and UXM, for the OC-3 MultiMode Fiber backcards, Y-Redundancy/hot standby is not supported due to a hardware restriction.
10. In order to maintain the database consistency between switch software and the card, after the switchcc, rebuild, or Y-redundancy switchover, switch software will first disable and then re-enable the OAM loopback feature if the feature was enabled previously. After the OAM loopback is re-enabled firmware will need to test the OAM loopback and report the status to switch software. This will cause a minimum 10 minute delay in displaying the OAM loopback status.
11. Trunk reconfiguration does not support IMA (ds0 bit map).
12. HDM to UVM interworking for Nx64K connections is not supported in this release.
| 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 current boot code version
In order to run Model B firmware on an UXM, the card needs to be running boot code revision 6 or greater. To determine the boot code running on the card, issue the following command from CLI (you must be logged in as Service level or greater to use this command):
rsh <slot #> sys version
Step 2 Upgrade UXM's boot code if necessary
The process for loading boot code is exactly the same process you would use to load firmware. The only part which changes is the name of the file.
Step 3 Upgrade UXM's firmware
Step 4 When Y-redundant trunks are used the red alarm in/out values must be configured to 1.25/1.5 seconds or greater else INVMUX failures will occur and trunk failures will be observed during a Y-redundancy switchover. Using the following command:
cnftrkparm
This is due to the IMA protocol and may cause re-route of connections.
Step 5 Upgrade NPM software to 9.2
Step 1 Upgrade BXM's firmware
Step 2 Upgrade BCC software to 9.2
Please consult your Support Representative before performing any software upgrade
Step 1 Upgrade the Tag Switch Controller (TSC)
The TSC is upgraded to CoS VSI Version capable release [IOS 12.05(T)]. This image is VSI bilingual, meaning it understands both VSI Version 1 and Version 2.
Step 2 Upgrade the BXMs
All the BXM cards in the node are upgraded to Revision E, which is VSI Version 2 and CoS capable. After each BXM card is downloaded with the Revision E image, it temporarily experiences VSI outage until the BCC software is upgraded to the 9.2.10 image. The VSI outage during the upgrade is caused by the Revision E firmware not being backward compatible with VSI Version 1 features.
Note that from the TSC perspective, after a BXM is upgraded to Revision 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 Revision 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 Release 9.2.10, the BCC recognizes the Revision 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 BPLS interfaces on the BPX. The TDP sessions are reestablished and BPLS traffic starts flowing again through the BPX.
Version 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.
The "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. The interoperability functionality uses network lowest revision for:
For a complete list of firmware versions supported, see the Compatibility Matrix document, which is included in this release package.
All processor cards must be configured with a minimum of 32 MB of RAM. This includes BCC's and NPMs. NPMs require at least 1 MB of BRAM. To verify the BRAM size on IGX 8400 nodes, use the dspcd command.
As specified below, the correct version of 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-4V | H.H.M |
| NPM Type | Firmware |
|---|---|
NPM-32 | R.B.R |
NPM-64 | R.C.R |
NPM-32B | R.E.R |
NPM-64B | R.F.R |
When upgrading the boot code on the NPM, perform 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 dncd command on the standby NPM(1) and physically reset (remove and reinsert) NPM(1). Wait until 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 dncd command on the standby NPM(2) and physically reset NPM(2)
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, as described below.
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.
Step 2 Replace with new CC front and back cards.
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.
Step 7 Replace with new CC front and back cards that are identical to the current active CC.
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.
The following features are not supported in this release:
1. OAM loop back in IGX
2. Out Of Band LAN IP address
3. Enhanced BXM
4. Enhanced UXM
1. In a BPX that contains BCC cards with 64MB, there is no legacy BXM card limitation. All 12 available slots can contain legacy BXM cards.
In a BPX that contains BCC cards with 32MB, a maximum of 10 legacy BXM cards are allowed.
2. Due to performance reasons, AIS status of connections is not sent to the standby BCC. After switchcc, it may take few minutes to update the AIS status of connections. If dspcon does not show the proper status of AIS or dspalms screen shows incorrect number of AIS, (after switchcc) wait for few minutes so that the status gets updated. (dspalms and dspcon commands show the status of AIS).
3. Hitless Rebuild has similar limitations to that of a "switchcc" and full rebuild:
4. 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.
5. Mismatch is reported when replacing a BXM card with another BXM card that has different Port Group, even though both BXM cards have identical channel numbers.
6. When upgrading from release 9.1 to 9.2, the 9.1 statistics on UXM cards are supported to maintain compatibility. However, once you configure a statistics level in 9.2, you can not revert 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 an UXM card with 9.2, a user must either:
7. The BXM and UXM channel statistics level feature gives these cards the capability of collecting more than 4 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-64 can collect at most 4 interval statistics per connection when there are 12,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 (4 x 12,000) on the BCC-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 stats enabled, etc.
With this approximation of 48,000 statistics on the BCC-64, this then means that as a rough estimate you could enable 32 stats on 1,500 connections, 48 stats on 1,000 connections or 9 stats on 5,000 connections, etc. The approximation formula being:
max_stats_per_connection = 48,000 / number_of_connections.
8. In release 9.1, the UXM card ran a proprietary IMA communication protocol. This protocol matched that used on the AXIS 4 IMATM-B cards and hence could be connected together to form a trunk. In release 9.2, we now support standards compliant IMA on the UXM card and the standards compliant IMATM-B on AXIS 5.0 is not yet released. Hence, when the network is upgraded to 9.2.10, the UXM will be running compliant IMA protocol and the IMATM-B will still be running the proprietary IMA communication protocol. They will no longer communicate and the trunk will fail. This will be fixed in the AXIS 5.0 release containing IMATM-B. However, it should be noted that an upgrade at that time will also incur some amount of downtime as there will be a difference in timing between the AXIS upgrade and the switch software upgrade. There should be no effect to UXM-IMA trunks connected to other UXM-IMA trunks in 9.1 to 9.2 interoperability mode.
9. We allow the transmit rate on an IGX IMA trunk to 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, we cannot add it back unless the transmit rates are the same.
10. When doing a grouped upgrade from release 9.1 to 9.2, the software error 1427 may be logged on the BPX/IGX node during non-graceful upgrade. This error can be ignored since it is harmless to the network.(CSCdm14613)
11. Reconfiguring trunk parameters may cause connection to be rerouted if the changed bandwidth load is smaller than what was used by the connections that use the trunk.
If LMI/ILMI is provided by the BCC:
The maximum number of ports on the BPX 8600 that can be configured with LMI/ILMI enabled is 36. Note that the total number of ports is 72 (for 32MB BCC) or 144 (for 64MB BCC), although only 36 of these can have LMI/ILMI enabled. This is due to the polling that must be done for the LMI/ILMI enabled ports. However, if any or all of the 16 possible feeder trunks are not being used on that specific node, then that many additional lines may have LMI/ILMI enabled. That is, if a BPX 8600 is configured with only 2 feeder trunks, then 36 + (16 - 2) = 50 lines can have LMI/ILMI enabled. Thus, the overall total can be 52 ports, when no feeder trunks exist.
If LMI/ILMI is provided by the BXM firmware:
12. Virtual Path Connections with cells whose VCI values are above 4095 will be transmitted correctly if and only if the path is exclusively through BXM trunks and terminates at BXM ports.
13. The feature of CIR=0 for Frame Relay connections is not supported for connections terminating between FRP /FRM cards in IPX/IGX nodes and FRSM cards in an MGX 8220 shelf.
14. SVC Connections are derouted after decreasing the allocated bandwidth (increasing Stat Reserve). It is the design intent that increasing the statistical reserve will cause SVC conns to derouted and not be rerouted.(See bug CSCst92308).
15. For the loadrev operation, it is important that the Cisco WAN Manager/TFTP buffers are maintained at their default size.
16. Due to a hardware limitation, the BNI trunk will send 13 -15% 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 IM-ATM pairs, which carry less than T3 bandwidth.
17. 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.
18. If the Stat Reserve field on a trunk is dramatically increased to a value which represents a significant majority of the total trunk bandwidth, then, if connections are present on the trunk, the dspload command will show negative values. This is to signify that the trunk is oversubscribed. The trunk load values will eventually reach 0, or a small positive number after all the necessary connections are routed off that trunk. (CSCdi84878)
19. When deleting trunks, there is a known limitation with the switch software. The deltrk command should always be executed on the node which remains as part of the network, rather than from the node which ends up being removed from the network. This is to ensure that all the necessary updates are sent to the rest of the network. (CSCdi85134). Also, If the command is not used as recommended here, a software error 419 could occur (CSCdi91285).
20. Due to Trunk Based Loading, any commands having to do with trunk loading and the load model (dspload chklm dsplm, etc.) need to be done only after waiting a certain period of time. This time is directly a function of the trunk load update interval time (as configurable) plus the conditional update latency time.
21. The external ABR segment control loop on ForeSight (ABRFST) is an option at the User Interface, but is not supported in hardware. The user should not enable this option on ForeSight connections (CSCdi92451). In any case, there is no coupling between the loops.
22. On a heavily loaded BPX 8600 node, during connection re-routing, the status of a particular connection is indicated as OK even though the line status of the other end of the connection is listed as failed. The connection is in fact OK, because the conditioning of the connection (to update the status for both ends) is done by a low-priority process so that the re-routing of the connections can be given high priority. The status will be eventually updated. (CSCdj10762)
23. A node whose number is greater than 63 cannot have a clrcnf operation performed on it. This is as designed. A clrallcnf can be done, or the node must be renumbered to less than 63 before running clrcnf. (CSCdj14920)
24. The interface between a BXM feeder trunk and an MGX 8220 feeder is always considered to be an NNI interface. (CSCdj16808)
25. When adding more than 4000 connections on a BPX node, the VC polling rate must be changed to a higher interval, to accommodate the additional time needed to poll for the statistics for each VC. The cnfsysparm command, parameter 24 must be changed according to the following:
0-3999 connections | Polling Rate: 5 Minutes (or higher) | |
4000-8000 connections | Polling Rate: 10 Minutes (or higher) | |
8000-12000 connections | Polling Rate: 15 Minutes | |
26. 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.
27. Because the detailed card error event log is not retained within BRAM, this information will be lost should a processor rebuild occur. Therefore, when issuing a dspcderrs command on a particular slot, the display will not show the detailed card error information should rebuild event occur. This functionality has not been modified from previous releases.
28. When a physical-layer failure (e.g., 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 only generate OAM cells from the RCMP, and the RCMP is in the ingress path, the cells must be backward routed to the egress (egress QE). Also, since end-to-end OAM cells are required, the ingress QE must be configured to drop ALL cells in the ingress path. This creates a break in continuity in the opposite direction, and AIS cells must also be generated at the other end of the same connection, in the upstream direction of the original fault.
29. There are problems in the downgrade mechanism which can cause database corruption. If downgrade is performed immediately after upgrading, the Stby_Info revision fields are not yet filled in on the new active CC. They don't get filled in until the upcard response from the new locked CC. This causes restart instead of a switchcc. If the locked CC is reset, then downgrade immediately, a restart will occur instead of a switchcc. (CSCdj30811).
30. 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).
31. BXM cards can support 32K PVC's only when no stats are collected. If collecting 4 stats per PVC is desired, the number of PVC's per BXM card drops to 16K. (CSCdj31773).
32. UBR traffic gains an advantage over ABR traffic when UBR and ABR PVC's are combined on the same network. This is because UBR and ABR PVC's share the same QBIN (Class of Service Queue) on the BXM card. ABR PVC's use a flow control mechanism, VSVD, which ensures that traffic sources slow down when the QBIN usage exceeds the EFCI threshold. However, UBR PVC's 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 PVC's are required then:
Step 1 Consider adding all best-effort PVC's as UBR, or
Step 2 Isolate the ABR and UBR paths by using the cnfpref command to ensure that ABR and UBR PVC's do not share the same queues.
Step 3 To provide UBR service on a connection, rather than setting up a UBR connection, set up an ABRSTD connection, enable VSVD, disable FCES (Flow Control External Segment), and choose policing option "5" 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 cell per second (explained later why doing 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 connection can be set at any user desired value.
Because FCES is enabled/disabled on a per port basis, UBR and ABR services are offered on different ports. However, connections carrying UBR and ABR services can share the same CoS queue inside the network and do not have to be separated.
When the network is experiencing congestion, all the affected 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 through put of 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 inside the network.
33. Combining FBTC and non-FBTC connections within a Class of Service can cause FBTC connections to not receive a fair share of bandwidth. For example, if VBR connections are added at a terminating port, and some of these VBR connections have FBTC enabled while other VBR connections have FBTC disabled, the VBR connections with FBTC disabled may obtain all of the excess bandwidth before the connections with FBTC enabled receive any of the excess bandwidth. The same holds true for ABR or UBR connections. This only is relevant where FBTC and non-FBTC connections share a QBIN, either at a port or at a trunk.
34. The maximum number of VC Parameters supported: 749 for BCC-32 MB, 2,999 for BCC-64 MB. (CSCdj48589).
VC Parameters are Virtual Circuit Parameters combinations/sets. One set of VC Parameter is used for each unique Virtual Circuit that has been provisioned. Identically provisioned Virtual Circuits (exclusive of endpoints) use the same set of parameters. Thus, on a 32MB BCC, a total of 749 uniquely configured Virtual Circuits can be provisioned.
35. Care must be taken when changing the Deroute Delay parameter, which is controlled by the cnftrk command. This parameter defaults to zero, but if it is set to anything but zero, connection re-routing due to a trunk failure will be delayed as provided by the parameter.
The logical line and logical port databases can be corrupted when an IGX has Frame Relay lines as well as ATM lines, and a rebuild or Control Card switch over occurs. This corruption is evident by the appearance the software errors 549, 886, and 2071 on a switch over or rebuild, or if a software error 928 occurs while upping an ATM line. If such a corruption is found, the database can be cleaned up. Refer to the workaround of CSCdm54814.
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 (which is a Service-level 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 node renumbering an active network, as described below.
There is a problem with node renumbering. Node renumbering (the rnmnd command) should be executed only during a stable network environment and only if absolutely necessary. A stable network environment would be, for example, one in which no connection was added for the past 30 minutes and no topology change was made in the last hour and there are no alarms or node unreachabilities. Node renumbering must only be done when the network is stable to reduce the possibility of certain temporarily blocked messages during the node renumbering process being delivered to the wrong nodes. This would occur after the completion of the node renumbering process.It is recommended that a node be renumbered prior to being added to the network.
The settling time for network wide updates can take a long time in certain situations. Specifically, the settling time for updates due to network wide topology changes and connections in a large network when a processor switchover occurs can take a long time. The time is proportional to the number of nodes as well as the number of connections. A general estimate would be 30 seconds per node. During the period of transitions (when the updates are occurring) some network operations such as adding connections might in some cases take somewhat longer to complete.
When using 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>
Users may not use the command addcon slot.1-24 v to add 24 voice connections to a CDP at once. Instead, they must separate this activity into two or more commands, so that no more than 16 connections are added at once. This is only an issue for voice connections. Data connections can be added using the "1-24" syntax. This also applies when the CDP circuit line is an E1, in which case "1-32" would apply. (CSCdj14319)
Statistics collection must be disabled prior to the start of an upgrade, prior to the issuing of the first loadrev command.
Statistics sampling must be disabled prior to the start of an upgrade (using off1/off2), prior to the issuing of the first loadrev command.
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.
Currently, T3-3 and T3-2 backcards are not interchangeable between ASI and BNI front cards, as this has been the case since the introduction of these cards. The back cards must be configured (with setnovram) so as to avoid backcard mismatch. (CSCdj41999)
In order to take advantage of the dual SIU when upgrading to the BCC-4, the BPX 8600 node must have a new back plane which has dual traces for incorporating with the BCC-4.
The command dspbpnv can be issued to verify if the node has the new back plane or the old back plane. The following table details the bit fields for the BCC Backplane NOVRAM format, the display of word 2 describes the back plane type:
| 16 Bit Word | Byte # (hex) | Contents |
0 | 0,1 | Hardware revision |
1 | 2,3 | Backplane Type (usually 0x65=101 decimal) |
2 | 4,5 | Backplane version (0x0000:old 0x0001:new) |
3 | 6,7 | Backplane serial number in ASCII - MSB |
4 | 8,9 | " |
5 | A,B | " LSB |
6 | C,D | Board FAB number, in ASCII - MSB |
7 | E,F | " |
8 | 10,11 | " |
9 | 12,13 | " |
A | 14,15 | " |
B | 16,17 | " LSB |
C | 18,19 | Unused |
D | 1A,1B | Unused |
E | 1C,1D | Unused |
F | 1E,1F | Checksum bytes - CURRENTLY NOT SUPPORTED |
With regards to statistics collection, the peak statistics collection intervals are controlled to be only those values for which peaks can be accurately collected The rules for peak intervals are as follows:
There are additional commands to control trunk and line loopbacks in this release:
The card synchronization (Hitless-Switchcc) feature can be turned on/off using the on3/off3 command (which is a StrataCom-level command). For example, enter at the command line:
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.
The following is the list of known anomalies in this Switch Software delivery. Included with each is a brief discussion of the problem. A more in depth discussion is available in the release note enclosure of the problem record in Bug Navigator
| Bug ID | Description |
|---|---|
CSCdi85160 | Symptom: Occasionally, when burning firmware, the process does not complete successfully. An error message is logged in the event log. Workaround: Since the process of burning firmware usually works, just try again. If the node is unstable due to problems in the network, wait until things settle down. |
CSCdj89081 | Symptoms: The VC queue threshold at a via node trunk uses a high default value 0xcfc95 and is not changeable by the value provisioned at the end point. Thus the thresholding mechanism using the VC queue at a via node most likely is not effected. Note that the VC queue at the trunk on the first hop is programmed correctly. Conditions: When there are multiple connections that go through the same trunk, ideally the VC queue thresholds specified at the ingress endpoints should be used at the via. Thus the VC queue thresholds are not effected at the via which could cause unfairness in traffic usage. Workaround: None. |
CSCdk04032 | Symptom: UVM connections do not show slot number in the event log, and show the incorrect channel number if the connection terminates on the second line. Conditions: The defect will be observed for any event log entry for a connection terminated on a UVM card. The format of the connection in the event log is displayed as slot.channel, rather than slot.line.channel. The channel displayed is the internal database channel (plus one for display). It is correct, but is not the format expected by the user. Workaround: The channel displayed is the actual channel used for the connection, plus one. The UVM has 31 channels for each line. Thus subtract 31 from the channel displayed in the event log for any connection terminating on line 2 of a UVM to get the expected channel for line 2. Example: |
CSCdk21160 | Symptom: Interval statistics on the Cisco WAN Manager are smaller than expected after a clrportstats, clrchstats or a clrtrkstats command is executed. Conditions: Whenever any of the commands that clear summary stats are executed: clrportstats, clrchstats or clrtrkstats, software will drop one or more ensuing polls, for ALL statistics (including interval statistics) rather than just for summary stat. The end result is that we will miss one polls worth of information. Workaround: None at this time Customer Impact: After invoking one of the above commands software will disregard the next statistical poll for all statistics, even though the command is meant only for summary statistics. This result in data loss as explained below. For releases 8.4 and later the polling rates are: FRelay and ATM connections: User configurable to 5, 10, 15 minutes All other types of conns: 1 minute Ports: 1 minute Circuit Lines: 10 seconds Packet Lines: 10 seconds For releases 8.5 and later the following changes apply Ports (IPX/IGX): User configurable to 5, 10, 15 minutes One samples worth of data will be lost, so the worst case scenario would be a loss of 15 minutes worth of data for 8.4 FR/ATM connections or 8.5 FR/ATM connections and 8.5 Ports. |
CSCdk28347 | Symptom: Connection to a FastPAD failed when the remote FastPAD becomes unreachable. Conditions: This can happen due to a FTM reset, card down and up, node rebuild. Workaround: Rebuild local end of connection or down and up connection. |
CSCdk29716 | Symptom: Discrepancy in the "dspchstats" when comparing the two end points of a given PVC. More traffic appears on one side than the source sends. Conditions: After a switchcc occurs while connections are rerouting. Workaround: "dncon" and "upcon" will resolve this problem |
CSCdk48816 | Symptom: There is no UAS alarming. Spec requires that when we have more than 10 consecutive SES then we should enter UAS. Because this is currently not implemented, no UAS alarm is generated in this situation. Conditions: This requires that both firmware and switch software fixes to the following bugs must be present to fix this problem. CSCdk48827 - Firmware bug to fix the thresholds for SES to kick in. This is fixed in firmware image BXMMCB or later images. CSCdk48816 - The software portion of this problem to alarm based on UAS. Without the software fix to this bug, customer cannot upgrade firmware beyond MBY because when we enter UAS, per specification, we stop counting Bip8 ES and SES - as such we will not have alarming on ES as well as no alarming on SES. MBY provides a temporary fix to keep the ES alarming on by raising this threshold. Workaround: Work around is to continue to use MBY which will prevent SES alarming to kick in. The side effect is that this will prevent the customer from using the features introduced in the MC firmware. |
CSCdk53502 | Symptom: ASI-T3 or ASI-E3 cards using T3-3 or E3-3 backcards show lines as Clear-OK when the line actually should show LOS. (No loopback or other line attached) Workaround: Use cnfbkcd to change the backcard to a T3-2 or E3-2 and the line will show LOS status correctly. |
CSCdk55887 | Symptom: dspport command is not available to level 6 user ids. Conditions: After upgrade from 7.x software to 8.1+ software. Workaround: Increase user privilege. Further Problem Description: The privileged level of the dspport command was changed in release 8.1 to level 2 from level 6. This difference was first noticed by offsite user after upgrade from 7.4 to 8.5.05. User who running 8.x.x software hasn't noticed this difference until opening of this problem. |
CSCdk75382 | Symptom: The modem upgrade failed. The failure rate may be as low as 10%, or as high as 95%. Conditions: This happen randomly. Workaround: 1. Try again after failure 2. If the failure rate is very high, try using the Fax Relay feature: a. Enable fax-relay on the channel or channels with the command cnfchfax. b. Disable V.25 modem detection on the channels with the command cnfvchparm. 3. Upgrade software to release 9.1.07 or above. Further Problem Description: This problem is caused by a race condition in Software. It occurs only about 10% of the modem sessions in the lab. In a customer environment the failure rate has been observed as high as 95%. |
CSCdk80347 | Symptom: NPM 2 restarted due to a Watchdog Timeout Conditions: Happens when you run resetsys command to reset all the cards (except the active NPM card) on an IGX node with lot of active connections. When the standby NPM comes up, the event log mentions that: "NPM 2 Restarted due to a Watchdog Timeout" where 2 refers to the slot number of the standby NPM card. Workaround: This does not affect any functionality except for the above log. Instead of running the resetsys command, individually reset the cards using resetcd command. |
CSCdk89002 | Symptom: A BPX switch experienced unreachabilities with all Axis feeder trunks. Conditions: Unknown Workaround :switchcc |
CSCdk93423 | Symptom: Extra connection statistics are reported in statistics file, or the Cisco WAN Manager rejects the statistics file indicating that it is corrupted. Conditions: This problem will occur when the user has an access device configured that is supporting connection other than the voice connections, and the Cisco WAN Manager's Stats Collection Manager has statistics of the subtypes FastPad Voice, FastPad Switched Voice, FastPad Data, or FastPad Frame Relay enabled. Work around: Do not enable statistics for the subtypes listed above when there are access devices other than FastPad's configured in the network. |
CSCdm00711 | Symptom: Hardware watchdog aborts on all versions of release 9.1 on an NPM-32. When software attempts to access memory in the 32-64Mb range on an NPM-32 an access error interrupt will not be generated, the CPU will freeze until a hardware watchdog occurs. A switchover will occur if a standby NPM is available. A rebuild will occur if a standby NPM is not available. Conditions: NPM-32 with the SNMP Get community string configured. Certain SNMP operations are causing switch software to access non existent memory. Workaround: Set the SNMP Get community string to NOACCESS. |
CSCdm05391 | Symptom: LCN is autodeleted. But Xlat database is not cleaned up properly. This will result in software error 370 Condition: This problem happens when a connection (VC/LCON) is autodeleted due to VC_DB/LCON database verification. The original bug is due to AUTO_DEL_VC/AUTO_DEL_LCON. Workaround: None. Do clrswlog to clear software errors. |
CSCdm06555 | Symptom: dsptrks on BNIs show Loss of Pointer. This results in comm. failure on trunks. Condition: Software is wrongly displaying the type of Alarm. Actually this is Out of Frame. When there is a OOF Alarms, comm. failure will happen. Workaround: Check the cables and backcards. Make sure that they are all properly connected. Do Loopback tests and make sure that physical layer is good. |
CSCdm08470 | Symptom: Return traffic on a CBR connection is not limited to its configured PCR rate. Example: A CBR connection configured for 5000/50 will not limit the return traffic to 50 cps. Workaround: Unknown |
CSCdm10372 | Symptom: When a VSI controller is deleted using delctrlr command, the object 6 in the 0x61 CBUS message is set to 1. Effects: Hence when a VSI controller is deleted, traps may not be sent to the controller. Workaround: This functionality is used by the PNNI controller which is not available in the 9.2 release. Hence this bug will not create any problems in this release. |
CSCdm10703 | Symptom: A software error 514 is generated after downing an ALM-B trunk. Condition: This problem is not readily reproducible. To date it has occured only a few times and each time it was on an ALM-B trunk. Analysis of the defect suggests that perhaps a UFM was in this slot prior to the ALM-B. When the trunk was downed, the 514 was logged. Workaround: None. Impact: The 514 is logged, but the memory is still freed. There should be no other side effects of this defect, other than the logging of the 514. |
CSCdm12876 | Symptom: Software error 324 is logged during re-routing of connections. Condition: During the process of routing connections on a via node, the routing state machine logs this error because it encounters an Via CON which contains Xlate Ids which point to Xlate entries that do not exist. WorkAround: Full rebuild or switchcc on the via node will fix this problem. |
CSCdm13482 | Symptoms: 1) dsplm shows fail "F" in the "LC "column. 2) This is due to inconsistent VLCONS. There exist dangling VLCONS, which have not got cleaned up. Conditions: 1) When the command xlat_verify is executed, software error 332 (BD_XLAT_INDX) is logged complaining about the dangling entries. 2) These errors do not cause any corruption or damage. Workaround: 1) Switchcc will cleanup. 2) The errors if logged can be cleared. |
CSCdm13495 | Symptoms: Sometimes after burning firmware, the card seems to disappear. Workaround: None needed. Usually, burning firmware seems to work fine. The problem was probably due to some particular circumstance. It is not clear whether may have been a configuration problem, or user error, since it is not being seen. |
CSCdm16353 | Symptom: Software error 9082 (Channel Config Bad Command Error) reported after issuing switchyred (or resetcd) on BXM card with redundancy. Conditions: - BPX with 2 BXMs (YRED) - LMI protocol is implemented by the BXM card. - There are a lot of connections (e.g. 1600) between the AXIS and the BPX. - A switchyred occurs (either due to a reset on the active BXM card or the switchyred command). The YRED BXM card will become active and all channels have to be reprogrammed by the BCC. Before the BCC has a chance to finish the programming, the Axis is already sending status to those channels that have not yet been re-programmed on the BXM card. The BXM reports this error which will then be translated into software error 9082. Workaround None |
CSCdm17732 | Symptoms: Software error 355 is logged. Conditions: This error is seen after switchcc because one conid is being used by two xlat entries. No corruption is caused. Workaround: switchcc may fix this problem. |
CSCdm17748 | Symptom: The fields UpdtStatus Rx, UpdtStatus Tx, Status Ack Tx, Status Ack Rx on dsplmistats increment when the LMI protocol is moved from BCC to the BXM but not when the protocol is moved back from BXM to BCC. Conditions: This is observed when LMI protocol is moved from BXM to BCC. Workaround: None Further Description: When the protocol is moved from BCC to BXM, BXM sends out the update status for all the connections. But this is not done when the protocol is moved from BXM to BCC. This means if something goes wrong with the BXM implementation of the protocol we cannot move the protocol to BCC and clear the problem. Customer Impact: The impact is minimal. This is more of an enhancement issue. |
CSCdm19535 | Symptom: (1) When adding a new VT on a BXM port already supporting VTs, some unnecessary channel programming takes place. (2) When deleting a VT on a BXM port the still supports other VTs, the directed networking channels get assigned to the VI of the deleted trunk. If this VI gets reassigned to a different port, Comm Breaks could happen. (3) A direct routing loop is not stopped for BXM VTs, as a VT transmitting a specific VPI/VCI can also receive it. This will fill up the VT with hipri traffic, when a routing loop is created where the neighbor sends this VPI/VCI back. Conditions (1) addtrk of multiple VTs on a single BXM port. (2) deltrk of one of several VTs of a single BXM port, and reassigning the VI to another port by dntrk of the VT and uptrk and addtrk of a new trunk on a different port of the same card. (3) Inconsistency of topology information of two neighbor nodes. Workaround (1) None, but the problem is not serious. (2) Resetting the BXM card (3) The operator can resolve this situation by removing the routing loop. Routing loops occur when nodes do not have the same topology information. The topology information can be made consistent by use of the updates 1 or the recovertopo command. Another note for (3) There exists a theoretical chance of a trunk loopback generating a large stream of cells. However, so far all attempts to demonstrate this have failed. |
CSCdm20508 | Symptom: Software error 447 gets logged Condition: Standby card is reset Workaround: None. The node logs software error because it does not expect this kind of message from the Standby and discards it. No harm is done, as the Standby is resetting anyway. |
CSCdm20593 | Symptoms: A request to block ATFR connections between UXM endpoints. Conditions: None Workaround: None |
CSCdm22241 | Symptom: Using the 'dspchstats' on a BXM there are missing value's Condition: During 9.1.08 system software testing the lab personnel discovered that the BXM statistics usually recorded in an enhancement in switch software 8.4.09 has been removed. Workaround: None |
CSCdm22255 | Symptom: Performing switchcc while in boot locks up the NPM cards. Effects: The NPM cards have to be physically reset by pulling them out of the IGX chassis and re-inserting them. Workaround: Doing switchcc in the boot is normally done by the development team for doing upgrades. This is not a recommended procedure for performing upgrades. The recommended procedure is to use loadrev command or to use TFTP to upload dnld.sw file with relevant upgrade information. |
CSCdm24020 | Symptoms: 1.) A hitless rebuild was done on a slave node while the master rerouting some connections. 2.) There is a remote chance that, when the rebuild occurs slave has not finished routing on its side. The connections remain as derouted on the slave side but are routed on the master. Conditions: 1.) Rebuild the slave when connections are being routed from the master side. Workaround: 1.) The command rrtcon will fix it. |
CSCdm24749 | Symptom: During y-red switchover OR card reset there will be multiple messages going to the standby cards. This may cause RSRC to hog cpu for some duration. Conditions: Node has Y-red configuration, y-red switchover OR CC switchover occurs. Workaround: None. Further Information: This is NOT going to cause any operational problem to customer. |
CSCdm28610 | Symptom: Software error 1415 is logged on the Standby after a network trunk is deleted meaning it was already deleted on the Standby. Workaround: None Impact: None. Software error shows that some updates from the Active indicating the existence of this trunk did not reach the Standby. This error was observed when several switchcc were executed within a short time interval which probably accounts for the loss of the updates. |
CSCdm36041 | Symptom: When a backcard to an active BCC is removed or inserted, no entry is logged into the event log. When the backcard to a standby BCC is removed or inserted, an entry is logged into the event log. Workaround: None. |
CSCdm40952 | Symptom: On a switchcc, the node will try to reroute some working connections not on their preferred route (dsprrst will show non-zero values). The reroute attempt will not be successful and the connections will continue to use their working path. Condition: This will happen only when preferred routes are set up for the connections and these connections are not routed on their preferred routes. Workaround: None |
CSCdm41151 | Symptom: Software error 372 is logged when a mandatory update is received from another node in the network. Condition: This happens when the LCON database is corrupted (one LCON entry is pointing to a VC index of -1). Workaround: None |
CSCdm42254 | Symptom: When a user ID is deleted from the user database, subsequent users are shifted and use of the same privilege level as the immediately following user. Conditions: Network of 9.1.09 where issue was discovered. Lab network at 9.1.09, 9.1.10, and 9.2.00 with problem. Not observed in lab environment at 8.4.21. Workaround: In order to prevent the shifting, a dummy user ID needs to be created any time an existing user ID is deleted. The dummy ID will fill the spot vacated by the deleted user ID and user IDs below the deletion will shift back to their normal positions. |
CSCdm46321 | Symptom: End to End OAM loopback in 9.2.0V with BXM MDA failed. Condition: When sending in F5 end to end OAM loopback to FR-ATM and ATM-ATM PVCs, data transfer/tstdelay can go through both FR-ATM and ATM-ATM PVCs. However, F5 end to end loopback fails for both ATM-ATM and FR-ATM PVCs. Work around: None |
CSCdm46335 | Symptom: Executing the following commands one after the other causes swerr 9091 1) resetcd both cards of a yred pair. 2) As soon as they come up OK in dspcds, add a conn. 3) As soon as the conn shows OK, perform tstdelay. Conditions: This swerr occurs when we execute tstdelay soon after we add a conn, after noticing in dspcons that the status is OK. It is to be noted that dspcons only displays if the route for that conn is established. The programming of the conn takes a little more longer. Workaround: Not to execute the tstdelay soon after adding the connection but to wait a couple of minutes. Especially this long if there are a lot of connections in the node for which the cards may take a little longer to program the conns. |
CSCdm47511 | Symptom: In a fully loaded network, a rebuild will in a rare occasion cause connection(s) with high bandwidth requirement to be left in a state of no routed. Conditions: This condition happens only when the traffic mix with some very high bandwidth requirements connections with many more low bandwidth requirements. After a rebuild, the low bandwidth connections are routed first while the bandwidth updates are gradually trickle in. In the end, one or more high bandwidth connection may be left in a state no routed. Workaround: Make sure that the network provision is not too tight in its trunk loading. Extra loading in the trunk provision will prevent this problem. |
CSCdm48389 | Symptom: Working connections (not on their preferred path) failed during switchcc. Condition: This happened only for connections which have preferred paths and were not routed over their preferred path. Workaround: None |
CSCdm50251 | Symptom: Certain counter values in CiscoView are undefined in CLI and display incorrect values. SNMP Agent on switch is returning bad values. Conditions: Observed on node with BXM viewing dspportstats, verifying CiscoView values, and walking switch MIB values. Workaround: None |
CSCdm52681 | Symptom: switchyred causes data transfer stops for 1 to 4 min. Condition: The data transfer stops/tstdelay fails for 1-4 min. after switchyred. dspchstats shows no data can be received from BPX node, dspcon shows route is OK and no alarm at all. Workaround: None |
CSCdm52909 | Symptom: The virtual trunk (VT) sometime can display inconsistent status on two ends of a virtual trunk. Conditions: The display of a VT (virtual trunk) may show two different status. One end displays okay; the other end may show Virtual path failure. Workaround: None |
CSCdm52909 | Symptom: The virtual trunk (VT) sometimes displays inconsistent status on two ends of a virtual trunk. Conditions: The display of a VT (virtual trunk) may show two different status. One end displays okay; the other end may show Virtual path failure. Workaround: None |
CSCdm69834 | Symptom: The default service class template is set to 2 (instead of 1) if upgrading from 9.1.00 to 9.2.10. Condition: This happens only when upgrading from 9.1.00 to 9.2.10 (directly, 9.1 -> 9.2.10 OR via 9.2.00, 9.1.00 -> 9.2.00 -> 9.2.10). Workaround: This will have an impact only if VSI is used in the network. Different scenarios: 1. If VSI is used in 9.1.xx and the network is upgraded to 9.2.10, then this is a showstopper - the VSI conns can loose continuity. All interfaces will have templates set to 2 (PNNI template) instead of 1 (MPLS template). MPLS network SHOULD NOT be upgraded from 9.1 to 9.2.10 - instead it should be upgraded to 9.2.20 (which will have this fix). 2. In all upgrade paths from 9.1 to 9.2.xx (xx < 20), the default template will be set to 2 for all interfaces. The template assignment can be modified using cnfvsiif if VSI is going to be used. |
The following is the list of fixed anomalies in the 9.2.10 Switch Software delivery. Included with each is a brief discussion of the problem.
| Bug ID | Description |
|---|---|
CSCdk21358 | Symptom: The MIB variable slotCardStatus does not show proper value. Conditions: The IPX/IGX/BPX SNMP agent reports the above MIB variable as active when there is no backcard installed. Work Around: None |
CSCdk26240 | Symptom: AIS alarm counts are not displayed for E3 lines and trunks when using the commands dsplnerrs line_num and dsptrkerrs trk_num. Conditions: The problem occurs on BPX nodes using E3 lines or trunks. Workaround: No workaround is available; however, the AIS alarm status is correctly displayed. |
CSCdk29716 | Symptom: Discrepancy in the "dspchstats" when comparing the two end points of a given PVC. More traffic appears on one side than the source sends. Conditions: After a switchcc occurs while connections are rerouting. Workaround: "dncon" and "upcon" will resolve this problem |
CSCdk33721 | Symptom: The connection got deleted because the update message sent from Master node is inconsistent with the Slave node. Software error 614 was logged. Condition: During graceful upgrade the software error 614 was seen. Workaround: None |
CSCdk51121 | Symptom: The command dsplnalmcnf only shows the line alarm configuration, it does not show the trunk (packet line) alarm configuration. Impact: The customer must use a round about way to view the trunks statistical alarm configuration as detailed in the workaround. Condition: This will always occur. Workaround: We can use a round about method to display the current line and trunk statistical alarm configuration. This can be done by invoking cnflnalm. Then from the list of alarms, choose one that is only relevant to trunks (i.e. Tx NTS C Dscd). You will then be prompted for the "Alarm Class?" immediately hit the <DEL> key to cancel the command. The screen now has the configuration for 8 statistical alarms, one of those is the alarm you specified. |
CSCdk51259 | Symptom: Only for the UXM and BXM can NMS get the information of slotBackNumPort from the MIB. Conditions: When query from SNMP Workaround: None |
CSCdk55034 | Symptom: BIP8 errors are received at 10E-3 and the line/trunk is in MINOR alarm. The line/trunk MAJOR alarm threshold is configured at 10E-3 (cnflnalm command). Condition: When BIP8 errors are received on an E3 line or trunk at a rate of 10E-3, the line or trunk will not go into a MAJOR alarm state. The line/trunk will instead go into a MINOR alarm. Workaround: Change the MAJOR alarm threshold for BIP8 to 10E-4 using the cnflnalm command. |
CSCdk65743 | Symptom: Software error 52 in dspswlog with VT_1 as running process Conditions: One-time occurrence of a watchdog timeout on a BCC while VT'd in from another node Workaround: None |
CSCdk69040 | Symptom: The wrong error message is reported: "SVC caching: timeslot(DS0) for this channel already in use". Conditions: Number of LCNs (channels) is used up on the remote BXM port while adding a connection. Work Around: 1. Verify the error condition by adding the same connection to the BXM port as a master end. Message "No channels left on this line" indicates the problem. 2. Allocate more channels on the port use command cnfrsrc so you can add the connection to the port. |
CSCdk77005 | Symptom: 1000003 abort in SNMP process Conditions: After an ARP request is received by the switch with the network id of the senders address different than the network id of the switch subsequent walks of the ARP table will cause a 1000003 abort. Workaround: Remove walks of the switch ARP table or set the SNMP get community string to NOACCESS. |
CSCdk87933 | Symptom: Some connections are deleted after network flood is cleared. Conditions: In the lab where faulty hardware is used to simulated flood, after flooding is cleared, there are some connections being deleted. This problem is caused by the network messages that are circulated in the queue using the faulty hardware. Network messages were corrupted causing the switch to interpret the network message incorrectly and the connections are deleted. Work Around: None |
CSCdm02272 | Symptom: dsplogcd 112 5 cmd entered and screen freezed Conditions: The card is BXM-T3/E3 and sonet mode attribute has bad value. Use "dspcmi p" to examine the value. It is bad if the value exceeds 6. Work Around: Patch sonet mode to 0. Please contact Cisco for the operation. |
CSCdm04262 | Symptoms: The OAM loopback test may be failing on a DAX conn with endpoints at 2 cards on the same node. When the OAM capability is disabled on one card, the OAM loopback failure condition is also cleared at the other card which still has the OAM capability enabled. Conditions: This happens only on a DAX conn using 2 cards. Workaround: None |
CSCdm04372 | Symptom: The response of an SNMP query of the object atmPortIfType is wrong. oc12-smf(10) is returned for a BXM T3/E3 card. Conditions: When query BXM T3/E3 cards. Work Around: None |
CSCdm04812 | Symptom: dspstatsinfo is counting a connection terminated at a feeder trunk. Conditions: If there are connections terminated at feeder trunk, they are included in the summary of the connection count. Workaround: None |
CSCdm14446 | Symptom: 3-byte frames routed over a UXM trunk on a frame forwarding connection between a UFMU and a UFM port are not being received by the other end. Condition: If transmitting 3 bytes frames on a frame forwarding connection between a UFMU and a UFM port, routed over a UXM trunk, the frames get corrupted at the UXM card on the transmitter node and hence are discarded by the receiver node. Workaround: Do not transmit frames of size less than 5 bytes on a frame forwarding connection between two UFMU connections routed over a UXM trunk |
CSCdm18555 | Symptom: For the following conditions, the user either cannot add yred or is reported with false mismatch alarm. The user does not get any benefit by upgrading to the enhanced UXM card because of the mismatch. Condition: 1. Cannot configure yred for mixed UXM cards if in standby mode. Cannot configure yred if in active mode and the primary card is enhanced while secondary is non-enhanced. 2. The switch issues false mismatch alarm under any of the following conditions: * For standby yred UXM card pair, when change the secondary card from non-extended card to extended card. * For mixed yred UXM card pair, when upgrade from release 91 to release 92. * For active non-yred card, when change from extended card to non-extended card. * For active yred card pair, when change the secondary card from extended card to non-extended card. Workaround: None |
CSCdm19544 | Symptom: dspchstats command does not show OAM Rx: AIS when line is failed in 9.2.1F. This works properly in 9.1.09. Condition: On an FR-ATM conn (Axis-BPX), fail the FRSM line. This should show AIS for connections on the BPX on the dspcon and dspchstats screens. Workaround: None |
CSCdm24031 | Description: If old 9.1 firmware is burned into a new enhanced BXM card, then the card will not function. Solution: The user interface should be able to verify that the version of firmware is correct for the card before allowing it to be burned. Workaround: Be careful when choosing the correct version of BXM firmware before burning it. |
CSCdm29600 | Symptom: Unable to add connections. Addcon command errors such as "Local resources unavailable or Network Expansion not allowed" or "Local channel unavailable" may be displayed. Commands such as "dcct t" will produce swerrs 374 and 752. (For 9.2, this only occurs on BPX; IGX works OK) Conditions: Command "dvc #" (where # is a number between one and the maximum number of VCs supported by the switch) for an unused VC shows "VC #0" on a BPX running release 9.1. Only VC 0 should have "VC #0". A VC with an invalid VC index may also have an invalid connection type for an uninitialized VC. If the first "dvc #" screen has "VC #0", "Exists : 0", and "Con Type : ADPCM", attempting to display the second screen will probably cause a 1000003 abort. Do not use "dvc" on an IGX. It will probably cause a 1000003 abort without displaying the first screen. This problem is observed after a non-graceful upgrade from release 8.4 to release 9.1 or on BPX from release 9.1 to release 9.2. There is not a problem with - graceful upgrades, or - non-graceful upgrades from releases 8.2.xx (xx = 55 or higher) or 8.5, or - non-graceful upgrades of IGX from release 9.1 to release 9.2. The problem is that VCs which were used for connections that were deleted in the previous release will have a VC number 0. There is not a problem with VCs which are used for connections, or which have never been used. Workaround: Audit the standby BCC. If the standby BCC does not have the "VC #0" set for VCs other than 0, and other standby databases are updated, perform a switchcc. Do not reset the standby BCC prior to the switchcc, as this will send the invalid active BCC "VC #0" over to the standby BCC for used VCs. Unused VCs will not be updated the standby CC. If the active BCC is in better condition than the standby, the standby BCC may be reset prior to the switch. The used VCs with index 0 will be auto deleted during database cleanup performed after the switch. Do not use "dvc" to audit an NPM/C. Prior to performing the switchcc, enable connection logging to the event log (cnffunc) so that any connections that are deleted as part of the database cleanup can be identified. If a non-graceful upgrade was performed because a standby CC was not available, loadrev the 9.1 release into flash, then rebuild the node a second time in 9.1 (the first rebuild was the non-graceful upgrade). (Use 9.2 instead if that's the release you are using) Further: The SW initializes the VC number for all VCs when the node rebuilds. In the case of a non-graceful upgrade, SW maps the BRAM from the old release to the new release after the rebuild. The VCs are mapped one at a time. A VC is mapped by clearing all fields (all fields initialized to 0), then mapping the values from BRAM. This mapping is performed for all connections that exist in BRAM. Connections that do not exist in BRAM have their LCON index set to 65535 (-1), but the other fields are not mapped from BRAM. VCs which have never existed (never been used for a connection) are not processed by the BRAM mapping software. Thus the VC number initialized by the rebuild initialization SW is not cleared by the BRAM mapping SW. |
CSCdm36631 | Symptom: APS activated alarm trap #20101 seen for T3 trunk. Conditions: A T3 trunk was modified using cnfrsrc command. Workaround: None Further Problem Description: The trunk object structure in the BPX has some fields reversed from the definition in the external interface specification. Cisco WAN Manager is coded according to the specification and so it interprets the max_channels_per_port field as the APS slot/port fields. |
CSCdm37694 | Symptom: Software error 9082 was seen after upgrade Condition: A race condition. The channels on the card were not reorganized the 9.2 way before reprogramming messages were sent to the card. Workaround: Not needed |
CSCdm37802 | Symptom: Software error 706 logged. Conditions: This problem occured when HDM fails the self test continuously due to the bad hardware. Workaround: Disable the HDM selftest by executing the cnftstparm command. |
CSCdm39210 | Symptom: A cnfrsrc on the trunk connecting a Tag Switching Controller to BPX does not allow the MAX PVC LCNs to be more than 10. Condition: BXM yred pair 1) disable VSI partition on trunk 3.3 2) dntrk 3.3 3) uptrk 3.3 4) cnfrsrc 3.3 Got "PVC Channels(256) Can not exceed (10)" message Workaround: None Description: The underlying problem could be that there is an APS channels halved attribute mismatch. |
CSCdm39227 | Symptom: CAC allows oversubscription. Conditions: Any environment Workaround: None |
CSCdm39836 | Symptom: Whenever NMS like CiscoView inquires about UXM back card and whenever we have E1 backcard with BNC type of connectors, we send UAI-E1 as enumerated value. Now, NMS inquires about port and finally get as DB-15 as connector type. If we have BNC type of connector, we end up in giving wrong back card - connector info to NMS. Condition: UXM with E1 back card and BNC type of connectors Solution: Use CLI to find out type of connector ("dspcd <slot>") or do not reply for SNMP query for UXM with E1 backcard with BNC connectors. |
CSCdm39871 | Symptom: SNMP walk will show some revision for ARM backcard. Condition: Have ARM card inserted with backcard. Workaround: None |
CSCdm40006 | Symptom: dspblkdfuncs did not list VT as being blocked as blocked for all but 9.2 - (VT not listed at all) Conditions: Mixed networks of 9.2 and earlier releases Workaround: None needed |
CSCdm40707 | Symptom: software error 4229 logged. Condition: switchcc was performed on a bpx having connections. The bpx was previously upgraded from rel 9.1.09 and the connection (due to which the error was logged) was added in release 9.1.09. Workaround: None |
CSCdm41274 | Symptom: Software errors 514, 589 on delyred following switchyred with a BXM and another BXM supporting more number of channels (BXM-E) forming the yred pair. Conditions: This software error occurs when you addyred two BXM cards, replace the secondary with another that supports more number of channels (BXM-E), switchyred and then delyred. Workaround: In a redundant BXM setup, do not replace the secondary with a BXM that supports more number of channels (BXM-E), and do switchyred. As a workaround replace the primary instead. |
CSCdm41406 | Symptom: Minor alarm regarding high CPU usage gets logged after rebuild or switchcc of a loaded node, and never clears. Conditions: Fully loaded node and rebuild Workaround: Ignore. There are no bad side effects except for the minor alarm indication. |
CSCdm41415 | Symptom: "Connection Channels" field is missing from dsptrkcnf and cnftrk screen. Conditions: N/A Workaround: None |
CSCdm41881 | Symptom: Software errors 514, 589 and 502. Condition: Under rare circumstances the first fragment of a message did not match the following received fragment causing buffer overwrites. Workaround: None |
CSCdm42754 | Symptom: 1) The active, or standby has non-zero interval statistics counts (as displayed by dspstatparms) thereby indicating that TFTP interval stats are enabled. However, TFTP interval stats are not enabled as indicated by dspstatparms' "Object Count" field showing zero objects, and the "Interval Stats:" field indicates DISABLED. This is being referred to as stats being partially enabled. 2) The standby controller card logs a software error 2000000 and then resets itself once. 3) The standby controller card logs the software error 2000000 and then resets itself at the regular interval of 5, 10, 15, 30 or 60 minutes. 4) After a controller card switch over, the new-active controller card logs the software error 2000000 and then reset itself. 5) After a controller card switch over, the new-active controller card fills the software error log with software error 136's. Conditions: The steps leading up to the various symptoms listed above are similar, but not quite the same. They are explained as follows: 1) The partial enabling of TFTP stats will occur if: a) The customer has a redundant controller card. b) TFTP interval statistics are enabled. c) The active controller card does a hitless rebuild At this point the standby will have TFTP interval stats partially enabled, when they have actually been disabled. d) A controller card switch over is done. At this point both the active and the standby will have TFTP interval stats partially enabled, when they have actually been disabled. 2) The single 2000000 and standby rest will occur if: a) The customer has a redundant controller card. b) TFTP interval statistics are enabled. c) The active controller card does a hitless rebuild d) A controller card switch over is done. e) The same set of TFTP interval statistics are enabled, as done in step b. When the active creates its TFTP interval stats file at the end of its file interval, it will send a message to the standby to do the same. However, when the standby stumbles across some of the TFTP interval stats that where partially enabled (see FURTHER PROBLEM DESCRIPTION below), the 2000000 is logged and the standby controller card is reset. However, when the standby resets all of the partially enabled TFTP statistics are deleted. Note that the active has its global statistic data structure indicating that stats are enabled, so when the standby update mechanism enables the statistics on the standby it will obtain acceptable initializers from the statistic global data structure and the problem "corrects itself". 3) The standby "2000000 and reset" scenario will occur if: a) The customer has a redundant controller card. b) TFTP interval statistics are enabled. c) The active controller card does a hitless rebuild d) A controller card switch over is done. |
CSCdm42754 - continued | NOTE: Statistics were not re-enabled. In this case the active has its global statistic data structure cleared, but it incorrectly has statistics enabled (See FURTHER PROBLEM DESCRIPTION below). Periodically, the active will send an update to the standby to roll its statistic buckets. At this time, the incorrectly initialized statistics will log a software error 2000000 and then restart the standby. These restarts will occur at approximately the bucket interval rate. We say approximately, because it generally takes longer than 5 or 10 minutes for the secondary card to become fully updated. 4) The scenario for the active controller card logging a software error 2000000 and then resetting itself will occur under the following conditions: a) The customer has a redundant controller card. b) TFTP interval statistics are enabled. c) The active controller card does a hitless rebuild d) A controller card switch over is done. e) Prior to a statistics bucket interval completion, another controller card switch over is done. Prior to the last switch over the standby has incorrectly initialized statistics. Some of the initialized values are zeros. When we switch over, the card starts using some of the fields and logs the 2000000 and then restarts. However, after the restart, the situation has cleaned itself up. 5) The scenario for the active controller card filling its log with 136 errors is the same as for scenario 4. The difference here is that symptom 4 was discovered in an earlier release, but the root cause was not tracked down, so instead preventative code was added to avoid the 2000000 and restart, and simply log a 136 and continue. This scenario will not clean itself up. The 136 software errors will be logged at a high frequency until the work around is enacted. Workaround: 1) Symptoms 1, and 3 can be resolved by doing the following: a) Enable statistics b) Disable the statistics. At this point, dspstatparms should indicate that interval statistics are disabled, and the statistic tally counts should also be zero. c) Reset the standby controller card. Realistically the standby should have disabled all of these statistics, but to make absolutely certain I recommend that the standby controller card be reset. 2) Symptom 2 corrects itself, however, I would still recommend following work around #1 to be absolutely certain. 3) Symptom 4 also corrects itself. However, to avoid symptom 4 from occurring in the first place, the following preventative steps can be done. a) After any hitless rebuild, validate that the standby agrees with the active regarding the state of statistics. If the standby has a non zero statistic count, while the active has a zero statistic count, then follow the steps for work around #1. b) Prior to doing a manual controller card switch over, follow the instructions for step a) above. |
CSCdm43471 | Symptom: After upgraded from 8.4 to 9.1 or from 9.1 to 9.2 Cisco WAN Manager can not see switch software FRM, VOICE and DATA connections anymore. Only FRM to ATM endpoint connections showed. Conditions: Problem exists on upgrade to Release 9.1 switch software from Release 8.2, Release 8.4 or Release 8.5, or to Release 9.2 from Release 9.1. Workaround: 1. Delete connections and re-add or 2. Rebuild Further Problem Description: After upgrade from 8.2, or 8.4, or 8.5 to 9.1 Cisco WAN Manager can not see SWSW FR-FR connections, voice connections, and data connections anymore. Only FR to ATM endpoint connections are not affected. |
CSCdm44056 | Symptom: APS Annex B connection is not defaulted to bi-directional. Condition: After adding APS Annex B line Workaround: Use cnfapsln to configure the line to bi-directional Description: Even though the default says uni-directional, BXM firmware will only use bi-directional internally for Annex B. |
CSCdm44387 | Symptom: Software error 1433 was sometimes logged on the Standby. Conditions: Customer typed command 'dspstbyclk'. Workaround: None Further Problem Description: The only side effect of this bug is the logging of software error 1433. |
CSCdm44587 | Symptom: Software error 29 is logged. Condition: Adding additional trunk from the neighbor node with the port number greater than 8, and the neighbor node is running release 9.1 while this node is running 9.2 before the fix. Workaround: This software error is harmless, just delete it. |
CSCdm44973 | Symptom: After a line or trunk alarm is modified, the alarm information is displayed on the top line of the screen, overwriting the "Line/Trunk Alarm Configuration" text. Workaround: None is needed. The command works correctly, it is just the display that is incorrect. |
CSCdm45274 | Symptom: 32K channels of BXM-E card not available until "resetcd h" is done Conditions: Replace the regular BXM active card with an Enhanced BXM card Bring up the BXM-E card in standby state 32K channels will not be available until the card is reset Workaround: None |
CSCdm45592 | Symptom: The most common symptom is that when TFTP interval statistics are enabled the software error log is filled with software error 2068's and 504's. However due to the nature of this defect, it is hypothesized that this could also lead to the aborts 1000003 and 2000000. Conditions: This occurs under the following conditions: 1) The customer has UXM ports 2) The customer has TFTP interval statistics enabled on the UXM ports. 3) A hitless rebuild occurs. After this point, the hypothesized effects could occur. If the customer then enables TFTP interval statistics again (which the SCM will do automatically when it discovers TFTP interval statistics have been disabled after the hitless rebuild) the software error log will fill with the 2068's and 504's -- but it will then clean itself up. Meaning that there is no longer a threat of the aborts and no further 2068's or 504's will logged (unless another hitless rebuild occurs). Workaround: Do not enable TFTP interval statistics on UXM ports, or disable the hitless rebuild functionality. Further descriptions: The problem is that the handle (pointer) to the linked list of memory used for monitoring TFTP interval statistics is not being correctly initialized on a hitless rebuild. After a hitless rebuild, the handle is referencing memory that is no longer allocated. Initially it has it will still have its old data (we do not clear out all memory on a rebuild) so it appears that we are pointing at valid memory. However, because this data is not allocated, it can be allocated for something else related to statistics at which point we now have two different handles to the same memory. If the allocation changes the data format, which is almost guaranteed. It is hypothesized that incorrect handle could, in the worst case, abort because the old data is no longer maintained, or simply cause one of several other possible statistics related errors. Similarly, the old handle could change the memory, clobbering the memory because it does not really own the memory, which could then cause the real memory owner to abort, or cause any other possible statistics related error. When TFTP statistics are enabled after a hitless rebuild we first check to make sure that all existing TFTP statistics are disabled, however, these handles appear to be pointing at existing statistics. When we go to free them, we first log a 2068 because this does not coincide with our internal statistics accounting, then we log a 504 because we are attempting to free memory that has not been allocated yet. Finally, after all of this has occured, we will correctly initialized the handle and then start the enabling process correctly. |
CSCdm45812 | Symptom: Forced or manual APS switch causes a switch to opposite line then requested. Switch software and BXM firmware may get out of sync. Conditions: Performing an APS switch to a line which is already active. Workaround: Perform an APS clear switch on the line (switchapsln option 1). This should get swsw and BXM firmware back in sync. Description: BXM Firmware cannot handle getting a command to switch to a line which is already active and requests that swsw block such a switch. |
CSCdm45889 | Symptom: Software errors 509 and 101 logged Conditions: This occurs when firmware debug command response from the card is processed immediately after the node rebuilds or after a switchover. There is a very remote chance for this error condition to occur. Workaround: Avoid issuing rsh command before a switchcc or node rebuild |
CSCdm46095 | Symptom: Software error 526 appears. Condition: Adding, deleting, or displaying an APS line Workaround: None Description: This is the result of a display problem in the code. There is no affect on BPX operation. |
CSCdm46601 | Symptom: Software error 116 (BAD_OBJ_RESP) seen close in time to when UXM cards were being reset or during switchccs or rebuilds. Conditions: Card resets Workaround: None |
CSCdm46790 | Symptom: dspswlog has SWERR 501, possible ABORT 3000000 (3M). dspprf r t shows overflows from DYNM region. dspprf m t shows high memory usage in TRNS process. nwstats shows a very high number of received bandwidth updates (fcode 80 has one of the highest message counts). Conditions: When the bandwidth for a connection is increased the nodes along the connection path are locked until the process is completed. If there are multiple nodes attempting to increase connection bandwidth at the same time there may be a collision if the connection paths go through the same node. A collision is when a node attempts to lock a node that is already locked. When this occurs, the locked node sends a message saying that it is already locked, and the locking node aborts the lock on all nodes along the connection path. If there are changes that affect adaptive voice connections a node will broadcast a message to abort a lock. The memory leak occurs whenever a node is locked for a bandwidth change, and receives a message to abort the lock. It is possible that this could happen while bandwidth is changed due to user configuration (frame relay connection configuration) or FAX/modem upgrade, but it is unlikely due to the low rate of change and the low probability that a locked node will receive a second request to lock. The memory leak is most likely to be observed in networks which have PCM, ADPCM, or LDCELP connections, and have adaptive voice enabled (cnfswfunc) because the bandwidth lock abort message is broadcast to all nodes. Workaround: Use cnfswfunc to disable 'Adaptive Voice'. Switch CC after disabling adaptive voice to free any leaked memory. If adaptive voice cannot be disabled, monitor the network for memory accumulation and switch CC if memory accumulation is observed. Use existing memory accumulation maintenance guidelines to determine when a switch CC should be performed. Existing audit scripts for SW release 8.4.xx will need to be modified for changes to the memory display screens. Further Problem Description: The SWSW will be changed to not leak memory when a node which is locked for a bandwidth update change receives a message to abort the bandwidth update lock. |
CSCdm47814 | Symptom: Software error 9000, indicating an improperly aborted selftest, after uptrk or upln on a UXM. Condition: No special condition. Workaround: Turn off the selftest or wait for it to finish when activating the card. |
CSCdm48694 | Symptom: CMGUI for the ATM ports of a BXM card is not available. The message "No ports on this card" is printed on selecting the pop-up port for the card. Condition: BXM card is a yred card and the command "switchyred" was given for this card to change the status of the primary card to standby. Workaround: switchyred back to the primary card (if possible) should solve the problem. |
CSCdm49385 | Symptom: In case of Controller Card Redundancy, hitless rebuild may cause switchover and new standby card may never come out of hitless rebuild. Condition: During Hitless Rebuild if some null pointer/ memory corruption is detected, which in turn again triggers hitless rebuild and so on. Workaround: Force FULL REBUILD on standby card |
CSCdm49988 | Symptom: BXM cards went to mismatch when upgraded BPX nodes from 9.1 to 9.2.01. Condition: The cards upgraded firmware from MCC to MDA were OK in 9.1.08 until upgraded to 9.2.01. Workaround: Provided the memory patched to correct the pg_max_lcns = 16352; (16320) |
CSCdm51212 | Symptom: 300000 Abort logged on the standby BCC of a BPX node with 16K connections Condition: If a full rebuild is done on a BPX node having a card with all 16,000 connections on the same card. Workaround: Not to have 16K connections on the card. With 15K connections on the card and no other connection on the node, this symptom has not been seen. |
CSCdm54599 | Symptoms: This problem is likely to manifest after a switchcc or an upgrade and results in loss of continuity to a large number of connections. Workarounds: The best way is to clean up the database manually (change memory) Other things are more drastic and not fool-proof, including deltrk / addtrk, and node rebuild. |
CSCdm54814 | Symptom: There are several symptoms of this defect as follows: - After a rebuild or switch over software error 549, 886 and 2071's are logged. - One or more software error 928's are logged when a UXM line is upped. - The switch indicates that "Maximum number of logical ports exceeds" but there are fewer than 65 UXM lines up. - A UXM line disappears from the 'dsplns' output after a rebuild or switch over. Conditions: This can occur on an IGX that has frame relay lines (FRM, UFM, etc.) as well as ATM lines (UXM), a rebuild is done and then lines are deleted. See Further Description for more information on how this can come about. Workaround: This problem is essentially caused by the logical line and logical port databases getting out of synch with each other (see Further Description). The defect resolution for CSCdm43412 has corrected the code so that these databases can no longer get out of synch. However, once the databases are out of synch, they will remain out of synch and cause the symptoms mentioned above until the databases are cleaned up as follows: 1) Do a dsplns to obtain a listing of all of the IGX's lines. 2) Filter out all of the lines that are not UXM lines. 3) Do a 'dsplogcd 10 slot' for each slot that has these lines, and obtain the logical port number from page 3's output. Find the logical port number for each line 4) Sort the logical ports in ascending order to make the next step easier. ---Now comes the tedious part, finding the corrupted logical port entries--- 5) For each logical port entry (1-64) that IS NOT being used for a line, do the following steps. 6) If the slot is 33, but the port state is other than 0, then we have an entry that will eventually cause a 928. Note all such logical port entries. 7) If the slot is not 33, then we have an orphaned logical port, which will never be deallocated, and will decrease the total number of ports that can be upped on the switch. Note all such logical port entries. ---- Now comes the cleanup ----- Background: When we allocate a UXM line, we start at the first logical port entry and search for the first available, logical port. The logical port is available if its slot value is a 33 and its state is 0, inactive. We will need to up lines so that there are no "free-log-port-holes" in the logical port database. I.E. Suppose you had 3 line up and they used logical ports 1, 3 and 6. Moreover, suppose you had 4 corrupted logical port entries (an orphan or one that will cause a 928) and these 4 corrupted logical ports where at 2, 7, 8 and 9. Then the "used" logical port entries would be 1, 2, 3, 6, 7, 8 and 9 and "free-log-port-holes" would be at 4 and 5. This means that the next two lines that are upped will use 4 and then 5, respectively. To be able to clean up corrupted entries 7, 8 and 9, we will need to up two lines to fill the "free-log-port-hole". To cleanup we need to get the on-line and BRAM databases in synch, which can be done as follows:
|
CSCdm54814 - continued | 8) Up lines to fill the free logical port holes. 9) Starting with the largest corrupted logical port entry we found and working backwards, do the following: a) Invoke 'dlprt' on the logical port entry, and obtain the memory address of the logical port entry from the field "Address:" b) The memory location for the slot field is (address + 42), do a patch memory to change the value to a 0x21 (33). This sets the slot to NULL_CD. c) The memory location for the port state is (address + 4), do a patch memory to change the value to a 0x00. This sets the port state to 0 (inactive). d) Up a line -- it should use this logical port entry. Validate that it uses this entry by doing a 'dlprt' on the entry. The slot and port should match what the line just upped. e) down the line you just upped. This will remove the software and BRAM entries for this line and logical port entry, and update the standby so that its software and BRAM are also up to date. This logical port entry has now been cleaned. f) Repeat the above steps for each corrupted logical port entry, working from the largest to the smallest corrupted logical port entry. Further Description: Prior to the fix for CSCdm43412 we could get the logical line and logical port databases out of sync, as follows: logical line logical port upln FRP 1 n/a upln UXM 13.4 2 1 upln UXM 13.2 3 2 Then when a rebuild, or switchover occurs the UXM's logical ports will get out of sync. as follows: logical line logical port upln FRP 1 n/a upln UXM 13.4 2 2 <<<<< upln UXM 13.2 3 3 <<<<< Now if we do a down line on 13.4 it will also deallocate the logical port #2, which really belongs to line 13.2. We are now in a state where 13.2 has its logical line entry, but its logical port entry is no longer there. Moreover, the logical port entry #1 has no corresponding logical line entry. Now if we load an image that has the fix for CSCdm43412 in it, when we rebuild or switch over we will correctly set the logical ports, however, for line 13.2, it no longer has a logical port entry. So software will log a 549, and later 886's and 2071's will be logged, for the same reason. Moreover when an upln is done we attempt to retrieve the first available logical port entry, as indicated by its slot being NULL_SLOT (33). We will stumble across the logical port entry that was incorrectly de-allocated when we downed line 13.4 earlier, but we also check the corresponding configured bit -- it should be cleared -- but the bit is set because this entry was not correctly de-allocated. The result is that a 928 gets logged. |
The following is the list of fixed anomalies in the 9.2.01 Switch Software delivery. Included with each is a brief discussion of the problem.
| Bug ID | Description |
|---|---|
CSCdj15839 | Symptom: False power supply over voltage or under voltage alarms reported Condition: A bogus minor alarm is generated on IGXs running 8.2.10 for power supplies with hardware revisions AR and AS. The commands dspalms and dsppwr show the problem. Workaround: Run the command 'off2 8'. This will disable all monitoring of the power supply, not just voltage. Fail status, temperature, and voltage will not be collected if "Power Supply Monitor" is disabled. Another workaround is to downgrade to a power supply with a hardware revision below AM (but NOT AM). Additional Information: With this fix in place, voltages and alarms are properly reported for nodes with PEMs installed in all PEM slots; however, a minor alarm will be reported for an empty PEM slot. Please see DDTS document CSCdm14418 for further information. |
CSCdj31366 | Symptom: The clrcnf command does not utilize a double confirmation prompt prior to acting on the users instructions. The warning message is also based on an understanding of the node/switch management operations. Workaround: Do not issue the clrcnf command unless there is the desire to erase the database and cause the node/switch to be removed from operations. Correction: An enhanced display screen with flashing lights and detailed operational messages in used in conjunction with a double confirmation prompting input request. |
CSCdk21503 | Symptom: Software error 921 may be logged when accessing atmTrunkStatsTable using SNMP get operation on an AIT/BTM/ALM trunk. Conditions: The above software error is logged when the above MIB variable is being accessed via an SNMP get operation on IGX/IPX node. Work Around: None. |
CSCdk28204 | Symptom: A software error 526 appears if a card failure event log string is longer than what can fit on the display screen. Conditions: This problem can be created if a dspswlog is done for the screen on which the long string is present. Workaround: None |
CSCdk29850 | Symptom: The protocol type value for an FRP port in the Cisco WAN Manager database is 0. Conditions: Whenever a FRP port is added to the node, the Cisco WAN Manager data base is updated and receives a message with the protocol type field in it. This field can have the value 1. Workaround: Treat the value 1 as a "Non signalling value" (2) |
CSCdk32046 | Symptom: E1 CCS Frame relay lines continue to send Yellow alarm to the remote end after a failure (red alarm) due to cnfclnsigparm 9 being set to 'YES'. Conditions: When an E1 configured for CCS fails and cnfclnsigparm 9 is set to Y. The E1 line will send yellow alarm to the remote end and will continue to do so even after LOS Red alarm is cleared. Workaround: Issue cnfclnsigparm 9 N to disable: 9 CDP & CIP Condition CCS Lines? [YES] |
CSCdk40766 | Symptom: The modem session for an UVM connection failed. Conditions: The modem session always fails for a local (dax) UVM connection. About 5% chance of failure for an inter-node connection. Workaround: No work-around. |
CSCdk47079 | Symptom: Software tries to access the invalid memory entry cause the ABORT when user executes the dth command. Condition: While doing the dth command, and the memory is corrupt thus cause the switch abort. Software error 1000003 is logged. Workaround: Make sure you clean up the unexpected event first. Do cth then dth. |
CSCdk52672 | Symptom: If a connection is added from a node to some other node which had just done a switchcc, the connection gets deleted. Conditions: The slave endpoint of the connection should be on a node which just did a switchcc. Workaround: Connection additions should be done approximately 10 minutes after switchcc. |
CSCdk56688 | Symptom: When trying to execute the command hipri, get the error messages. Correct the earlier error and then execute it, it may come up with another error and so on. Conditions: Need to execute the hipri command when it's supposed to work. Workaround: Login into the control port with the proper privileged level and then execute the command hipri as the first command immediately after login. This really isn't the workaround, just the way it's supposed to be. |
CSCdk69440 | Symptom: 'dspprf' shows IDLE very low when many UVM cards in IGX chassis with switch software 9.1.04 Conditions: 'dspprf' is as low as 27% Workaround: When turning off either 'off2 1' or 'off2 10' or 'off1 16' parameters the idle time rises to over 70%. Disabling Modem Test (off1 16) will disable modem upgrade detection capability on the node. |
CSCdk69498 | Symptom: The A-Bit status of a connection is not correctly displayed on LMI failure at the user end over a frame relay NNI link. Conditions: Environment is not an issue as this happens on the customers network and in the LAB with just a single node. This problem has only been seen on 9.1.03 and 9.1.04, although it is suspected in all releases of 9.1, 8.2 and 8.5 have been tested and work correctly. Workaround: None |
CSCdk72199 | Symptom: Trunk Capacity is not displayed correctly on a DSPLOAD of an IMA group. Trunk on UXM and IMA T-1 Back cards. One end of the IMA trunk shows a reduction in available receive bandwidth though all physical lines are clear of alarms. Connections fail if their bandwidth requirements exceed the available bandwidth on the reduced side. Conditions: This has been observed when IMA physical line failure and repair events occur in rapid succession. Workaround: Three possible workarounds are available: 1. Call TAC and have them issue manual updates 2 command. 2. Delete and re-add the trunk, if possible. 3. Set the number of retained links equal to the total number of physical lines in the IMA trunk group. If the loading problem was encountered, workaround 1 or 2 must be done first. |
CSCdk74438 | Symptom: The job does not take 8/8 option. Conditions: N/A Workaround: Manually create the connection. |
CSCdk82927 | Symptom: Slow response and time-outs when telnetting from CAT5000 or NMS workstation to IGX switch LAN port running 9.1.04. Most of telnet sessions disconnect after 5 minutes. Average delay is between 3-4 seconds for telnet connect. Conditions: Relatively new switch without large quantity of traffic running on it. telnet, tcp, nwip, and snmp are set to defaults. Lan is configured with IP, subnet, gateway, and default port number. Switchcc does not increase telnet connect time. Workaround: Telnet from a NMS workstation with acceptable telnet delay set above 4 seconds. |
CSCdk83511 | Symptom: When issuing a 'tstconseg' on a connection endpoint, the software passes a returned F5 OAM Segment loopback with a correlation tag different from what was sent. This is in violation of ATM Forum specification UNI 3.1 section 3.5.3.2 But CLI indicates test passed. Conditions: BPX switch software: 9.1.04 BXM firmware: M.B.Y 'tstconseg' on a connection endpoint Workaround: None Further Problem Description: Non-compliant with ATM forum, ITU and Belcore specifications. |
CSCdk87005 | Symptom: The addcon command using the avoid satellite links in 8.5 and 9.1 needs to have all the optional parameters entered as stars before the *s can be used. i.e. addcon 8.1.100 igx32-1 9.1.100 4 * * * * * * * * *s Shouldn't need the starts for optional parameters. Condition: Always happens Workaround: Use the full command for specifying restrictions (with the *'s for the optional parameters). |
CSCdk91395 | Symptom: A vague error message ("BW PARAMS: Unknown response (xx)") is returned to user when a connection's remote PCR value is configured to a value higher than the maximum port speed. Condition: This happens when the cnfcon command is executed. Workaround: None |
CSCdk92892 | Symptom: There is no obvious symptom when this problem occurs. This problem consumes more trunk bandwidth than what the connection needs. Conditions: This problem occurs to the G729 connection only. The problem occurs when a FAX session is terminated from active state. When a G729 connection upgrade to the FAX session its bandwidth is configured to be 64Kps. When the FAX session is over, the connection's bandwidth should be configured back to 8Kps. But due to the software bug the connection's bandwidth remains in 64Kps. Workaround: dncon and then upcon. Further Problem Description: There will be no any problem to the connection when this problem occurs. The only problem is that the system bandwidth is not used efficiently. |
CSCdm05373 | Symptom: Most of time no specific symptom shows up. Sometime channel configuration may be corrupted. Conditions: When a channel configuration changes this problem may occur. But if the default channel configuration is used then there is no problem. Workaround: Reconfigure the channel again. |
CSCdm07825 | Symptom: When the customer enables TFTP interval statistics with an invalid configuration the switch logs a 2065 and the SCM receives the following error string: Node=l2a Undefined TFTP Error num=28 text=021, Bucket interval (5m/300s) is not a multiple of Invalid obj type polling interval(900s) Condition: This will occur when the customer attempts to enable statistics with an invalid bucket interval. Bucket intervals must be a multiple of the switches largest polling interval. i.e If the switches largest polling interval is 15 minutes and 5 minute buckets are enabled, then that would trigger this error. Impact: This has minimal customer impact. The switch is logging a software error because it cannot correctly formulate the return error string. This then means that instead of telling the customer which object type has the largest polling interval it will say "Invalid obj type". However, it still specifies how large the largest polling interval is, therefore the customer still has enough information to correct the problem. Workaround: None |
CSCdm10020 | Symptom: Both the BPX routing node and the IGX feeder node are at 9.1 level. After upgrading the IGX feeder node to 9.2, the LMI communication between the 9.1 BPX routing node and 9.2 IGX feeder node is broken. Conditions: The problem only occurs when the feeder node is a 9.2 IGX and the routing node is a 9.1 BPX. Work around: Upgrade the BPX routing node to 9.2 before upgrading the IGX feeder node to 9.2. |
CSCdm13012 | Symptom: Upping the 32nd log interface results in BXM cards going into failed state. Condition: BXM supports only 31 Log Interfaces per card. But software allows 32 logical interfaces (31 virtual trunk and 1 port). Bringing up the 32nd log interface will result in card going into failed state. Workaround: Bring down the last port/trunk which was upped and reset the card. Make sure that we do not configure more than 31 log interface per card. |
CSCdm15043 | Symptom: There may exist dangling lcns, which indicate one less connection to add on the card. Conditions: There are two conditions when this may happen: 1. If addcon fails with "Warning: Inconsistent shift mode" 2. After executing the command rbldcondb, if there are software errors 614 & 612. Workaround: Switchcc will clean up the dangling lcns. |
CSCdm16904 | Symptom: Processor card repeatedly sends message 0x52 to the UXM card for all the dax connections. Condition: Dax connections are added on an IGX node, with %Util less than 100. Switchover is performed. Workaround: Dax connections cannot have %Util less than 100. Do not add dax connections with %Util less than 100.
|
CSCdm17109 | Symptoms: Software error 526 appears in the error table. Description: This can be caused by running certain user commands, such as dsptrkerrs. The problem occurs when the command is run on a trunk or physical line with a long address, so the address does not fit in the space available. This causes a minor alignment problem in the display. Workaround: The software error 526 is not an indication of any problem beyond the display misalignment. Just clear the error table. |
CSCdm17582 | Symptom: "dspcmi l 2" command shows value of 0 for "CdRed Chan:" for BXM card following a graceful upgrade. Conditions: This is seen after a graceful upgrade from Rel. 9.1 to Rel 9.2. Workaround: None Problem Description: This will not be a service affecting problem. It is only seen in an upgrade from 9.1 to 9.2. The APS feature uses CdRed Chan and APS did not exist in Rel. 9.1 so CdRed Chan is defaulted to 0. When card redundancy is added to 2 BXM cards, the CdRed Chan is computed at that time based upon how many channels the card supports. The default value is not used for this computation. |
CSCdm20480 | Symptom: Incorrect card state Conditions: When a failed UFM card is exchanged with another UFM, this problem occured. Workaround: Remove the card and plug the card back in. |
CSCdm20716 | Symptom: When switching controller cards, some connections for which this node is a VIA or SLAVE node may reroute. Conditions: Occurrence is related to the presence of Virtual Path Cons (VPC). When a switchcc is done on a slave or via node for a VPC, there is a chance that one unrelated con could reroute for every VPC. There is also a chance that the VPC may reroute. Graceful upgrade of a node can cause this to happen, too. Details: VPCs may have conids that are duplicates of conids assigned to VCCs. The VPC conid space is managed separately from the VCC space. Trunk translate verification of the neighbor update message currently tries to match the trunk xlat entry from the VCC space against the con info for the VPC. This inevitably does not match, and the VCC con is rerouted. When there is no VCC con with a conid matching the VPC, no con is rerouted, though a swerr 331 occurs if the Neighbor Update Debug switch is on. Cons appear to recover properly after the reroutes. Workaround: None |
CSCdm22316 | Symptom: Traffic going out of the VSI feeder endpoint will be mapped to the wrong VPI/VCI. Conditions: A connection is added from a VSI feeder endpoint to any other endpoint. Traffic is passing from the other endpoint to the VSI feeder endpoint. Workaround: There is no workaround for this. |
CSCdm23206 | Symptom: Command cnfcon gives the following error message: "Extraneous value entered, ignore and continue (y/n)? " Condition: Command cnfcon was given for an ATM non-dax connection, such that all the parameters were entered on the command line at the same time, rather than entering one by one. Workaround: None. However the problem is harmless unless you need to give cnfcon in a script file. Just press 'y' and enter the value of the parameter 'Trunk Cell Routing Restrict' if/when prompted. Command would work fine. |
CSCdm23489 | Description: After a graceful upgrade from 9.1 to 9.2, connections throughout the network were manually downed and then upped using the UI commands dncon and upcon. Most of these tests completed successfully. However, on one node, not all of the conns were successfully upped, and a software error 514 was logged. Workaround: It is not clear whether there could be a problem with either the dncon or upcon command. Use them only when necessary. |
CSCdm23669 | Symptom: The port got the wrong value FFFFFFFF. This value is out of range of the port number allow. Condition: This happen when a trunk is deleted. It happen for 9.2.0I in regression network Workaround: None |
CSCdm24282 | Symptom: Software error 1000003 logged. Condition: Command cnfch was executed for a BNI trunk. Workaround: None |
CSCdm25268 | Symptom: After upgrading from 9.1 to 9.2 The feeders are in loop. Conditions: The problem only happens after an upgrade from 9.1 to 9.2 on a BPX/IGX node with feeder(s) attached. Workaround: None |
CSCdm25595 | Symptom: Upon upgrade (9.1.09 to 9.2.0J) some connections were seen by the dspcons command but not seen using the dspcon command. Conditions: None Workaround: If the problem is that of dangling logical endpoints. They can be deleted by deleting and re-adding the connection |
CSCdm26897 | Symptom: Free the memory for IP relay message. Condition: This problem is seen when Cisco WAN Manager continuously ping the SES feeder over an UXM feeder trunk. The memory allocated for these message was not free correctly. Workaround: The problem will not occur if there is no ping message from Cisco WAN Manager to the SES feeder. |
CSCdm27681 | Symptom: YRED UXM/IMA trunk cards came up as mismatch after graceful upgrade from 9.1 to 9.2. Conditions: UXM cards are burned with 9.2 UXM firmware before the upgrade. IMA compliance is a new attribute in 9.2. When the switch is gracefully upgraded to 9.2, only non YRED IMA trunk cards inherit the new attribute while the YRED pair will flag the mismatch condition. Work Around: Delete the YRED pair before the graceful upgrade Re-add YRED after the graceful upgrade. |
CSCdm28561 | Symptom: Software error 4225, 614, 534, 612, 4208, and 3058 are logged. As mentioned in the Eng-note and Description, the 4225 error caused the rest of the errors to be logged. Condition: The 4225 error was logged on a node which has jobs that do switchcc, full/hitless rebuilds, delcon/addcon, and rrtcon. WorkAround: None |
CSCdm28721 | Symptoms: Software error 532 logged. Conditions: Run deltrk with invalid slot number between 16 and 32 Workaround: None |
CSCdm29043 | Symptom: Card error 0x25010022 appears. Conditions: A BXM with APS 1+1 trks/lines configured reports card errors when node rebuilds. Work around. None needed, should self correct, and program correctly when active card is configured. Description: The standby card is being configured and programs the active card's card redundancy channel before that card is ready, causing card errors. |
CSCdm29706 | Symptom: To configure HCF shift to "on" or "off" on a port, the connections must be deleted and the port downed and upped. Workaround: Delete all the connections, down the port, change the parameter, up the port, and re-add all the connections. |
CSCdm30018 | Symptom: The "Trunk cell routing restriction" may not be prompted for ATM connections when executing the addcon command. Condition: This happens only on IGX and occurs intermittently (may or may not happen). Workaround: If connection is being added between IGX-BPX, execute the addcon from the BPX side. For an IGX-IGX connection, there is no workaround. The trunk cell routing restriction will be set to FALSE except for VPC connections. |
CSCdm30262 | Problem: When we have vtrk up on one port and then we up a trunk (vtrk) with multiple ports grouped i.e. IMA trunk, we can add the above port and IMA port group by "cnftrk" command. This should not be allowed as the port where we upped the vtrk before upping an IMA trunk, belongs to different trunk. Workaround: Do not add ports in "cnftrk"-> IMA port group option, with vtrks upped on those ports and are not part of this IMA group. |
CSCdm30359 | Symptom: addcon for a dax path connection fails with error "Local channel unavailable". Condition: Tried to add a dax path connection as follows: >addcon a.b.c.* <node_name> x.y.z.* Where a connection such as x.y.c.d already existed where c is not equal to z and d can have any value. Workaround: - Delete the connection x.y.c.d if possible or - Change the vpi of a.b.c.* to a value say 'n' such that connection x.y.n.d does not exist, where 'd' could be any number. |
CSCdm30608 | Symptom: Software error 55 (BAD_CD_TYPE), after using addalmslot on an ARM card. There are more subtle problems, such as line statistics not being polled / responded to properly, and other statistics related errors occurring. The database becomes corrupted for a slot (usually 4, but could be 12,20, or 28) The corruption can be seen by doing dspcmi l <slot> Workaround: Don't use addalmslot; or, don't use above mentioned slots. If those slots must be used, then activate the slots after addalmslot has been done. |
CSCdm31674 | Symptom: In a T1 (CCS) environment, IGX cannot notify PBXs of a connection failure within the network. Conditions: In a T1 (CCS) environment -- in which T1 channels do not use Robbed Bit Signalling (RBS), and channels status information is conveyed between PBXs in a d-channel -- IGX cannot notify the PBXs of a connection failure within the network since the d-channel is carried transparently through the IGX network. Workaround: None Further Problem Description: In a voice E1 CCS environment, there is an super-user IGX command to handle this situation: cnfclnsigparm, option 9. If the option is enabled, IGX generates an alarm for a whole circuit lines if any channel connection in that line is failed in the IGX network. |
CSCdm32384 | Symptom: Comm. fail or no continuity on connections after switchcc or hitless rebuild. Condition: The comm. fail happens because a blind channel LCN was reallocated to a routing channel on a BXM card when the node is in switchcc or hitless rebuild mode. BXM routing channel rebuild is done a little later after local rebuild is done which leaves a window of possible LCN reallocation and may cause either comm. fail or no continuity on connections. Workaround: Avoid rerouting or adding connections while the node is in switchcc or hitless rebuild. |
CSCdm33967 | Symptom: After upgrading from 9.1 to 9.2.00 some BXM trunks go briefly into Comm Fail. Conditions: There is definitely a race condition here. Otherwise the rule is that a trunk s.p goes into Comm Fail, if trunk s.(p-1) exists. Workaround: None Further Problem Description: All Comm Fails are caused by data mismatches due to a change in 9.2 that moves up transparent channel programming by one channel. |
CSCdm34282 | Symptom: The maximum route cost of a connection could be incorrect after a graceful upgrade from release 9.1 to 9.2. Conditions: This problem only happens during 9.1 to 9.2 graceful upgrade. Work around: Re-configure the maximum route cost of a connection by using the CLI cnfrtcost. |
The SNMP IGX/BPX switch SNMP MIB is being provided with the delivery of Release 9.2.10 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.
The following Switch MIB changes were introduced in Release 9.2.
The object identifiers that are assigned to various hardware platforms, and hence are returned as values for sysObjectID:
cisco OBJECT IDENTIFIER ::= { enterprises 9 }
ciscoProducts OBJECT IDENTIFIER ::= { cisco 1 }
ciscoIGX8410 OBJECT IDENTIFIER ::= { ciscoProducts 232 }
ciscoIGX8420 OBJECT IDENTIFIER ::= { ciscoProducts 233 }
ciscoIGX8430 OBJECT IDENTIFIER ::= { ciscoProducts 234 }
ciscoIGX8450 OBJECT IDENTIFIER ::= { ciscoProducts 235 }
ciscoBPX8620 OBJECT IDENTIFIER ::= { ciscoProducts 237 }
ciscoBPX8650 OBJECT IDENTIFIER ::= { ciscoProducts 238 }
ciscoBPX8680 OBJECT IDENTIFIER ::= { ciscoProducts 239 }
switchIfTable: This table supports functions equivalent to CLI commands uptrk, dntrk, addtrk, deltrk, upln, dnln.
New object:
.switchIfScTmpltId
Modified objects:
. switchIfAdmStatus
. switchIfPartiId
. switchIfCtrlerId
atmPortTable: This table provides the manager a detailed view of the ATM ports available on the switch.
New object:
. atmPortVcShaping
lineChan Table: This table provides the manager access to read and configure a voice/data/svc channel.
The voiceChannel Table was obsoleted and replaced by lineChanTable
New object:
.lineChanIdleCodeSuppr
atmEndptTable:
Modified object:
. atmEndptMinAdjustICA
The following objects are under the branch of shelfCnfgObject:
Modified object:
. shelfCnfgNodeType
New object:
.shelfCnfgVcPollRate
.shelfCnfgInternalFdrEthIPAddr
.shelfCnfgInternalFdrNwIPAddr
.shelfCnfgAverageIdle
The following objects are under the branch of shelf information:
shelfSlotInfoTable:
Modified objects:
.slotCardStatus
. .slotFrontLnFormat
.slotBackNumPort
.slotBackSonetMode
ds3LineStatsTable:
Modified objects:
.ds3StatsPktCrcs
The following describes the MIB variables for the fpRoutingTrunks table.
fpRoutingTrunks table:
Modified objects:
. fpRteTrkOeNdType
The following describes the MIB variables for the atmTrunks table.
atmTrunks table:
New objects:
. atmTrkIMAProtocolOption
.atmTrkIMADiffDelay
. atmTrkIMAClockMode
. atmTrkHdrType
. atmTrkVcShaping
Modified objects:
. atmTrkRcvRate
. atmTrkVPI
. atmTrkOeNdType
. atmTrkGtwyChCount
.atmTrkRetainedLinks
. atmTrkImaWindowSize
.atmTrkImaTrnsCnts
.atmTrkImaReenableTimer
rsrcPartiTable:
This table provides the manager a detailed view of the ATM ports or trunks resouces available on the switch.
Modified objects:
. rsrcPartiId
.rsrcPartiAdminStatus
. rsrcPartiPvcMaxLcns
.rsrcPartiPvcMaxBw
atmQbinTable:
This table provides the manager a detailed view of the ATM ports or trunks queue parameters available on the switch.
Modified objects:
. atmQbinEntry
. atmQbinId
. atmQbinAdminStatus
. atmQbinEfci
Obsolete object:
.atmQbinMinBw
New objects:
. atmQbinTmpltCnfg
. atmQbinVcShaping
.atmQbinEpd
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
System-Wide Parameters
1 Max Time Stamped Packet Age (msec) ................................ 32
2 Fail Connections On Communication Break ........................... 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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
1 Update Initial Delay [ 5000] (D) 16 TFTP Memory (x 10KB) [ 61] (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)
34 Max Via LCONs [50000] (D)
35 Max Blind Segment Size [ 3570] (D)
36 Max XmtMemBlks per NIB [ 3000] (D)
37 Max Mem on Stby Q (%) [ 33] (D)
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
Function Number Status
Trace Msg Sent 1 Disabled
Multi-DB Stby Updates 2 Enabled
Trace Conv Msg 3 Disabled
This Command: on3
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 3.1 Config T3 [96000 cps] BNI-T3 slot: 3
Transmit Rate: 96000 Line framing: PLCP
Protocol By The Card: -- coding: --
VC Shaping: -- CRC: --
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,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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 3.1 Parameters
1 Q Depth - Voice [ 242] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 9070] (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 - VBR [ 100] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 10.1 Config E3 [80000 cps] BNI-E3 slot: 10
Transmit Rate: 80000 Line framing: --
Protocol By The Card: -- coding: --
VC Shaping: -- CRC: --
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,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 10.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 10.1 Parameters
1 Q Depth - Voice [ 202] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [ 9170] (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 - VBR [ 100] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 10.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 6.1 Config OC3 [353207cps] BNI-155 slot: 6
Transmit Rate: 353208 Line framing: STS-3C
Protocol By The Card: -- coding: --
VC Shaping: -- CRC: --
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,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 6.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 6.1 Parameters
1 Q Depth - Voice [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [15655] (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 - VBR [ 100] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 6.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 2.1 Config OC3 [353207cps] BNI-155 slot: 2
Transmit Rate: 353208 Line framing: STS-3C
Protocol By The Card: -- coding: --
VC Shaping: -- CRC: --
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,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 2.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 2.1 Parameters
1 Q Depth - Voice [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - VBR [ 1000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [15655] (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 - VBR [ 100] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 2.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 9.1 Config OC3 [353207cps] BXM slot: 9
Transmit Rate: 353208 Line framing: STS-3C
Protocol By The Card: No coding: --
VC Shaping: No CRC: --
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,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 9.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 9.1 Parameters
1 Q Depth - Voice [ 885] (Dec) 15 Q Depth - CBR [ 600] (Dec)
2 Q Depth - Non-TS [ 1324] (Dec) 16 Q Depth - VBR [ 5000] (Dec)
3 Q Depth - TS [ 1000] (Dec) 17 Q Depth - ABR [20000] (Dec)
4 Q Depth - BData A [10000] (Dec) 18 Low CLP - CBR [ 60] (%)
5 Q Depth - BData B [10000] (Dec) 19 High CLP - CBR [ 80] (%)
6 Q Depth - High Pri [ 1000] (Dec) 20 Low CLP - VBR [ 60] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 9.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 11.1 Config OC12 [1412679cps] BXM slot: 11
Transmit Rate: 1412830 Line framing: STS-12C
Protocol By The Card: No coding: --
VC Shaping: No CRC: --
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,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 11.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 11.1 Parameters
1 Q Depth - Voice [ 3533] (Dec) 15 Q Depth - CBR [ 1200] (Dec)
2 Q Depth - Non-TS [ 5297] (Dec) 16 Q Depth - 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 - VBR [ 60] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 11.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 12.1 Config T3 [96000 cps] BXM slot: 12
Transmit Rate: 96000 Line framing: PLCP
Protocol By The Card: No coding: --
VC Shaping: No CRC: --
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,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 12.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 12.1 Parameters
1 Q Depth - Voice [ 242] (Dec) 15 Q Depth - CBR [ 400] (Dec)
2 Q Depth - Non-TS [ 360] (Dec) 16 Q Depth - 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 - VBR [ 60] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 13.1 Config E3 [80000 cps] BXM slot: 13
Transmit Rate: 80000 Line framing: --
Protocol By The Card: No coding: --
VC Shaping: No CRC: --
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,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 13.1
sw167 TN SuperUser BPX 8620 9.2.10 Date/Time Not Set
TRK 13.1 Parameters
1 Q Depth - Voice [ 202] (Dec) 15 Q Depth - CBR [ 400] (Dec)
2 Q Depth - Non-TS [ 300] (Dec) 16 Q Depth - 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 - VBR [ 60] (%)
7 Max Age - Voice [ 20] (Dec) 21 High CLP - 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 13.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
System-Wide Parameters
1 Max Time Stamped Packet Age (msec) ................................ 32
2 Fail Connections On Communication Break ........................... 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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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 [ 50] (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 [ 0] (D) 47 Verify CBA for non-FRP [ N] (Y/N)
33 Max Via LCONs [20000] (D)
34 Max Blind Segment Size [ 3570] (D)
35 Max XmtMemBlks per NIB [ 3000] (D)
36 Max Mem on Stby Q (%) [ 33] (D)
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
Index Status Function
1 Disabled Data Frame Multiplexing
2 Disabled Adaptive Voice
3 Disabled 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 Disabled Virtual Trunks
10 Disabled ABR standard with VSVD
This Command: cnfswfunc
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
Function Number Status Function Number Status
Background Upcard 1 Enabled Dynamic BW Allocation 15 Enabled
Background Updates 2 Disabled Modem Polling 16 Enabled
Standby Terminal 3 Disabled Conn Stat Sampling 17 Enabled
Memory Protection 4 Enabled FastPAD Test 18 Enabled
Comm Break 5 Enabled Neighbor Update Errs 19 Disabled
Comm Fail Test 6 Enabled
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
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
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
Function Number Status
Trace Msg Sent 1 Disabled
Multi-DB Stby Updates 2 Enabled
AIT/BTM/ALM 32h Ext2 3 Enabled
Card Synchronization 4 Disabled
Loop Access Dev Init 5 Disabled
Auto allocate UXM UBU 6 Disabled
Trace Conv Msg 7 Disabled
Automatic Cbus Diags 8 Disabled
This Command: on3
Last Command: dsptrks
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 5 Config E1/32 [10666 pps] BTM slot:5
Line DS-0 map: 0-31 Line CRC: No
Transmit Trunk Rate: 4830 cps Line recv impedance: 75 ohm + gnd
Rcv Trunk Rate: 10666 pps HCS Masking: Yes
Pass sync: Yes Payload Scramble: Yes
Loop clock: No Traffic: V,TS,NTS,FR,FST
Statistical Reserve: 600 pps Deroute delay time: 0 seconds
Gateway Type: BAM
VPI Address: 0
VCI Address: 0
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line coding: HDB3
Last Command: dsptrkcnf 5
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 5 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (D) [ 20]
3 Rx EFCN - BdataB (D) [ 30] 20 Tx EFCN - BdataB (D) [ 30]
4 Gateway Efficiency (D) [ N/A]
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 Voice [ 28] 15 BDataA [ 600] 29 Voice [ 28] 32 BDataA [ 600]
13 Non TS [ 40] 16 BDataB [ 600] 30 Non TS [ 40] 33 BDataB [ 600]
14 TS [14632] 17 HighPri[ 100] 31 TS [14632] 34 HighPri[ 100]
This Command: cnftrkparm 5
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 6 Config E2/3 [1000 pps] BTM slot:6
Transmit Trunk Rate: 19900 cps Payload Scramble: Yes
Rcv Trunk Rate: 1000 pps Traffic: V,TS,NTS,FR,FST
Pass sync: Yes Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pp
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.
HCS Masking: Yes
Last Command: dsptrkcnf 6
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 6 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 4] 15 BDataA [ 2264] 29 Voice [ 111] 32 BDataA [ 2264]
13 Non TS [ 3] 16 BDataB [ 2264] 30 Non TS [ 163] 33 BDataB [ 2264]
14 TS [11365] 17 HighPri[ 100] 31 TS [11098] 34 HighPri[ 100]
This Command: cnftrkparm 6
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 7 Config E3/3 [1000 pps] BTM slot:7
Transmit Trunk Rate: 80000 cps Payload Scramble: Yes
Rcv Trunk Rate: 1000 pps Traffic: V,TS,NTS,FR,FST
Pass sync: Yes Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pps
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.
HCS Masking: Yes
Last Command: dsptrkcnf 7
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 7 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 4] 15 BDataA [ 2264] 29 Voice [ 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 7
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 4 Config HSSI/3 [1000 pps] BTM slot:4
Clock Rate: 50840000 bps HCS Masking: Yes
Transmit Trunk Rate: 111491 cps Payload Scramble: No
Rcv Trunk Rate: 1000 Traffic: V,TS,NTS,FR,FST
Pass sync: No Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pps
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 4
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 4 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 4] 15 BDataA [ 2264] 29 Voice [ 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 4
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 3 Config T3/3 [1000 pps] BTM slot:3
Transmit Trunk Rate: 96000 cps Payload Scramble: No
Rcv Trunk Rate: 1000 pps Traffic: V,TS,NTS,FR,FST
Pass sync: Yes Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pps
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.
HCS Masking: Yes
Last Command: dsptrkcnf 3
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 3 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 4] 15 BDataA [ 2264] 29 Voice [ 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 3
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 8 Config SR/30 [10000 pps] NTM slot:8
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 8
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 8 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - Voice (D) [ N/A] 19 Tx Max Age - Voice (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 Voice [ N/A] 15 BDataA [ N/A] 29 Voice [ 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 8
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 9 Config T1/24 [8000 pps] NTM slot:9
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 9
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 9 Parameters:
1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ N/A] 19 Tx Max Age - Voice (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 Voice [ N/A] 15 BDataA [ N/A] 29 Voice [ 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 9
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 10 Config E1/32 [10666 pps] NTM slot:10
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 10
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 10 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - Voice (D) [ N/A] 19 Tx Max Age - Voice (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 Voice [ N/A] 15 BDataA [ N/A] 29 Voice [ 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 10
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 12.1 Config E3/530 [80000 cps] UXM slot:12
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,VBR,ABR
Statistical Reserve: 1000 cps Deroute delay time: 0 seconds
Header Type: NNI VC Shaping: No
VPI Address: 1
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 12.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 12.1 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 443] 15 BDataA [10000] 29 Voice [ 443] 32 BDataA [10000]
13 Non TS [ 662] 16 BDataB [10000] 30 Non TS [ 662] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 VBR [ 5000] 39 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 VBR [ 80] 45 VBR [ 60] 50 VBR [ 80] 53 VBR [ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 12.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 14 Config E3/3 [1000 pps] ALM slot:14
Transmit Trunk Rate: 80000 cps Payload Scramble: Yes
Rcv Trunk Rate: 1000 pps Traffic: V,TS,NTS,FR,FST
Pass sync: Yes Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pps
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.
HCS Masking: Yes
Last Command: dsptrkcnf 14
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 14 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - 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 (%) 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 Voice [ 4] 15 BDataA [ 1000] 29 Voice [ 443] 32 BDataA [ 1000]
13 Non TS [ 3] 16 BDataB [ 8000] 30 Non TS [ 662] 33 BDataB [ 8000]
14 TS [ 5993] 17 HighPri[ 1000] 31 TS [ 4895] 34 HighPri[ 1000]
This Command: cnftrkparm 14
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 15 Config T3/3 [1000 pps] ALM slot:15
Transmit Trunk Rate: 96000 cps Payload Scramble: No
Rcv Trunk Rate: 1000 pps Traffic: V,TS,NTS,FR,FST
Pass sync: Yes Deroute delay time: 0 seconds
Loop clock: No
Statistical Reserve: 1000 pps
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.
HCS Masking: Yes
Last Command: dsptrkcnf 15
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 15 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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) [ N/A] Tx Age Step2 (D) Tx Age Step (D)
6 Low CLP - 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 (%) 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 Voice [ 4] 15 BDataA [ 1000] 29 Voice [ 532] 32 BDataA [ 1000]
13 Non TS [ 3] 16 BDataB [ 8000] 30 Non TS [ 795] 33 BDataB [ 8000]
14 TS [ 5993] 17 HighPri[ 1000] 31 TS [ 4673] 34 HighPri[ 1000]
This Command: cnftrkparm 15
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 11.1 Config T3/636 [96000 cps] UXM slot:11
Transmit Trunk Rate: 96000 cps Payload Scramble: No
Rcv Trunk Rate: 96000 cps Connection Channels: 256
Pass sync: Yes Gateway Channels: 200
Loop clock: No Traffic: V,TS,NTS,FR,FST,CBR,VBR,ABR
Statistical Reserve: 1000 cps Deroute delay time: 0 seconds
Header Type: NNI VC Shaping: No
VPI Address: 1
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: PLCP
Line cable length: 0-225 ft.
HCS Masking: Yes
Last Command: dsptrkcnf 11.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 11.1 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 15000] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 532] 15 BDataA [10000] 29 Voice [ 532] 32 BDataA [10000]
13 Non TS [ 795] 16 BDataB [10000] 30 Non TS [ 795] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 VBR [ 5000] 39 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 VBR [ 80] 45 VBR [ 60] 50 VBR [ 80] 53 VBR [ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 11.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 13.1 Config OC3 [353207cps] UXM slot:13
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,VBR,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
Routing Cost: 10
Idle code: 7F hex
Restrict PCC traffic: No
Link type: Terrestrial
Line framing: STS-3C
HCS Masking: Yes
Payload Scramble: Yes
Last Command: dsptrkcnf 13.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 13.1 Parameters:
1 Yel Alm-In/Out (D) [ 2500/ 10000] 18 Red Alm-In/Out (D) [ 2500/ 10000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 1952] 15 BDataA [10000] 29 Voice [ 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 13.1 Parameters:
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 VBR [ 5000] 39 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 VBR [ 80] 45 VBR [ 60] 50 VBR [ 80] 53 VBR [ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 13.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 11.1 Config E1/30 [4528 cps] UXM slot:11
Line DS-0 map: 1-15,17-31 Line coding: HDB3
IMA Group Member(s): 1 Line recv impedance: 120 ohm
Retained links: 1 HCS Masking: Yes
Transmit Trunk Rate: 4528 cps Payload Scramble: Yes
Rcv Trunk Rate: 4528 cps Connection Channels: 256
Pass sync: Yes Gateway Channels: 200
Loop clock: No Traffic: V,TS,NTS,FR,FST,CBR,VBR,ABR
Statistical Reserve: 600 cps IMA Protocol Option: Disabled
Header Type: NNI IMA Max. Diff. Dly: 200 msec.
VPI Address: 1 IMA Clock Mode: CTC
Routing Cost: 10 Deroute delay time: 0 seconds
Idle code: 54 hex VC Shaping: No
Restrict PCC traffic: No
Link type: Terrestrial
Last Command: dsptrkcnf 11.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 11.1 Parameters:
1 Yel Alm-In/Out (D) [ 1000/ 2000] 18 Red Alm-In/Out (D) [ 1000/ 2000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 27] 15 BDataA [10000] 29 Voice [ 26] 32 BDataA [10000]
13 Non TS [ 37] 16 BDataB [10000] 30 Non TS [ 36] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 VBR [ 5000] 39 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 VBR [ 80] 45 VBR [ 60] 50 VBR [ 80] 53 VBR [ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 11.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 12.1 Config T1/24 [3622 cps] UXM slot:12
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,VBR,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
Last Command: dsptrkcnf 12.1
ss7 TN SuperUser IGX 8420 9.2.10 Date/Time Not Set
TRK 12.1 Parameters:
1 Yel Alm-In/Out (D) [ 600/ 600] 18 Red Alm-In/Out (D) [ 2500/ 15000]
2 Rx Max Age - Voice (D) [ 20] 19 Tx Max Age - Voice (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 Voice [ 22] 15 BDataA [10000] 29 Voice [ 21] 32 BDataA [10000]
13 Non TS [ 30] 16 BDataB [10000] 30 Non TS [ 28] 33 BDataB [10000]
14 TS [ 1000] 17 HighPri[ 1000] 31 TS [ 1000] 34 HighPri[ 1000]
Rx Queue Depth(D) Tx Queue Depth(D) Rx EFCN (%) Tx EFCN (%)
35 CBR [ 600] 38 CBR [ 600]
36 VBR [ 5000] 39 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 VBR [ 80] 45 VBR [ 60] 50 VBR [ 80] 53 VBR [ 60]
43 ABR [ 80] 46 ABR [ 60] 51 ABR [ 80] 54 ABR [ 60]
This Command: cnftrkparm 12.1
| PCB Description | Latest F/W | Minimum F/W | |
|---|---|---|---|
ASC F/W |
| 5.0.00 | 5.0.00 |
ASC Boot |
| 1.0.00 | 1.0.00 |
CESM-8T1/E1 |
| 4.1.03 | 4.1.03 |
CESM Boot |
| 1.0.00 | 1.0.00 |
FRSM-8T1 |
| 5.0.00 | 5.0.00 |
FRSM-8T1 Boot |
| 1.0.00 | 1.0.00 |
FRSM-HS1 |
| 4.0.14 | 4.0.14 |
FRSM-HS1 Boot |
| 1.0.00 | 1.0.00 |
AUSM-8T1/E1 |
| 5.0.00 | 5.0.00 |
AUSM-8T1/E1 Boot |
| 1.0.00 | 1.0.00 |
| PCB Description | Latest F/W | Minimum F/W | |
|---|---|---|---|
BCC (model B) boot |
| HBJ | HBJ |
BCC3-32 (model C) boot |
| HCM | HCM |
BCC3-64 (model D) boot |
| HDM | HDM |
BCC4V(model H) boot |
| HHM | HHM |
| PCB Description | Latest F/W | Minimum F/W | |
|---|---|---|---|
ASI 155 |
| WHC | WHC |
ASI 155 E |
| WEC | WEC |
ASI-1 2T3/C |
| UCF | UCF |
ASI-2 2T3/B |
| UBK | UBK |
BNI 3T3/C |
| TCM | TCM |
BNI 3E3/B |
| TCM | TCM |
BNI 155 E |
| VDR | VDR |
BNI I55 |
| VBR | VBR |
ASM |
| GAC | GAC |
BXM T3/E3 |
| MDB | MCD |
BXM 155 |
| MDB | MCD |
BXM 622 |
| MDB | MCD |
BME |
| MKB | MKB |
| PCB Description | Latest F/W | Minimum F/W | Comments |
|---|---|---|---|
NPM 32 Boot | RBR | RBR |
|
NPM 64 Boot | RCR | RCR |
|
NPM 32B Boot | RER | RER |
|
NPM 64B Boot | RFR | RFR |
|
| PCB Description | Latest F/W | Minimum F/W | Comments |
|---|---|---|---|
ALM-A | CAE | CAE |
|
ALM-B | CBH | CBH |
|
BTM Model A | IAF | IAF |
|
BTM Model B | IBL | IBL |
|
BTM Model D | IDC | IDC |
|
CVM Model A | DAF | DAF |
|
CVM Model B | DBE | DBE |
|
CVM Model C | DCA | DCA |
|
FRM Model D | FDZ | FDZ |
|
FRM Model E | FEZ | FEZ |
|
FRM Model H | FHB | FHB |
|
FRM Model J | FJA | FJA |
|
FRM Model K | FKA | FKA |
|
FRM-2 | FFD | FFD |
|
FTM Model B | JBJ | JBJ |
|
FTM Model C | JCB | JCB |
|
HDM | SCF | SCF |
|
LDM | LCB | LCB |
|
NTM Model E | NEK | NEK |
|
NTM Model F | NFJ | NFH |
|
UFM-C | ZAN | ZAN |
|
UFM-U | YAH | YAH |
|
UVM-Model A | DAD | DAD |
|
UVM-Model B | DBD | DBD |
|
UVM-Model C | DCA | DCA |
|
UVM-Model D | DDF | DDE |
|
UVM Model E | DEB | DEA |
|
UXM | ABB | ABB | Boot code version AB06 |
| Release ID | Product | Rev. | Model | Image |
|---|---|---|---|---|
SwSw 9.2.10 | Sys S/W IGX 8400 | 9.2.10 |
|
|
| Sys S/W BPX 8600 | 9.2.10 |
|
|
| BCC3-32 (Model C) Boot | M0 | C | HCM |
| BCC3-64 (Model C) Boot | M0 | D | HDM |
| BCC4V (Model H) Boot | M0 | H | HHM |
| NPM 32 Boot | R0 | B | RBR |
| NPM 64 Boot | R0 | C | RCR |
| NPM 32 B Boot | R0 | D | RDR |
| NPM 64 B Boot | R0 | F | RFR |
| Release ID | Product | Rev. | Model | Image |
|---|---|---|---|---|
CWM 9.2.04 | Cisco WAN Manager & SNMP | 9.2.04 |
|
|
| Cisco WAN Manager SCM | 9.2.04 |
|
|
| Release ID | Product | Rev | Model | Image |
|---|---|---|---|---|
BPX 8600 9.2.10 | ASI 155 | C0 | H | WHC |
| ASI 155E | C0 | E | WEC |
| ASI-1 2T3/E3 | F0 | C | UCF |
| ASI-2 T3/E3 | K0 | B | UBK |
| BNI 3T3/E3 | M0 | C | TCM |
| BNI 155E | R0 | D | VDR |
| BNI I55 0C3 | R0 | B | VBR |
| ASM | C0 | A | GAC |
| BXM T3/E3 | A0 | D | MDA |
| BXM 155 | A0 | D | MDA |
| BXM 622 | A0 | D | MDA |
IGX 8400 9.2.10 | BTM Model A | F0 | A | IAF |
| BTM Model B | L0 | B | IBL |
| BTM Model D | C0 | D | IDC |
| CVM | F0 | A | DAF |
| CVM Model B | D0 | B | DBD |
| CVM Model C | A0 | C | DCA |
| FRM (Model H) | B0 | H | FHB |
| FRM (Model J) | A0 | J | FJA |
| FRM (Model K) | A0 | K | FKA |
| FRM (2) | D0 | F | FFD |
| HDM | F0 | C | SCF |
| ALM-A | E0 | A | CAE |
| ALM-B | H0 | B | CBH |
| UFM-C | N0 | A | ZAN |
| UFM-U | H0 | A | YAH |
| UVM Model A | D0 | A | DAD |
| UVM Model B | D0 | B | DBD |
| UVM Model C | A0 | C | DCA |
| UVM Model D | F0 | D | DDF |
| UVM Model E | A0 | E | DAE |
| FTM | B0 | C | JCB |
| LDM | B0 | C | LCB |
| NTM Model E | K0 | E | NEK |
| NTM Model F | H0 | F | NFJ |
| UXM | B0 | B | ABB |
| PCB Description | Part Number | Latest H/W | Minimum H/W |
|---|---|---|---|
IMATM-8T1 | 73-3026-01 | F | A |
IMATM-8E1 | 73-3027-01 | F | A |
IMATM-8T1/B | 73-2451-05 | F | A |
IMATM-8E1/B | 73-2452-06 | J | A |
ASC | 73-2454-01 | N | H |
ASC 2 | 73-2586-01 | B | A |
ASC/B | 73-3456-01 | B | A |
BNM-E3 | 73-2866-01 | B | A |
BNM-T3 | 73-2802-01 | C | A |
BNM-155 | 73-2459-02 | C | A |
FRSM-4T1 | 73-2455-01 | C | A |
FRSM-4E1 | 73-2456-01 | C | A |
SRM T1E1 (B) | 73-2565-01 | C | B |
SRM-3T3 | 73-2464-04 | D | A |
CESM-4T1 | 73-2525-02 | F1 | B |
CESM-4E1 | 73-2541-02 | E2 | B |
CESM-8T1 | 73-2561-03 | C | A |
CESM-8E1 | 73-2562-03 | C | A |
AUSM-4T1 | 73-2990-01 | C | A |
AUSM-4E1 | 73-2991-01 | C | A |
FRSM-8T1 | 73-2367-04 | A1 | A1 |
FRSM-8E1 | 73-2360-04 | A1 | A1 |
FRSM-HS1 | 73-2602-02 | J | A |
AUSM-8T1 | 73-2493-06 | F | A |
AUSM-8E1 | 73-2494-06 | F | A |
FRASM-8T1 | 73-2347-04 | A2 | A2 |
| PCB Description | Part Number | Latest H/W | Minimum H/W |
|---|---|---|---|
BCC-32M (Non -Orderable) | 73-213840-00 | P | A |
BCC-64M (Non-Orderable) | 73-213840-01 | P | A |
BCC-BC (Non-Orderable) | 73-211380-00 | D | A |
BCC-3-32M | 73-3719-02 | R | J |
BCC-3-64M | 73-3720-02 | R | J |
BCC-3-BC | 73-2671-01 | D | C |
BCC-4V | 73-3057-04 | D | B |
ASM | 73-214020-00 | C | A |
ASM-BC | 73-211910-00 | C | A |
BXM-T3-8 | 73-2589-05 | H | A |
BXM-E3-8 | 73-2591-05 | H | A |
BXM-T3-12 | 73-2588-05 | H | A |
BXM-E3-12 | 73-2590-05 | H | A |
T3/E3-BC | 73-2759-02 | A | A |
BXM-155-8 | 73-2490-05 | H | A |
MMF-155-8-BC | 73-2887-01 | B | A |
SMF-155-8-BC | 73-2889-01 | B | A |
SMFLR-155-8-BC | 73-2411-02 | B | A |
BXM-155-4 | 73-2492-05 | H | A |
MMF-155-4-BC | 73-2888-01 | B | A |
SMF-155-4-BC | 73-2890-01 | B | A |
SMFLR-155-4-BC | 73-2412-02 | B | A |
BXM-622-2 | 73-2473-08 | L | A |
622-2-BC | 73-2884-01 | D | A |
SMFLR-622-2-BC | 73-2885-01 | D | A |
RDNT-LR-155-8 | 73-2951-01 | A | A |
RDNT-LR-622 | 73-2945-01 | A | A |
RDNT-SM-155-4 | 73-2950-01 | A | A |
RDNT-SM-155-8 | 73-2948-01 | A | A |
RDNT-SM-622 | 73-2944-01 | A | A |
RDNT-SM-622-2 | 73-2912-01 | A | A |
BNI-3-T3/C | 73-2637-01 | J | A |
BNI-3-E3/B | 73-2638-01 | K | A |
BNI-2-155/B | 73-218100-03 | J | A |
ASI-2-E3/B | 73-216330-01 | F | A |
ASI-2-T3/C | 73-216330-00 | F | A |
ASI-2-155E | 73-218100-02 | J | A |
T3-BC | 73-213070-01 | E | A |
E3-BC | 73-213070-01 | E | A |
MMF-2-BC | 73-214290-00 | D | A |
SMF-2-BC | 73-216270-00 | D | A |
SMFLR-2-BC | 73-216270-01 | D | A |
BME-0C12 | 73-2469-07 | L | A |
| PCB Description | Part Number | Latest H/W | Minimum H/W |
|---|---|---|---|
IGX-NPM-32 | 73-2894-01 | W | A |
IGX-NPM-64 | 73-2895-01 | W | A |
IGX-NPM-32B | 73-2554-04 | L | A |
IGX-NPM-64B | 73-2363-02 | C | A |
IGX-SCM | 73-3341-01 | W | A |
IGX-ARM | 73-218230-00 | B | A |
BC-512011 | 73-212360-00 | D | A |
IGX-NTM | 73-2296-04 | E | A |
BC-6271A-T1 | 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 (BTM/B=AIT+ACM1) |
ACM1 | 73-2921-02 | T | A |
BC-571110A-T3 | 73-2879-01 | L | A |
BC-571210A-E3 | 73-2679-01 | K | A |
BC-571310A-E2 | 73-215940-00 | D | A |
BC-571410A-HSSI | 73-216370-00 | A | A |
IGX-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 |
IGX-UXM-4-155-SMF | 73-2511-03 | D | A |
BC-UAI-4-155-SMF | 73-2703-03 | D | A |
IGX-UXM-4-155-MMF | 73-2511-03 | D | A |
BC-UAI-4-155-MMF | 73-2705-03 | D | A |
IGX-UXM-2-155-SMF | 73-2511-03 | D | A |
BC-UAI-2-155-SMF | 73-2699-03 | C | A |
IGX-UXM-6-T3 | 73-2511-03 | D | A |
BC-UAI-6-T3 | 73-2952-02 | A | A |
IGX-UXM-3-T3 | 73-2511-03 | D | A |
BC-UAI-3-T3 | 73-2954-02 | A | A |
IGX-UXM-6-E3 | 73-2511-03 | D | A |
BC-UAI-6-E3 | 73-2953-02 | A | A |
IGX-UXM-3-E3 | 73-2511-03 | D | A |
BC-UAI-3-E3 | 73-2955-02 | A | A |
IGX-UXM-8-E1-BNC | 73-2511-03 | D | A |
BC-UAI-8-E1-BNC | 73-2932-02 | C | A |
IGX-UXM-4-E1-BNC | 73-2511-03 | D | A |
BC-UAI-4-E1-BNC | 73-3061-01 | C | A |
IGX-UXM-8-T1-DB15 | 73-2511-03 | D | A |
BC-UAI-8-T1-DB15 | 73-2941-02 | C | A |
IGX-UXM-8-E1-DB15 | 73-2511-03 | D | A |
BC-UAI-8-E1-DB15 | 73-2942-02 | C | A |
IGX-UXM-4-T1-DB15 | 73-2511-03 | D | A |
BC-UAI-4-T1-DB15 | 73-3059-01 | C | A |
IGX-UXM-4-E1-DB15 | 73-2511-03 | D | A |
BC-UAI-4-E1-DB15 | 73-3060-01 | C | A |
BC-UXM-4-STM1E | 73-2511-03 | D | A |
BC-UAI-4-STM1E | 73-3364-02 | A | A |
IGX-FTM | 73-2519-01 | M | A (FTM=FTC+ACM1A) |
ACM1A | 73-2930-02 | T | A |
BC-6351A-V35 | 73-213240-00 | E | A |
BC-6352A-T1 | 73-213420-00 | C | A |
BC-6353A-E1 | 73-213410-00 | B | A |
BC-6354A-X21 | 73-214120-00 | C | A |
IGX-HDM | 73-2853-02 | H | F (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 (LDM=LDP+ACM1A) |
ACM1A | 73-2930-02 | T | A |
BC-5286A-RS232 | 73-207180-01 | L | A |
BC-5287A-RS232 | 73-207180-00 | L | A |
IGX-CVM-DSOA | 73-3002-02 | D | A (CVM=CDP+ACM1A) |
IGX-CVM-T1EC | 73-3003-03 | E | A (CVM=CDP+ACM1A) |
IGX-CVM-E1EC | 73-209660-00 | H | A (CVM=CDP+ACM1A) |
BC-6271A-T1 | 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 (FRM-2=FRP+ACM1A) |
BC-6251B-V35 | 73-3253-01 | M | A |
BC-6254A-X21 | 73-211440-00 | H | A |
BC-6355A-X21 | 73-214120-01 | C | A |
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-03 | H | 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 |
Version MEB of BXM firmware supports all the existing interfaces and models of BXM hardware. The following table outlines the various levels of hardware revisions supported for BXM firmware version MEB.
| Model Number | Description | FW model | HW Rev | FW Rev |
|---|---|---|---|---|
BXM-155-4 | 4 port OC3 Line Module (Front Card) | E | B | MEA |
BXM-155-8 | 8 port OC3 Line Module (Front Card) | E | B | MEA |
BXM-622 | 1 port OC12 Line Module (Front Card) | E | D | MEA |
BXM-622-2 | 2 port OC12 Line Module (Front Card) | E | D | MEA |
BXM-T3-8 | 8 port T3 Line Module (Front Card) | E | B | MEA |
BXM-T3-12 | 12 port T3 Line Module (Front Card) | E | B | MEA |
BXM-E3-8 | 8 port E3 Line Module (Front Card) | E | B | MEA |
BXM-E3-12 | 12 port E3 Line Module (Front Card) | E | B | MEA |
| 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 |
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 |
BPX-T3/E3-12 | 12 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 |
There are no new features supported in release MEB.
1. VSI version 2.2 (single partition)
2. ITUT Annex B and configurable SD and SF thresholds for SONET Linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1).
The current default thresholds are as follows:
| BIP Count | Condition |
|---|---|
10^-4 | SF detected |
10^-5 | SD detected & SF clear |
10^-6 | SD clear & SF clear |
1. Support for Virtual Trunking
2. Support for BXM Enhanced Multi-Level Channel Statistics
3. SONET Linear APS on BXM-OC3 and BXM-OC12 (1+1, 2 card, 1:1)
4. Support for card based LMI and ILMI
1. The OC-3 MultiMode Fiber backcards do not support Y-cable redundancy.
2. MEA supports ATM Forum CBR class of service. It does not support the following classes of service:
MPLS
ATMF VBR-rt
ATMF VBR-nrt
ABR
UBR
3. Upgrade from VSI 1.1 to VSI 2.2 is supported in this release. It is not a graceful upgrade. See the upgrade section on page 6 .
4. Customers currently operating MPLS with the 9.1 switch software and MCx firmware should note that either they can run 9.1 with MCx or 9.2.10 or above with firmware MEA. They can not intermingle software and firmware releases for MPLS as they run different VSI versions.
BXM cards with MCC/MDA firmware or later can be smoothly migrated to the MEA version of firmware by using y-cable redundancy. To upgrade a BXM card pair in y-redundancy, first upgrade the standby card with the MEA firmware version and wait for all the configuration to be downloaded into the card. Execute the switchyred command to switch to the card with firmware MEA and burn the other card also with MEA firmware. Follow the standard firmware upgrade procedure for downloading and burning the firmware into the cards.
VSI 1.0 is obsoleted by VSI 2.2 in this release.
1. MEA is fully compatible with 9.1 and 9.2 Switch Software. It has not been tested for compatibility with 8.4 or 8.5 Switch Software.
2. Burn firmware should not be interrupted. Card resets in the middle of burning 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.
3. 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.
4. 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 the 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)
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 will become 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, then execute 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 hardware and firmware:
CSCdm50469 | Symptom: Software error 105 and malloc card errors happened continuously Condition: 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. Condition: 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. |
The following is the list of known anomalies for the MEB version of BXM hardware and firmware:
:
CSCdm66131 | Symptom: After addapsln trunk goes to LOS Condition: 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: Add aps when primary cards are active. |
The following is the list of anomalies for the BXM hardware and firmware that have been fixed in firmware release MEB:
CSCdm50469 | Symptom: Software error 105 and malloc card errors happened continuously Condition: 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. Condition: 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 anomalies for the BXM hardware and firmware that have been fixed in firmware release MEA:
CSCdm09882 | Symptom: Log non fatal message related to RCMP errors. Condition: It is mainly seen in the heat chamber. Workaround: None |
CSCdm18186 | Symptom: AIS status could be randomly be displayed in dspcon Condition: 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 Condition: 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. Condition: 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. Condition: When MC10 is burnt into BXM-OC12 with trunks. Workaround: None |
CSCdm37709 | Symptom: APS line fails to clear channel mismatch after lockout. Condition: 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. Condition: 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 Annex B line. Condition: 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 anomalies for the BXM hardware and firmware that have been fixed by the MDA release:
CSCdm38647 | Symptom: MDA fw may report incorrect number of port-groups when APS channels are set to halved. Condition: 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. Condition: When one or more trunks are failed in the network, there may be a comm break in the network. Workaround: Set all the Virtual trunks to restrict CC traffic. |
CSCdm23827 | Symptom: APS alarm may clear on switchyred. Condition: 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. Condition: BXM fw allowed configuration of networking channel to be bidirectional only. Workaround: None |
CSCdm38647 | Symptom: APS (1:1) trunk goes into comm fail after burning Firmware. Condition: If a manual or forced switch to protection is active on the remote end when the card is reset, it is possible that the trunk may go into a communication failure. Workaround: After the trunk goes into communication failure, cause a forced switch to working and a clear. |
These release notes define the UXM functionality of firmware version ABC which is required to operate version 9.2.10 WAN Switching software. The UXM is a trunks and port card in the IGX 8400 series switch.
UXM firmware revision ABC is needed for 9.2.00 or later WAN Switching system software.
UXM firmware revision ABC will operate under 9.1.XX software, so it can be loaded prior to upgrading switch software to 9.2.
UXM firmware ABC introduces no new features.
UXM firmware ABB introduced no new features.
UXM firmware ABA introduced the following features:
1. Support for Virtual Trunking
2. VC Traffic Shaping on ports only
3. Standards compliant IMA on E1 and T1 interface cards
4. Enhanced Multi-Level Channel Statistics, enables more statistics on each connection
5. Ports and trunks on the same card
1. On the BXM and UXM, for the OC-3 MultiMode Fiber backcards, no Y-Redundancy/hot standby is supported.
2. Traffic Shaping is a new feature on UXM card. The VC/VP traffic shaping shapes each individual connection by scheduling the cells using the WFQ (Weighted Fair Queueing) technique to ensure appropriate conformance dictated by the service provider.In general, traffic shaping provides a tight control on each connection's CDV in order to meet carrier requirement.Also, it prevents any connection dominate bandwidth resources.On UXM, the traffic shaping is on per port basis. Once the traffic shaping is turned on, then all connections added after will have traffic shaping on. For details, please refer to 9.2 feature description and commands.
Before upgrading to this release when UXM cards are to be used, certain legacy cards firmware must be upgraded. See the Compatibility Matrix for cards affected and the exact versions to be used.
Failure to follow this procedure may result in the card not operating. The card should be returned to Cisco if this occurs:
Step 1 First upgrade the boot code by using the same procedure as burning firmware, only specify the boot version in place of the firmware version. Use the C option over D as it is faster. Use boot 6 or greater.
Step 2 After the boot code has been loaded burn the firmware.
Step 3 When Y redundancy trunks are used the red alarm in/out values must be configured to 1.25/1.5 seconds or greater else INVMUX failures will occur and trunk failures will be observed during a Y redundancy switchover. This is due to the IMA protocol and may cause re-route of connections. Use the cnftrkparm command.
None
The following features will be released at a later date:
OAM RAS loopback
Auto link disable on IMA groups is no longer available as the ATM forum standard does not permit it.
1. Multi level Stats has to be configured as the card is initially configured in the down state. The higher levels of statistics contain more information on each connection. As a result the maximum number of connections is limited as defined below:
Level 0 = 8126 conns
Level 1 = 8126 conns
Level 2 = 8126 conns (UXM-E), 4030 conns (UXM)
Level 3 = 4030 conns (UXM-E), 1982 conns (UXM)
2. There is no 9.1 statistics support for UXM cards that were shipped with 9.2 firmware since the UXM card has the default level 1 statistics.
There is 9.1 statistics support for UXM-E cards that were shipped with 9.2 firmware since the UXM-E card has the default level 2 statistics. Level 2 stats include all of the statistics needed to be 9.1 compatible.
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
3. The UXM-IMA and AXIS IMATM are not compatible if the IMA group contains only one T1 or E1 line. Since on the IGX-UXM trunk, the IMA protocol is invoked only if an IMA trunk consists of multiple physical lines, therefore, for a trunk with a single T1 or E1 line, the IMA protocol is not invoked. This implementation is different with MGX 8220 IMATM because the MGX 8220 shelf invokes the IMA protocol regardless of the number of T1/E1 lines in the IMA group.
4. UXM IMA trunk groups must use common clock. Independent clocking is not permitted.
5. On the UXM, for the OC-3 Multi-Mode Fiber backcards, no Y-Redundancy/host standby is supported.
6. It is not recommended to combine ABR and UBR PVCs on the same network. ABR and UBR PVCs share the same Qbin (Class of Service Queue) on the BXM card. However, ABR (VSVD) uses a flow control mechanism which ensures that the traffic source slows down when the Qbin usage exceeds the EFCI threshold. However, UBR does not have a mechanism to slow down. Thus, UBR traffic gains an unfair advantage over ABR. This implementation is not considered a problem, since the decision to share a QBIN for ABR and UBR traffic was intentional, since any best-effort service that one would route over UBR can be routed over ABR (VSVD), with the additional benefit of protecting resources in the network. If there is a real requirement to use UBR PVCs instead of ABR (VSVD), then either (1) add all best-effort PVC's as UBR, or (2) isolate the ABR and UBR paths by using cnfpref and separating ABR and UBR endpoints.
7. Combining FBTC and non-FBTC connections within a Class of Service can cause FBTC connections to not receive a fair share of bandwidth. For example, if VBR connections are added at a terminating port, and some of these VBR connections have FBTC enabled while other VBR connections have FBTC disabled, the VBR connections with FBTC disabled may obtain all of the excess bandwidth before the connections with FBTC enabled receive any of the excess bandwidth. The same holds true for ABR or UBR connections. This only is relevant where FBTC and non-FBTC connections share a Qbin, either at a port or at a trunk.
For a complete list of firmware revisions supported, see the Compatibility Matrix document, which is included in this release package.
UXM model B uses the standards-compliant IMA protocol. This is not compatible with the previous proprietary IMA protocol in Model A firmware.
None.
| Bug ID | Description |
|---|---|
CSCdm48498 | Symptom: With more than 2000 connections routed across [or terminating on] a UXM, the UXM may produce a software error 103 and be automatically reset in about 1:5 'switchcc' or 'rrtcon *' commands. The failure rate increases to about 1:3 'switchcc' or'rrtcon *' commands as the number of connections routed across [or terminating on] the UXM exceeds 7000. When the UXM is reset, all connections are rerouted or temporarily down until rerouted. The UXM recovers, however, it may take several minutes to reroute all connections after the UXM is reset. Configuration: The UXM under test was running FW with baseline revision ABA. Software revision was baseline 9.2.01. For the test case, there were two ports and one trunk on the UXM of OC3 rate each, and traffic on the trunk was about 10% of a full OC3 rate. The connection types were mixed: 700 Interworking Gateway - terminating on a UFM. 1000 CBR - using default settings 500 VBR - using default settings 500 ABR - using default settings. Solution: A fix for the problem is found in UXM firmware revision ABC. |
| Bug ID | Description |
|---|---|
CSCdm28864 | Software error 9081 on Y-redundant IMA trunks |
CSCdm28270 | Symptom: UXM trunk card went UNAVAILABLE after a graceful upgrade from 9.1 to 9.2. Condition: This happens occasionally with UXM firmware ABA. Workaround: None |
CSCdm44427 | Symptom: Connection terminating on a UXM or traversing a UXM trunk may fail the OAM loopback test [refer to 'cnfoamlpbk' command] and begin showing status 'OAM-F'. All connections traversing the problem UXM which have the OAM loopback test enabled will show status 'OAM-F' and fail all 'tstdelay' tests. Connections traversing a problem UXM trunk which do not have the OAM loopback test enabled will show status 'OK', however, will fail 'tstdelay'. Connectivity for real user traffic is unaffected in either case. The failure condition occurs and will persist after the problem UXM experiences a short-term, large burst of OAM packets. Configuration: With 400 connections from each of 20 port cards which support the OAM loopback test, traversing a UXM trunk, and then terminating on 20 additional port cards on the other side of the trunk, the OAM loopback test enabled, traversing a UXM trunk, and then terminating on 20 additional port cards on the other side of the trunk, the failure will occur within a few hours of operation. Failure will occur within a few hours with following setup if all terminating port cards have OAM loopback test enabled: >15 UFM cards @ 400 conns each -> UXM trunk -> >15 UFM cards @ 400+ conns each '>15' greater than 15 terminating cards. The failure is unlikely to occur when there are fewer than 10 terminating port cards with connections which traverse a UXM trunk even though OAM loopback is enabled on all cards. Solution: With more than 15 or 20 terminating cards, there is a possibility of a short-term burst of OAM packets through the UXM trunk. This short- term burst of OAM packets may cause an internal OAM queue error condition. Previous versions of firmware could not recover from this error condition and stop passing traffic. It is necessary to reset the UXM in order to recover from the overflow condition. Firmware revision A.B.B contains a fix for this failure. |
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.
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.
Posted: Thu Nov 18 12:52:32 PST 1999
Copyright 1989-1999©Cisco Systems Inc.