we had an a issue last night where a server started sending a broadcast storm and caused latency in the network. (this was an email migrantion and we expected that type of broadcast) but problem started when Cisco4507 (where server is connected) started sending broadcast to every host in the network and spiked the CPU, in my understanding switch is not supposed to forward this traffice and should have supressed it but I think it acted as a hub and not switch. My question is what can I do to stop/limit a host to send this type of broadcast or tell the switch not to process it to other hosts. I found an interface level command
storm-control broadcast level
storm-control action shutdown/trap
Has anyone tried this? Or if someone has other suggestions?
It's broadcast nature to "broadcast" traffic. When compared to a hub only unicast traffic will be isolated from other ports. Broadcast and multicast frames WILL enter ALL switchports except the origination port.
You can configure a threshold (with the storm-control command)on the troubled port. However use this with great caution. Apply it to one port at a time, because you can lock up your switch with this.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...