Date: Tue, 28 Aug 2018 16:50:47 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: marius.h@lden.org Cc: np@freebsd.org, freebsd-net <freebsd-net@freebsd.org> Subject: Re: cxl nic not working after reboot Message-ID: <CAN6yY1toQDXQya2jKv90TSNxVeOZt%2BpeGkSYJ8jxPECXe_r1pQ@mail.gmail.com> In-Reply-To: <1535487192.1547312.1489227960.14DA5D07@webmail.messagingengine.com> References: <1535379569.2132387.1487489784.45227861@webmail.messagingengine.com> <20180827151302.GA10167@ox> <1535395530.234212.1487804896.64257978@webmail.messagingengine.com> <1535448912.3229649.1488521184.1EE83C33@webmail.messagingengine.com> <3bdfa15a-1b9f-e8cd-00a5-f5fdaaa5d15e@FreeBSD.org> <1535480853.1508751.1489107768.35E0F6F1@webmail.messagingengine.com> <72e8b5b8-631b-35b3-b378-804e69dd3250@FreeBSD.org> <1535484638.1530345.1489178328.3374515B@webmail.messagingengine.com> <32fc6737-87f8-7156-17f0-8e17b65a0812@FreeBSD.org> <1535487192.1547312.1489227960.14DA5D07@webmail.messagingengine.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Aug 28, 2018 at 1:14 PM Marius Halden <marius.h@lden.org> wrote: > On Tue, Aug 28, 2018, at 21:34, Navdeep Parhar wrote: > > On 8/28/18 12:30 PM, Marius Halden wrote: > > > tx_frames does move, rx_frames is stuck at zero. The following > counters are non-zero and does increase when traffic is sent through the > interface, all other are stuck at zero: > > > > > > dev.cxl.0.stats.tx_frames_65_127: 26083 > > > dev.cxl.0.stats.tx_frames_64: 4084 > > > dev.cxl.0.stats.tx_mcast_frames: 26083 > > > dev.cxl.0.stats.tx_bcast_frames: 4084 > > > dev.cxl.0.stats.tx_frames: 30167 > > > dev.cxl.0.stats.tx_octets: 2608846 > > > > > > Anything else I should look at? > > > > > > > What is on the other side of the link? Look at the peer's rx stats and > > see if it received the frames that cxl0 claims it has transmitted or not. > > Our ISPs router is connected to the other side. Unfortunately I don't have > access to any of the counters, but from what I understood when originally > debugging this with our ISP they did not see any traffic. If needed I can > ask them to check the rx counters tomorrow. > > -- > Marius Halden > This looks a lot like either a routing or NDP issue with the adjacent router. Well, an NDP issue devolves to a routing issue. It also possible that RDP is an issue, but, if you can't ping the opposite end, that eliminates RDP. You might check for NDP traffic with tcpdump or wireshark when the connection is restored. If you are not IPv6 conversant, NDP is the IPv6 replacement for ARP and it's pretty obvious how this would impact your connectivity.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1toQDXQya2jKv90TSNxVeOZt%2BpeGkSYJ8jxPECXe_r1pQ>