Registering a VASA Provider Fails
search cancel

Registering a VASA Provider Fails

book

Article ID: 368313

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

  • When trying to register VASA Provider on vCenter, the following error appears:  "A problem was encountered while registering the provider.”

  • vCenter has been upgraded to 8.x from 5.x
  • /var/log/vmware/vmware-sps/sps.log shows the following error:

SNI = null
multiVcSupported = true
port = null
serviceHost = null
vcGuid = XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX

Environment

vCenter 8.x

Cause

 

The vcGuid will appear in capital letters which is the cause of the failure.

Resolution

Update vpxd-service-spec.prop and instance.cfg to use lowercase lettering for the vCenter guid. 

  1. Take snapshot of vCenter
  2. Open SSH connection to vCenter as root
  3. vi /etc/vmware-vpx/instance.cfg
    1. Change line instanceUuid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX to reflect instanceUuid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  4. vi /etc/vmware-vpx/firstboot/vpxd-service-spec.prop
    1. Change line cmreg.serviceid=XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX to reflect  cmreg.serviceid=xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
  5. Download lsdoctor https://knowledge.broadcom.com/external/article/320837/ and upload file into vCenter
  6. Run lsdoctor -r
    1. Selection option 3 when prompted
    2. Select the endpoint named "vcenterserver"
  7. Reboot vCenter and register vasa provider

Fix license tied to upper case vCenter

  1. Obtain vCenter LDU ID with command:

    /usr/lib/vmware-vmafd/bin/vmafd-cli get-ldu --server-name localhost

  2. Remove uppercase license with command: (Adjust dc=vsphere,dc=local to reflect deployment domain name)

    /opt/likewise/bin/ldapdelete -H ldap://localhost -D "cn=administrator,cn=users,dc=vsphere,dc=local" -w "password" "cn=AssetEntity_XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX-LDU-ID,cn=LicenseService,cn=Services,dc=vsphere,dc=local"

    Note: Adjust dc=vsphere,dc=local to reflect the environment's SSO domain.

Reboot vCenter and re-assign license.