IP customization skipped without any error during test recovery
search cancel

IP customization skipped without any error during test recovery

book

Article ID: 390929

calendar_today

Updated On:

Products

VMware Live Recovery

Issue/Introduction

Symptoms : 

  • When VMs are configured with IP customization set to "Auto", the customization is skipped during test recovery without displaying any error message
  • Test recovery completes successfully. however, the IP customization feature does not get applied to certain virtual machines.

Validation Steps : 

  • After the test recovery completes, open the history for the latest test recovery and verify that IP customization for the specific virtual machine is marked as "Skipped
  •  Click on Recovery plan name --> Select History --> Open latest Test recovery --> Export report in new tab and make a note of IP customization status 

               
           

  • Open vmware-dr.log and check any issues with network mappings 
     
    Log path : less /var/log/vmware/vmware-dr.log

    2025-02-28T10:38:30.314Z verbose vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=###-b4a2-410b-####-###-test:b8c7:###:33aa] [#######-e0ba-###-bad1-####.ipCust-p
    rotected-vm-288927189] Identified guest running in VM ###########_DB_PROD [vm-165597]: oracleLinux8_64Guest (Linux); vmtools: '12389'
    2025-02-28T10:38:30.314Z info vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=###opID=####-b4a2-###-####-####-test:b8c7:b01d:33aa] [00f350b4-e0ba-####-bad1-#####.ipCust-prot
    ected-vm-288927189] Resolving IP Settings for ADYA_#####_DB_PROD [vm-165597]
    2025-02-28T10:38:30.316Z verbose vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=######opID=######-####-410b-#####-4cb8d6a01d38-test:b8c7######] [IpMapper.ADYA_####_###_RP] Found IP Mapping
     'VLAN_663 -> VLAN_663' at dvportgroup-4452 for vm-####:4000 (dr.IPMapping) {   >>>>>> Checking network mapping 
    -->    name = "VLAN_663 -> VLAN_663",
    -->    rules = (dr.IPMapping.SubnetRule) [
    -->       (dr.IPMapping.SubnetRule) {
    -->          Name = "VLAN_663 -> VLAN_663",      >>>>>>>>>>>>>>>>>>Identify which vLAN Shows issue 
    -->          remoteSubnet = "10.###.##.64/26",
    -->          localSubnet = "10.##.##.###/26",
    -->          remoteIPSettings = (vim.vm.customization.IPSettings) {
    -->             ip = (vim.vm.customization.FixedIp) {
    -->                ipAddress = "0.0.0.0"
    -->             },
    -->             subnetMask = <unset>,
    -->             gateway = (string) [
    -->                "10.##.##.65"
    -->             ],
    -->             ipV6Spec = (vim.vm.customization.IPSettings.IpV6AddressSpec) null,
    -->             dnsServerList = (string) [
    -->                "10.###.##.38",
    -->                "10.###.#.171",
    -->                "10.###.##.41"
    -->             ],
    :
    -->             ipV6Spec = (vim.vm.customization.IPSettings.IpV6AddressSpec) null,
    -->             dnsServerList = (string) [
    -->                "10.##.##.38",
    -->                "10.##.#.171",
    -->                "10.###.##.41"
    -->             ],
    -->             dnsDomain = <unset>,
    -->             primaryWINS = <unset>,
    -->             secondaryWINS = <unset>,
    -->             netBIOS = <unset>
    -->          },
    -->          dnsSuffixes = <unset>
    -->       }
    -->    ],
    -->    skipTestNetworks = <unset>          >>>>>>Skipping due to improper network settings 
    --> }
    2025-02-28T10:38:30.316Z verbose vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=992ee25f-b4a2-####-####-4cb8d6a01d38-test:b8c7:b01d:33aa] [NicInfoResolver.vm-165597.###] Didn't match 10.###.##.126/25   >>>>>>>>>>> Found it did not match 
    2025-02-28T10:38:30.316Z verbose vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=992ee25f-b4a2-###-####-4cb8d6a01d38-test:b8c7:####:33aa] [NicInfoResolver.vm-165597.4000] Matched 0/1/0 addresses
    2025-02-28T10:38:30.316Z info vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=992ee25f-b4a2-####-###-4cb8d6a01d38-test:b8c7:b01d:33aa] [IpMapper.######_DB_WEB_RP] No match for vm-165597:####
    2025-02-28T10:38:30.316Z verbose vmware-dr[01215] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=992ee25f-b4a2-####-####-#####-test:###:######:33aa] [00f350b4-###-4777-bad1-b5a4a6ffb247.ipCust-protected-vm-288927189] No IP Mapping found for ADYA###########[vm-165597]
    2025-02-28T10:38:30.319Z info vmware-dr[01581] [SRM@6876 sub=Recovery ctxID=88d0bdf8 opID=992ee25f-###-####-b329-4cb8d6a01d38-test:###:###:33aa:###] [00f350b4-####-4777-bad1-######.ipCust-protected-vm-288927189-GuestPowerOff] Powering off vm 

Environment

VMware Site Recovery Manager 8.x
VMware Site Recovery Manager 9.x

Windows and Linux VMs 

Cause

  • Due to subnet mask and CIDR range mismatch the IP customization is skipped .The address is not matched to the rule and IP customization skipped
  • When SRM is processing IP customization, it compares the IP address provided by VM Tools with predefined network rules.
    If the subnet mask or CIDR range in the Guest OS does not match the expected values in SRM, the IP customization will either fail or be skipped.
    SRM requires that the IP addresses and subnet masks align with the expected ranges for customization to apply successfully. This alignment issue results in SRM skipping the IP customization process or failing due to the mismatch.

Cause Validation 

  • Validate affected VM Network (Click on Affected VM -->Summary -->Make a note of network 

         

  • Site Recovery Page -- >Network mappings --> Select affected VM network --->Edit IP customization --> Make a note of IP address and Subnet mask and CIDR Range 

       

           

 

 

 

Resolution

  • Correct Subnet mask and IP ranges are provided for the VMS and Validate CIDR range for affected VM. 

             For Example, 

                 If subnet mask is 255.255.255.192>>>> Prefix should be 26 

  • Once the correct details are updated, IP customization gets applied successfully
  • Below snippet shows correct details after Changing IP details in Site recovery Network mappings 

         

 

 

Powered by Wolken Software