Configuring HTTP Probe

Hi All,
I want to configure a new HTTP Probe. The application server was installed with the following URL: http://lta43:8011/HealthApp/health.txt
The goal is ACE can monitor this URL.
What would be the way to configure the Probe in the ACE?
Regards,
Jaime.

Hi Jaime,
The minimum configuration you would need is the following:
probe http
  port 8011
  request method get url /HealthApp/health.txt
  expect status 200 200
As you can see, I didn't configure the hostname of the server anywhere. That's because the probe will be associated to a real server, and the IP address will be the one of the server it's checking.
There are also several other parameters you can configure the probe, such as timers or headers to be inserted into the request, so I would recommend you to have a look at the relevant chapter of the configuration guide:
http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/probe.html
Daniel

Similar Messages

  • Http probe on non-standard tcp port 8021

    I've configured http probe on standard port 80 with no issue. I'm now trying http probe on non-standard tcp port 8021, confirmed with packet capture to confirm that the CSM is indeed probing, status code 403 is returned but the reals are showing "probe failed". Am I missing something? Thank you in advance.
    CSM v2.3(3)2
    probe 8021 http
    request method head
    interval 2
    retries 2
    failed 4
    port 8021
    serverfarm TEST
    nat server
    no nat client
    real 10.1.2.101
    inservice
    real 10.1.2.102
    inservice
    probe 8021
    vserver TEST
    virtual 10.1.2.100 tcp 8021
    serverfarm TEST
    replicate csrp connection
    persistent rebalance
    inservice
    VIP and real status:
    vserver type prot virtual vlan state conns
    Q_MAS_8021 SLB TCP 10.1.2.100/32:8021 ALL OUTOFSERVICE 0
    real server farm weight state conns/hits
    10.1.2.101 TEST 8 PROBE_FAILED 0
    10.1.2.102 TEST 8 PROBE_FAILED 0

    you need to specify what HTTP response code you expect.
    The command is :
    gdufour-cat6k-2(config-slb-probe-http)#expect status ?
    <0-999> expected status - minimum value in a range
    The default is to expect only 200.
    This is why your 403 is not accepted.
    Gilles.

  • HTTPS Probe on ACE

    We have some webserver behind our ACE that use SSL certificates that are issued by an internal CA.
    Do I need to do anything special in order to probe HTTPS?  Does the ACE need the internal CA to be trusted?
    Thanks.
    Jason

    Hi,
    If https server is working properly, only you need to do is configure https probe on ACE like below.
    You do not have to anything related certificate on ACE side.
    ACE-A327/context02# show running-config
    Generating configuration....
    probe https HTTPS
      interval 15
      passdetect interval 60
      ssl version all
      expect status 200 200
      open 1
    rserver host S1
      ip address 10.1.142.209
      inservice
    serverfarm host SF
      probe HTTPS
      rserver S1
        inservice
    interface vlan 11
      ip address 10.1.142.1 255.255.255.0
      no shutdown
    ACE-A327/context02# show probe detail
    probe       : HTTPS
    type        : HTTPS
    state       : ACTIVE
    description :
       port      : 443     address     : 0.0.0.0         addr type  : -          
       interval  : 15      pass intvl  : 60              pass count : 3   
       fail count: 3       recv timeout: 10  
       SSL version      : All
       SSL cipher       : RSA_ANY
       http method      : GET
       http url         : /
       conn termination : GRACEFUL 
       expect offset    : 0         , open timeout     : 1        
       regex cache-len  : 0        
       expect regex     : -
       send data        : -
                    ------------------ probe results ------------------
       associations ip-address      port  porttype probes   failed   passed   health
       ------------ ---------------+-----+--------+--------+--------+--------+------
       serverfarm  : SF
         real      : S1[0]
                    10.1.142.209    443   DEFAULT  11       0        11       SUCCES
    S
       Socket state        : CLOSED
       No. Passed states   : 0         No. Failed states : 0
       No. Probes skipped  : 0         Last status code  : 200
       No. Out of Sockets  : 0         No. Internal error: 0
       Last disconnect err :  -
       Last probe time     : Thu Apr 14 17:34:02 2011
       Last fail time      : Thu Apr 14 17:30:42 2011
       Last active time    : Thu Apr 14 17:30:44 2011
    ACE-A327/context02#
    Additionaly, you can specify cipher in client hello, also you can select ssl/tls version.
    http://www.cisco.com/en/US/docs/interfaces_modules/services_modules/ace/vA2_3_0/configuration/slb/guide/probe.html#wp1162289
    If you find this helpful, please rate this topic.
    Regards,
    Kim.

  • Local Director http probes with URLs and http redirect mode

    I am trying to configure http probes on my Local director 430 running 4.2.3
    I am using http redirect mode so the Virtual is bound to URLs not REALs with are linked to DIPs which are bound to REALs. So far the probes seem to not actually do anything. Does anyone know if the probes are compatible with URL redirect loadbalancing. And if so how one would go about configuring it.
    Thanks for your help.

    keepalive can be used for the probe notification in this case.
    Check the following url for details.
    http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/bsccfggd/services.htm#xtocid727448

  • HTTP Probe

    How does the HTTP Probe function work ? Setting it up appears simple but it's not clear to me whether 1) the Local Director's will generate the probe traffic themselves or 2) do they just monitor return codes in client query's ?
    If they're just monitoring client traffic, then a failed server may go unnoticed for some time if the file specified in the ProbeHTTP command isn't requested by a client for a period.
    Also, aside from reviewing the syslogs, is there any way to see that it was the Probe which caused a server to change to a "failed" state ?

    I haven’t used http probe yet but the docs look like it probes either the http get or http header (depending on how it’s configured). I’m sure you can use this with snmp to avoid having to parse the syslogs. Or setup a script to do that for you.

  • Attempting to use HTTP probe

    We're currently using the TCP probe for a load balanced app, however will need to change it to HTTP. The back-end servers are Window based and are running IIS. There's an app team, another team that supports IIS and another team that support the servers. Once we've configured the HTTP probe on the ACE, including the request method and the url, which of the above team would we need to reach out to coordinate the url path and the expected status code from the server?
    Thanks.
    _ Greg...  

    Thanks Kanwal. I was just curious which team would the load balancer team be typically dealing with as in my case, it has become a hot potatoe syndrom and none of the teams is willing to own up to this task and pointing fingers to the others. It would seem to me the app team be most likely the one as the server team be just supporting the servers and the IIS team be managing the IIS.
    Thanks again.
    _ Greg

  • HTTP Probe and DNS names

    Hi,
    I think i have a very simple question.
    I want to setup an HTTP probe to test for URL, like http://www.cnn.com/
    When I specify such "request" command under probe confif menu, I would assume that ACE will need to perform name resolution for www.cnn.com, but I cannot find any reference on how to configure DNS servers on ACE....
    Am I missing something, or maybe I cannot do HTTP probe request by name and it had to be in a format of
    http://<ip address/?
    Thank you,
    David

    Hi,
    My initial idea was to use the following command:
    request method get url http://www.abc.com/
    This is why I had my initial question about how will ACE resolve www.abc.com
    Now thinking more about it I wonder if ACE even needs to resolve it at all.
    I intend to apply the probe under rserver in serverfarm config, so ACE will know the IP address of where to send the probe from rserver configuration. If so, no DNS query is needed. ACE will just construct the packet and put relevant information in HTTP portion.... Am I correct?
    If yes, what would be a difference is doing
    header Host header-value "http://www.abc.com/"
    vs
    request method get url http://www.abc.com/
    Thanks!
    David

  • ACE HTTP Probe with regex

    ACE HTTP Probe with regex
    Hi,
    I'm trying to setup a HTTP probe with expected string rather then a code (config below). I do a GET for the page then a search for a string in the response however it's not working, as probe appears as failed.
    I've tested the connection to the server by using telneting and then looking at the page displayed to make sure the string I want to match is in the response.
    probe http HTTP-PROBE
    port 43050
    interval 30
    passdetect interval 30
    passdetect count 1
    request method get url /action=help
    open 43050
    expect regex action=help
    Q. Is there anything wrong with this configuration and what I'm trying to achive?
    Thanks,
    Pritesh

    Use "expect status" under probe config. expect regex doesnt work if expect status is not configured.
    expect regex work flawlessly with static pages. It doesnt work all the time with dynamic pages.
    Specially if "content-length" header is missing from Server response.
    Hope it helps
    Syed Iftekhar Ahmed

  • ACE HTTP probe hash md5 value

    Hi,
    We would like to see the hash value calculated by the ACE when the HTTP probe hash command configured.
    This is possible on CSS via the "sh service" command. We have tried to get it from sh rserver , sh probe XXX detail sh serverfarm XXX det but we do not get it.
    Is this possible to get it on the ACE as we do on the CSS?
    We need this to manually configure it via the hash <value> command because if the ACE probe is reseted for any reason, the probe http hash will be re-calculated based on the first http response of the server and we can not predict that the server will give the expected web page at this time.
    A // question is: on what the md5 value is calculated? HTTP header + payload or only http object payload? We have calculated the md5 hash value by ourselves but the probe is still failing whatever the http portion used for the calculation is.
    Many thanks for your help.
    Regards/ludovic.

    probe http MD5-HTTP
    interval 15
    passdetect interval 15
    request method get url /index.html
    expect status 200 200
    hash 2441DA7F68A265F8CFB4426B6897CE33
    And here is how I computed the hash on the server itself [linux machine]
    md5sum /var/www/HTML/index.html
    2441da7f68a265f8cfb4426b6897ce33 /var/www/HTML/index.html
    [root@linux-1 tftpboot]#
    The probe is UP
    switch/Admin# sho probe MD5-HTTP detail
    probe : MD5-HTTP
    type : HTTP
    state : ACTIVE
    description :
    port : 80 address : 0.0.0.0 addr type : -
    interval : 15 pass intvl : 15 pass count : 3
    fail count: 3 recv timeout: 10
    http method : GET
    http url : /index.html
    Hash-value : 2441da7f68a265f8cfb4426b6897ce33
    conn termination : GRACEFUL
    expect offset : 0 , open timeout : 10
    expect regex : -
    send data : -
    --------------------- probe results --------------------
    probe association probed-address probes failed passed health
    ------------------- ---------------+----------+----------+----------+-------
    serverfarm : linux1
    real : linux1[0]
    192.168.30.27 13 4 9 SUCCESS
    md5sum is a standard tool.
    Nothing fancy about it.
    Gilles.

  • Strange HTTP probe with .cfm files.

    Hey All,
    I setup an http probe that checks a .cfm page for a keyword. according to the documentation there needs to be a content-length in the header for this to be parsed correctly. For some reason this .cfm page does not send the content-length. The developer manually told coldfusion to put the content-length in the header and I can see that the header now has the content-length. The probe is still failing with "Unrecognized or invalid response" If i put a test html page with a keyword, it parses it correctly and passes. If i change the keyword it fails as expected. Has anyone had any issues with the headers of coldfusion? There is no compression on the server side. Below is the probe.
    probe http KEYWORD
      interval 15
      passdetect interval 30
      request method get url /index.cfm
      open 2
      expect regex "go"
    Any help or suggestion would be much appreciated.
    Regards,
    Christian

    Hey Christian and Paul,
    Actually, when using expect regex, you don't need the expect status.  I alerted the documentation team about this and they have updated the documents with the following note:
    Note If you do not configure an expected status code, any response from the server is marked as failed. However, if you configure the expect regex command without configuring a status code, the probe will pass if the regular expression response string is present.
    Christian,
    You mention that you see the error message Unrecognized or invalid response, even with the content-length header added.  Is this the same error message you got before your app team added the header?  If so, then I might suspect that the ACE doesn't like the format they used.  The header should look like this:
    Content-Length:
    This is per RFC2616 and can be found at section 14.13 here.  Note that the C and the L are uppercase, the header name is immediately followed by a colon, and there is a spece between the colon and the value.
    I would recommend confirming that the header matches this description in a network capture.  If it does match, then I would like to see the capture, if possible.
    Thanks and I hope this helps,
    Sean

  • ACE Module - HTTP Probe failure

    Hi,
    I have configured the http probe with expect status 200 202, but the probe fails despite availability of the port on rserver.
    I tried head/get method to see the return code, and it came back with HTTP1.1/302. How can I configure an http probe to understand HTTP 302 code as success return.
    Thanks.

    I changed the expect status value as below
    probe http TEST-HTTP
    interval 30
    passdetect interval 10
    request method head
    expect status 302 302
    The probe is still failing with the log message
    Apr 20 2009 12:04:35 : %ACE-3-251010: Health probe failed for server 192.168.1.10 on port 80, received invalid status code
    On 'show probe detail' it shows the last status code as 400 which means Bad Request
    --------------------- probe results --------------------
    probe association probed-address probes failed passed health
    ------------------- ---------------+----------+----------+----------+-------
    serverfarm : TEST-APP
    real : TEST-SERVER1[80]
    192.168.1.10 27 27 0 FAILED
    Socket state : CLOSED
    No. Passed states : 0 No. Failed states : 1
    No. Probes skipped : 0 Last status code : 400
    No. Out of Sockets : 0 No. Internal error: 0
    Last disconnect err : Received invalid status code
    Last probe time : Mon Apr 20 12:05:33 2009
    Last fail time : Mon Apr 20 12:00:53 2009
    Last active time : Never
    The http page is showing perfectly on the web browser. Also, using the http head/get tool, I can see that 302 is returned.
    What could be the problem.
    Regards.

  • Http probe on ace 30

    hi,
    i need to configure an http probe on ace,
    the url is like /zz?/ee/rr.png
    the probe is get /zz?/ee/rr.png
    pb: i can type this ? ,
    how can i do that ?
    thanx for your answers

    That's just easy. Type CRTL + v and then you can type ?. That's all.

  • ACE HTTP Probe

    Hi,
    This is the current probe that I am using:
    probe http http-probe
    interval 3
    passdetect interval 3
    passdetect count 3
    request method head
    expect status 200 200
    Someone told me that I should be using a more sophisticated web page to probe. If you agree with that statement, could someone please provide a sample config?
    Thank you...

    Hi,
    I'm not sure what your colleague meant by more sophisticated. When I've set up an HTTP probe I've asked that the server management team set up a simple static page on the server that can be tested. So in my probe I'd specify something like:
    request method head url /serverhere.html
    This enables the team to take a server out of service by renaming the page (e.g. to servernothere.html) without having to ask me to modify the ACE configuration. The server can then be tested without real users having access and brought back in when they're happy.
    HTH
    Cathy

  • ACE Appliance HTTP Probe with "POST" query

    Does the ACE support HTTP Probe with a "POST" query?
    Thanks
    Joe

    Hi Joe,
    The ACE only supports GET and HEAD
    Here is the documentation related to this:
    http://www.cisco.com/en/US/customer/docs/interfaces_modules/services_modules/ace/vA5_1_0/configuration/slb/guide/probe.html#wp1031485
    Cesar R

  • CSM HTTP Probes with Method GET

    Hello.
    How does the HTTP Probe with Method GET work on CSM and what is the difference with CSS?
    CSS calculates the HASH of the web page it receives as a first answer and considers that as a REFERENCE HASH, to compare with subsequent answers. Is the behaviour of the CSM the same?
    In the CSS it is also possible to insert the HASH in the configuration as a reference HASH. I did not find such a command on the CSM. Is that feature not present on CSM?
    Thanks.

    the CSM just looks for the response code.
    No hash or anything similar to the CSS.
    Regards,
    Gilles.

Maybe you are looking for