Date: Wed, 26 Oct 2022 08:11:54 -0300 From: Cristian Cardoso <cristian.cardoso11@gmail.com> To: freebsd-net@freebsd.org Subject: Re: netstat -I ix0 Message-ID: <CAKeEC-LTACAi4S_rT%2Bxw4Rf--jnMmp9cCqusFXSMDq15FLLwsA@mail.gmail.com> In-Reply-To: <7d62ceba-3878-3ec7-9b9e-844d56641514@otcnet.ru> References: <3095c007-2582-32f2-c203-db0a30af14a8@otcnet.ru> <2afa3987d7f35bb655f9eb63aa6f4451@korbank.pl> <CAKeEC-KWLoiczDFvUPp0PJLev%2BqT6iwoWbE0bZVZS6U7SDq8JA@mail.gmail.com> <7d62ceba-3878-3ec7-9b9e-844d56641514@otcnet.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000004f1d3105ebee18ae Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Despite the error increments in the interface, I used the equipment for a month until I migrated my things from the router I had and even with a large error increment I didn't have any problems with packet loss or routing. Em ter., 25 de out. de 2022 =C3=A0s 17:58, Victor Gamov <vit@otcnet.ru> esc= reveu: > So, it's not a problem but counter only bug? > > > On 24.10.2022 23:29, Cristian Cardoso wrote: > > Hi > > > > After I upgraded my hardware from 12.2 to 12.3-RELEASE, I also started > > getting error alerts on my FreeBSD monitors via snmp. > > People asked me to upgrade the version to 13, I did but the problem > > persisted, I changed SFP modules and fiber cable, even so the error > > persisted. > > This was a system change that created more counters from the > > implementation of a new revision in FreeBSD. > > > > I reported my bug at the time: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262093 > > > > From what you could see in the url that Konrad passed, a fix is alread= y > > being tested. > > > > Em seg., 24 de out. de 2022 =C3=A0s 17:21, Konrad Kr=C4=99ciwilk > > <konrad.kreciwilk@korbank.pl <mailto:konrad.kreciwilk@korbank.pl>> > escreveu: > > > > Hello, > > > > It seems your issues is related with > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D266048 > > Regards, > > KK > > > > W dniu 2022-10-24 17:59, Victor Gamov napisa=C5=82(a): > > > Hi All > > > > > > On my FreeBSD 12.3-STABLE r372089 GENERIC amd64 I have a huge > amount > > > of RX errors on ix0: > > > > > > =3D=3D=3D=3D=3D > > > # netstat -n -I ix0 > > > Name Mtu Network Address Ipkts Ierrs Idrop > > Opkts > > > Oerrs Coll > > > ix0 1500 <Link#1> a0:36:9f:1d:80:80 2336589698003 > > 774784702245 > > > 0 1816532334151 0 0 > > > =3D=3D=3D=3D=3D > > > > > > =3D=3D=3D=3D=3D > > > # sysctl dev.ix.0 | grep errs > > > dev.ix.0.mac_stats.checksum_errs: 774729511713 > > > dev.ix.0.mac_stats.rec_len_errs: 31682 > > > dev.ix.0.mac_stats.byte_errs: 14414734 > > > dev.ix.0.mac_stats.ill_errs: 3034419 > > > dev.ix.0.mac_stats.crc_errs: 54705100 > > > dev.ix.0.mac_stats.rx_errs: 774787585085 > > > =3D=3D=3D=3D=3D > > > > > > > > > Are these errors phy/hw problems e.x. wrong SFP+ > hardware/firmware, > > > too high / too low RX levels, broken patch cord? Or may it be > > some OS > > > errors? > > > > > > > > > Thanks for any advise! > > > -- > CU, > Victor Gamov > > --0000000000004f1d3105ebee18ae Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div>Hi</div><div><br></div>Despite the error increments i= n the interface, I used the equipment for a month until I migrated my thing= s from the router I had and even with a large error increment I didn't = have any problems with packet loss or routing.<br></div><br><div class=3D"g= mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">Em ter., 25 de out. de 20= 22 =C3=A0s 17:58, Victor Gamov <<a href=3D"mailto:vit@otcnet.ru">vit@otc= net.ru</a>> escreveu:<br></div><blockquote class=3D"gmail_quote" style= =3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding= -left:1ex">So, it's not a problem but counter only bug?<br> <br> <br> On 24.10.2022 23:29, Cristian Cardoso wrote:<br> > Hi<br> > <br> > After I upgraded my hardware from 12.2 to 12.3-RELEASE, I also started= <br> > getting error alerts on my FreeBSD monitors via snmp.<br> > People asked me to upgrade the version to 13, I did but the problem <b= r> > persisted, I changed SFP modules and fiber cable, even so the error <b= r> > persisted.<br> > This was a system change that created more counters from the <br> > implementation of a new revision in FreeBSD.<br> > <br> > I reported my bug at the time: <br> > <a href=3D"https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D262093"= rel=3D"noreferrer" target=3D"_blank">https://bugs.freebsd.org/bugzilla/sho= w_bug.cgi?id=3D262093</a> <br> > <br> >=C2=A0 From what you could see in the url that Konrad passed, a fix is = already <br> > being tested.<br> > <br> > Em seg., 24 de out. de 2022 =C3=A0s 17:21, Konrad Kr=C4=99ciwilk <br> > <<a href=3D"mailto:konrad.kreciwilk@korbank.pl" target=3D"_blank">k= onrad.kreciwilk@korbank.pl</a> <mailto:<a href=3D"mailto:konrad.kreciwil= k@korbank.pl" target=3D"_blank">konrad.kreciwilk@korbank.pl</a>>> esc= reveu:<br> > <br> >=C2=A0 =C2=A0 =C2=A0Hello,<br> > <br> >=C2=A0 =C2=A0 =C2=A0It seems your issues is related with<br> >=C2=A0 =C2=A0 =C2=A0<a href=3D"https://bugs.freebsd.org/bugzilla/show_b= ug.cgi?id=3D266048" rel=3D"noreferrer" target=3D"_blank">https://bugs.freeb= sd.org/bugzilla/show_bug.cgi?id=3D266048</a><br> >=C2=A0 =C2=A0 =C2=A0Regards,<br> >=C2=A0 =C2=A0 =C2=A0KK<br> > <br> >=C2=A0 =C2=A0 =C2=A0W dniu 2022-10-24 17:59, Victor Gamov napisa=C5=82(= a):<br> >=C2=A0 =C2=A0 =C2=A0 > Hi All<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > On my FreeBSD 12.3-STABLE r372089 GENERIC=C2= =A0 amd64 I have a huge amount<br> >=C2=A0 =C2=A0 =C2=A0 > of RX errors on ix0:<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > =3D=3D=3D=3D=3D<br> >=C2=A0 =C2=A0 =C2=A0 > # netstat -n -I ix0<br> >=C2=A0 =C2=A0 =C2=A0 > Name=C2=A0 =C2=A0 Mtu Network=C2=A0 =C2=A0 = =C2=A0 =C2=A0Address=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Ipkts = Ierrs Idrop<br> >=C2=A0 =C2=A0 =C2=A0Opkts<br> >=C2=A0 =C2=A0 =C2=A0 > Oerrs=C2=A0 Coll<br> >=C2=A0 =C2=A0 =C2=A0 > ix0=C2=A0 =C2=A0 1500 <Link#1>=C2=A0 = =C2=A0 =C2=A0 a0:36:9f:1d:80:80 2336589698003<br> >=C2=A0 =C2=A0 =C2=A0774784702245<br> >=C2=A0 =C2=A0 =C2=A0 >=C2=A0 =C2=A00 1816532334151=C2=A0 =C2=A0 =C2= =A00=C2=A0 =C2=A0 =C2=A00<br> >=C2=A0 =C2=A0 =C2=A0 > =3D=3D=3D=3D=3D<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > =3D=3D=3D=3D=3D<br> >=C2=A0 =C2=A0 =C2=A0 > # sysctl dev.ix.0 | grep errs<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.checksum_errs: 77472951171= 3<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.rec_len_errs: 31682<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.byte_errs: 14414734<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.ill_errs: 3034419<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.crc_errs: 54705100<br> >=C2=A0 =C2=A0 =C2=A0 > dev.ix.0.mac_stats.rx_errs: 774787585085<br> >=C2=A0 =C2=A0 =C2=A0 > =3D=3D=3D=3D=3D<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > Are these errors phy/hw problems e.x. wrong S= FP+ hardware/firmware,<br> >=C2=A0 =C2=A0 =C2=A0 > too high / too low RX levels, broken patch co= rd?=C2=A0 Or may it be<br> >=C2=A0 =C2=A0 =C2=A0some OS<br> >=C2=A0 =C2=A0 =C2=A0 > errors?<br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 ><br> >=C2=A0 =C2=A0 =C2=A0 > Thanks for any advise!<br> <br> <br> -- <br> CU,<br> Victor Gamov<br> <br> </blockquote></div> --0000000000004f1d3105ebee18ae--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKeEC-LTACAi4S_rT%2Bxw4Rf--jnMmp9cCqusFXSMDq15FLLwsA>