For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Patrik_Jonsson's avatar
Patrik_Jonsson
Icon for MVP rankMVP
Nov 07, 2012

LB_FAILED not always triggered when all members disabled

  Hi there   I'm on a mission to create a generic iRule in order to serve sorry-pages from fallback hosts.     A few criterias that was needed:   1. Strip the subdomain.   2. Pr...
application delivery
dev
devops
iRules
What_Lies_Bene1's avatar
What_Lies_Bene1
Icon for Cirrostratus rankCirrostratus
Nov 07, 2012

OK, just FYI a Pool Member that is disabled will continue to service any existing connections until they are closed or time out, but will not receive new connections (except persisted connections I think).

 

Keep in mind that persistence effectively bypasses load balancing.

 

 

I believe even when a monitor marks a Pool Member as down, if you have Action on Service Down set to the default value of None, then existing and possibly persisted connections will continue to work as long as the F5 sees data being sent and received to and from that Pool Member. OneConnect overcomes this by making a persistence decision on each request (and thus load balancing each request) within a connection, not just when the connection is initially established and it won't persist to a node marked as down or disabled.

 

 

Does that make sense?