7.0

Table Of Contents
Cause
The TFTP server is down or unreachable.
Solution
n Ensure that your TFTP service is running and reachable by the host that you are trying to boot.
n To view the diagnostic logs for details on the present error, see your TFTP service
documentation.
vSphere Auto Deploy Host Boots with Wrong Configuration
A host is booting with a different ESXi image, host profile, or folder location than the one specified
in the rules.
Problem
A host is booting with a different ESXi image profile or configuration than the image profile or
configuration that the rules specify. For example, you change the rules to assign a different image
profile, but the host still uses the old image profile.
Cause
After the host has been added to a vCenter Server system, the boot configuration is determined
by the vCenter Server system. The vCenter Server system associates an image profile, host profile,
or folder location with the host.
Solution
u Use the Test-DeployRuleSetCompliance and Repair-DeployRuleSetCompliance
vSphere PowerCLI cmdlets to reevalute the rules and to associate the correct image profile,
host profile, or folder location with the host.
Host Is Not Redirected to vSphere Auto Deploy Server
During boot, a host that you want to provision with vSphere Auto Deploy loads iPXE. The host is
not redirected to the vSphere Auto Deploy server.
Problem
During boot, a host that you want to provision with vSphere Auto Deploy loads iPXE. The host is
not redirected to the vSphere Auto Deploy server.
Cause
The tramp file that is included in the TFTP ZIP file has the wrong IP address for the vSphere Auto
Deploy server.
Solution
u Correct the IP address of the vSphere Auto Deploy server in the tramp file, as explained in the
vSphere Installation and Setup
documentation.
VMware ESXi Installation and Setup
VMware, Inc. 206