And if you are not sure what is appropriate just make it less than 32K.Įxample: set protocols rstp bridge-priority 8k Point is keep your BP's appropriate for their role and Lower than the rogue switches. I am assuming you got a 3 tier architecture maybe you got a hybrid 2 tier or just a VC with rogue users plugging in switches. And the Aggregates are going to have lower BP's than the default of 32k.And the Distribution with lower BP's than the Aggregates.You are going to want to set the Core switches with lower BP's than the Distribution.First you are going to want to set your bridge-priority (BP) on all your Core, Distribution & Aggregate switches.How can I prevent this from happening again? I'm trying to say that a proper STP design is part of broadcast loop prevention. Maybe you are good but if you have left the defaults consider building a better STP design of some sort. Weeeeeeeeeeĭefault RSTP by itself is not enough. Part of the frames that would make up that broadcast storm would be STP TCN's. And If a user found one, dusted it off and made a loop: you got a broadcast storm. And Maybe you had proper bpdu's set to prevent that but you could get bitten this way.Īnother thing is there are still Hubs out there in the wild. Everyone on CoreA now get's to CoreB through the 100Mbps link on the voip phone. And the other port, on the rogue switch, is connected to CoreB access port. That voip phones switch port uplinks to the Rogue Switch. And it's been uplinked to both of your core ex4200's (lets call them CoreA and CoreB).ĬoreA is connected, to the new rogue root, by a 100Mbps connection through an access port that is connected to a voip phone. This rogue switch is now your root switch.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |