One of more transport node(s) realization failed while creating the transport node collection with profile <uuid> on compute collection <uuid>:domain-c## through NSX Manager <NSX manager IP>
Cause: InvalidRequest (com.vmware.vapi.std.errors.invalid_request) (statusCode:400) => { messages = [], data = => [error_message=2 Hosts in Transport node collection <uuid>-domain-c## are incompatible with ENS based HostSwitchMode config in transport node profile /infra/host-transport-node-profiles/<uuid>. sample incompatible Host and Pnic info: x.x.x.1=[vmnic1],x.x.x.2=[vmnic1]. Remove ENS incompatible hosts from the cluster or use STANDARD as HostSwitchMode in the TransportNodeProfile., httpsStatus=BAD_REQUEST, error_code=609679, module_name=policy}, errorType = INVALIDA_REQUEST }
esxcfg-nics -eName Driver ENS Capable ENS Driven INTR Capable INTR Enabled MAC Address Descriptionvmnic0 nenic False False False False ##:##:##:##:##:##Cisco Systems Inc Cisco VIC Ethernet NICvmnic1 nenic False False False False ##:##:##:##:##:##Cisco Systems Inc Cisco VIC Ethernet NIC
VCF 9
By default, VCF 9 will deploy transport node(s) using EDP (Enhanced Data Path), formally known as ENS (Enhanced Network Stack), if the host does not have physical nic(s) which support EDP, this error is displayed.
Please review the following guide for details on EDP Enhanced Data Path
In the above case, the host is using nenic drivers, these drivers do not support EDP, there is a Cisco driver called nenic_ens which does support EDP.
Ensure the physical nic(s) of the host are compatible with EDP, if not, use a Standard host switch for transport nodes.
To check if a nic supports EDP, check the compatibility guide COMPATIBILITY GUIDE
If in doubt, please consult with the nic vendor.
For Cisco UCS, first confirm Geneve offload configuration is enabled on nenic driver
Please review the following guide for details on tuning to enable EDP on the nic Tuning Guidelines for Cisco UCS Virtual Interface Cards (White Paper)