After ESXi upgrade NSX version to 4.0.1.1, vmotion vmk interface which connected to VDS could not bring up

Products

• VMware NSX

Issue/Introduction

After ESXi upgrade NSX version to 4.0.1.1, vmotion vmk interface which connected to VDS could not bring up.

Create new vmk interface and connect it to this VDS, will fail with following error:

WARNING: nsxt-ipfix: IpfixNSXSocketCreateOne: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Fail to create socket(domain 1): Unsupported address family
WARNING: nsxt-ipfix: IpfixNSXSocketInit: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Failed to initialize sockets: Unsupported address family
WARNING: nsxt-ipfix: IpfixNSXActivate: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Activation failed for 'DvsPortset-x': Unsupported address family
WARNING: nsxt-ipfix: IpfixNSXPortInsert: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Configuration failed for switch DvsPortset-x port 0xxxxx : Unsupported address family
WARNING: nsxt-ipfix: IpfixNSXPortPropSet: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Configuration failed for 'DvsPortset-x(0xxxxx)' : Unsupported address family
WARNING: nsxt-ipfix: IpfixDVPortParamWrite: [nsx@xxx comp="nsx-esx" subcomp="ipfix"]Failed to enable IPFIX on port 0xxxxx: Unsupported address family
WARNING: NetDVS: Failed to write critical property com.vmware.etherswitch.port.ipfix on port xxx, returen : Unsupported address family
WARNING: NetPort : failed to enable port, portID: 0xxxxx, status: Unsupported address family

Environment

NSX 4.0.1.1

Resolution

This issue is fixed in NSX 4.1.0

Workaround:

1. Customer is using vRNI (also known as Aria Operations for Networks) and configured vCenter server as data source. On vRNI, edit data source vCenter, uncheck "IPFIX" and save.
2. Recreate vMotion vmk interface.

Additional Information

If above workaround could not solve the problem, please refer to KB  https://knowledge.broadcom.com/external/article/345873/ for more solution.