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

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

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

HTTP probes not working on Local Director 416 using 4.2.4

Situation: We are using an LD-416 to load balance http and https requests for 4 web servers with publicly addressable IP's behind one publicly addressable virtual IP.

Desired: We would like to setup http probes to monitor a web page on the servers and fail them if the expected header result of 200 is not met.

Steps taken: Setup http probes to monitor one of the web servers per the Command Reference guide. Page used for testing is written to generate a header response other than the expected result. Commands entered:

1. probe real websrv04 HTTP 1

2. probehttp real websrv04 file /sw/testfileserver/badpage.asp expected 200 request HEAD

3. probeconfig HTTP 1

4. write t

5. write mem

Websrv04 is defined as a real server. We have also tried doing it by the IP address as well as leaving out those settings for which we're checking the defaults (ie. expected and request).

Expectation: The LD should run an http probe against websrv04 every ten seconds looking for the page "badpage.asp" and expect to receive a header result of 200. The first time the LD sees anything other than the expected result, it should fail the server.

Reality: The server never fails. We can even remove the page in question from the web server and the probe still will not fail the server.

Any and all help would be most greatly appreciated.

  • Application Networking
Cisco Employee

Re: HTTP probes not working on Local Director 416 using 4.2.4

you need to configure a probe to the virtual address as well otherwise probing does not work.

This is done in the web document but it does not appear clearly that it is necessary. Hoewever, you need it to make it work.


New Member

Re: HTTP probes not working on Local Director 416 using 4.2.4

Thanks, that did the trick.