Users Guide

Cloning state (captured in command
output)
Cloning status (captured in command
output)
Applicability
Warning Minor release version mismatch Target
If the compatibility check passes through, the target aggregator strips the cloning header and proceeds to parsing actual conguration in
the cloning-le. It goes through the conguration one by one and checks if any command or feature requires 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 le. The
counter is incremented for the rst instance that would require reboot. The counter is incremented only when a conicted or dependent
instance is encountered. The counter is not incremented for the cases which are mutually exclusive.
The current list identies all command that requires reboot to take into eect.
Table 3. Command List — Reboot
Command Comments
Upgrade system stack-unit <> Action command, are not present in xxxx- cong le
DCB enable autodetect on-next-reload Comes into picture after subsequent reload
stack-unit stack-number priority 1-14 Stacking specic. Stack cong cloning is not supported.
stack-unit stack-number stack-group <> Stacking specic. Stack cong cloning is not supported.
Stack-unit <> renumber <>
Restore factory defaults Action command, not present in xxxxx-cong le.
Reset stack-unit Stacking specic
Power-cycle stack-unit <> Action command, not present in xxxxx-cong le.
Global buer prole
Cam-acl Not present in STOMP UI
Clonability Conguration 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 conguration is getting committed, no new cloning checks are entertained until the target aggregator device is up and
running with the applied clone conguration. A log is generated once the target aggregator is running completely with the cloned
conguration.
Conguration
Cloning 33