Forum Discussion
NimbostratusPersistence rebalance on F5
NimbostratusI did a quick research about the Cisco option , and it does look similar to oneconnect. However, I don't know enough about Cisco CSM to confirm that works the same way as F5 oneconnect.
With the mask of 255.255.255.255, only the same IP will reuse the connection. So, that is almost the same as not use oneconnect, in relation to what the server sees and the number of open connections.
Have you tried without oneconnect?
In case you have not read yet, he is the oneconnect overview solution:
https://support.f5.com/csp/article/K7208
Nimbostratus"in one http request there are multiple connections, thats why we need to use oneconnect."
It is the other way around, multiple HTTP requests in the same connection.
Here is the solution you were talking about in relation to cookie persistence:
https://support.f5.com/csp/article/K7964
As described in the solution, one option is to use oneconnect and another option is to use LB::detach.
The oneconnect provides 2 important functions, first make sure every HTTP request triggers a new load balance decision. Second, reuse the server side connection.
Persistence, on the other hand, is to make sure there is no new load balancing decision when you come back, so you go to the same server.
Based on what you said, I guess oneconnect with cookie persistence looks to be a good option for your case.
