LB persistence in source-ip template VS. method in service-group
Can anyone tell me the difference between enabling persistence in a source-ip persist template applied to a virtual server vs. enabling the src-ip-only-hash method in a service-group? Both seem to say the same thing and if so which would take precedence? (if the other were configured otherwise)
slb template persist source-ip persist-service slb virtual-server some-udp-service-vip x.x.x.x port 999 udp service-group 999-group template persist source-ip persist-service slb service-group 999-group udp method src-ip-only-hash
If the goal is to make all client requests stick to the same back end server (perpetually even after session ages out, assuming it's available) which of the above would do this? Said another way, which of these are enabling the desired effect or take precedence?
The docs state template persistence selection of "the same server resources" whereas the service-group method type dictates "connecting session data flow to the back end server". Virtually the same language from my standpoint.
Thoughts anyone? Thank you.