Cisco Systems 3130 User Manual
5-20
Cisco Catalyst Blade Switch 3130 for Dell Software Configuration Guide
OL-13270-01
Chapter 5 Managing Switch Stacks
Understanding Switch Stacks
Stack master election
specifically determined
by the cryptographic
software image and the IP
base feature set
specifically determined
by the cryptographic
software image and the IP
base feature set
Assuming that all stack members have the
same priority value:
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.
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.
time.
The stack member with the cryptographic image and
the IP base feature set is elected stack master.
the IP base feature set is elected stack master.
Stack master election
specifically determined
by the MAC address
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.
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.
elected stack master.
Stack member number
conflict
conflict
Assuming that one stack member has a
higher priority value than the other stack
member:
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.
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.
time.
The stack member with the higher priority value
retains its stack member number. The other stack
member has a new stack member number.
retains its stack member number. The other stack
member has a new stack member number.
Add a stack member
1.
Power off the new switch.
2.
Through their StackWise Plus ports,
connect the new switch to a powered-on
switch stack.
connect the new switch to a powered-on
switch stack.
3.
Power on the new switch.
The stack master is retained. The new switch is
added to the switch stack.
added to the switch stack.
Stack master failure
Remove (or power off) the stack master.
Based on the factors described in the
, one
of the remaining stack members becomes the new
stack master. All other stack members in the stack
remain as stack members and do not reboot.
stack master. All other stack members in the stack
remain as stack members and do not reboot.
Add more than nine stack
members
members
1.
Through their StackWise Plus ports,
connect ten switches.
connect ten switches.
2.
Power on all switches.
Two switches become stack masters. One stack
master has nine stack members. The other stack
master remains as a standalone switch.
master has nine stack members. The other stack
master remains as a standalone switch.
Use the Mode button and port LEDs on the switches
to identify which switches are stack masters and
which switches belong to each stack master. For
information about using the Mode button and the
LEDs, see the hardware installation guide.
to identify which switches are stack masters and
which switches belong to each stack master. For
information about using the Mode button and the
LEDs, see the hardware installation guide.
Table 5-2
Switch Stack Configuration Scenarios (continued)
Scenario
Result