We have a lab based on VMware NFV 3.0 release:
We are installing NSX-T Datacenter 2.3 in the lab environment.
Other components we use:
We create one logical switch on NSX-T Manager, import it to vCD as organization network and connect the network on virtual machines deployed from OVF. In the vSphere page we see that the NSX-T logical switch is connected to VMs NIC as expected. Ovf environment file is passed in the VM as CD-ROM.
When ovf-env file is opened the <ve:EthernetAdapterSection></ve:EthernetAdapterSection> section is empty. Normally when we deploy VMs connected to organization networks backed from vSphere networks we see there the mac address and portgroup names, but it looks that same behavior is not applicable with NSX-T networks. Other OVF properties injected in OVF env file as OVF properties are passed fine.
<Environment xmlns="http://schemas.dmtf.org/ovf/environment/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:oe="http://schemas.dmtf.org/ovf/environment/1" xmlns:ve="http://www.vmware.com/schema/ovfenv" oe:id="" ve:vCenterId="vm-21897">
<Property oe:key="xxx" oe:value=""/>
<Property oe:key="xx" oe:value="xx"/>
Does anyone else observed this behavior with NSX-T? Unfortunately nothing is mentioned in NSX-T documentation or other VMware documentation. Could someone using NSX-T share the ovf-env file?