Unable to see some External Networks under Provider VDC in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

• System Administrator user cannot locate few Extenal networks under Provider VDC in VMWare Cloud Director (VCD).
• The issue is intermittent and can be seen across few Provider VDCs.
• You won't be able to perform migration of Virtual Machines (VMs) across few Organization VDCs because the network does not appear, as it is absent from the Provider VDC. 

Environment

VMware Cloud Director 10.5.1.1

Cause

The issue is caused because there are missing entries in cloud director database table to reflect mapping of external network to the portgroups on remaining resource pool.

When an external network is created in VCD it has a backing of a segment created in NSX-T manager. This segment has links to multiple transport nodes of a transport zone. So, the segment, which was created in NSX-T internally created portgroups on all the cluster resource pools present in VMware vCenter. 
However as per VCD database, there are only mappings present between the network and dv-portgroup which is causing the network interruption in the Provider VDC and Organization VDC. 

Resolution

As a workaround you can need to edit and save the network to make it appear under the Provider VDC.

• Identify the external network where issue is present
• Edit the description (or any other edit you wish to do)
• Save the external network (It should update the real network backings in the database).
• Check if the external network is now visible under provider vdc. 

If the above workaround does not resolve the issue, contact Broadcom Support and note this Article ID (383907) in the problem description. For more information, see Creating and managing Broadcom support cases