User guide

Appendix B: Auto-deployment process 278
Appendix B: Auto-deployment process
Overview of the auto deployment process
Auto-deployment enables administrators to set up a configuration on the local management network to allow
a form of pre-provisioning for Virtual Connect domain configurations. The deployment configuration
provides easy, automated initial setup of domain configurations for one or more enclosures available on the
network.
The key elements involved in the deployment process include the following:
• 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 auto-deployment
• 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.
Auto-deployment supports single-enclosure domains. Multi-enclosure domains are not supported.
2. Start the auto-deployment process using the CLI. The user initiating a deployment process must have VC
domain user role permission.
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 auto-deployment process, the DHCP server that is used for IP address assignment of the VC
modules must be configured to support BOOTP parameters, specifically Options 66 and 67 of the DHCP
protocol. Many DHCP servers provide the ability to customize these options. Configuration of the BOOTP
options depends on the DHCP server application being used, and varies by operating system. The following
section provides a sample configuration of a common Linux-based DHCP server to support deployment.