JAKNimbostratus Mar 25, 2016Thanks for replying raduioncu
Scenario, entire Data Center goes down, when clients begin to come back online, they need to reach out to their DNS servers, DC, etc....but the local DNS servers are not avaialbe. So the idea was to provide a single Global IP for all clients to reach and be able to send the request to an available DNS server in a remote Data Center.
This works fine using LTM, if the LTM is online at the local Data Center, but the scenario states the local LTM is down as well. The idea would be to have that IP globally held on the local GTM so it would know which LTM was available with online DNS servers. We could have the local GTM in an active/active pairing with a remote GTM, in case the local GTM is down as well.
As I type this, it's starting to dawn on me why this might not be possible...so if we had a local GTM in active/active state with a remote GTM, they cannot share the same listener...
Primary goal...configure all client with DNS (and eventually other required services such as NTP, syslog etc.) to use the SAME primary and secondary IP...regardless of site. Trying to avoid major routing manipulation by involving the GTM, however, we may only be able to do this with tunnels via WAN and interface based routing locally.
-Jeff