Forum Discussion

Chris_123510's avatar
Chris_123510
Icon for Nimbostratus rankNimbostratus
Apr 02, 2014

GTM Topology

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.

 

availability
BIG-IP DNS
design

22 Replies

Sort By
  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 02, 2014

    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?

     

  • Chris_123510's avatar
    Chris_123510
    Icon for Nimbostratus rankNimbostratus
    Apr 02, 2014

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

     

  • Chris_123510's avatar
    Chris_123510
    Icon for Nimbostratus rankNimbostratus
    Apr 03, 2014

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

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 03, 2014

    Could you post your topology region and record configurations? Sanitized of course.

     

  • Chris_123510's avatar
    Chris_123510
    Icon for Nimbostratus rankNimbostratus
    Apr 03, 2014

    gtm region Corp_DNS { region-members { subnet 192.168.1.0/24 { } subnet 192.168.2.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/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 { } state US/Pennsylvania { } } } gtm region INTERNAL { region-members { subnet 10.0.0.0/8 { } } }

     

    gtm topology ldns: region /Common/East server: subnet 10.42.0.0/16 { order 2 } gtm topology ldns: region /Common/West server: subnet 10.43.0.0/16 { order 3 } gtm topology ldns: region /Common/West_Region server: datacenter /Common/West { order 4 } gtm topology ldns: region /Common/East_Region server: datacenter /Common/East { order 5 } gtm topology ldns: region /Common/EXTERNAL server: pool /Common/www.new.com_external { order 6 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.old.com_internal { 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/EXTERNAL server: pool /Common/www.old.com_external { order 10 } gtm topology ldns: region /Common/INTERNAL server: pool /Common/www.new.com_internal { order 11 } gtm topology ldns: region /Common/Corp_DNS server: region /Common/West_Region { order 12 score 5 }

     

  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    Apr 03, 2014

    If you move your Corp_DNS topology record up to the top of the list, does that make a difference? Right now it's last in the order.

     

    Are you using longest match for topology order? If so and not running v11.5, this may be of concern:

     

    http://support.f5.com/kb/en-us/solutions/public/14000/700/sol14794.html

     

  • Chris_123510's avatar
    Chris_123510
    Icon for Nimbostratus rankNimbostratus
    Apr 03, 2014

    Currently I am on 11.4.0 HF ENG 4, and we are using longest match on the records. If I change from longest match, other then placing Corp_DNS at the top, do I need to be concerned about the order of the other records?

     

    • Cory_50405's avatar
      Cory_50405
      Icon for Noctilucent rankNoctilucent
      Apr 03, 2014
      Yes. If some of them could overlap, you want to put the more specific ones at the top of the list. The more general/catch-all ones should go at the bottom to ensure they match as you intend.
  • Chris_123510's avatar
    Chris_123510
    Icon for Nimbostratus rankNimbostratus
    Apr 03, 2014

    Ok, I have set this with Corp DNS at the top now and still customers are seeing the same reaction from the sites. Should I give this more time to settle down?

     

    • Cory_50405's avatar
      Cory_50405
      Icon for Noctilucent rankNoctilucent
      Apr 03, 2014
      Depending on caching or persistence, it may take time.