For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Lloyd_Bare's avatar
Lloyd_Bare
Icon for Nimbostratus rankNimbostratus
Nov 02, 2016

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...
application delivery
LTM
keshav_163381's avatar
keshav_163381
Icon for Nimbostratus rankNimbostratus
Nov 03, 2016

You can create a custom persistence profile and change the mask settings under the custom settings and configured a 255.255.255.255 which will solve your problem :)

 

Lloyd_Bare's avatar
Lloyd_Bare
Icon for Nimbostratus rankNimbostratus
Nov 04, 2016

I'm still having issues using the methods shared by the group here. In ACE I was able to use load balancing predictor of "hash of source address"; which isn't necessarily a persistence method; but accomplishes that natively. I've not been able to find a way to do this on the F5 because the initial request is going to use the Pool Load Balancing algorithm that is set (Predictive (Node)); and then make a persistence record based on source address for example. I'm still getting all the requests hitting the same server. Maybe I need to change to round robin?