Bug ID 854177: ASM latency caused by frequent pool IP updates that are unrelated to ASM functionality

Last Modified: Sep 13, 2023

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

Known Affected Versions:
12.1.0, 12.1.1, 12.1.2, 12.1.3,,,,,,,, 12.1.4,, 12.1.5, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0,,,,,,,,, 13.1.1,,,,, 13.1.3,,,, 14.0.0,,,,,, 14.0.1,, 14.1.0,,,,,, 14.1.2,,,,, 15.0.0, 15.0.1,,,,, 15.1.0,,,,

Fixed In:

Opened: Nov 29, 2019

Severity: 3-Major


Whenever a pool IP address is modified, an update is sent to bd regardless of whether that pool is relevant to ASM. When these updates occur frequently, as can be the case for FQDN nodes that honor DNS TTL, latency can be introduced in ASM handling.


Latency is introduced to ASM handling.


Pool nodes have frequent IP address updates, typically due to an FQDN node set to honor DNS TTL.


Set the fast changing nodes to static updates every hour.

Fix Information

ASM now correctly ignores pool member updates that do not affect remote logging.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips