vCSA 6.0 is out and boy, is it awesome!! Best thing about the new version : its scalability.
You can go upto almost 10,000 machines and manage them all using vCSA 6.0. If that isn’t awesome I don’t know what is ;)
When I initially deployed vCSA I ran into this error which said:
After scratching my head for a while on why I ended up facing this error I realized that I had not resolved the hostname/FQDN on my DNS.
I had carelessly entered the IP information for the hostname for the server without actually mapping them on the DNS Server. The error pretty much tells that directly. But, I wasn’t too sure of it at the time.
So, I went ahead and resolved the name and restarted the deployment on my host client and it worked perfectly fine. Though it says Installation failed, which you can see at the bottom of my error in the backend, the machine gets deployed, just fine. I did not go ahead and work with it to see what would go wrong if you ignore this error.
I would suggest not to proceed with the deployment if you face this error. Go back to your DNS and resolve the hostname. You’ll never know when ignoring this error might come back and haunt you!
Hope you guys are as excited as I am about the new version of vCSA.
Abhilash Basavarajaiah is a Global Technical Alliance Manager and an Ambassador for the Office of the CTO @ VMware.
He is a dynamic IT professional and an ambitious, highly-motivated individual with experience in pre-sales, business development, and
strategic alliances. He experienced in designing and architecting
hybrid cloud infrastructure with a focus on Software-Defined Datacenter.
He is passionate about technology and all things virtual and VMware has recognized him as a VMware vExpert and a vExpert Pro under the Evangelist path for his contribution to the virtualization and cloud computing communities through knowledge sharing and content creation.
Abhilash holds numerous technical certifications from VMware, EMC, Cisco, CNCF, Microsoft, and Rackspace