Bug ID 579760: HSL::send may fail to resume after log server pool member goes down/up

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IP TMOS(all modules)

Known Affected Versions:
12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 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,, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1

Fixed In:

Opened: Mar 11, 2016

Severity: 3-Major

Related Article: K55703840


High speed logging (HSL): asymmetric bandwidth loss might result in no bandwidth tracking.


For a period of time after the logging node comes back up, HSL::send events will not be sent to the log server. Sometimes it never recovers and tmm needs to be restarted.


This will occur if the log server pool only has a single member in it, and that member goes down and up while HSL::send is occurring during traffic processing.


If possible, configure log server pools with multiple members to avoid this condition.

Fix Information


Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips