Error: "Mismatch" configuration state on Edge Transport Nodes - NSX
search cancel

Error: "Mismatch" configuration state on Edge Transport Nodes - NSX

book

Article ID: 415750

calendar_today

Updated On:

Products

VMware NSX VMware Telco Cloud Platform

Issue/Introduction

  • After upgrading NSX, Edge nodes display a "Mismatch" configuration state in the NSX Manager UI, accompanied by an alarm indicating CLI configuration and intent configuration hostname discrepancies:
    • Reason: CLI configuration: {"Host name":"NewName.net"},
    • intent configuration: {"Host name":"OldName.net"}

Environment

  • NSX 3.x, 4.x
  • TCP: 3, 4.x, 4.0.1, 5.x, 5.0. 5.0.1, 5.0.2

Cause

  • A discrepancy exists between the Edge node hostname configured in CLI and the intended configuration stored within NSX Manager, often caused by post-upgrade synchronization failures or hostname modification operations.

Resolution

  1. Perform a backup of the NSX Manager configuration and Edge Transport Node state before proceeding.
  2. Navigate to System > Fabric > Nodes > Edge Transport Nodes in the NSX Manager UI.
  3. Locate the Edge node showing a "Mismatch" status in the Configuration State column.
  4. Select the Mismatch link.
  5. In the resolution pop-up, choose vSphere/Edge Appliance as the source.
  6. Click Resolve to trigger the configuration synchronization.

For further assistance with NSX Edge configurations, visit Broadcom Support.