All Host TNs in a TNP applied Cluster show NSX Configuration state "Mismatch"

Products

• VMware NSX

Issue/Introduction

• All Hosts in a TNP applied Cluster show NSX Configuration state "Mismatch" even though status is "Up":

• When clicking on "Mismatch", following error seen: "Configuration Mismatch: Host has a configuration that does not match other hosts in this cluster"

• Following message seen when trying to clock on "Match Cluster Configuration":  "############# Profile will be applied to this host in order to match the cluster configuration. Would you like to proceed"

NOTE: Proceed with caution as clicking on "YES" above may cause data-path outage depending on the mismatch involved

• Reviewing the TNP configuration and Host configuration, one finds a Transport Zone missing in the TNP even though it is applied on all Hosts in the Cluster.

Environment

VMware NSX

Cause

This mismatch is caused by a difference in the Transport Node Profile (TNP) configuration and the actual configuration applied to the Host TN

Resolution

The following options are available to resolve the issue 

Option 1: Match the configuration on the Host TN to match the configuration on the TNP 

Option 2:  Reconfigure the TNP to match the configuration set on the Host TN

Additional Information

Related KBs:

ESXi host is reporting "Mismatch" error on the NSX UI -- Host that has a configuration that does not match other host in this cluster

Re-Configuring Transport Node Profile or Sub Transport Node Profiles assigned to cluster/sub-cluster to match configuration of the Transport Nodes that are in "Mismatch"

NSX Installation Fails on New ESXi Hosts: Configuration Mismatch Detected in Cluster