Broadcast Storm

[strawberry]

We've recently had a student loopback a cable into an unmanaged switch ( SW1), unforautnely I flattened the managed switch (SW2) it was plugged into. Should / Would loop protection protect against this or does it only work on the switch itself? Edited October 23, 2014 by Dos_Box

[jamesb]

Depending on the version. I believe most modern switches claim to be able to pick up downstream loop protection, so while it won't prevent the unmanaged switch from being hit it should prevent it from taking down any upstream switches.

[cpjitservices]

Spanning-Tree protocol.

[FN-GM]

We've recently had a student loopback a cable into an unmanaged switch ( SW1), unforautnely I flattened the managed switch (SW2) it was plugged into. Should / Would loop protection protect against this or does it only work on the switch itself?

 

What switch is the managed switch? Make sure portfast isn't enabled on the port the unmanaged switch is connected to.

 

Get rid of that unmanaged switch as well!

[win]

Spanning-Tree protocol.

 

This ^

 

Log into the managed switch and make sure this is enabled. Only computers connected to that unmanaged switch will be effected, best to get rid of it - even a cheapo second hand managed switch (with STP) would be better.

[cpjitservices]

@strawberry - how did you get on ?

[strawberry]

Waiting till half term to find out!.

 

I need to enable it on quite a few switches so will be doing it during half term.

[SteveM555]

We used to have this occasionally.. except with Staff doing it not students. Spanning-Tree solved all the problems, now when they do it they just look silly.

[Geoff]

Bin all non-managed switches. Spanning tree on all your switches. Loop Protect (or equivalent feature on nonProcurves) client ports. If you have 802.1X port auth too you also know what machine and who was last using the port and can exact vengeance.

[Dos_Box]

Just edited the title to make it more relevant.