Table of ContentsView in Frames

Resolving VASA Provider registration issues

The VASA Provider for ONTAP menu might not be displayed in the Virtual Storage Console (VSC), VASA Provider, and Storage Replication Adapter (SRA) GUI even after enabling VASA Provider. This issue might occur due to the improper cleanup of legacy registered instances of VASA Provider. You must clean up legacy VASA Provider instances, register VSC with the vCenter Server instance again, and then enable VASA Provider.

Steps

  1. Access the managed access browser of your vCenter Server instance: https://<vCenter_ip>/mob.
  2. Click Content > Extension Manager > Unregister Extension.
  3. Unregister all of the com.netapp.* extensions by selecting the following extensions in the UnregisterExtension key dialog box:
    • com.netapp.nvpf
    • com.netapp.nvpf.webclient
    • com.netapp.vasa.vvol.webclient
  4. Launch PuTTY, and log in to the vCenter Server instance by using the root user credentials.
  5. Switch to the vsphere-client-serenity directory: cd /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity
  6. Stop the vSphere Web Clientservice:
    • For vCenter Server 5.x: service vsphere-client stop
    • For vCenter Server 6.x: service-control --stop vsphere-client
  7. Delete the directories that have the VSC UI extensions: rm -rf com.netapp.nvpf.webclient* com.netapp.vasa*
    Note: You must include the asterisk (*) at the end of the command.

    The command removes both the VSC extension and the VASA Provider extension.

  8. Restart the vSphere Web Client service:
    • For vCenter Server 5.x: service vsphere-client start
    • For vCenter Server 6.x: service-control --start vsphere-client

    The vSphere Web Client service takes several minutes to restart and initialize correctly.

After you finish

After the vSphere Web Client service has restarted, you should register VSC with the vCenter Server instance, and then register VASA Provider with VSC.