NimbostratusHi,
we are having two servers in the pool with persistence enabled (cookie as default and src_addr as fall back). we are using least connections node as load balancing method for this pool. I am seeing one of the server is receiving twice the traffic as other from past two months. Please help me in determining the reason why we have unbalanced servers.
Thanks,
Sekhar
Hi,
You must check both Cookie and Source Address persistence profiles. Please check also in Statistics ›› Module Statistics : Local Traffic ›› Persistence Records if you have any persistence record and adjust your source address affinity profile accordingly (This indicates that the primary Cookie Persistent may be not working all the time). Also, you can try changing you load balancing method to least connections (member).
CirrostratusHI
as you are using source address as fallback the LTm keeps in his memory the peristence details . which will be used if client does not send any cookie in the request .
Please check if cookie persistence is working .
NimbostratusCirrostratusHi Sekhar ,
If this browser based application the you can cehck in developer tool in IE and see if the response has Cookie set in it .
THanks
NimbostratusNimbostratusHi,
To troubleshoot this, try to disable the fallback persistence clear the statistics and check again your pool statistics. Probably the pool is using most of the time the source address persistence instead of cookie persistence. That's why you can experiment unequal load balancing. Can you post the cookie profile configuration?
Hi,
That's the default cookie persistence profile. Did you try to disable source address persistence as a fallback persistence and left only cookie as a Default Persistence?
When you use Source Address Affinity as a fallback persistence method, is not uncommon that appears that the BIG-IP system incorrectly distributes more requests to a particular server. The BIG-IP system uses the fallback persistence method when it cannot use the specified primary persistence profile. In this case, cookie persistence is configured with source address affinity as a fallback, but if a client does not send a persistence cookie, the fallback persistence method is used instead.
Remember that when a cookie persistence profile is configured for a virtual server, the BIG-IP system does not store the session data locally in the persistence table; the BIG-IP system stores the session data in the cookie.
