Differences

This shows you the differences between two versions of the page.

--- spanning_tree_protocol [2024/01/18 11:57] – [Spanning Tree and Portfast] 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.
+\\
+\\
+<color #ed1c24>Spanning Tree</color> is a <color #ed1c24>Layer 2</color> Protocol.
 \\
 ----
@@ Line 272: / Line 275: @@
 \\
 Spanning Tree Portfast should be configured on edge ports where you can expect client PCs, Servers, Printers etc. Basically any port that is not part of a STP loop that expects STP messages or BPDUs.
+\\
+\\
+Having said that, <color #ed1c24>Portfast</color> will not stop STP operation, if that port receives any STP or BPDU messages, it will revert back to 'normal' mode and participate in <color #ed1c24>Listening</color> and <color #ed1c24>Learning</color> modes.
+\\
+----
+==== Two Switches with Single Link ====
+For what we do with our systems, there are generally two data switches between devices, with a link between them (per VLAN) which looks like this diagram below:
+\\
+\\
+{{ :stp_004.png?700 |}}
+\\
+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.
+**//
+\\
+\\
+Having STP running is not going to cause any issues, and in fact as a safety measure is still quite good (who knows who might bridge the switches with a second cable).
 \\
 \\