Operating System - HP-UX
1825294 Members
4179 Online
109679 Solutions
New Discussion юеВ

ICMP source quench / nddconf

 
SOLVED
Go to solution
someone_4
Honored Contributor

ICMP source quench / nddconf

 
9 REPLIES 9
John Palmer
Honored Contributor
Solution

Re: ICMP source quench / nddconf

Hi,

The leading space won't have any effect, it'll be ignored by the shell.

Check your setting with:
ndd -get /dev/ip ip_send_source_quench

Regards,
John
someone_4
Honored Contributor

Re: ICMP source quench / nddconf

#/etc/rc.config.d# ndd -get /dev/ip ip_send_source_quench
1
someone_4
Honored Contributor

Re: ICMP source quench / nddconf

so it should be 0
James R. Ferguson
Acclaimed Contributor

Re: ICMP source quench / nddconf

Hi Richard:

Your 'nddconf' file violates (as documented) the supported syntax. The leading space is not the problem, rather, that the indices specified for various parameters are not listed in ascending order.

The internal documentation reads: "For each additional tunable parameter, add a set of variable assignments like the ones below, changing the index to "[0]", "[1]" et cetera. Index must be starting from 0 and they must be in sequential order. Missing index values inside the array range is not supported."

Regards!

...JRF...
Sridhar Bhaskarla
Honored Contributor

Re: ICMP source quench / nddconf

Hi Richard,

Change the index from 0 to 6 for source quench. I mean TRANSPORT_NAME[6] = etc.,

I have seen disabling source quench messages on certain primitive applications as they do error checking based on ICMP sequences. For ex., to find out if the host is alive or not, they ping to the server. And HP-UX 11.0 servers do not respond sometimes due to this feature causing application failures.

Fixing this doesn't mean the problem is fixed. Server that was sending source quenches will still have buffer full conditions and the root cause is to be found.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
harry d brown jr
Honored Contributor

Re: ICMP source quench / nddconf

Spaces shouldn't matter in nddconf. Issue this to see what it is currently set to:

ndd -get /dev/ip ip_send_source_quench

If it's zero after a reboot, then you are set (according to HP).
Live Free or Die
Uday_S_Ankolekar
Honored Contributor

Re: ICMP source quench / nddconf

Hi ,

Explaination in Document Id : S3100005739

ICMP source quench messages are generated when an IP packet is
received by the 11.0 system that can't be delivered to the socket
buffer of the receiving application. The intent is to inform the
sender of the full buffer condition so the rate of the transmission
is slowed down until the buffer can be read by the receiving
application.

Setting the ndd parameter ip_send_source_quench to 0 can be an
effective way to deal with the messages.

Programs that use icmp protocol, such as ping, use a type of
socket called SOCK_RAW. The nature of using raw IP sockets is
that ALL packets received that match the protocol type of the raw
socket are delivered to ALL the sockets using that protocol. It is
up to the application to read all the data in it's socket buffer
and discard the data it's not interested in. If any of these
sockets are full, the icmp source quench message will be generated.

One process that uses one of these sockets is part of DCE, and it
is 'rpcd'. This program opens a raw socket in order to listen for
icmp messages, which it uses to monitor the health of other systems
on the network running DCE. In this case 'rpcd' used a 32K buffer,
and processed the messages received every 5 minutes, which led to
the buffer full condition.

PHSS_17810 addresses the problem by increasing
the buffer size to 128K and processing the messages every 2 minutes.

-USA..
Good Luck..
John Palmer
Honored Contributor

Re: ICMP source quench / nddconf

Your entries should read:-

TRANSPORT_NAME[5]=ip
NDD_NAME[5]=ip_send_source_quench
NDD_VALUE[5]=0

As you are already setting array elements 0 through 4.

Your current setting will overwrite the values:
TRANSPORT_NAME[0]=tcp
NDD_NAME[0]=tcp_keepalive_interval
NDD_VALUE[0]=3600000

However, if you haven't rebooted since changing nddconf then you'll have to run ndd -set as requested by HP.

Regards,
John

harry d brown jr
Honored Contributor

Re: ICMP source quench / nddconf

Richard,
The document http://people.hp.se/stevesk/bastion11.html , also suggests that you turn ip_send_source_quench off, as well as some other parameters.

live free or die
harry
Live Free or Die