Host Profile Compliance Check fails with error "vSwitch network policy property doesn't match"

Products

• VMware vCenter Server

Issue/Introduction

• After applying a Host Profile to an ESXi host, the host reports a status of Not Compliant.
• Compliance check fails with the specific error: vSwitch network policy property doesn't match.
• The following log pattern is observed in :
  /var/log/vmware/vpxd.log :
  [YYYY-MM-DD] info vpxd[05864] [Originator@6876 sub=moHostProfile opID=mm320m8o-1473-auto-14z-h5: 70000669-ac] [CheckCompliance] : Host #### is not compliant with profile xxxx: 
(vim.profile. ComplianceResult.ComplianceFailure) 
[
(vim.profile. ComplianceResult. ComplianceFailure) 
{
failureType = "VSwitch. NicDevicesNotMatching",
message = (vmodl. LocalizableMessage) 
}
key = "com. vmware. vim. profile. ComplianceFailure. VSwitch. NicDevicesNotMatching. label", arg = (vmodl. KeyAnyValue) 
]
(vmodl. KeyAnyValue) 
{
key = "vswitchName",
value = "vSwitch0"
message = "vSwitch vSwitch0 doesn't have the required NIC devices connected."
expressionName = "network. vswitch["key-vim-profile-host-VirtualSwitchProfile-vSwitch0"] . link-pnicsList",
failureValues = (vim.profile. ComplianceResult. ComplianceFailure. ComplianceFailureValues) 
(vim.profile. ComplianceResult. ComplianceFailure. ComplianceFailureValues) 
  
  

Environment

vSphere 7.x
vSphere 8.x

Cause

The physical adapter configuration (e.g., vmnic0) on the target host does not align with the Host Profile's defined network policy. Specifically, this error is triggered when an adapter is configured as an Unused adapter in the vSwitch settings on the host, while the Host Profile expects a different Teaming and Failover state (Active or Standby).

Resolution

To resolve this issue, ensure the vSwitch settings on the host match the reference host configuration within the Host Profile.

1. Log in to the vSphere Client.

2. Navigate to Hosts and Clusters.

3. Select the ESXi host reporting non-compliance.

4. Navigate to Configure > Networking > Virtual switches.

5. Select the affected vSwitch (e.g., vSwitch0) and click Edit.

6. Navigate to the Teaming and Failover tab.

7. Verify the status of the physical adapters (Uplinks). If an adapter like vmnic0 is under Unused adapters, move it to Active or Standby to match the desired configuration of the cluster/Host Profile.

8. Click OK.

9. Right-click the host and select Host Profiles > Check Host Profile Compliance to verify the fix.

 

Additional Information

If the configuration must remain as "Unused" for specific design reasons, the Host Profile must be updated by capturing the settings from a reference host that shares this specific configuration.