Rapid Spanning Tree
7278_en_04 PHOENIX CONTACT 4-9
4.2.1.4 Enabling via serial interface
Establish a connection to the switch as described in Section "Management via local V.24
(RS-232) communication interface" on page 3-48. Set "Rapid Spanning Tree, Enabled" on
the following page in the "Redundancy" field and select "Save".
Figure 4-7 Activating Rapid Spanning Tree
4.2.1.5 Connecting the switches to form a meshed topology
Having activated Rapid Spanning Tree for all switches, you can create a meshed topology
with redundant data paths. Any data connections can now be created without taking loops
into consideration. Loops can even be added on purpose in order to create redundant
connections.
A data path between Rapid Spanning Tree switches can be:
–A direct connection.
– A connection via one or more additional switches that do not support Spanning Tree.
– A connection via one or more additional hubs that do not support Spanning Tree.
Furthermore, a data path can also consist of a connection of a Spanning Tree switch to:
–A termination device.
– A network segment in which no loops may occur, which consists of several
infrastructure components (hubs or switches) without Spanning Tree support.
For the first three scenarios, the following rules must be observed:
– Rule 1: Spanning Tree transparency for all infrastructure components
All infrastructure components used in your network that do not actively support
Spanning Tree must be transparent for Spanning Tree messages (BPDUs) and must
forward all BPDUs to all ports without modifying them. When Spanning Tree is
disabled, the switch is transparent for BPDUs.
If Spanning Tree is not supported by all of the switches used, the reconfiguration time for
Spanning Tree is extended by the aging time of switches without Spanning Tree support.
To Next Page
Loading...
