I have an issue on GTM just updated to 11.4.1.HFX5, the issue is when disabling a wide IP via the properties page it disables all wide IPs and marks them black. also, when adding a comment in the description window it populates that field for all wide IPs, looks like an issue with that page of the configuration utility. Any ideas? work around is to disable the wide IP via the main page, just check it an click disable. I installed 11.5.1 & 11.6.0 and still the same issue. F5 says it is a bug no fix yet! any one has the same issue?

Hi Ahmad, If F5 has confirmed this as bug what else to confirm now... :) let them get back with the HF for this Regards,

Seeing it on 11.5.1 HF5 but not on 11.5.1 HF7. I am about to upgrade my HF5->HF7 to see if it persists. In reference to the first statement about disabling a WideIP, is your GTM still providing an answer to the requests when the WideIP is disabled? I am seeing this behavior on my 2 environments. Will be calling F5 on Monday.

Issue has been fixed on 11.4.1 HF6, I installed the HF6 and it is fixed.

How about the issue where the wideIP is returning records when it is disabled? This is not fixed on 11.5.1HF7. Thanks.

Hi Erich, Could it be that the A records are still left in Zonerunner (if you are using it), and the GTM is simply round-robining them out?

Disabling Wide IP issue

10 Replies

Techgeeeg
Nimbostratus
Nov 09, 2014
Hi Ahmad,

If F5 has confirmed this as bug what else to confirm now... :) let them get back with the HF for this

Regards,
Erich_Rockman_1
Cirrus
Jan 17, 2015
Seeing it on 11.5.1 HF5 but not on 11.5.1 HF7. I am about to upgrade my HF5->HF7 to see if it persists. In reference to the first statement about disabling a WideIP, is your GTM still providing an answer to the requests when the WideIP is disabled? I am seeing this behavior on my 2 environments. Will be calling F5 on Monday.
AbuAhmad
Nimbostratus
Jan 20, 2015
Issue has been fixed on 11.4.1 HF6, I installed the HF6 and it is fixed.
Erich_Rockman_1
Cirrus
Jan 20, 2015
How about the issue where the wideIP is returning records when it is disabled? This is not fixed on 11.5.1HF7. Thanks.
OTS02
Cirrus
Jan 20, 2015
Hi Erich,

Could it be that the A records are still left in Zonerunner (if you are using it), and the GTM is simply round-robining them out?
Erich_Rockman_1
Cirrus
Jan 21, 2015
There are A records in zonerunner. How do you not use zonerunner when using GTM and WideIPs? It creates the zones and resource records for you when you create the WideIP. Thanks.
OTS02
Cirrus
Jan 21, 2015
I don't know how to not use Zonerunner. I have seen blogs where folks were using Bind instead of Zonerunner. But anyway, if there is A records with the same name as the WIP, and there is no Last Resort Pool on the WIP, and the pool Load Balancing Method is set to Return to DNS (default), then the GTM will resolve according to what is in Zonerunner.
Erich_Rockman_1
Cirrus
Jan 30, 2015
I was hoping to put the GTM in front of a pool of DNS servers so that the DNS can answer any query for which there is not a WideIP. The concept works great except when you want to disable a WideIP. You need to change the dns profile setting "Unhandled Query Action" from Allow to Reject or Drop. Then it stops answering for the disabled WideIP, but unhandled queries do not make it to the back end DNS pool.

Guess I can't have both.
Erich_Rockman_1
Cirrus
Apr 28, 2015
Yeah. This was 2 (really 3) separate issues. Should have started a new thread.

HF7 fixed the issue w/ the disabling of the WideIPs in regard to all of them getting disabled.

As far as the other issue, I have it configured slightly different. I configured my GTM with a pool of DNS servers. See this: https://support.f5.com/kb/en-us/products/big-ip_gtm/manuals/product/gtm-implementations-11-5-0/8.htmlconceptid

The problem is that, you need to configure the "Unhandled Query Options" to Allow in order for GTM to pass the query to the pool of DNS servers. However, when you disable a WideIP, all the A records are returned for that WideIP. You cannot have both.
David__Pasch
Altostratus
Sep 15, 2015
FYI: Still be broken in 11.6.0 HF3. F5 Support stated 11.6 HF4 it is fixed.

D