User guide

Appendix B: Auto-deployment process 290
Waiting for TFTP
This wait/retry state can occur if the TFTP server to be used by the deployment is offline or is not accessible
on the network, or if the TFTP configuration file cannot be downloaded from the TFTP server. Resolution
includes testing the TFTP server to ensure it is accessible by other TFTP clients on the management network,
and verifying the file referenced in the DHCP configuration to ensure it is correct for the TFTP server address
and the configuration file on the TFTP server. The retry interval for this state is 5 minutes.
Failed to configure domain
If the deployment process encounters an error when processing the domain configuration, the deployment
process enters a wait state of 10 minutes checking for a new configuration file on the TFTP server. If a new
file is found that is different from the one used in the last deployment attempt, it is reprocessed and a new
deployment cycle occurs. A failed configuration attempt might be caused by a syntax error in a script, a
command that is not valid for the target VC configuration, or an actual failure during the command
processing against the hardware. For more information on a failure, see the auto-deployment output file,
viewable in the GUI or with the VCMCLI command show auto-deployment output.
Triggering a restart of the deployment process
If an issue occurs that causes the deployment process to enter one of the retry/wait states and if the condition
is corrected, you must wait for the retry interval to cycle before the deployment process can be automatically
attempted again.
Configuring file restrictions
The auto-deployment process validates and allows a subset of VCMCLI commands in the script being
processed for configuration of the domain. Commands that would be disruptive to the auto-deployment
process are not allowed.
Only the following commands are allowed in the VCMCLI configuration script used in deployment:
• set
• add
• copy
• poweron
• poweroff
• assign
• unassign
• remove
If any other commands are used in the deployment script, they result in an error, and the current deployment
process is aborted, going into a "Failed to Configure Domain" wait/retry state. The same is true for VCMCLI
errors in general.