Cisco Systems 3560 Manual Do Utilizador

Página de 1288
 
6-14
Catalyst 3560 Switch Software Configuration Guide
OL-8553-06
Chapter 6      Clustering Switches
Planning a Switch Cluster
If you change the member-switch password to be different from the command-switch password and save 
the change, the switch is not manageable by the cluster command switch until you change the 
member-switch password to match the command-switch password. Rebooting the member switch does 
not revert the password back to the command-switch password. We recommend that you do not change 
the member-switch password after it joins a cluster.
For more information about passwords, see the 
.
For password considerations specific to the Catalyst 1900 and Catalyst 2820 switches, refer to the 
installation and configuration guides for those switches.
SNMP Community Strings
A cluster member switch inherits the command-switch first read-only (RO) and read-write (RW) 
community strings with @esN appended to the community strings:
  •
command-switch-readonly-community-string@esN, where N is the member-switch number. 
  •
command-switch-readwrite-community-string@esN, where N is the member-switch number.
If the cluster command switch has multiple read-only or read-write community strings, only the first 
read-only and read-write strings are propagated to the cluster member switch.
The switches support an unlimited number of community strings and string lengths. For more 
information about SNMP and community strings, see 
For SNMP considerations specific to the Catalyst 1900 and Catalyst 2820 switches, refer to the 
installation and configuration guides specific to those switches.
TACACS+ and RADIUS
If Terminal Access Controller Access Control System Plus (TACACS+) is configured on a cluster 
member, it must be configured on all cluster members. Similarly, if RADIUS is configured on a cluster 
member, it must be configured on all cluster members. Further, the same switch cluster cannot have some 
members configured with TACACS+ and other members configured with RADIUS.
For more information about TACACS+, see the 
. For more information about RADIUS, see the 
LRE Profiles    
A configuration conflict occurs if a switch cluster has Long-Reach Ethernet (LRE) switches that use both 
private and public profiles. If one LRE switch in a cluster is assigned a public profile, all LRE switches 
in that cluster must have that same public profile. Before you add an LRE switch to a cluster, make sure 
that you assign it the same public profile used by other LRE switches in the cluster. 
A cluster can have a mix of LRE switches that use different private profiles.