1. Zerto Virtual Manager user interface is not loading any elements. 

NSX switch ZVM dashboard not loading

  1. An NSX network is presented to the VMware architecture and the NSX network is presented as an Opaque Network.


  1. The following error can be found in the ZVM logs (logfile.csv, log.###.csv):

System.ArgumentException Zerto.Zvm.Common.VirtualizationManager.VCenter.NetworkIdentifier ExternalIdToInternalId(Vim25Api.ManagedObjectReference) System.ArgumentException: Type of externalId is OpaqueNetwork

  1. Paired ZVM may show a site disconnection alert despite the being no actual network or connectivity issues.

The Opaque Network object present in a VMware architecture breaks the Zerto data collection mechanism for VMware.  This mechanism is referred to as the reflection.  When this mechanism breaks the ZVM it is not able to gather data about the available resources, nor share this data with its peer sites.  The inability to synchronize the reflection can lead to a state where all ZVMs paired to the affected ZVM appear to be bouncing between a synchronizing and site disconnected state with the affected ZVM.

Currently, the Zerto Virtual Replication solution has no concept of what an Opaque Network is nor how to interpret its object data.  This causes reflection mechanism to fail with the following error:

W,<thread ID>,VCenterProxy,AddHostReflectionItem,"failed when constructing reflection for entity: <VMware Resource> (type: <VMware Resource type>, value: <Entity MoRef>)","System.ArgumentException Zerto.Zvm.Common.VirtualizationManager.VCenter.NetworkIdentifier ExternalIdToInternalId(Vim25Api.ManagedObjectReference) System.ArgumentException: Type of externalId is OpaqueNetwork

The sections of this error that are not in bold can change based on what is currently being queried from the vCenter server by the ZVM.


There are three ways to address this issue until the ZVR product is updated to be able to handle the Opaque Network type objects:

  1. Separate the environment into 2 network segments.  One network segment will contain the NSX-T switch, the other will be a traditional VMware network (referred to as NSX-V) that has no visibility to the NSX-T switch.
  2. Remove the NSX-T interface that is presented by vCenter as an Opaque Network from the virtual architecture.
  3. Upgrade to 6.5u2