10-21-2010 09:20 AM
I am setting up a basic service on my CSS but it is showing as DOWN even though I can reach it fine directly and from the CSS.
I'd appreciate any hints on why. I am running sg0810106 (08.10.1.06) on a CSS 11501. Other services on the same backend subnet are working fine.
Here is the service definition and status:
CSS11501# sh run service vmi-82-100-8000
!************************** SERVICE **************************
service vmi-82-100-8000
ip address 10.10.82.100
protocol tcp
port 8000
keepalive type tcp
keepalive port 8000
active
CSS11501# sh service vmi-82-100-8000
Name: vmi-82-100-8000 Index: 37
Type: Local State: Down
Rule ( 10.10.82.100 TCP 8000 )
Session Redundancy: Disabled
Redirect Domain:
Redirect String:
Keepalive: (TCP-8000 5 3 5 )
Keepalive Encryption: Disabled
Last Clearing of Stats Counters: 10/21/2010 07:24:59
Mtu: 1500 State Transitions: 0
Total Local Connections: 0 Total Backup Connections: 0
Current Local Connections: 0 Current Backup Connections: 0
Total Connections: 0 Max Connections: 65534
Total Reused Conns: 0
Weight: 1 Load: 255
Weight Reporting: None
CSS11501#
Debugging in the CSS seems to indcate the service should be up:
CSS11501(debug)# icp probe service vmi-82-100-8000
Probing 10.10.82.100:8000(-) KeepAlive probe..
IP Address: 10.10.82.100
Port: 8000
URL: /
HTTP Version: 1.1
Server Model: Apache/2.2.9 (Unix) mod_ssl/2.2.9 OpenSSL/0.9.8h
Server Date: Thu, 21 Oct 2010 16:11:37 GMT
HEAD Response: 404 Not Found
HEAD Support: Yes
Persistence: Yes
Keep-Alive: Yes
Request Depth: 100
TBR: 5
Connect Time: 1 ms
Rqst/Rsp Time: 4 ms
Pipeline: No
SSL: No
CSS11501(debug)# icp probe host 10.10.82.100
Probing 10.10.82.100:80(-) KeepAlive probe..
IP Address: 10.10.82.100
Port: 80
URL: /
HTTP Version: 1.1
Server Model: Apache/2.2.3 (Unix) mod_ssl/2.2.3 OpenSSL/0.9.8h
Server Date: Thu, 21 Oct 2010 16:12:34 GMT
HEAD Response: 403 Forbidden
HEAD Support: Yes
Persistence: Yes
Keep-Alive: Yes
Request Depth: 100
TBR: 5
Connect Time: 1 ms
Rqst/Rsp Time: 13 ms
Pipeline: No
SSL: No
Solved! Go to Solution.
10-21-2010 04:15 PM
From the CSS can you ping the server? If the answer is yes, try to use the default icmp keepalive. If the service is still down, you are probably hitting this bug:
10-21-2010 10:48 AM
Hi,
When you say "I can reach it fine directly and from the CSS." I'm assuming you mean ICMP reach correct?
From your PC when you do C:> telnet 10.10.82.100 8000 what do you get?
ICP probe is not a good test here as it's trying to reach the site with a HTTP HEAD and not getting a response as shown in the output..
HEAD Response: 404 Not Found
HEAD Response: 403 Forbidden
Is this a HTTP service that you're trying to probe?
Are you able to connect using the command:
CSS11503(config) socket connect host 10.10.82.100 port 8000 tcp
Regards
__ __
Pablo
10-21-2010 04:15 PM
From the CSS can you ping the server? If the answer is yes, try to use the default icmp keepalive. If the service is still down, you are probably hitting this bug:
10-21-2010 06:06 PM
ceroque,
It was the bug. A restart of the CSS while running 8.10.1.06 (and changing nothing in the config or server) fixed the stuck keepalive and brought the services up.
I also upgraded to 8.20.4.02 later on this afternoon. According to TAC and Cisco Bug Toolkit, that release should fix the keepalive bug.
Thanks for the assist.
10-21-2010 06:02 PM
juporras,
The http errors are false leads. They are becasue the server is not publishing anything in the root directory. Thanks for the suggestion though.
10-21-2010 06:45 PM
Glad you upgraded... a reboot would've been just a temporary solution when it comes to keepalive down bugs...
Good catch Cesar!
__ __
Pablo
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide