Question

Trouble with new cumulus OS version


Hello,
I recently upgraded my EdgeCore switches 2.5.7 to 3.7.0
The problem is that the old configurtation does not work with the new OS version.
In the config file we just have LACP MLAG and some vlan
Do you have any idea on the issue ?
Thank you.
best Regards.

11 replies

Userlevel 5
There were some very large changes between those versions. But if you're just using L2 features most of that should still work as it used to in 2.5.7.

Do you have any specific error messages for us to look at?
What are the symptoms of the configuration not working?
Hello Eric,

Since we have updated our EdgeCore switches in 3.7, we can't do LACP between EdgeCore and new switches (Huawei).

Seems well configured on Huawei.

The MLAG between EdgeCore1 and EdgeCore2 is ok:
_I can ping EdgeCore2 from EdgeCore1 and EdgeCore1 from Edgecore2.
_From a PC on EdgeCore1, I can ping an other PC on EdgeCore2 through vlan 3010

This is the MLAG conf :

"# MLAG Peer-Link
auto peer-link
iface peer-link
bond-slaves swp51 swp52
bond-mode 802.3ad
bond-min-links 1
bond-miimon 100
bond-lacp-rate 1
bond-xmit-hash-policy layer3+4
mtu 9000

# MLAG Peer-Interface
auto peer-link.4094
iface peer-link.4094
address 169.254.1.1/30
clagd-priority 8192
clagd-peer-ip 169.254.1.2
clagd-sys-mac 44:38:39:ff:ff:01
mtu 9000"

But we can't ping ip our Huawei Swithes or anything on Huawei Switches.

This is our conf in EdgeCore1:
"auto lacp-swp3
iface lacp-swp3
bond-slaves swp3
bond-mode 802.3ad
bond-min-links 1
bond-miimon 100
bond-use-carrier 1
bond-lacp-rate 1
bond-xmit-hash-policy layer3+4
mstpctl-bpduguard yes
mtu 9000
clag-id 3
bridge-vids 114 1000 3010 3011 3012 3013 3014"

and EdgeCore2:
"auto lacp-swp3
iface lacp-swp3
bond-slaves swp3
bond-mode 802.3ad
bond-min-links 1
bond-miimon 100
bond-use-carrier 1
bond-lacp-rate 1
bond-xmit-hash-policy layer3+4
mstpctl-bpduguard yes
mtu 9000
clag-id 3
bridge-vids 114 1000 3010 3011 3012 3013 3014"

Best Regards
This is a net show of our lacp interface, I don't know what does mean "ADMDN" :


"root@sw-ec-2:~# net show interface lacp-swp3
Name MAC Speed MTU Mode
----- --------- ----------------- ----- ---- -------
ADMDN lacp-swp3 cc:37:ab:a0:a0:c3 N/A 9000 802.3ad

Bond Details
------------------ --------
Bond Mode: 802.3ad
Load Balancing: layer3+4
Minimum Links: 1
LACP Sys Priority:
LACP Rate: 1
LACP Bypass: Inactive

All VLANs on L2 Port
--------------------
1,114,1000,3010-3015

Untagged
--------
1

LLDP Details
------------
LocalPort RemotePort(RemoteHost)
--------- ----------------------
swp3 g1(None)
"

Thank you.
Best Regards
Userlevel 5
What ports connect to the other switch?
Is the link up (output from `net show interface`)?
What does CLAG say about the link (output from `net show clag`)
This is the output of net show clag:

code:
root@sw-ec-1:~# net show clag
The peer is alive
Peer Priority, ID, and Role: 8192 cc:37:ab:a0:a0:f3 primary
Our Priority, ID, and Role: 8192 cc:37:ab:a0:a2:33 secondary
Peer Interface and IP: peer-link.4094 169.254.1.2
Backup IP: (inactive)
System MAC: 44:38:39:ff:ff:01

CLAG Interfaces
Our Interface Peer Interface CLAG Id Conflicts Proto-Down Reason
---------------- ---------------- ------- -------------------- -----------------
lacp-swp50 - 50 - -
lacp-swp49 - 49 - -
lacp-swp3 - 3 - -



Swp3 on each EdgeCore connect to other switch
Userlevel 5
What does `sudo cat /proc/net/bonding/lacp-swp3` show on each device?
Hi,
I'm his co-worker

code:
root@sw-ec-1:~# cat /proc/net/bonding/lacp-swp3
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: up
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: 44:38:39:ff:ff:01
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 9
Partner Key: 49
Partner Mac Address: a4:ba:db:92:22:17

Slave Interface: swp3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 2
Permanent HW addr: cc:37:ab:a0:a2:03
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 2
Partner Churned Count: 3
details actor lacp pdu:
system priority: 65535
system mac address: 44:38:39:ff:ff:01
port key: 9
port priority: 255
port number: 1
port state: 63
details partner lacp pdu:
system priority: 1
system mac address: a4:ba:db:92:22:17
oper key: 49
port priority: 1
port number: 2
port state: 61


Userlevel 5
This one looks healthy, how about the other switch?

Also what does `ip -d link show` look like on each switch?
Hi,

On the other switch, it seem similar :

code:
root@sw-ec-2:~# cat /proc/net/bonding/lacp-swp3
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: up
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: 44:38:39:ff:ff:01
Active Aggregator Info:
Aggregator ID: 1
Number of ports: 1
Actor Key: 9
Partner Key: 49
Partner Mac Address: a4:ba:db:92:22:17

Slave Interface: swp3
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: cc:37:ab:a0:a0:c3
Slave queue ID: 0
Aggregator ID: 1
Actor Churn State: monitoring
Partner Churn State: monitoring
Actor Churned Count: 0
Partner Churned Count: 0
details actor lacp pdu:
system priority: 65535
system mac address: 44:38:39:ff:ff:01
port key: 9
port priority: 255
port number: 1
port state: 63
details partner lacp pdu:
system priority: 1
system mac address: a4:ba:db:92:22:17
oper key: 49
port priority: 1
port number: 1
port state: 61
I'm wondering what meens ADMDN in the net show interface command ?
Userlevel 4
@AOUCH ADMDN means ADMIN DOWN, the interface was taken down administratively.

You could do this with ifdown `sudo ifdown --admin-state swp1`

Reply