Bug ID 651476: bigd may core on non-primary bigd when FQDN in use

Last Modified: Nov 07, 2022

Affected Product(s):
BIG-IP LTM(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, 13.0.0

Fixed In:
13.0.0 HF1, 12.1.2 HF1

Opened: Mar 15, 2017

Severity: 2-Critical


When using FQDN node/pool member resolution, a non-primary bigd process may core under certain circumstances. A non-primary bigd is any process instance other than zero in a multi-bigd scenario, or any bigd process on a non-primary blade in a chassis.


bigd may core and be restarted in a loop, causing some monitor instances to not be serviced. This may cause node/pool member flapping, or may cause certain nodes or pool members to be effectively not monitored.


FQDN is in use.


Use static IPs instead of FQDN for node/pool member address assignment.

Fix Information

Known causes of the bug have been fixed.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips