A series of Auto Deploy ESXi hosts which utilize vDS are unable to boot in prior testing. All of the hosts were able to boot successfully.
Which two conditions might cause this issue? Choose two
A.
the hosts have experienced a network error
B.
the auto deploy server permissions are invalid
C.
vCenter server is down
D.
the hosts have experienced a local disk error
I have seen several posts on multiple sites with different answers for this question.
Who else here believes B & C are incorrect?
Let me explain why I believe A & C are correct.
A. the hosts have experienced a network error.
Anyone who has ever worked with AutoDeploy knows how critical the network infrastructure is. Everything from the DHCP server being online and configured correctly, the TFTP server being online and configured correctly to the switching/routing infrastructure needs to be spot on for an image to be pulled over the network. AutoDeploy has everything to do with the network!
B. the AutoDeploy server permissions are invalid
What permissions are we talking about here? You can search the whole AutoDeploy guide and you will see no reference to permission problems being related to troubleshooting (If you find something, please post!)
C. vCenter server is down
Absolutely this is correct. The ESXi hosts require vCenter online to retrieve the image.
D. the hosts have experienced a local disk error
A big advantage to AutoDeploy is not relying on local disks. This option is clearly incorrect.
0
0
Hi Matt,
The information below is one of Prerequisites before Install the Auto Deploy Server, so I think “B. the AutoDeploy server permissions are invalid” is more suitable than “A. the hosts have experienced a network error.”.
“Obtain administrative privileges to the DHCP server that manages the network segment you want to boot from. You can use a DHCP server already in your environment, or install a DHCP server.
Sample DHCP Configuration in vSphere Installation and Setup shows sample files for a regular scripted installation. For your Auto Deploy setup, replace the gpxelinux.0 file name with undionly.kpxe.vmw-hardwired.”
Ref: http://pubs.vmware.com/vsphere-50/topic/com.vmware.ICbase/PDF/vsphere-esxi-vcenter-server-50-auto-deploy-guide.pdf , page 20
0
0
The permissions required for the DHCP server (which isn’t the auto deploy server, or doesn’t HAVE to be) is a one time thing for configuration.
A&C are absolutely correct.. It doesn’t say ‘vcenter permissions’ it says ‘auto deploy server permissions’.. TFTP doesn’t use authentication, however the hosts need to communicate with vcenter. The question indicated that credentials and configuration were correct because they were ‘previously able to boot’. This indicates a temporary situational issue, not a configuration issue – again pointing towards network/vcenter issues.
0
0
I think Matt is right.
0
0
Auto Deploy Server runs under vCenter Server administrator credentials, it is asked during the setup. I don’t know if the setup can be completed if wrong credential is informed on this step… If somebody can do this validation in a lab will be very useful to make answer “B” a valid alternative or not (if setup validate the vCenter administrator credential before proceed, I believe that we can assume that Auto Deploy Server has valid permission to do their job, if not, answer “B” is a possibility).
0
0
I found AutoDeploy guide in the following link:
http://pubs.vmware.com/vsphere-50/index.jsp?topic=/com.vmware.vsphere.install.doc_50/GUID-A9FFEDEE-1A3D-4EFD-A130-F6E78C727380.html
……………………
Follow the tasks in the order presented in this document. Some steps can be performed in a different order, but the order used here limits repeated manipulation of some components.
Procedure
1/ Proof of Concept Preinstallation Checklist
Before you can start the proof of concept setup, make sure that your environment meets the hardware and software requirements and that you have the necessary permissions for the components included in the setup.
2/ Install the TFTP Server
Auto Deploy relies on a TFTP server for sending the boot image to the hosts it provisions. You must install a TFTP server in your environment.
…
0
0
has anyone been able to validate an answer?
0
0
Its A and C… no doubt about it. The key is in the question. TThe hosrs “were” able to boot. A permission didnt change without the admin knowing. Either the network went down or vCenter did.
0
0
Definitely A and C
0
0
I think A over B as well, due to the fact the hosts were able to boot previously. So, A and C.
0
0
Definitely it’s A&C.
Permissions must be set in advance to the Auto Deploy Server; once the profiles are stored in the ADS, and the initial config is finished, the esxi deploy & boot phase it has to do with DHCP, PXE ecc.: those processes are not in the domain of authentication. And again bad permissions are still bad unless corrected by admin, why the hosts were booting then?
0
0
admin
It would be easier to understand the question if you corrected the grammar. The question should be stated thus.
A series of Auto Deploy ESXi hosts which utilize vDS are unable to boot. In prior testing all of the hosts were able to boot successfully.
Why don’t you correct this fairly obvious error?
0
0