HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: ndd parms
Operating System - HP-UX
1825767
Members
2056
Online
109687
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
12-14-2001 08:02 AM
12-14-2001 08:02 AM
ndd parms
Could someone please help me to understand why when I do the following netstat command I see 5 fin_wait???s and when, at the same time, I do the ndd ???get command I only find one and it doesn???t even look related to anything in the netstat output?
root@dev3:/ $netstat -a | grep -i fin_wait_2
tcp 0 0 dev3.80 10.0.1.73.1384 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1385 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1386 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1383 FIN_WAIT_2
tcp 0 0 dev3.64220 p79.9100 FIN_WAIT_2
root@dev3:/ $ndd -get /dev/tcp tcp_status | grep -i fin_wait
070f6840 010.000.001.208 722f6dd1 722f6dd1 00000000 00002000 01300001 01300001 00008000 03789 01024 [fadc,238c] TCP_FIN_WA
IT_2
Moreover, does the ndd parameter tcp_fin_wait_2_timeout, have any effect on a fin_wait_2 connection that was established by hpnpf?
Thanks very much for any insight on this.
TR.a
root@dev3:/ $netstat -a | grep -i fin_wait_2
tcp 0 0 dev3.80 10.0.1.73.1384 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1385 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1386 FIN_WAIT_2
tcp 0 0 dev3.80 10.0.1.73.1383 FIN_WAIT_2
tcp 0 0 dev3.64220 p79.9100 FIN_WAIT_2
root@dev3:/ $ndd -get /dev/tcp tcp_status | grep -i fin_wait
070f6840 010.000.001.208 722f6dd1 722f6dd1 00000000 00002000 01300001 01300001 00008000 03789 01024 [fadc,238c] TCP_FIN_WA
IT_2
Moreover, does the ndd parameter tcp_fin_wait_2_timeout, have any effect on a fin_wait_2 connection that was established by hpnpf?
Thanks very much for any insight on this.
TR.a
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2001 10:04 AM
12-14-2001 10:04 AM
Re: ndd parms
Hi,
You can use ndd command for this
To see the current setting
ndd -get /dev/tcp tcp_fin_wait_2_timeout
To set the new value to
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000 (Value in Mili second)
Goodluck,
-USA..
You can use ndd command for this
To see the current setting
ndd -get /dev/tcp tcp_fin_wait_2_timeout
To set the new value to
ndd -set /dev/tcp tcp_fin_wait_2_timeout 600000 (Value in Mili second)
Goodluck,
-USA..
Good Luck..
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-17-2001 12:15 PM
12-17-2001 12:15 PM
Re: ndd parms
Hi Tim,
Take a look at this document; I hope it will answer your questions:
http://us-support.external.hp.com/cki/bin/doc.pl/sid=537ff78b1732ede65f/screen=ckiDisplayDocument?docId=200000016401876
I suspect the reason your -get command only displays one entry is that the listings in the netstat output are all linked and by getting rid of the one entry will knock out all the other fin_wait_2s. use this command:
# ndd -set /dev/tcp tcp_discon 0x070f6840
to get rid of the entry in your tcp_status query and then do another netstat. If there are any more, then query the tcp_status for other fins and get rid of them as necessary.
Hope this helps.
Chris
Take a look at this document; I hope it will answer your questions:
http://us-support.external.hp.com/cki/bin/doc.pl/sid=537ff78b1732ede65f/screen=ckiDisplayDocument?docId=200000016401876
I suspect the reason your -get command only displays one entry is that the listings in the netstat output are all linked and by getting rid of the one entry will knock out all the other fin_wait_2s. use this command:
# ndd -set /dev/tcp tcp_discon 0x070f6840
to get rid of the entry in your tcp_status query and then do another netstat. If there are any more, then query the tcp_status for other fins and get rid of them as necessary.
Hope this helps.
Chris
It wasn't me!!!!
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
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP