HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Details about FIN_WAIT_2
Operating System - HP-UX
1832654
Members
3673
Online
110043
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
06-19-2005 06:21 PM
06-19-2005 06:21 PM
Details about FIN_WAIT_2
Could some one answer my questions below.
1) IS FIN_WAIT_2 configurable in HP-11i and HP-11
systems? If so how?
2) What is the default time for a port to get freed off after it gets into FIN_WAIT_2 scenario.
3) Can the time be reduced than the default time out?
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-19-2005 07:47 PM
06-19-2005 07:47 PM
Re: Details about FIN_WAIT_2
First of all, you have to install system patch PHNE_19375, there is an ndd parameter called 'tcp_fin_wait_2_timeout'.
This parameter sets the fin_wait_2 timer on
11.x to stop idle fin_wait_2 connections. It
will not survive a reboot, so modification
of the /etc/rc.config.d/nddconf is necessary. with following.
TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_fin_wait_2_timeout
NDD_VALUE[0]=1200000
The default for tcp_fin_wait_2_timeout is 0,
which allows the connection to live forever,
as long as the far side continues to answer
keepalives.
To enable the tcp_fin_wait_2 timer to timeout do the following:
1. Get the current value (0 is turned off):
# ndd -get /dev/tcp tcp_fin_wait_2_timeout
0
2. Set the value to 20 min's:
# ndd -set /dev/tcp tcp_fin_wait_2_timeout 1200000
3. Check the setting:
# ndd -get /dev/tcp tcp_fin_wait_2_timeout
1200000
Note: (1000 ms in 1 second) * (60 seconds) *
(20 minutes)= 1200000 ms. 20 minutes is just
an example but probably a good selection.
Any setting less than this may cause data
loss.
you can also check DocID: KBRC00001353 for more information.
This parameter sets the fin_wait_2 timer on
11.x to stop idle fin_wait_2 connections. It
will not survive a reboot, so modification
of the /etc/rc.config.d/nddconf is necessary. with following.
TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_fin_wait_2_timeout
NDD_VALUE[0]=1200000
The default for tcp_fin_wait_2_timeout is 0,
which allows the connection to live forever,
as long as the far side continues to answer
keepalives.
To enable the tcp_fin_wait_2 timer to timeout do the following:
1. Get the current value (0 is turned off):
# ndd -get /dev/tcp tcp_fin_wait_2_timeout
0
2. Set the value to 20 min's:
# ndd -set /dev/tcp tcp_fin_wait_2_timeout 1200000
3. Check the setting:
# ndd -get /dev/tcp tcp_fin_wait_2_timeout
1200000
Note: (1000 ms in 1 second) * (60 seconds) *
(20 minutes)= 1200000 ms. 20 minutes is just
an example but probably a good selection.
Any setting less than this may cause data
loss.
you can also check DocID: KBRC00001353 for more information.
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