Tacacs+ And Radius; Lre Profiles; Using The Cli To Manage Switch Clusters - Cisco 3750G - Catalyst Integrated Wireless LAN Controller Configuration Manual

Using the CLI to Manage Switch Clusters

•
•
•
•
For more information about switch stacks, see

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
page
section on page

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.
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
Catalyst 3750 Switch Software Configuration Guide
6-16
If the cluster command switch is a switch stack and new stack masters are simultaneously elected in
the cluster command switch stack and in cluster member switch stacks, connectivity between the
switch stacks is lost if there are no redundant connections between the switch stack and the cluster
command switch. You must add the switch stacks to the cluster, including the cluster command
switch stack.
All stack members should have redundant connectivity to all VLANs in the switch cluster.
Otherwise, if a new stack master is elected, stack members connected to any VLANs not configured
on the new stack master lose their connectivity to the switch cluster. You must change the VLAN
configuration of the stack master or the stack members and add the stack members back to the switch
cluster.
If a cluster member switch stack reloads and a new stack master is elected, the switch stack loses
connectivity with the cluster command switch. You must add the switch stack back to the switch
cluster.
If a cluster command switch stack reloads, and the original stack master is not re-elected, you must
rebuild the entire switch cluster.
9-10. For more information about RADIUS, see the
9-17.
Chapter 5, "Managing Switch Stacks,"
"Controlling Switch Access with TACACS+" section on
"Controlling Switch Access with RADIUS"
Chapter 6 Clustering Switches
OL-8550-02