Chapter 7
| Spanning Tree Algorithm
Configuring Interface Settings for STA
–
194
–
◆
Admin Edge Port
–
Since end nodes
cannot
cause forwarding loops, they can
pass directly through to the spanning tree forwarding state. Specifying Edge
Ports provides quicker convergence for devices such as workstations or servers,
retains the current forwarding database to reduce the amount of frame
flooding required to rebuild address tables during reconfiguration events, does
not cause the spanning tree to initiate reconfiguration when the interface
changes state, and also overcomes other STA-related timeout problems.
However, remember that Edge Port should only be enabled for ports
connected to an end-node device. (Default: Auto)
■
Enabled
–
Manually configures a port as an Edge Port.
■
Disabled
–
Disables the Edge Port setting.
■
Auto
–
The port will be automatically configured as an edge port if the
edge delay time expires without receiving any RSTP or MSTP BPDUs. Note
that edge delay time (802.1D-2004 17.20.4) equals the protocol migration
time if a port's link type is point-to-point (which is 3 seconds as defined in
IEEE 802.3D-2004 17.20.4); otherwise it equals the spanning
tree’s
maximum age for configuration messages (see maximum age under
“Configuring Global Settings for STA”
An interface cannot function as an edge port under the following conditions:
■
If spanning tree mode is set to STP (
), edge-port mode cannot
automatically transition to operational edge-port state using the automatic
setting.
■
If loopback detection is enabled (
) and a loopback BPDU is
detected, the interface cannot function as an edge port until the loopback
state is released.
■
If an interface is in forwarding state and its role changes, the interface
cannot continue to function as an edge port even if the edge delay time
has expired.
■
If the port does not receive any BPDUs after the edge delay timer expires,
its role changes to designated port and it immediately enters forwarding
state (see
“Displaying Interface Settings for STA”
When edge port is set as auto, the operational state is determined
automatically by the Bridge Detection State Machine described in 802.1D-2004,
where the edge port state may change dynamically based on environment
changes (e.g., receiving a BPDU or not within the required interval).
◆
BPDU Guard
–
This feature protects edge ports from receiving BPDUs. It
prevents loops by shutting down an edge port when a BPDU is received instead
of putting it into the spanning tree discarding state. In a valid configuration,
configured edge ports should not receive BPDUs. If an edge port receives a
BPDU an invalid configuration exists, such as a connection to an unauthorized
device. The BPDU guard feature provides a secure response to invalid
Summary of Contents for GEL-5261
Page 14: ...14 Contents Glossary 551 Index 559...
Page 26: ...26 Figures...
Page 30: ...30 Section I Getting Started...
Page 42: ...42 Section II Web Configuration IP Services on page 527...
Page 45: ...Chapter 2 Using the Web Interface NavigatingtheWebBrowserInterface 45 Figure 1 Dashboard...
Page 62: ...62 Chapter 2 Using the Web Interface NavigatingtheWebBrowserInterface...
Page 180: ...Chapter 6 Address Table Settings Issuing MAC Address Traps 180...
Page 208: ...Chapter 8 Congestion Control Storm Control 208 Figure 121 Configuring Storm Control...
Page 228: ...228 Chapter 10 Quality of Service Attaching a Policy Map to a Port...
Page 332: ...Chapter 12 Security Measures ARP Inspection 332 Figure 207 Displaying the ARP Inspection Log...
Page 436: ...Chapter 13 Basic Administration Protocols LBD Configuration 436...
Page 488: ...488 Chapter 14 Multicast Filtering Filtering MLD Query Packets on an Interface...
Page 498: ...Chapter 15 IP Tools Address Resolution Protocol 498...
Page 517: ...517 Chapter 16 IP Configuration Setting the Switch s IP Address IP Version 6 interface...
Page 542: ...540 Section III Appendices...
Page 560: ...Glossary 558...
Page 570: ...568 Index E062017 ST R01...