NSX-T segment using new transport zone fails to show as available for Org VDC network in VMware Cloud Director

Products

• VMware Cloud Director

Issue/Introduction

When attempting to import a new NSX-T segment into an Org VDC as a new network it fails to show. It may show if you attempt to add it as an external network at the provider VDC level. There are no error messages in the logs. The transport zone for the segment is new and not in use by other networks in VMware Cloud Director.

Environment

VMware Cloud Director 10.6.1

Cause

The configuration in NSX-T is incomplete.

Resolution

The configuration must be completed in NSX-T. The transport zone must be in use by ESXi hosts and edge cluster nodes. The steps using a transport node profile is here:
https://techdocs.broadcom.com/us/en/vmware-cis/nsx/vmware-nsx/4-2/installation-guide/transport-zones-and-transport-nodes/add-a-transport-node-profile.html

Some considerations:
- If it is a VLAN backed transport zone it should be added to a host switch. The click path is in NSX -> System -> Fabric -> Hosts -> Transport Node Profile -> select the Host Switch number next to the transport node profile that is currently applied to our target applied clusters. Add the new VLAN transport zone here.
- If it is a new overlay transport zone further architecture considerations must be made. Only one overlay transport zone is supported per host or cluster.