|
|
The 8.5.03 software release supports the existing Cisco StrataCom switch family (including the Cisco StrataCom IGX and Cisco StrataCom BPX) and introduces the following features:
Release 8.5.02 contains a superset of the features from 8.2.3, 8.2.5 and 8.4. For customers upgrading from Release 8.2.x to 8.5.02, this new release will also introduce the availability of features developed in Release 8.4. These are the 8.4 features:
For customers upgrading from Release 8.4.0 to 8.5.0, this new release will also introduce the availability of features developed in the 8.2.1 and 8.2.5 releases.
The following new features were introduced in the 8.2.1 and 8.2.5 releases:
None
If upgrading from Release 7.4, Structured Networks must be flattened before the software upgrade.
If new Control Cards (BCC/NPM/NPC) are to be installed as part of the upgrade to Release 8.4, then the physical card upgrade procedure described below must be completed as a separate activity from the Switch software upgrade.
Statistics collection must be disabled prior to and during the software upgrade process.
Statistics sampling must be disabled prior to the start of an upgrade.
Before upgrading to this release, if there are any ABR connections with an MCR value set to 0, it is highly recommended that the MCR value for each of these connections be set to 1. This is to insure that the Load model will be correct after an upgrade. This addresses a problem in earlier releases which did not handle Load model calculations correctly for connections having MCR=0. This is only an upgrade precaution; MCR=0 is supported in release 8.5.
See the Compatibility Matrix within this document for the tested/supported versions of other firmware and software which work with this release.
Consult CCO for any additional Software Upgrade procedural issues.
Switch software upgrades are supported from Release 8.4.0x and 7.4 to Release 8.5. Upgrades from Release 8.2.5x are supported for IGX/IPX only (BPX is supported in a later release of 8.5).
Due to a limitation in the 8.2.5x to 8.5.02 upgrades, firmware for the BTM should not be upgraded to model B firmware (for BTM rev L's) or model D firmware (on any BTM) until after the control software is upgraded to 8.5.02.
All processor cards must be configured with a minimum of 32 MB of RAM. This includes BCCs, NPMs and NPCs. NPCs and NPMs require at least 1 MB of BRAM.
As specified below, the correct version of BCC boot firmware must be installed on the cards prior to a software upgrade to Release 8.5.
| BCC Type | Firmware |
|---|---|
| BCC-32 | H.B.J |
| BCC-3-32 | H.C.M |
| BCC-3-64 | H.D.M |
| BCC-4 | H.E.M |
The following boot code is required for NPMs and NPCs.
| NPM Type | Firmware |
|---|---|
| NPM-32 (1 M BRAM) | R.B.N or R.E.N |
| NPM-64 (1 M BRAM) | R.C.N |
| NPM-64B (4 M BRAM) | R.F.N |
| NPC Type | Firmware |
|---|---|
| NPC-32 | B.B.F |
| NPC-64 | B.C.F |
Each redundant pair of Control cards in a given node must be of the identical type and memory configuration. This is true for all card types: NPCs, NPMs and BCCs. For example, if the active card is a BCC-3-32, then so must be the standby. BCC-3 cards with 32MB of RAM cannot be mixed with BCC-3 cards with 64MB of RAM.
This is a requirement for all software upgrade and downgrade procedures. It does not apply to the physical card upgrade procedure, as described below.
When performing a Control Card (CC) upgrade, the following procedure must be used. This applies to all processors: BCCs, NPMs and NPCs.
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.
Software upgrades have been tested from and are supported from the following versions of switch software:
Node-by-Node upgrades are not supported from any previous release.
The SNMP IPX/IGX/BPX switch SNMP MIB is being provided with the delivery of Release 8.5.00 Switch Software. The MIB is in standard ASN.1 format and is located in the ASCII text files switch.m, swtraps.m, and errors.m which are included in the same directory as the Switch Software images. These files may be compiled with most standards-based MIB compilers.
The following Switch MIB changes were introduced in Release 8.5.xx
The BTM-E1 trunk card set is supported in two trunk tables, atmTrunks and atmTrunkStatsTable. The ATM trunk attributes are supported in these two tables as they are for BTM-E3 trunks. The atmEndptTable is accessed by atmEndptIndex. Voice connections are supported by cards such as the CDP, CVM, and UVM. Data connections are supported by cards such as the CDP, LDP, SDP, CVM, LDM, and HDM. The "other end" of a connection may be a local feeder trunk, but feeder trunk endpoints are supported by the atmEndptTable instead of dataEndptTable or voiceEndptTable. The voice and data interworking connection segments are created, configured, and deleted via the voiceEndptTable and dataEndptTables, instead of the atmEndptTable.
The bandwidth and class of service parameters for voice and data connection segments are determined by voice and data endpoint objects, such as voiceEndptRateType or dataEndptRate. These parameters may be reflected by objects in the atmEndptTable, but are not configurable there. Some atmEndptTable objects provide default values for the feeder trunk endpoints, but no read-write access is required for them.
A new enumeration is added to slotBackType in shelfSlotInfoTable. Its value is "btmE1"(205). The existing value of "btm"(212) is used for slotFrontType.
The BTM-E1 trunk card set is supported in two media tables, ds1LineTable and ds1LineStatsTable. The media layer attributes are supported in these two tables as they are for NTM-E1 trunk cards.
The lineChanTable contains two objects, lineChanDataDceDte and lineChanDataUcs, for data connection support on channelized data cards such as the CDP or CVM. These are not configurable for channels that have an active voice connection. The existing voice-specific objects in the lineChanTable are not configurable for a channel that has a data connection.
The voiceEndptTableContains a new object, voiceEndptLocRmtLpbk for Tiered Networks.
A new value serialPort(22), is added to switchIfMediaType enumeration.
The dataEndptTable is accessed by dataEndptIndex. Data connections are supported by cards such as the CDP, LDP, SDP, CVM, LDM, and HDM. The "other end" may be a local feeder trunk. The syntax, "slot.channel" or "slot.port" is used in the dataEndptDesc and dataEndptOeDesc strings to create (add) data endpoints. "slot.vpi.vci" is used for feeder trunk endpoints.
dataEndptTable (New)
dataEndptIndex
dataOtherEndptIndex
dataEndptDesc
dataOtherEndptDesc
dataEndptAdmStatus
dataEndptOperStatus
dataEndptRate
dataEndPtRemoteFail
dataEndptNoRouteFail
dataEndptTestFail
dataEndptTestType
dataEndptLpbkStatus
dataEndptLocLpbkEnable
dataEndptLocRmtLpbk
dataEndptConnPtr
dataEndptPortPtr
dataEndptTrkAvoid
dataEndptZCSAvoid
dataEndptFastEia
dataEndptEiaUpdt
dataEndptSampPerPkt
dataEndptTspnt
dataEndptSuperRateN
dataEndptCoding
dataEndptDfmEnable
dataEndptDfmLen
dataEndptOeDceDte
dataEndptOeClk
The serialPortTable allows management of serial data interfaces that are not found in DS1, DS3, or SONET media tables. This does not include any support for control ports, auxiliary, or printer ports. The support for the media layer attributes of frame relay ports, ATM ports, or trunks with HSSI interfaces may be added in later releases, but is not included in the initial switch software release. Typical serialPorts are found on the LDP, LDM, SDP, and HDM cards. The MIB objects for a serial port are summarized in the table below, as well as their constraints for SNMP set-request operations.
serialPortTable (New)
serialPortIfType
serialPortStatus
serialPortDceDte
serialPortClk
serialPortUtil
serialPortEndptPtr
serialPortConnPtr
serialPortEiaUpdt
serialPortDfmEnable
serialPortDfmLen
New objects are added to support the CAS Switching feature of the UVM card type.
circuitLines
cirLineCnfStatus
cirLinePassOe
cirLineCasswMode
cirLineCasConType
cirLineCCSType
cirLineCASType
cirLineCASParm1
cirLineCASParm2
cirLineCASParm3
cirLineCASParm4
cirLineCASParm5
cirLineCASParm6
cirLineCASParm7
cirLineCASParm8
cirLineCASParm9
cirLineCASParm10
cirLineCASParm11
cirLineCASParm12
cirLineCASParm13
cirLineCASParm14
cirLineCASParm15
cirLineCASParm16
cirLineCASParm17
cirLineCASParm18
None
Grouped Connections are not supported, unless they existed prior to the upgrade to this release. In that case, they are carried forward as part of the upgrade. Grouped connections can no longer be created in this release. Existing grouped connections can be modified with the cnfcon command. Please note that this will be the last major release supporting grouped connections.
Priority Bumping is no longer supported.
NPM/NPC-16 is not supported.
Structured Networks are not supported.
IGX Hubs can support up to 4 IPX or IGX feeders. They do not support AXIS Feeders. Each Feeder can have only 1 routing trunk to the Hub.
Voice connections in Tiered Networks cannot support Fast Modem or Adaptive Voice features.
By design, three segment voice and data connections must be added using SV+, rather than using the Switch Software Command Line interface. This will ensure that endpoint information, such as remote-end clocking and remote-end interface type, are cross-configured correctly. If connection segments are added using the CLI, continuity cannot be ensured. DAX connections on feeders must be added using the CLI. SV+ support for this feature will be supported in a later release of 9.0 (SV+ release for 8.5).
The maximum number of ports on the BPX that should be configured with LMI enabled is 36, due to possible performance impact. 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 enabled. This is due to the polling that must be done for the LMI enabled ports. However, if any or all of the 16 possible feeder trunks are not being used on that specific node, then that many additional lines may have LMI enabled. That is, if a BPX is configured with only 2 feeder trunks, then 36 + (16 - 2) = 50 lines can have LMI enabled. Thus, the overall total can be 52 ports, when no feeder trunks exist.
UVM Pass-through is not supported for CAS-Switching.
UVM model B can be configured to interwork with UVM model A by turning off CAS-switching. However, the following restrictions apply:
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.
The feature of CIR=0 for Frame Relay connections is not supported for connections terminating between FRP /FRM cards in IPX/IGX nodes and FRSM cards in an AXIS shelf.
SVC Connections are derouted after decreasing the allocated bandwidth (increasing Stat Reserve). It is the design intent that increasing the statistical reserve will cause SVC conns to derouted and not be rerouted.(See bug CSCst92308).
The FRP port does not show the FECN/BECN frames count. FECN and BECN bits are only registered on the egress port or connection, not the ingress. (See bug CSCst96096).
For the loadrev operation, it is important that the StrataView Plus/TFTP buffers are maintained at their default size.
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.
When using the shift/no-shift feature on a BPX node's port card, controlled via the cnfport command, the other end of the connection must have the same setting. Otherwise, there will be a loss of continuity.
If using the no shift feature to utilize Virtual Trunks across a Cisco/StrataCom cloud operating an 8.1 release, then the node number "2" must either not be used, or be the node connecting to the cloud.
If using the no shift feature to utilize Virtual Trunks across a Cisco/StrataCom cloud operating any Switch Software release, then the ForeSight feature will not be utilized. In general, any connections which are routed or potentially may be routed through Virtual Trunks must not be configured with ForeSight enabled.
If the Stat Reserve field on a trunk is dramatically increased to a value which represents a significant majority of the total trunk bandwidth, and if connections are present on the trunk, the dspload command will show negative values. This is to signify that the trunk is oversubscribed. The trunk load values will eventually reach 0, or a small positive number after all the necessary connections are routed off that trunk. (CSCdi84878)
When deleting trunks, there is a known limitation with the switch software. The deltrk command should always be executed on the node which remains as part of the network, rather than from the node which ends up being removed from the network. This is to ensure that all the necessary updates are sent to the rest of the network. (CSCdi85134). Also, If the command is not used as recommended here, a software error 419 could occur (CSCdi91285).
Due to Trunk Based Loading and the potential latency of distributing Trunk-Based Loading (TBL) updates, any commands having to do with verifying or displaying 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 in cnftlparm) plus the conditional update latency time.
The BXM cannot return Foresight Round Trip Delay cells. Thus, as of this release, the ForeSight adjust interval will no longer be a function of the Round Trip Delay calculation for the connection. Instead, all BXM terminated connections will use the maximum adjust interval. This affects all ForeSight endpoints on AXIS, BPX, and IGX. (CSCdi87455)
The external ABR segment control loop on ForeSight (ABRFST) is an option at the User Interface, but is not supported in hardware. The user should not enable this option on ForeSight connections (CSCdi92451). In any case, there is no coupling between the loops.
A problem has been observed, on several instances, where the time to re-route connections may take over an hour. When large numbers of connections are being re-routed, this can be caused by routing collisions, which means that routing attempts being initiated at different nodes collide when they meet a common node at which point one of the routing attempts must be rescheduled. (CSCdi89734)
On a heavily loaded BPX node, during connection re-routing, the status of a particular connection is indicated as OK even though the line status of the other end of the connection is listed as failed. The connection is in fact OK, because the conditioning of the connection (to update the status for both ends) is done by a low-priority process so that the re-routing of the connections can be given high priority. The status will be eventually updated. (CSCdj10762)
A node whose number is greater than 63 cannot have a clrcnf operation performed on it. This is as designed. A clrallcnf can be done, or the node must be renumbered before running clrcnf. (CSCdj14920)
The interface between a BXM feeder trunk and an AXIS feeder is always considered to be an NNI interface. (CSCdj16808)
The Command Line Interface currently allows a standard ABR VSVD endpoint to be configured (with cnfcon) as a non-VSVD endpoint. This should not be allowed because the BXM does not support this. This should not be attempted since it will cause connection continuity failure. (CSCdj08862)
When adding more than 4000 connections on a BPX node, the VC polling rate must be changed to a higher interval, to accommodate the additional time needed to poll for the statistics for each VC. The cnfsysparm command, parameter 24 must be changed according to the following:
| 0-3999 connections | Polling Rate: 5 Minutes (or higher) |
| 4000-8000 conns | Polling Rate: 10 Minutes (or higher) |
| 8000-12000 conns | Polling Rate: 15 Minutes |
Given a connection that terminates on an IGX FRM at one end and an ASI on the other end, tstdelay initiated at the FRM end may not work if the ASI firmware is below the supported revision and does not support OAM cells as opposed to supervisory cells. This is because the updated BTM on the IGX will always generate OAM cells. Please check the compatibility matrix.
The tstcon command does not work (it indicates continuity failure when it is not the case) when initiated from an FRSM card on an AXIS shelf and the path of the connection passes through an IGX node. (CSCdj23908).
Because the detailed card error event log is not retained within BRAM, this information will be lost should a processor rebuild occur. Therefore, when issuing a dspcderrs command on a particular slot, the display will not show the detailed card error information should rebuild event occur. This functionality has not been modified from previous releases.
The setnovram command can be used on BXM cards to change the number of channel statistics. If this number is set to 0 to increase the number of channels available on the card, dspchstats command will not work properly.
When a physical-layer failure (e.g., LOS) is detected, a Major Alarm is generated, and any connection routed over that port is downed (Fail state). The software sends a command to the remote end of the connection to generate AIS in the egress direction. (CSCdj30543).
Impact:
Since the connection is in a failed state, AIS is generated in the upstream direction (in addition to the downstream direction). Although this does conform to the letter of the I.610 standard, this is not necessarily what a user would expect to see, because it interferes with the RDI response from the end-to-end connection termination point. (A fault in the downstream direction causes a fault in the upstream direction.)
Reason for the current implementation:
The BNI can not generate AIS. If there is a fault at a BNI trunk, the current mechanism is to cause AIS to be generated by the BXM port by downing the connection. Since the BXM can only generate OAM cells from the RCMP, and the RCMP is in the ingress path, the cells must be backward routed to the egress (egress QE). Also, since end-to-end OAM cells are required, the ingress QE must be configured to drop ALL cells in the ingress path. This creates a break in continuity in the opposite direction, and AIS cells must also be generated at the other end of the same connection, in the upstream direction of the original fault.
Future AIS support:
There is a discussion in progress for an improvement, which will apply only to connections that are routed only over BXM trunks (or dax connections).
Two new options are added to cnfcmparm (CSCdj26583):
1) 20 Wait for TBL Updates [ 70] (100 msecs);
2) 21 Max Derouting Bndl (0=all)[ 500] (D)
(TBL is the acronym for Trunk Based Loading)
When you first bring up the image through lanbtld your default values will be 100 for Wait for Trunk Based Loading (TBL) Updates and 258 for Max Derouting Bndl. This is because some fields in CM_PARMS are being reused. The recommended values for these parameters are 70 (for option 20) and 500 (for option 21). These will be the default values if you do a clear mem or upgrade to 8.4.1. If you don't want this new feature:
1) set option 20 to 0
2) set option 21 to 0 (which means all connections)
These parameters are used for:
1) Wait for Trunk Based Loading (TBL) Updates will delay failing the connection if it fails to find a path due to no load and no conid available. This delay allows Trunk Based Loading (TBL) updates to be processed. This value should always be greater than the cnftlparm Fast Interval interval. This will clear some PVC's going in and out of alarm.
2) Max Derouting Bndl works like Maximum Routing Bundle, except it's for the derouting case. Currently we go and deroute all 12,000 connections at one time without giving up the process to handle Trunk Based Loading (TBL) updates, and other tasks. This value will allow us to deroute x number of connections at a time, then go and try to route. Do remember that as this number goes up, the table updates takes a little longer to be sent out, since the node is busy derouting.
There are problems in the downgrade mechanism which can cause database corruption. If downgrade is performed immediately after upgrading, the Stby_Info revision fields are not yet filled in on the new active CC. They don't get filled in until the upcard response from the new locked CC. This causes restart instead of a switchcc. If the locked CC is reset, then downgrade immediately, a restart will occur instead of a switchcc. (CSCdj30811).
During a conditional upgrade or downgrade in the network that has more than 20 nodes, there is a likelihood for some nodes to receive all the updates before receiving the revision change message (to upgrade/downgrade). Since the standby had the update capacity of approximately only 10 mesg/sec, it may take over 3 seconds for these nodes to finish these updates. The revision change update may not be properly delivered to the standby, and thus causes non-graceful upgrade to occurred on these nodes. (CSCdj32054).
In order to test/simulate the Y-redundant switchover of ASI T3 or E3 pairs the resetcd command must be used, or by pulling out the active card. It will not be correctly simulated by doing a dncd (downcard) on the active card. Using dncd will cause cell discards. (CSCdj08923).
In certain conditions where memory is exhausted, an Abort 3000000 can occur, which is fully recoverable. This is due to an accumulation of memory in the telnet process, and the root cause is the improperly terminated telnet sessions that were originated from a StrataView Plus workstation. To prevent this condition from occurring, exit all SV+ telnet sessions correctly by using the CTRL-] key chord and then typing q. (CSCdi92256).
BXM cards can support 32K PVCs only when no stats are collected. If collecting 4 stats per PVC is desired, the number of PVCs per BXM card drops to 16K. (CSCdj31773).
When connection status logging to StrataView Plus is enabled in the switch (via the cnffunc command), when more than 1500 PVC's exist on a node, an event log entry indicating there is a "comm break on flooding" may occur. This is because the network handler is being flooded with messages due to the per-PVC status updates flowing to the StrataView Plus workstation. This is a recoverable situation. However, PVC status may not be available for all connections. (CSCdj36127)
It is not recommended to combine ABR and UBR PVC's on the same network. ABR and UBR PVC's 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 PVC's 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.
Combining FBTC and non-FBTC connections within a Class of Service can cause FBTC connections to not receive a fair share of bandwidth. For example, if VBR connections are added at a terminating port, and some of these VBR connections have FBTC enabled while other VBR connections have FBTC disabled, the VBR connections with FBTC disabled may obtain all of the excess bandwidth before the connections with FBTC enabled receive any of the excess bandwidth. The same holds true for ABR or UBR connections. This only is relevant where FBTC and non-FBTC connections share a QBIN, either at a port or at a trunk.
If a TFTP download has been started, and a fault occurs in the network that interrupts the download, then it is possible to get an software error 513 logged into the software error table. This occurs when there is an attempt to free a memory block that has not been allocated. There is no negative side effect to this attempt, other than the appearance of the error in the table. (CSCdj45311).
Momentary data discontinuity is expected when switchcc is performed. The controller card switchover is likely to produce a traffic break due to reprogramming of the trunks. During switchcc, the routing tables and translation tables on trunks are cleared before they are reprogrammed after a switchover and therefore until they are reprogrammed traffic will not flow. The clearing and reprogramming is necessary to insure consistency between the card configuration and the software database. The expected time before traffic is resumed for all connections is dependent on the number of connections and is in the order of a few seconds/minutes. (CSCdj28246)
Voice I/W connections from CDP/CVM to FTC/FTM must be added from CDP/CVM side as master. CDP/CVM circuit line must be configured to use option 'CAS' for CDP/CVM to FTC/FTM connections.
Switch Software supports up to a combined total of 64 C3801 units or FastPadmm per IGX/IPX node.
The maximum number of FastPADmm cards allowed per IPX/IGX node has been reduced from 576 to 288.
The maximum number of FastPAD ports allowed per IPX/IGX node has been reduced from 1024 to 512.
Only one C3801 unit can be assigned per FTC/FTM port (30 maximum per FTC/FTM card for E1 backcard); the total number of C3801 connections allowed per FTC/FTM is 252.
Switch Software does not support remote connections between C3801 and FastPADmm, C3801 and UFM, C3801 and FRSM, or C3801 and UVM.
Switch software supports up to 16 LDCELP channels per UVM card.
Users man not use the command addcon slot.1-24 v to add 24 voice connections to a CDP/CVM 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/CVM circuit line is an E1, in which case "1-32" would apply instead.
The maximum PVCs per logical port supported for Annex A. Annex D, and StrataLMI is 899, 899, and 562 respectively. These limits are applicable to any supported cards, including UFM-C and UFM-U with maximum frame length of 4510. Switch software DOES NOT prevent user from configuring more # of PVCs on a port than above. If more than supported PVCs are configured, the LMI will not work on a port. The full status message resulting out of such a configuration will be discarded and LMI timeout will occur on a port. This will cause port failure, and potentially lead to the A-BIT failures in different segments of the connection path. (CSCdj33507)
ATM connections from ASI to ALM-A must be added from IGX side as master, and must have VCC header type.
Tstdelay and tstcon commands are not supported on ALM-A end-points for connections made from UFM-U to ALM-A.
ForeSignt/ABT VS/VD are not supported for ALM-A cards.
Asymmetric connections not supported for ALM-A card.
NNI headers are not supported for ALM-A cards.
ILMI and LMI are not supported for ALM-A cards.
SVC signalling and multicast are not supported for ALM-A cards.
Segment OAM cells are not processed for ALM-A cards.
ALM-A cards are not supported on feeder nodes within a tiered network architecture.
For VPC connections on ALM-A cards, the value 3 for VCI is reserved and should not be used. Refer to ALM-A Release Notes for details on ALM-A card/connection configuration.
The maximum value for VPC and VCC is 255 for ALM-A cards.
The percent utilization for ALM-A connections is always 100%.
Frame Relay endpoints must be capable of supporting the ALM-A supported Frame Relay connection type: atfr, aftx, and atft.
The ALM-A drops cells with CLP=1 when the VC queue associated with the connection exceed 80% of the user-specified depth or the system-specified depth. Therefore, if a high level of bursty traffic is expected or if cell discards appear when dsplnerrs command is issued, specify a larger queue size.
There is a problem with node renumbering. Node renumbering (the rnmnd command) should be executed only during a stable network environment and only if absolutely necessary. A stable network environment would be, for example, one in which no connection was added for the past 30 minutes and no topology change was made in the last hour and there are no alarms or node unreachabilities. Node renumbering must only be done when the network is stable to reduce the possibility of certain temporarily blocked messages during the node renumbering process being delivered to the wrong nodes. This would occur after the completion of the node renumbering process.
The settling time for network wide updates can take a long time in certain situations. Specifically, the settling time for updates due to network wide topology changes and connections in a large network when a processor switchover occurs can take a long time. The time is proportional to the number of nodes as well as the number of connections. A general estimate would be 30 seconds per node. During the period of transitions (when the updates are occurring) some network operations such as adding connections might in some cases take somewhat longer to complete.
When using StrataView Plus, there could be a problem with communicating with a node that just had a processor switchover. The problem is within the SPARCstation itself and its caching of EtherNet addresses. It can be solved by execution the following command on the workstation as the superuser: # arp -d <node_name>
Users may not use the command addcon slot.1-24 v to add 24 voice connections to a CDP/CVM 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/CVM circuit line is an E1, in which case "1-32" would apply. (CSCdj14319)
Care must be taken when changing the Deroute Delay parameter, which is controlled by the cnftrk command. This defaults to zero, but if set to anything but zero, connection re-routing, due to a trunk failure, will be delayed as provided by the parameter.
When a switchcc is executed on a BPX configured with two BCC-4 cards and contains a BXM-622 trunk card, there may be a bad clock path problem reported. It is indicated as a Minor Alarm - bad clock path. This is a transitory problem, although the alarm indication persists. To clear this, execute the clrclkalm command.
Currently, T3-3 and T3-2 backcards are not interchangeable between ASI and BNI frontcards, as this has been the case since the introduction of these cards. The backcards must be configured (with setnovram) so as to avoid backcard mismatch. (CSCdj41999)
When the last trunk to a node is deleted and it has 2500+ connections, it will cause software errors 1000's and 590's. This can be avoided by first deleting all connections across the trunk before deleting the trunk. If the problem occurs a switch over or rebuild will clean up the node. (CSCdj25075).
The software error occurs when deleting a trunk that
EFFECT: Not all connections that should be deleted will be deleted. In addition, memory leak may occur.
WORKAROUND: Prior to deleting the last trunk to a node, determine the connections going across the trunk and manually delete them first.
CLEANUP: If software errors 1000's and 590's are received because the last trunk on the node was deleted AND that trunk had 2500+ connections routed across it. The problem can be cleaned up by:
1) Clear the active CC's software log.
2) Check then clear the standby CC's software log.
3) switchcc
If the network does not have a redundant CC then rebuild the active CC by doing the following:
1) Clear the active CC's software log.
2) resetcd <active CC slot>
For grouped connections, if and when all connections of a group are deleted, then the connection group itself should be deleted as soon as possible to avoid any possible side effects that could potentially be caused by having empty connection groups. (CSCdj47562)
The following rare occurrence has been observed: user receives 'connection failed' status when trying to add LDCELP connections after deleting some on-LDCELP connections on a fully utilized UVM. The problem can be cleared by resetting UVM card.
User may receive an error message 'Local device code allocation problem' when adding FR connection on IPX/IGX. No DAX connections can be added. This intermittent problem occurred only twice during the integration/system testing cycle. The root cause is still under investigation.
Voice I/W connections from CDP to FTC must be added from CDP side as master. CDP circuit line must be configured to use option 'CAS' for CDP to FTC connections.
Switch Software supports up to a combined total of 64 C3800 units or FastPADmm per IGX/IPX node.
The maximum number of FastPADmm cards allowed per IPX/IGX node had been reduced from 576 to 288.
The maximum number of FastPAD ports allowed per IPX/IGX node had been reduced from 1024 to 512.
Only one C3801 unit can be assigned per FTC port (30 maximum per FTC card for E1 backcard); the total number of C3801 connections allowed per FTC is 252.
Switch Software does not support remote connections between C3801 and FastPADmm, C3801 and UFM, C3801 and AIX/FRSM, or C3801 and UVM.
Switch software supports up to 16 LDCELP channels per UVM card.
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 instead.
Momentary data discontinuity is expected when switchcc is performed. The controller card switchover is likely to produce a traffic break due to reprogramming of the trunks. During switchcc, the routing tables and translation tables on trunks are cleared before they are reprogrammed after a switchover and therefore until they are reprogrammed traffic will not flow. The clearing and reprogramming is necessary to insure consistency between the card configuration and the software database. The expected time before traffic is resumed for all connections is dependent on the number of connections and is in the order of a few seconds/minutes. (CSCdj28246)
The maximum PVCs per logical port supported for Annex A. Annex D, and StrataLMI is 899, 899, and 562 respectively. These limits are applicable to any supported cards, including UFM-C and UFM-U with maximum frame length of 4510. Switch software DOES NOT prevent user from configuring more # of PVCs on a port than above. If more than supported PVCs are configured, the LMI will not work on a port. The full status message resulting out of such a configuration will be discarded and the LMI timeout will occur on a port. This will cause port failure, and potentially lead to the A-BIT failures in different segments of the connection path. (CSCdj33507)
ATM connections from ASI to ALM-A must be added from IGX side as master, and must have VCC header type.
Testdelay and testcon commands are not supported on ALM-A end-points for connections made from UFM-U to ALM-A.
ForeSight/ABR VS/VD are not supported for ALM-A cards.
Asymmetric connections not supported for ALM-A card.
ALM-A VC statistics are not kept, but spotlight statistics are planned for a maintenance release in the near future. Spotlight statistics will display connection statistics on a single connection.
NNI headers are not supported for ALM-A cards.
ILMI and LMI are not supported for ALM-A cards.
SVC signalling and multicast are not supported for ALM-A cards.
Segment OAM cells are not processed for ALM-A cards.
ALM-A cards are not supported on feeder nodes within a tiered network architecture.
For VPC connections on ALM-A cards, the value 3 for VCI is reserved and should not be used. Refer to ALM-A Release Notes for details on ALM-A card/connection configuration.
The maximum value for VPC and VCC is 255 for ALM-A cards.
The percent utilization for ALM-A connections is always 100%.
Frame Relay endpoints must be capable of supporting the ALM-A supported Frame Relay connection type: atfr, aftx, and atft.
The ALM-A drops cells with CLP=1 when the VC queue associated with the connection exceed 80% of the user-specified depth or the system-specified depth. Therefore, if a high level of bursty traffic is expected or if cell discards appear when dsplnerrs command is issued, specify a larger queue size.
The following rare occurrence has been observed: User receives 'connection failed' status when trying to add LDCELP connections after deleting some non-LDCELP connections on a fully utilized UVM. The problem can be cleared by resetting UVM card.
User may receive an error message 'Local device code allocation problem' when adding FR connection on IGX. No DAX connections can be added. This intermittent problem occurred only twice during the integration/system testing cycle. The root cause is still under investigation (CSCdj15929). To clear the problem, re-route any one of the existing non-DAX connections using 'rrtcon' command; or add a single non-DAX connection if no non-DAX connection exists.
Prior to Release 8.1.70, with regards to statistics collection, any time period was allowed to be a peak interval. However, those peaks were not gathered correctly. In this release, the peak intervals are controlled to be only those values for which peaks can be accurately collected The rules for peak intervals are as follows:
There are additional commands to control trunk and line loopbacks in this release:
This release requires SV+ Release 9.0.01 or higher.
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 any AXIS Release 4.0.0x, 3.0.x, and 2.1.x.
A performance enhancement has been made to the Switch Software and BTM and ALM-B firmware to reduce the time to configure connections. This change provides a significant improvement in scenarios where many connections need to be configured, such as rebuild, processor card switchover, y-cable redundancy switchover, trunk failure/recovery, connection rerouting, etc. It is recommended that users take advange of this improvement by upgrading their firmware to a minimum of revision of IDA (BTM) or CBD (ALM-B).
The following is the list of known anomalies in this Switch Software delivery.
| Bug ID | Descriptions |
|---|---|
| CSCdj67238 | Unable to access ATM PortQ info on BXM in SNMP. The SNMP get and set work correctly for ASI cards. |
| CSCdj55127 | Switchcc caused temporary communication breaks on IGX with 5000 connections. Probably a performance issue. User traffic not impacted. |
| CSCdj61528 | FR traffic being discarded due to VC queue limits. Problem not seen after deleting and re-adding connection. |
| CSCdj63048 | Continuous packet CRC errors on BTM trunk after 8.2.56-8.5.01 upgrade. |
| CSCdj56026 | When there are events that cause resetting of an IGX node, some delay in processing the background diagnostic frames may occur. In cases of a heavily loaded IPX or IGX node, a "failure" of the background diagnostic test may be logged. |
| CSCdj56856 | Software errors 1122, 105, and 21 occurred on IGX after running 8.5.00 image. |
| CSCdj48540 | Switch software attempts RTD measurements on IGX. AIT/BTM firmware doesn't treat messages consistently. |
| CSCdj52297 | A- bit not going away after both sides of NNI connections are downed and then upped. |
| CSCdj66314 | During 8.5 loop testing, noticed that the command addloclp slot.port did not work for BXM ports. It worked OK on the ASI port. Issuing the addloclp will receive the error message "Invalid Connection Address". |
| CSCdj56030 | Software error 21 occurred during switchcc. |
| CSCdj58620 | The bus signal count (BusSigCng) accumulates and may cause false bus failures. |
| CSCdj62191 | Traffic on a FRM PVC was observed to loop back while the FRM port was in Port Communication Failure due to an LMI timeout. |
| CSCdj62635 | Software error 1000 occurred on an IGX node when switchcc was executed on a neighbor IGX node. |
| CSCdj68516 | A voice connection that was configured with "cnfpref * " and connected through a BPX node with BNI and BXM trunks failed to reroute after the 'upcd trunk #' command was issued. |
| CSCdj42353 | The command dspprfhist on a BPX node shows incorrect values for SUMM and tick interval. |
| CSCdj50640 | BTM trunks may not pass CGW traffic when configured with Gateway Type of CAM or SAM. |
| CSCdj56666 | Slow frame drops observed on 1 segment FR-FR connections on IGX nodes. |
| CSCdj63247 | The use of tstcon command with the -nolp option can cause problems for voice or data segments in a tiered network. |
| CSCdj64509 | ASI abrfst connections lose continuity after oversubscription. |
| CSCdj64510 | Some abrfst connections that route over virtual trunks don't throttle to reach 100% capacity. |
| CSCdj67042 | Software error 4208 occurred when repeatedly issuing the prtcons command on a connection from a local CDP to FTC Access Device. |
| CSCdj67825 | The UBR connections that were added using SNMP (StrataView or SNMP script) may be incorrectly formed and routed as ABR connections. When these connections are upgraded to the software release 8.5, the dspcon command will show them as ABR connections instead of UBR connections. |
| CSCdj69644 | Traffic discontinuity noticed on ATFR conenctions after a non-graceful upgrade from 8.4 -> 8.5. |
The following conditions have been corrected with the 8.5.03 version of the software release. In addition, all corrections applied to previous releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj67013 | Incorrect VC conditioning occurs on the BPX connection when the connection is made with the other end card type supporting FRM to UFM and is in a 'circuit line alarm' status (circuit line failure). |
| CSCdj62636 | BTM trunk failure and FRM port failure after upgrade from 8.2.56 to 8.5.01. SW not correctly upgrading card attributes which apply to upgraded firmware on BTM. Hence, attributes are incorrectly set in upgraded release and cause cards to be removed and reinserted by the SW. The correlation of this issue to the failures seen is still being investigated. |
| CSCdj62849 | Software 2000000 abort occurs when the 68040 receives the "transfer error ACK" (TEA) signal. The problem is with interrupt latency during a switchover. |
| CSCdj62525 | Software error 332 logged on BPX during trunk failure/recovery testing. Trunk was `downed' and then `upped' when this error was logged. |
| CSCdj63591 | Problem with storing FPAD_ADDR values in user endpoint. |
| CSCdj43128 | Upgrade of memory regions can copy too many regions. Only applies to 8.2.56 -> 8.5 upgrades (BPX). |
| CSCdj64464 | Connections failed to route after rebuild of IGX node -- no CGW Lcns on BTM trunk. This is not an issue for connections that terminate on the node that rebuilt. It was a problem for some BPX connections that routed through the IGX that performed the rebuild. |
| CSCdj60745 | Unable to change muxbus utilization for UFM slots. |
| CSCdj65875 | Unknown OE CLP enable and OE UPC enable bits are not upgraded correctly. |
| CSCdj61151 | Not all the requested TFTP statistics are being enabled. |
| CSCdj40551 | No alarm generated when FRP/AIT cards were removed. |
| CSCdj46114 | It was observed that during a rebuild, Switchcc or upgrade, all the connections on the Max_Slot may either get deleted or left hanging without being recognized. |
| CSCdj59263 | Software error 532 occurs when deleting connections. |
| CSCdj62504 | Software does not support trunk status 133-140 on ALM but does on BTM. |
| CSCdj64824 | Circuit lines or packet lines in the last slot of a 16 or 32 card IPX/IGX are not appearing for the summary screen when dspcderrs or dsplns commands are issued. |
| CSCdj63165 | This bug applies to pass-thru configuration where 3 UVM's are used to support 48 LDCELP connections on two T1 lines. When a fax call is originated on port B of the secondary UVM card, the connection upgrades to p, but does not downgrade after the fax call ends. This would potentially causing some trunk congestion.x56 Message not sent down to Port 2 of UVM card during Pass-through Connection. |
| CSCdj62982 | User can not add a port with port number 250 on an UFM-C T1. |
| CSCdj61181 | Processors with at least 32 Mb have extended regions. These regions are not supported by the scanrgn command. The latter only supports the basic regions - DYNM, STAT, STTC, and POOL. |
| CSCdj43344 | On the BPX, Line alarms and errors set or cleared only for the first 100 lines. I.e., Alarms do not work for lines with a logical line number greater than 100. This is not a problem for trunks, only for lines. Even if the cable is removed from the interface the Port LED stays green and the dsplns command shows the "Current Line Alarm Status" for the line is "Clear - OK", when it should show Loss of Signal. |
| CSCdj62226 | A software error 21 is logged from an LDM card after a NPM switchover. |
| CSCdj61022 | Software error 925 if dnln command is executed when the line status is "Bad Clock Path" in the "Current Line Alarm Status" field of the dsplns command display. |
| CSCdj68870 | Software error 30 occurs when trying to configure a trunk in the preferred route. |
| CSCdj68885 | Software error 4208 occurs when trying to configure a trunk in the preferred route. |
| CSCdj68076 | A frame relay connection using a non-circuit line interface may be erroneously flagged as hardware failure. |
| CSCdj68296 | The interworking BPX connection where the other end is a frame relay card with non-circuit line interface may be erroneously conditioned. |
| CSCdj28429 | BTM/AIT Rx Spacer Queues are not configured properly. |
| CSCdj69569 | The addcon command does not support adding Frame Relay connections with PVC parameters. |
The following conditions have been corrected with the 8.5.02 version of the software release. In addition, all corrections applied to previous releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj66885 | swerr 614 (AUTO_DEL_LCON) FRELAY daxcons upgrading from 8.4.1 to 8.5 |
| CSCdj66856 | invalid a-bit alarm due to bugus bogus reference to ctl_status[]. |
| CSCdj56632 | Y redundant pair of BTM's shows both cards in standby. |
The following conditions have been corrected with the 8.5.01 version of the software release. In addition, all corrections applied to previous releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj23296 | Block 4x4 Frame Relay bundles from being added. |
| CSCdj55201 | UFM-U ports failed after reset of primary card in y redundant setup. |
| CSCdj56632 | Y redundant pair of BTM's shows both cards in standby. |
| CSCdj52048 | The clrallcnf command does not completely clear BRAM configuration. |
The following conditions have been corrected with the 8.4.10 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj34394 | When attempting to re-add the connections deleted by the autodelete command (see CSCdj33379), software error 4205 occurred for every attempt. |
| CSCdj36826 | Incorrect values in the physical card attribute table cause AXIS shelves to become unreachable after loading the software release 8.4.08 image. |
| CSCdj37318 | Resetting the BXM-DS3 Y-redundant card causes communication failure on the DS3 trunk to occur. |
| CSCdj38707 | Executing Node-by-Node upgrade process from software release 8.1.50 to release 8.4.09 resulted in a node unreachability. |
| CSCdj38337 | It was noted that during a Node-by-Node upgrade, CLEAR_MSG messages are queued but not dumped to the network. The would potentially cause nodes to become unreachable when the messages are finally dumped. |
| CSCdj38922 | There was no data continuity after adding a new ASI connection. It was noted that during the card verification process, the ASI back card is being reset, but never cleared. This will result in channel configuration message not being sent to the card. |
| CSCdj39341 | During an upgrade, it was noted that a rebuild problem could likely occur on the node number 64. |
| CSCdj39402 | Abort 1000003 occurred while a batch job reset all cards every 0.5 hour. |
| CSCdj40425 | BXM card with 32K or greater LCNs would use up to 50% of the processor time even if no channels are set. |
| CSCdj40257 | Data discontinuity observed with connections routed over virtual trunks. |
| CSCdj39700 | During a Flash upgrade from software release 8.2.04 to release 8.4.09, software error 21 occurred on two nodes (one IPX, one IGX). A subsequent non-graceful upgrade resulting in data discontinuity. |
| CSCdj35538 | The expected mismatch messages were not displayed when replacing one of the Y-Redundant BXM cards with a card having different PVC counts (i.e., 32K vs. 16K). |
| CSCdj36677 | The tstdelay command reports 'test passed' results even when the link being tested is down. |
| CSCdj36834 | The tstdelay command does not work on VP connections added between two ports of the same ASI card. |
| CSCdj37348 | The reroute state machine is not re-enabled after a Node-by-Node upgrade ends. |
| CSCdj38335 | Invoking the nwupgrade switch command can cause the node to downgrade unexpectedly. |
| CSCdj38228 | The dsplog command displays erroneous alarm status. |
| CSCdj36932 | After the reset of a BXM-622 card, a software error 1000 was logged. This indicates a shortage of memory buffers for inter-process message transmission. This occurs on heavily loaded systems. |
| CSCdj39028 | The following event log strings need to have a corresponding Robust Alarm Trap: |
| 1. BCC n Restarted due to a System Reset | |
| 2. BCC n Restarted due to a Powerfail | |
| 3. CC Redundancy Alarm in slot n | |
| 4. Y Redundancy Alarm in slot n. | |
| CSCdj19597 | Software errors (45, 3016, 364) occurred while executing a batch job, which reset cards at a 10-minute interval. |
| CSCdj39701 | The SNMP routine returns an incorrect index value for Frame Relay ports. |
| CSCdj39969 | Software error 424 occurred after removing an active BCC card during a Node-by-Node upgrade. |
| CSCdj39627 | A Robust Alarm Message needs to be generated for a Communication Break event. |
The following conditions have been corrected with the 8.4.09 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj32934 | Handling of error conditions in Utility Processor is not correct, which could cause a Bus Error. |
| CSCdj33231 | The delcon command does correctly delete the channel information from the other end of the connection. This is for BPX-BPX connections. |
| CSCdj34045 | The execution of an addtrk command caused 1M3 abort (Bus Error) and a software error 1117 (Too many topology messages). |
| CSCdj35421 | Memory is lost if a switched virtual circuit is deleted before the routing of the connection has been completed. |
| CSCdj35151 | Comm failure occurred between AXIS and BPX after switchcc on a BPX node. |
| CSCdj36220 | When attempting to clear a comm failure with a manual switchcc, the comm failure continued to occur on the port. |
| CSCdj36276 | Software error 4206 is reported on the standby BCC of a BPX node after the node has recovered from a power failure. |
| CSCdj36282 | Software error 52 (watchdog timer timeout) occurred on a BPX node after failure recovery from a power failure. |
| CSCdj33379 | Software error 614 occurred on a BPX node after invoking a switchcc command. |
| CSCdj34394 | When attempting to re-add the connections that had already been deleted, software error 4205 occurred for every connection addition attempt. |
| CSCdj36826 | AXIS shelves become unreachable after the lanbtld command was invoked. |
| CSCdj28245 | There was no communication between two BCC3s in Boot. |
| CSCdj32495 | The cnfbpnv and dspbpnv commands did not display backplane novram content correctly. |
| CSCdj32843 | Invoking the cbstats clear command did not clear the value in the DROPPED MSGS category. |
| CSCdj34949 | Invoking the clrlnerrs command caused software error 1000003 and a switchcc. |
| CSCdj34754 | BPX takes too long to revert to the primary clock source. |
| CSCdj33696 | Invoking the nwupgrade end * command caused software error 3333 and 1427 to occur. |
| CSCdj29008 | Software error 2064 occurred when VNS bulk calls are being provisioned. |
| CSCdj34724 | Deroute Delay Maximum needs to be raised to 600 seconds. |
| CSCdj33772 | Software error 4205 occurred when running VNS Bulk Call provisioning. |
| CSCdj35917 | Software error 1417 occurred when deltrk and dntrk commands are issued. |
| CSCdj34821 | A switchcc during firmware download caused the target card to fail. |
| CSCdj36148 | Parity errors are not cleaned up correctly on the BPX node. |
| CSCdj35538 | BXM does not report mismatch message when a new Y-redundant card is inserted which has a different max PVC count configured. |
| CSCdj36677 | The tstdelay command reports erroneous test results. |
| CSCdj36834 | The tstdelay command fails on VP connections added between 2 ports on the same ASI card. |
| CSCdj37649 | Logical Endpoint allocation takes lot of time during rebuilds. |
| CSCdj37348 | Connection rerouting was not re-enabled after a Node-by-Node upgrade ends. |
| CSCdj33667 | The clrlnerrs command does not work when the port number is greater than 2. |
| CSCdj35764 | The dspalms command does not display any alarm status even though the node is in major alarm due to problems after a switchcc. |
| CSCdj31909 | When invoking the clrportstats command, user may not be allowed to specify the "all ports" option via use of ala * . |
| CSCdj36568 | The cnfclnsigparm and cnfclnsigparm commands do not work correctly. |
| CSCdj37070 | When attempting to issue dsputl command before the stats areas have not been created for the IPX/IGX node, an error message 'Line currently being monitored' is displayed even though there is only one user on the system. |
The following conditions have been corrected with the 8.4.08 version of the software release. In addition, all corrections applied to previous 8.4 releases are included in this release.
| Bug ID | Descriptions |
|---|---|
| CSCdj25851 | It was observed that, at the completion of a burnfwrev command on a BXM-155, the active BCC switched to the standby BCC due to watchdog timeout. |
| CSCdj25121 | Software error 52 occurred and followed by a system abort when routing was turned-on after switchcc is completed. |
| CSCdj24913 | tstdelay command may not working properly when BTM trunk is in the path. |
| CSCdj27193 | Virtual trunks stopped working after upgrade from 8.2 to 8.4.0 release. |
| CSCdj27713 | Due to a database mapping problem, the trunks configurations were lost on an IGX node and hence the connections configured on those trunks received failed status. This problem occurred during the upgrade testing (from 8.2.07 to 8.4.0 release) and was after completion of the power failure test. |
| CSCdj28302 | Due to an error in trunk alarm checking, the alarm counters was incremented even though the ILMI task has stopped sending node status message to SAR when a the trunk or port is in a Major Alarm status. This may have caused an AXIS node to become unreachable. |
| CSCdj28234 | BPX nodes could not be recovered after power failure in the lab. |
| CSCdj26349 | After switchcc on a BPX node, the node continued sending out LMI messages for ASI and BXM ports and would not allow users to telnet or vt to the node for 10-11 minutes. This causes ATM ASI/BXM port failure. |
| CSCdj29233 | It was observed that when routing more than 1500 connections through a BNI-OC3 trunk, communication failure on the trunk would occur. |
| CSCdj31042 | After upgrading the node from release 8.1.19 to 8.4.0, a slow memory depletion (leak) was observed. |
| CSCdj33231 | While investigating tstdelay time-out problem on BXM-T3 to ASI-T3 connections, when the connection were attempted to be deleted from the master side, the VPCs were deleted, but not from the other end. There was software error 3017 generated at the slave end on each delcon. |
| CSCdj25962 | After a Node-by-Node upgrade (from 8.1.50 to 8.4.0), it was observed from an BPX node within the same group to be upgraded that two IPX nodes were not shown status as being upgraded even though the upgrade was successfully completed. |
| CSCdj25826 | Time for ILMI port stats was incremented incorrectly, causing the time polling cycle to restart every 48 seconds rather than every 60 seconds. |
| CSCdj22859 | Due to a mapping problem, an inconsistent status would be shown on the Standby card. This problem occurred during an upgrade from 8.1.xto 8.4.x and the NIB standby update message were processed. |
| CSCdj24120 | It was observed that duplicate "file not found" events were logged by the TFTP Client code and would potentially fill up the event log. |
| CSCdj26257 | When configuring a Frame Relay class on an IPX node, the PIR value was displayed as *.* but interpreted as 19.2/19.2. |
| CSCdj17569 | On a BXM-T3 Y-Redundant trunk, the active BXM card was reset while the standby card was in a failed state due to a fatal hardware error. Invoking the dspcds command after the card reset showing BXM backcard in a mismatch state. |
| CSCdj25075 | Software error 1000 occurred on a BPX node when deleting a trunk that: 1). splits the network (i.e. the last trunk to a node, or the only trunk connecting two sub nets); 2). has 2500+ connections routed across it to a single node. |
| CSCdj32686 | The clock source was configured on a virtual trunk port BNI-OC3 on a BPX node. When invoking the dspcurclk command on an remote IPX node, the display showed incorrect trunk port value. |
| CSCdj24948 | Connections were added from FRSM-HSSI to FRP and FRM. FRSM-HSSI is configured in DTE mode and traffic is being pumped at the rate of 20Kbps on those connections. The connections are configured with CIR=MIR=PIR=100kbps. Invoking dspchancnt command on both FRP and FRM showed that all frames are received in excess of CIR. It was noticed that bc (Committed Burst) for IPX was set to 0 when it should be set to 65535. FRP/FRM tagging all frames as received in excess of CIR. |
| CSCdj28594 | When issuing a cnfcon command to change the EPD (FBTC) value from disabled to enabled for BXM card, only the ingress of the ports and trunks was enabled. The egress remains as EPD disabled. |
| CSCdj29291 | Memory leak occurred during execution of the FRP background test. |
| CSCdj24118 | BCC stay at DnLder status after switchcc and can only be recovered by removing and putting back the card to for it become active. |
| CSCdj12410 | Inconsistent connection status between two endpoints occurred when the master node was not informed of an error found at the completion of connection re-route on the endpoint node. |
| CSCdj29001 | Software error 532 occurred when invoking VNS voice SVC calls. |
| CSCdj29677 | Changing the receive rate using the cnftrk command following a addtrk command caused some neighbor nodes to become unreachable. |
| CSCdj07631 | An TFTP error 22 indicating that the peak value was invalid occurred when enabling statistics for a BPX node through the Statistics Manager GUI. |
| CSCdj31320 | Changes to the maximum channel count for a trunk were lost after a switchcc. If the channel count was changed at the remote end of a trunk, the local end would not update its standby CC correctly. A subsequent switchcc at the local end would wipe out the new configuration. |
| CSCdj27042 | Due to the changes made to the ADTF value range, a preferred route could not be configured for the connections that has ADTF value equal to 10. |
| CSCdj33370 | Software error 2117 occurred on a BPX node when burning FW is interrupted by a "getfwrev 0.0" command. |
| CSCdj31439 | When attempting to add an AXIS to a BPX node, communication breakdown message occurred. The AXIS shelf can not be added. |
| CSCdj30470 | Software error 2065 occurred on a BPX node approximately 20 minutes after a switchcc. Further investigation indicated that the root cause of this problem was an invalid boundary check on the active, which created a flawed update message for the standby. |
| CSCdj25547 | Background test failure was reported on an ASI Y-Redundant card when congestion on the port occurred and software error 105 were logged. |
| CSCdj26583 | PVCs were in an in-and-out of Alarm state when deltrk was issued or a trunk is in a fail state. |
| CSCdj29493 | Software error 4209 occurred on BPX nodes while the BCC was in standby status. |
| CSCdj31105 | Even though the dnln command was issued for ASI-155E card the front LED stayed on active. It appeared as though the card was active when it wasn't. |
| CSCdj32843 | When trying to clear cbstats using cbstats clear command, the DROPPED MSGS category were never cleared. |
| CSCdj31091 | When a clrlnerrs command was issued, it caused 1000003 abort and a switchcc. |
| Bug ID | Descriptions |
|---|---|
| CSCst96798 | Switch software sets shelfCnfgRebuildStatus object as REBUILD when switchcc occurs. DNS software interprets this as the node went down and deletes all SVCs associated with that node. This will cause calls to be dropped. |
| Bug ID | Descriptions |
|---|---|
| CSCdj24114 | A 1000003 abort occurred when attempting to add more than 12,000 connections. |
| CSCdj26862 | A software error 4209 occurred while adding connections due to the local resources unavailability. |
| CSCdj28579 | Remove debugging code that logged software error 7777. |
| CSCdj27744 | BXM feeder trunks weren't being programmed during the card configuration process. |
| Bug ID | Descriptions |
|---|---|
| CSCdj19652 | The dspclksrcs command shows invalid clock source information, The primary, secondary, and tertiary sources are incorrect. |
| CSCdj03075 | A virtual path connection could not be added because the support for BNI-E3 cards is missing. |
| CSCdj21794 | A software error 614 (LCON automatically deleted) due to the logical endpoint VC index did not agree at each end. |
| CSCdj22424 | Routing virtual trunk traffic through a BXM via trunk does not work. |
| CSCdj23350 | IPX feeder nodes cannot use the trunk as a timing source. The "pass sync" option is not allowed on feeder trunks. Packet lines which pass sync are not allowed to be clock sources. |
| CSCdj27532 | When nwip_on is asserted in the ~svplus/config.sv file, the savecnf operation does not work from an IPX feeder. |
| CSCdj23570 | Multiple problems after performing a switchcc on a BPX with many connections: the problems are all caused by comm failures due to inefficient programming of the BXM cards. |
| CSCdj27129 | A 100003 abort occurred when handling an error condition returned by the SAR which indicated that an invalid command was received. |
| CSCdj27059 | Software error 514 occurred on a heavily loaded BPX node. |
| CSCdj19165 | There is a 10-15 second delay in traffic continuity after a port Y-redundant switchover. |
| CSCdj19637 | Incorrect trunk number is shown as the clock source when using the dspcurclk command. |
| CSCdj19512 | The dspports command only displays the first 96 ports of a BPX node. |
| CSCdj20069 | Standby Y-redundant cards can still drive the clock bus. |
| CSCdj15103 | Software error 4208 (Bad connection address type) occurred on a BPX node. |
| CSCdj21070 | Invoking dspcons with a starting channel number as the only argument fails to display the appropriate connections. |
| CSCdj20682 | A BPX event log indicates that there are BFrame parity errors and Rx Invalid Port errors, but the StrataView Plus HPOV event log does not indicate any of these. |
| CSCdj22346 | After a graceful upgrade from 8.1.50, trunk number 32 is missing. |
| CSCdj21369 | The cnfswfunc feature 6 on a BPX, ABR standard with VSVD, becomes disabled when any IPX or IGX routing node rebuilds. |
| CSCdj23566 | Using dspport or dspports with only a slot number as the argument incorrectly displays Speed as "UNKNOWN" and Interface as "EMPTY". |
| CSCdj26131 | The cnfclksrc command allows a trunk to be a primary clock source while it is passing sync. |
| CSCdj25301 | On the BXM, Early Packet Discard (EPD) and/or Frame Discard is not enabled. |
| CSCdj26827 | On an ASI-T3 card, the 1000th connection on the card is not programmed correctly. |
| CSCdj27511 | Software error 618 occurred on a heavily loaded BPX node. |
| Bug ID | Descriptions |
|---|---|
| CSCdj15795 | Software error 1406 (indicating a bad checksum on a network topology update message) floods the error log. |
| CSCdj16467 | For BXM-DS3 terminated connections, Virtual Path Connections do not operate when the other end terminates on an AXIS shelf in NNI mode. |
| CSCdj16162 | After a Y-Redundant switchover between a pair of BXM cards, it has been observed that a software error 105 (CBUS buffers full) was logged. This is due to multiple connections being re-configured within one CBUS message, which results in a much longer than expected execution time. This will be addressed in the next release where appropriate message throttling will be inserted. At this time, BXM port and trunk cards should not be configured in Y-redundant pairs. |
| CSCdj14719 | The BPX is constantly re-routing connections due to the failure of topology updating, which caused an incorrect view of the topology to exist. |
| CSCdj18088 | There is network topology corruption caused by a node, whose number is set to 64, when that node rebuilds. |
| CSCdj19179 | After a Node-by-Node upgrade, there are cases where the battery backed up RAM is not being rewritten properly. |
| CSCdj15047 | The dspnwip command repeatedly displays the same node's information, rather than all the nodes. |
| CSCdj09736 | There is an intermittent condition where a self-test timeout occurs on the BCC-32. This is not a true indication of a problem with the BCC. |
| CSCdj12314 | When rerouting connections that terminate on AXIS shelves due to the establishment of a preferred route, failure status is reported because an A-bit alarm is being sent by the BPX. |
| CSCdj15594 | Multiple software errors 21 were logged on a BPX. |
| CSCdj15999 | The addcon command cannot be used in jobs on the BPX. An infinite loop results. |
| CSCdj15226 | After a node rebuilds, messages indicating that the time of day is changing is flooding the event log. |
| CSCdj11989 | After a switchcc command is issued, the event log is formatted after the switch, and thus the switchcc even will not be reported to StrataView Plus. |
| CSCdj17569 | A BXM-DS3 trunk card in y-redundant configuration indicated a backcard mismatch after being reset. At the time, the standby card was in failed state. |
| CSCdj18216 | Invoking the dsptrkstats commands on virtual trunks shows incorrect BFrame cell count values. |
| CSCdj09369 | On the cnftrk command, for BNI-OC3 trunks the Payload Scramble option cannot be set to "No" because it results in an Out Of Frame alarm. The software must prevent the user from making this setting. |
| CSCdj19165 | There is a 15 second delay/interruption of traffic on BXM port cards after a Y-redundant switchover occurs. |
| CSCdj19637 | An incorrect trunk number is displayed as the clock source when running the dspcurclk command. |
| CSCdj19512 | The dspports command displays only the first 96 ports of a node. |
| CSCdj13934 | The dspports command works on IPX nodes but not on BPX nodes. |
| CSCdj10363 | The Deroute Delay Timer value used always varies 2 seconds from the configured value. |
| Bug ID | Descriptions |
|---|---|
| CSCdj17869 | During an upgrade from 8.1.5, multiple node unreachabilities were encountered, along with software errors 254 and 526. |
| CSCdj15833 | |
| CSCdj16479 | A feeder shelf cannot be deleted. When the delshelf command is issued, the message "Resources Low---Interface Shelf not changed."is returned. |
| CSCdj16874 | During an upgrade from 8.1.5 to 8.4.0, the standby BCCs on all the BPX nodes keep toggling between the upgrading and upgraded/(clear) state. |
| PCB Description | Rev. | Latest F/W | Minimum F/W |
|---|---|---|---|
| IMATM F/W | C | 4.0.05 | 4.0.04 |
| IMATM Boot | N/A | 4.0.00 | 4.0.00 |
| ASC F/W | M | 4.0.05 | 4.0.04 |
| ASC Boot | N/A | 4.0.03 | 4.0.03 |
| BNM-E3 | B | N/A | N/A |
| FRSM-4T1 | C | 4.0.05 | 4.0.04 |
| FRSM-4T1 Boot | N/A | 4.0.00 | 4.0.00 |
| SRM T1E1 (B) | B | N/A | N/A |
| CESM-4T1/E1 | C | 4.0.05 | 4.0.04 |
| CESM Boot | N/A | 4.0.00 | 4.0.00 |
| AUSM-4T1E1 | B | 4.0.05 | 4.0.04 |
| AUSM Boot | N/A | 4.0.00 | 4.0.00 |
| FRSM-8T1 | A | 4.0.05 | 4.0.04 |
| FRSM-8T1 Boot | N/A | 4.0.00 | 4.0.00 |
| FRSM-HS1 | A | 4.0.05 | 4.0.04 |
| FRSM-HS1 Boot | N/A | 4.0.00 | 4.0.00 |
| AUSM-8T1/E1 | A | 4.0.05 | 4.0.04 |
| AUSM-8T1/E1 Boot | N/A | 4.0.00 | 4.0.00 |
| PCB Description | Rev. | Latest F/W | Minimum F/W |
|---|---|---|---|
| BCC (model B) boot | K | HBJ | HBH |
| BCC3-32 (model C) boot | K | HCM | HCH |
| BCC3-64 (model D) boot | K | HDM | HDJ |
| BCC4 (model E) boot | K | HEM | HEM |
| PCB Description | Rev. | Latest F/W | Minimum F/W |
|---|---|---|---|
| ASI 155 | EOL | WHB | WHB |
| ASI 155 E | E | WEB | WEB |
| ASI-1 2T3/C | D | UCC | UCA |
| ASI-1 2T3/B | D | UBJ | UBH |
| BNI 3T3/C | F | TCL | TCK |
| BNI 3E3/B | F | TCL | TCK |
| BNI 155 E | E | VDN | VDN |
| BNI I55 | EOL | VBN | VBN |
| ASM | B | GAC | GAC |
| BXM 4P | A | MBT | MBM |
| BXM 8P | A | MBT | MBM |
| PCB Description | Latest F/W | Minimum F/W | Comments |
|---|---|---|---|
| NPC Boot | BAF | BAF | |
| NPC 32 Boot | BBF | BBF | |
| NPC64 Boot | BCF | BCF | |
| NPM Boot | RAN | RAN | |
| NPM 32 Boot | RBN | RBN | |
| NPM 64 Boot | RCN | RCN | |
| NPM 32B Boot | REN | REN | |
| NPM 64B Boot | RFN | RFN |
| PCB Description | Latest F/W | Minimum F/W | Comments |
|---|---|---|---|
| ALM-A | CAB | CAA | |
| ALM-B | CBD | CBB | |
| BTM Model A | IAF | IAE | |
| BTM Model B | IBK | IBF | |
| BTM Model D | IDA | IDA | |
| CVM Model A | DAF | DAF | |
| CVM Model B | DBC | DBC | |
| CVM Model C | DCA | DCA | |
| FRM Model D | FDX | FDX | Avoid Rev. FDU & FDV |
| FRM Model E | FEX | FEX | Avoid Rev. FEU & FEV |
| FRM Model H | FHB | FHB | |
| FRM-2 | FFD | FFD | |
| FTM Model B | JBF | JBB | |
| FTM Model C | JCA | JCA | |
| HDM | SCF | SCF | |
| LDM | LC3 | LC3 | |
| NTM | NEJ | NED | |
| NTM (B) | NFF | NFD | Recommend using NFF |
| AIT Model A | IAF | IAE | |
| AIT Model B | IBL | IBK | |
| CDP Model A | DAF | DAF | |
| CDP Model B | DBC | DBC | |
| FRP(M) Model D | FDX | FDX | Avoid Rev FDU & FDV |
| FRP(M) Model E | FEX | FEX | Avoid Rev FEU & FEV |
| FRP(M) Model H | FHB | FHB | FRM(B) |
| FTC Model B | JBF | JBB | |
| FTC Model C | JCA | JCA | |
| NTC | NEJ | NED | |
| SDP | SCF | SCF | |
| UFM-C | ZAE | ZAB | |
| UFM-U | YAA | YAA | |
| UVM | DAA | DAA | |
| UVM-B | DBA | DBA |
| Release ID | Product | Rev. | Model | Image |
|---|---|---|---|---|
| SwSw 8.5.03 | Sys S/W IPX | 8.5.03 | ||
| Sys S/W IGX | 8.5.03 | |||
| Sys S/W BPX | 8.5.03 | |||
| BCC (Model B) Boot | J0 | B | HBJ | |
| BCC3-32 (Model C) Boot | M0 | C | HCM | |
| BCC3-64 (Model C) Boot | M0 | D | HDM | |
| BCC4 (Model E) Boot | M0 | E | HEM | |
| NPC Boot | F0 | A | BAF | |
| NPC 32 Boot | F0 | B | BBF | |
| NPC 32 Boot | F0 | C | BCF | |
| NPM Boot | N0 | A | RAN | |
| NPM 32 Boot | N0 | B | RBN | |
| NPM 64 Boot | N0 | C | RCN | |
| NPM 32 B Boot | N0 | D | RDN | |
| NPM 64 B Boot | N0 | F | RFN |
| Release ID | Product | Rev. | Model | Image |
|---|---|---|---|---|
| SV 9.0.01 | StrataView Plus | 9.0.01 | ||
| StrataView Plus SCM | 9.0.01 | |||
| SNMP | 9.0.01 |
| Release ID | Product | Rev | Model | Image |
|---|---|---|---|---|
| AXIS 4.0.05 | IMATM F/W | A0 | 4.0.05 | 4.0.05 |
| IMATM Boot | N/A | 4.0.00 | 4.0.00 | |
| ASC F/W | A0 | 4.0.05 | 4.0.05 | |
| ASC Boot | A0 | 4.0.03 | 4.0.03 | |
| BNM-E3 | N/A | N/A | N/A | |
| FRSM-4T1 | A0 | 4.0.05 | 4.0.05 | |
| FRSM-4T1 Boot | N/A | 4.0.00 | 4.0.00 | |
| FRSM-8T1 | A0 | 4.0.05 | 4.0.05 | |
| FRSM-8T1 Boot | N/A | 4.0.00 | 4.0.00 | |
| FRSM-HS1 | A0 | 4.0.05 | 4.0.05 | |
| FRSM-HS1 Boot | N/A | 4.0.00 | 4.0.00 | |
| SRM T1/E1 (B) | N/A | N/A | N/A | |
| CESM-4 T1/E1 | A0 | 4.0.05 | 4.0.05 | |
| CESM Boot | N/A | 4.0.00 | 4.0.00 | |
| AUSM-4 T1/E1 | A0 | 4.0.05 | 4.0.05 | |
| AUSM-4 T1/E1 Boot | N/A | 4.0.00 | 4.0.00 | |
| AUSM-8 T1/E1 | A0 | 4.0.05 | 4.0.05 | |
| AUSM-8 T1/E1 Boot | N/A | 4.0.00 | 4.0.00 | |
| BPX 8.5.03 | ASI 155 | B0 | B | WEB |
| ASI 155E | B0 | D | WHB | |
| ASI-1 2T3/E3 | A0 | C | UCC | |
| ASI-2 T3/E3 | J0 | B | UBJ | |
| BNI 3T3/E3 | K0 | C | TCL | |
| BNI 155E | N0 | D | VDN | |
| BNI I55 0C3 | N0 | B | VBN | |
| ASM | A0 | A | GAC | |
| IGX 8.5.03 | BTM Model A | K0 | A | IAF |
| BTM Model B | K0 | B | IBL | |
| BTM Model D | D | IDA | ||
| CVM | F0 | A | DAF | |
| CVM Model B | C0 | B | DBC | |
| CVM Model C | A0 | C | DCA | |
| FRM (Model D) | V0 | D | FDX | |
| FRM (Model E) | V0 | E | FEX | |
| FRM (Model H) | V0 | H | FHB | |
| HDM | D0 | C | SCD | |
| ALM-A | B0 | A | CAB | |
| ALM-B | D0 | B | CBC | |
| UFM-C | E0 | A | ZAE | |
| UFM-U | A0 | A | YAA | |
| UVM | A0 | A | DAA | |
| UVM-B | A0 | B | DBA | |
| FTM | A0 | C | JCA | |
| LDM | P2 | C | LC3 | |
| NTM | J0 | E | NEJ | |
| NTM (B) | F0 | F | NFF | |
| IPX 8.5.03 | AIT Model A | F0 | A | IAF |
| AIT Model B | K0 | B | IBL | |
| CDP | F0 | A | DAF | |
| LDP | P2 | C | LC3 | |
| FRP Model D | V0 | D | FDX | |
| FRP Model E | V0 | E | FEX | |
| FTC Model C | 20 | C | JC20 | |
| NTC | J0 | E | NEJ | |
| SDP | D0 | C | SCD |
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.
CCO is Cisco Systems' primary, real-time support channel. SMARTnet customers and partners can self-register on CCO to obtain additional content 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, 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 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.
Please use CCO to obtain general information about Cisco Systems, Cisco products, or upgrades. If CCO is not accessible, contact 800 553-6387, 408 526-7208, or cs-rep@cisco.com.
|
|