Forum Discussion

markymark_30996's avatar
markymark_30996
Icon for Nimbostratus rankNimbostratus
Sep 14, 2018

Monitoring poolmember thru html return code

We like to change the way the loadbalancers monitor the poolmembers. Currently, the LB check if a specific port is available/accessible. To give us some flexibility to exclude a poolmember temporarily, we want the LB to check an URL and verify the html return code.

 

I will give an example. The LB should: •check an URL something like ; •verify the html return code is ‘200’; •use the response time to determine which poolmember is the fastest.

 

May I ask if this is possible?

 

application delivery
BIG-IP
devops
LTM

4 Replies

Sort By
  • Dan_Pacheco's avatar
    Dan_Pacheco
    Icon for Cirrus rankCirrus
    Sep 14, 2018

    You are describing two separate features. First is a “http health monitor” to send an http request and receive a http status code back. Secondly distribution method “response time”.

     

    There are several knowledge base articles that describe how to set up health checks in detail. https://support.f5.com/csp/article/K2167

     

    If you still have questions after reading this post back.

     

  • Dan_Pacheco's avatar
    Dan_Pacheco
    Icon for Cirrus rankCirrus
    Sep 14, 2018

    Also don’t forget to use the full http hostname, not just the short name that you have in your example above.

     

  • markymark_30996's avatar
    markymark_30996
    Icon for Nimbostratus rankNimbostratus
    Sep 14, 2018

    Ok, how about using the response time to determine which poolmember is the fastest? Do we have this kind of feature in F5?

     

  • Stanislas_Piro2's avatar
    Stanislas_Piro2
    Icon for Cumulonimbus rankCumulonimbus
    Sep 14, 2018

    To check if response code is 200 for URL use following configuration

     

    send string

     

     GET /alive/1.0/alive HTTP/1.1\r\nHost: rbcdevesh210:8081\r\nConnection: Close\r\n\r\n

    and in receive string

     

    HTTP/1.[01] 200

    to load balance with priority based on response speed, use fastest(member) load balancing method