Dismantling a Stack

To dismantle a stack and use the Summit switches in stand-alone mode, do the following:

Issue the show stacking stack-ports command to see if any nodes in the stack are using alternate stacking ports.

In the following example, the switches in slots 1 and 2 have 24 data ports, and the switches in slots 3 and 4 have 12 data ports. The numbers in the Select column show that all ports in this stack are alternate stacking ports, not regular data ports.

Slot-1 Stack.5 # show stacking stack-ports
Stack Topology is a Ring
Slot Port Select Node MAC Address  Port State  Flags Speed
---- ---- ------ ----------------- ----------- ----- -----
*1   1    27     00:04:96:9c:e4:39 Operational C-      10G
*1   2    28     00:04:96:9c:e4:39 Operational CB      10G
2   1    27     00:04:96:9b:c1:34 Operational CB      10G
2   2    28     00:04:96:9b:c1:34 Operational C-      10G
3   1    15     00:04:96:9e:5c:76 Operational C-      10G
3   2    16     00:04:96:9e:5c:76 Operational C-      10G
4   1    15     00:04:96:9c:53:b6 Operational C-      10G
4   2    16     00:04:96:9c:53:b6 Operational C-      10G
* - Indicates this node
Flags:  (C) Control path is active, (B) Port is Blocked

For every non-master node in the stack that is using alternate stacking ports, log into the node and issue the unconfigure stacking-support command.
Do not reboot any of the switches.
If step 1 showed that no alternate stacking ports are in use, skip this step.
Note
- This command resets the ports so that they are no longer dedicated for use as stacking ports.
- It is not necessary to unconfigure stacking-support on the master node.
- If a node is a member of the active topology, you can log in to other nodes using the telnet slot slot-number {no-auto-login} command. Otherwise, you need access to the node's console port, or you need to log in through a management network.
Log into the master node and issue the unconfigure switch all command.
After this command is entered, the configuration file is deselected, all stacking parameters are reset to factory defaults, and all nodes in the active topology reboot. In effect, this sets all nodes back to the factory default configuration, thus allowing each switch to be redeployed individually.
Restore the saved configuration for each switch, if applicable.

Published March 2020prev | next

Email this topic

Print this page Print this page

Leave feedback Feedback