uneven load balance issue, want to try persist source port on particular server

Hi!

There's no need to write a rule to persist on source port as the F5 device would do that automatically by default if no persistence profile has been added.

Reason being that no member switch would be done in mid-session (unless you're using re-select as Action On Service Down, which requires does not work unless in special scenarios). Even if you did persist on source port there would be a new source port for each new TCP session, so essentially you'd accomplish nothing.

My suggestion would be to disable persistence for the virtual server entirely, or specifically for the airwatch servers. Not sure if you'd gain much by doing so though unless they open up multiple connections per server?

/Patrik