Forum Discussion

netfortius's avatar
netfortius
Icon for Nimbostratus rankNimbostratus
Jun 18, 2015

Oneconnect and http profile - why recommended, and not mandated?

I was reading sol7208: Overview of the OneConnect profile in an attempt to understand an odd behavior of an F5 config: with a specific version of OS and application, the oneconnect WITHOUT http profile works fine, while with an upgraded OS and app the oneconnect WITHOUT an http profile breaks functionality.

 

My Qs:

 

  1. Under which conditions an http profile SHOULD not be used with oneconnect?

     

  2. If no such @1, why isn't the usage of http profile alongside oneconnect mandated, instead of just recommended?

     

TIA

 

application delivery
deployment
http profile
LTM
oneconnect
  • Ed_Summers's avatar
    Ed_Summers
    Icon for Nimbostratus rankNimbostratus
    Jun 18, 2015

    The same SOL alludes to one reason. OneConnect can be used for protocols other than HTTP. However there are some guidelines on protocol behavior that would not be suitable for OneConnect, which are listed in the SOL. Examples are listed in the 'Recommendations' section of the SOL.

     

    So the 'http' profile should only be used if the traffic handled by the virtual is http traffic. OneConnect could be used for other (non-http) protocols to load balance separate requests inside the same TCP connection, instead of load balancing the TCP connection itself (i.e. all requests in the connection will go to the same pool member).