I've had a 2950 access layer meltdown in the same way with a broadcast loop caused by a blocking uplink port intermitantly (twice in 3 months second time for long enough to identify) not receiving any data (inc BPDUs) even though up and looking healthy so it needless to say thought there had been a change and the root was not on that port so started to forward with disasterous results i.e. broadcasts killed most of the servers! A reboot strangely fixed the problem untill we changed the box in a maint. window - on further problems 7mths later.
I will say in Ciscos defence that once we added Loopguard and UDLD detection to our configs, we failed to simulate the fault! Kevin >Message: 5 >Date: Sun, 7 Oct 2007 22:09:11 -0700 >From: Mark Messier <[EMAIL PROTECTED]> >Subject: Re: [c-nsp] protecting cisco switches >To: cisco-nsp@puck.nether.net >Message-ID: <[EMAIL PROTECTED]> >Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed >Revisiting this Aug 31 topic... my simple set-up just >blew up again. I've got this: ********************************************************************** This transmission is confidential and must not be used or disclosed by anyone other than the intended recipient. Neither Corus Group Limited nor any of its subsidiaries can accept any responsibility for any use or misuse of the transmission by anyone. For address and company registration details of certain entities within the Corus group of companies, please visit http://www.corusgroup.com/entities ********************************************************************** _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
