Bug ID 693388: Log additional HSB registers when device becomes unresponsive

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP TMOS(all modules)

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5

Fixed In:
14.0.0, 13.1.3, 12.1.4.1

Opened: Nov 08, 2017
Severity: 3-Major

Symptoms

HSB becomes unresponsive, and logs no registers to indicate the state of the device. There is no logging of additional registers to assist in diagnosing the failure.

Impact

Limited visibility into the HSB state when it becomes unresponsive.

Conditions

It is unknown under what conditions the HSB becomes unresponsive.

Workaround

None.

Fix Information

There is now logging of additional registers to assist in diagnosing the failure. The registers can be seen in the TMM log files when there is either an HSB transmitter or receive failure.

Behavior Change