I was looking at a config of a Cisco CSM that I am converting to F5 and see the good ‘ol ‘persistent rebalance’. This is essentially support for client persistence (client keep alive) via http 1.1 – is this supported natively on the LTM or do I need to create a specific persistence profile? I would think this would be something natively supported but I just want to make sure.
This also is a 'dummed down' feature of one connect, but I was wondering if anything else is necessary to honor the http 1.1 client keepalive. If there isn't a comparable feature for F5 I would gladly take any advice for an acceptable workaround. The F5 is terminating https as well as regular http.
Thanks a lot,
Based on a rough description of the feature on a blog (http://blog.super-networking.net/2006/07/cisco-csm-info/), I think the equivalent functionality on LTM is a OneConnect profile. If you're using SNAT you can use the default OneConnect profile with a 0.0.0.0 source mask. If you're not doing source address translation on connections to the pool, then it's best to create a custom OneConnect profile with a 255.255.255.255 source mask. This ensures the source IP the pool members sees matches with the client side TCP connection.
For details on OneConnect, see these pages:
SOL7208: Overview of the OneConnect profile
OneConnect wiki page
OneConnect? For my iRule? - Deb's article