Occasionally, installation of the VMware Data Services Manager plugin might fail due to misconfigurations, such as incorrect DNS settings or incorrect vCenter Server credentials. If any of such misconfigurations occur, DSM alerts you, so that you can troubleshoot your installation.

If you see any problems with your installation, you can log in to the DSM console as a root user to check for potential misconfigurations.

Prerequisites

Deploy your VMware Data Services Manager plugin Deploying the VMware Data Services Manager Plugin in vSphere Client.

Procedure

  1. Log in to the DSM console as a root user.
  2. Select Global Alerts, and check the following installation alerts.
    You can remediate several of them.
    Alerts Actions
    Invalid DNS configuration Check if the DNS name of vCenter Server host or DNS servers are indicated correctly.

    Select Settings > System Settings, and click Edit under Target vCenter.

    If needed, correct the DNS server or vCenter Server host.
    Invalid vCenter thumbprint

    Verify if the SHA256 thumbprint of vCenter Server is correct.

    Select Settings > System Settings, and click Edit under Target vCenter.

    Upgrade the thumbprint in the VC Thumbprint field.
    Invalid vCenter administrator credentials Check the username and password of the DSM administrator.

    Select Settings > System Settings, and click Edit under Target vCenter.

    Verify that the credentials are correct.
    Insufficient privileges Make sure that the DSM administrator has sufficient privileges.

    Select Settings > System Settings, and click Edit under Target vCenter.

    Verify that the user indicated in the VC Admin Username field is the correct user with required privileges. For information about minimum required privileges, see Creating a User with Limited Permissions for VMware Data Services Manager.
    vCenter plugin is not registered Generate a log bundle and contact VMware/Broadcom support at https://www.broadcom.com/support.

    To generate a log bundle, see Collecting System Logs and KB 376062.