I recently noticed a question on the ESXi forum about trying to add a host to a vCenter server that had the "SSL host certificate verification" enabled while using the vSphere SDK for Perl Utility hostops.pl on vMA. The user encountered the following error when trying to add the host:
Fault string: Authenticity of the host's SSL certificate is not verified.
Fault detail: SSLVerifyFault
The SSL host verification is a feature that came with the release of vSphere that provides a security measure to verify the validity of a host before adding it to your VMware infrastructure. This feature is disabled by default, but when it is enabled, a user will need to accept a dialog box to confirm the SHA1 thumbprint of the host in question.
This particular use case was not handled properly by hostops.pl which caused the error message to be thrown. With a small tweak to VMware's canned script, the new and improved hostops-lamw.pl now supports adding an ESX or ESXi host into vCenter with SSL host verification enabled. You'll still be expected to verify the SHA1 thumbprint, but now you can pass this as an additional parameter which will tell vCenter that you have verified the host and add to vCenter management.
Scott Lowe originally wrote an article on how to verify the SHA1 thumbprint for both an ESX and ESXi host.
On ESX you can run the following:
openssl x509 -sha1 -in /etc/vmware/ssl/rui.crt -noout
On ESXi, the only real way to verify is by looking at the DCUI's "View Support Information":
However, if you truly trust the ESX or ESXi host that you're going to add to vCenter, there is an alternative way of retrieving the SHA1 thumbprint using the vCLI's vifs and the modified hostops-lamw.pl.
By default, you'll be able to point your web browser to https://[hostname]/host/ssl_cert to see actual SSL certificate on your host, assuming this functionality is not disabled. What you can do is download the ssl_cert to vMA or system with vCLI installed and query for the SHA1 hash and provide that as input to hostops-lamw.pl.
Step 1. Download hostops-lamw.pl to either vMA or system running vCLI copy it to the following path:
|vMA or Linux host||/usr/lib/vmware-cli/apps/host|
|Windows||C:\Program Files\VMware\VMware vSphere CLI\Perl\apps\host|
Step 2. Download the ssl_cert to vMA:
[[email protected] ~]$ vifs --server esxi4-1.primp-industries.com --username root --get "/host/ssl_cert" esxi4-1.primp-industries.com-ssl_cert
Downloaded file to esxi4-1.primp-industries.com-ssl_cert successfully.
Step 3. Get the SHA1 thumbprint from the ssl_cert you downloaded:
[[email protected] ~]$ openssl x509 -sha1 -in esxi4-1.primp-industries.com-ssl_cert -noout -fingerprint
Step 4. Use the modified hostops-lamw.pl and the new --sslthumbprint providing the SHA1 thumbprint (remember to double quote it) along with the other required input to add the host to vCenter:
[[email protected] ~]$ ./hostops-lamw.pl --server reflex.primp-industries.com --username primp --operation addhost --target_host esxi4-1.primp-industries.com --target_username root --target_password 'password' --sslthumbprint "79:BB:39:09:F6:E5:91:BD:B0:C3:F3:09:B4:38:50:FB:ED:9C:53:A5" --cluster virtual-cluster
Host 'esxi4-1.primp-industries.com' added successfully
Can the same changes be made to the add_standalone operation? It appears to only work with the addhost operation at the moment. That requires adding to a cluster.