VMware ESXi host disconnects and do not connect back to vCenter
- vCenter was not able to recognize this host due to incorrect certificate
- Regenerate the certificate on the host (VMware Link)
- Log in to SSH of the host
- Browse /etc/vmware/ssl and backup the existing certificate and remove it
- Run the command /sbin/generate-certificates to regenerate the certificate
- Restart the services using the command services.sh restart
- Verify that the certificates are regenerated
- Try to reconnect the host in vCenter and you will receive the below error:
- You will be prompted for credentials again
- If your cluster is using EVC mode, you will receive a new error (VMware KB 1012864):
- Now you may need to note down the folders used by VMs in the affected host and remove the host from vCenter inventory
- Try to add the host outside the cluster.
- As expected, you will need to reconnect to the old dvSwitch.
- Once done, move the host to the cluster.
- Move the VMs to their respective folders
Issue:
ESXi host
disconnects from vCenter. And if tried to reconnect, the activity fails at 89%
Error from vCenter :
A general system
error occurred: internal error
Processing data
from vCenter agent on ESXi01
Snippets from the vpxd logs from vCenter:
===============================================================
2016-03-29T12:28:37.644+05:30 error vpxd[14460]
[Originator@6876 sub=HttpConnectionPool-000001] [ConnectComplete] Connect
failed to <cs p:000000001099ab00, TCP:IP Address:443>; cnx: (null),
error: class Vmacore::Ssl::SSLVerifyException(SSL Exception: Verification
parameters:
--> PeerThumbprint: Thumbprint
--> ExpectedThumbprint:
--> ExpectedPeerName: IP/Hostname
--> The remote host certificate has these
problems:
-->
--> * The host certificate chain is incomplete.
-->
--> * Host name does not match the subject
name(s) in certificate.
-->
--> * unable to get local issuer certificate)
===================================================================
Troubleshooting:
Authenticity of the host's SSL certificate is not verified.
The host cannot be admitted to the cluster's current Enhanced vMotion Compatibility mode. Powered-on or suspended virtual machines on the host may be using CPU features hidden by that mode.
Comments
Post a Comment