{"id":865,"date":"2014-07-17T12:04:48","date_gmt":"2014-07-17T12:04:48","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2014\/07\/17\/gtm-why-does-the-monitor-status-change-to-down-after-a-single-probe-failure\/"},"modified":"2023-01-06T16:43:08","modified_gmt":"2023-01-06T16:43:08","slug":"gtm-why-does-the-monitor-status-change-to-down-after-a-single-probe-failure","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/gtm-why-does-the-monitor-status-change-to-down-after-a-single-probe-failure.html","title":{"rendered":"GTM Monitor Marked Down After a Single Failure"},"content":{"rendered":"
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.<\/p>\n
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.<\/p>\n
These conditions are :<\/p>\n
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.<\/p>\n
Further Information : http:\/\/support.f5.com\/kb\/en-us\/solutions\/public\/8000\/100\/sol8170.html<\/a><\/p>\n","protected":false},"excerpt":{"rendered":" Issue 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. Reason 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 … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":864,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"yoast_head":"\n