Dell PowerEdge FN I/O Module Configuration Guide 9.10(0.0)

Cloning Configuration Output Status

If you specify the XML option in the CLI, the output of the CLI commands is displayed in XML format.

The output includes the following parameters:

Cloning state displays one of the following status:
- Success
- Warning
- Failure
Cloning detailed status displays a string that gives detailed description of cloning status. When multiple error or warning messages are present, the status is separated by the ; delimiter.
Cloning status codes are useful when there are multiple warning or failure messages. Each warning or failure message is given a code number; this status can list the message codes that can be decoded when the cloning status string could not accommodate all the errors and warnings.
Number of Reboots count the number of reboots required to complete the cloning operation. The reboot details can be displayed only when the clonability check is done.

Table 1. Cloning Status
Cloning state (captured in command output)	Cloning status (captured in command output)	Applicability
Success	Cloning file successfully created	Source
Success	Cloning file compatibility passed	Target
Success	Target IOA is up and running with cloning config.	Target
Failure	Failed to create running-configuration	Source
Failure	Failed to extract release information	Source
Failure	Failed to extract platform information	Source
Failure	Release version info missing in header	Target
Failure	Platform info missing in header	Target
Failure	IOM — mode info missing in header	Target
Failure	Cloning header missing	Target
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 2. 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.

Welcome

Welcome to Dell

Dell PowerEdge FN I/O Module Configuration Guide 9.10(0.0)

Cloning Configuration Output Status

Rate this content