Question on using OneConnect (as referenced in contained article/link)

Good input guys.

 

 

I've had a chance to read the http://www.f5.com/pdf/deployment-guides/oneconnect-tuning-dg.pdf article. Nice.

 

1. Can someone explain where I'd set the "Pool Member Connection Limit" on a non-CMP device?

 

 

2. Also everytime I read the OneConnect article, F5 or someone else would keep mentioning client source IPs as if they get 'mingled' with OneConect on.

 

Eg. SOL 5911: "Note: Using a broad source mask may skew server-side statistical data. For example, when using the mask 0.0.0.0, request from multiple clients may appear as though they are originating from a single IP address." So what? Is that a hint for 'watchout? I've heard a case where the customer had different users seeing other users mailboxes randmly in exchange and I wonder if I'd have to question this? We are using OneConnect on Exchange VS as well.

 

 

3. I had this question at the back of my head as well about OneConnection with Load Balancing. And F5 is tracking the Least Connections option under CR120223 - what about other algorithms though (either way one connection would send request to same member!!!). I for one thought the loadbalancing algorithm is somehow ignored with OneConnect on for existing server-side connections. Deb Allen mentioned that load balancing is done at connection level not request level????? Again I must admit that F5 mention that (SOL 7208) "Because the OneConnect profile re-uses idle connections, it may appear that the BIG-IP system is not load balancing traffic evenly across pool members."

 

 

Above all I think the OneConnect is such a feature. I still need to fgure out where to intercept for connections that I want to reset etc. There is LB::detach, OneConnect::enable & OneConnect::detach.

 

Awesome.

 

Maybe I should take some time off networking to delve in Applications related staff a bit. HTTP::Header etal is the new lingo!!