Skip to main content
NetApp Knowledgebase

How to regenerate a VASA provider certificate in vCenter

Views:
513
Visibility:
Public
Votes:
0
Category:
netapp-hci
Specialty:
virt
Last Updated:

Applies to

  • NetApp Element Plug-In for VMware vCenter Server
  • VMware vCenter Server
  • VMware ESXi

Description

  • If issues are encountered with SSL certificates in vCenter, it's possible that users will be unable to manage VVOLs through the Element Plugin for vCenter (VCP) and will instead see SSL certificate errors.
  • Storage provider may show active in vCenter but ESXi hosts show “Not Connected”. The vvol datastores show “(inactive)”.

Example errors on the ESX host side (/var/log/vvold.log);

<DATE / TIME> warning vvold[2100222] [Originator@6876 sub=Default] VasaSession::GetEndPoint: failed to get endpoint, err=SSL Exception: Verification parameters:
--> PeerThumbprint: <thumbprint value>
--> ExpectedThumbprint:
--> ExpectedPeerName: <IP Address>
--> The remote host certificate has these problems:
-->
--> * unable to get local issuer certificate, using default
<DATE / TIME> info vvold[2100222] [Originator@6876 sub=Default] VasaSession::Initialize url is empty
<DATE / TIME> warning vvold[2100222] [Originator@6876 sub=Default] VasaSession::DoSetContext: Empty VP URL for VP (<hostname>)!
<DATE / TIME> info vvold[2100222] [Originator@6876 sub=Default] Initialize: Failed to establish connection

 

CUSTOMER EXCLUSIVE CONTENT

Registered NetApp customers get unlimited access to our dynamic Knowledge Base.

New authoritative content is published and updated each day by our team of experts.

Current Customer or Partner?

Sign In for unlimited access

New to NetApp?

Learn more about our award-winning Support