From owner-freebsd-net@freebsd.org Wed Aug 29 06:14:10 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 9EA8C10A2D96 for ; Wed, 29 Aug 2018 06:14:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 25BA37E432; Wed, 29 Aug 2018 06:14:10 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-oi0-x22a.google.com with SMTP id c190-v6so7177842oig.6; Tue, 28 Aug 2018 23:14:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=PA8+2Pk3mk3XMySo/rNDcV10iIvwpugYAyq+573cFGk=; b=MGx3Py1p0ZuklWSHWF4bPsHjuvgNA/N3qEYkWQ0l0T3IIqQFZVLArMMiGQkalI33D4 sxSP82/9cGP8kl+sDBKF65t9qdvKD4Nx/X1X2hQ6Hb9c/Rjn6WbiYIsQ9ARxqhUivfVS dLwQdTxJgkHcHT9HmSxx0YV0aQfWGgdj0aoON8Nq7DoPSCh0Ga4/YeokcwbP2hCx2x1F 4UY/t6bXmS7peT3ZPHMUHLM5K0ngRGaPo7L/iBLumv86ONWyx2z/phfTYMgA3PPbZPgh /q2RNqOpU7iY69vRl4bAB6zIKQO/nePHxKEOwpO2n6kbKJ8ie1enDZ8VXkitSyQt9SAa NMTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=PA8+2Pk3mk3XMySo/rNDcV10iIvwpugYAyq+573cFGk=; b=q/s4yZGTYMzRsLjRZxrvso/03iTgYiXbG8oAua05T14Ff9DMlFgUOVFd86s6PhL3Uq akuDMlz+V0h5wTHe2/1klazsAvHwPLLUZtwbVGDu8se8CmKkSLI7ficci3T6Kr65VcEC kbnYtan/GyZ3EuNt7P4VA+Q6W9HELhM+9C21ut4Jd9X7Pv5pfKn8T9Fra/FMTfE7azrA +WXsa8Spw8/lZDiIf/1Kok+eTHLwxjtZkjmPvlqNlhD6+U9KPMGm1WZvXZRTfxbeT5mr DIJZNdMXJd9u9pA+2e977VsZDqdfK0khCY75uqtojl0/ItWlD+sZEtoErJrTClL9KPfR RELA== X-Gm-Message-State: APzg51DN74NUJwsmwFCVZ/uqZ+8HhdVH4luWKYOqEUWg6eRHfecsGD8r ZAwVU3CQUCMq8nLZqS9FeMiy6SyvZBzHxORZAz3e0vEX X-Google-Smtp-Source: ANB0Vda6+PlShlOPCOreGh8foiDczWsEhQg/kX4GSFutSnm17c2CTrafny80r60mbuHII9c7XY8VOV305bWaS2CQn0k= X-Received: by 2002:aca:f0d4:: with SMTP id o203-v6mr1284874oih.21.1535523249243; Tue, 28 Aug 2018 23:14:09 -0700 (PDT) MIME-Version: 1.0 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> <1535501855.1625820.1489435784.68EBD122@webmail.messagingengine.com> In-Reply-To: <1535501855.1625820.1489435784.68EBD122@webmail.messagingengine.com> From: Kevin Oberman Date: Tue, 28 Aug 2018 23:13:52 -0700 Message-ID: Subject: Re: cxl nic not working after reboot To: marius.h@lden.org Cc: freebsd-net , np@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.27 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Aug 2018 06:14:10 -0000 On Tue, Aug 28, 2018 at 5:17 PM Marius Halden wrote: > On Wed, Aug 29, 2018, at 01:50, Kevin Oberman wrote: > > On Tue, Aug 28, 2018 at 1:14 PM Marius Halden 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. > > I do see ARP requests and neighbor solicitations with tcpdump, but not any > replies for either. Though I'm pretty sure that's just a symptom of the > problem and not the root cause considering both ipv4 and ipv6 will start > working again if the SFP is removed and reinserted. > > What is RDP in this context? > > -- > Marius Halden > Router Discovery Protocol. Since you are unable to communicate with the adjacent system, RDP is not relevant. I do agree that this is almost certainly a hardware/driver issue. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683