Test Connection in VDP Appliance fails with the error: Unable to find this VDP in the vCenter inventory
search cancel

Test Connection in VDP Appliance fails with the error: Unable to find this VDP in the vCenter inventory

book

Article ID: 309504

calendar_today

Updated On:

Products

VMware vSphere ESXi

Issue/Introduction

Symptoms:
  • Attempting a Test Connection when configuring the vSphere Data Protection (VDP) Appliance fails.
  • When you attempt a Test Connection during VDP Appliance configuration, you see the error:

    Unable to find this VDP in the vCenter inventory

  • The hosts file in the /etc directory contains the IP address for the VDP Appliance but the hostname is blank.
  • The vami-ovf.log file (located at /opt/vmware/var/log/vami/) contains entries similar to:

    DD/MM/YYYY 14:53:38 [info] [process id: 4062] Hostname property is not present, querying and setting hostname.
    DD/MM/YYYY 14:53:39 [info] [process id: 4062] Output:Host name has been set to localhost.localdom


  • The vdr-configure.log file (located at /usr/local/avamar/var/vdr/server_logs/) contains entries similar to:

    YYYY-MM-DD 14:59:26,443 ERROR [http-nio-8543-exec-9]-config.VDRApplianceCurrentConfig: Unable to get the set host name and domain.
    java.net.UnknownHostException: localhost.localdom: localhost.localdom: Name or service not known
    at java.net.InetAddress.getLocalHost(Unknown Source)
    at com.emc.vdp2.config.VDRApplianceCurrentConfig.getNetworkDetails
    :q(VDRApplianceCurrentConfig.java: 153)
    at com.emc.vdp2.config.VDRApplianceCurrentConfig.init(VDRApplianceCurrentConfig.java:60)
    at com.emc.vdp2.config.VDRApplianceCurrentConfig.<init>(VDRApplianceCurrentConfig.java:47)
    at com.emc.vdp2.config.VDRWorkflowFactory.getConfig(VDRWorkflowFactory.java:247)
    at com.emc.vdp2.config.VDRWorkflowFactory.getConfiguration(VDRWorkflowFactory.java:53)
    at com.emc.vdp2.config.services.ConfigurationService.getConfiguration(ConfigurationService.java:110)


Environment

VMware vSphere Data Protection 5.1.x
VMware vSphere Data Protection 5.5.x

Cause

The issue occurs because Data Name Server (DNS) entries were not defined prior to deploying the OVF for the VDP Appliance. The DNS entries (forward and reverse) for the VDP appliance must exist prior to the deployment. During the deployment of the OVF, the /etc/hosts file is created. Since DNS lookup fails, the IP address of the VDP Appliance is entered, but the hostname remains blank. When you update the DNS entries for the VDP Appliance after the deployment, the /etc/hosts file is not updated and a Test Connection fails when it performs a lookup using that file.

Resolution

This is a known issue affecting all 5.x versions of vSphere Data Protection. Currently, there is no resolution.
To work around this issue, ensure that the DNS is configured correctly and redeploy the OVF template.
  1. Before you deploy VDP, add an entry to the DNS Server for the IP address of the VDP Appliance and Fully Qualified Domain Name (FQDN). Ensure there is a reverse lookup entry as well.

    Note
    : The DNS server must support both forward and reverse lookup. To check that DNS is configured correctly, see Preinstallation Configuration in the vSphere Data Protection 5.5 Administration Guide.

  2. Redeploy the OVF template in the VDP Appliance.

    In vSphere Client, perform these steps:
  1. Log in to the vSphere Client.
  2. Navigate to File > Deploy OVF Template.
  3. Browse to the location of the VDP Appliance downloaded .ova or the .ovf file and click Open.
  4. On the OVF Template Details page, click Next.
  5. On the Name and Location page, enter the name of your VDP Appliance and click Next.
  6. Select a datastore and click Next.
  7. Select a disk format and click Next.
  8. Click Finish.
In vSphere Web Client, perform these steps:
  1. Log in to the vSphere Web Client as Administrator.
  2. Click vCenter > Datacenters.
  3. On the Objects tab, click Actions > Deploy OVF Template.
  4. Allow and install the VMware Client Integration Plug-in, if prompted.
  5. Select the source where the VDP Appliance is located. By default the File name dialog is set to OVF
    Packages ( *.ovf).
  6. From the dropdown to the right of File name, select OVA Packages ( *.ova).
  7. Navigate to the location of the VDP Appliance .ova file. Confirm that you select the appropriate file for
    the datastore. Click Open and Next.
  8. Review the template details and click Next.
  9. Accept the EULA, then click Next.
  10. Enter the name for the VDP Appliance.

    Note: The name must match the entry configured on the DNS Server.

  11. Click on the folder or datacenter in which you want it deployed and click Next.

    Note: Do not change the VDP Appliance Name after installation.

  12. Select the host for the VDP Appliance and click Next.
  13. Select the virtual disk format and select the location of the storage for the VDP Appliance. Click Next.
  14. Select the Destination Network for the VDP Appliance and click Next.
  15. Specify the Default Gateway, DNS, Network 1 IP Address, and Network 1 Netmask.
    Confirm that the IP addresses are correct and match the entry in the DNS Server and click Next.

    Notes:
    • Setting incorrect IP addresses in this dialog box will require the .ova to be redeployed.
    • The VDP Appliance does not support DHCP. You must specify a static IP address.

  16. Review all deployment options and select Power on after deployment.
  17. Click Finish.


Additional Information

VDP アプライアンスでのテスト接続が次のエラーで失敗する: この VDP が vCenter インベントリで見つかりません
在 VDP Appliance 中执行测试连接失败,并出现以下错误: 在 vCenter 清单中找不到此 VDP