"cluster-network-nsx-level-inventory-mismatch found" errror when attempting to add an "Unassigned" host to a cluster.

Products

• VMware SDDC Manager / VCF Installer

Issue/Introduction

• The below error is observed when attempting to add an "'Unassigned" host to a cluster:
  
Map host NICs to this cluster's vSphere Distributed Switch configuration.
cluster-network-nsx-level-inventory-mismatch-found.
  cluster network nsx level inventory mismatch found.

Environment

VCF 9.0

Cause

The "cluster-network-nsx-level-inventory-mismatch-found" error is due to a synchronization drift between the SDDC Manager Inventory (Intent) and the NSX Manager (Realized State).

Missing "Master Template" (TNP) SDDC Manager requires that the target cluster is managed by a Transport Node Profile (TNP) in NSX. If a cluster is set to "None" or "Standalone" in NSX Manager, SDDC Manager cannot calculate the configuration for the new host, resulting in the mismatch error.

Resolution

Verify & Re-Apply Transport Node Profile. Follow these steps to confirm if the profile association is broken:

Inspect NSX Manager Association

1. Log in to the NSX Manager UI.
2. Navigate to System > Fabric > Nodes.
3. Change the "Managed By" dropdown to your Cluster Name.
4. Critical Check: Look at the "Transport Node Profile" column.
5. Pass: Displays a profile name (e.g., nsx-default-transport-node-profile).
6. Fail: Displays "None" or is empty.

Remediation (If "None") If the profile is missing, you must re-attach it to restore the "Template" logic:

1. Select the Cluster checkbox.
2. Click Configure NSX.
3. Select the correct profile (created by VCF) from the dropdown.
4. Click Save.
5. Reference: Attach a Transport Node Profile to a Cluster

Final Synchronization Once the TNP is attached in NSX, retry the Add Host wizard in SDDC Manager. The validation logic should now detect the correct profile and allow the expansion to proceed.