Forum Discussion

BlurredVision_1's avatar
BlurredVision_1
Icon for Nimbostratus rankNimbostratus
Apr 12, 2010

Check until up

I am working for a customer at the moment and i was lookin gto testlab some active/passive monitor pairs using the "Inband" monitor features added in v10. When testing the setup on the BigIP VE, the "Check until up" feature is just not there.. It can't even be entered into the config either manually or interactively via tmsh.

 

 

Nothing to explain it in the V10.1.0 release notes, so does anyone know if this feature has been:

 

- Moved;

 

- Replaced;

 

- Not carried into the VE featureset or;

 

- Deprecated

 

 

Thoughts ?

 

 

snrkl.

 

3 Replies

  • Hi snrkl,

     

     

    I see the "time until up" option in 10.1 on an appliance and the virtual edition for a standard HTTP monitor and others. I don't see this option in either version for inband monitors. As an inband monitor only applies to load balanced traffic, it wouldn't make sense to limit its use until the pool member has been up for X seconds (the pool member would have to be marked up in order for the inband monitor to have any traffic to check). Hope this make sense.

     

     

    Aaron
  • Mark_Atkinson_5's avatar
    Mark_Atkinson_5
    Historic F5 Account
    Check until up has been replaced in v10.x.x with the option 'up interval.'

     

     

    Check until up stopped monitoring once the server was found to be up, instead now use 'up interval' set to a large value to slow down checks rather than stop checking altogether when the node/service is found to be up.

     

     

    see the list all option here in the tcp monitor listing 'up interval'

     

     

    monitor mon_echo4 {

     

    defaults from tcp

     

    up interval 30

     

    timeout 10

     

    dest *:7

     

    recv "test"

     

    send "test\r\n"

     

    }

     

     

     

     

     

  • Thanks for clarifying Mark. For inband monitors, I guess there still isn't such an option as there isn't much overhead in looking for layer 4 issues in all load balanced traffic to the pool.

     

     

    Aaron