I configured my companies 2 CSS's as load balancers for a bunch of web servers and they work great except for a minor issue that I cant seem to resolve. When a web daemon on a server crashes, or is shutdown for one reason or another, the CSS removes that service from the pool, which is good, but that server looses connection to the outside world. We can still SSH into the server and push data onto it, but the route to the outside world is dead.
This is a problem since our servers often need to connect to outside resources on startup.
We are currently set up with a 2-Tier network layout where the CSS is connected to our public network (say 18.104.22.168/24) and our servers sit on a private network(192.168.0.0/24) and use the CSS as their gateway.
I tried a number of fixes to rectify the situation, but nothing has worked so far. The servers have another NIC connected directly to the public network, but since the default GW is the CSS, it does not help. I tried changing the default GW on the servers to point to our public GW, but then access through the CSS VIP does not work. Static routes don't do the trick either.
Is there any configuration option that I can change so that the CSS does not kill the GW for a server whose service is down?
Either that, or do you know of a better way to lay out the configuration so we avoid the problem?
If needed I can post the configuration of our CSS and the network setup on our servers.
Any help is greatly appreciated.