HI F5 Warriors
I have a trouble from my costumer.Which in his server on the server he experiences very different traffic differences between their servers and in the F5 settings he has used the Round Robin method, but in the Persistance Source Address Affiliance profile, so how can the server be able to distribute traffic to the server evenly, due to info from the customer for the apps need persistence profile
Thanks for your help!!!
17-Apr-2023 01:12 - edited 17-Apr-2023 01:14
When the client connection is accepted, persistence entry have priority over the Load Balancing method.
So if an entry exists in the persistence table, F5 will send traffic to the real server that was bound with that entry.
This might lead to uneven traffic distribution, expecially if your clients are behind NAT, but it's the intended behavior.
To even out resource usage on your server farrm you might want to consider different load balancing methods instead of Round Robin, and use something dynamic instead. For example, F5 provides out-of-the-box connection-based or persistence-entry-based dynamic load distribution.
https://my.f5.com/manage/s/article/K42275060 details this further
Thanks for the answer
but which dynamic load balancing method is better to use for these conditions? because as you said that persistence has a higher entry value
Do you have the possibility to try them out in a test plant before installing? Every environment is different from another and different method might perform better in some cases and worse in others.
Least Connections (node based) can be a "safe bet" if server farm is omogeneous and the goal is to even out traffic load.
I wouldn't go for session-based in this case since as I said sourceIP persistence doesn't really like NATs.
Is this an HTTP-based application? If so, and you are able to offload SSL to the VIP, try using cookie persistence instead of source IP persistence.
With source IP persistence, if clients are traversing a forward proxy or have their source IP PAT'd to a single IP address, this may cause very uneven load distribution between the back-end servers. Coookie persistence doesn't have this problem as it doesn't use the source IP of the client.