From: David Ahern <dsa@cumulusnetworks.com>
To: AMG Zollner Robert <robert@cloudmedia.eu>, ganeshgr@chelsio.com
Cc: netdev@vger.kernel.org
Subject: Re: [bug] cxgb4: vrf stopped working with cxgb4 card
Date: Mon, 4 Jun 2018 11:17:58 -0700 [thread overview]
Message-ID: <8073c78c-3243-d7f3-55c3-2cc1a2153366@cumulusnetworks.com> (raw)
In-Reply-To: <b515a1c7-2cf8-1af8-372d-393420d298b8@cloudmedia.eu>
On 6/4/18 8:03 AM, AMG Zollner Robert wrote:
> I have noticed that vrf is not working with kernel v4.15.0 but was
> working with v4.13.0 when using cxgb4 Chelsio driver (T520-cr)
>
> Setup:
> Two metal servers with a T520-cr card each, directly connected without a
> switch in between.
>
> SVR1 only ipfwd SVR2 with vrf
> .----------------------------. .----------------------------------.
> | | | |
> | 192.168.8.1 [ ens2f4]--|---------|--[ens1f4] 192.168.8.2 |
> | 192.168.9.1 [ens2f4d1]--|---------|--<ens1f4d1> 192.168.9.2 VRF=10 |
> `----------------------------' `----------------------------------'
>
> When vrf is not working there are no error messages (dmesg or iproute
> commands), tcpdump on the interface (SVR2.ens1f4d1) enslaved in vrf 10
> shows packets(arp req/reply) coming in and going out, but outgoing
> packets(arp reply) do not reach the other server SVR1.ens2f4d1
>
>
> Bisect:
> Found this commit to be the problem after doing a git bisect between
> v4.13..v4.15:
>
> commit ba581f77df23c8ee70b372966e69cf10bc5453d8
> Author: Ganesh Goudar <ganeshgr@chelsio.com>
> Date: Sat Sep 23 16:07:28 2017 +0530
>
> cxgb4: do DCB state reset in couple of places
>
> reset the driver's DCB state in couple of places
> where it was missing.
>
>
> A bisect step was considered good when:
> - successful ping from SVR1 to SVR2.ens1f4d1 vrf interface
> - successful ping from SVR2 global to SVR2 vrf interface trough SVR1(l3
> forwarding) (this check was redundant,both tests fail or pass simultaneous)
>
> The problem is still present on recent kernels also, checked v4.16.0 and
> v4.17.rc7
>
> Disabling DCB for the card support fixes the problem ( Compiling kernel
> with "CONFIG_CHELSIO_T4_DCB=n")
>
Are you doing the VRF enslave while it is up?
If so, does it work ok if you change the sequence:
ip li set ens1f4d1 down
ip li set ens1f4d1 master <VRF>
ip li set ens1f4d1 up
next prev parent reply other threads:[~2018-06-04 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-04 15:03 [bug] cxgb4: vrf stopped working with cxgb4 card AMG Zollner Robert
2018-06-04 18:17 ` David Ahern [this message]
2018-06-04 20:14 ` AMG Zollner Robert
2018-06-04 20:35 ` David Ahern
2018-06-10 0:47 ` David Ahern
2018-06-11 9:17 ` Ganesh Goudar
[not found] ` <20180619132425.GA6576@chelsio.com>
2018-06-19 20:32 ` AMG Zollner Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8073c78c-3243-d7f3-55c3-2cc1a2153366@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=ganeshgr@chelsio.com \
--cc=netdev@vger.kernel.org \
--cc=robert@cloudmedia.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).