RE: Concerns about changing TCP/IP keep alive time.

I can't give you any specific answers, but I can tell you that we had "some kind of problem" a while back and changed ours to 2. That was probably 3-4 years ago, and we haven't noticed any problems.

Completely different environment, hence the first part of my answer.
--
Sean Porterfield


-----Original Message-----
From: Rob Berendt
Sent: Thursday, February 23, 2012 14:04
To: midrange-l@xxxxxxxxxxxx
Subject: Concerns about changing TCP/IP keep alive time.

I recently got an update to a Domino ticket that went like this:
Looking at the current data from netstat the GDDATA system has 2872
sessions from LDAP in close2 status.
These are sessions that will Eventually close.

One thing we can do is drop the keep alive time.

This is the TCP parameter that limits how long a dead but not closed session will hold the socket open.
The default is 2 hours, We could cut that to 15 minutes and drop the
CLO2 session count ,
And I confirmed that he wants me to change from CHGTCPA TCPKEEPALV(255) to CHGTCPA TCPKEEPALV(15)

My dilemma is that I can't remember why I have it set to that on this one lpar and I am hoping that this change will not adversely affect ftp or anything. I am going to start documenting changes to system values and such. That being said, any concerns about this change?


Rob Berendt
--


This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.