This issue is resolved in VMware NSX for vSphere 6.3.5 and 6.4.0, available at Broadcom Downloads.
To work around this issue if you do not want to upgrade, apply a REST API call to add the Interface or sub interface.
Note: If you have NSX for vSphere 6.3.2, 6.3.3 or 6.3.4 deployed, you can first create the interface through the web User Interface (UI) and use the REST API to add the IP address.
- In order to add the Interface or sub interfaces, do a GET API call to retrieve the existing setting of the targeted interface, and then revise the returned XML body to add the Interface or sub-interface with IP address.This procedure is to maintain the existing configuration for the interface.
GET https://NSXMGR_IP/api/4.0/edges/edgeId/vnics/index
- Apply the REST API call.
For example:
POST https://NSXMGR_IP/api/4.0/edges/edge-8/vnics/?action=patch
<vnics>
<vnic>
<label>vNic_1</label>
<name>vnic1</name>
<addressGroups/>
<subInterfaces>
<subInterface>
<isConnected>true</isConnected>
<label>vNic_11</label>
<name>sub1</name>
<tunnelId>5</tunnelId>
<logicalSwitchId>virtualwire-1</logicalSwitchId>
<enableSendRedirects>false</enableSendRedirects>
<mtu>1500</mtu>
<addressGroups>
<addressGroup>
<primaryAddress>192.168.111.11</primaryAddress>
<subnetMask>255.255.255.0</subnetMask>
<subnetPrefixLength>24</subnetPrefixLength>
</addressGroup>
</addressGroups>
</subInterface>
</subInterfaces>
<mtu>1600</mtu>
<type>trunk</type>
<isConnected>true</isConnected>
<index>1</index>
<portgroupId>dvportgroup-111</portgroupId>
<portgroupName>test_portgroup</portgroupName>
<enableProxyArp>false</enableProxyArp>
<enableSendRedirects>false</enableSendRedirects>
</vnic>
</vnics>