- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
10-17-2025 02:19 AM
The customer is experiencing issues with their PSM Load-Balancing Configuration, resulting in one of the PSM servers being overloaded with excessive connections.
They have confirmed the Load Balancer configuration was changed from Least Connection to Round Robin and are now monitoring how the load is distributed across the PSM servers.
Is it recommended to continue using Round Robin instead of switching back to Least Connection?
10-17-2025 02:22 AM
CyberArk always recommend
"Set load balancing method to least connections so the load, on average, is balanced equally between the nodes within the PSM pool."
You need to investigate why the lb is sending so much traffic to one server as it doesn't seem to be distributing it properly, so check the health monitors and rules are fine etc
10-17-2025 03:11 AM
One issue that comes up a lot in this context is the persistency method configured on the loadbalancer - meaning, how does the loadbalancer know that an incoming packet belongs to an existing session. On F5 BIG-IP I believe the default method uses the Source IP only (or a combination of Source IP and Destination IP), which means that if one person opens 100 PSM sessions, they will all be routed to the same PSM.
10-17-2025 03:49 AM
Hi @Joyce Ebrado
It’s a perfect scenario which confirms why round robin is not the recommended load balancing method for PSM.
The solution is to use least connection.
10-17-2025 02:46 PM
Hi @Joyce Ebrado
There are certain challenges using round robin for PSM load balancing.
Maybe consider checking if persistency is configured correctly and also check how the server pool is configured.
Refer below links:
Hope this helps
10-19-2025 08:18 PM
for the Load Balancing Method, should it be Least Connection (node) or Least Connection (member)?
10-19-2025 08:44 PM
Hi @Joyce Ebrado the Load Balancing method should be Least Connection (member). Please refer the below link for Load Balancer setup:
https://docs.cyberark.com/pam-self-hosted/latest/en/content/psm/exampleloadbalancer.htm
specifically refer section to create server pool here:
https://docs.cyberark.com/pam-self-hosted/latest/en/content/psm/exampleloadbalancer.htm#
Hope this helps.
10-19-2025 11:47 PM
We observed this for customer when they have LB in place and load balancing PVWA, PSM, HTML5 Gateway components. They were also complaining about incorrect load distribution of F5 load balancer. I think the load balancing using html5 gateway can direct most connections to 1 psm since the source ip is html5 gateway ip address. Any idea how to deal with this? @Malcolm Murray @Malhar Vora
10-20-2025 01:37 AM
Hi,
for HTML5 gateway you must set "session cookie" on the load balancer, instead of source IP.
The load balancer must also know the certificate of the gateway so it can decrypt/recrypt the session during the process.
Regards,
10-20-2025 03:46 AM
Hi @Madat Yuzbashli
Please disable or not use source IP persistence on the F5 LB that handles traffic for the PSM pool (TCP/3389) because it directly causes the session stacking issue when the HTML5 Gateway is the source.
10-20-2025 03:55 AM
thanks for ideas @Nicolas Louis @Malhar Vora !
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

