Forum Discussion

Piotr_Lewandows's avatar
Piotr_Lewandows
Icon for Altostratus rankAltostratus
Apr 21, 2015

OneConnect, no HTTP profile, still per HTTP request LB?

Hi, My understanding was that one of the functions of service or protocol profiles is to allow LTM to decode, understand and manipulate protocol data at given layer. In Overview of the OneConnect p...
application delivery
design
LTM
performance
TMOS
dragonflymr's avatar
dragonflymr
Icon for Cirrostratus rankCirrostratus
Apr 21, 2015

@nitass, one last question. Just would like to be sure if I understand why OC is crucial for LDAP example.

 

My understanding of TCP connection setup is:

 

  • Without OC
  • client initiates connection
  • 3WH is performed with LTM
  • client sends first data packet
  • LTM performs 3WH with server
  • then data is flowing
  • client initiates connection tear down with LTM, client side connection closed
  • LTM initiates tear down with server, connection closed (or maybe LTM passes tear down to server?)
  • With OC
  • as above up to client initiated tear down
  • Client connection is closed but server side connection is maintained for reuse and marked idle
  • Server side connection is kept open until Idle Timeout on LTM or server expires (or one of the thresholds set in OC config is met)

So the point here is that OC is not passing client side tear down to server side and new packets can be send via this SS connection. I assume that for other protocols than HTTP (where one of the requirement is server support for keep-alive) preservation of SS connection is basically based on Idle Timeout setting for TCP? Or some special support on the side of application (like LDAP server) is required?

 

Piotr