Forum Discussion

Robert_47833's avatar
Robert_47833
Icon for Altostratus rankAltostratus
Apr 20, 2015

connection behavior with or without oneconnect

hi ,dear Irule according to test in lba,here is what I found for connection behavior with/without oneconnect all tests have http profile enabled,and source

 

1:without oneconnect profile after client----vs,vs---backend server connection established,after keep alive timeout is met,backend "fin ack" connection with F5,then VS "fin ack " with client.

 

2:with oneconnect profile after client----vs,vs---backend server connection established,after keep alive timeout is met,backend "fin ack" connection with F5,but VS doesn't send "fin ack " with client.

 

3:it seems client ,such as IE chrome doesn't hornor keep-alive:timeout in response from backend server even ,after the timeout value,it can still reuse the client side keep alive connection

 

10 Replies

  • What is your question? You can read about configuring Oneconnect here: https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html

     

    • Robert_47833's avatar
      Robert_47833
      Icon for Altostratus rankAltostratus
      I want to confirm whether my words matches the expected behavior?
    • Hannes_Rapp_162's avatar
      Hannes_Rapp_162
      Icon for Nacreous rankNacreous
      1) yes 2) yes 3) yes. The keep-alive setting as set in a clientside profile supersedes server responses.
  • What is your question? You can read about configuring Oneconnect here: https://support.f5.com/kb/en-us/solutions/public/7000/200/sol7208.html

     

    • Robert_47833's avatar
      Robert_47833
      Icon for Altostratus rankAltostratus
      I want to confirm whether my words matches the expected behavior?
    • Hannes_Rapp's avatar
      Hannes_Rapp
      Icon for Nimbostratus rankNimbostratus
      1) yes 2) yes 3) yes. The keep-alive setting as set in a clientside profile supersedes server responses.
  • Just wonder do you mean Keep Alive Interval or Idle Timeout from TCP profile? I guess that for server side connections with OneConnect applied what is used to end connection are settings from OneConnect profile (Maximum Age, Maximum Reuse) not from TCP profile - but may be wrong, I am not really sure what Idle Timeout Override (in OneConnect) setting is changing in this equation. Or maybe it's like that: 1. Maximum Age (OC profile) specifies how long server side connection can be used, after specified number of seconds connection is closed if it's Idle Timeout in TCP profile was not exceeded 2. If Maximum Age did not pass but Idle Timeout in TCP connection expired then server connection is closed not honoring Maximum Age setting 3. When it's necessary to have different Idle Timeout for server side (using OC) for setting in TCP profile (and used in this case for client side connections) then it can be changed using Idle Timeout Override in OC profile Is above makes sense? Piotr
  • thanks for your reply I want to know the keep alive:timeout sent from backend server and its related behavior