nsxapi.log:
hostd.log:
VMware NSX-T Data Center 3.x
VMware NSX
The problem arises due to traffic shaping policies applied to the vMotion VMkernel. When traffic shaping is enabled without proper configuration parameters (e.g., missing average or peak bandwidth), NSX-T transport node preparation is blocked or partially applied. This results in the inability to fully configure the transport node, preventing proper network setup and creation of essential VMkernel interfaces like vmk10
.
To address this, follow these steps to temporarily adjust the configuration and enable successful transport node preparation:
Remove the vMotion VMkernel Interface: Temporarily delete the vMotion VMkernel from the ESXi host configuration to avoid policy conflicts.
Update the Transport Node Profile:
Re-add the vMotion VMkernel: Once the transport node updates are successfully applied, reconfigure and add back the vMotion VMkernel.