For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Jeff_Ferrell_11's avatar
Jeff_Ferrell_11
Icon for Nimbostratus rankNimbostratus
Jul 01, 2014

GTM Topology records across datacenters

Hello,

 

We are struggling with splitting in some fashion user requests across two active datacenters.

 

I am currently using topology records by state, but that is not working since most all of the customers in our area are using Comcast, and they all use 75.75.75.75 or 75.75.76.76.

 

It is often that we see a client connect and get DC1, tehn as soon as they login, get bounced to DC2, assuming they requested an additional DNS lookup for the domain name and this time Comcast used a different DNS server to service it.

 

Discussing with my ecommerce manager, we wondered about using either IP Subnet topology records to get most of one area to a specific datacenter, and the rest to another. That is tedious but does not have to be exact in its boundaries.

 

Then I noticed the ISP records in the GTM. I see Comcast in there, no Verizon, Time Warner etc. Since the Geo Location DB is updated monthly, I assume the Comcast CIDR's are in there and that is what it is using to determine the client.

 

I'm rambling on I think, have all the thoughts in my head, so surely missed writing some.

 

Bottom line, how do you all split traffic to different datacenters when the web servers are session based?

 

tia

 

availability
BIG-IP DNS
design
management

1 Reply

  • The_Bhattman's avatar
    The_Bhattman
    Icon for Nimbostratus rankNimbostratus
    Jul 04, 2014

    Hi Jeff, How is your LDNS set up? Are you ONLY looking at state or do you use a tier'd approach where you are looking at state then CIDR with a weighted format? Are you using any persistence so that the clients stick to a specific domain when it's choosen? All this has a play in how you split the traffic.

     

    -=Bhattman=-