Last Modified: Oct 16, 2023
Affected Product(s):
BIG-IP GTM
Known Affected Versions:
11.5.1, 11.5.2, 11.5.3, 11.5.4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 11.6.0, 11.6.1, 11.6.2, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 HF1, 12.1.0 HF1, 12.0.0 HF2, 12.1.0 HF2, 12.0.0 HF3, 12.0.0 HF4, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2, 12.1.0, 12.1.1, 12.1.2, 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, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6
Opened: Mar 02, 2016 Severity: 3-Major Related Article:
K51305649
GTM/BIG-IP DNS cannot discover LTM virtual servers created on different VLANs, using identical IP:port combinations.
Only one of the virtual servers will be autodiscovered and added to the GTM/BIG-IP DNS config. Which one depends on the order in which they are processed by the GTM/BIG-IP DNS system.
On an LTM system, two virtual servers are created: /Common/vsname1 1.2.3.4:80 /Common/vsname2 1.2.3.4:80 on different VLANs. Auto discovery is enabled on the GTM system.
When this occurs, there will be only one virtual server on the GTM/BIG-IP DNS server config with the specified IP/Port (1.2.3.4:80). There are 2 possible workarounds: 1. Remove this virtual server from the GTM/BIG-IP DNS server config. At the next autoconfig interval, both virtual servers will be added to the GTM/BIG-IP DNS Server config. 2. This has two parts. Assuming that 'vsname1' has been added to the GTM/BIG-IP DNS config during autodiscovery. A. Modify the vsname1 on the GTM/BIG-IP DNS system and set the LTM NAME property to match the name of the virtual server on the LTM system (vsname1). B. Manually add vsname2 to the GTM/BIG-IP DNS config, setting the LTM NAME to match the name of the virtual server on the LTM system (vsname2).
None