Usefulness of server ip on Big-IP DNS systems
I am trying to understand on a F5 GTM system, what purpose does the server ip fulfill? Say I am setting up a WideIP that's supposed to return the IP of a generic host. How I'd typically go about it is a.) create a "server" object that corresponds to a DataCenter and then b.) configure virtual servers that are part of this server. The Big-IP system requires an IP address for this 'server' object and it doesn't seem to matter what IP you enter - because ultimately - it's the IP of one of the virtual servers that gets returned as the WideIP anyway. I've set up Generic Host servers with made up IPs and it has still worked.GSLB - Monitoring LTM VIP load balancing via iRule
In one of our environments we are configuring a single LTM VIP and load balancing multiple applications via an iRule. We currently have other LTM environments integrated via iQuery with our GTM for GSLB configuration and monitoring. Is there a way to monitor the VIP at the GTM level via iQuery that would give a true back-end pool status? Since, let's say, we are load balancing 100 different applications via a single VIP, if 99 of them went offline, the VIP would still show as ONLINE/GREEN. Or would we even go as far as integrating via iQuery and adding a dependency monitor of the pool itself instead?
DNS LTM adding recommendation
Hello, What is the recommendation in adding GTM and LTM/AWAF devices in multi datacenter More explanation if we have HQ and DR datacenters HQ data center GTM device (One device) LTM/AWAF Device (Pair) DR data center GTM device (One device) LTM/AWAF Device (Pair) shall we add DR LTM/AWAF to HQ GTM by using DR LTM/AWAF self IP reachable through internet or internally? Please highlight pros and cons for each method Why are we think to add DR LTM/AWAF to HQ GTM is to ensure that HQ GTM will see VS on DR LTM/AWAF down when internet link is down in DR If there another way to ensure that by monitoring links please clarify
