Forum Discussion
Brian_Saunders1
Altostratus
AltostratusGTM 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 wa...
Jason_40733
Cirrocumulus
CirrocumulusKeep in mind. The source IP is not going to necessarily be the source IP of a client, but the source-IP of the DNS resolver being used by the client. If your 10.67.36.12 is querying a DNS resolver to get the record, it will be the IP of the DNS resolver that will be used for load balancing.
Anyways, to your issue. It "may" be because your load balancing is defined as "pools" but your topology is defined as "Data Centers". I'd try adjusting the topology records to be the more granular 'Pool is blah-blah' instead of 'Data Center is ho-ho' and see if that works.
Brian_Saunders1Altostratus
AltostratusI pulled a packet capture while performing the DNS query. The DNS query went to the same DNS resolver each time but the DNS resolver didn't always respond with the same result. I'll try modifying the topology records to reflect the pool instead of data center. Is it possible to add this without impacting the existing topology setup? Do I just need to create two more data centers and change my servers to those so they won't fall into the existing topology rules?