Forum Discussion

K-Dubb's avatar
K-Dubb
Icon for Nimbostratus rankNimbostratus
Dec 17, 2010

Monitor help

Hi,

 

 

We are on version 9.4.8. We came from version 4.6.4. In 4.6.4, we had custom monitors set up of which we lost in the upgrade that would monitor our web application. I have setup a custom monitor to do this, but the bigip keeps marking the node member as down.

 

 

My monitor:

 

 

Send String: Get /somepage.asp

 

Receieve String: HTTP/1.1 200 OK

 

 

I got the receive string from doing a fiddler trace and reviewing what is returned. Perhaps this is wrong, but I am at a loss as to what I am doing wrong. It seems like it should be really simple. Thanks for any help!

 

management
monitoring
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Dec 18, 2010
    Can you try this for the send string:

     

     

    GET /somepage.asp HTTP/1.1\r\nHost: \r\nConnection: Close

     

     

    And this for the receive string:

     

     

    HTTP/1.(0|1) 200

     

     

    For details on send strings and the bigd behavior in recent versions you can check this SOL:

     

     

    SOL10655: Change in Behavior: CR/LF characters appended to the HTTP monitor Send string

     

    http://support.f5.com/kb/en-us/solutions/public/10000/600/sol10655.html

     

     

    Aaron
  • K-Dubb's avatar
    K-Dubb
    Icon for Nimbostratus rankNimbostratus
    Dec 20, 2010
    Thanks for the response Aaron. I have revied the SOL. Also, I tried the syntax from your post, and the node is still saying offline. Any suggestions?
  • hooleylist's avatar
    hooleylist
    Icon for Cirrostratus rankCirrostratus
    Dec 20, 2010
    You can check this wiki page for more suggestions on troubleshooting monitors:

     

     

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

     

     

    Aaron
  • K-Dubb's avatar
    K-Dubb
    Icon for Nimbostratus rankNimbostratus
    Dec 20, 2010
    I know why it is not working. It is because it is responding with a 302 (redirect). The page I am requesting checks to see if the client is using IE7 or IE8. If not, it redirects it to a different page. I suppose my receive string could be changed to expect a 302, but I am not sure if that is best...