Persistence and limited sources issue
1.1.1.1 & 1.1.1.2 are two main sources + A few tester machine IPs VIP is 2.2.2.2 Pool members are 3.3.3.1 & 3.3.3.2 - Round Robin + Source Address Persistence When pool members are recycled / rebooted, traffic sticks to single node. Clearing persistence record for the VIP fixes the issue, but any 2020 solution ?276Views0likes2Comments