December 16, 2002
HDM connections report failed after upgrading to 9.2.42. However, the connections still pass data.
The root cause of this anomaly is the reading of an incorrect bit from the connection database. The particular incorrect bit being read is the second least significant bit from the local EIA update rate. Based on this bug, 9.2.42 will be deferred and removed from the Cisco.com Software Center.
An HDM or LDM connection will report as failed. Issuing the command dcct slot.port will show a similar display to the one below. The display is the last page of the dcct command.
node VT StrataCom IGX 8430 9.2.42 Oct. 18 2002 16:44 PDT
VC #: 0 &Vc_Db: 3194340A Slot: 22 Chan: 0
dsp, oe : 0, 1
AddrType : CHN,CHN
TCON : 0
Reconfigure the EIA update rate at both connection endpoints, using the cnfcheia command. The EIA rate must be chosen such that its binary representation does not have the second least significant bit set to 1. For example, the default rate value of 2 results in the connection failure for the conditions described above, while a rate value of 4 avoids the failure condition. The range of EIA update rate values is 0 to 20. The following rate values should not be used:
2 (default), 3, 6, 7, 10, 11, 14, 15, 18, 19
If upgrading to a release that has this defect, change the EIA rate prior to the upgrade. If the problem occurs while already running a release with the defect, do the following:
Configure the EIA update rate appropriately at both ends of the connection.
Manually send mandatory updates from one end of the connection toward the end that is in the failed state. The updates are sent using the command updates 1.
This anomaly may be avoided by upgrading to a release of 9.2 which has this fix. Monitor the ddts bug using the link provided below to view which release of 9.2 bears this fix.
To follow the bug ID link below and see detailed bug information, you must be a registered user and you must be logged in.
HDM connections report failed after upgrading to 9.2.42.
For More Information
If you require further assistance, or if you have any further questions regarding this field notice, please contact the Cisco Systems Technical Assistance Center (TAC) by one of the following methods: