in our network, when a user connects a third party mini-switch (that doesn't have STP) to an outlet and creates a loop (connecting 2 ports of the mini-switch with each other), this causes the cpu of our core switch to go to 99%.
I would like to know why.
And I also would like to know what we can do to protect us.
My guess is that the third party switch does not run STP and that it consumes the BPDUs. Normally the BPDUs would loop back and the Cisco switch could detect it but I think this device is consuming the BPDU without participating in STP.
A catastrophy by design!
So there is no way of stopping the loop at the Cisco device, you can only cut your losses so to speak. Some things that you can implement:
Port security - Limit the number of MAC addresses per port, shut down the port if there is a violation
Storm control - Limit how much multicast/broadcast can come through the port
Basically it's a policy violation as well. The users need to understand what happens when they do this. Only approved devices should be allowed to connect to the network.
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...