Forum Discussion
uni
Altocumulus
Mar 08, 2018Wrong monitor interval, but not failing
I was upgrading software on a box I was unfamiliar with. When rebooting, I discovered what I consider a misconfiguration in one of the monitors. I has interval 1200 and timeout 16.
The behaviour I ...
Simon_Blakely
Employee
Mar 09, 2018The monitor issues a status check every 1200 seconds. If a status check does not get an OK response within 16 seconds, it will be marked down.
If the first check attempt fails to get a response before the timeout period (16 seconds), the member is marked down.
The next check will be 1184 (1200-16) seconds after the pool is marked down. If the pool member responds within 16 seconds, then the member will be marked up and will stay marked up until the next check 1200 seconds later.
Is that clear?
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects