Virtual Volumes(vVOLs) are inaccessible running on ESXi connected to vCenter Server after convergence of external Platform Services Controller server to embedded Platform Services Controller server
search cancel

Virtual Volumes(vVOLs) are inaccessible running on ESXi connected to vCenter Server after convergence of external Platform Services Controller server to embedded Platform Services Controller server

book

Article ID: 319608

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • This article provides information to resolve the certificate issue for VVOL connected to ESXi host after convergence of external Platform Services Controller server to embedded Platform Services Controller server.


Symptoms:
  • Virtual Volumes(vVOLs) are inaccessible running on ESXi connected to vcenter server after convergence of external Platform Services Controller server to embedded Platform Services Controller server.


Environment

VMware vCenter Server 6.7.x
VMware vCenter Server 6.5.x

Cause

  • Convergence tool change the VMCA certs, while the old certs are retained maintaining VC<-> host communication, other solutions like vVOl do not operate as the new certs provided to VASA providers have new certs whereas the hosts still have old ones causing vVol workflows to break.
     

Resolution

To workaround, the issue, Renew or Refresh ESXi Certificates connected to vCenter Server after converting a vCenter Server instance with an external Platform Services Controller to a vCenter Server instance with an embedded Platform Services Controller using convergence. Please follow the steps documented here .