cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
672
Views
0
Helpful
1
Replies

CSS 11150 - "Keepalive type http" doesn't work.

jan.sveide
Level 1
Level 1

I've two webservers, A and B, sharing the same webdata on a NetApp filer. A CSS 11150 (5.033) have a content rule, C, with a VIP registred in internet DNS.

I've added A and B to C. When using default "Keep alive type (ICMP)" on services the site is fully functional. When I disable the site on webserver A, clients attached to this server get errors and are not redirected to the B webserver. This is because the CSS doesn't check the for "Keepalive type http".

The CSS thinks that A is online because it is answering for ping. This solution is not good so I tried to change the "Keepalive type" to http. This is better when something is wrong with one of the load-balanced webservers, but when activating "Keepalive type http" the CSS marks A and B down and site is offline.

Is something wrong with my configuration???

service lbws1.kov

ip address xx.xx.193.25

protocol tcp

port 80

active

service lbws2.kov

ip address xx.xx.193.27

port 80

protocol tcp

active

owner KOV

content D

protocol tcp

add service lbws1.kov

add service lbws2.kov

balance aca

port 80

advanced-balance sticky-srcip-dstport

vip address xx.xx.193.245

active

content C

add service lbws1.kov

add service lbws2.kov

protocol tcp

port 80

balance aca

advanced-balance sticky-srcip-dstport

vip address xx.xx.193.28

active

1 Reply 1

drussell
Level 1
Level 1

By default the CSS will attempt to read http:///index.html

It looks like that may not exist. Try to access the index page yourself from each of the services.

Review Cisco Networking for a $25 gift card