You may observe the GTM marking the monitor as down even though only a single probe failure has occurred and the timeout not been reached.
When configuring a monitor there are various conditions that are considered by the GTM as a down response. This means that the GTM will mark the monitor as down rather then wait for the monitor timeout to exceed.
These conditions are :
- All Monitors – if a RST is received or if there is no response after the 3WHS.
- HTTP Monitors (without receive string) – If a response is not received within the probe timeout period. Note that 4xx and 5xx responses are considered valid.
- HTTP Monitors (with receive string) – If the response does not contain the receive string. Or if the receive string is not received within the probe timeout period.
To instruct the GTM to ignore these down responses, and wait until the monitor timeout is reached before marking the monitor as down the option ‘Ignore-down-response’ is enabled.
Further Information : http://support.f5.com/kb/en-us/solutions/public/8000/100/sol8170.html
- How to Configure a BIND Server on Ubuntu - March 15, 2018
- What is a BGP Confederation? - March 6, 2018
- Cisco – What is BGP ORF (Outbound Route Filtering)? - March 5, 2018
Want to become an F5 Loadbalancers expert?
Here is our hand-picked selection of the best courses you can find online:
F5 BIG-IP 101 Certification Exam – Complete Course
F5 BIG-IP 201 Certification Exam – Complete Course
and our recommended certification practice exams:
AlphaPrep Practice Tests - Free Trial