Bug ID 1497709: GSLB Sync Group does not reconnect at certificate rotation or reboot

Last Modified: Feb 11, 2025

Affected Product(s):
BIG_IP_NEXT(VE/HW) GTM(all modules)

Known Affected Versions:
20.1.0, 20.1.1

Opened: Jan 30, 2024

Severity: 1-Blocking

Symptoms

GSLB Engine loses connection to another GSLB Engine Peers in a GSLB Sync Group and fails to reconnect.

Impact

The affected connection appears in a "half-open" state where one peer considers the connection open, another peer considers the connection closed and disconnects it every 10 seconds. As a result, GSLB Engines in a GSLB Sync Group have states of connections completely unsynced which results in the inability to distribute monitoring resources between each other and share statuses of resources.

Conditions

When a GSLB Engine gets a certificate rotation, reboots, or experiences a temporary network issue that causes disconnection to another GSLB Engine Peers in a GSLB Sync Group, that connection can be not restored.

Workaround

Once any GSLB Engine in a GSLB Sync Group gets certificate rotation or reboots, all GSLB Engines in the GSLB Sync Group need to have re-created configuration for all non-local GSLB Engine Instances.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips