spanning_tree_protocol
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
spanning_tree_protocol [2024/01/18 13:15] – [Two Switches with Single Link] walkeradmin | spanning_tree_protocol [2024/01/18 13:26] (current) – [Introduction] walkeradmin | ||
---|---|---|---|
Line 9: | Line 9: | ||
\\ | \\ | ||
Spanning Tree Protocol essentially stops packet loops (where the same packet transports around your switches constantly) which causes broadcast storms and thus grinds the network to a complete halt. | Spanning Tree Protocol essentially stops packet loops (where the same packet transports around your switches constantly) which causes broadcast storms and thus grinds the network to a complete halt. | ||
+ | \\ | ||
+ | \\ | ||
+ | <color # | ||
\\ | \\ | ||
---- | ---- | ||
Line 284: | Line 287: | ||
\\ | \\ | ||
In this example, we can see just a single link from Switch A to Switch B. This means that there cannot be any Loops, so STP would not be required here (although it is worth remember that STP in some form runs on a Cisco be default). | In this example, we can see just a single link from Switch A to Switch B. This means that there cannot be any Loops, so STP would not be required here (although it is worth remember that STP in some form runs on a Cisco be default). | ||
+ | \\ | ||
+ | \\ | ||
+ | Remember this Statement regarding STP - //**When a switch receives a broadcast message, that switch will forward that message out of every interface on that switch, except the one it was received on. | ||
+ | **// | ||
\\ | \\ | ||
\\ | \\ |
spanning_tree_protocol.1705583729.txt.gz · Last modified: 2024/01/18 13:15 by walkeradmin