Http Monitor

have u seen this article? it's very helpful.

 

 

troubleshooting ltm monitors by aaron

 

http://devcentral.f5.com/wiki/default.aspx/AdvDesignConfig/TroubleshootingLtmMonitors.html

Do you have the monitor assigned to the pool? Did the server return a status 200 response when you got the "service unavailable" message?

 

 

Is the IP:port which returned the service unavailable message the same as the pool member IP:port?

 

 

Aaron

thanks nitass

 

 

yes the server returns 200 response

 

the ip which return this is the ip of the member where the service has stopped, the other ip works just fine, the only problem is that why the bigip cannot recognize that this member is unavialable (since monitor fails) and display it in red and not green ?

Can you post the output of the curl command to the test page of the pool members (for each success and fail cases)?

 

 

curl -v http://pool-member1/test/index.html

 

curl -v http://pool-member2/test/index.html

 

Member 1

 

curl -v http://192.168.1.2:81/test/index.html

 

* About to connect() to 192.168.1.2 port 81

 

* Trying 192.168.1.2... connected

 

* Connected to 192.168.1.2 (192.168.1.2) port 81

 

> GET /test/index.html HTTP/1.1

 

> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5

 

> Host: 192.168.1.2:81

 

> Accept: */*

 

>

 

< HTTP/1.1 200 OK

 

< Date: Wed, 22 Jun 2011 05:16:50 GMT

 

< Content-Type: text/html

 

< Last-Modified: Mon, 06 Jun 2011 07:32:52 GMT

 

< Content-Length: 293

 

< Content-Language: en-US

 

< Server: Proxy/1.0

 

< Age: 276

 

 

 

 

 

This is Intelligent

 

 

 

Enjoy !

 

 

Connection 0 to host 192.168.1.2 left intact

 

* Closing connection 0

 

 

Member 2

 

curl -v http://192.168.1.3:81/test/index.html

 

* About to connect() to 192.168.1.3 port 81

 

* Trying 192.168.1.3... connected

 

* Connected to 192.168.1.3 (192.168.1.3) port 81

 

> GET /test/index.html HTTP/1.1

 

> User-Agent: curl/7.15.5 (i686-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5

 

> Host: 192.168.1.3:81

 

> Accept: */*

 

>

 

< HTTP/1.1 200 OK

 

< Date: Wed, 22 Jun 2011 05:02:11 GMT

 

< Content-Type: text/html

 

< Last-Modified: Mon, 06 Jun 2011 07:32:52 GMT

 

< Content-Length: 293

 

< Content-Language: en-US

 

< Server: Proxy/1.0

 

< Age: 1346

 

 

 

 

 

This is Intelligent

 

 

 

Enjoy !

 

 

Connection 0 to host 192.168.1.3 left intact

 

* Closing connection 0

 

 

thanks

I think the HTML in the response content was stripped. Can you try uploading it as a text file and attaching it to a reply to this post?

 

 

Aaron

i am sorry i did not get what you mean !!!!

I'm not fully understanding the problem. It seems like you have two pool members with service port 81. Which pool member is using service port 80?

 

 

Do you mean, you have a pool member with port 80, and it is not supposed to be "up", but it passes the monitor test?

 

 

For the logs, you can check /var/log/ltm, which should contain the logs related to LTM.

 

 

Can you also give us the pool configuration? You can use the following command:

 

b pool [pool_name] list

 

 

Dears, I have a viprion box, I configured an internal vlan , and a pool includes a web server from this vlan ....and its pingable from the viprion , the problem is that I configured HTTP monitor but it shows that the web server is down although that from the SSH of the viprion I can telnet the web server in port 80 !!!!!!!!!!!!!!!!!!!!!!!!!!!!

Can you share your HTTP monitor configuration?