topic Re: ndd parms in Operating System - HP-UX

ndd parms

Tim Rotunda — Fri, 14 Dec 2001 16:02:40 GMT

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

Re: ndd parms

Uday_S_Ankolekar — Fri, 14 Dec 2001 18:04:06 GMT

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..

Re: ndd parms

Christopher McCray_1 — Mon, 17 Dec 2001 20:15:26 GMT

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