VMware Cloud Community
snochico1
Enthusiast
Enthusiast

Cannot resolve from recovery site a protected site Opaque Network by device backing info.

I am moving my NSX-V over to NSX-T.   I have two sites, Site-A with a DVS and Site B with NVDS. When I move my VMs from Site-A to Site-B, IP customization works without issue. I then re-protect my workload and move the VMs from Site-B to Site-A.  The VMs get connected to the DVS on the correct portgroup but the recovery site will not process the ip customization.  When I go through the DR.LOG I have an error "Cannot resolve from recovery site a protected site Opaque Network by device backing info."

I have opened a ticket with VMware. Hopefully someone else had the issue can point me at a resolution before I hear back from VMware.  

Site Recovery manager : Version 8.2.0, Build 14761905

vCenter Version : 6.7 U3F

ESXi version: VMware ESXi, 6.5.0, 15256549

NSX-T : 2.5.1

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03696] [SRM@6876 sub=LocalSite.LocalVcServer.PCM tid=task-43820.VirtualMachineReconfigure] Starting destruction of filter 'sessionId[5293b]520b7acf-802d-74dd-5aea-11bd89792110'

2020-04-28T15:36:29.584-04:00 info vmware-dr[03696] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6:f61d:3c12] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg] DeployPackageJob succeeded for VM: 6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] 6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932-deployPkg succeeded for Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Retrieving network cards from VM Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 verbose vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Retrieved network cards from VM Test250 [vm-2041]

2020-04-28T15:36:29.584-04:00 warning vmware-dr[03688] [SRM@6876 sub=Replication.VmRecoveryInterface ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Protected site resolved device info is not found for NIC with key '4000'. Attempt best effort guess of the original protected site Network MoRef by the device backing info object.

2020-04-28T15:36:29.584-04:00 warning vmware-dr[03688] [SRM@6876 sub=Replication.VmRecoveryInterface ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Cannot resolve from recovery site a protected site Opaque Network by device backing info.

2020-04-28T15:36:29.584-04:00 error vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6]  Protected Network for VirtualEthernetCard :00:50:56:A4:5C:E6 is NULL, skipping this device

2020-04-28T15:36:29.584-04:00 info vmware-dr[03688] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.ipCust-protected-vm-122932] Skipping IP mapping based customization for VM Test250 [vm-2041]

2020-04-28T15:36:29.599-04:00 info vmware-dr[03844] [SRM@6876 sub=HostDomain ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:c9f6] Task 'Task-8773' has completed, tasks in queue 'TaskQueue-8768': 0

2020-04-28T15:36:29.599-04:00 verbose vmware-dr[03844] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.failoverOrchJob] IP customization succeeded for VM Test250 [vm-2041]

2020-04-28T15:36:29.599-04:00 verbose vmware-dr[03696] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.failoverOrchJob] VM Test250 [vm-2041]powerOnTimeout: 300,powerOnDelay: 0

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=Recovery ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] [6227472c-7fc9-4a3d-943c-2e55fbcf9efe.masterPowerOn-protected-vm-122932] Initializing power on sequence for VM Test250 [vm-2041], powerOn: 1, # of pre/post callouts: 0/0, VM tools timeout (secs): 300, power on delay (secs): 0

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=PlaceholderVmManager ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Looking up the VM handler for '[dr.replication.ProtectedVm:0202eca5-a511-49e7-a185-d44bd62e352b:protected-vm-122932]' to get it's placeholder VM info.

2020-04-28T15:36:29.615-04:00 verbose vmware-dr[03612] [SRM@6876 sub=PlaceholderVmManager ctxID=da59654f opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Getting the PlaceholderVmInfo for placeholder VM '[vim.VirtualMachine:b36a38d5-940d-4e29-a584-e0a45def8825:vm-2041]' of '[dr.replication.ProtectedVm:0202eca5-a511-49e7-a185-d44bd62e352b:protected-vm-122932]'.

2020-04-28T15:36:29.615-04:00 info vmware-dr[03816] [SRM@6876 sub=HostDomain opID=c1531bb8-3a1c-4882-9e01-4778673bfd95-test:3825:51cb:1abc:b311] Starting task 'Task-8776', queue 'TaskQueue-8768' at: Dr::HostDomainImpl::EnqueueBootVmOrShutdownVmTask(3336)

0 Kudos
2 Replies
snochico1
Enthusiast
Enthusiast

The VMware Site Recovery Manager (SRM) team has told me this is a known but with an internal ticket.  I was instructed to open a ticket with the NSX team to get more details.  I have a opened a new ticket.

0 Kudos
ashilkrishnan
VMware Employee
VMware Employee

Hi

Thank you for updating this thread

Yes, it does seem like a known issue with NSX-T when working with SRM. There is already a problem report raised for this issue and it is being investigated

Please keep this thread posted if you receive any workaround/resolution from NSX team

0 Kudos