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, thanks again for time. I am still not sure if I got it right. According to SOL OC with only TCP profile should be able to do per request LB, without any iRules etc. But question is how messages can be recognized (HTTP requests) without HTTP profile.

There is as well statement in SOL:

The OneConnect profile may be used with any TCP protocol, but only when applied to virtual servers that process simple request/response protocols where transaction boundaries are explicitly obvious, such as those in which each request and each response is contained within a single packet.

So it seems like in this situation LTM can consider packet from client as equal to HTTP request and based on that per request LB is performed.

Still, according to your test it's not true - so info in SOL is not correct.

Then you state that with OC and TCP profiles and iRule this per request LB can be achieved by using iRule to detach server side connection - Am I right?

If so what could be an iRule that can do that? There is no HTTP profile so HTTP_RESPONSE or HTTP_REQUEST events can not be used. Is detaching possible using L4 events? Would appreciate a lot some guidance here.

Piotr