Resetting F5 Persistence once one of the pool member restarts

Hi All,

We are using Source address affinity on F5 device which distributes load across 2 backend servers. If one of the server stops, then all the traffic is sent to Server 1. As we use source affinity, even after server 1 comes back up, load balance is off.

We cleaned up the persistence records on the Virtual Server, but still the load balancing is off?

To cover this scenerio, are we better off with other persistence profiles or should we able to start with clean slate of persistence records once one of the pool member restarts?

Thank you for your time on this

Ravi