How OneConnect Profile works with Cookie Persistence

Peter, in this article, OneConnect is enabled between BIG-IP1 <-> BIG-IP2 the whole time. Some of our customers do this to avoid opening too many TCP connections. With that in mind, in this particular test, client will be using the same TCP connection between BIG-IP1 <-> BIG-IP2. Now, the lab tests were performed when Cookie Persistence is enabled only on BIG-IP2 regardless. These things I mentioned were fixed in my configuration. Now, what I'm showing here is when we enable/disable OneConnect on BIG-IP 2. When we disable OneConnect on BIG-IP2, no other load balancing decision is taken and some of our customers created support ticket to complain that Cookie Persistence was not working on BIG-IP2 and that is not the case. Why? Because BIG-IP makes load balancing decision per TCP connection. Therefore, the solution would be to enable OneConnect which would ultimately allow BIG-IP to change its load balancing decision to be based on HTTP requests rather than TCP connection. So once a load balancing decision is taken, BIG-IP reads persistence records so Cookie Persistence works every time with OneConnect.