Managing Spanning Tree Protocol; Rstp Operation - Siemens RUGGEDCOM ROS User Manual

RUGGEDCOM ROS
User Guide
Section 5.3

Managing Spanning Tree Protocol

The following sections describe how to configure and manage STP:
• Section 5.3.1, "RSTP Operation"
• Section 5.3.2, "RSTP Applications"
• Section 5.3.3, "MSTP Operation"
• Section 5.3.4, "Configuring STP Globally"
• Section 5.3.5, "Configuring STP for Specific Ethernet Ports"
• Section 5.3.6, "Configuring eRSTP"
• Section 5.3.7, "Viewing Global Statistics for STP"
• Section 5.3.8, "Viewing STP Statistics for Ethernet Ports"
• Section 5.3.9, "Managing Multiple Spanning Tree Instances"
• Section 5.3.10, "Clearing Spanning Tree Protocol Statistics"
Section 5.3.1

RSTP Operation

The 802.1D Spanning Tree Protocol (STP) was developed to enable the construction of robust networks that
incorporate redundancy while pruning the active topology of the network to prevent loops. While STP is effective,
it requires that frame transfer halt after a link outage until all bridges in the network are guaranteed to be aware of
the new topology. Using the values recommended by 802.1D, this period lasts 30 seconds.
The Rapid Spanning Tree Protocol (RSTP, IEEE 802.1w) was a further evolution of the 802.1D Spanning Tree
Protocol. It replaced the settling period with an active handshake between bridges that guarantees the rapid
propagation of topology information throughout the network. RSTP also offers a number of other significant
innovations, including:
• Topology changes in RSTP can originate from and be acted upon by any designated bridges, leading to more
rapid propagation of address information, unlike topology changes in STP, which must be passed to the root
bridge before they can be propagated to the network.
• RSTP explicitly recognizes two blocking roles - Alternate and Backup Port - which are included in computations
of when to learn and forward. STP, however, recognizes only one state - Blocking - for ports that should not
forward.
• RSTP bridges generate their own configuration messages, even if they fail to receive any from the root bridge.
This leads to quicker failure detection. STP, by contrast, must relay configuration messages received on the
root port out its designated ports. If an STP bridge fails to receive a message from its neighbor, it cannot be
sure where along the path to the root a failure occurred.
• RSTP offers edge port recognition, allowing ports at the edge of the network to forward frames immediately
after activation, while at the same time protecting them against loops.
While providing much better performance than STP, IEEE 802.1w RSTP still required up to several seconds to
restore network connectivity when a topology change occurred.
A revised and highly optimized RSTP version was defined in the IEEE standard 802.1D-2004 edition. IEEE
802.1D-2004 RSTP reduces network recovery times to just milliseconds and optimizes RSTP operation for
various scenarios.
Managing Spanning Tree Protocol
Chapter 5
Setup and Configuration
137