ndd parameters

[William Pribble]

I am running 11.0 on an N4000.
How do I list all the values of my ndd parameters?

Second part, is there any good documentation or resorces besides the ndd help on what these ndd parameters do and how to tune them?

thanks

[Bernhard Mueller]

Hello,

try:

ndd -h

then

ndd -get

HTH
Regards,
Bernhard

[eran maor]

Hi

i dont know a command that can give you all the vaule but you can use the command :
ndd -h to get all the params that ndd have and you can also write a smapp script that will take all hte info

[John Dvorchak]

To list all ndd parameters:

ndd -h

As far as what they do and how to tune them, I have always felt that if I don't know the acronyms, I shouldn't be messing with them. Nework tuning is best left to the networking gurus, because the defaults are very good only in rare extremem cases of a messed up LAN should they be tuned. And ususlly only with the help of a network sniffer and someone eminently qualified to decypher the results of the probe.

[S.K. Chan]

Apart from the man pages, there is little or perhaps not much documentation of ndd at all. If you were to tweak it just remmeber to make use of /etc/rc.config.d/nddconf to make 'em permanent.

[eran maor]

Hi Again

if you have a que about sepacial param you can ask over here and i will give you some guide lines about .

the command param htat every body change is :
tcp_keepalive_interval
Supported for 11.0
Supported for 11i

The parameter tcp_keepalive_interval determines the amount of time that TCP waits for an idle connection with no unacknowledged data before sending keepalive packets.

If the remote does not acknowledge the keepalive packet, TCP will use one of the following retransmission timers and terminate the connection when it elapses as follows:

Established connection tcp_ip_abort_interval
Connection establishment tcp_ip_abort_cinterval
Connection terminating tcp_keepalive_detached_interval

The timer itself restarts every time TCP sends or receives a packet.
So, when no activity is seen on the connection, the time will increase until the timer value reaches tcp_keepalive_interval.

When the timer values reaches tcp_keepalive_interval, KEEPALIVE 'probe' packet is sent to the other side and the other timer starts.
The 'probe' packet is retransmitted if no ACK comes. The retransmission happens in the same way as normal TCP data retransmission policy using exponential backoff algorithm. When the other timer's value reaches tcp_ip_abort_interval during the retransmission, the connection will be terminated silently

[MANOJ SRIVASTAVA]

Hi

good help is man ndd


you can go this site :

http://www.docs.hp.com/hpux/onlinedocs/B2355-90681/B2355-90681.html

Manoj Srivastava

[Robert-Jan Goossens]

hi

Why dont you use lanadmin

#lanscan
locate NMID number

#lanadmin -x

Kind regards,

RJ

[rick jones]

the advice about "if you don't understand it well, don't mess with it" is very good.

the tcp_keepalive_interval change for ndd would only affect those applications that have used setsockopt() to set SO_KEEPALIVE.

an unofficial resource for ndd settings can be found at:

ftp://ftp.cup.hp.com/dist/networking/briefs/

look for the annotated_ndd.txt file

[Sridhar Bhaskarla]

How do you list all your ndd parameters??.. Hmmmm.. write a script.


for PARAM in $(ndd -h |grep "_"|awk '{print $1}')
do
SUB=$(echo $PARAM|awk '{FS="_";print $1}')VALUE=$(ndd -get /dev/${SUB} $PARAM)
echo $SUB:$PARAM = $VALUE
done

-Sri

[Sridhar Bhaskarla · Accepted solution]

The spaces got messed up.. Lemme try again

for PARAM in $(ndd -h |grep "_"|awk '{print $1}')
do
SUB=$(echo $PARAM|awk '{FS="_";print $1}')
VALUE=$(ndd -get /dev/${SUB} $PARAM)
echo $SUB:$PARAM = $VALUE
done

I wouldn't try to dump the output into a file.

-Sri