Extreme Networks

cpacho · ‎03-31-2021

Hello;

I have configured an MLAG between 2 X590 routers with a double LACP link between them. This is my configuration:
R1:
create vlan "MANAGE"
configure vlan MANAGE tag 1000
create vlan "MLAG_CORE"
configure vlan MLAG_CORE tag 250
configure ports 29 description-string "LINK_R-A52_Port_29_VRRP"
enable sharing 29 grouping 29.33 algorithm address-based L2 lacp
configure vlan MANAGE add ports 1-32,34-36 untagged
configure vlan MLAG_CORE add ports 29 tagged
configure vlan MANAGE ipaddress 10.1.0.251 255.255.0.0
enable ipforwarding vlan MANAGE
configure vlan MLAG_CORE ipaddress 10.250.0.1 255.255.255.252
create mlag peer "CORE"
configure mlag peer "CORE" ipaddress 10.250.0.2 vr VR-Default
configure mlag peer "CORE" lacp-mac 00:04:96:e5:17:94
enable mlag port 22 peer "CORE" id 1

R2:
create vlan "MANAGE"
configure vlan MANAGE tag 1000
create vlan "MLAG_CORE"
configure vlan MLAG_CORE tag 250
configure ports 29 description-string "LINK_R-A52_Port_29_VRRP"
enable sharing 29 grouping 29.33 algorithm address-based L2 lacp
configure vlan MANAGE add ports 1-32,34-36 untagged
configure vlan MLAG_CORE add ports 29 tagged
configure vlan MANAGE ipaddress 10.1.0.252 255.255.0.0
enable ipforwarding vlan MANAGE
configure vlan MLAG_CORE ipaddress 10.250.0.2 255.255.255.252
create mlag peer "CORE"
configure mlag peer "CORE" ipaddress 10.250.0.1 vr VR-Default
configure mlag peer "CORE" lacp-mac 00: 04: 96: e5: 17: 94
enable mlag port 22 peer "CORE" id 1

This is the command output (same on both routers)

R1#show mlag peer
Multi-switch Link Aggregation Peers:

MLAG Peer : CORE
VLAN : MLAG_CORE Virtual Router : VR-Default
Local IP Address : 10.250.0.2 Peer IP Address : 10.250.0.1
MLAG ports : 1 Tx-Interval : 1000 ms
Checkpoint Status : Up Peer Tx-Interval : 1000 ms
Rx-Hellos : 98878 Tx-Hellos : 98880
Rx-Checkpoint Msgs: 4943 Tx-Checkpoint Msgs: 4872
Rx-Hello Errors : 0 Tx-Hello Errors : 0
Hello Timeouts : 0 Checkpoint Errors : 0
Up Time : 1d:2h:54m:59s Peer Conn.Failures: 0
Local MAC : 00:04:96:e5:17:94 Peer MAC : 00:04:96:e5:17:22
Config'd LACP MAC : 00:04:96:e5:17:94 Current LACP MAC : 00:04:96:e5:17:94
Authentication : None

Alternate path information: None

R1#sh mlag ports

Local Local Remote
MLAG Local Link Remote Peer Fail Fail
Id Port State Link Peer Status Count Count
================================================================================
1 22 A Up CORE Up 0 0
================================================================================
Local Link State: A - Active, D - Disabled, R - Ready, NP - Port not present
Remote Link : Up - One or more links are active on the remote switch,
Down - No links are active on the remote switch,
N/A - The peer has not communicated link state for this MLAG port,
Virtual - MLAG peer switch does not have physical port.

Number of Multi-switch Link Aggregation Groups : 1
Convergence control : Conserve Access Lists
Reload Delay Interval : 30 seconds
Reload Delay : Disabled
Link Up Isolation : Off

This is the configuration of my switches stack
SW1-stack
configure snmp sysName "SW-A51"
configure snmp sysContact "https://www.extremenetworks.com/support/"
configure slot 1 module X450G2-48p-10G4
configure sys-recovery-level slot 1 reset
configure slot 2 module X450G2-48p-10G4
create vlan "MANAGE"
configure vlan MANAGE tag 1000
enable sharing 1:52 grouping 1: 52,2: 52 algorithm address-based L2 lacp
configure vlan MANAGE add ports 1: 1-52,2: 1-51 untagged
configure vlan MANAGE ipaddress 10.1.0.241 255.255.0.0
enable ipforwarding vlan MANAGE

Slot-1 SW-A51.2 # sh lacp

LACP Up : Yes
LACP Enabled : Yes
System MAC : 02:04:96:e3:eb:d8
LACP PDUs dropped on non-LACP ports : 0

Lag Actor Actor Partner Partner Partner Agg
Sys-Pri Key MAC Sys-Pri Key Count
--------------------------------------------------------------------------------
1:52 0 0x041c 00:00:00:00:00:00 0 0x0000 0
================================================================================

* Slot-1 SW-A51.3 # sh lacp
<cr> Execute the command
counters Counters
lag LACP user defined LAG (link agg group)
member-port Member port of the LACP trunk
| Filter the output of the command

sh lacp counters

LACP PDUs dropped on non-LACP ports : 0
LACP Bulk checkpointed msgs sent : 1
LACP Bulk checkpointed msgs recv : 0
LACP PDUs checkpointed sent : 0
LACP PDUs checkpointed recv : 0

Lag Member Rx Rx Drop Rx Drop Rx Drop Tx Tx
Group Port Ok PDU Err Not Up Same MAC Sent Ok Xmit Err
--------------------------------------------------------------------------------
1:52 1:52 0 0 0 0 3150 0
2:52 0 0 0 0 2993 0

================================================================================

Slot-1 SW-A51.10 # sh lacp lag 1:52

Lag Actor Actor Partner Partner Partner Agg Actor
Sys-Pri Key MAC Sys-Pri Key Count MAC
--------------------------------------------------------------------------------
1:52 0 0x041c 00:00:00:00:00:00 0 0x0000 0 02:04:96:e3:eb:d8

Port list:

Member Port Rx Sel Mux Actor Partner
Port Priority State Logic State Flags Port
--------------------------------------------------------------------------------
1:52 0 Defaulted Unselected Detached A-G---F- 0
2:52 0 Defaulted Unselected Detached A-G---F- 0
================================================================================
Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization
C-Collecting, D-Distributing, F-Defaulted, E-Expired

the problem I have is that there is no ping response from the routers to the switch stack.

Can anybody help me??
Thanks

Chris_H · ‎04-01-2021

your edge-switch has LACP for the uplinks configured (1:52 and 2:52), but your core-switches don’t have LACP on the port 22 configured, which seems to be the MLAG port… that’s why the edge-switch shows no RX LACP frames, but only TX in your “show lacp counter” output and the aggregation doesn’t come up..

you need to “enable sharing 22 grouping 22 algorithm address-based l2 lacp” to enable LACP on port 22 on each of the cores and then add the port again to the VLAN..

View solution in original post

Stefan_K_ · ‎03-31-2021

Hello,

a few things…

The problem is that you can’t ping from Edge-Switch to the routers when you are sitting on the switch via SSH/Telnet, right? Did you specify the VR?
```
ping vr vr-default 10.1.0.251
```
You don’t have to enable ipforwarding for the Mgmt-VLAN on the Edge-Switches.
Do you really need a /16 subnet for the Mgmt-VLAN?
I like to use an MLAG ID that matches the used port (e.g. for port 1:22 I would use MLAG ID 122, for Port 2:6 I would use ID 206.) But this is just an cosmetic hint, technically you can of course use MLAG ID on Port 22.

Extreme Networks

MLAG-LACP

MLAG-LACP