MLAG setup - looks like hitting a L2 loop

[zerodivisionerr]

Hello,

We tried to set up a MLAG between 2 x670 switches and once we enabled the second "leg" (port 41 on sw1) looks like we did hit a loop. Unfortunately it's a production network and we are very limited in opportunities to reproduce it.

MLAG related configs are as follows:

sw1:

code:

create mlag peer "sw2" 
configure mlag peer "sw2" ipaddress 192.168.128.242 vr VR-Default 
enable mlag port 41 peer "sw2" id 202 
enable sharing 41 grouping 41-48 algorithm address-based L2 lacp

sw2:

code:

create mlag peer "sw1" 
configure mlag peer "sw1" ipaddress 192.168.128.241 vr VR-Default 
enable mlag port 41 peer "sw1" id 202 
enable sharing 41 grouping 37-48 algorithm address-based L2 lacp

MLAG peers see each other, checkpoint status is 'Up'. What caught my attention is this. On sw1:

code:

sw1.118 # debug hal show vsm 

VSM Blocking Filters:
  Ingress port: 1:1
    Blocked ports:
      Unit 1 (inst 1 Fid A553 l3_inst 1 l3_Fid A551 l3rem_inst 1 l3rem_Fid A552 pend 0):
           41 42 43 44 45 46 47 48 

VSM Redirection: (Enabled)

But on sw2:

code:

sw2.29 # debug hal show vsm 

VSM Blocking Filters:
  Ingress port: 1:1
    Blocked ports:

VSM Redirection: (Enabled)

Could this be the cause of the problem (that there're no blocked ports for the filter)? If so, why they could've not been added?

Both switches are running 16.2.4.5-patch1-6.

[FES]

Hi,
i have used the EXOS MLAG script to test the mlag configuration. The problems (seems like loops) apprears randomly and we dont know why.

We have updated to 30.2.1.8 to ensure that is not a bug. Otherwise we have seen a protocol to view mlag loops in this new version.

[Brian_Anderson1]

Did you add the ISC vlan to the ports between the switches?

https://gtacknowledge.extremenetworks.com/articles/How_To/How-to-configure-MLAG-in-Extreme-switches/...

[Tomasz]

Hi FES,

Is that a two-tier MLAG design?
If 'show mlag peer' and 'show mlag port' and 'show sharing' are all good, is it possible that the loop is introduced elsewhere in the network (even on non-MLAG-considered VLAN) and hits the switches? You say that the loop doesn't happen at the moment but in days - is that loop happening randomly or was the test performed a while ago?

Kind regards,
Tomasz

[FES]

Hi, we have the same problem with a pair of x870 devices conected to another pair of x690. The firmware version running is 22.6.1.4

We have cheked mlag configuration running the mlag script and its all ok.

Also we have tested x870 with 30.2.1.8 versión connected to a pair of x690 with 22.6.1.4 and the loop behaviour is produced again (not at the moment but in days).

The next test is upgrading all the 4 switches to 30.2.1.8.

[jeronimo]

What does "show mlag peer" and "show mlag port" on both switches show?

Can you draw a network map of what you're trying to accomplish?

You created LAGs using ports 41-48 on one switch, and 37-48 on the other. Are you sure that is correct?

BTW 16.2 is end of service life in December. You should consider upgrading.