5-20
Cisco Catalyst Blade Switch 3130 and 3032 for Dell Software Configuration Guide
OL-12247-04
Chapter 5 Managing Switch Stacks
Understanding Switch Stacks
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.
Stack master election
specifically determined
by the cryptographic
software image and the
IP services feature set
and the IP services
feature set
Assuming that all stack members have the
same priority value:
1.
Make sure that one stack member has
the cryptographic image installed and
the IP services feature set enabled and
that the other stack member has the
noncryptographic image installed and
the IP services feature set enabled.
2.
Restart both stack members at the same
time.
The stack member with the cryptographic image and
the IP services feature set is elected stack master.
Stack master election
specifically determined
by the cryptographic
software image and the
IP base feature set
Assuming that all stack members have the
same priority value:
1.
Make sure that one stack member has
the cryptographic image installed and
the IP base feature set enabled and that
the other stack member has the
noncryptographic image installed and
the IP base feature set enabled.
2.
Restart both stack members at the same
time.
The stack member with the cryptographic image and
the IP base feature set is elected stack master.
Stack master election
specifically determined
by the MAC address
Assuming that both stack members have the
same priority value, configuration file, and
feature set, restart both stack members at
the same time.
The stack member with the lower MAC address is
elected stack master.
Stack member number
conflict
Assuming that one stack member has a
higher priority value than the other stack
member:
1.
Ensure that both stack members have
the same stack member number. If
necessary, use the
switch
current-stack-member-number
renumber
new-stack-member-number
global configuration command.
2.
Restart both stack members at the same
time.
The stack member with the higher priority value
retains its stack member number. The other stack
member has a new stack member number.
Table 5-2
Switch Stack Configuration Scenarios (continued)
Scenario
Result