Knowledge Base

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

vSphere Data Protection connects to vCenter Server over port 443 even if vCenter Server is configured use a different port (2044826)

Symptoms

When vCenter Server is configured to use a different port because another application is using Port 443, you experience these symptoms:

  • vSphere Data Protection fails to connect to vCenter Server even after you set the correct port configured for vCenter Server in the vdp-configure screen
  • In the mcserver.log file, located at /usr/local/avamar/var/mc/server_log/, you see entries similar to:

    2013-01-18 07:38:18,422 INFO [com.emc.vdr.server.VDRServer$1]-service.AdapterUtils: MCS Web Services URL: https://univdpstr.unifund.com:9443/services/mcService MCUserId="MCUser" MCUserPswd="*****************************"
    2013-01-18 07:38:19,369 INFO [com.emc.vdr.server.VDRServer$1]-service.ServiceInstance: ServiceInstanceMoref desc=Service Id: urn:uuid:EAD7AD3A76FD9D418A1358512774542 name=urn:uuid:EAD7AD3A76FD9D418A1358512774542 value=SERVICE
    2013-01-18 07:38:19,550 ERROR [com.emc.vdr.server.VDRServer$1]-server.ConnectionService: Unable to get the vi access: VI SDK invoke exception:java.net.ConnectException: Connection refused


  • In the vdr-server.log file, located at /usr/local/avamar/var/vdr/server_logs/, you see entries similar to:

    2013-01-18 07:38:18,422 INFO [com.emc.vdr.server.VDRServer$1]-service.AdapterUtils: MCS Web Services URL: https://univdpstr.unifund.com:9443/services/mcService MCUserId="MCUser" MCUserPswd="*****************************"
    2013-01-18 07:38:19,369 INFO [com.emc.vdr.server.VDRServer$1]-service.ServiceInstance: ServiceInstanceMoref desc=Service Id: urn:uuid:EAD7AD3A76FD9D418A1358512774542 name=urn:uuid:EAD7AD3A76FD9D418A1358512774542 value=SERVICE
    2013-01-18 07:38:19,550 ERROR [com.emc.vdr.server.VDRServer$1]-server.ConnectionService: Unable to get the vi access: VI SDK invoke exception:java.net.ConnectException: Connection refused

Cause

This issue occurs because VDP, by default, connects to vCenter Server through Port 443. This is because of the configuration in the mcserver.xml file.

Resolution

To resolve this issue:

  1. Connect to the VDP appliance using SSH as root.
  2. Run this command:

    #su admin

  3. Change directory to /usr/local/avamar/var/mc/server_data/prefs using this command:

    #cd /usr/local/avamar/var/mc/server_data/prefs

  4. Take a backup of the mcserver.xml file using this command:

    #cp -p mcserver.xml mcserver.xml-bak

  5. Open the mcserver.xml file using a text editor. For more information, see Editing files on an ESX host using vi or nano (1020302).
  6. Locate this entry within the file:

    <entry key="sdk_port" value="9443" />

  7. Change this entry to:

    <entry key="sdk_port" value="9442" />

  8. Restart the management agents using these commands:

    #dpnctl stop mcs
    #dpnctl start mcs
    #dpnctl start sched

  9. Exit the Admin shell.
  10. Log in as the root user.
  11. Change directory to /usr/local/vdr/etc/ using this command:

    #cd /usr/local/vdr/etc/

  12. Open the vcenterinfo.cfg file using a text editor.
  13. Locate this entry within the file:

    vcenter-port=443


  14. Change this entry to:

    vcenter-port=442


  15. Reboot the VDP appliance.
  16. Connect the VDP appliance to vCenter Server.

Tags

port vcenter VDP 443 mcserver.xml

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

  • 1 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)
  • 1 Ratings
Actions
KB: