02-12-2012 11:59 PM - edited 03-07-2019 04:53 AM
Hi,
I just wanted some advice last week while our company was doing some refurbishment a hired contractor came in and plugged on ethernet cable from one wall port directly into another wall port. This caused the end of the world till I managed to trace the issue, I just wanted to ask if anyone knew good prevention methods for storm control incidents.
The current setup was
4x 3750E poe switch stack for users workstations
That runs 2x dot1q trunks to the
2x distribution 3750G switches
then that runs to the
2x 6500 cores
Once the port was plugged into it's self this created a storm that from the first 3750e poe switch started bleeding the storm up the uplinks to affect finally the 6500 cores causing a halt to the entire system.
Standard configuration of a workstation port
interface GigabitEthernet1/0/1
description *** WORKSTATION PORT ***
switchport access vlan 40
switchport mode access
no logging event link-status
mls qos cos override
no snmp trap link-status
no cdp enable
spanning-tree portfast
spanning-tree bpdufilter enable
spanning-tree bpduguard enable
spanning-tree guard root
end
and configuration on all switches
spanning-tree mode rapid-pvst
spanning-tree loopguard default
spanning-tree portfast bpduguard default
spanning-tree extend system-id
Ins't 802.1w spanning tree rapid met to to prevent this issue? or is portfast stuffing this up? My current solutuion would be to enable on all workstation interfaces storm-control
storm-control broadcast level 20
storm-control action shutdown
ANY OTHER IDEAS? how this can be prevented?
any help would be great cheers
Eddy
Solved! Go to Solution.