Forum Discussion
NimbostratusGSLB design for few small number of source addresses
We are trying to design a load balancing solution that will take high volumes of traffic from a client with few IP addresses (even just 1) and evenly distribute between our datacenters. Even on a transaction by transaction basis going round robin.
Using a DNS based solution we run into the following - Clients may not respect TTL value that have been assigned and will swing traffic unevenly. Causing large spikes and not spreading the traffic evenly.
We are thinking to somehow route/proxy the traffic through another endpoint in or out of our network. Any suggestions? Thank you.
1 Reply
IheartF5_45022Nacreous
URL is mysite.com.au - WideIP has 2 pool members - s1 and s2, round robin, no persistence, TTL as low as you can go (60s).
Also have wideIPs for s1.mysite.com.au, 2 pool members, Global Availability (prefer s1).
Also have wideIPs for s2.mysite.com.au, 2 pool members, Global Availability (prefer s2).
On LTM in site1, if traffic arrives for Host: mysite.com.au, HTTP redirect to http://s1.mysite.com.au/.
On LTM in site2, if traffic arrives for Host: mysite.com.au, HTTP redirect to http://s2.mysite.com.au/.
I hope that makes sense.
