To look for applicable IP subnet mapping rule, SRM needs to retrieve from target guest OS its original IP configuration. Once the storage is failovered and target virtual machine ready to be powered on.
For this purpose:
SRM IP customization to be skipped on VMs with the affected Linux distributions as SRM cannot receive any IP addresses on step #2.
When the vNIC is disconnected, VMware Tools is not able to read IP settings in order to provide it to VC and then to SRM. On such VMs executing 'ifconfig' or 'ip addr show' doesn't report any IP settings when powered on with a disconnected NIC. Once the NIC is connected the IP settings are available again from both VMware Tools and running 'ifconfig'/'ip addr show'.
Except with examining 'ifconfig'/'ip addr show' output after powering on with disconnected NICs, you can recognize this problem in SRM server logs:
2019-02-27T10:52:18.408+02:00 trivia vmware-dr[02960] [SRM@6876 sub=Recovery ctxID=50b6730f opID=########-####-####-####-##########52-test:4fa1:be3b:3aaa:7fcd] [NicInfoResolver.vm-41.4000] Guest NIC info: (vim.vm.GuestInfo.NicInfo) {
--> network = "srmpg-########-####-####-####-##########46",
--> ipAddress = <unset>,
--> macAddress = "00:50:##:##:##:30",
--> connected = false,
--> deviceConfigId = 4000,
--> dnsConfig = (vim.net.DnsConfigInfo) null,
--> ipConfig = (vim.net.IpConfigInfo) {
--> ipAddress = <unset>,
--> dhcp = (vim.net.DhcpConfigInfo) null,
--> autoConfigurationEnabled = <unset>
--> },
--> netBIOSConfig = (vim.net.NetBIOSConfigInfo) null
--> }
SRM retrieves 'ipAddress = <unset>' for a target VM's NICs.