Bug ID 756177: GTM marks pool members down across datacenters

Last Modified: Feb 26, 2019

Bug Tracker

Affected Product:  See more info
BIG-IP GTM(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, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.1.0, 14.1.0.1, 14.1.0.2

Opened: Jan 22, 2019
Severity: 3-Major

Symptoms

GTM pool members are marked down even though the monitored resource is available. GTM debug logs indicate that each GTM is relying on the other GTM to conduct probing: debug gtmd[13166]: 011ae039:7: Check probing of IP:Port in DC /Common/dc1 debug gtmd[13166]: 011ae03a:7: Will not probe in DC /Common/dc1 because will be done by other GTM (/Common/gtm2) --- debug gtmd[7991]: 011ae039:7: Check probing of IP:Port in DC /Common/dc2 debug gtmd[7991]: 011ae03a:7: Will not probe in DC /Common/dc2 because will be done by other GTM (/Common/gtm1)

Impact

Pool members are marked down.

Conditions

-- GTM configured in different data centers. -- GTM pool configured with a single monitor, and the monitor uses an alias address that can be pinged from both datacenters. -- GTM pool members configured from different data centers.

Workaround

Instead of a single monitor, use a monitor created specifically for each Datacenter.

Fix Information

None

Behavior Change