Last Modified: Apr 28, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
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, 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, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3
Fixed In:
13.0.1, 12.1.3, 11.6.3.2
Opened: Feb 17, 2017 Severity: 3-Major Related Article:
K54432535
When FQDN Ephemeral Nodes are being used at the same time as static Node objects, and there is change in those objects, either via DNS resolver changes or manual changes to static nodes, there exists a chance where one may be misidentified as the other during an update, causing a crash in bigd.
The bigd process restarts and produces a core file, causing interruption of pool member monitors.
This issue occurs when all of the following conditions are met: -- The BIG-IP configuration contains a mix of FQDN pool members or nodes, and static node objects. -- You perform one of the following actions: + Modify current node settings + Create or delete nodes
Avoid use of FQDN Nodes and Pool Members; use only static-IP Nodes/Members instead.
Fixed case where misidentification may occur, resulting in bigd running without crashing.