A issue about session persistence

huzhiqi · June 2021

Clients access the VIP by SSL VPN,all the client's ip was NAT to sslvpn ip-10.182.21.141,so the A10 load balalncing the request to single real server and port,the A10 use source ip persistence method.

At the end,all other real server has no http request,all requst go to the same one real server-10.182.43.171:9002.

so how fix this issue?

mdunn · June 2021

A few thoughts come to mind:

Within the source-ip persistence template, you can enable "incl-sport" to include the source-port in the persistence evaluation.

If this is HTTP traffic, you could Cookie persistence template

If this is HTTPS, you could use SSL Session ID persistence template

Would any of those be viable?

A issue about session persistence

Comments