5-4
Catalyst 2950 Desktop Switch Software Configuration Guide
78-11380-03
Chapter 5 Clustering Switches
Planning a Switch Cluster
Planning a Switch Cluster
Anticipating conflicts and compatibility issues is a high priority when you manage several switches
through a cluster. This section describes these guidelines, requirements, and caveats that you should
understand before you create the cluster:
• Automatic Discovery of Cluster Candidates and Members, page 5-4
• HSRP and Standby Command Switches, page 5-10
• IP Addresses, page 5-13
• Host Names, page 5-14
• Passwords, page 5-14
• SNMP Community Strings, page 5-14
• TACACS+, page 5-15
• Access Modes in CMS, page 5-15
• Management VLAN, page 5-15
• LRE Profiles, page 5-16
• Availability of Switch-Specific Features in Switch Clusters, page 5-16
Refer to the release notes for the list of Catalyst switches eligible for switch clustering, including which
ones can be command switches and which ones can only be member switches, and for the required
software versions and browser and Java plug-in configurations.
Automatic Discovery of Cluster Candidates and Members
The command switch uses Cisco Discovery Protocol (CDP) to discover member switches, candidate
switches, neighboring switch clusters, and edge devices in star or cascaded topologies.
Note Do not disable CDP on the command switch, on cluster members, or on any cluster-capable switches that
you might want a command switch to discover. For more information about CDP, see the “Configuring
CDP” sectiononpage6-13.
Following these connectivity guidelines ensures automatic discovery of the switch cluster, cluster
candidates, connected switch clusters, and neighboring edge devices:
• Discovery through CDP Hops, page 5-5
• Discovery through Non-CDP-Capable and Noncluster-Capable Devices, page 5-6
• Discovery through Different Management VLANs, page 5-8
• Discovery through the Same Management VLAN, page 5-7
• Discovery of Newly Installed Switches, page 5-9