Forum Discussion

jaked_150553's avatar
jaked_150553
Icon for Nimbostratus rankNimbostratus
Apr 29, 2014

additional monitoring on pools members

I have configured a pool with monitoring port 5443/tcp. On the same nodes there is http running on 8001. I need to monitor http also on the nodes and conditionally mark them down based on whether port 8001 is available or not on each node. Traffic goes only to port 5443, Can this be done LTM? I know this can be done on GTM using the depends_on monitor, is this possible with ltm (bigip version is 11.2.x)

 

7 Replies

  • So to clarify, do you have two pools each with the same nodes as members, just specified to listen on different ports (one pool defined for 5443, and the other for 8001)?

     

    If so, you'd apply a tcp monitor to your 5443 pool and an http monitor to your 8001 pool. The monitor will by default use the port specified in the pool config for your members.

     

  • You can create a HTTP monitor for port 8001 and assign that monitor to the pool with the monitor for tcp/5443. If HTTP one of the monitors is down the pool member will be down. All monitors assigned to a pool need to be up for a pool member to be available.

     

    • JRahm's avatar
      JRahm
      Icon for Admin rankAdmin
      all monitors assigned need to be up only if configured that way, you can configure the pool to still be available if one or some of the monitors are successful.
    • Cristian_Gal_12's avatar
      Cristian_Gal_12
      Icon for Nimbostratus rankNimbostratus
      Indeed, you can change the behavior in the Advanced configuration mode, but the default is All monitors need to be up for availability.
  • thanks for the answers, i got this done using the advances settings and selecting the port for http service. I tested it and it is working fine.

     

  • One more thing I wanted to know is that, if a node is marked down by bigip because i brought down service on port 8001, will connections already existing on port 5443 be torn down?

     

  • I got answer to this from the following link:

     

    https://devcentral.f5.com/articles/ltm-action-on-service-down