Problems monitoring web page content - LTM v. 9.4.x

Hi Brantly,

 

 

A receive string of 'GET /hmcng_web/login.jsp HTTP/1.1\r\nHost: hrsdr\r\nConnection: Close' should work for 9.4.x. What is the receive string your'e using?

 

 

You can check this page for tips on troubleshooting LTM monitors:

 

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

 

 

Aaron

Thank you Aaron. My receive string is:

 

 

Use a valid HRS username and password

 

 

I will check out the link you sent. Appreciate your time.

Interesting. Connection Refused. Wonder why? The webpage comes up fine:

 

 

14:18:16.656245: send_active_service_ping: addr=::ffff:30.248.91.25:9002 writing GET /hmcng_web/login.jsp HTTP/1.1

 

Host: hrsdr

 

Connection: Close

 

 

...

 

14:18:16.656266: (_send_active_service_ping): addr=::ffff:30.248.91.25:9002 sent ping

 

14:18:16.656280: (_main_loop): wfd selected for addr=::ffff:30.248.91.25:9020 pending=1

 

14:18:16.656293: (_send_active_service_ping): addr=::ffff:30.248.91.25:9020

 

14:18:16.656310: (_connect_to_service): addr=::ffff:30.248.91.25:9020 connect: Connection refused

 

14:18:16.656341: (_send_active_service_ping): addr=::ffff:30.248.91.25:9020 unable to connect; giving up

 

14:18:16.656365: (_main_loop): wfd selected for addr=::ffff:30.248.91.25:9001 pending=1

 

14:18:16.656379: (_send_active_service_ping): addr=::ffff:30.248.91.25:9001

 

14:18:16.656400: send_active_service_ping: addr=::ffff:30.248.91.25:9001 writing GET /

It looks like this monitor is checking multiple pool members: port 9001, 9002, and 9020. The 9020 is being refused, but you referenced port 9002 at the top. Are you sure you're looking at the right pool members?

Sorry, not blowing anyone off on my monitoring issue. I've been on vacation and just returned today. I'm jumping back into this issue now.

Based on this output, I really don't know why this monitor isn't working:

 

 

[bperry@TNNASF5SF1:Standby] / curl -v http://30.248.91.11/hmcng_web/login.jsp

 

* About to connect() to 30.248.91.11 port 80

 

* Trying 30.248.91.11... connected

 

* Connected to 30.248.91.11 (30.248.91.11) port 80

 

> GET /hmcng_web/login.jsp HTTP/1.1

 

> User-Agent: curl/7.15.3 (i686-redhat-linux-gnu) libcurl/7.15.3 OpenSSL/0.9.7l zlib/1.1.4

 

> Host: 30.248.91.11

 

> Accept: */*

 

>

 

< HTTP/1.1 200 OK

 

< Cache-Control: no-cache="set-cookie"

 

< Date: Mon, 30 Aug 2010 17:42:19 GMT

 

< Content-Length: 10405

 

< Content-Type: text/html; charset=ISO-8859-1

 

< Set-Cookie: JSESSIONID=mpLyM7tbdnBDnxPyC0wvgh2gL5GQqZsGxFGsdP1TphwG3tl5ycW0!722396472; path=/

 

< X-Powered-By: Servlet/2.4 JSP/2.0

 

< Set-Cookie: BIGipServerWeb_HRS=442234910.11555.0000; path=/

 

 

also, here is my receive string I found in the output:

 

 

});

 

 

var loginPanel = new Ext.Panel({

 

contentEl: 'login-panel',

 

title:'Welcome to the Healthy Returns System (HRS)',

 

frame:true,

 

width:500,

 

height:200,

 

autoShow:true,

 

renderTo:'ext-login-panel'

 

});

 

 

Anyone see anything I may be missing? Thanks.

This is what I've gathered from your post:

Send string:

GET /hmcng_web/login.jsp HTTP/1.1\r\nHost: hrsdr\r\nConnection: Close

Receive string:

Use a valid HRS username and password

Output:

}); 
var loginPanel = new Ext.Panel({ 
contentEl: 'login-panel', 
title:'Welcome to the Healthy Returns System (HRS)', 
frame:true, 
width:500, 
height:200, 
autoShow:true, 
renderTo:'ext-login-panel' 
}); 

If I have that correct, then your output does not contain the Receive String and I would expect the monitor to fail. Please clarify.

Sorry for the confusion. The receive string I mentioned above is incorrect. The string configured on my bigip is actually:

 

 

Welcome to the Healthy Returns System

This may be a case of a bad Send String - but since I've never run 9.4.x, I don't know how many trailing \r\n are required. Hoolio said it should work without any, and he may be right. But if it were me, I'd also try one trailing \r\n, and then two if one didn't work.

 

 

I also suspect the web server may not like your Host: header. In the monitor you specify Host: hrsdr, but curl sets the host header to the IP: Host: 30.248.91.11.

 

 

Have you taken a network trace of the monitor traffic? Taking and/or analyzing network traces isn't something everyone knows how to do, so don't feel bad if you haven't and don't know how. But a network traces should isolate this problem very quickly.

I did run a trace, and everything there seems to be in order as well. I'll go ahead and start fooling with the send string.