Information Technology Reference
In-Depth Information
Figure 2.8
h is screen provides
information about
the Auto Deploy
server that is regis-
tered with vCenter
Server.
That's it for the Auto Deploy server itself; once it's been installed and is up and running,
there's very little additional work or coni guration required, except coni guring TFTP and
DHCP on your network to support vSphere Auto Deploy. The next section provides an overview
of the required coni gurations for TFTP and DHCP.
Configuring TFTP and DHCP for Auto Deploy
The exact procedures for coni guring TFTP and DHCP are going to vary based on the specii c
TFTP and DHCP servers you are using on your network. For example, coni guring the ISC DHCP
server to support vSphere Auto Deploy is dramatically different from coni guring the DHCP
Server service provided with Windows Server. As a matter of necessity, then, we can provide only
high-level information in the following section. Refer to your specii c vendor's documentation for
details on how the coni guration is carried out.
Confi guring TFTP
For TFTP, you only need to upload the appropriate TFTP boot i les to the TFTP directory. The
Download TFTP Boot Zip hyperlink shown in Figure 2.8 provides the necessary i les. Simply
download the Zip i le using that link, unzip the i le, and place the contents of the unzipped i le
in the TFTP directory on the TFTP server.
Confi guring DHCP
For DHCP, you need to specify two additional DHCP options:
Option 66, referred to as next-server or as Boot Server Host Name, must specify the IP
address of the TFTP server.
◆
◆
Option 67, called boot-filename or Booti le Name, should contain the value undionly
.kpxe.vmw-hardwired.
If you want to identify hosts by IP address in the deployment rules, then you'll need a way to
ensure that the host gets the IP address you expect. You can certainly use DHCP reservations to
accomplish this, if you like; just be sure that options 66 and 67 apply to the reservation as well.
Once you've coni gured TFTP and DHCP, you're ready to PXE boot your server, but you still
need to create the image proi le to deploy ESXi.
