Forum Discussion

smeunier_318004's avatar
smeunier_318004
Icon for Nimbostratus rankNimbostratus
Jul 06, 2018

How to refresh configuration changes

Can some tell me, when you make a change to TCP protocol (in my case IDLE TIMEOUT and Keep Alive Interval) when those new values take affect after I click the update button? Is it dynamic and any new connection would then connect with the new rules, or do i need to take the resource out of the pool and then put it back in for the new setting to take affect?

 

I'm trying to adjust settings so long lived connections do not timeout, but I don't seem to see a difference if I increase the idle timeout to one minute longer than the default. This tells me my changes are not taking affect. Currently the defaults are in place (300/1800). I have a client that times out at 5 minutes, which makes sense with the 300 Idle timeout default. But if I change it to 360 it should timeout at 6 minutes. But it stays at 5 minute time out? My F5 Admin, doesn't seem to know the answer to this?!

 

application delivery
BIG-IP
inactivity_timeout
mq
  • boneyard's avatar
    boneyard
    Icon for MVP rankMVP
    Jul 07, 2018

    Is it dynamic and any new connection would then connect with the new rules

    that is how i always understood it indeed. existing sessions aren't touched, new ones are.

    how do you determine it didn't work? the difference between 300 and 360 isn't that extreme, have you checked the session table and are sure you are looking at new sessions?