Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

HTTP probe not working

Hi,

I had a migration this last weekend. I ran into an issue that most of the servers would fail HTTP probes, but when configured for ICMP the servers would answer it's probe and load balancing works fine.

What is the major symptom of this issue?

Thank you,

John...

4 REPLIES
Silver

Re: HTTP probe not working

Hi,

what is the error that you get in "show probe XXX detail?

ACE_module5/Admin# show probe HTTP_PROBE detail

probe : HTTP_PROBE

type : HTTP

state : ACTIVE

description :

----------------------------------------------

port : 80 address : 0.0.0.0 addr type : -

interval : 10 pass intvl : 10 pass count : 3

fail count: 3 recv timeout: 10

http method : GET

http url : /

conn termination : GRACEFUL

expect offset : 0 , open timeout : 1

expect regex : -

send data : -

------------------ probe results ------------------

associations ip-address port porttype probes failed passed health

------------ ---------------+-----+--------+--------+--------+--------+------

rserver : SERVER1

192.168.10.45 80 -- 24 15 9 SUCCESS

Socket state : CLOSED

No. Passed states : 1 No. Failed states : 1

No. Probes skipped : 0 Last status code : 200 <-----------------------------------------------

No. Out of Sockets : 0 No. Internal error: 0

Last disconnect err : - <----------------------------------------------

Last probe time : Tue Apr 7 16:21:05 2009

Last fail time : Tue Apr 7 16:17:16 2009

Last active time : Tue Apr 7 16:20:05 2009

What did you change during migration? Is an ACL/Firewall blocking HTTP traffic to the ACE - server?

Kr,

Dario

New Member

Re: HTTP probe not working

Dario,

Unfortunatley; I did not save the outputs of the show probe detail commands, but I would guess that it was very generic like the one you posted.

port : 80 address : 0.0.0.0 addr type : -

interval : 10 pass intvl : 10 pass count : 3

fail count: 3 recv timeout: 10

http method : GET

http url : /

conn termination : GRACEFUL

expect offset : 0 , open timeout : 1

expect regex : -

send data : -

There were no FW or ACL change for the migration. Load balancing is working fine once I configured the probe to ICMP. My probe is configured to probe the header of the page and not a specific URL. I wonder if this symptom only occurs when the webpage does not have a default page configured.

I do remember during the brief time period I had to troubleshoot that when I tried to view the default page via telnet "telnet 10.10.10.10 80" it would connect to port 80, but when I entered "GET /" I would get a 404 error on some servers or I would get nothing on others.

John...

Silver

Re: HTTP probe not working

Hi,

If you still want to troubleshoot aside of the prod serverfarm, you can configure a dummy serverfarm, add an rserver that had those problems and define your HTTP probe under it. Logically, it would still fail but you will be able to see the error using the show probe XXX detail command.

If you want, post your config of your probe, your rserver and the output of the show probe xxx detail command.

Kr,

Dario

New Member

Re: HTTP probe not working

Team,

The issue that I ran into was two fold. 1) My probe was configured to probe an HTTP header.

2) The server did not have a default web page configured.

When I configured my probe to probe the actual url that the clients were requested the probe worked fine.

Johnny...

190
Views
3
Helpful
4
Replies