SRM skips IP Customization of virtual machines

Products

• VMware Live Recovery

Issue/Introduction

Symptoms:

1. IP customization rules are skipped. 
2. Manual IP customization is also skipped.  

Cause

recovery.powerOnTimeout is set to 0. SRM does not set _ipSettings and _useIpMapper if the powerOnTimeout is 0.
 

Check user-configured powerOnTimeout. If it's set to 0, then according to the VmRecoverySettings VMODL we should not be waiting for tools, etc, which would mean the workflow would fail down the road. So, we just bail out early.
 

VMware-dr.log : 

2022-07-22T15:25:06.471-06:00 verbose vmware-dr[13463] [SRM@6876 sub=Recovery ctxID=b009fd5b opID=########-####-####-####-########3104-test:7e32:f152:69c2] [########-####-####-####-########0e3e.failoverOrchJob] Performing IP customization (if applicable) for VM RH7development4 [vm-6908]
2022-07-22T15:25:06.474-06:00 verbose vmware-dr[13154] [SRM@6876 sub=Recovery ctxID=b009fd5b opID=########-####-####-####-########3104-test:7e32:f152:69c2:a6aa] [########-####-####-####-########0e3e.ipCust-protected-vm-277486] Initializing IP customization for VM [vim.VirtualMachine:########-####-####-####-########ca78:vm-6908] with name RH7development4 [vm-6908]
2022-07-22T15:25:06.474-06:00 warning vmware-dr[13154] [SRM@6876 sub=Recovery ctxID=b009fd5b opID=########-####-####-####-########3104-test:7e32:f152:69c2:a6aa] [########-####-####-####-########0e3e.ipCust-protected-vm-277486] PowerOnTimeout is set to 0 for RH7development4 [vm-6908]
2022-07-22T15:25:06.474-06:00 verbose vmware-dr[13154] [SRM@6876 sub=Recovery ctxID=b009fd5b opID=########-####-####-####-########3104-test:7e32:f152:69c2:a6aa] [########-####-####-####-########0e3e.ipCust-protected-vm-277486] Starting prepare VM master job for RH7development4 [vm-6908]
2022-07-22T15:25:06.475-06:00 verbose vmware-dr[13154] [SRM@6876 sub=Recovery ctxID=b009fd5b opID=########-####-####-####-########3104-test:7e32:f152:69c2:a6aa] [########-####-####-####-########0e3e.ipCust-protected-vm-277486] VM RH7development4 [vm-6908] doesn't need guest operations 

We can check the powerOnTimeout value in /opt/vmware/srm/conf/vmware-dr.xml as shown below OR from the SRM UI under Advanced settings > Recovery Settings

  
<recovery>
    <autoDeployGuestAlias>true</autoDeployGuestAlias>
    <customizationShutdownTimeout>300</customizationShutdownTimeout>
    <customizationTimeout>600</customizationTimeout>
    <defaultPriority>3</defaultPriority>
    <forceRecovery>false</forceRecovery>
    <hostPowerOnTimeout>1200</hostPowerOnTimeout>
    <powerOffTimeout>300</powerOffTimeout>
    <powerOnDelay>0</powerOnDelay>
    <powerOnTimeout>0</powerOnTimeout>
    <skipGuestShutdown>false</skipGuestShutdown>
    <useIpMapperAutomatically>true</useIpMapperAutomatically>
  </recovery>

Resolution

Reset the value of recovery.powerOnTimeout to default at both the sites.
 

Restart srm-server service (Appliance) OR VMware vCenter Site Recovery Manager Server service (Windows)