IP Customization fails with "Unable to retrieve IP addresses from VMware Tools after XXX seconds

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

VMware Tools does not report NICs data to SRM. 
 VMware-dr.log :
YYYY-MM-DDTHH:MM:SS.SSS-06:00 info vmware-dr[03349] [SRM@6876 sub=Recovery ctxID=4dd402ee opID=##:#:#:#:#:#] [##.ipCust-protected-vm-##.waitForIpAddresses-vm-##] Waiting for Tools to report NICs data with set IP address from VM [vim.VirtualMachine:##:vm-##]; timeout: 450 seconds
YYYY-MM-DDTHH:MM:SS.SSS-06:00 error vmware-dr[06244] [SRM@6876 sub=Recovery ctxID=4dd402ee opID=##:#:#:#:#:#] [##.ipCust-protected-vm-##.waitForIpAddresses-vm-##] Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-##]; timeout (secs): 450
YYYY-MM-DDTHH:MM:SS.SSS-06:00 error vmware-dr[06244] [SRM@6876 sub=Recovery ctxID=4dd402ee opID=##:#:#:#:#:#] [##.ipCust-protected-vm-##] Cannot check VM '<VMNAME> [vm-####]' for applicable subnet mapping rules; Tools up and running but no IP addresses propagated:
--> (dr.recovery.fault.UnableToGetGuestIpAddresses) {
--> faultCause = (vmodl.MethodFault) null,
--> faultMessage = <unset>,
--> timeout = 450,
--> vm = 'vim.VirtualMachine:##:vm-####'
--> msg = ""
 

Checking VMs that are timing out.
 Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-####]; timeout (secs): 150
Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-####]; timeout (secs): 150
Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-####]; timeout (secs): 300
Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-####]; timeout (secs): 450
Timed out while waiting for NICs IP addresses from VM tools; [vim.VirtualMachine:##:vm-####]; timeout (secs): 600
 

Checking the Guest OS.
Identified guest family running in VM <VMNAME> [vm-####]: linuxGuest
Identified guest family running in VM <VMNAME> [vm-####]: linuxGuest
Identified guest family running in VM <VMNAME> [vm-####]: linuxGuest
Identified guest family running in VM <VMNAME> [vm-####]: linuxGuest
Identified guest family running in VM <VMNAME> [vm-####]: linuxGuest

 

Environment

Site Recovery Manager 8.x

Cause

SRM customization design depends on the ability to gather and change IP settings on VMs with disconnected NICs. To apply existing IP subnet mappings based customization SRM needs to get from VMTools the existing IP settings after the first VM boot. As this is happening with disconnected NICs, it turns out a lot of Linux systems can’t report IP settings for disconnected NICs. Hence, VMTools can’t report IP settings and SRM skip the customization for such VMs. 

Resolution

If the above symptoms and issue matches, please contact Broadcom Support to investigate the issue