Page 1 of 1

L2 loop protection on a not mananaged switch.

Posted: Mon Jun 01, 2015 5:18 pm
by leostereo
Hello , guys , as tittle says, I need to protect my network against L2 loops produced by an unmanaged switch.

The loop occurs when some one connects tho ports of same switch with a cable (see picture bellow).
I would like to be able to shutdown the port of my managed mikrotik when the loop occurs.
I have been testing with stp running on my managed switch but have no luck so far.
Edge port feature would help ?
It is very critical situation, since when loop ocurs I have a broadcast and arp storm flooding my network, and also have many mac address flapping on upstream switches.
I know I can limit broadcast storm but I would like to shutdown the port.
Take a look bellow:
external_protection_mini.png

Re: L2 loop protection on a not mananaged switch.

Posted: Tue Jun 02, 2015 3:30 am
by chechito
on a CRS switch can be implemented, but on integrated switch on RB751 or rb951 dont know how to do it or if can be

Re: L2 loop protection on a not mananaged switch.

Posted: Tue Jun 02, 2015 4:53 pm
by leostereo
Chechito , i dont understand your comment, could you be more clear?
Witch feature are you refering at?
Do you think is there any especific mechanism to handle my problem ?
Thanks for your response.
Leandro.

Re: L2 loop protection on a not mananaged switch.

Posted: Tue Jun 02, 2015 7:47 pm
by chechito
Chechito , i dont understand your comment, could you be more clear?
Witch feature are you refering at?
Do you think is there any especific mechanism to handle my problem ?
Thanks for your response.
Leandro.
loop protection can be implemented on mikrotik CRS switches using inbound broadcast limit rate and drop dynamic move on ports.

on integrated switches on little mikotiks i dont see that features

Re: L2 loop protection on a not mananaged switch.

Posted: Fri Jun 05, 2015 6:37 pm
by leostereo
Very strange ... I performed same test replacing mikrotik for another switch witch rstp feature and it worked as espected, it takes half second to detect the loop condition and move the port to "bloqued" state.
I think that switch notice the loop condition when he receives a bpdu over the same port it was sended.
I can not get same result with my mikrotik yet.

Re: L2 loop protection on a not mananaged switch.

Posted: Fri Jun 05, 2015 8:44 pm
by chechito
maybe using static host mapping on switch can help a little to mitigate the situation preventing the mac flapping on mikrotik fsb poisoning and amplifying the storm.