Lloyd_Bare
Nov 02, 2016Nimbostratus
Persistence Question
We have just migrated from Cisco's ACE to F5's LTM platform.
We have a VIP that is primarily hit by two different Source IP's. I need persistence and ideally want to spread the load. On ACE we used a hash of the source address; and one of the source IP's was always sent to Pool Member A (assuming its up) and the other IP always was sent Pool Member B.
On F5 LTM we have tried source address affinity; and tried swapping between CARP and Default hashing algorithms; but all traffic goes to the same Pool Member. Anyone know a way to tweak these so that the hash may result differently between the two sources?