tcp_keepalive

[Raj123_bang]

What are the optimal values of tcp_keepalive and tcp_abort parameters for better performance?

[Mridul Shrivastava]

tcp_keepalive_interval:

Interval for sending keep-alive probes.

If any activity has occurred on the connection or if there is
any unacknowledged data when the time-out period expires, the
timer is simply restarted. If the remote system has crashed
and rebooted, it will presumably know nothing about this
connection, and it will issue an RST in response to the ACK.
Receipt of the RST will terminate the connection.

If the keepalive packet is not ACK'd by the remote TCP, the normal
retransmission time-out will eventually exceed threshold R2,
and the connection will be terminated.

With this keepalive behavior, a connection can time-out and
terminate without actually receiving an RST from the remote TCP.
[10000, 10*24*3600000] Default: 2 * 3600000 (2 hours)


tcp_ip_abort_interval:

Second threshold timer for established connections.

When it must retransmit packets because a timer has expired,
TCP first compares the total time it has waited against two
thresholds, as described in RFC 1122, 4.2.3.5. If it has waited
longer than the second threshold, TCP terminates the connection.
[500,-] Default: 600000 (10 minutes)

[RAC_1]

Which version of OS? There are few ndd settings invloved. I can see following. Which one you are talking about. also before you do any changes, read carefully what it will result into.
tcp_ip_abort_cinterval - R2 during connection establishment
tcp_ip_abort_interval - R2 for established connection
tcp_keepalive_interval - Interval for sending keepalive probes
tcp_keepalive_detached_interval - Send keepalive probes for detached TCP

ndd -h tcp_keepalive_interval