Multiple LACP bonds have the same Aggregator ID

Solution Verified - Updated -

Issue

  • Multiple LACP bonds have the same Aggregator ID
  • In /proc/net/bonding/bond* all 802.3ad bonds have negotiated to the same Aggregator ID in the Active Aggregator section
/proc/net/bonding/bond0

Active Aggregator Info:
    Aggregator ID: 1
    Number of ports: 2
    Actor Key: 9
    Partner Key: 44
    Partner Mac Address: 20:4e:71:aa:aa:aa

/proc/net/bonding/bond1

Active Aggregator Info:
    Aggregator ID: 1
    Number of ports: 2
    Actor Key: 11
    Partner Key: 43
    Partner Mac Address: 20:4e:71:bb:bb:bb
  • Debugging bonding shows two bonds joining the same LAG:
bond0: Port 1 joined LAG 5(new LAG)
bond0: LAG 5 chosen as the active LAG
bond0: Port 2 joined LAG 5(existing LAG)
bond0: Port 4 joined LAG 5(existing LAG)
bond0: Port 3 joined LAG 5(existing LAG)
...
bond1: Port 1 joined LAG 5(new LAG)
bond1: LAG 5 chosen as the active LAG
bond1: Port 2 joined LAG 5(existing LAG)
bond1: Port 3 joined LAG 5(existing LAG)
bond1: Port 4 joined LAG 5(existing LAG)

Environment

  • Red Hat Enterprise Linux
  • Bonding mode 4 (aka 802.3ad aka LACP)

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.