I am running topology on my wide IPs for two data centers, which splits the US down the Mississippi. From my corporation network, we have two NS that are geographically seperated, one in Colorado and one in Pennsylvania these are doing round robin to the computers. We need to be able to reach this WIP via our Corp network, and stay in one location and not bounce between the two data centers. I have tried taking Pennsylvania and putting it into the Western region under topology, but that hasn't changed it. I took the IP address to the corporate NS server and put it in the Western region and it still didn't work. Is there a way to run Topology, but have one part of do what I need done here? I would have thought that you could do this by adding the state into the region.

When is the last time your IP geolocation database was updated?

It was updated this past week to the newest database.

If you create specific regions for your corporate name servers based on IP address and build topology records for those, does that make a difference? Or have you done this?

I had not tried it in that direction. I have placed this in now, and will give it some time to stablize before testing.

After giving this configuration plenty of time, it is still not working, users are still getting bounced between the data centers.

GTM Topology | DevCentral

22 Replies

Chris_123510
Nimbostratus
Apr 04, 2014
I turned off longest match yesterday afternoon, and it looks like it has actually gotten worse with the bouncing. Below is the new config that I placed in yesterday afternoon.

gtm region Corp_DNS { region-members { subnet 192.168.106.0/24 { } subnet 192.168.35.0/24 { } } } gtm region East { region-members { subnet 10.42.0.0/16 { } } } gtm region EAST_Region { region-members { continent AF { } continent EU { } continent OC { } country CA { } country LC { } country MX { } state "US/Armed Forces Americas" { } state "US/District of Columbia" { } state "US/New Hampshire" { } state "US/New Jersey" { } state "US/New York" { } state "US/North Carolina" { } state "US/Puerto Rico" { } state "US/Rhode Island" { } state "US/South Carolina" { } state "US/Virgin Islands" { } state "US/West Virginia" { } state US/Alabama { } state US/Connecticut { } state US/Delaware { } state US/Florida { } state US/Georgia { } state US/Indiana { } state US/Kentucky { } state US/Maine { } state US/Maryland { } state US/Massachusetts { } state US/Michigan { } state US/Ohio { } state US/Pennsylvania { } state US/Tennessee { } state US/Vermont { } state US/Virginia { } } } gtm region EXTERNAL { region-members { not subnet 10.0.0.0/8 { } } } gtm region West { region-members { subnet 10.43.0.0/16 { } } } gtm region West_Region { region-members { not region /Common/DCA_Region { } } } gtm region INTERNAL { region-members { subnet 10.0.0.0/8 { } } }

gtm topology ldns: region /Common/Corp_DNS server: region /Common/West_Region { order 1 score 5 } gtm topology ldns: region /Common/West_Region server: datacenter /Common/FTW { order 2 } gtm topology ldns: region /Common/East_Region server: datacenter /Common/DCA { order 3 } gtm topology ldns: region /Common/West server: subnet 10.3.0.0/16 { order 4 } gtm topology ldns: region /Common/East server: subnet 10.2.0.0/16 { order 5 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.new.com_external { order 6 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.old.com_external { order 7 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.been.com_external { order 8 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.been.com_internal { order 9 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.old.com_internal { order 10 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.new.com_internal { order 11 }
Cory_50405
Noctilucent
Apr 04, 2014
Your region "West_Region" references a region that I don't see in the list (DCA_Region). Does this region exist? Or should West_Region look like this:

gtm region West_Region { region-members { not region /Common/EAST_Region { } } }
Chris_123510
Nimbostratus
Apr 04, 2014
You are correct, it does look that way.
Chris_123510
Nimbostratus
Apr 04, 2014
To make sure we are straight here it is again.

gtm region Corp_DNS { region-members { subnet 192.168.106.0/24 { } subnet 192.168.35.0/24 { } } } gtm region East { region-members { subnet 10.42.0.0/16 { } } } gtm region EAST_Region { region-members { continent AF { } continent EU { } continent OC { } country CA { } country LC { } country MX { } state "US/Armed Forces Americas" { } state "US/District of Columbia" { } state "US/New Hampshire" { } state "US/New Jersey" { } state "US/New York" { } state "US/North Carolina" { } state "US/Puerto Rico" { } state "US/Rhode Island" { } state "US/South Carolina" { } state "US/Virgin Islands" { } state "US/West Virginia" { } state US/Alabama { } state US/Connecticut { } state US/Delaware { } state US/Florida { } state US/Georgia { } state US/Indiana { } state US/Kentucky { } state US/Maine { } state US/Maryland { } state US/Massachusetts { } state US/Michigan { } state US/Ohio { } state US/Pennsylvania { } state US/Tennessee { } state US/Vermont { } state US/Virginia { } } } gtm region EXTERNAL { region-members { not subnet 10.0.0.0/8 { } } } gtm region West { region-members { subnet 10.43.0.0/16 { } } } gtm region West_Region { region-members { not region /Common/East_Region { } } } gtm region INTERNAL { region-members { subnet 10.0.0.0/8 { } } }

gtm topology ldns: region /Common/Corp_DNS server: region /Common/West_Region { order 1 score 5 } gtm topology ldns: region /Common/West_Region server: datacenter /Common/West { order 2 } gtm topology ldns: region /Common/East_Region server: datacenter /Common/East { order 3 } gtm topology ldns: region /Common/West server: subnet 10.43.0.0/16 { order 4 } gtm topology ldns: region /Common/East server: subnet 10.42.0.0/16 { order 5 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.new.com_external { order 6 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.old.com_external { order 7 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.been.com_external { order 8 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.been.com_internal { order 9 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.old.com_internal { order 10 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.new.com_internal { order 11 }
Cory_50405
Noctilucent
Apr 04, 2014
Are you copying and pasting these directly from the configuration? I still see one discrepancy:

gtm region West_Region { region-members { not region /Common/East_Region { } } }

This region references "East_Region", but it looks to be defined in the configurations you posted as "EAST_Region"
Chris_123510
Nimbostratus
Apr 04, 2014
Sorry Cory, that was my mistake during the sanitization process. What is listed as EAST_Region, should be East_Region.
Cory_50405
Noctilucent
Apr 04, 2014
Just wanted to make sure. So if this solution is still not working, I would recommend simplifying it as much as possible.

Currently, your Corp_DNS region references West_Region, which in turn references the West datacenter. Can you change your Corp_DNS region to instead reference the West datacenter, or better yet a pool in the West datacenter?
Chris_123510
Nimbostratus
Apr 04, 2014
Ok, so this is the current config simplified to point to the West data center, and I am still getting IP addresses to the east. Plus, when going to the website, it is in the East as well.

gtm region Corp_DNS { region-members { subnet 192.168.106.0/24 { } subnet 192.168.35.0/24 { } } } gtm region East { region-members { subnet 10.42.0.0/16 { } } } gtm region East_Region { region-members { continent AF { } continent EU { } continent OC { } country CA { } country LC { } country MX { } state "US/Armed Forces Americas" { } state "US/District of Columbia" { } state "US/New Hampshire" { } state "US/New Jersey" { } state "US/New York" { } state "US/North Carolina" { } state "US/Puerto Rico" { } state "US/Rhode Island" { } state "US/South Carolina" { } state "US/Virgin Islands" { } state "US/West Virginia" { } state US/Alabama { } state US/Connecticut { } state US/Delaware { } state US/Florida { } state US/Georgia { } state US/Indiana { } state US/Kentucky { } state US/Maine { } state US/Maryland { } state US/Massachusetts { } state US/Michigan { } state US/Ohio { } state US/Pennsylvania { } state US/Tennessee { } state US/Vermont { } state US/Virginia { } } } gtm region EXTERNAL { region-members { not subnet 10.0.0.0/8 { } } } gtm region West { region-members { subnet 10.43.0.0/16 { } } } gtm region West_Region { region-members { not region /Common/East_Region { } } } gtm region INTERNAL { region-members { subnet 10.0.0.0/8 { } } }

gtm topology ldns: region /Common/Corp_DNS server: datacenter /Common/West { order 1 } gtm topology ldns: region /Common/West_Region server: datacenter /Common/West { order 2 } gtm topology ldns: region /Common/East_Region server: datacenter /Common/East { order 3 } gtm topology ldns: region /Common/East server: subnet 10.42.0.0/16 { order 4 } gtm topology ldns: region /Common/West server: subnet 10.43.0.0/16 { order 5 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.been.com_external { order 6 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.new.com_external { order 7 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.old.com_external { order 8 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.been.com_internal { order 9 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.new.com_internal { order 10 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.old.com_internal { order 11 }
Cory_50405
Noctilucent
Apr 04, 2014
Do you have scores applied to your records? Not sure if you were just omitting those or they aren't set. If not set, score your Corp_DNS record higher than the rest. You might want to assign scores to each one appropriately so they are preferred as you intend.
Chris_123510
Nimbostratus
Apr 04, 2014
Yes there is a weight on the Corp_DNS, it is set to 5, the rest are set to 1, as I was doing Topology, I didn't want one more heavily weighted then the other.

When I set up the Corp_DNS to reference the West data center, I forgot to change the weight, I have done that now, and will give it a bit of time for testing.

Forum Discussion

GTM Topology

22 Replies

Recent Discussions

GTM Packet Capture command

Wildcard SSL Certificate Deployment on F5 LTM

Migration from i series 10200 with 1 child VCMP to r series 10900 series

Open Redirection Mitigation

How to Implement 2 Way SSL in F5 LTM

Related Content

DNS Topology Load balancing

GTM synchronization group

Migrate part of GTM to another GTM

F5 GTM resolution issue

DNS lite with topology selection