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

MahendraRaj_131's avatar
MahendraRaj_131
Icon for Nimbostratus rankNimbostratus
Sep 11, 2013

Thanks for your quick response Jason...

 

Yes, we have the list of IP Ranges of AKAMAI edge servers. If I do topology based solutiong.. for example...

 

AKAMAI IP Range1:- 10.10.0.0/16 AKAMAI IP Range2:- 10.20.0.0/16

 

Lets take if the above two ranges are from Akamai, based on the topology load balancing, IP Range1 goes to DC1 and IP Range2 goes to DC2 in ideal scenario.... What will happen if the DC1 failed..? Will GTM do redirect the traffic to DC2 for IP Range1 as well?

 

Thanks

 

Jason_40733's avatar
Jason_40733
Icon for Cirrocumulus rankCirrocumulus
Sep 11, 2013
Let's say Range1 goes to Pool1 ( an IP address for DC1 ) and Range2 goes to Pool2 ( an IP address for DC2 ). If you define Pool1 to have the DC1 IP address ( or VIP if using an LTM ) as the primary node and have the DC2 IP address ( or VIP... ) as the next node and set Pool1's load balancing to "Global Availability" you should get what you want. All incoming LDNS requests from Range1 would receive the DC1 IP address. If the DC1 IP address was down, the global availability load balancing would then return the DC2 IP address instead. You'd do the same process for the Pool2, except Pool2 would return the DC2 address and resort to the DC1 address if the DC2 was unavailable. Please note... we use LTMs to provide a VIP ( or IP & port availability ) to provide status to our GTMs. If you're not using an LTM to send the DC1 and DC2 status up to the GTMs, test and re-test your monitoring solution that determines if DC1/DC2 is available. Also note, the TTL on your returned DNS answer can affect failover times on top of your monitoring intervals.