In this episode of Lightboard Lessons, Jason covers the basics of OneConnect, F5's connection pooling technology. Details: community.f5.com/articles/lightboard-lessons-oneconnect-30138
Пікірлер: 8
@dronomads6 жыл бұрын
Thanks Jason for this article I was wondering when this session will come as I posted in community also .. Nicely explained
@mmm7637 ай бұрын
What if server closes the connection?.....will one connect still maintain the connection as idle in f5?
@naveenshanmugam61894 жыл бұрын
Please guide Source NAT , Destination NAT and Auto NAT Why it is required and how it works
@hummer-k1k4 жыл бұрын
Great explanation
@100mexiko5 жыл бұрын
Json, we are using one-connect with a snat pool of 3 IPs. How many requests each IP can handle per second? Sorry if my question is confusing.
@jobshu3746 жыл бұрын
You should very be care for using HTTP profile with OneConnect profile together when you apply this feature on http traffic. It is a requirement, but not a recommendation or suggestion. Without HTTP profile, you will not be able to perform oneconnect translations and the TMM may reply server response to incorrect client if the original client close connection by sending FIN.
@JasonRahm6 жыл бұрын
I'm not sure I understand your point here, but to clarify, OneConnect requires TCP and to functional properly, a layer 7 transactional protocol like HTTP. But HTTP profile does not require a OneConnect profile, that decision depends on the type of traffic.