DPDK usage discussions
 help / color / Atom feed
* [dpdk-users] 802.3ad bonding kni ports
@ 2020-06-04  8:57 孙文杰
  2020-06-05 12:47 ` Jay Rolette
  0 siblings, 1 reply; 3+ messages in thread
From: 孙文杰 @ 2020-06-04  8:57 UTC (permalink / raw)
  To: users

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] 802.3ad bonding kni ports
  2020-06-04  8:57 [dpdk-users] 802.3ad bonding kni ports 孙文杰
@ 2020-06-05 12:47 ` Jay Rolette
  2020-06-08  7:32   ` 孙文杰
  0 siblings, 1 reply; 3+ messages in thread
From: Jay Rolette @ 2020-06-05 12:47 UTC (permalink / raw)
  To: 孙文杰; +Cc: users

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
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [dpdk-users] 802.3ad bonding kni ports
  2020-06-05 12:47 ` Jay Rolette
@ 2020-06-08  7:32   ` 孙文杰
  0 siblings, 0 replies; 3+ messages in thread
From: 孙文杰 @ 2020-06-08  7:32 UTC (permalink / raw)
  To: Jay Rolette; +Cc: users

Ok, thanks for the clarification.   Nic information is  support for KNI
just when physic nic  is ixgbe or igb, so bond cannot get the KNI
information such as speed, so the lacp negotiation unsuccessful。

Jay Rolette <rolette@infinite.io> 于2020年6月5日周五 下午8:47写道:

> 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
>>
>

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-06-04  8:57 [dpdk-users] 802.3ad bonding kni ports 孙文杰
2020-06-05 12:47 ` Jay Rolette
2020-06-08  7:32   ` 孙文杰

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox