DNS Wide-IP "Priority" Pools or members?
I'd like to have a Wide-IP that always resolves to a particular LTM service, but in the event that service goes down, have it fail over to a Disaster Recovery Site. No load balancing back and forth, a straight "if A is up, Give answer=a, if A is down, give answer=B". In the LTM world I would look to a priority group setup to accomplish this. For Wide-IP, I can use a Last Resort Pool, but is there another way to fail over to a DR site that should be considered?
GTM WIDE IP IRULE
Hello ALL , I working on one project where I need to failover between Wide IP's across two geographical location . One Wide IP ( XYZ-APAC.production.com) sits in Australia which polls TWO DC's DC1 and Dc2 . The Other Wide IP ( ABC-AMER.production.com)sits in AMERICA which Also Polls two Dc's DC1 and DC2 . The requirement is to failover to the AMERICA Wide IP if all pools in AUSTRALIA goes DOWN ( or DC's goes DOWN ) and VICE- VERSA . I never developed an irule for DNS . reading through the documents , I found below irule BUT no sure if this will work with my requirement . when DNS_REQUEST { # Changed = = 0 to < 1 for CR100063 / SOL10137 if { [active_members pool_test] > 0 } { cname "XYZ-APAC.production.com" } else { cname "ABC-AMER.production.com" } } Can I please request to get some guidance on this ? Thanks
GTM Sync or Device Management Sync?
I have an old pair of devices on HA in version 11.6.4, they don't have GTM module, but Link Controller instead. There's an issue that sometimes, suddenly, Wide IPs configuration is changed without any human intervention, and I think that is probably due that I have Device Management Sync in Manual, and also I have Link Controller Configuration Synchronization activated. So, my theory is that maybe I only need to have Device Management Sync configured, and Link Controller Configuration Synchronization needs to be disabled in order to prevent issues with automatic GTM (Link Controller) sync. I'm not sure if Device Management Sync syncronize the bigip_gtm.conf file or this only happens with GTM (Link Controller) sync...
GTM Wide IP Topology Based Load Balancing
Hello, I'm interested in creating an active / active GTM record that load balances at the wide IP level based on typologies. We already have a small implementation in place where I work that was setup before my time, but I've been getting inconsistent results. Basically I have a wide IP created with two pools and only one server in each pool. There is a topology record created as follows:  My source IP is 10.67.36.12 so based on the topology record defined above I should always get directed to Virtual-CGS Topology, but when I test it out I'll sometimes go to Virtual-CGS and sometimes Virtual-PD. From reading documentation it reads like this type of topology setup is more for load balancing at the pool level and not wide IP level? Is that the case? Cheers, Brian
WideIP.conf does not reflect configuration changes.
Hello, hope you guys can help me. I have a redundant pair of Link Controllers, we are about to release a new website so im configuring a new virtual server and a new WideIP for link redundancy purposes. i configure the Virtual server, but when i create a new inbound wideip and try to associate the new virtual server with the wideip, the virtual server does not appear in the drop-down list. I've been doing some troubleshooting and found out that my wideip.conf file does not reflect the new virtual server configuration, so i'm guessing that should be the problem. What can i do? a little help would be appreciatedWide IP and SOA query
Hi, That is probably obvious question but I am not sure if I am getting things right. All related to 13.1.0.6 version. Setup: Wide IP: created Automatically ZoneRunner Zone wip.exmaple.com creted with: SOA NS A for DNS profile with: Only GSLB enabled Unhandled Query Actions: Reject When performing A query for answer with correct IP returned. When performing SOA query for wip.exmaple.foo reply with REFUSED status returned. Only way I figured out to make SOA query work is: Unhandled Query Actions: Allow Use BIND Server on BIG-IP: Enabled I wonder if above is really only way to have SOA query working? Are SOA and NS RRs created just because bind zone file db.external.wip.example.foo. format requires it and those RR are not really necessary for any real life scenarios? Sure this is just W2K8 implementation but to create delegation (using wizard) without error for configured NS (for wip.example.foo subdomain) SOA query has to work. That is not big deal because even if there is error in wizard, name resolution is working. Still I am a bit curious if lack of ability to answer SOA query can be important? Piotr
Create a Wide-IP in the "Member list" does not appear any virtual server to associate.
Hello People, I'm a licensed equipment and provisioned with the LC version 11.6HF3 and when i create a Wide-IP in the "Member list" does not appear any virtual server to associate. Recalling that created the Virtual Server to the association, do not know if you have any specific configuration to create the Virtual Server to get to my associate Wide-IP. Would like you guys to help. Thank U.
iRule to resolve DNS for GTM (wide-ip if possible)
Hi I've server on cloud and want to try to use irule to resolve dynamic IP from cloud and return IP to user. I saw irule LTM can use RESOLVE:lookup and we can use it on Listener. But Is it possible to have the same function irule in wide-ip ? because if we attach irule on Listener, it will surely take more performance than wide-ip. Flow is When user send dns request for wide-ip "A" -> F5 resolve dynamic IP from cloud (it's hostname will be like ABCDEFG.cloud-us.com)-> F5 return IP to user. ps. due to some circumstance CNAME is not possible. Thank you
GTM Query - Global Availability clarification.
Hi All, Reading the documentation, I see (what I expect Global Availability to do)... "BIG-IP GTM distributes DNS name resolution requests to the first available virtual server in a pool. BIG-IP GTM starts at the top of a manually configured list of virtual servers and sends requests to the first available virtual server in the list. Only when the virtual server becomes unavailable does BIG-IP GTM send requests to the next virtual server in the list. Over time, the first virtual server in the list receives the most requests and the last virtual server in the list receives the least requests." In the case of a Wide IP it'll select the first available pool. In the case of a pool, it'll select the first available virtual server. As I gather, the first being order number 0 then 1, then 2 and so on. So here's my setup: Wide IP (Method Global Availability) -> Single Pool -> Two virtual servers. Single Pool configured with Pref: Global Availability, Alternate: None, Fallback: Fallback IP: The IP of the first VS in the list. There's no monitoring against the pool, or dependencies. So both virtual servers are green, so is the pool. Looking at the DNS resolutions, it seems quite often the second in the list is being returned. Why is that, when the first isn't down? Thanks, JD