Last Modified: Sep 14, 2023
Affected Product(s):
BIG-IP DNS, GTM
Known Affected Versions:
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, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6
Fixed In:
15.0.0
Opened: Jan 09, 2018 Severity: 3-Major
Two GTM devices that have the same local IP address are not able to establish an iQuery connection, even when a translated address is configured.
When one or more GTM devices attempt to establish an iQuery connection to another device, it actually establishes a connection with itself instead of the other device.
This condition may occur if two GTM servers have the same self IP address on separate networks that are attempting to use address translation to establish a connection.
To resolve the issue, 1. Configure the devices to have different self IP addresses. 2. Change the addresses and translated addresses of the corresponding GTM servers to match the new configuration using the following example command: tmsh modify gtm server <server_name> addresses ...
You can now mitigate this issue by setting a variable to the name of the configured device that matches the local machine using a command similar to the following example: tmsh modify sys db gtm.selfdevicename value <device_name> If those values match and the two GTM servers are configured with different data centers, then a proper connection between devices can be established using address translation.