Bug ID 1273141: GTM pool members are not probed and multiple GTMs are reporting inconsistent status

Last Modified: Apr 24, 2024

Affected Product(s):
BIG-IP DNS, GTM(all modules)

Known Affected Versions:
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

Fixed In:
17.1.1

Opened: Mar 17, 2023

Severity: 3-Major

Symptoms

GTM pool members are not probed and multiple GTMs in the same GTM syncgroup report inconsistent status.

Impact

GTM pool members are marked incorrect status and inconsistent across GTMs.

Conditions

1. Create a GTM pool with a pool member disabled. 2. Create another GTM pool with same monitor and pool member as in the previous GTM pool.

Workaround

Use the following command: # tmsh modify gtm global-settings general monitor-disabled-objects yes or Use a unique monitor names for pools that has disabled pool members.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips