ESX hosts won't prepare in vcloud director

[KettieKop]

Hi Guys

I have a weird problem, might be a simple fix but I am yet to find the solution I have added 2 new hosts to my vcenter cluster, and now I want to add the hosts to my VDC. Problem is whwn I right click the hosts to prepare all the options are grayed out.

To give you some background, these new hosts have been moved to a DR location but the whole layer 2 network has been spanned, not sure if I might be missing something on the networking side.

Now I have done some checking, I can move VM's to the hosts so the networking is there, I have tried rebooting the hosts, all the hosts are on the same build but still nothing I can't do anything with the hosts. I have also removed the hosts from the cluster and added them again but this also did not solve the problem.

Any help would be greatly appreciated

[Gortee]

Evening,

So a few thoughts.  They are already in vcenter and show up in vcloud director. 

- Confirm they can be put into maint mode.. and put them into it then try to deploy.

- If this does not work you may have to manually deploy the agent. 

-Make sure if your using VXLAN they have been added and prepared in vShield Manager as well

Here is a good checkup doc to review:

VMware vCloud Director Essentials: Provider vDC and more

Let me know if this solves the issue or if you need more help.

Thanks,

J

[KettieKop]

Thanks for the response

Both hosts can be put in maintenance mode, and all the hosts can reach each other, I have also tried to manually install the agent yesterday but still no luck. I can see the hosts in vcloud director but I just can't do anything with them, when I right click all I can choose is properties.

I have even tried re installing the host and still no luck. I am not using VXLAN though.

Will continue to troubleshoot and provide feedback, I am sure it is something silly

[mcfadyenj]

I had similar issues to this from memory it turned out to be an issue with our shared storage settings. As this was a home lab I was trying to cut corners on cost and was using ISCSI disk.

this in turn created an issue where the vmotion wasn't setup correctly which was stopping migration of machines which meant the agent couldnt install.

this was some time ago now I cannot remember the exact details.

[IamTHEvilONE]

i agree that most of the time I see this there are two probable causes:

1. hosts can't evacuate fully

2. storage for where the VIB gets installed is too slow/has issues

The general process is an NFC upload to the hypervisor, then run a command to install the VIB file.  It's not all that big either, so internal networks should ship it rather fast.

Most of the time is spent entering and exiting Maintenance Mode (most times when I see it with a customer).

[KettieKop]

Hi All

Well I said it was something simple, turned out the person that manages the vcloud environment (he has been on leave) Never updated vcloud director to 5.5 so when I installed the new hosts with 5.5 Vcloud director didn't have the agent for it thus not giving me any options. an error would be nice. Anyway problem solved.

what is funny though is if you install the host with 5.1 add it to the VDC and then upgrade to ESXI 5.5 it still works, but if you force install the agent while 5.5 is installed it doesn't seem to work.

Thanks for the help though feel like a moron.

[adiVmware]

Hi all ,

If you are getting issue during prapare host in vcloud you can follow few checks.

-Try to resolve vlcoud director ,so that you can check proper dns entry is there.

-Try to resolve Hosts which you are trying to prepare.

-login to Vcloud Director and check if it is in domain or not.

-Login to Vcloud and try to resolve Hosts .

Hope these steps will help to resolve few error ...