Unconfiguring a 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.
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 the current stack unit, enter the following command.
device# stack unconfigure me
To remove the configuration from the current unit, including the startup configuration, so that the unit reboots as a clean unit, enter the following unit on the stack member console.
device# stack unconfigure clean
To remove the configuration from the entire stack, enter the following command on the active controller for the stack.
device# stack unconfigure all
To remove the configuration from a specific stack unit, on the active controller for
the stack, enter the
stack unconfigure command followed by the stack unit ID as shown in the following example.
device# stack unconfigure 3
The example unconfigures stack unit 3.
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.
ICX7250-48 Router# show stack T=15d23h18m0.7: alone: standalone, D: dynamic cfg, S: static ID Type Role Mac Address Pri State Comment 1 S ICX7250-48 active cc4e.24b4.23e8 0 local Ready 2 S ICX7250-24P standby cc4e.24b4.8aa8 0 remote Ready 3 S ICX7250-24 member cc4e.24b4.8cc4 0 remote Ready ! ! ICX7250-48 Router# 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 ICX7250-48 Router(config-unit-1)# show stack T=15d23h18m0.7: alone: standalone, D: dynamic cfg, S: static ID Type Role Mac Address Pri State Comment 1 S ICX7250-48 active cc4e.24b4.23e8 0 local Ready 2 S ICX7250-24P member cc4e.24b4.8aa8 0 reserved 3 S ICX7250-24 standby cc4e.24b4.8cc4 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.