I administer 2 environments that have multiple PCS appliance in each. One has three and the other four.I've been observing the following message in abundance: Connection from IP XXX.XXX.XXX.XXX not authenticated yet (URL=/dana/js?prot=1&svc=4) Upon investigation, I've discovered that these are user sessions that have tried to continue on an appliance that the sesssion was not initiated on. This is because, for one reason or another, the user's source IP changed. Since I use source IP affinity persistence, the session is considered new on the load balancers and sent to the next available PCS. Has anyone else noticed this? If so, is there a better load balancing strategy than source IP persistence? I've looked at everything else but am very limited due to the IPSec traffic.
... View more
