Forum Discussion

taylan_sayilan_'s avatar
taylan_sayilan_
Icon for Nimbostratus rankNimbostratus
Feb 28, 2019

Health monitor to pool members

Hello, I have 2 node members belong to pool that has been monitored with x port which is also service port. both 2 node's y port was opened and i want to have health monitor different then service port .

 

GET /ping/index HTTP/1.1\r\nHost: a.b.c.d:x\r\nConnection: close\r\n that monitor working properly. GET /ping/index HTTP/1.1\r\nHost: a.b.c.d:y \r\nConnection: close\r\n is not working properly.

 

when i add health monitor which is "GET /ping/index HTTP/1.1\r\nHost: a.b.c.d:y \r\nConnection: close\r\n " to pool members is not working. do u have any idea why its not working or how could i make it work ?

 

Best Regards,

 

application delivery
cloud
iControl
iRules

7 Replies

Sort By
  • Dave_McCauley_3's avatar
    Dave_McCauley_3
    Icon for Cirrostratus rankCirrostratus
    Feb 28, 2019

    What’s the response on port y and what’s your receive string? Sounds like it’s not using the same setup and responding differently. Run it with curl or netcat on the command line and see if both ports respond the same way.

     

    • Michael_Saleem1's avatar
      Michael_Saleem1
      Icon for Cirrus rankCirrus
      Feb 28, 2019

      You can also try enabling health monitor logging on the pool temporarily to see what response the F5 is receiving back from the pool members (the F5 will create a log file in the /var/log/monitors/ directory)

      1) Enable logging on the pool

      tmsh modify ltm pool  members modify { all { logging enabled } }

      2) Check the logs from bash

      cat /var/log/monitors/

      3) Disable logging on the pool

      tmsh modify ltm pool  members modify { all { logging disabled } }

  • uzair's avatar
    uzair
    Icon for Nimbostratus rankNimbostratus
    Feb 28, 2019

    Configure the Alias port in health monitor as port Y.

     

  • Jinshu's avatar
    Jinshu
    Icon for Cirrus rankCirrus
    Feb 28, 2019

    Hi Mate,

     

    It is because the health monitor is configured for port X and you might missed configuring port Y as alias so BIG IP will ignore it.

     

    Configure port Y as alias in the health monitor and verify the status.

     

    -Jinshu