Web Management Guide-R05
Table Of Contents
- How to Use This Guide
- Contents
- Figures
- Tables
- Getting Started
- 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
- 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
- Index
Chapter 7
| Spanning Tree Algorithm
Configuring Interface Settings for STA
– 195 –
Administrative path cost cannot be used to directly determine the root port on
a switch. Connections to other devices use IEEE 802.1Q-2005 to determine the
root port as in the following example.
Figure 109: Determining the Root Port
For BPDU messages received by i1 on SW3, the path cost is 0.
For BPDU messages received by i2 on SW3, the path cost is that of i1 on SW2.
The root path cost for i1 on SW3 used to compete for the role of root port is
0 + path cost of i1 on SW3; 0 since i1 is directly connected to the root bridge.
If the path cost of i1 on SW2 is never configured/changed, it is 10000.
Then the root path cost for i2 on SW3 used to compete for the role of root port
is 10000 + path cost of i2 on SW3.
The path cost of i1 on SW3 is also 10000 if not configured/changed.
Then even if the path cost of i2 on SW3 is configured/changed to 0, these ports
will still have the same root path cost, and it will be impossible for i2 to become
the root port just by changing its path cost on SW3.
For RSTP mode, the root port can be determined simply by adjusting the path
cost of i1 on SW2. However, for MSTP mode, it is impossible to achieve this only
by changing the path cost because external path cost is not added in the same
region, and the regional root for i1 is SW1, but for i2 is SW2.
◆ Admin Link Type – The link type attached to this interface.
■
Point-to-Point – A connection to exactly one other bridge.
■
Shared – A connection to two or more bridges.
■
Auto – The switch automatically determines if the interface is attached to a
point-to-point link or to shared media. (This is the default setting.)
◆ Root Guard – STA allows a bridge with a lower bridge identifier (or same
identifier and lower MAC address) to take over as the root bridge at any time.
Root Guard can be used to ensure that the root bridge is not formed at a
suboptimal location. Root Guard should be enabled on any designated port
connected to low-speed bridges which could potentially overload a slower link
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)
Gigabit Ethernet 10,000 10,000
10G Ethernet 1,000 1,000
Table 12: Default STA Path Costs (Continued)
Port Type Short Path Cost
(IEEE 802.1D-1998)
Long Path Cost
(IEEE 802.1D-2004)