5-18
Catalyst 3750-X and 3560-X Switch Software Configuration Guide
OL-21521-01
Chapter 5 Managing Switch Stacks
Understanding Switch Stacks
Be careful when using multiple CLI sessions to the stack master. Commands that you enter in one session
are not displayed in the other sessions. Therefore, it is possible that you might not be able to identify the
session from which you entered a command.
We recommend using only one CLI session when managing the switch stack.

Connectivity to Specific Stack Members

If you want to configure a specific stack member port, you must include the stack member number in the
CLI command interface notation. For more information, see the “Using Interface Configuration Mode”
section on page 13-17.
To debug a specific stack member, you can access it from the stack master by using the session
stack-member-number privileged EXEC command. The stack member number is appended to the system
prompt. For example, Switch-2# is the prompt in privileged EXEC mode for stack member 2, and the
system prompt for the stack master is Switch. Only the show and debug commands are available in a
CLI session to a specific stack member.
Switch Stack Configuration Scenarios
Table 5-2 provides switch stack configuration scenarios. Most of the scenarios assume that at least two
switches are connected through their StackWise Plus ports.
Tab le 5-2 Switch Stack Configuration Scenarios
Scenario Result
Stack master election
specifically determined
by existing stack masters
Connect two powered-on switch stacks
through the StackWise Plus ports.
Only one of the two stack masters becomes the new
stack master. None of the other stack members
become the stack master.
Stack master election
specifically determined
by the stack member
priority value
1. Connect two switches through their
StackWise Plus ports.
2. Use the switch stack-member-number
priority new-priority-number global
configuration command to set one stack
member with a higher member priority
value.
3. Restart both stack members at the same
time.
The stack member with the higher priority value is
elected stack master.
Stack master election
specifically determined
by the configuration file
Assuming that both stack members have the
same priority value:
1. Make sure that one stack member has a
default configuration and that the other
stack member has a saved (nondefault)
configuration file.
2. Restart both stack members at the same
time.
The stack member with the saved configuration file
is elected stack master.