Page 316 / 400 Scroll up to view Page 311 - 315
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-4
Managing Switch Stacks
202-10088-01, March 2005
Switch Stack Cabling
Figure 12-1
and
Figure 12-2
illustrate how individual switches are interconnected to form a stack.
You can use the regular Category 5 Ethernet 8 wire cable.
Figure 12-1:
Interconnecting individual FSM7328S switches to form a stack
Figure 12-2:
Interconnecting individual FSM7352S switches to form a stack
FSM73285
FSM73285
FSM73285
Interconnect
ports 27 and 28
as shown
port 27
port 28
FSM73525
FSM73525
FSM73525
Interconnect
ports 51 and 52
as shown
port 51
port 52
Page 317 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-5
202-10088-01, March 2005
Stack Master Election and Re-Election
The stack master is elected or re-elected based on one of these factors and in the order listed:
1.
The switch that is currently the stack master
2.
The switch with the highest stack member priority value
Note
: Netgear recommends assigning the highest priority value to the switch that you prefer to
be the stack master. This ensures that the switch is re-electedas stack master if a re-election
occurs.
3.
The switch with the higher MAC address
A stack master retains its role unless one of these events occurs:
The stack master is removed from the switch stack
The stack master is reset or powered off
The stack master has failed
The switch stack membership is increased by adding powered-on standalone switches or
switch stacks
In the case of a master re-election, the new stack master becomes available after a few seconds. In
the meantime, the switch stack uses the forwarding tables in memory to minimize network
disruption. The physical interfaces on the other available stack members are not affected while a
new stack master is elected.
If a new stack master is elected and the previous stack master becomes available, the previous
stack master does not resume its role as stack master.
Stack Member Numbers
A stack member number (1 to 8) identifies each member in the switch stack. The member number
also determines the interface-level configuration that a stack member uses. You can display the
stack member number by using the
show switch
user EXEC command.
A new, out-of-the-box switch (one that has not joined a switch stack or has not been manually
assigned a stack member number) ships with a default stack member number of 1. When it joins a
switch stack, its default stack member number changes to the lowest available member number in
the stack.
Page 318 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-6
Managing Switch Stacks
202-10088-01, March 2005
Stack members in the same switch stack cannot have the same stack member number. Every stack
member, including a standalone switch, retains its member number until you manually change the
number or unless the number is already being used by another member in the stack.
See
“Renumbering Stack Members” on page 12-13
and
“Merging Two Operational Stacks” on
page 12-14
.
Stack Member Priority Values
A stack member priority can be changed if the user would like change who is the master of the
stack. Use the following command to change stack member's priority (this command is in the
global config mode):
switch
unit
priority
value
Switch Stack Offline Configuration
You can use the offline configuration feature to preconfigure (supply a configuration to) a new
switch before it joins the switch stack. You can configure in advance the stack member number,
the switch type, and the interfaces associated with a switch that is not currently part of the stack.
See
“Preconfiguration” on page 12-15
.
Effects of Adding a Preconfigured Switch to a Switched Stack
When you add a preconfigured switch to the switch stack, the stack applies either the
preconfigured configuration or the default configuration.
Table 12-1
lists the events that occur
when the switch stack compares the preconfigured configuration with the new switch:
Page 319 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-7
202-10088-01, March 2005
Effects of Replacing a Preconfigured Switch in a Switch Stack
When a preconfigured switch in a switch stack fails, is removed from the stack, and is replaced
with another switch, the stack applies either the preconfiguration or the default configuration to it.
The events that occur when the switch stack compares the configuration with the preconfigured
switch are the same as those described in
“Effects of Adding a Preconfigured Switch to a Switched
Stack” on page 12-6
.
Effects of Removing a Preconfigured Switch from a Switch Stack
If you remove a preconfigured switch from the switch stack, the configuration associated with the
removed stack member remains in the running configuration as configured information. To
completely remove the configuration, use the
no member
unit_number
(this is in the stacking
configuration mode).
Table 12-1.
Results of comparing the preconfiguration with the new switch
Scenario
Result
The stack member numbers and the switch types
match.
If the stack member number of the preconfigured
switch matches the stack member number in the
configuration on the stack, and
If the switch type of the preconfigured switch
matches the switch type in the configuration on
the stack.
The switch stack applies the configuration to the
preconfigured new switch and adds it to the stack.
The stack member numbers match but the switch
types do not match.
If the stack member number of the preconfigured
switch matches the stack member number in the
configuration on the stack, but
The switch type of the preconfigured switch does
not match the switch type in the configuration on
the stack.
The switch stack applies the default configuration
to the preconfigured switch and adds it to the
stack.
The configuration in the preconfigured switch is
changed to reflect the new information.
The stack member number is not found in the
configuration.
The switch stack applies the default configuration
to the new switch and adds it to the stack.
The preconfigured information is changed to
reflect the new information.
The stack member number of the preconfigured
switch is not found in the configuration.
The switch stack applies the default configuration to
the preconfigured switch and adds it to the stack.
Page 320 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-8
Managing Switch Stacks
202-10088-01, March 2005
Switch Stack Software Compatibility Recommendations
All stack members must run the same software version to ensure compatibility between stack
members. The software versions on all stack members, including the stack master, must be the
same. This helps ensure full compatibility in the stack protocol version among the stack members.
If a stack member is running a software version that is not the same as the stack master, then the
stack member is not allowed to join the stack. Use the
show switch
command to list the stack
members and software versions. See
“Code Mismatch” on page 12-16
.
Incompatible Software and Stack Member Image Upgrades
You can upgrade a switch that has an incompatible software image by using the
archive
download-sw
xmodem | ymodem | zmodem | tftp://
ip/filepath/filename
command (this is in the
stacking configuration mode). It copies the software image from an existing stack member to the
one with incompatible software. That switch automatically reloads and joins the stack as a fully
functioning member.
Switch Stack Configuration Files
The configuration files record settings for all global and interface specific settings that define the
operation of the stack and individual members. Once a
save config
command is issued, all stack
members store a copy of the configuration settings. If a stack master becomes unavailable, any
stack member assuming the role of stack master will operate from the saved configuration files.
When a new, out-of-box switch joins a switch stack, it uses the system-level settings of that switch
stack. However, if you want it to store this system level configuration, you must issue a
save
config
command.
You back up and restore the stack configuration in the same way as you would for standalone
switch configuration by using the copy command.

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

Press Ctrl + D to add this site to your favorites!

Share
Top