Forum Discussion
How does a Monitor act when node is marked down?
We currently have HTTPS monitors set up at Pool level, because we have LOTS of servers and this makes config easier. Problem arises when we mark the node down for a deployment and the monitor continues to call the web service behind that node. During deployment the service starts and stops several times, and we'd rather there be no traffic on the service.
So, is there a way to stop the monitor for a node that's been marked down? If we configure the monitor at Pool Member level will this get the desired result? How about a custom monitor configured at the Node level?
Thanks! Ryan
7 Replies
- Hannes_Rapp
Nimbostratus
If you don't want to see any health-check requests in end-servers during the maintenance, you have to remove the health-check monitor from LTM pool(s), in addition to forcing the node offline.
Forcing a pool member offline (instead of a node) would produce no different outcome, the health-check always continues to make it's requests.
- NikhilB
Employee
Look into the 'manual resume' option in the monitor profile. After a system is marked down by a monitor, you will have to manually activate it. May be handy for what your looking to do and you can apply this monitor to a specific pool member also. (as opposed to the pool level)
- RLakin_185753
Nimbostratus
I don't think that helps in my case. Manual resume only appears to ipact whether the node is automatically marked 'up' when the monitor gets good signals. Based on the previous reply, and some of my experience, the monirot will continue to fire regardless of the state of the node. What I'm trying to do is stop, or turn off, the monitor completely while the node is marked down. It appears the only way to it is by reconfiguring the monitor when we mark the node up/down. - NikhilB
Employee
Here's a tght: if you can complete your maintenance in a span of 24hrs, change the internal time of the monitor to (86400sec).
- NikhilB_149913Historic F5 Account
Look into the 'manual resume' option in the monitor profile. After a system is marked down by a monitor, you will have to manually activate it. May be handy for what your looking to do and you can apply this monitor to a specific pool member also. (as opposed to the pool level)
- RLakin_185753
Nimbostratus
I don't think that helps in my case. Manual resume only appears to ipact whether the node is automatically marked 'up' when the monitor gets good signals. Based on the previous reply, and some of my experience, the monirot will continue to fire regardless of the state of the node. What I'm trying to do is stop, or turn off, the monitor completely while the node is marked down. It appears the only way to it is by reconfiguring the monitor when we mark the node up/down. - NikhilB_149913Historic F5 AccountHere's a tght: if you can complete your maintenance in a span of 24hrs, change the internal time of the monitor to (86400sec).
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com