Table Of Contents
Creating and Managing Clusters
Creating Clusters with Different Releases of IOS Software
Understanding Management VLAN Changes
Automatically Discovering Cluster Candidates
Changes to the SNMP Community Strings
Adding and Removing Member Switches
Determining Why a Switch Is Not Added to a Cluster
CLI: Adding a Member to a Cluster
CLI: Removing a Member from a Cluster
Recovering from a Failed Command Switch without HSRP
Configuring a Cluster Standby Group
Standby Command Switch Requirements
Using the Standby Configuration Window
CLI: Adding Member Switches to a Standby Group
CLI: Removing a Switch from a Standby Group
CLI: Removing a Standby Group from the Network
Accessing the Cluster Management Suite
Configuring Initial Cluster Settings
Arranging and Saving the Network Map
Rearranging the Order of the Displayed Switches
Displaying an Inventory of Cluster Switches
Guidelines for Changing the Management VLAN
Changing the Management VLAN for a Cluster
Changing the Management VLAN for a New Switch
CLI: Changing the Management VLAN Through a Telnet Connection
Monitoring and Configuring Ports
Guidelines for Configuring Ports
Connecting to Devices That Do Not Autonegotiate
CLI: Setting Speed and Duplex Parameters
CLI: Configuring Flow Control on Gigabit Ethernet Ports
Upgrading or Reloading the Switch Software
Guidelines for Upgrading or Reloading Switch Software
Configuring the Cisco TFTP Server to Upgrade Multiple Switches
CLI: Copying the Startup Configuration from the Switch to a PC or Server
Using the Software Upgrade Page to Upgrade Switch Software
CLI: Upgrading a Standalone Switch
CLI: Reloading or Upgrading Catalyst 2950, 2900 XL, or 3500 XL Member Switches
CLI: Upgrading Catalyst 1900 or 2820 Member Switches
Configuring SNMP for a Cluster
Enabling or Disabling the SNMP Agent
Configuring Community Strings for Cluster Switches
Configuring Trap Managers and Enabling Traps
Creating and Managing Clusters
A cluster is a group of connected switches that are managed as a single entity.
The switches can be in the same location, or they can be distributed across a contiguous Layer 2 network. All communication with cluster switches is through one IP address.
Tips
You can have up to 16 switches in a cluster: 1 command switch and up to 15 member switches. The command switch is the single point of access used to manage, configure, and monitor the member switches.
Clusters can be configured for management redundancy by using the Hot Standby Router Protocol (HSRP). Figure 3-1 shows a cluster of switches with a standby command switch.
This chapter describes how to create and manage clusters of switches by using the Cluster Management Suite (CMS) applications: Cluster Builder, Cluster View, and Cluster Manager. You use Cluster Builder to create the cluster, you use Cluster View to display the devices connected to the cluster, and you use Cluster Manager to configure and monitor your cluster after it has been created.
This chapter describes how to perform the following tasks:
•
•
•
•
Figure 3-1 A Cluster with a Standby Command Switch
Planning Your Cluster
Anticipating conflicts and compatibility issues is a high priority when you manage several switches through a cluster. This section describes the requirements and caveats that you should understand before you create the cluster.
Before you create a cluster, you might want to consider creating a cluster with a redundant command switch. Cluster redundancy is described in the "Building a Redundant Cluster" section.
Creating Clusters with Different Releases of IOS Software
Some versions of the Catalyst 2900 and 3500 XL software do not support clustering, and other versions do not support the features in this release. To ensure that all cluster switches are operating with the same level of software, we recommend that you upgrade all cluster switches to IOS Release 12.0(5)WC(1).
Note
Command Switch Requirements
You must select a switch to be the command switch of your cluster. The command switch must satisfy the following requirements:
•
Note
•
•
•
•
•
Note
Candidate Switch Requirements
Before adding a candidate switch to the cluster, you must know any assigned enable or enable secret password.
A candidate switch must satisfy the following requirements to join a cluster.
•
•
•
•
A candidate switch can have an IP address, but it is not required.
Note
Understanding Management VLAN Changes
Communication with the switch management interfaces is through the switch IP address. The IP address is associated with the management VLAN, which by default is VLAN 1. To manage switches in a cluster, the port connections among the command, member, and candidate switches must be connected through ports that belong to the management VLAN.
You can change the management VLAN on an existing cluster, and the command switch synchronizes activities with member switches to ensure that no loss of management connectivity occurs.
Note
To change the management VLAN on an existing cluster, see the "Changing the Management VLAN" section.
If you add a new switch to an existing cluster and the cluster is using a management VLAN other than the default VLAN 1, the command switch automatically senses that the new switch has a different management VLAN and has not been configured. The command switch issues commands to change the management VLAN and change the port on the new switch, which is connected to the cluster, to match the one in use by the cluster. This automatic change of the VLAN only occurs for new, out-of-box switches that do not have a config.text file and for which there have been no changes to the running configuration.
Creating Clusters
You create a cluster by performing these tasks:
1.
2.
3.
After the cluster is formed, you can access all switches in the cluster by entering the IP address of the command switch into the browser Location field (Netscape Communicator) or Address field (Internet Explorer).
Enabling the Command Switch
You enable the command-switch functionality through the Switch Manager or through the CLI. Before you enable a switch as a command switch, see the "Command Switch Requirements" section to ensure that the switch meets all the requirements.
Follow these steps to enable the switch as a command switch by using Visual Switch Manager (VSM):
Step 1
Step 2
Step 3
Step 4
After you have enabled the command switch, select Cluster > Cluster Builder to begin building your cluster. To enable a switch as the command switch by using the command-line interface (CLI), see the "CLI: Creating a Cluster" section.
Automatically Discovering Cluster Candidates
Cluster Builder uses the CDP to discover candidate switches that can be added to a cluster. By using CDP, a switch can automatically discover switches in star or cascaded topologies that are up to three CDP-hops away from the edge of the cluster. You can configure the command switch to discover switches up to seven CDP-hops away.
When an edge device that does not support CDP is connected to the command switch, CDP can still discover the candidate switches that are attached to it. When a switch that does support CDP but does not support clustering is connected to the command switch, the cluster is unable to discover candidates that are attached to it. For example, Cluster Builder cannot create a cluster that includes candidates that are connected to a Catalyst 5000 series or 6000 switch connected to the command switch.
When Cluster Builder starts, it automatically prompts you to create a cluster by adding qualified candidates, as shown in Figure 3-2. The Suggested Candidate window lists each candidate switch with its device type, MAC address, and the switch through which it is connected to the cluster. When new switches are added to the topology, Cluster Builder prompts you the next time it starts to add the latest candidate to the cluster. The Suggested Candidate window does not display after the number of switches in the cluster has reached the maximum of 16.
By default, the suggested candidates are highlighted in the Suggested Candidates window, but you can select one or more switches as long as the number of switches selected does not exceed 16. You can accept the suggested candidates or not. If you do not accept the suggested candidates, none of the switches are added.
Note
When you accept the suggested candidates, enter the password of the candidate switch if one has been defined. If no password has been defined, click OK to add the switch to the cluster with no password. If you enter a password that does not match the password defined for the candidate, or if the switch does not have a password, it does not look at the password field, and the candidate is not added to the cluster. In all cases, once a candidate switch joins a cluster, it inherits the command-switch password. For more information on setting passwords, see the "Changes to Passwords" section.
Note
You can set Cluster Builder to not automatically display suggested candidates. For more information, see the "Changing User Settings" section.
Figure 3-2 Suggested Candidate Window
CLI: Creating a Cluster
This procedure assumes that the candidate switches and the command switch are connected through ports that belong to the same management VLAN. The "Changing the Management VLAN" section describes the characteristics of the management VLAN.
Beginning in privileged EXEC mode on the command switch, follow these steps to enable the command switch and add candidate switches to the cluster:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
When a Cluster is Created
When a cluster is created, Network Address Translation (NAT) commands are added to the configuration file of the command switch. Do not remove these commands. The command switch also automatically makes configuration changes to the member switch host name, password, and SNMP community string.
Changes to the Host Name
If you did not assign a host name to a member switch, the command switch appends a unique member number to its own host name and assigns it sequentially to the switch when it joins the cluster. The number indicates the order in which the switch was added to the cluster. For example, a command switch named eng-cluster could name cluster member 5 eng-cluster-5.
If you did not assign a host name to the command switch, it keeps the default host name of Switch.
If you assigned a host name to a member switch, it retains that name when it joins the cluster. A host name is also retained even after removing the switch from the cluster.
However, if your switch was part of a cluster, received its host name from the command switch, was removed and then added back to a new cluster, its host name (such as eng-cluster-5) is not overwritten with the new version of the command switch host name.
Changes to the SNMP Community Strings
The following SNMP community strings are added to a member switch when it joins a cluster:
•
•
If the command switch has multiple read-only or read-write community strings, only the first read-only and read-write strings are propagated to the member switch.
Catalyst 2950, 2900 XL, and 3500 XL switches support an unlimited number of community strings and string lengths.
The Catalyst 1900 and 2820 switches support up to four read-only and four read-write community strings; each string contains up to 32 characters. When these switches join the cluster, the first read-only and read-write community string on the command switch is propagated and overwrites the fourth read-only and read-write community string on the member switches. To support the 32-character string-length limitation on the Catalyst 1900 and 2820 switches, the command-switch community strings are truncated to 27 characters when propagating them to these switches, and the @esN (where N refers to the member switch number and can be up to two digits) is appended to them.
For more information about configuring community strings through Cluster Manager, see the "Configuring SNMP" section.
Changes to Passwords
The member switch inherits the command-switch enable-secret or enable password when it joins the cluster and retains it when it leaves the cluster. If no command-switch password is configured, the member switch inherits a null password. Member switches only inherit the command-switch password privilege level 15.
However, certain caveats apply to Catalyst 1900 and 2820 switches as cluster members. Their passwords and privilege levels are altered in the following ways:
•
–
–
–
•
The command switch supports up to 15 privilege levels. Catalyst 1900 and 2820 member switches support only levels 1 and 15.
–
–
Adding and Removing Member Switches
You can use the network map in Cluster Builder (Figure 3-3) to add a switch or switches to a cluster. Clustered switches have green labels, and candidates have blue labels. To add a single switch to a cluster, right-click the candidate, and click Add to Cluster from the pop-up menu. If the candidate is in a different management VLAN than the command switch, a message is displayed indicating that this candidate is unreachable, and you will not be able to add it to the cluster.
To add several switches to a cluster, press Ctrl, and left-click the candidates you want to add. The candidates are added if they all have the same password. If any of the candidates cannot be added, Cluster Builder displays a message explaining which candidates were not added and why.
You can add a candidate to a cluster if no more than 16 switches are in the cluster; otherwise, you must remove a member before adding a new one. If a password has been configured on the switch, you are prompted to enter.
Note
To remove a member switch, right-click it, and select Remove from Cluster from the pop-up menu. The switch retains the password configured for it when it leaves the cluster. You can also use the CLI to remove a member switch, as described in the "CLI: Removing a Member from a Cluster" section.
Figure 3-3 Cluster Builder
Determining Why a Switch Is Not Added to a Cluster
If a switch does not become part of the cluster, you can learn why by selecting Views > Toggle View from the menu bar in Cluster Builder. Cluster View displays the cluster as a double-switch icon and shows connections to devices outside of the cluster (Figure 3-4). Right-click the device (yellow label), and select Disqualification Code to display the reason it did not join the cluster.
Figure 3-4 Cluster View
CLI: Adding a Member to a Cluster
You can use the cluster setup command to add members to an existing cluster or to create a cluster. This command generates a script that proposes configuration changes and prompts you to approve or disapprove them. Enter this command from a switch that is enabled as a command switch.
Note
Beginning in privileged EXEC mode on a command switch, follow these steps to add a member switch to a cluster:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
CLI: Removing a Member from a Cluster
You remove a cluster member by entering commands on the command switch.
Beginning in privileged EXEC mode on the command switch, follow these steps to remove a member switch from the cluster:
You can remove a member by entering commands on the member itself, but the member is not entirely removed from the cluster until you also enter commands on the cluster command switch. A member switch that is removed by entering commands only on the member switch is considered by the command switch to be down until it is explicitly removed on the command switch.
Beginning in privileged EXEC mode on a Catalyst 2950, 2900 XL, or 3500 XL member switch, follow these steps to remove it from a cluster:
For information on how to remove Catalyst 1900 or 2820 member switches, refer to the Catalyst 1900 Series Installation and Configuration Guide or the Catalyst 2820 Series Installation and Configuration Guide.
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
Building a Redundant Cluster
Because a cluster command switch manages the forwarding of all configuration information to cluster members, a redundant command switch is necessary to take over if the command switch fails. Cisco IOS Release 12.0(5)WC(1) supports a version of the HSRP so that you can configure a standby group of Catalyst 2950, 2900 XL, or 3500 XL switches. When this standby group is bound to the cluster, one of the switches acts as a standby command switch that becomes active when the command switch fails. The "Understanding HSRP" section describes how the protocol works.
Redundant cabling is also required for a standby switch to automatically take over when a command switch fails. Figure 3-5 shows a network cabled to allow the standby switch to maintain management contact with the member switches if the cluster command switch fails. Spanning Tree Protocol prevents the loops in such a configuration from reducing performance.
Figure 3-5 Redundant Cabling to Support HSRP
Understanding HSRP
To build a redundant cluster, you use HSRP to configure a stand-by group that contains a cluster command switch and one or more eligible member switches. The standby group is configured with a unique virtual IP address. When the standby group is bound on the command switch, the command switch receives member traffic destined for the virtual IP address.
To manage the redundant cluster, access the command switch through the virtual IP address and not the command-switch IP address. If HSRP is enabled and you use the command-switch IP address, you can be prompted a second time for a password when you move between Cluster Builder and VSM.
Other switches in the standby group are candidates to become the standby command switch and are ranked according to a set of user-defined priorities. The member switch with the highest priority in the group is the standby command switch. To ensure that the standby command switch can take over the cluster if the command switch fails, the command switch continually forwards cluster configuration information to the standby command switch.
Note
If the command switch fails, the standby command switch assumes ownership of the virtual IP address and MAC address and begins acting as the command switch. The remaining switches in the group compare their assigned priorities to determine the new standby command switch. To configure an HSRP standby group, see the "Configuring a Cluster Standby Group" section.
If a standby switch replaces a command switch and the command switch becomes active again, the command switch resumes its role as the active command switch. An automatic recovery procedure can add cluster members that were added to the cluster while the command switch was down.
Recovering from a Failed Command Switch without HSRP
If a command switch fails and no standby command switch is configured, member switches continue forwarding among themselves, and they retain the ability to be managed through normal standalone means. You can configure member switches through the console-port CLI, and they can be managed through SNMP, HTML, and Telnet after you assign an IP address to them.
The password you enter when you log into the command switch gives you access to member switches. If the command switch fails and there is no standby command switch, you can use the command-switch password to recover. For more information, see "Recovering from a Command Switch Failure" section.
Configuring a Cluster Standby Group
This section describes how to create a standby group and bind it to a cluster, how to add and remove members from a standby group, and how to remove a standby group from the network.
Use the Standby Command Configuration window (Figure 3-6) to create a standby group. When an active command switch fails, a new command switch is chosen from this group according to their order in their Selected list in the window.
Standby Command Switch Requirements
To be eligible to join a standby group, a switch must meet the following requirements:
•
•
Any number of eligible switches can belong to a standby group.
Note
For redundancy, we also recommend that a switch belonging to a standby group have the following characteristics:
•
•
Using the Standby Configuration Window
You create a standby group by moving candidates from the Candidates list to the Selected list in the Standby Command Configuration window (Figure 3-6). Eligible switches are listed in the Candidates list according to an eligibility ranking. Switches are ranked first by the number of links they have and second by the speed of the switch. If switches have the same number of links and speed, they are listed alphabetically.
When you add a switch to the standby group, you can configure the priority of group members by using the Add and Remove buttons. The command switch has the highest priority and is always at the top of the list. The standby switch is below the command switch, and the priority of the other switches is represented by their place in the list. The last switch in the list has the lowest priority.
Figure 3-6 Standby Command Configuration
The following abbreviations are appended to the switch host names in the Selected list to indicate their status in the standby group:
AC
Active command switch
SC
Standby command switch
PC
Passive command switch (member of the standby group but is not the standby command switch)
CC
Command switch when HSRP is disabled
The virtual IP address (VIP) must be in the same subnet as the IP addresses of the switches, and the group number must be unique within the IP subnet. It can be from 0 to 255, and the default is 0. The VIP should be different from the commander IP address to avoid duplicate IP addresses.
The Standby Command Configuration window uses default values for the preempt and name commands that you can explicitly set by using the CLI. If you use this window to create the HSRP group, all switches in the group have the preempt command enabled, and the name for the group is clustername_standby.
CLI: Creating a Standby Group
There are two steps to configuring a standby group through the CLI:
1.
2.
Follow these guidelines when you configure a standby group by using the CLI:
•
•
•
•
•
Beginning in privileged EXEC mode on the command switch, follow these steps to create the HSRP group and bind it to the command switch:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
CLI: Adding Member Switches to a Standby Group
Member switches must have an IP address and be running Cisco IOS
Release 12.0(5)XU or later before they can be added to an existing HSRP group. Beginning in privileged EXEC mode on the command switch, follow these steps to add the switch to the HSRP group:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
CLI: Removing a Switch from a Standby Group
You can remove standby switches from a standby group, but you cannot remove an active command switch from a standby group. Beginning in privileged EXEC mode on the command switch, follow these steps to remove a switch from the HSRP group:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
CLI: Removing a Standby Group from the Network
You remove a standby group from your network by disabling the standby group on the command switch and entering the no version of the HSRP CLI commands on all switches in the HSRP group. When all HSRP parameters have been removed from all the members of the group, including the command switch, the group has been removed from the network.
Beginning in privileged EXEC mode on the command switch, follow these steps to remove a standby group:
Note
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
Managing Switch Clusters
This section describes how to perform tasks on switch clusters. Cluster members could be Catalyst 1900, 2820, 2950, 2900 XL, or 3500 XL switches. These management tasks operate on all switches in the cluster and are distinct from configuring individual switches. For information on managing individual devices, see "Managing Switches."
This section describes how to perform the following tasks:
•
•
•
•
•
•
•
•
•
•
Accessing the Cluster Management Suite
If you have not already configured your browser for CMS, refer to the Release Notes for the Catalyst 2950 Cisco IOS Release 12.0(5)WC(1) for detailed instructions on configuring the browsers.
When you enter the switch IP address in the browser Location field (Netscape Communicator) or Address field (Internet Explorer), the Cisco Systems Access page (Figure 3-7) is displayed. Click Cluster Management Suite or Visual Switch Manager. Cluster Builder or Cluster Manager displays (Figure 3-8).
Figure 3-7 Cisco Systems Access Page
After you have created a cluster, you can use Cluster Manager to monitor and configure the cluster switches. Figure 3-8 shows a cluster displayed in Cluster Manager. The switch software updates the LEDs displayed on these images in real time, making the images displayed by Cluster Manager as informative as the switch LEDs themselves. You can also use Cluster Builder and Cluster View to manage your cluster.
Figure 3-8 Cluster Manager
Configuring Initial Cluster Settings
This section describes how to customize the CMS environment to meet
your needs.Arranging and Saving the Network Map
You can reposition devices in Cluster Builder and Cluster View and save this information. Before arranging and saving the network map, make sure that the command switch discovered all the devices and that you have added them to the cluster.
You arrange the layout by clicking and holding the left mouse-button on a device and dragging it to a new location on the map. Select Options > Save Layout from the menu bar to save the arrangement displayed by Cluster Builder and Cluster View.
If the topology did not change, the saved version of the network map displays the next time you start Cluster Builder or Cluster View. If a topology change occurs, you can arrange the devices and save the map again.
Changing User Settings
Select Cluster > User Settings from the menu bar in Cluster View, Cluster Builder, or Cluster Manager to change the parameters described in the following list. The user settings are automatically saved in permanent storage on the command switch.
•
Reload the page for the new setting to take effect.
Tips
•
24 seconds. Reload the page for the new setting to take effect.•
•
Rearranging the Order of the Displayed Switches
You can arrange the order in which switches are displayed in Cluster Manager to match the arrangement in your wiring closet. Select Cluster > Device Position from the menu bar to display the Device Position window (Figure 3-9). Select a device in the Device Position window, and use the arrows to move it up or down in the list. Click OK when you are finished.
Figure 3-9 Device Position
Changing the Host Name
You can change the host name of any switch in the cluster by using Cluster Builder.
To change the host name of a member switch in Cluster Builder, right-click the switch, and select Host Name Config from the pop-up menu. Enter a host name of up to 28 characters in the field, and click OK. Member switch host names must be unique in the cluster. Do not use a number as the last character in a host name on any switch.
When you change the host name on the command switch, assign a name no longer than 28 characters. Limiting the command switch host name to 28 characters ensures that each member switch host name is unique and viewable in the application. The "Changes to the Host Name" section describes how the command switch appends a member number to its host name and propagates it to new switches not originally configured with a name when they joined the cluster.
Saving Configuration Changes
Configuration changes on the Catalyst 2950 switches are not written to Flash memory until you select System > Save Configuration in Cluster Manager or Options > Save Configuration in Cluster Builder or Cluster View.
As you make cluster configuration changes (except for changes to the network map and in the User Settings window), make sure you periodically save the configuration. The configuration is saved on the command and member switches.
Displaying an Inventory of Cluster Switches
You can display a summary table of all the switches in a cluster. The cluster inventory contains the following information:
•
•
•
•
•
To display the Inventory window (Figure 3-10), select System > Inventory. To display this information for a single switch, select the switch, right-click with the mouse, and select System > Inventory.
Figure 3-10 Inventory
Displaying Link Information
You can see how the cluster members are interconnected by using the Cluster Builder network map. It shows how the switches are connected and the type of connection between each device. Click Help > Legend in Cluster Builder to learn the meaning of each icon, link, and color.
To display port-connection information, select Views > Toggle Labels. By clicking Toggle Labels, you display the port numbers for each end of the link.
Changing the Management VLAN
Access to all switch management facilities is through the switch IP address, and the switch IP address always belongs to the management VLAN, VLAN 1, by default. This section describes how to configure a cluster to support management connectivity when the management VLAN is other than the default.
Guidelines for Changing the Management VLAN
The management VLAN has the following characteristics:
•
•
•
•
Before changing the management VLAN on your switch network, make sure you follow these guidelines:
•
•
•
•
Changing the Management VLAN for a Cluster
To manage switches in a cluster, the port connections among the command, member, and candidate switches must all be in the management VLAN. You can use the VLAN Management window (Figure 3-11) or the CLI to change the management VLAN of the command and member switches. Any VLAN can serve as the management VLAN as long as there are links between the command switch and the member switches for both the old and the new management VLANs.
Figure 3-11 Management VLAN
When you select the new VLAN to be the management VLAN, the IOS software coordinates the change on the member switches to ensure that the cluster continues running without a loss in management connectivity.
If your cluster includes members that are running a software release earlier than
Cisco IOS Release 12.0(5)XP, you cannot change the management VLAN of the cluster. If your cluster includes member switches that are running Cisco IOS Release 12.0(5)XP, those members need to have the VLAN changed before using the Management VLAN window. The procedure for changing member switches running Cisco IOS Release 12.0(5)XP is included in the Cisco IOS Desktop Switching Software Configuration Guide for Catalyst 2900 Series XL and Catalyst 3500 Series XL Cisco IOS Release 12.0(5)XP.
Caution
Changing the Management VLAN for a New Switch
For a new switch to be added to a cluster, it must first be connected to a port that belongs to the management VLAN of the cluster. If the cluster is configured with a management VLAN other than the default, the command switch changes the management VLAN for new switches when they are connected to the cluster. In this way, the new switch can exchange CDP messages with the command switch and be proposed as a cluster candidate.
Note
Because the switch is new and unconfigured, its management VLAN is changed to the cluster management VLAN when it is first added to the cluster. All ports that have an active link at the time of this change become members of the new management VLAN.
CLI: Changing the Management VLAN Through a Telnet Connection
Before you start, review the "Guidelines for Changing the Management VLAN" section. Beginning in privileged EXEC mode on the command switch, follow these steps to configure the management VLAN interface through a Telnet connection:
The "Finding More Information About IOS Commands" section contains the path to the complete IOS documentation.
Monitoring and Configuring Ports
You can configure one or more ports on the same switch by clicking them from Cluster Manager. You can also configure groups of ports from different switches as a group, and you can display the settings for each port. Table 3-1 describes the parameters that you can monitor and configure.
