default TCP profile - idle timeout vs keepalive

Short answer, it doesnt. But if you set the keepalive less than the idle timeout it would be able to.

 

 

H

Right, so why the bizarre defaults?? if that's the intended behavior, then the keepalive should be set to zero surely? It's pretty misleading I think, as I would think users are given to believe they must be *good* defaults...

The only thing I can think of is maybe the default is set so that keepalives will only be used if the idle timeout is increased past 1800 seconds.

 

 

You could open a case with F5 Support to clarify the logic and/or request a change to the default value.

 

 

Aaron

Can we configure TCP profile timeout 14400sec. user said to configure it. i am not sure whther LB will support or not.

 

 

Please help me

Can we configure TCP profile timeout 14400sec. user said to configure it. i am not sure whther LB will support or not.do you mean tcp idle timeout?

[root@ve10:Active] config  b profile tcp test idle timeout 14400
[root@ve10:Active] config  b profile test list
profile tcp test {
   idle timeout 14400
}

I have configured like this. but it is not working. can any one please suggest me on this.

 

 

b profile tcp tcp_240min {'

 

defaults from tcp

 

idle timeout 14400

 

'}

 

but it is not working. what is not working?? what does it mean??

It is logging us out prematurely instead of keeping the session open.

It is logging us out prematurely instead of keeping the session open.

 

It is logging us out prematurely instead of keeping the session open.you do see tcp reset being sent from bigip to both client and server, don't you?