Forum Discussion

Sylvain_Goulmy's avatar
Sylvain_Goulmy
Icon for Altostratus rankAltostratus
Apr 18, 2018

OneConnect always close server sessions

Hi all,

I'm noticing that on my one-connect profile i have strange Current Idle and Maximum values for :

--------------------------------------
Ltm::OneConnect Profile: my_oneconnect
--------------------------------------
Virtual Server Name    N/A

Connections
  Current Idle        4.2G
  Maximum             4.2G
  Total Reuses        4.9M
  New                16.5M

When i reset those statistics i have then the following display :

--------------------------------------
Ltm::OneConnect Profile: my_oneconnect
--------------------------------------
Virtual Server Name    N/A

Connections
  Current Idle        4.2G
  Maximum             4.2G
  Total Reuses        0
  New                 0

Moreover a network capture shows that servers connections are closed immediately by the F5, after receiving the HTTP response.

Here is the one-connect profile used :

ltm profile one-connect my_oneconnect {
    app-service none
    defaults-from /Common/oneconnect
    description none
    idle-timeout-override disabled
    limit-type none
    max-age 86400
    max-reuse 100000
    max-size 10000
    partition my_partition
    share-pools enabled
    source-mask any
}

Do have already noticed such values/behaviour ?

Thanks in advance for your feedback.

PS : F5 Firmware version 12.1.3

2 Replies

  • Hello,

     

    Did you find a solution to your problem?

     

    I am currently experiencing a simliar problem in that new connections are always created, connections are not kept open.

     

  • Surgeon's avatar
    Surgeon
    Ret. Employee

    In order for OneConnect work properly you need to meet next requirements

     

    1) HTTP traffic. You still can uses for non-http traffic but it is highly not recommended

     

    2) HTTP profile applied to the VIP

     

    3) HTTP server need to support HTTP pipelining

     

    4) HTTP server need to support keep-alive

     

    Also check the packet capture. If the back-end server sends FIN than big-ip will close the connection.