Although note that RcvFifoNoBuf I believe is not a cable error but a too-much-traffic error, which would suggest that it's being maxed out vs the radio link. Outdiscards I believe also not a cable error, but I don't know
On Thu, Nov 8, 2018 at 10:47 AM Sam Lambie <samtaos...@gmail.com> wrote: > Guys, > > I have a backhaul that is driving me nuts. We have a 6.9 mile link from > our NOC to the site. The Master at the NOC is exhibiting ehternet errors up > the wazoo when loaded. During prime time, we are pushing about 70 mbps > through the link. Wirelessly, everything is perfect, 106/19 with 99% link > quality and no errors on the RF side of things. > Yesterday I replace the main cable up to the radio, replaced the surge > suppressor and even plugged in a Cambium power supply to bypass the CMM. > Then I moved the LAN cable from it's switch to a new switch in case that > port was choking, nothing has made a difference. I even changed out the > radio for about an hour a few days ago with no difference. > > Frame utilization has never spiked beyond 68% but the CPU is pegged during > peak time at 100% > > Any suggestions? or need any other screen shots? > > thanks! > > > [image: Screen Shot 2018-11-08 at 9.43.22 AM.png] > > > > > -- > -- > *Sam Lambie* > Taosnet Wireless Tech. > 575-758-7598 Office > www.Taosnet.com <http://www.newmex.com> > -- > AF mailing list > AF@af.afmug.com > http://af.afmug.com/mailman/listinfo/af_af.afmug.com >
-- AF mailing list AF@af.afmug.com http://af.afmug.com/mailman/listinfo/af_af.afmug.com
