White Papers

in reboot. A counter is maintained to inform the user about number of reboots required to make the target aggregator up
and running with the cloning file. The counter is incremented for the first instance that would require reboot. The counter is
incremented only when a conflicted or dependent instance is encountered. The counter is not incremented for the cases which
are mutually exclusive.
The current list identifies all command that requires reboot to take into effect.
Table 9. Command List — Reboot
Command Comments
Upgrade system stack-unit <> Action command, are not present in xxxx- config file
DCB enable autodetect on-next-reload Comes into picture after subsequent reload
stack-unit stack-number priority 1-14 Stacking specific. Stack config cloning is not supported.
stack-unit stack-number stack-group <> Stacking specific. Stack config cloning is not supported.
Stack-unit <> renumber <>
Restore factory defaults Action command, not present in xxxxx-config file.
Reset stack-unit Stacking specific
Power-cycle stack-unit <> Action command, not present in xxxxx-config file.
Global buffer profile
Cam-acl Not present in STOMP UI
Clonability Configuration apply command
Based on the status of check command on the target aggregator, you can proceed or abort the operation. When the clonability
check results in Failure, the clone config apply is automatically aborted. If clonability check results in Success, the Apply
command proceeds further without any intervention. If the Check results in Warnings, you are prompted to proceed or abort.
When the cloning configuration is getting committed, no new cloning checks are entertained until the target aggregator device
is up and running with the applied clone configuration. A log is generated once the target aggregator is running completely with
the cloned configuration.
214
Configuration Cloning