Appendix B: Auto-deployment process
Overview of the auto deployment process
•A configured DHCP configuration on the management network that supports the BOOTP configuration protocol
•A TFTP server on the management network that contains the CLI configuration scripts to be used for domain configuration
•Virtual Connect modules in enclosures to be configured that support
•A Virtual Connect user with domain user role permission to initiate the deployment process
These elements, as well as the process and configuration involved in the deployment process, are described in more detail in the following sections.
Following are the general steps of the typical deployment process:1.Import the local enclosure configuration.2.Start the
o If a DHCP/TFTP configuration is configured properly for deployment and available on the management network, a deployment process is initiated.
o If a DHCP server of TFTP server is not configured for deployment, a deployment does not occur immediately, and the deployment is in a "Waiting for DHCP" or "Waiting for TFTP" state until a proper DHCP/TFTP server exists on the network.
After the deployment process occurs, it completes successfully, or reports an error that explains why deployment was prevented from completing.
A deployment status and log is available for viewing from the CLI and GUI that shows details on the status and reports the error condition if one occurred during the deployment. The status and logs can be used for troubleshooting deployment failures, so they can be corrected and redeployment can be attempted.
DHCP server configuration
To support the VC
Appendix B: