Forum Discussion
Cirruswhich Persistence to use when F5 works in SSL Bridging mode and traffic is natted at core.
My deployment is like this
Client-->https-->F5-->https-->server (F5 is in bridge mode not pass through)
I can not use source ip persistence as frenchise users will be natted at core. Can i use cookie persistence and which cookie persistence? will it work in my senario? as i tried it and it was not working for some reason.
8 Replies
Brad_Parker_139Nacreous
Are you terminating SSL with a client-ssl profile then re-encrypting with a server-ssl profile? If you do that you should be able to use an HTTP profile and cookie persistence. The default "insert cookie" method is the easiest cookie method to use and should work just fine for you. Remember you can't use cookie persistence without an HTTP profile. I would also highly recommend using a OneConnect profile with cookie persistence or else you run the risk on not load balancing all requests to the same server.
Muhammad_Irfan1yes i am terminating and re-encrypting SSL. Some how cookie persistence was not working today, will test tomorrow again.
natheCirrocumulus
I agree with all brad says. Further, if cookie persistence seems not to work then a tool like fiddler/http watch/http fox should help troubleshoot. You should see a BIGIPxxxxx cookie in the http requests. Xxxxx will be specific to a pool member- Brad_Parker_139Any luck?
Brad_ParkerAre you terminating SSL with a client-ssl profile then re-encrypting with a server-ssl profile? If you do that you should be able to use an HTTP profile and cookie persistence. The default "insert cookie" method is the easiest cookie method to use and should work just fine for you. Remember you can't use cookie persistence without an HTTP profile. I would also highly recommend using a OneConnect profile with cookie persistence or else you run the risk on not load balancing all requests to the same server.
- Muhammad_Irfan1yes i am terminating and re-encrypting SSL. Some how cookie persistence was not working today, will test tomorrow again.
- natheI agree with all brad says. Further, if cookie persistence seems not to work then a tool like fiddler/http watch/http fox should help troubleshoot. You should see a BIGIPxxxxx cookie in the http requests. Xxxxx will be specific to a pool member
- Brad_ParkerAny luck?
