Knowledge Base

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

IP customization and command file in vCenter Site Recovery Manager 5.x fails with errors (2035981)

Details

  • While performing a recovery in vCenter Site Recovery Manager (SRM), the Guest IP Customization fails.
  • In the vmware-dr-xx.log file, you see an error similar to:

    Internal error: std::exception 'class Vmacore::Exception' "FIXME: Unwrapped VixError: 'There was an error in communication' Error Code: '14010'".
    [vim.VirtualMachine:vm-169]
    2012-09-08T10:24:47.740+09:00 [04584 error 'Recovery' ctxID=24622ffd] [recovery-plan-16269.ipCust-protected-vm-16093] IP Customization failed for VM Test-SERVER1 [vm-169]: (dr.recovery.fault.VixGenericFault) {
    --> dynamicType = <unset>,
    --> faultCause = (vmodl.MethodFault) null,
    --> errorCode = 14010,
    --> message = "There was an error in communication",
    --> msg = "",
    --> }

  • In the vmware-vix-SYSTEM-xxxx.log file, you see an error similar to:

    2012-09-08T10:24:50.065+09:00| vthread-6| I120: Vix: [6772 foundryVMPowerOps.c:6113]: Error VIX_E_HOST_TCP_SOCKET_ERROR in 
    FoundryVMOpenSocketToVMXThroughAuthd(): unable to contact authd: 'Host address lookup for server ESX-Test1 failed: The requested name is valid, but no data of the requested type was found'

Solution

SRM communicates with ESXi/ESX hosts through the vCenter Server. This means that SRM does not need to know the IP addresses of the ESXi/ESX hosts for most operation. However, some operations require direct connection with the ESXi/ESX host. If an ESXi/ESX host is accessed by its hostname, it must be resolved to its IP address on both the vCenter Server and the Site Recovery Manager Server. All ESXi/ESX Servers must be accessible by their DNS hostnames from the SRM Server.

To resolve this issue, you must add entries in the /etc/hosts file on both the Protected and Recovery sites of the Site Recovery Manager Server in this format:

IP_Address  Hostname

For example, a /etc/hosts file on an SRM Server might look like:

100.118.12.26 VMMVCS   # vCenter
100.118.12.27 VMMSRM   # SRM
100.118.12.14 VMMESX1  # ESXi server1
100.118.12.15 VMMESX2  # ESXi server2
100.118.12.16 VMMESX3  # ESXi server3
100.118.12.17 VMMESX4  # ESXi server4
100.118.12.18 VMMESX5  # ESXi server5

Note: Text after the # is a comment and is ignored.

For more information on editing text files, see Editing files on an ESX host using vi or nano (1020302).


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

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