A LAG is when you are using one or more interfaces on the same device, like your ISL on the VSX members or on the "single device" switches in your lab.
Original Message:
Sent: Aug 24, 2024 04:36 PM
From: barisben
Subject: Aruba AOS-CX in EVE-NG LACP Blocked Issue 10.09
Thank you so much. I made a change in the topology because there was a mistake. The change is SW-L3-A-2 1/1/4 port to Kat-1-L2. It was 1/1/4 to Kat-1-2-L2. When I create multi-chassis lags on L3s and normal lags on L2s everything worked well. Now I want to know why, could you please explain it to me. The first thing is we create mclags on L3s and the second is normal lags on L2s. Why we needed to create MCLAGs on L3s and why we dont needed to create MCLAGs on L2s?
This is what I do and works like a charm;
SW-L3-A-1 and SW-L3-A-2 configs;
interface lag 1 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 2 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 3 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 4 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 5 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 256
no shutdown
description ISL
no routing
vlan trunk native 1 tag
vlan trunk allowed all
lacp mode active
interface 1/1/2
no shutdown
lag 3
interface 1/1/3
no shutdown
lag 4
interface 1/1/4
no shutdown
lag 5
interface 1/1/5
no shutdown
lag 1
interface 1/1/6
no shutdown
lag 2
and Kat-1-L2, Kat-2-L2, Kat-3-L2 configs;
interface lag 1
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface 1/1/3
no shutdown
lag 1
interface 1/1/4
no shutdown
lag 1
Original Message:
Sent: Aug 24, 2024 08:27 AM
From: ArneO
Subject: Aruba AOS-CX in EVE-NG LACP Blocked Issue 10.09
Hi,
Do you have MC LAG at the Fortigates? If you don't have MCLAG at the FortiGates yoy need it an the CX side.
interface lag 1 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface lag 2 multi-chassis
no shutdown
no routing
vlan trunk native 1
vlan trunk allowed all
lacp mode active
interface 1/1/5
no shutdown
lag 1
interface 1/1/6
no shutdown
lag 2
Without spanning-tree yout L2 topology creates loop.
And the simulators don't have a functional STP, it forwards packets out on blocked interfaces.
On Kat-2 and Kat-3 you may create a LAG and a MCLAG on your VSX to avoid the loop.
On Kat-1-2 you must remove one of the links to upstream switch becase you cant avoid to create a loop there.
------------------------------
Arne Opdal
Original Message:
Sent: Aug 23, 2024 03:25 AM
From: barisben
Subject: Aruba AOS-CX in EVE-NG LACP Blocked Issue 10.09
Hey! I have a topology as follows; There is HA between FortiGates and there is Aggregate that contains VLANs on port5-port6 and no problem with the config for sure. And Kat-1-L2, Kat-2-L2, Kat-3-L2, Kat-1-2-L2 switches has all vlans and trunks configured well. So no problem with them. SW-L3-A-1 has vsx between SW-L3-A-2. If I don't start SW-L3-A-2 there is no problem, every switch can access each other but if I start it then all lacp ports blocking and nothing works. I have no idea why. L3-A-1 and L3-A-2 configs in the below. (LAG256 was working very well when only Fortigates and SW-L3-A-1, SW-L3-A-2 works. When I start L2 Switches then it stopped)
This is what "sh lacp int" says when I start A-2;