Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 15 Jan 2018 00:55:14 -0500
From:      Zaphod Beeblebrox <zbeeble@gmail.com>
To:        FreeBSD Net <freebsd-net@freebsd.org>
Subject:   FreeBSD11 bge and bce interfaces showing packet loss with older Cisco.
Message-ID:  <CACpH0Mfq3m-WP815ueS5njm9pCnT3tKu3=UsUzhF1MweQ7sRog@mail.gmail.com>

next in thread | raw e-mail | index | archive | help
I've been trying to track this problem down for awhile now.  I have two
different router servers with two different chipset on board NICs.  One
server has BGE and the other server has BCE.  Both are running a full
650k-odd route BGP table with quagga and they're joined internally with
OSPF (also quagga).

Anyways, I'm seeing, under load (in the netstat -in output):

bge1   1500 <Link#2>      00:19:b9:f9:ad:13 592048810 2127231     0
576341766     0     0

... indicating 2127231 error packets out of 592048810 packets.  Somewhere
around 0.3% in total ... but this rises to about 1% as traffic increases.

My first problem is that I don't see any number of packets in any of the
netstat -s outputs.  How do I track this down to something more specific
than the netstat -i output?

Now the other end of the dedicated, newly purchased cat6 cable is a Cisco
WS-C3550-12G  ...  a 12 port GigE switch with 10 GBICs and two copper
ports.  In my case, it's mostly full of copper GBICs and has one SMF GBIC
for the uplink.

The GBICs show up two ways on the switch: "a-full a-1000 1000BaseTX" for
the "older" ones and "a-full a-1000 10/100/1000BaseTX" for the "newer"
ones.  Since Cisco doesn't allow setting duplex or speed on any of them, I
have the problem server connected to the 1000BaseT-only GBIC and I have the
server hard set to full-duplex and 1000BaseT.  This doesn't seem to change
the nature of the problem for better or worse.  That is to say both "auto"
and hardwired settings have the same failures.

Now... I'm fully willing to swap out the switch, but I also have trouble
believing that anything has changed with GigE 1000BaseT recently... so I'm
also sensitive that it may not be the fix either.

Help?  Suggestions?



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACpH0Mfq3m-WP815ueS5njm9pCnT3tKu3=UsUzhF1MweQ7sRog>