Forum Discussion
GTMs, Route Domains, and Sync Groups
Well, I'm just thinking about all my options at this point and this idea is a bit more on the radical side. Basically here's the scenario. We have two DCs and 3 different LDNS sources querying WideIPs.
- LDNS_Source_A -> should always resolve Server_A regardless of state
- LDNS_Source_B -> should always resolve Server_B regardless of state
- LDNS_Source_C -> should always resolve Server_A until we make Data Center A inactive and activate Data Center B without impacting LDNS_Source_A or LDNS_Source_B queries
The idea would be to have partition 1 on each GTM handle requests from LDNS_Source_A and LDNS_Source_B, always returning the server that resides in the same data center as the source regardless of state. Partition 2 would handle requests from LDNS_Source_C based off the state of the Data Denter on the GTM (or whatever other topology methodology we develop later down the line).
The same idea can be accomplished with just strictly topology and I have it mocked up in my lab and it works. But I don't like the idea of having a lot of topology records and also having to query for the specific pools and then enable / disable depending on the state of the data centers in the event of a DR.
Brian
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com