Bug ID 1067641: Full sync can incorrectly change the status of a monitored pool member.

Last Modified: Oct 24, 2023

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 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

Opened: Dec 13, 2021

Severity: 4-Minor

Symptoms

In a gateway failsafe high availability (HA) pair, with high availability (HA) unit monitors in different pools changes monitor status from "unchecked" to "up" post a full sync.

Impact

Incorrect status display.

Conditions

-- Gateway failsafe configured on a high availability (HA) pair (where one high availability (HA) unit monitors one particular pool and the other high availability (HA) unit another pool) -- LTM pool member(s) monitor status will be "unchecked" -- Run full sync on peer unit -- LTM pool member(s) monitor status will now become "up".

Workaround

-- Run 'tmsh load sys config' -- Run 'guishell to query MCPD for the pool member status (below example is for a pool named 'pool-gw' which is located on partition /Common/, change the syntax as necessary): # guishell -c "select POOL_NAME,STATUS_STATUSREASON from pool_member where POOL_NAME='/Common/pool-gw'"

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips