Skip to main content
NetApp Knowledge Base

How to regenerate a VASA provider certificate in vCenter

Last Updated:

Applies to

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


  • 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


Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.