05-08-2003
TCP ports - TIME_WAIT
What is the maximum number of TCP ports that can be consumed at any one time? How can I determine what the number is or increase it?
I was under the impression that with our system (UnixWare 7.1.1) 1024 was the maximum under our current Kernel tuning parms, but I think that is really just for telnet and not all TCP ports combined.
The reason I ask? Because our Unix server makes calls to a Windows 2000 machine all day long and there have been times that the number of ports stuck simultaneously in TIME_WAIT between these 2 machines has been nearly 1500 (1499 to be exact) and I'm concerned that we'll run out.
Any help is greatly appreciated.
10 More Discussions You Might Find Interesting
1. IP Networking
We are being setup with a client over their VPN to support them remotely. We are unable to access their VPN through our server, they said to look and make sure that the TCP ports are enabled for their security setup (ports are in the 4000 range).
How do you look for this and how do you enable a... (3 Replies)
Discussion started by: blacksheep
3 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
Can someone instruct me on how to change the listening port for ftp ( or any tcp service) from 21 to another port number? Thanks in advance..
-AJ (3 Replies)
Discussion started by: jacobsa
3 Replies
3. UNIX for Dummies Questions & Answers
Just starting to work with unix, wondering if there is any good on-line documentation explaining TCP/UDP ports, how to use them, etc...
Thanks.... (1 Reply)
Discussion started by: eugene_mayo
1 Replies
4. IP Networking
Just wondering if anyone knows of any good on-line documentation on TCP/UDP Ports. Basically i want to know how to check if they are in use, learn how to close them, etc...
Thanks... (5 Replies)
Discussion started by: eugene_mayo
5 Replies
5. Windows & DOS: Issues & Discussions
In using a music file sharing program (WinMx), I am told that I
cannot make a primary connection (fastest downloads) because I do not
have a TCP and UDP port. I am running Windows Me.What do I do? Thanks. (6 Replies)
Discussion started by: dookster5
6 Replies
6. UNIX for Advanced & Expert Users
hi,
I'm currently running with an issue whereby we are experiencing very poor access speeds to our Informix database. Connections or requests to the DB are taking in excess of 2/3/4 minutes during peek periods during the day. This has only just started to happen but so far we have been unable to... (0 Replies)
Discussion started by: fastyan
0 Replies
7. UNIX for Dummies Questions & Answers
I'm not sure if this is the right place for this post, but I'd be grateful if somebody could please help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used
iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i... (2 Replies)
Discussion started by: thehaapyappy
2 Replies
8. IP Networking
Please can somebody help me. I'm trying to open ports 999, 1982 and 1983 but am not having much luck. I used
iptables -A INPUT -i eth0 -p tcp --sport 999 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables -A INPUT -i eth0 -p tcp --sport 1982 -m state --state NEW,ESTABLISHED -j ACCEPT
iptables... (5 Replies)
Discussion started by: thehaapyappy
5 Replies
9. Solaris
Hello,
One of our developers is asking for a command/script in Solaris similar to "netstat -anp" in Linux. He gave this output as an example:
root@xxx:~# netstat -anp | grep LISTEN
tcp 0 0 0.0.0.0:7937 0.0.0.0:* LISTEN 16082/nsrexecd
tcp 0 ... (7 Replies)
Discussion started by: vimes
7 Replies
10. Red Hat
Hi,
I want to kill TCP connections which have status as TIME_WAIT & no PID
(as per the output of the "netstat - p" command).
Is there any command/utility available to kill connections to a specific port or IP address.
The problem is that these connections don't have process ID (see... (4 Replies)
Discussion started by: Davinder31may
4 Replies
LEARN ABOUT HPUX
max_async_ports
max_async_ports(5) File Formats Manual max_async_ports(5)
NAME
max_async_ports - maximum number of asynchronous disk ports that can be open at any time
VALUES
Failsafe
Default
Allowed values
Recommended values
There is no recommended value for this tunable. The number of processes that will be accessing the driver simultaneously can be used as a
guideline to set a value.
DESCRIPTION
The asynchronous disk driver provides an interface to execute high-performance I/O to the raw disk. Instead of reading or writing directly
to the raw disk, a process writes requests to the asynchronous driver which then makes appropriate calls to the disk driver.
Every process that opens the asynchronous disk driver is assigned a port. The driver uses the port to keep track of I/O and other internal
resources for that process. The number of opens to the asynchronous disk driver is limited by the number of available ports.
Who Is Expected to Change This Tunable?
Anyone.
Restrictions on Changing
Changes to this tunable take effect immediately if the new value is allowed; otherwise the change takes effect at next boot. Increases
within the allowed range are always accepted immediately. Decreases in the value may take effect immediately, or may be deferred until
next boot depending on the current number of ports in use or the maximum number of ports ever used.
When Should the Value of This Tunable Be Raised?
When the number of processes opening the driver needs to be more than the current value of the tunable.
What Are the Side Effects of Raising the Value of This Tunable?
The resources for the port are allocated from the kernel memory. Setting a higher value would result in the driver using slightly more
kernel memory. Other kernel components which may need kernel memory could suffer. However, the amount of memory reserved for each port is
low. Only when a new port is actually issued does any significant amount of memory get consumed.
When Should the Value of This Tunable Be Lowered?
There should be no real need to lower the value of the tunable. However, if many processes are opening the async driver and allocating
ports, then lowering the value will put a cap on the maximum number of ports that can be allocated and will put a cap on the maximum amount
of memory that the driver may allocate.
What Are the Side Effects of Lowering the Value of This Tunable?
The number of simultaneous opens are limited by this tunable. This may impact the performance of applications that need to have a higher
number of processes accessing the driver.
What Other Tunables Should Be Changed at the Same Time?
None.
WARNINGS
All HP-UX kernel tunable parameters are release specific. This parameter may be removed or have its meaning changed in future releases of
HP-UX.
Installation of optional kernel software, from HP or other vendors, may cause changes to tunable parameter values. After installation,
some tunable parameters may no longer be at the default or recommended values. For information about the effects of installation on tun-
able values, consult the documentation for the kernel software being installed. For information about optional kernel software that was
factory installed on your system, see at
AUTHOR
was developed by HP.
Tunable Kernel Parameters max_async_ports(5)