{"id":739,"date":"2013-04-01T00:00:00","date_gmt":"2013-04-01T00:00:00","guid":{"rendered":"https:\/\/fir3netwp.gmsrrpobkbd.com\/2013\/04\/01\/bigip-f5-ltm-action-on-service-down\/"},"modified":"2021-07-24T18:05:59","modified_gmt":"2021-07-24T18:05:59","slug":"bigip-f5-ltm-action-on-service-down","status":"publish","type":"post","link":"https:\/\/www.fir3net.com\/Loadbalancers\/F5-BIG-IP\/bigip-f5-ltm-action-on-service-down.html","title":{"rendered":"BIGIP F5 LTM – Action on Service Down"},"content":{"rendered":"
“Action on Service Down” defines the action that should be taken once the pool member has been marked as “down” by the associated healthcheck, after it has been selected as the load balancing target for a connection.<\/p>\n
To configure “Action on Service Down” goto the GUI and then to ‘Local Traffic \/ Pools’.<\/p>\n<\/p>\n
<\/p>\n
The 4 options are :<\/p>\n
Reject<\/strong> :<\/strong> A reset is sent to both client and server. Should you wish to use the functionality of the “Action on Service Down” feature within an iRule then the following commands can be used.<\/p>\n LB_FAILED<\/a> – Triggered when the pool member is unreachable or does not respond to a connection request. Background “Action on Service Down” defines the action that should be taken once the pool member has been marked as “down” by the associated healthcheck, after it has been selected as the load balancing target for a connection. Configuration To configure “Action on Service Down” goto the GUI and then to ‘Local Traffic \/ Pools’. … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":738,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[15],"tags":[],"yoast_head":"\n
Drop<\/strong> :<\/strong> Traffic on the established connection is silently dropped.
Reselect :<\/strong> A new pool member is selected and the existing connection is sent to the new pool member. This option is only useful when the pool member is a transparent device such as firewall or proxy server and\/or a UDP virtual server.
None :<\/strong> Established connections will still be sent to the server whilst the client and server are responding. This is useful when session draining is required (i.e the server is marked down by the health-check but existing connections are still honored).<\/p>\niRule Options<\/strong><\/h2>\n
LB::reselect<\/a> – This command is used to selects the next available member in the current pool.<\/p>\n","protected":false},"excerpt":{"rendered":"