Re: 'dropped due to full socket buffers' by SNMP

22.01.2021 20:26, Victor Gamov wrote: >>>> What FreeBSD version do you use currently? Do you use IPv6 for UDP or >>>> IPv4 only? >>> >>> >>> FreeBSD 12.2-STABLE r366543 GENERIC amd64 >>> >>> UDP-4 only >> >> In case

Re: 'dropped due to full socket buffers' by SNMP

multicast traffic to this host. Total input traffic about 1Gbit/s What FreeBSD version do you use currently? Do you use IPv6 for UDP or IPv4 only? FreeBSD 12.2-STABLE r366543 GENERIC amd64 UDP-4 only In case of IPv4 UDP the counter "dropped due to full socket buffers" is increased fo

Re: 'dropped due to full socket buffers' by SNMP

ulticast >>> traffic to this host. Total input traffic about 1Gbit/s >> >> What FreeBSD version do you use currently? Do you use IPv6 for UDP or >> IPv4 only? > > > FreeBSD 12.2-STABLE r366543 GENERIC amd64 > > UDP-4 only In case of IPv4 UDP the counter

Re: 'dropped due to full socket buffers' by SNMP

On 22.01.2021 13:21, Eugene Grosbein wrote: 22.01.2021 17:02, Victor Gamov wrote: No link overload: this host attached to network via 10G ix0, many VLANs on this ix0 and some sender on every VLAN sends multicast traffic to this host. Total input traffic about 1Gbit/s What FreeBSD version

Re: 'dropped due to full socket buffers' by SNMP

22.01.2021 17:02, Victor Gamov wrote: > No link overload: this host attached to network via 10G ix0, many VLANs on > this ix0 and some sender on every VLAN sends multicast traffic to this host. > Total input traffic about 1Gbit/s What FreeBSD version do you use currently? Do you use IPv6 for U

Re: 'dropped due to full socket buffers' by SNMP

On 22.01.2021 12:52, Eugene Grosbein wrote: 22.01.2021 16:27, Victor Gamov wrote: I increase kern.ipc.maxsockbuf from 2097152 -> 2597152 -> 3145728 but netstat -sn -p udp | grep 'dropped due to full socket buffers' still show dropped packets. Then I increase net.inet.udp

Re: 'dropped due to full socket buffers' by SNMP

22.01.2021 16:27, Victor Gamov wrote: > I increase kern.ipc.maxsockbuf from 2097152 -> 2597152 -> 3145728 but > netstat -sn -p udp | grep 'dropped due to full socket buffers' still show > dropped packets. > > Then I increase net.inet.udp.recvspace 84160 ->

Re: 'dropped due to full socket buffers' by SNMP

f and then net.inet.udp.recvspace. Eugene, at first message you suppose Host-A (sender) "outgoing link for that UDP packets is congested" because this host shows non-zero "dropped due to full socket buffers". So is net.inet.udp.recvspace increasing on Host-B (mainly receiver)

Re: 'dropped due to full socket buffers' by SNMP

05.01.2021 16:39, Victor Gamov wrote: >>> As I understand hw.ix.flow_control=3 to allow flow-control for negotiation. >>> Real PAUSE setting will be set during negotiation. >> >> At the moment of congestion. > > As I understand PAUSE feature negotiated during auto-negotiation process. If > flow-

Re: 'dropped due to full socket buffers' by SNMP

first message you suppose Host-A (sender) "outgoing link for that UDP packets is congested" because this host shows non-zero "dropped due to full socket buffers". So is net.inet.udp.recvspace increasing on Host-B (mainly receiver) will be affected for this congestion? Can't

Re: 'dropped due to full socket buffers' by SNMP

cause this host shows non-zero "dropped due to full socket buffers". > So is net.inet.udp.recvspace increasing on Host-B (mainly receiver) will be > affected for this congestion? Can't tell in details without going deep into your setup :-) You can try it yours

Re: 'dropped due to full socket buffers' by SNMP

-A (sender) "outgoing link for that UDP packets is congested" because this host shows non-zero "dropped due to full socket buffers". So is net.inet.udp.recvspace increasing on Host-B (mainly receiver) will be affected for this congestion? Or I need to try to increas

Re: 'dropped due to full socket buffers' by SNMP

30.12.2020 16:44, Victor Gamov wrote: > Currently I'm thinking about ethernet flow control: Host-B connected to > VLAN-750 on the third switch has 1G link (via igb driver) > and both Host-A and Host-B has fc=3. So when Host-B get microburst it can > send PAUSE and Host-A start to fill queue. >

Re: 'dropped due to full socket buffers' by SNMP

Hi Eugene Thank for your reply On 30/12/2020 02:13, Eugene Grosbein wrote: 29.12.2020 23:36, Victor Gamov wrote: Please do not top-post. Thanks. On 30/11/2020 18:33, Victor Gamov wrote: Hi All Can somebody help me to get UDP 'dropped due to full socket buffers' by SNMP? Is i

Re: 'dropped due to full socket buffers' by SNMP

29.12.2020 23:36, Victor Gamov wrote: Please do not top-post. > Thanks. > > > On 30/11/2020 18:33, Victor Gamov wrote: >> Hi All >> >> Can somebody help me to get UDP 'dropped due to full socket buffers' by >> SNMP? Is it possible? Now I'

Re: 'dropped due to full socket buffers' by SNMP

And one more question about 'dropped due to full socket buffers': how to avoid it? Which params must be tuned? Thanks. On 30/11/2020 18:33, Victor Gamov wrote: Hi All Can somebody help me to get UDP 'dropped due to full socket buffers' by SNMP?  Is it possible?  Now

'dropped due to full socket buffers' by SNMP

Hi All Can somebody help me to get UDP 'dropped due to full socket buffers' by SNMP? Is it possible? Now I'm getting it with `netstat -n -p udp -f inet -s` but SNMP will be more useful for remote monitoring. Thanks! -- C

Re: Reason of "dropped due to full socket buffers" UDP

Artem Naluzhny wrote: > hi > > I have 6.1-RELEASE with default sysctl vars. Continuous 'netstat -sp > udp' with 100 ms. interval shows dropped UDP due to full socket > buffers sometimes. The script also monitors 'netstat -anp udp' and > there are no connect

Reason of "dropped due to full socket buffers" UDP

hi I have 6.1-RELEASE with default sysctl vars. Continuous 'netstat -sp udp' with 100 ms. interval shows dropped UDP due to full socket buffers sometimes. The script also monitors 'netstat -anp udp' and there are no connections with non-zero Recv-Q value by the end of the

Re: socket buffers

On Wednesday, September 18, 2002, at 08:03 AM, Petri Helenius wrote: > > I played around adjusting udp socket buffers for a while and noticed > that if the input buffer is set to a value, packets start getting > dropped > when npkt*MTU > SO_RCVBUF so if a socket receives 100

socket buffers

I played around adjusting udp socket buffers for a while and noticed that if the input buffer is set to a value, packets start getting dropped when npkt*MTU > SO_RCVBUF so if a socket receives 100 byte packets over an ethernet interface of 1500 byte MTU and receive buffer of 100k the pack

Re: name resolution problems and "full socket buffers"

03735 63.203.35.55.53 > 10.0.1.14.1069: 26930 q: MX? www.yahoo.com. 1/1/0 www.yahoo.com. CNAME[ |domain ] (DF) (ttl 249, id 16303, len 153) > >> nestat -s also shows the following udp counters incrementing: >> >> "x dropped due to no sock

Re: name resolution problems and "full socket buffers"

missing something. > nestat -s also shows the following udp counters incrementing: > > "x dropped due to no socket" This is what I would expect for what you describe... > "y dropped due to full socket buffers" H... Could we double-check the firewall issue, $ sy

name resolution problems and "full socket buffers"

port used by my machine as the source port for the dns query. nestat -s also shows the following udp counters incrementing: "x dropped due to no socket" "y dropped due to full socket buffers" The output of "sysctl -a", for the relevant variables, seems fine... when