MLAN setup under Cumulus VX


Userlevel 1
Hello,

I am similar MLAN which is using GNS 3 now with Cumulus VX 3.1 which running Virtual Box now. With reference to
https://docs.cumulusnetworks.com/display/DOCS/Multi-Chassis+Link+Aggregation+-+MLAG?_ga=1.215073879....

but still fail to setup. Also, some other discuss
https://community.cumulusnetworks.com/cumulus/topics/cumulus-vx-support-mlag

looks have some problem there. Is it under MLAN is known problem under GNS 3?

Following is my config.

-- Switch 1 ---

auto eth0
iface eth0

auto swp1
iface swp1

auto swp2
iface swp2

auto peerlink
iface peerlink
bond-slaves swp1 swp2
clag-id 1

auto peerlink.4094
iface peerlink.4094
address 169.254.255.1/24
clagd-priority 4096
clagd-peer-ip 169.254.255.2
clagd-args --vm
clagd-sys-mac 44:38:39:ff:00:01

--- Switch 2 ---

auto eth0
iface eth0

auto swp2
iface swp2

auto swp4
iface swp4

auto peerlink
iface peerlink
bond-slaves swp2 swp4
clag-id 1

auto peerlink.4094
iface peerlink.4094
address 169.254.255.2/24
clagd-priority 8192
clagd-peer-ip 169.254.255.1
clagd-args --vm
clagd-sys-mac 44:38:39:ff:00:01

-------------------------------------------------
# check the status $ sudo clagctl
The peer is not alive
Our Priority, ID, and Role: 4096 08:00:27:13:01:a4 secondary
Peer Interface and IP: peerlink.4094 169.254.255.2
Backup IP: (inactive)
System MAC: 44:38:39:ff:00:01

CLAG Interfaces
Our Interface Peer Interface CLAG Id Conflicts Proto-Down Reason
---------------- ---------------- ------- -------------------- -----------------
peerlink - 1 - -

=======================================
Also it keep to have error find at Switch 1

[ 2013.570133] peerlink: An illegal loopback occurred on adapter (swp1)
[ 2013.570133] Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports bond-mode 802.3ad

======================================
Please advise how to trace the problem.

Thanks!

7 replies

Userlevel 4
the peerlink should not have a clag-Id associated with it. The clag-Id is only for dual connected hosts. I am pretty confident that is the problem you are having.
Userlevel 4
Agree with Sean. This message "peerlink: An illegal loopback occurred on adapter (swp1)" means they're each presenting the same MAC address and hence the bond will not form because it thinks you're asking it to bond with itself.
Userlevel 3
Machi,

Thanks for giving Cumulus VX a try. You might want to go back and re-read the MLAG documentation again. There are several issues with the configuration you posted.
  • Firstly, like Sean and Eric said, the peerlink should not have a clag-id assigned to it.
  • Secondly, you should create a bridge in each switch.
  • Thirdly, the links to the dual connected hosts should be placed in bonds and the same clagd-id should be assigned to bonds connected to the same hosts. Also, those bonds should be added as members of the bridge.
The documentation has fairly detailed configuration examples to guide you through each of these things: https://docs.cumulusnetworks.com/display/DOCS/Multi-Chassis+Link+Aggregation+-+MLAG

Userlevel 1
Hello,

Thanks all those material. However, I still get stuck now. Following please find my latest config.

1. removed clag-id
2. Added bridge binding peerlink
3. Not understand your meaning? peerlink is bonds already?

Could you please guide me more details?

-------- switch 1 -----

auto swp1
iface swp1

auto swp2
iface swp2

auto peerlink
iface peerlink
bond-slaves swp1 swp2

auto peerlink.4094
iface peerlink.4094
address 169.254.255.1/24
clagd-priority 4096
clagd-peer-ip 169.254.255.2
# clagd-backup-ip 10.0.0.2
clagd-sys-mac 44:38:39:ff:00:01
clagd-args --vm

auto br0
iface br0
# bridge-vlan-aware yes
bridge-ports peerlink
bridge-stp on
bridge-vids 1000-2999
bridge-pvid 1
mstpctl-treeprio 4096

--------- switch 2 -------------------

auto swp2
iface swp2

auto swp4
iface swp4

auto peerlink
iface peerlink
bond-slaves swp2 swp4

auto peerlink.4094
iface peerlink.4094
address 169.254.255.2/24
clagd-priority 8192
clagd-peer-ip 169.254.255.1
# clagd-backup-ip 10.0.0.1
clagd-sys-mac 44:38:39:ff:00:01
clagd-args --vm

auto br0
iface br0
# bridge-vlan-aware yes
bridge-ports peerlink
bridge-stp on
bridge-vids 1000-2999
bridge-pvid 1
mstpctl-treeprio 4096
------------------------

Thanks!
Userlevel 4
Hey machiasiaweb,

The peerlink config looks right. You don't need the clagd-args --vm if you are using a recent release of Cumulus VX, it is now smart enough to know its running on a VM. I have done this on 2.5.7 and newer and not had problems.

Where the mis-config now is you are mixing up the linux bridge modes. There are two 'modes' for the Linux bridge. VLAN-aware and traditional. The bridge-vids and bridge-pvid are keywords to be used in the vlan-aware mode but you have commented this line out->bridge-vlan-aware yes.

Check out this KB: https://support.cumulusnetworks.com/hc/en-us/articles/204909397-Comparing-Traditional-Bridge-Mode-to...

What is the error you are seeing? I imagine its barking at the keywords under the bridge.

Userlevel 1
Hello,

That's great of that KB and now I have more clear about two types of Bridge mode.

I have updated the config like below but rebuild the whole testing environment.

Unfortunately still fail there.

-------- switch 1 -----

auto swp2
iface swp2

auto swp3
iface swp3

auto peerlink
iface peerlink
bond-slaves swp2 swp3

auto peerlink.4094
iface peerlink.4094
address 169.254.255.1/24
clagd-priority 4096
clagd-peer-ip 169.254.255.2
# clagd-backup-ip 10.0.0.2
clagd-sys-mac 44:38:39:ff:00:01

auto br0
iface br0
bridge-vlan-aware yes
bridge-ports peerlink
bridge-stp on
bridge-vids 1000-2999
bridge-pvid 1
mstpctl-treeprio 4096

--------- switch 2 -------------------

auto swp2
iface swp2

auto swp3
iface swp3

auto peerlink
iface peerlink
bond-slaves swp2 swp3

auto peerlink.4094
iface peerlink.4094
address 169.254.255.2/24
clagd-priority 8192
clagd-peer-ip 169.254.255.1
# clagd-backup-ip 10.0.0.1
clagd-sys-mac 44:38:39:ff:00:01

auto br0
iface br0
bridge-vlan-aware yes
bridge-ports peerlink
bridge-stp on
bridge-vids 1000-2999
bridge-pvid 1
mstpctl-treeprio 4096
------------------------

I find that the peerlink bond looks did not work fine too.

Please find the following output.

--------------------------
sudo cat /proc/net/bonding/peerlink

Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011)

Bonding Mode: IEEE 802.3ad Dynamic link aggregation
Transmit Hash Policy: layer3+4 (1)
MII Status: down <-------- down
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

802.3ad info
LACP rate: fast
Min links: 1
Aggregator selection policy (ad_select): stable
System priority: 65535
System MAC address: 08:00:27:13:01:a4
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 9
Partner Key: 1
Partner Mac Address: 00:00:00:00:00:00

Slave Interface: swp2
MII Status: up <--------
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:13:01:a4
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 08:00:27:13:01:a4
port key: 9
port priority: 255
port number: 1
port state: 207
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: 3

Slave Interface: swp3
MII Status: up <------
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 08:00:27:5c:43:32
Slave queue ID: 0
Aggregator ID: 2
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 1
Partner Churned Count: 1
details actor lacp pdu:
system priority: 65535
system mac address: 08:00:27:13:01:a4
port key: 9
port priority: 255
port number: 2
port state: 199
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: 3
----------------------------------------------

and still keep got error
[11174.661756] peerlink: An illegal loopback occurred on adapter (swp3)
[11174.661756] Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports

could you please advise what can I do to trace the problem?

Thanks!

Userlevel 1
Finally it can resolved by change all interface MAC address. It is because all MAC is same during import into VirtualBox.

That's why even the Bonding connection has problem.

Thanks for all support.

Reply