Error: Host is not conforming with the requirement of single vmknic for vMotion/management traffic type
search cancel

Error: Host is not conforming with the requirement of single vmknic for vMotion/management traffic type

book

Article ID: 407383

calendar_today

Updated On:

Products

VMware vSphere ESXi VMware Cloud Foundation

Issue/Introduction

Symptoms:

  • After running an invnetory sync, the following error message is displayed in the SDDC Manager UI:
    • Host is not conforming with the requirement of single vmknic for vMotion/management traffic type
    • Remediation: Verify the host has exactly one vmknic of vMotion/management traffic type

  • Hosts with multiple vMotion vmnics are not getting the same perfrormance or concurrence of vMotion in VCF 9.x as achieved in vSphere 8.x. In example, while hosts are on 8.0 U3, they can perform ~16 vMotions at once. But once upgraded to VCF 9.x only ~2 vMotions at once

Environment

VCF 9.x

Cause

This issue occurs due to one or more of the following conditions:

  • Multiple VMkernel adapters are assigned to the "management" traffic type.
  • A VMkernel adapter is sharing a port group with another traffic type.
  • The vMotion subnet is unisolated or incorrectly routed for the target hosts. While vSphere and VVF support Multi-NIC vMotion, VCF enforces a strict 1:1 mapping that limits concurrency, unless Load-based Teaming is used on a single vmk.
  • ESXi host SSL certificates are untrusted or invalid (e.g., following an upgrade or certificate expiration).
  • The SDDC service account status is "Disconnected" due to a hung management agent state (hostd/vpxa).
  • An IP conflict exists on the vMotion network for the affected hosts (e.g., IP ####.####.####.#### is already in use).

Resolution

  1. Ensure each VMkernel adapter is uniquely assigned to a specific traffic type and does not share a port group.
  2. Verify and isolate the vMotion subnet for the target hosts to satisfy SDDC Manager network validation rule sets.
  3. Regenerate and apply new SSL certificates directly on the ESXi hosts to restore cryptographic trust.
  4. Reboot the ESXi hosts to refresh management agents and restore the SDDC service account connectivity.
  5. Re-run the host commissioning workflow in SDDC Manager.