Web Management Guide-R07
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- Introduction
- Key Features
- Description of Software Features
- Configuration Backup and Restore
- Authentication
- Access Control Lists
- Port Configuration
- Rate Limiting
- Port Mirroring
- Port Trunking
- Storm Control
- Static MAC Addresses
- IP Address Filtering
- IEEE 802.1D Bridge
- Store-and-Forward Switching
- Spanning Tree Algorithm
- Virtual LANs
- IEEE 802.1Q Tunneling (QinQ)
- Traffic Prioritization
- Quality of Service
- IP Routing
- Address Resolution Protocol
- Multicast Filtering
- Link Layer Discovery Protocol
- System Defaults
- Introduction
- Web Configuration
- Using the Web Interface
- Basic Management Tasks
- Displaying System Information
- Displaying Hardware/Software Versions
- Configuring Support for Jumbo Frames
- Displaying Bridge Extension Capabilities
- Managing System Files
- Setting the System Clock
- Configuring the Console Port
- Configuring Telnet Settings
- Displaying CPU Utilization
- Configuring CPU Guard
- Displaying Memory Utilization
- Resetting the System
- Using Cloud Management
- Interface Configuration
- VLAN Configuration
- Address Table Settings
- Spanning Tree Algorithm
- Congestion Control
- Class of Service
- Quality of Service
- VoIP Traffic Configuration
- Security Measures
- AAA (Authentication, Authorization and Accounting)
- Configuring User Accounts
- Web Authentication
- Network Access (MAC Address Authentication)
- Configuring HTTPS
- Configuring the Secure Shell
- Access Control Lists
- Filtering IP Addresses for Management Access
- Configuring Port Security
- Configuring 802.1X Port Authentication
- DoS Protection
- DHCP Snooping
- IPv4 Source Guard
- ARP Inspection
- Basic Administration Protocols
- Configuring Event Logging
- Link Layer Discovery Protocol
- Power over Ethernet
- Simple Network Management Protocol
- Configuring Global Settings for SNMP
- Setting the Local Engine ID
- Specifying a Remote Engine ID
- Setting SNMPv3 Views
- Configuring SNMPv3 Groups
- Setting Community Access Strings
- Configuring Local SNMPv3 Users
- Configuring Remote SNMPv3 Users
- Specifying Trap Managers
- Creating SNMP Notification Logs
- Showing SNMP Statistics
- Remote Monitoring
- Switch Clustering
- Setting a Time Range
- LBD Configuration
- Smart Pair Configuration
- Multicast Filtering
- Overview
- Layer 2 IGMP (Snooping and Query for IPv4)
- Configuring IGMP Snooping and Query Parameters
- Specifying Static Interfaces for a Multicast Router
- Assigning Interfaces to Multicast Services
- Setting IGMP Snooping Status per Interface
- Filtering IGMP Query Packets and Multicast Data
- Displaying Multicast Groups Discovered by IGMP Snooping
- Displaying IGMP Snooping Statistics
- Filtering and Throttling IGMP Groups
- MLD Snooping (Snooping and Query for IPv6)
- Filtering and Throttling MLD Groups
- Filtering MLD Query Packets on an Interface
- IP Tools
- IP Configuration
- General IP Routing
- Unicast Routing
- Overview
- Configuring the Routing Information Protocol
- Configuring General Protocol Settings
- Clearing Entries from the Routing Table
- Specifying Network Interfaces
- Specifying Passive Interfaces
- Specifying Static Neighbors
- Configuring Route Redistribution
- Specifying an Administrative Distance
- Configuring Network Interfaces for RIP
- Displaying RIP Interface Settings
- Displaying Peer Router Information
- Resetting RIP Statistics
- IP Services
- Appendices
- Glossary
Chapter 7
| Spanning Tree Algorithm
Configuring Interface Settings for STA
– 194 –
by taking over as the root port and forming a new spanning tree topology. It
could also
be used to form a border around part of the network where the root
bridge is allowed. (Default: Disabled)
◆ 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” on page 185).
An interface cannot function as an edge port under the following conditions:
■
If spanning tree mode is set to STP (page 185), edge-port mode cannot
automatically transition to operational edge-port state using the automatic
setting.
■
If loopback detection is enabled (page 183) 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” on page 196).
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,