Last Modified: Jun 20, 2019
See more info
Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 22.214.171.124, 126.96.36.199, 13.1.1, 188.8.131.52
14.1.0, 14.0.0, 184.108.40.206, 220.127.116.11
Opened: May 07, 2018
Related AskF5 Article: K25348242
When sufficient resources are configured with the same monitor interval, and the monitor timeout value is no more than two times the monitor interval, the monitored resource may be marked as unavailable (due to a timeout) then immediately changed to available.
Monitor probes are not consistently performed at the configured interval.
Monitor interval is lower than the number of resources configured with the same monitor interval.
Set the monitor interval to a value greater than the number of resources monitored using that same interval value. The key to this workaround is to ensure that the sum of the resources monitored at a given interval is not greater than the interval. That can be accomplished several ways depending on your configuration and requirements. For example, if the monitoring interval is 30 seconds and there are 40 different monitors with a 30-second interval and each monitor is assigned to exactly one resource, there are at least two options: -- Change the interval for 10 of the monitors to a different value. -- Set the monitor interval to 40. Note: If you change the monitor interval, make sure to also change the timeout value to follow best practices: timeout value = (3 x interval) + 1.
Monitoring is now consistently performed at the configured interval regardless of the number of resources with the same monitor interval.