Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Deploying or upgrading a VMware vSphere Data Protection appliance configured with a custom HTTP port (2062947)

Symptoms

  • During configuration of the VMware vSphere Data Protection (VDP) 5.5.5 or later appliance, you see a licensing error:

    Failed to acquire VDP Advanced license keys

  • After you acknowledge the error, enter a valid VDP license and click Decode, you see another error:

    This is not a valid VDP Advanced license key

  • The vdr-server.log file (located in the directory /usr/local/avamar/var/vdr/server_logs/)contains entries similar to:

    ERROR [http-nio-8543-exec-2]-rest.LicenseService: Failed To Get All License Keys
    java.rmi.RemoteException: VI SDK invoke exception:java.io.IOException: Unable to tunnel through proxy. Proxy returns "HTTP/1.1 400 Bad
    Request"
    at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:212)
    at com.vmware.vim25.ws.WSClient.invoke(WSClient.java:136)
    at com.vmware.vim25.ws.VimStub.loginExtensionByCertificate(VimStub.java:1580)
    at com.vmware.vim25.mo.SessionManager.loginExtensionByCertificate(SessionManager.java:154)
    at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:126)
    at com.vmware.vim25.mo.ServiceInstance.(ServiceInstance.java:83)
    at com.emc.vdp2.common.vi.VIAccess.getServiceInstance(VIAccess.java:200)
    at com.emc.vdp2.common.extension.ExtensionManagerReconnectExecutor.getExtensionManager(ExtensionManagerReconnectExecutor.java:76)

    Note: Symptoms may vary dependent on whether you are upgrading to VDP 5.5.5 or later or deploying a new VDP 5.5.5 or later appliance.

Purpose

This article provides steps to configure VDP after the deployment or upgrade to a VDP 5.5.5 or later appliance when using a custom HTTP port (a port other than 80).

Cause

This issue occurs when there is a conflict with the default HTTP port for the VDP appliance. 

Resolution

To resolve this issue, modify the port value in the vdp-options.properties file.

Note: The resolution steps apply to VDP 5.5.5 only. There is no vdp-options.properties file in VDP 5.1.

To modify the port value:
  1. Open an SSH session to the VDP appliance and log in as the root user.
  2. Navigate to the directory /usr/local/vdr/etc/.
  3. Open the vdp-options.properties file using a text editor.
  4. Locate the entry:

    com.vmware.vdp.option.vcenter.http_port

    Note: This entry determines the HTTP port in use, the preconfigured value is 80.

  5. Change the value from the default (80) to the your configured HTTP port matching your vCenter Server configuration.
  6. Save and close the vdp-options.properties file.
  7. Log out of vSphere Web Client VDP plugin and/or VDP configuration UI sessions if they exist.
  8. Restart the web services by running these commands:

    emwebapp.sh --restart

Additional Information

 This applies to VDP 5.5.6 as well.

See Also

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 3 Ratings
Actions
KB: