Forum Discussion
What_Lies_Bene1
Nov 15, 2012Cirrostratus
I've come up with two alternative iRules and something else entirely;
1) Reselect a different pool member. This should work and not pick another member that is disabled (as only the fact the connection is existing or persisted kept it on a down member) but there's a chance a loop could occur;
when LB_SELECTED {
switch [LB::status] {
"session_disabled" -
"down" {
[LB::reselect]
return }
default { }
}
}
3) Configure the Pool Action on Service Down setting as Reject or Reselect. I'd prefer this over either iRule.