NIC Teaming via NMTUI with mode 802.3AD
Hi Everyone,
Would like to ask if the setup of this is correct as this was configured only using the nmtui. As checked it seems like that the traffic only flows on one of the ethernet ports. however the mode is already 802.3 AD The expected output is that the expected traffic will flow both on the 2 slaves. For your guys help or recommendation.
cat /proc/net/bonding/bond1
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): 100
Up Delay (ms): 0
Down Delay (ms): 0
Peer Notification Delay (ms): 0
802.3ad info
LACP active: on
LACP rate: slow
Min links: 0
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 00:0c:29:71:8f:d6
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 15
Partner Key: 15
Partner Mac Address: 00:0c:29:92:7f:3b
Slave Interface: ens192
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:71:8f:d6
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: none
Partner Churn State: none
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 00:0c:29:71:8f:d6
port key: 15
port priority: 255
port number: 1
port state: 61
details partner lacp pdu:
system priority: 65535
system mac address: 00:0c:29:92:7f:3b
oper key: 15
port priority: 255
port number: 1
port state: 61
Slave Interface: ens224
MII Status: up
Speed: 10000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:0c:29:71:8f:e0
Slave queue ID: 0
Aggregator ID: 2
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: 00:0c:29:71:8f:d6
port key: 15
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
Responses
It looks like only one of the NICs is receiving LACPDUs. Check the switch config.
I'm not sure what you mean.
There are two switchports which are plugged into the NICs on the system.
On the switch, those switchports need to be entered into a link aggregation bundle, and the bundle set to LACP mode.
In other words, you need an LACP bond on the switch as well. Just switch vendors use a different term for it.
If you can't configure your switch that way, then LACP can't be used.
It's been a long time since I've done any Cisco stuff but according to some documentation a Static LAG is a link aggregation group without LACP.
The bonding equivalent of that is Mode 2 aka balance-xor. That performs the transmit hashing using the xmit_hash_policy bonding option without LACP.
You need to configure the switch with a similar traffic load balancing, so that all switchports are used for transmit from the switch.
For example, if you have the bond considering the L3 header for transmit balancing with xmit_hash_policy=layer2+3, then you should do a similar configuration on the switch so that it also balances by the L3 header.