Forum Discussion
NimbostratusFrom a given source IP address, What conditions other than the persistence timeout expiring can cause the F5 to rebalance traffic?
When Source Address Affinity persistence is used, What conditions other than the persistence timeout expiring can cause the F5 to rebalance traffic from a given source IP address?
A failed health check on the pool member associated with a particular source IP address would cause the F5 to rebalance the session to another pool member. What other conditions (other than persistence timeout) might cause the F5 to rebalance traffic from a given source IP address to another pool member?
4 Replies
- irule command perhaps. Or a local traffic policy action that sends the traffic to a different pool. What exactly are you trying to troubleshoot? Might be easier to help with that. I can't think of any other condition off the top of my head.
Vee_142890Other conditions like : Match Across Services Match Across Virtual Servers Match Across Pools Hash Algorithm Override Connection Limit If any of the above mentioned are enabled in addition to Persistence Timeout, will that cause F5 to rebalance traffic ?- James_Thomson
Employee
Match across settings won't cause rebalance. not sure about connection limits though.
Amine_KadimiMVP
In addition to the member marked down by a monitor, another condition that will cause F5 to rebalance is a failover event when you have an HA pair and you are not mirroring persistence.
