Managing a Switch Stack 139
might trigger many other protocols. However, it is possible to intentionally
pre-configure a unit. You can view the preconfigured/unassigned units by
using the show switch CLI command.
If a new switch is added to a stack of switches that are powered and running
and already have an elected Management Unit, the newly added switch
becomes a stack member rather than the Management Unit.
You can preconfigure information about a stack member and its ports before
you add it to the stack. The preconfiguration takes place on the Management
Unit. If there is saved configuration information on the Management Unit for
the newly added unit, the Management Unit applies the configuration to the
new unit; otherwise, the Management Unit applies the default configuration
to the new unit.
Removing a Switch from the Stack
The main point to remember when you remove a unit from the stack is to
disconnect all the links on the stack member to be removed. Also, be sure to
take the following actions:
• Remove all the STP participating ports and wait to stabilize the STP.
• Remove all the member ports of any Port-Channels (LAGs) so there will
not be any control traffic destined to those ports connected to this
member.
• Statically re-route any traffic going through this unit.
When a unit in the stack fails, the Master unit removes the failed unit from
the stack. No changes or configuration are applied to the other stack
members; however, the dynamic protocols will try to reconverge as the
topology could change because of the failed unit. When there are no
connected ports on the failed unit, the stack will be intact without any
changes.
If you remove a unit and plan to renumber the stack, issue a no member
unit
command in Stack Configuration mode to delete the removed switch from
the configured stack member information.
To Next Page
Loading...
