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
FrojasHi, sorry for the late answer.
There will be two one connect profile, one for SNAT (/24) and other without SNAT (/32), in one http request there are multiple connections, thats why we need to use oneconnect.
In fact, we migrate a couple of vserver from Cisco CSM with persistence-rebalance to our F5 without oneconnect profile, and the connections were four times higher.
i was testing with a vserver, and with oneconnect profile and no persistence profile, i always get a 402 answer from my http server, but if i add a persistence profile like source address, works fine, but i cant use source address because there will be a lot of connection using only one server for forever, with cookie persistence its kinda weird the behavior, but there is a KB where indicates that we have to use an irule to solve this (an ugly solution i think).
Checking the configuration in the cisco CSM, i was looking for persistence profiles or something like that, but only use "persistence-rebalance" no source address, or cookie or something.
im going to continue with the lab and see if something is missing.
Thanks! Felipe.
- Leonardo_Souza3
"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.
- Frojas
Yes, i think im going to apply oneconnect with cookie persistence, and the irule.
But im going to open a SR because in the CSM the only option in the virtual server is use persistence-rebalance, and works, in my f5 if i use oneconnect only i got an 402 answer.
Best Regards, Felipe.
- Leonardo_Souza3
Ok, but just to clarify, you need oneconnect or the iRule, not both.
