D-Link Unified Access System
Software User Manual
12/10/09
Page 246
Configuring Spanning Tree Protocol
Document
34CSFP6XXUWS-SWUM100-D7
C
ONFIGURING
S
PANNING
T
REE
P
ROTOCOL
The Spanning Tree Protocol (STP) provides a tree topology for any arrangement of bridges. STP also provides one path
between end stations on a network, eliminating loops. Spanning tree versions supported include Common STP, Multiple
STP, and Rapid STP.
Classic STP provides a single path between end stations, avoiding and eliminating loops. For information on configuring
Common STP, see
“CST Port Configuration/Status” on page 252
Multiple Spanning Tree Protocol (MSTP) supports multiple instances of Spanning Tree to efficiently channel VLAN traffic
over different interfaces. Each instance of the Spanning Tree behaves in the manner specified in IEEE 802.1w, Rapid
Spanning Tree (RSTP), with slight modifications in the working but not the end effect (chief among the effects, is the rapid
transitioning of the port to ‘Forwarding’). The difference between the RSTP and the traditional STP (IEEE 802.1D) is the
ability to configure and recognize full duplex connectivity and ports which are connected to end stations, resulting in rapid
transitioning of the port to ‘Forwarding’ state and the suppression of Topology Change Notification. These features are
represented by the parameters ‘pointtopoint’ and ‘edgeport’. MSTP is compatible to both RSTP and STP. It behaves
appropriately to STP and RSTP bridges. A MSTP bridge can be configured to behave entirely as a RSTP bridge or a STP
bridge.
The Spanning Tree
folder contains links to the following STP pages:
•
•
•
•
“CST Port Configuration/Status”
•
“MST Port Configuration/Status”
•
For two bridges to be in the same region, the force version should be 802.1S and their configuration
name, digest key, and revision level should match. For more information about regions and their effect
on network topology, refer to the IEEE 802.1Q standard.