Applying the transport node profile to the ESXi host failed with error ‘Bad parameter'

Products

• VMware NSX

Issue/Introduction

• Applying transport node profile to ESXi host is failed with below message in ESXi var/run/log/nsx-syslog.log
  
  ApplyHostSwitchCpuConfig to [xxx-xxx-xxx] failed : Failed to reconfigure dvs:
{'fault': 'PlatformConfigFault', 'msg': 'An error occurred during host configuration: ',
'faultMessage': ['Operation failed, diagnostics report: Unable to set the dvs extraConfig:
Status(bad0007) = Bad parameter']} ;

Environment

VMware NSX 4.X

Cause

The issue occurs when stale NSX properties remain in the ESXi host’s distributed switch configuration (e.g., kcp). These stale entries create a conflict during NSX re-preparation, preventing ESXi from installing the required properties and setting the correct switch type. As a result, the switch type defaults to the nulldev device, causing the operation to fail.

Resolution

To resolve the issue, remove the stale entries before re-preparing the host from NSX

1. SSH to the ESXi host. 
2. Confirm stale properties are present on the switch which is currently not being used by NSX
   
   # net-dvs -l | grep "common.alias\|kcp.enable\|vdsSecurity.enabled"
   
   
3. If the properties in the output are set to "true" (sample below), proceed to the next step:
   
   com.vmware.nsx.kcp.enable = true ,      propType = CONFIG


4. To disable these properties:
   
   # net-dvs -u com.vmware.nsx.kcp.enable -p hostPropList <dvsName>
   # net-dvs -u com.vmware.nsx.vdsSecurity.enabled -p hostPropList <dvsname>

   Note the <dvsName> is in output of command run in step 2.
   
   
5. Prepare host again for NSX.

To workaround the issue

1. Create a new VDS with the same set up as the existing VDS
2. Add the host to the new VDS.
3. Apply the transport node profile to ESXi host to prepare it for NSX.