Page 321 / 400 Scroll up to view Page 316 - 320
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-9
202-10088-01, March 2005
Switch Stack Management Connectivity
You manage the switch stack and the stack member interfaces through the stack master. You can
use the web interface, the CLI, and SNMP. You cannot manage stack members on an individual
switch basis.
Connectivity to the Switch Stack Through Console Ports
You can connect to the stack master through the console port of the stack master only.
Connectivity to the Switch Stack Through Telnet
You can connect to the stack master using telnet by telnetting to the ip address of the stack.
Switch Stack Configuration Scenarios
Table 12-2
provides switch stack configuration scenarios. Most of the scenarios assume at least
two switches are connected through their stacking ports.
Table 12-2.
Switch stack configuration scenarios
Scenario
Result
Stack master election specifically determined by
existing stack masters
Note
: This is not recommended.
Connect two powered-on switch stacks through
the stacking 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
Connect two switches through their stacking
ports.
Use the
switch
stack-member-number
priority
new-priority-number
global configuration
command to set one stack member to a higher
member priority value.
Restart both stack members at the same time.
The stack member with the higher priority value is
elected stack master.
Page 322 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-10
Managing Switch Stacks
202-10088-01, March 2005
Stacking Recommendations
The purpose of this section is to collect notes on recommended procedures and expected behavior
of stacked FSM7328S/FSM7352S. Procedures addressed initially are listed below.
Initial installation and power-up of a stack.
Removing a unit from the stack
Adding a unit to an operating stack
Replacing a stack member with a new unit
Renumbering stack members
Moving the master to a different unit in the stack
Removing a master unit from an operating stack
Merging two operational stacks
Preconfiguration
Upgrading firmware
Migration of configuration with a firmware upgrade
Stack master election specifically determined by
the MAC address
Assuming that both stack members have the
same priority value and software image, restart
both stack members at the same time.
The stack member with the higher MAC address is
elected stack master.
Add a stack member
Power off the new switch
Through their stacking ports, connect the new
switch to a powered-on switch stack.
Power on the new switch.
The stack master is retained. The new switch is
added to the switch stack.
Stack master failure
Remove (or power off) the stack master.
Based on "Stack Master Election and Re-Election"
on page 5, 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.
Table 12-2.
Switch stack configuration scenarios
(continued)
Page 323 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-11
202-10088-01, March 2005
General Practices
When issuing a command (such as move management, or renumber), it is recommended that
the command has fully completed before issuing the next command. For example, if a reset is
issued to a stack member, use the “show port” command to verify that the unit has remerged
with the stack, and all ports are joined before issuing the next command.
When physically removing or relocating a unit, always power down the unit before
disconnecting stack cables.
When reconnecting stack cables, connect them before powering up the unit, if possible, and
insure a good connection by tightening all connector screws (where applicable).
Initial installation and Power-up of a Stack
1.
Install units in rack.
2.
Install all stacking cables. Fully connect, including the redundant stack link. It is highly
recommended that a redundant link be installed.
3.
Identify the unit to be the master. Power this unit up first.
4.
Monitor the console port. Allow this unit to come up to the login prompt. If unit has the default
configuration, it should come up as unit #1, and will automatically become a master unit. If
not, renumber as desired.
5.
If desired, preconfigure other units to be added to the stack. Preconfiguration is described in
Section Preconfiguration.
6.
Power on a second unit, making sure it is adjacent (next physical unit in the stack) to the unit
already powered up. This will insure the second unit comes up as a member of the stack, and
not a “Master” of a separate stack.
7.
Monitor the master unit to see that the second unit joins the stack. Use the “show switch”
command to determine when the unit joins the stack. It will be assigned a unit number (unit
#2, if it has the default configuration).
8.
Renumber this stack unit, if desired. See section Renumbering Stack Members on
recommendations for renumbering stack members.
9.
Repeat steps 6 through 8 to add additional members to the stack. Always power on a unit
adjacent to the units already in the stack.
Page 324 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
12-12
Managing Switch Stacks
202-10088-01, March 2005
Removing a Unit from the Stack
1.
Make sure the redundant stack connection is in place and functional. All stack members
should be connected in a logical ring.
2.
Power down the unit to be removed.
3.
Disconnect stack cables.
4.
If unit is not to be replaced, reconnect the stack cable from the stack member above to the
stack member below the unit being removed.
5.
Remove unit from the rack.
6.
If desired, remove the unit from the configuration by issuing the command:
no member
<unit-id>
Adding a Unit to an Operating Stack
1.
Make sure the redundant stack connection is in place and functional. All stack members
should be connected in a logical ring.
2.
Preconfigure the new unit, if desired.
3.
Install new unit in the rack. (Assumes installation below the bottom-most unit, or above the
top-most unit).
4.
Disconnect the redundant stack cable that connects the last unit in the stack back up to the first
unit in the stack at the position in the ring where the new unit is to be inserted.
5.
Connect this cable to the new unit, following the established order of “stack up” to “stack
down” connections
6.
Power up the new unit. Verify, by monitoring the master unit console port, that the new unit
successfully joins the stack by issuing the
show switch
command. The new unit should always
join as a “member” (never as master; the existing master of the stack should not change).
7.
If the code version of the newly added member is not the same as the existing stack, update the
code as described in section Upgrading Firmware.
Replacing a Stack Member with a New Unit
There are two possible situations here. First, if you replace a stack member of a certain model
number with another unit of the same model, follow the process below:
Page 325 / 400
User Manual for the NETGEAR 7300S Series Layer 3 Managed Switch Software
Managing Switch Stacks
12-13
202-10088-01, March 2005
Follow the process in section Removing a Unit from the Stack to remove the desired stack
member.
Follow the process in section Adding a Unit to an Operating Stack to add a new member to the
stack with the following exceptions:
Insert the new member in the same position in the stack as the one removed.
Preconfiguration described in step Preconfigure the new unit, if desired. of that procedure
is not required.
Second, if you replace a stack member with another unit of a different model number, use the
following process:
Follow the process in section Removing a Unit from the Stack to remove the desired stack
member.
Remove the now-absent stack member from the configuration by issuing the command
no
member
command.
Add the new stack unit to the stack using the process described in section Adding a Unit to an
Operating Stack. The unit can be inserted into the same position as the unit just removed, or
the unit can be inserted at the bottom of the stack. In either case, make sure all stack cables are
connected with the exception of the cable at the position where the new unit is to be inserted to
insure that the stack does not get divided into two separate stacks, causing the election of a
new master.
Renumbering Stack Members
1.
If particular numbering is required, it is recommended that stack members be assigned specific
numbers when they are first installed and configured in the stack, if possible.
2.
If the desired stack unit number for a particular unit is unused, a unit can be renumbered
simply by using the
switch
<oldunit-id>
renumber
<newunit-id> CLI command. This
command is found in global config mode.
3.
If the newunit-id has been preconfigured, you may need to remove the newunit-id from the
configuration before renumbering the unit.
4.
If reassignment of multiple existing stack unit numbers is necessary, there are a number of
implications in terms of mismatching of configuration. In this case, it is recommended that all
units except the master be powered down and added back one at a time using the procedure in
Section Adding a Unit to an Operating Stack.

Rate

4.5 / 5 based on 2 votes.

Bookmark Our Site

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

Share
Top