HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: nettune ndd parameter equivalency
Operating System - HP-UX
1838250
Members
4321
Online
110125
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
04-03-2001 10:27 AM
04-03-2001 10:27 AM
nettune ndd parameter equivalency
hi all
I need to know the equivalent ndd parameters for the 3 nettune tcp parms: tcp_keepstart, tcp_keepstop, tcp_keepfreq
thanks for your help
I need to know the equivalent ndd parameters for the 3 nettune tcp parms: tcp_keepstart, tcp_keepstop, tcp_keepfreq
thanks for your help
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2001 10:45 AM
04-03-2001 10:45 AM
Re: nettune ndd parameter equivalency
Hi:
You should look at document #S1100002433B.
This defines the keepalive timers in 10.20 and 11.0. There is no 'tcp_keepfreq' equivalent in 11.x. Otherwise:
# tcp_keepalive_interval = tcp_keepstart
# tcp_ip_abort_interval = tcp_keepstop
...JRF...
You should look at document #S1100002433B.
This defines the keepalive timers in 10.20 and 11.0. There is no 'tcp_keepfreq' equivalent in 11.x. Otherwise:
# tcp_keepalive_interval = tcp_keepstart
# tcp_ip_abort_interval = tcp_keepstop
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-04-2001 09:51 AM
04-04-2001 09:51 AM
Re: nettune ndd parameter equivalency
You might find the briefs at:
ftp://ftp.cup.hp.com/dist/networking/briefs/
useful.
There are now two keepalive parms in 11.X - one is tcp_keepalive_interval, which is analagous to tcp_keepstart, but in units of _milliseconds_ not seconds... There is also tcp_keepalive_detached_interval, which is the "tcpkeepstart" used when the connection becomes detached (basically, it is there to cull FIN_WAIT_2 connections to buggy stacks/apps using RTS instead of FIN closing of TCP connections).
The tcp_keepstop is now based on tcp_ip_abort_interval, but do be _very_ careful messing with that as it will also be the maximum (cumulative) time to wait for an ACK of a TCP segment in an ESTABLISHED connection.
ftp://ftp.cup.hp.com/dist/networking/briefs/
useful.
There are now two keepalive parms in 11.X - one is tcp_keepalive_interval, which is analagous to tcp_keepstart, but in units of _milliseconds_ not seconds... There is also tcp_keepalive_detached_interval, which is the "tcpkeepstart" used when the connection becomes detached (basically, it is there to cull FIN_WAIT_2 connections to buggy stacks/apps using RTS instead of FIN closing of TCP connections).
The tcp_keepstop is now based on tcp_ip_abort_interval, but do be _very_ careful messing with that as it will also be the maximum (cumulative) time to wait for an ACK of a TCP segment in an ESTABLISHED connection.
there is no rest for the wicked yet the virtuous have no pillows
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP