Problem with Sorry Server, HELP!!

[saluko]

I'm a newbie to content technology. I've recently implemented a css 11154 into our test environment and done the configs. Everything seems to work fine, however when I took the webserver off line the Sorry server displayed "page cannot be found" instead of displaying what I was wrote on the Sorry server site. I pasted the revelant bit of my config for you all to look at to see if I've missed any thing. Thanks in advance.

service SORRYwebserver

ip address 132.130.203.16

protocol tcp

port 443

keepalive type http

keepalive port 80

active

service TEST1webserver

ip address 132.130.203.13

protocol tcp

port 443

keepalive port 443

keepalive type http

active

service TEST2webserver

ip address 132.130.203.14

protocol tcp

port 443

keepalive port 443

keepalive type http

active

!*************************** OWNER ***************************

owner samson

content rule_external

add service TEST1webserver

add service TEST2webserver

balance leastconn

protocol tcp

vip address 132.130.205.3

primarySorryServer SORRYwebserver

active

content rule_internal

add service TEST1webserver

add service TEST2webserver

balance leastconn

protocol tcp

vip address 132.130.205.4

primarySorryServer SORRYwebserver

active

[pknoops]

Couple of things here.

1. Is there a reason why you have specified 'port 443' in each of the services. This implies that you are natting the backend connection between the css and the webserver to port 443 even if the data coming in is something else, like port 80.

Quite honestly if your users are coming in port 443, then specifiy this in the content rule and remove it from the service.

2. As for why your sorry server does not work. The sorry server shows port 443 in the service, but the keepalive is port 80. If port 80 is working on the webserver and port 443 is not in your senario, the service will remain active even though it is not working for 443.

In other words, it makes no sense to use keepalive port 80 on a service when the way you have it configured only allows connections from the css to be on port 443 because you specified port 443 in the service. You generally want the keepalive to be the same port as the type of traffic you are sending the server so that the css really knows if the server is up.

Hope this all makes sense

Pete Knoops

Cisco Systems