Last Modified: Jan 09, 2025
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4
Fixed In:
17.1.2
Opened: Nov 30, 2023 Severity: 3-Major
In a few instances, the status of LTM nodes and/or pool members monitored by the bigd daemon may not be correctly or completely communicated to the mcpd daemon. The mcpd daemon then communicates with the rest of the BIG-IP about the status of monitored objects. Currently, there is no clear mechanism for detecting when bigd and mcpd are out of sync for the observed status of LTM nodes and/or pool members monitored by LTM health monitors.
Without a clear indication that bigd and mcpd are out of sync for the observed status of monitored LTM nodes and/or pool members, it is not known when corrective action needs to be taken to re-synchronize the LTM node and/or pool member status between bigd and mcpd.
This issue may occur when LTM nodes and/or pool members are monitored by LTM health monitors.
When it is thought that bigd and mcpd are not in sync with the status of monitored LTM nodes and/or pool members, the following actions can be taken to force a re-synchronization of the monitored object status. This causes mcpd to monitor the state of the monitored objects correctly. -- Restart the bigd using the command: "bigstart restart bigd" -- Remove the health monitor from the affected pool, pool member or node, then re-add the health monitor to the affected pool, pool member or node.
The tmstat table for bigd, monitor_instance, now includes action and status which reflects the last action taken on the node and the status.