From: Jay Rolette <rolette@infinite.io>
To: 孙文杰 <findtheonlyway@gmail.com>
Cc: users <users@dpdk.org>
Subject: Re: [dpdk-users] 802.3ad bonding kni ports
Date: Fri, 5 Jun 2020 07:47:38 -0500 [thread overview]
Message-ID: <CADNuJVqcoHgbq1JQnyeXdamKO2DrMTHF71orFyFqEEuAuaLGng@mail.gmail.com> (raw)
In-Reply-To: <CAJkJp4VXBrUU_H-gUxyGmP1TjOQTRrU8PVNHS9Qw=F1Qq+rGfw@mail.gmail.com>
I'm not sure how that would work. LACP is a point-to-point protocol. The
negotiation with the switch for a bond/LAG would be between the switch and
DPDK. KNI is a third-party, so no good way for it to participate directly.
Jay
On Thu, Jun 4, 2020 at 3:58 AM 孙文杰 <findtheonlyway@gmail.com> wrote:
> HI, All.
>
> Now, I bonding two kni ports use mode 802.3ad, and the lacp link
> aggregation
> failed, does kni ports support lacp link aggregation?
>
> error info:
> kernel: bond0: Warning: No 802.3ad response from the link partner for any
> adapters in the bond
>
> bond step:
> ip link del bond0
> ip link add bond0 type bond mode 802.3ad
> ifconfig vnic0 down
> ifconfig vnic1 down
> ifconfig vnic1 hw ether b8:59:9f:1b:01:5a
> ip lin set vnic1 master bond0
> ip lin set vnic0 master bond0
> ifconfig vnic0 up
> ifconfig vnic1 up
> ifconfig bond0 up
>
> bond status:
> Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)
>
> Bonding Mode: IEEE 802.3ad Dynamic link aggregation
> Transmit Hash Policy: layer2 (0)
> MII Status: up
> MII Polling Interval (ms): 0
> Up Delay (ms): 0
> Down Delay (ms): 0
>
> 802.3ad info
> LACP rate: slow
> Min links: 0
> Aggregator selection policy (ad_select): stable
> System priority: 65535
> System MAC address: b8:59:9f:1b:01:5a
> Active Aggregator Info:
> Aggregator ID: 1
> Number of ports: 1
> Actor Key: 0
> Partner Key: 1
> Partner Mac Address: 00:00:00:00:00:00
>
> Slave Interface: vnic1
> MII Status: up
> Speed: Unknown
> Duplex: Unknown
> Link Failure Count: 0
> Permanent HW addr: b8:59:9f:1b:01:5a
> Slave queue ID: 0
> Aggregator ID: 1
> Actor Churn State: none
> Partner Churn State: churned
> Actor Churned Count: 0
> Partner Churned Count: 1
> details actor lacp pdu:
> system priority: 65535
> system mac address: b8:59:9f:1b:01:5a
> port key: 0
> port priority: 255
> port number: 1
> port state: 77
> details partner lacp pdu:
> system priority: 65535
> system mac address: 00:00:00:00:00:00
> oper key: 1
> port priority: 255
> port number: 1
> port state: 1
>
> Slave Interface: vnic0
> MII Status: up
> Speed: Unknown
> Duplex: Unknown
> Link Failure Count: 0
> Permanent HW addr: f6:5e:dc:c3:74:6f
> Slave queue ID: 0
> Aggregator ID: 3
> Actor Churn State: churned
> Partner Churn State: churned
> Actor Churned Count: 1
> Partner Churned Count: 1
> details actor lacp pdu:
> system priority: 65535
> system mac address: b8:59:9f:1b:01:5a
> port key: 0
> port priority: 255
> port number: 2
> port state: 69
> details partner lacp pdu:
> system priority: 65535
> system mac address: 00:00:00:00:00:00
> oper key: 1
> port priority: 255
> port number: 1
> port state: 1
>
next prev parent reply other threads:[~2020-06-05 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 8:57 孙文杰
2020-06-05 12:47 ` Jay Rolette [this message]
2020-06-08 7:32 ` 孙文杰
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=CADNuJVqcoHgbq1JQnyeXdamKO2DrMTHF71orFyFqEEuAuaLGng@mail.gmail.com \
--to=rolette@infinite.io \
--cc=findtheonlyway@gmail.com \
--cc=users@dpdk.org \
/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).