Table Of Contents
Configuring and Monitoring from the Switch Manager
Making Changes from the Switch Manager
Assigning or Changing Basic Switch Information
Assigning or Changing the Switch Host Name and Description
Switch and Command-Switch IP Addresses
Using the Switch Image to Monitor the Switch
System Status LED on the Switch Image
Redundant Power System LED on the Switch Image
Port LEDs and Modes on the Switch Image
Link to Telnet to the Management Console
Links to Cisco Systems Resources
Enabling or Disabling Flooding of Unknown MAC Addresses
Enabling or Disabling ECC on the 100-Mbps Ports
Assigning or Changing a Port Name or Description
Managing the Switch Address Tables
Changing the Address Aging Time
Permanent Unicast Address Table
Permanent Multicast Address Table
Changing the Port Security Table
Changing the Maximum Secure Address Count
Clearing Addresses on LinkDown
Assigning or Changing the SNMP Read Community Strings
Assigning or Changing the SNMP Write Community Strings
Assigning or Changing Trap Managers
Authentication Trap Generation
LinkUp/LinkDown Trap Generation
Broadcast Storm Trap Generation
Address Violation Trap Generation
Assigning or Changing Write Managers
Changing the Spanning-Tree Protocol Settings
Enabling or Disabling Spanning-Tree Protocol
Changing the Spanning-Tree Options for the Switch
Changing Spanning-Tree Settings for Bridge Group 1 and Its Ports
Port and Forwarding STP States
Enabling or Disabling CDP on a Port
Port Monitoring (Switched Port Analyzer)
Changing the Console Port Settings and Upgrading the Firmware
Configuring the Switch Console Port
Management Console Inactivity Timeout
Downloading Switch Firmware from a TFTP Server
Downloading Switch Firmware from a TFTP Client
Exception and Utilization Statistics
Resetting Port and Switch Statistics
Changing the System Management Settings
Assigning or Changing IP Information
Switch Performance and Flooding and Traffic Control
Store-and-Forward for Multicast Frames
Action Upon Address Violations
Half-Duplex Back Pressure on 10-Mbps Ports
Managing Multicast Packets with CGMP
Configuring and Monitoring from the Switch Manager
This chapter explains how to use the switch manager to change the configuration settings and to monitor the switch. This chapter assumes that you have already performed these preliminary tasks that are described in this guide or in the Quick Start Guide: Catalyst 1900 Series Ethernet Switches:
•
"Connecting to the Console Port" section
•
•
Note
Note
Navigating the Switch Manager
At the top of each switch manager page is a menu bar. Figure 3-1 describes the functions of the pages accessible from this bar.
Note
Figure 3-1 Switch Manager Menu Bar
Making Changes from the Switch Manager
You can change the switch settings by entering information into fields, adding and removing list items, or selecting and deselecting check boxes. Click Apply to save your changes. Click Cancel to discard all your unsaved changes and to return the previous settings to the page.
Note
Note
•
•
•
Assigning or Changing Basic Switch Information
You can assign or change basic descriptions about the switch. You can also assign an encrypted (secret) privileged-level password to the switch management interfaces and monitor network activity through the live switch image.
From the switch manager, you can open a Telnet session on the management console and contact Cisco Systems resources.
To display the (Figure 3-2), click HOME on the menu bar.
Figure 3-2 Home Page
Assigning or Changing the Switch Host Name and Description
You can assign or change the following information about the switch:
•
•
•
Switch Host Name
Caution
The name you assign to the switch is kept even when the switch joins or leaves a cluster. If the switch does not have a name before it joins a cluster, the command switch assigns it a name that consists of the command-switch name and a number that reflects when the switch was added to the cluster. For example, a command switch can name a Catalyst 1900 switch eng-cluster-5, where eng-cluster is the command-switch name and 5 means that it is the fifth switch to join the cluster. When the switch name is viewed from the Cluster Management applications, the name is truncated to 32 characters. If the switch leaves the cluster, the switch keeps the name given by the command switch.
When the switch is a cluster member, the Member Switch Host Name field also displays the switch name at the top of each switch manager page. Therefore, the names in the Host Name and Member Switch Host Name fields are identical.
Switch and Command-Switch IP Addresses
The Switch IP Address field displays the IP address of the switch itself, which is typically assigned after the switch is installed. (See the "Assigning IP Information and a Password to the Switch" section.) If the switch does not have an IP address, the Switch IP Address field displays 0.0.0.0. When the switch is a cluster member, the Command Switch IP field displays the command-switch IP address at the top of each switch manager page.
IP information identifies the switch on the network and is required to configure and monitor it as an individual switch. When you assign the switch its own IP address, you can manage it from its management interfaces (switch manager, management console, SNMP, or CLI). The switch retains its own IP address even when it joins or leaves a switch cluster.
If you do not assign an IP address to the switch, you must add the switch to a switch cluster and manage it through the command switch. Whether or not the switch has its own IP address, when the switch is a cluster member, it is managed and communicates with other member switches through the IP address of the command switch. If the switch leaves the cluster and it does not have its own IP address, you then must assign IP information to it to manage and monitor it as a nonmember switch.
Note
For additional information, see the "Assigning or Changing IP Information" section. For information about IP information in switch clusters, refer to the Cisco IOS Desktop Switch Software Configuration Guide, Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
Changing the Switch Password
A privileged-level password (encrypted or unencrypted) is required to access the switch management interfaces (switch manager, management console through a Telnet session, or CLI).
The password you assign from the Assign/Change Password field on the is an encrypted (secret) privileged-level password. This password provides higher security and supersedes any existing unencrypted privileged-level password, including the unencrypted privileged-level password that is assigned from the [P] Console Password option on the . (For information about where you can assign privileged-level passwords, see the "Privileged-Level Passwords" section.)
Follow these steps to assign an encrypted privileged-level password to the switch or to change the existing switch password to an encrypted privileged-level password:
Step 1
Step 2
Step 3
Step 4
Note
When your switch is a cluster member, the highest privileged-level password for the command switch is the privileged-level password to the switch. The command-switch password overwrites any switch-specific passwords. For more information about passwords in switch clusters, see the "Cluster Member Passwords" section.
Note
If you have lost or forgotten the password, see the "Recovering from a Lost or Forgotten Password" section.
Privileged-Level Passwords
If you plan to manage the switch outside of a switch cluster, you can assign an unencrypted or encrypted privileged-level password to the switch to restrict access to its management interfaces ().
Read and Write community strings operate as passwords to the switch when managing it from an SNMP management station. See the "Changing the SNMP Settings" section.
For information about the user-level passwords, refer to the online-only Catalyst 1900 Series and Catalyst 2820 Series Command Reference.
Cluster Member Passwords
When the switch joins a cluster, the highest privileged-level password (encrypted or unencrypted) of the command switch supersedes any existing password for the switch. Keep in mind the following considerations:
•
•
•
Note
For password information about switch clusters, refer to the Cisco IOS Desktop Switch Software Configuration Guide, Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
Using the Switch Image to Monitor the Switch
If you are using a remote station, you can use the LEDs and the Mode button on the switch image to monitor the switch. The switch image on the shows the front-panel LED colors at the last polling interval and refreshes every 30 seconds.
System Status LED on the Switch Image
The colors of the system status (SYSTEM) LED on the switch image show that the switch is receiving power and functioning properly ().
Table 3-2 SYSTEM LED Description
Solid green
Switch is operating normally.
Solid amber
Switch is receiving power but might not be functioning properly. One or more power-on self-test (POST) errors occurred. The message identifies which nonfatal test(s) failed.
Note
Redundant Power System LED on the Switch Image
The colors of the redundant power system (RPS) LED show the status () of a connected Cisco RPS (model PWR600-AC-RPS). For more information about the RPS, see the "Power Connectors" section.
Table 3-3 RPS LED Description
Black (off)
RPS is off or is not installed.
Solid green
RPS is operational.
Blinking green
RPS and the switch AC power supply are both powered up.
Note
Solid amber
RPS is connected but is not functioning properly. One of the power supplies in the RPS could be powered down, or a fan on the RPS could have failed.
Port LEDs and Modes on the Switch Image
Each port has an LED above it. These LEDs, as a group or individually, display information about the switch and about individual ports (Table 3-4).
Changing Between Modes
Click the Mode button on the switch image to change the mode of the port LEDs. The STAT (port status), UTL (switch utilization), and FDUP (port duplex mode) LEDs show which mode is active (Table 3-5). The selected mode remains on approximately for 30 seconds before returning to the default mode (port status). You can change the default mode from the on the management console.
Port Status Mode
The port status mode is the default mode. In this mode, the colors of the LEDs above the ports show the status of those ports (). You cannot change the default mode from the switch manager; instead, you must use the on the management console. (See the "Console Settings Menu" section.)
Note
Bandwidth Utilization Mode
In the UTL mode, the port LEDs as a group show the switch bandwidth being used at any one time. The more LEDs that are lit, the higher the bandwidth being used. The peak utilization is recorded in the bandwidth-capture interval, described in the "Bandwidth Usage Report" section.
Full-Duplex Operation Mode
The colors of the LEDs in FDUP mode show which 10BaseT and 100BaseT ports are operating in full-duplex mode ().
Table 3-8 FDUP LED Description
Blue
Half-duplex mode is operational.
Green
Full-duplex mode is operational.
Cluster Management Button
Click Cluster Management to display the Cluster Management applications on the command switch. This button is available only when the switch is a cluster member. For information about the Cluster Management applications, refer to the Cisco IOS Desktop Switch Software Configuration Guide, Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
Link to Telnet to the Management Console
Click Telnet to open a Telnet session on the management console. At the prompt, enter the switch password or, if applicable, the command-switch password.
Links to Cisco Systems Resources
The provides these links to connect to Cisco Systems resources:
•
•
•
Changing the Port Settings
You can change the settings of the 10- and 100-Mbps ports. To display the (Figure 3-3), click PORT on the menu bar, or click the port on the switch image.
Figure 3-3 Port Management Page
Note
Enabling or Disabling a Port
Note
By default, all ports are enabled to transmit and receive data. To disable a port:
Step 1
Step 2
A linkDown trap is sent to the management station if you configured an SNMP manager.
Step 3
To re-enable a port:
Step 1
Step 2
A linkUp trap is sent to the management station if you configured an SNMP manager.
Step 3
Port Status
The Status: Requested/Actual column also displays the port status in the gray area below the Enable check box. Security violations, management intervention, or actions of the Spanning-Tree Protocol (STP) can change the port status. No packets are forwarded to or from a disabled or suspended port. However, suspended ports do monitor incoming packets to look for an activating condition. For example, when a linkbeat returns, a port suspended for no linkbeat returns to the enabled state.
Each port is always in one of the states listed in .
Changing the Port Duplex Mode
The default duplex mode depends on the port type:
•
•
To change the port duplex mode:
Step 1
The default for the 10-Mbps ports and the 100-Mbps fiber-optic ports is half duplex. The default for the 100BaseTX ports is autonegotiate.
Note
Note
Step 2
Step 3
Step 4
Full-Duplex Operation
Full-duplex operation is the simultaneous transmission of data in both directions across a link. For example, a 100-Mbps port operating in full-duplex mode can provide up to 200 Mbps of bandwidth across the switched link.
Note
Flow Control
Flow control is a function whereby the transmitting station does not send data or control information faster than the receiving station can accept it. This prevents the loss of outgoing packets during transmission. If the switch is transmitting packets faster than the attached device can receive and process them, the attached device sends pause-control frames when its port buffer becomes full. When you use the full-duplex with flow control option on a 100-Mbps port, the switch port responds to the pause-control frames sent from the attached device. The switch holds subsequent transmissions in the port queue for the time specified in the pause-control frame. When no more pause-control frames are received, or when the default time specified has passed, the switch resumes transmitting frames through the port.
Note
Note
Autonegotiation
When you use the autonegotiate option on a 100BaseTX port, it automatically configures for full-duplex operation if the connected device also supports full duplex. If the attached device does not autonegotiate, the port automatically configures itself to half duplex.
Note
Enabling or Disabling Flooding of Unknown MAC Addresses
By default, all switch ports are enabled to forward unicast and multicast packets with unknown destination Media Access Control (MAC) addresses. You can enable or disable flooding on a per-port basis.
A unicast packet is information addressed to one recipient from one sender. This type of traffic typically comprises the bulk of traffic on an Ethernet LAN. A multicast packet is information sent to multiple recipients from one sender. This lightens the load on the sender and on the network because only one data stream is sent, rather than one per recipient. A broadcast packet is information sent to all nodes within a single network segment and can be a major source of congestion.
The switch forwards each unicast or multicast packet it receives according to the entries stored in the switch content-addressable memory (CAM) table. The table entries are mappings of the MAC addresses of destination end-stations and of the associated switch ports through which incoming packets are forwarded to those destination end-stations.
•
•
Flooding is the forwarding of unicast or multicast packets with unknown destination addresses to all the switch ports. (A broadcast packet is always forwarded [flooded] to all ports.) Flooding adds traffic on the switch ports. In some configurations, flooding could be unnecessary. For example, there are no unknown destinations on switch ports with only statically assigned addresses or single stations attached. In this case, you can disable flooding on these ports.
You can assign a network port to which all unknown unicast addresses are forwarded. For more information, see the "Network Port" section.
The switch can store up to 1024 address entries in memory.
For more information about address management, see the "Managing the Switch Address Tables" section. For information about multicast packet control, see the "Managing Multicast Packets with CGMP" section. For information about broadcast packet control, see the "Broadcast Storm Control" section.
To disable flooding on a port:
Step 1
Step 2
To enable flooding on a port:
Step 1
Step 2
Enabling or Disabling ECC on the 100-Mbps Ports
By default, enhanced congestion control (ECC) is disabled on all 100-Mbps ports. This option reduces congestion on the switch and keeps the switch from dropping frames because of full transmit queues. The ECC option can be enabled on half-duplex ports and can be configured on a per-port basis on the 100-Mbps ports.
For information about ECC on the 10-Mbps ports, see the "ECC on 10-Mbps Ports" section. ECC on the 10-Mbps ports is set on a global basis, not on a per-port basis.
To enable ECC on a 100-Mbps port:
Step 1
•
•
•
•
Step 2
Assigning or Changing a Port Name or Description
To assign a name or description to a port:
Step 1
(up to 60 characters).Step 2
Detailed Port Statistics
The (Figure 3-4) displays the receive and transmit statistics for the port you select. You can use this page to help identify performance or connectivity problems, which are listed under the Errors area of the page. For example, Frame Check Sequence (FCS) and alignment errors could be the result of cabling problems such as the following:
•
•
•
•
•
To display this page, click View... for a particular port on the . The errors are described in .
Figure 3-4 Detailed Port Statistics Page
Managing the Switch Address Tables
The switches use source address tables (filters) to efficiently forward packets between the switch ports. Address filtering applies only to incoming (received) traffic on the switch. The source address tables list the source addresses (sending end-stations) and the associated switch port(s) through which packets are forwarded to the destination end-stations.
Packets with static addresses are usually received on any source port. The switch also supports source-port filtering on unicast and multicast addresses. This enhanced filtering enables the switch to only forward packets from source addresses when they are received on specified switch ports. These source addresses are referred to as restricted static addresses.
The switch can store up to 1024 address entries in memory.
For additional traffic control options, see the following sections:
•
•
•
•
To display the (Figure 3-5), click Address on the menu bar.
Figure 3-5 Address Table Management Page
Dynamic Address Table
The switch provides dynamic addressing by learning the source MAC address of each packet received on each switch port and then adding the address and its associated forwarding switch port number to the Dynamic Address Table. As end-stations are added or removed from the network, the switch updates the table, adding new entries and removing unused ones.
To delete a specific entry from the Dynamic Address Table:
Step 1
Step 2
Changing the Address Aging Time
As the switch reaches the maximum address limit of 1024 address entries in memory, switch performance can degrade. Address aging helps prevent this by allowing the switch to keep only dynamic addresses that remain active over a specified period of time.
During a topology change, if the Port Fast mode option on the is disabled, addresses are aged more quickly by using the Forward delay option on the . When the topology stabilizes, the address-aging value again takes effect.
To assign the length of time the switch stores an inactive entry, after which it is removed from the table:
Step 1
This value applies to all dynamic addresses in the Dynamic Address Table.
Step 2
Permanent Unicast Address Table
The entries in the Permanent Unicast Address Table allow MAC addresses to be permanently associated with a switch port. Unlike the Dynamic Address Table, the entries in the Permanent Unicast Address Table are manually entered or sticky-learned. (See the "Securing a Port" section.)
If the address table is full, an error message is generated. You can change the size of the address table by using the . (See the "Changing the Maximum Secure Address Count" section.) For additional information about port security, see the "Changing the Port Security Table" section.
You can assign a network port to which all unknown unicast addresses are forwarded. For more information, see the "Network Port" section.
Note
To add a secure address to the Permanent Unicast Address Table:
Step 1
Step 2
Step 3
Static entries do not age out and must be manually removed from the table. To delete an entry from the table:
Step 1
Step 2
Permanent Multicast Address Table
The entries in the Permanent Multicast Address Table allow multicast addresses to be permanently associated with the switch port(s) that receive packets destined for those multicast addresses. Using the Permanent Multicast Address Table reduces the amount of multicast flooding on the switch. Unlike the Dynamic Address Table, the entries in the Permanent Multicast Address Table entries are manually entered.
If the address table is full, an error message is generated. You can change the size of the address table by using the . (See the "Changing the Maximum Secure Address Count" section.)
For additional information, see the
•
•
To add a secure address to the Permanent Multicast Address Table:
Step 1
Step 2
Step 3
Static entries do not age out and must be manually removed from the table. To delete an entry from the table:
Step 1
Step 2
Changing the Port Security Table
You can use the (Figure 3-6) to prevent the switch from forwarding packets from unauthorized users and to send SNMP traps if security violations occur. To display this page, click Port Security Table from the .
Figure 3-6 Port Security Table Page
Securing a Port
By default, port security is disabled (Security check box is not selected). Secure ports restrict the use of a switch port to a specific group of source addresses (sending end-stations). When you assign source addresses to a secure port, the switch does not forward any packets from addresses outside that group.
The source addresses on a secure port are manually assigned (static) or sticky-learned. Sticky-learning takes place when the address table for a secure port does not contain a full complement of static addresses. The port sticky-learns the source address of incoming packets and automatically assigns them as static addresses.
Note
To enable port security on a port:
Step 1
Step 2
To disable port security on a port:
Step 1
Step 2
Changing the Maximum Secure Address Count
If the port is not a secure port, the value in the Maximum Secure Addresses field is 0. A secure port can have from 1 to 132 secure addresses associated with it.
Limiting the number of devices that can connect to a secure port has the following advantages:
•
•
Note
To change the number of addresses to the secure port:
Step 1
Step 2
Security Reject Count
The Security Reject Count (SRC) column displays the number of unauthorized addresses seen on the secure port.
Secure ports generate address-security violations under the following conditions:
•
•
If a security violation occurs, the port can be suspended or disabled. When a port is disabled, you must manually re-enable the port. When a port is suspended, it is re-enabled when a packet containing a valid address is received. You can also choose to ignore the violation. You can define the action taken by the switch either by using the or by using the MIB objects.
On the following switch manager pages, you can specify the action the switch takes if packets with unauthorized addresses arrive on the port:
•
•
Clearing Addresses on LinkDown
By default, the secure port keeps its association with all static addresses even if it loses link (Clear Addresses on LinkDown check box is not selected). You can enable a secure port to clear its address associations on linkDown.
Note
To enable the secure port to clear its address table on linkDown:
Step 1
Step 2
To disable the secure port from clearing its address table on linkDown:
Step 1
Step 2
Changing the SNMP Settings
Simple Network Management Protocol (SNMP) provides the means to manage and monitor the switch through the Management Information Base (MIB) objects. Additional information about SNMP and MIB objects is in the "Simple Network Management Protocol" section and the "Accessing MIB Files" section.
For information about how the command switch uses SNMP to manage the switch in the cluster, refer to the Cisco IOS Desktop Switch Software Configuration Guide, Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
To display the (Figure 3-7), click SNMP on the menu bar.
Figure 3-7 SNMP Management Page
Assigning or Changing the SNMP Read Community Strings
The default for the first Read community string is public. You can assign up to four community strings to serve as passwords that enable the switch to validate SNMP read (Get) requests from a management station.
When the switch joins a cluster, the command switch propagates its first Read community string as the last Read community string for the member switch. If the joining Catalyst 1900 switch already has four Read community strings, the command switch overrides that fourth community string with its own first community string. When the switch leaves the cluster, the command-switch community string is deleted.
The command-switch string contains up to 27 characters and a suffix "@esNN" where NN is the member switch number.
Caution
To add or change a SNMP Read community string:
Step 1
Step 2
To remove a SNMP Read community string:
Step 1
Step 2
Assigning or Changing the SNMP Write Community Strings
The default for the first Write community string is private. You can assign up to four community strings to serve as passwords that enable the switch to validate SNMP read-write (Set) requests from a management station. The write managers you assign to the switch can use any of the switch Write community strings.
When the switch joins a cluster, the command switch assigns its first Write community string as the last Write community string for the member switch. If the joining Catalyst 1900 switch already has four Write community strings, the command switch overrides that fourth community string with its own first community string. When the switch leaves the cluster, the command-switch community string is deleted.
The command-switch string contains up to 27 characters and a suffix "@esNN" where NN is the member switch number.
Caution
To add or change a SNMP Write community string:
Step 1
Step 2
To remove a SNMP Write community string:
Step 1
Step 2
Assigning or Changing Trap Managers
A trap manager, or trap client, is an SNMP management station that receives traps, which are the system alerts generated by the switch. If no trap manager is defined, no traps are issued.
You can assign up to four trap managers and their accompanying community strings. A trap manager can use its accompanying community string only; it cannot use the community string of another trap manager.
Trap manager settings can be configured from the switch or, if the switch is a cluster member, from the command switch.
After you have assigned the trap manager(s), the switch generates, by default, the following traps:
•
•
•
•
•
•
•
•
•
•
•
•
•
For more information about traps, see the "Simple Network Management Protocol" section and the "Accessing MIB Files" section.
To assign a trap manager and its community string:
Step 1
If the switch is connected to a Domain Name System (DNS) server, you can enter the name of the trap manager instead.
Step 2
Step 3
To remove a trap manager:
Step 1
Step 2
Authentication Trap Generation
By default, authentication trap generation is enabled (Enable Authentication Trap Generation check box is selected). This option enables the switch to generate authentication traps, which alert a management station of SNMP requests not accompanied by a valid community string.
Note
To disable authentication trap generation:
Step 1
Step 2
LinkUp/LinkDown Trap Generation
By default, linkUp/linkDown trap generation is enabled (Enable LinkUp/LinkDown Trap Generation check box is selected). This option enables the switch to generate linkDown traps when a port is suspended or disabled for any of these reasons:
•
•
•
The switch generates linkUp traps when a port is enabled for any of these reasons:
•
•
•
Note
To disable linkUp/linkDown trap generation:
Step 1
Step 2
Broadcast Storm Trap Generation
By default, broadcast storm trap generation is disabled (Enable Broadcast Storm Trap Generation check box is not selected). When this option is enabled, the switch generates SNMP alerts when the broadcast threshold is exceeded. The alert generated is the trapbroadcastStorm. A trap is generated every 30 seconds.
For information about broadcast storm control, see the "Broadcast Storm Control" section.
To enable broadcast storm trap generation:
Step 1
Step 2
Address Violation Trap Generation
By default, address violation trap generation is enabled (Enable Address Violation Trap Generation check box is selected). This option enables the switch to generate SNMP alerts if an address violation occurs.
To disable address violation trap generation:
Step 1
Step 2
Assigning or Changing Write Managers
A write manager is an SNMP management station that can issue write requests to the switch. You can assign up to four write managers. The switch allows write requests from only the specified write managers or from the command switch. The write managers you assign can use any of the switch Write community strings.
Caution
Note
To assign a write manager:
Step 1
If the switch is connected to a DNS server, you can enter the name of the write manager instead.
Step 2
To remove a write manager:
Step 1
Step 2
Changing the Spanning-Tree Protocol Settings
The Spanning-Tree Protocol (STP) constructs network topologies that do not contain loops. When the network configuration changes, STP transparently reconfigures bridges and switches to avoid the creation of loops. STP avoids loops by placing ports in a forwarding or blocking state and establishes redundant paths (in the event of lost connections).
The following are two examples for using STP:
•
•
A separate spanning-tree instance runs on each bridge group, and each bridge group participates in a separate spanning tree. Each switch in a spanning tree adopts the Hello, Max age, and Delay parameters of the root bridge regardless of how it is configured. Overlapping ports (ports that belong to more than one bridge group) participate in all spanning trees to which they belong. All ports on the switch support STP, and STP is managed through the standard Bridge MIB.
Note
Overlapping ports should be connected to end nodes only, not to other bridges. To configure the STP settings for other bridge groups on the switch, use the on the management console.For more information about bridge groups and to configure bridge groups, see the and the "Spanning Tree Configuration Menu" on page 31. For information about VLANs, refer to the Catalyst 1900 Series and Catalyst 2820 Series Enterprise Edition Software Configuration Guide.
To display the (), click STP on the menu bar.
Figure 3-8 Spanning-Tree Management Page
Enabling or Disabling Spanning-Tree Protocol
<
