ldelloca wrote:
I've seen it happening at times with version 8, both because of broken downloads, and also differences in the binary files when downloaded from different service pack levels.
Another quick and dirty solution, if the number of ESXi hosts is not that much, is to directly install the vib files into the hosts… I know it's not a good solution, but has saved me some hours of work once to try and find out why the import or the deploy stage was not working as expected. To be honest, both those errors were happening on the v8, in v9 I never had problems while preparing ESXi servers….
Luca.
In my experience: If the import fails it's most likely a corrupt file, or some strange condition that causes it (full database, no disk space).
If the deployment fails it is most likely DNS or firewall issues. Deep Security is highly depending of DNS and FQDN. A full disk on the host might also be an issue.
Normally you can find what causes the deployment issues by checking /var/log/esxupdate.log on the ESXi server.
When you deploy the filter driver you will find this in your log:
2013-06-10T08:50:15Z esxupdate: downloader: DEBUG: Downloading from https://<DSM-Server>:4119/vib/FilterDriver-ESX_5.0-9.0.0-995.x86_64.zip...
Any errors, either connecting to DSM, doing DNS requests or full disk will be located here. It is not that easy to figure out the problem only by checking the DSM log-files....
It is possible to install the VIB directly into the hosts, however I would not recommend it.