Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

Keeping Keepalives from Killing Server

I've encounterd a problem on one of our application servers where the server process would lock up and refuse anymore http sessions. We have a setup where load-balancing occurs between two servers. We create two content rules per server, one for http (80), and one for ssh (22) so that we can access the servers through the CSS. We were originally using http keepalives, but this had the effect of shutting down all content rules when the http service was stopped, making the server inaccessible until the keepalive was changed to icmp or an active service port.

I have two questions. The first one is, can I make it so that if a http keepalive fails, we can still access the server via its other content rule through ssh, even while the CSS takes it out of the load-balancing loop (since it is technically "down").

My second question is this. When a server locks up, port 80 is actually still open, though not responding. If we are using http keepalives, how does it react to this? Will it consider the server still up, or will it try to look for some kind of response from the server via port 80, and mark it as down if it doesn't get it?


New Member

Re: Keeping Keepalives from Killing Server

1- create a different service for the ssh rule (same server IP, different port).

2- the http keepalive uses "HEAD" by default, which requires the server to respond with a "200-OK" message. So when your server locks up, even if still listenning to port 80, it needs to respond with http code 200 or else the CSS will mark it as "down".

New Member

Re: Keeping Keepalives from Killing Server

Thanks for the info!

CreatePlease to create content