Bug ID 1053605: When you use NAT, the iQuery status displays 'BIGIP' instead of 'BIGIP-DNS'.

Last Modified: Sep 24, 2024

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

Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5

Opened: Oct 08, 2021

Severity: 5-Cosmetic

Symptoms

Use the 'show gtm iquery' command. The 'Server Type' for the connection to its own box may show as "BIGIP" rather than "BIGIP-DNS", even though DNS is provisioned on that device. # tmsh show gtm iquery ---------------------------------------- Gtm::IQuery: 10.0.0.1 ---------------------------------------- Server GTM1 Server Type BIG-IP <-- ... ... ... Note: Other BIG-IP DNS devices in the same sync group will correctly show the status as 'BIGIP-DNS'.

Impact

This is purely cosmetic, and does not affect the operation of the iQuery protocol.

Conditions

This occurs in the following conditions: - The gtm server has both an address and a translation defined. - The BIG-IP running the command is the same device being viewed (that is, it is showing its own status). For example: gtm server GTM1 { devices { GTM1 { address { 10.0.0.1 { translation 192.168.1.1 } } } } ... }

Workaround

N/A

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips