Unconfiguring a traditional stack

The stack unconfigure command is a runtime command that returns stack units to their pre-stacking state. When a stack unit is unconfigured, its stacking flash is removed, and its startup-config.txt flash file is recovered. These actions apply to all units to which this command is applied, regardless of the role of the unit in the stack.

When the stack unconfigure command is applied to the active controller, it removes stack enable from the runtime configuration but not from the startup configuration. If you want to remove the stack enable command from the active controller permanently, you must enter the write memory command after the stack unconfigure command.

When the stack unconfigure command is applied to the standby controller or a stack member (besides the active controller), it removes stack enable from the recovered startup-config.txt file and resets the unit.

NOTE
When a stack member becomes a standalone unit after the stack unconfigure command, it could become a clean unit if it had no startup configuration flash. When a clean unit matches the active controller’s static configuration, the active controller integrates the clean unit into the stack. Thus, the standalone unit is reloaded to be a member of the stack. Users can avoid this problem by disconnecting the member unit from the stack and issuing the stack unconfigure me command on the unit to change it to a standalone unit.

To remove the configuration from a specific traditional stack unit or from the entire stack, enter a command similar to the following.

device# stack unconfigure me

Syntax: stack unconfigure [ stack-unit | all | me | clean ]

  • stack-unit - Unconfigures the stack member with this ID
  • all - Unconfigures every unit including this unit
  • me - Unconfigures this unit only
  • clean - Removes all startup configuration files including v4 and v5 and makes this a clean unit
NOTE
The stack unconfigure me command can be entered from any unit; however, stack unconfigure all and stack unconfigure stack-unit commands can be issued only on the active controller.

The following example shows a session where stack unit 2 is unconfigured.

ICX7750-48XGC# show stack
alone: standalone, D: dynamic config, S: static config
ID   Type          Role    MAC Address       Pri State    Comment
1 S  ICX7750-48XGC active  0000.00eb.a900    128 local    Ready
2 S  ICX7750-48XGC standby 0000.004f.4243      0 remote   Ready
3 S  ICX7750-48XGC member  0000.0001.0100      0 remote   Ready
ICX7750-48XGC# stack unconfigure 2
Will recover pre-stacking startup config of this unit, and reset it. Are you sure? (enter 'y' or 'n'): y
Stack 2 deletes stack bootup flash and recover startup-config.txt from .old
ICX7750-48XGC# show stack
alone: standalone, D: dynamic config, S: static config
ID   Type          Role    MAC Address       Pri State    Comment
1 S  ICX7750-48XGC active  0000.00eb.a900    128 local    Ready
2 S  ICX7750-48XGC member  0000.0000.0000      0 reserved
3 S  ICX7750-48XGC standby 0000.0001.0100      0 remote   Ready

When the stack unconfigure 2 command is issued, stack unit 2 recovers the startup-config.txt from the startup-config.old configuration file that was saved when this unit downloaded its configuration from the active controller. As the output shows, stack member 2 has been removed from the stack, and ID 2 is now reserved for a replacement unit. Stack member 3 is now the standby controller.