vShield EndPoint: Lost communication with ESX module


We bought two new blades recently. When my colleague tries to configure the vShield Endpoint on the two new hosts, he always get an error ‘Lost communication with ESX module’.

I SSH into the host, and checked the syslog. It complains the certificate is not yet valid. And I noticed that the time is not correct on the hosts. The time has been set back to more than a year ago. Now it makes sense – if the certificate is issue this year, of course the host will complain the certificate is not yet valid. As 2013 means feature to them Smile

Correct the time settings does fix this issue.

image

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s