10-22-2010 02:40 AM
There are two services to be load balanced:
High availability at site level is also required for both services. We are opting for two models as mentioned below:
- Anycast using RHI for DNS
- GSLB for SMTP
Anycast using RHI for DNS
DNS service is hosted at four Data Centers and SI is also present at all locations. I am clear about its working and concepts but need some clarification for the following:
- DSR topology is best for Anycast?
- What should be the IP used for management of real servers? I read somewhere that the IP address of physical interface should be the management IP and the service IP should be configured as loopback on real server.
- DSR dictates that the SI and real servers should be on the same L2 domain. Suppose 18.104.22.168/32 is the Service VIP and needs to be advertised from two locations. Servers will have 22.214.171.124/32 configured as loopback address. But the physical interface IP should be unique so as to ensure real server reachability to the internet. Can we make the real servers and SI part of 126.96.36.199/24 IP subnet serving the VIP of 188.8.131.52/32?
GSLB for SMTP
SMTP service is hosted at two Data Centers. We will use GSLB for load balancing between the sites. The model is clear to me but I have two questions:
1- Site ServerIron and Controller should be two separate boxes? Is it possible to configure one of the site load balancers as GSLB controller?
2- Does enabling GSLB (either controller or site LB) adds some restrictions on ServerIron? We will be using the same boxes as part of Anycast DNS plan. I need to be sure that enabling GSLB will not restrict any feature on ServerIron.
10-22-2010 02:53 PM
Direct Server Return (DSR) enables the return traffic to not be processed by the ServerIron ADX. Instead, the real server directly sends the return traffic to the client. In this case, the ServerIron ADX changes the way it sends health checks to the application so that the health checks do not rely
on the return traffic.
SwitchBack configurations enhance server response time and increase capacity on the ServerIron ADX, by allowing server responses to bypass the ServerIron ADX on the way to clients and at the same time increasing the number of simultaneous connections the ServerIron ADX can support.
Its main (but not only) reason is to still increase server responce AND reduce resources used in the SI.
You cannot have a router hop between the ServerIron ADXs. They must have Layer 2 connectivity. So you are correct in that they must connected in the same layer 2 domain.
As for IP address you will need something like 184.108.40.206/30 assigned so the SI can have 1 address and the Real the other (and yes add the SI ip address as a lookback for the real server).
I hope that helps.
10-24-2010 10:36 PM
It means that we can have SI Service IP 220.127.116.11/30 and the real servers and SI interface is part of 18.104.22.168/24. Servers will have loopback of 22.214.171.124/30. 126.96.36.199/24 address will be used by real servers for management and interaction with internet???
10-25-2010 01:21 AM
Yes that is correct .
VIP has public IP address (and that is the address you add as a loopback on the server.
SI interface and real have a address in the same subnet range.
see pic above