Last Modified: Nov 07, 2022
Affected Product:
See more info
BIG-IP LTM
Known Affected Versions:
11.6.0, 11.6.0 HF1, 11.6.0 HF2, 11.6.0 HF3, 11.6.0 HF4, 11.6.0 HF5, 11.6.0 HF6, 11.6.0 HF7, 11.6.0 HF8, 11.6.1, 11.6.1 HF1, 11.6.1 HF2, 11.6.2, 11.6.2 HF1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 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, 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, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Fixed In:
13.0.0
Opened: Dec 20, 2016
Severity: 2-Critical
'bigd' may restart, or restart continously, when an FQDN-configured pool member is removed due to an IP-node change in the associated DNS server.
The 'bigd' process will restart, and monitoring will continue as expected. It is possible that the 'bigd' process will restart continuously, causing monitoring to not be performed (as 'bigd' continually restarts).
A pool member is configured through FQDN; and that pool member IP node is changed in the associated DNS (causing the old pool member to be removed, and a new pool member with a new IP to be configured in its place).
Configure monitors statically (not using FQDN); or ensure IP addresses provided through DNS for FQDN configured monitors remain unchanged.
'bigd' no longer restarts continuously when an FQDN-configured pool member is removed due to an IP-node change in the associated DNS server.
