Information
This article describes how to base User portal affinity on a cookie instead of using source addressing.
Configuration
Detailed setup for HAProxy described here: load balancing, affinity, persistence, sticky sessions: what you need to know
Examine the Using application session cookie for persistence section from the article above for details related to session affinity based on cookie.
The User portal uses a cookie with ID ASP.NET_SessionId
cookie ASP.NET_SessionId prefix no-cache
The load balancer must act in round-robin mode
balance round-robin
Assuming that the IP addresses of the RAS Gateways are 10.125.1.10 and 10.125.1.20 respectively, The final configuration should be as follows:
frontend ft_web
bind 0.0.0.0:443
default_backend bk_web
backend bk_web
balance roundrobin
cookie ASP.NET_SessionId prefix nocache
server s1 10.125.1.10:443 check cookie s1
server s2 10.125.1.20:443 check cookie s2
bind 0.0.0.0:443
default_backend bk_web
backend bk_web
balance roundrobin
cookie ASP.NET_SessionId prefix nocache
server s1 10.125.1.10:443 check cookie s1
server s2 10.125.1.20:443 check cookie s2
NOTE: Please contact your load balancing solution vendor for detailed configuration.
Was this article helpful?
Tell us how we can improve it.