5-3
Catalyst 2960 Switch SoftwareConfiguration Guide
78-16881-01
Chapter5 Clustering Switches
Using the CLI to Manage Switch Clusters
•It is redundantly connected to the cluster so that connectivity to cluster member switches is
maintained.
•It is not a command or member switch of another cluster.
Note Standby cluster command switches must be the same type of switches a s the cluster command
switch. For example, if the cluster command switch is a Catalyst2960 switch, the standby
cluster command switches must also be Catalyst 2960 switches. See the switch configuration
guides of other cluster-capable switches for their requirements on standby cluster command
switches.

Candidate Switch and Cluster Member Switch Characteristics

Candidate switches are cluster-capable switches that have not yet been added to a cluster. Cluster
member switches are switches that have actually been added to a switch cluster. Although not required,
a candidate or cluster member switch can have its own IP address and password.
To join a cluster, a candidate switch must meet these requirements:
•It is running cluster-capable software.
•It has CDP Version 2 enabled.
•It is not a command or cluster member switch of another cluster.
•If a cluster standby group exists, it is connected to every standby cluster command switch through
at least one common VLAN. The VLAN to each standby cluster command switch can be different.
•It is connected to the cluster command switch through at least one common VLAN.
Note Catalyst 1900, Catalyst 2820, Catalyst 2900 XL, Catalyst 2950, and Catalyst 3500 XL
candidate and cluster member switches must be connected through their management VLAN
to the cluster command switch and standby cluster command switches. For complete
information about these switches in a switch-cluster environment, see the software
configuration guide for that specific switch.
This requirement does not apply if you have a Catalyst 2970, 2960, 3550, 3560, or 3750
cluster command switch. Candidate and cluster member switches c an connect through any
VLAN in common with the cluster command switch.
Using the CLI to Manage Switch Clusters
You can configure cluster member switches from the CLI by first logging into the cluster command
switch. Enter the rcommand user EXEC command and the cluster member switch number to start a
Telnet session (through a console or Telnet connection) and to access the cluster member switch CLI.
The command mode changes, and the Cisco IOS commands operate as usual. Enter the exit privileged
EXEC command on the cluster member switch to return to the command-switch CLI.
This example shows how to log into member-switch 3 from the command-switch CLI:
switch# rcommand 3