tag:blogger.com,1999:blog-8221207.post109453613817757099..comments2023-03-18T06:07:56.466-05:00Comments on Bitspitter: Cheap Switches and Broadcast Stormsbitspitterhttp://www.blogger.com/profile/14808524441658851666noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-8221207.post-17975336246290041422012-06-10T09:32:16.231-05:002012-06-10T09:32:16.231-05:00You can trace broadcast storms through your manage...You can trace broadcast storms through your managed switches.<br />commands<br />switch>enable<br />switch# debug arp (logs and displays arp requests)<br />switch# term mon (allows the display to show from your telnet or ssh session)<br />watch the display for the same ip address over and aver once you see that enter:<br />switch# term no mon (turns off term mon)<br />switch# un all (turns off all debugging)<br />switch# sh arp<br />find the IP address that you discovered earlier and write down the MAC that is associated with it.<br />switch# sh mac address-table<br />find the MAC you just wrote down and see what port it is associated with. If it is associated with a trunk port do the last step again until you find a single port connection.<br /><br />That's how you trace a broadcast storm through your network without having to purchase 3rd party tools.The Tru-Geekhttps://www.blogger.com/profile/06095464337474121645noreply@blogger.comtag:blogger.com,1999:blog-8221207.post-38791683851886568752009-03-25T09:18:00.000-05:002009-03-25T09:18:00.000-05:00Thank you posting this! I am not a network specia...Thank you posting this! I am not a network specialist. I am learning and several times I have had network storms. I even replaced some switches only to have to problem resurface. This was a very enlightening read. Now I know why all my lights are flashing together like that, lol. I only wish I has a way to locate the source of the problem.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8221207.post-75870062384994116952008-03-09T13:56:00.000-05:002008-03-09T13:56:00.000-05:00I realize this is an older posting, but thank you ...I realize this is an older posting, but thank you for illuminating this - something only experience can testify to!<BR/><BR/>I have been confronted with a broadcast storm on a small network only once, but after this event, discovered a wealth of inefficient processes that we were able to address afterward, even though they were 'red herrings' during the original incident. Thank you for sharing the experience and the metaphors, this is very helpful to those of us just learning the subtleties of the network world. (Best advice I was ever given: "Define what the problem ISN'T!")<BR/>Thanks!L. Easterlyhttps://www.blogger.com/profile/17616549397957073780noreply@blogger.com