thx for the info.

1. Do you have any descriptions for the other codes ?

2. if ok means there is no error, why is the service down in my special case ?

blncss01-100# show service canyon-b_kso

Name: canyon-b_kso Index: 26

Type: Local State: Down

Rule ( 172.21.167.162 ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String: (null)

Keepalive: (HTTP-80:HEAD:/kso-web/AliveCheckServlet.do?op=css 60 2 90 )

Keepalive Error: OK

Keepalive Encryption: Disabled

Last Clearing of Stats Counters: 08/30/2007 09:25:00

Mtu: 1500 State Transitions: 1

Total Local Connections: 182194 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 182194 Max Connections: 65534

Total Reused Conns: 0

Weight: 1 Load: 255

Weight Reporting: None

3. if the service is alive and the keepalives are fine, normally there is no "keepalive error" field in "show service"

blncss01-100# show service baden-b_lso

Name: baden-b_lso Index: 6

Type: Local State: Alive

Rule ( 172.21.91.28 ANY ANY )

Session Redundancy: Disabled

Redirect Domain:

Redirect String: (null)

Keepalive: (HTTP-80:HEAD:/svi/AliveCheckServlet.do?op=css 60 2 90 )

Keepalive Encryption: Disabled

Last Clearing of Stats Counters: 09/19/2007 08:59:46

Mtu: 1500 State Transitions: 44

Total Local Connections: 5714 Total Backup Connections: 0

Current Local Connections: 0 Current Backup Connections: 0

Total Connections: 5714 Max Connections: 65534

Total Reused Conns: 60

Weight: 1 Load: 2

Weight Reporting: None

String: baden

looks a little bit strange.

we are running SW 07.50.1.03

sounds like you have hit the following ddts.

CSCei81533 - Class A keepalives get stuck into a DOWN state

Gilles.

doesn?t sounds good, but is an explanation

Hi,

The sh keepalive command provides a complete summary of all keepalives on the CSS. If you see State: Alive, you know that that service has been configured, and the CSS can see the device. This command also provides information on what type of keepalive it is and the specifics on what will make the service fail. The services starting with AUTO_ are default services generated by the CSS when you add a service; this includes the default gateway. If a service is shown as State: Down, you need to check your connection from the CSS to your real server (by default it takes three failures of a particular keepalive to mark a service as down). State:Dying means the CSS has not yet had contact with the real server.

If it doesn't work then please post the output from the following commands by replacing the uri and ip of your host and send it to me ....

CSS# llama

CSS(debug)# icp probe service server1 "http://www.server1.bg"

CSS(debug)# icp probe host 172.17.249.22 "http://www.server1.bg"

Or CSS(debug)# icp probe host 172.17.249.22

Kind regards

Sachin garg