HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Equivalent TCP parameters in Solaris and HP-UX
Operating System - HP-UX
1833785
Members
2907
Online
110063
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
Go to solution
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
03-01-2001 08:37 AM
03-01-2001 08:37 AM
Hi,
I need to change some TCP parameters in HP-UX as recommended by my application developer. The problem is that I just have the Solaris parameters. Does anybody know the names or equivalence for the Solaris parameters below ?
tcp_conn_req_max_q0
tcp_conn_req_max_q
tcp_close_wait_interval
tcp_fin_wait_2_flush_interval
I need to change some TCP parameters in HP-UX as recommended by my application developer. The problem is that I just have the Solaris parameters. Does anybody know the names or equivalence for the Solaris parameters below ?
tcp_conn_req_max_q0
tcp_conn_req_max_q
tcp_close_wait_interval
tcp_fin_wait_2_flush_interval
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2001 10:26 AM
03-01-2001 10:26 AM
Re: Equivalent TCP parameters in Solaris and HP-UX
The parameters tcp_conn_req_max_q0, tcp_conn_req_max_q were introduced with Solaris 2.6, the equivalent parameter in HP-UX is tcp_conn_request_max.
The equivalent to tcp_close_wait_interval (changes to tcp_time_wait_interval in Solaris 7) under HP-UX is called tcp_time_wait_interval.
Finally, the HP-UX equivalent for tcp_fin_wait_2_flush_interval is tcp_fin_wait_2_timeout.
BTW, an excellent TCP tuning guide (based on Solaris, but I think is generally relevant) can be found at http://www.rvs.uni-hannover.de/people/voeckler/tune/EN/tune.html
The equivalent to tcp_close_wait_interval (changes to tcp_time_wait_interval in Solaris 7) under HP-UX is called tcp_time_wait_interval.
Finally, the HP-UX equivalent for tcp_fin_wait_2_flush_interval is tcp_fin_wait_2_timeout.
BTW, an excellent TCP tuning guide (based on Solaris, but I think is generally relevant) can be found at http://www.rvs.uni-hannover.de/people/voeckler/tune/EN/tune.html
Remember, wherever you go, there you are...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2001 11:30 AM
03-01-2001 11:30 AM
Re: Equivalent TCP parameters in Solaris and HP-UX
Jim,
Thanks for the site, it seems very usefull.
I?ve just found out a parameter on HP-UX called tcp_syn_rcvd_max that is related to max number of connections in SYN_RCVD state. May I use it instead of tcp_conn_req_max for the tcp_conn_req_max_q0 in Solaris ?
Thanks for the site, it seems very usefull.
I?ve just found out a parameter on HP-UX called tcp_syn_rcvd_max that is related to max number of connections in SYN_RCVD state. May I use it instead of tcp_conn_req_max for the tcp_conn_req_max_q0 in Solaris ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-01-2001 12:25 PM
03-01-2001 12:25 PM
Solution
Yes, it is basically the equivalent. I would follow the advice of the paper I mentioned above, and make sure that this value is larger than the value you give to tcp_conn_request_max.
# ndd -h tcp_syn_rcvd_max
tcp_syn_rcvd_max:
Controls the SYN attack defense of TCP. The value specifies
the maximum number of suspect connections that will be allowed
to persist in SYN_RCVD state. For SYN attack defense to work,
this number must be large enough so that a legitimate connection
will not age out of the list before an ACK is received from the
remote host. This number is a function of the speed at which
bogus SYNs are being received and the maximum round trip time
for a valid remote host. This is very difficult to estimate
dynamically, but the default value of 500 has proven to be highly
effective. [1,10000] Default: 500 connections
# ndd -h tcp_syn_rcvd_max
tcp_syn_rcvd_max:
Controls the SYN attack defense of TCP. The value specifies
the maximum number of suspect connections that will be allowed
to persist in SYN_RCVD state. For SYN attack defense to work,
this number must be large enough so that a legitimate connection
will not age out of the list before an ACK is received from the
remote host. This number is a function of the speed at which
bogus SYNs are being received and the maximum round trip time
for a valid remote host. This is very difficult to estimate
dynamically, but the default value of 500 has proven to be highly
effective. [1,10000] Default: 500 connections
Remember, wherever you go, there you are...
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