Administrator Guide

Cloning state (captured in
command output)
Cloning status (captured in
command output)
Applicability
Failure Release version mismatch Target
Failure Card type mismatch Target
Failure Optional –module mismatch at
slot <>
Target
Failure IOM-mode mismatch Target
Failure The specified file doesn’t exist to
check compatibility
Target
Failure The specified file cannot be
applied as it ‘failed’ compatibility
check.
Target
Failure The specified file has not
completed for compatibility check.
Target
Warning Uplink bandwidth mismatch Target
Warning BMP is disabled to complete
cloning operation.
Target
Warning IOM modes are changed from <>
to <> to complete cloning
operation.
Target
Warning Minor release version mismatch Target
If the compatibility check passes through, the target aggregator strips the cloning header and proceeds to
parsing actual configuration in the cloning-file. It goes through the configuration 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 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
Configuration Cloning 263