F5 AppWorld 2024 session proposal deadline extended to Friday, December 8th!
22.214.171.124 & 126.96.36.199 are two main sources + A few tester machine IPs
VIP is 188.8.131.52
Pool members are 184.108.40.206 & 220.127.116.11 - 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 ?
This is known behaviour in persistence. I will suggest you to reduce source persistence ideal time value.. this may help you..
If it's http based traffic you can try using cookie persistence. You'll need to have an http profile on the virtual server.
If traffic is not session based, you might try taking out persistence all together.
If neither of those are possible, then you might try reducing the persistence timeout to a value just above the application's session timeout.
Hope that helps.
or learn more...