06-23-2008 11:46 PM
10.176.56.113 and 10.176.56.114 are 2 x DNS servers in Site 1.
We are planning to put in 10.188.56.49 and 10.188.56.50 which are Site 2 DNS servers as standby realserver because there was a time when 2 of the Site 1 DNS servers went dead and there was no DNS server running in Site 1.
We do not want the DNS vip to route to Site 2 DNS unless both of the .113 and .114 are dead. Can you advice if 'inservice standby' can be used?
serverfarm DNS
nat server
nat client DNS
real 10.176.56.113
inservice
real 10.176.56.114
inservice
real 10.188.56.49
inservice standby
real 10.188.56.50
inservice standby
probe DNS
In Cisco documentation: http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/csm/4.1.x/4.1.2/configuration/guide/rsfarms.html#wp1038112
"If a client making a request is stuck to an out-of-service server (using a cookie, SSL ID, source IP, etc), this connection is balanced to an in-service server in the farm. If you want to be stuck to an out-of-service server, enter the inservice standby command. When you enter the inservice standby command, no connections are sent to the standby real server with the exception of those connections that are stuck to that server and those servers with existing connections. After the specified standby time, you can use the no inservice command to allow only existing sessions to be sent to that real server. Sticky connections are then sent to an in-service real server in the server farm. "
The explanation above is rather vague and confusing. Hence I would like to seek your advice whether the usage of 'inservice standby' can serve the purpose that we required, which is to failover to .49 and .50 when .113 and .114 became "out of service" in the CSM.
06-24-2008 01:38 AM
"no inservice" and "inservice standby" are used to gracefully shutdown the real servers. "Inservice standby" is used for shutting down (taking out of LB logic) a real server when stickiness is configured.
You can use Backup server farm for your requirement. A sample config
vserver DNS
virtual z.z.z.z tcp
serverfarm SITE1 backup SITE2
inservice
!
serverfarm SITE1
nat server
real x.x.x.1
inservice
real x.x.x.2
inservice
!
serverfarm SITE2
nat server
real y.y.y.1
inservice
real y.y.y.2
inservice
If all the servers in SITE1 goes down then the real of SITE2 will be used. If a single server of SITE1 comes back then all connections will go to that server in SITE1.
Hope it helps
Syed Iftekhar Ahmed
06-24-2008 04:48 PM
Thank you very much Syed. I will try this. So all we have to ensure is that the IP addresses of the real servers in SITE2 are routable from the CSM - right
06-24-2008 05:00 PM
Yes. CSM needs to probe these reals.
Syed
06-24-2008 05:10 PM
Thanks Syed.
06-24-2008 05:17 PM
You also need to make sure that the return traffic should pass through the CSM to the client.
Syed
06-24-2008 05:22 PM
Thanks Syed
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide