Reselct based on http response code 503
Below is the irule I am using when CLIENT_ACCEPTED { set retries 0 set default_pool pool-name } when HTTP_REQUEST { if { [HTTP::method] eq "GET" && $retries == 0 }{ set request_headers [HTTP::request] log local0. "Saving HTTP request headers: $request_headers" } } when LB_SELECTED { if { $retries > 0 } { LB::reselect pool $default_pool } } when HTTP_RESPONSE { if { [HTTP::status] starts_with "503" } { log local0. "503 error caught: retry $retries out of [active_members $default_pool]" if { $retries < [active_members $default_pool] } { HTTP::retry $request_headers return } } set retries 0 } Below are the things I noticed. Client side is hung with no responses. F5 is not giving the request to other working members which doesn’t have a 503. So we can alter the irule to send to other members in the next retry itself instead of sending to existing node. We are having a VIP with FQDN nodes with IP based persistencePool member reselection - not working
Hi, We are using BIG IP LTM 11.3.0. We have a requirement that in case a pool member fails immediately after a health checkup and LB doesn't know the until the next checkup. During this interval the connections that gets hit to the failed pool member should get routed to the next available pool member. I tried the below iRule as mentioned in the article: http://support.f5.com/kb/en-us/solutions/public/10000/600/sol10640.html, but no luck. when LB_FAILED { if { [active_members [LB::server pool]] > 0 } { catch { LB::down } LB::mode rr LB::reselect } } I even created an "inband" monitor (with default values) and associated with the pool (in addition to the https monitor). Apart from this, the "Reselect tries" option was set to "3" at the pool. Inspite of configuring these settings, the website doesn't loads from new member when LB contacts the failed pool member. Am I missing anything? Can someone help on this? Thanks Sathish