Edge VM shows Configuration State as “Mismatch” after upgrade due to hostname inconsistency

Products

• VMware NSX

Issue/Introduction

After upgrading NSX from 3.2x to 3.2.x or 4.x, two Edge nodes were observed to be in a “Mismatch” configuration state in the NSX Manager UI.

The following mismatch alarm was seen:

Reason: CLI configuration: {"Host name":"NewName.net"}, 
intent configuration: {"Host name":"OldName.net"}

Environment

Vmware NSX

Cause

A mismatch was detected between the Edge hostname configuration in the NSX intent and the CLI configuration of the Edge VM.

This typically occurs when the Edge VM hostname differs from the intended configuration name stored within NSX Manager whihc is often seen after a rename operation or upgrade activity.

Resolution

1. Verify the current CLI hostname on the Edge:

   get hostname

   Compare with the hostname reflected under System > Fabric > Nodes > Edge Transport Nodes in the NSX Manager UI.

2. If the hostname mismatch is confirmed, attempt to resolve it by reapplying the configuration:

   • SSH to the Edge node and rename the hostname (if required).

   • From NSX Manager UI, click Resolve under the Edge node’s configuration state.

3. If the issue persists, perform a reboot of the affected Edge node and click Resolve again from NSX Manager.

After reboot and manual “Resolve” action, the Edge configuration state changed to Success, and the mismatch alarm will be cleared.