Forum Discussion

yuanqiang_22112's avatar
yuanqiang_22112
Icon for Nimbostratus rankNimbostratus
Dec 06, 2016

tcp connection Idle Timeout

Vs with fastL4 protocol profile ,fastL4 Idle Timeout 300; tmsh : show sys connection cs-server-addr 3.10.10.40 ,print :3.20.10.131:47179 3.10.10.40:4451 3.10.10.244:47179 3.10.10.42:4451 tcp 57650 (slot/tmm: 1/0) ; client no flow generated and Wait for 5 minutes ,show connection cs-server-addr 3.10.10.40 ,still print 3.20.10.131:47179 3.10.10.40:4451 3.10.10.244:47179 3.10.10.42:4451 tcp ; I don't understand to be so ,I think if client no flow generated and the time to be Idle Timeout ,tmsh show connection should no value output .please help give your idea .

 

5 Replies

  • There used to be some bugs regarding idle timeout with PVA accelerated connections. One that I am aware of is known issu 597089-8: Connections are terminated after 5 seconds when using ePVA full acceleration. This does not fit the problem you are experincing, but it might be a hint... Can you try setting the PVA acceleration in the fastL4 profile to none (create a new one) and see if the problem persists? If not, it is most probably PVA-related (I don't trust that thing anymore).

     

  • persistence : when a client open a new connection, there is an entry to be sure to go everytime on the same backend server tcp idle time-out : if your client not send any tcp packet during this time, the tcp connection is closed.

     

    you can have a persistence entry with no tcp connection !

     

    it's ok for you ?

     

  • I think yuanqiang is aware what persistence means, but this issue has got nothing to do with persistence at all...