- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Changing tcp_time_wait_interval ndd parameter
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 07:22 AM
тАО01-08-2010 07:22 AM
Changing tcp_time_wait_interval ndd parameter
Hello All,
Our application vendor suggested to change tcp_time_wait_interval parameter from 30sec (current value) to 70sec. They have made this suggestion to reduce the network traffic.
Can any one tell me is there any other ndd parameter need to be looked?
Thanks,
Manoj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 07:50 AM
тАО01-08-2010 07:50 AM
Re: Changing tcp_time_wait_interval ndd parameter
The utility as root to do this is ndd
It has an interface for you to see options and such.
Permanent boot changes are done at /etc/rc.config.d/nddconf
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 08:05 AM
тАО01-08-2010 08:05 AM
Re: Changing tcp_time_wait_interval ndd parameter
Hello Steven,
Thanks for the information.
Actually I am looking for whether any other ndd parameters are dependant to tcp_time_wait_interval.
Regards,
Manoj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 12:14 PM
тАО01-08-2010 12:14 PM
Re: Changing tcp_time_wait_interval ndd parameter
ftp://ftp.cup.hp.com/dist/networking/briefs/annotated_ndd.txt
For example:
----
tcp_time_wait_interval:
Amount of time TCP endpoints persist in TCPS_TIME_WAIT state.
[1000,600000] Default: 60000 (60 seconds)
The TIME_WAIT interval is an integral part of TCP's correctness algorithms. TCP connections are "named" (uniquely identified) by the four-tuple of local and remote IP address, and local and remote TCP
port number. There is no concept of "this is the N'th connection by this name." So to prevent TCP segments from an old connection being accepted on a new connection, TCP uses the TIME_WAIT state. This preserves TCP information long enough to be statistically certain that all the segments of the old TCP connection by that name are gone.
The HP-UX TCP stack can track literally millions of TIME_WAIT connections with no particular decrease in performance and only a
slight cost in terms of memory. So, it should almost never be the case that you need to decrease this value from its default of 60 seconds.
----
So, tcp_time_wait_interval does not seem (at least, not directly) related to reducing/increasing network traffic. *Restoring* the setting to the *standard* value of 60 s should be harmless anyway.
The application can modify the behavior of the sockets it uses quite a lot by setting the appropriate socket options.
If the application is "biting off more than it can chew", i.e. accepting more incoming connections than it can really handle with an acceptable level of performance, that is completely fixable within the application: there is no need to fiddle with the OS-level settings.
MK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2010 04:10 PM
тАО01-08-2010 04:10 PM
Re: Changing tcp_time_wait_interval ndd parameter
The *only* way it could would be if the attempted TCP connection rate involving your system would lead to TCP connection name reuse (local/remote ip, local/remote port) within 70 seconds that wasn't happening at 30 seconds.
If that is the case, it means you will see lower performance.
That your application vendor is suggesting this suggests to me that there is some non-trivial confustion somewhere, or the application from the vendor is quite profligate in its (ab)use of TCP connections. Neither of which is all that encouraging frankly. I would suggest you ask the application vendor to be extremely specific as to why they think changing tcp_time_wait_interval will reduce network traffic - and for that matter why network traffic needs to be reduced.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-11-2010 04:29 AM
тАО01-11-2010 04:29 AM
Re: Changing tcp_time_wait_interval ndd parameter
no ndd parameter will permit to limit the network traffic.
so you'd better tell your real need.