GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- How to define TCP/IP outbound ports
Operating System - HP-UX
1854683
Members
5195
Online
104102
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
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-29-2006 06:40 PM
03-29-2006 06:40 PM
Dear All,
Can you please help me in defineing the TCP/IP Outbound ports in HP-UX11i v2 (11.23) on IA64. Is there any way to do this.
In TRU64 Unix we can define in kernel the minimum starting port number.
TIA
Cheers,
Vishwanath A
Can you please help me in defineing the TCP/IP Outbound ports in HP-UX11i v2 (11.23) on IA64. Is there any way to do this.
In TRU64 Unix we can define in kernel the minimum starting port number.
TIA
Cheers,
Vishwanath A
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2006 07:03 PM
03-29-2006 07:03 PM
Solution
Hi Vishwanath
This is the Command that you're searching for:
# /usr/bin/ndd -set /dev/tcp tcp_smallest_anon_port 50001
# /usr/bin/ndd -set /dev/tcp tcp_largest_anon_port 61000
# /usr/bin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port
The file to make it persistent is:
/etc/rc.config.d/nddconf
rgds
HGH
This is the Command that you're searching for:
# /usr/bin/ndd -set /dev/tcp tcp_smallest_anon_port 50001
# /usr/bin/ndd -set /dev/tcp tcp_largest_anon_port 61000
# /usr/bin/ndd /dev/tcp tcp_smallest_anon_port tcp_largest_anon_port
The file to make it persistent is:
/etc/rc.config.d/nddconf
rgds
HGH
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2006 11:02 PM
03-29-2006 11:02 PM
Re: How to define TCP/IP outbound ports
Thanks HGH i was looking for the same.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2006 04:45 AM
03-31-2006 04:45 AM
Re: How to define TCP/IP outbound ports
If you have an application that wants to churn through a large number of ports - say lots of connection establishment and tear-down - you might want to consider two alternatives:
1) Use the connections longer so create/destroy fewer at a time
2) Have the application make explicit bind() calls to select port numbers. For example, a full set of port numbers in the range of 5000 to 65535. Stuff like netperf TCP_CRR and SPECweb do that.
The nice thing about option 1 is you will save CPU overhead on the TCP connection setup and teardown.
The nice thing about option 2 is you will not depend on the systems' ndd settings.
1) Use the connections longer so create/destroy fewer at a time
2) Have the application make explicit bind() calls to select port numbers. For example, a full set of port numbers in the range of 5000 to 65535. Stuff like netperf TCP_CRR and SPECweb do that.
The nice thing about option 1 is you will save CPU overhead on the TCP connection setup and teardown.
The nice thing about option 2 is you will not depend on the systems' ndd settings.
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 2026 Hewlett Packard Enterprise Development LP