Transport Node Configuration Status - Mismatch - Display Name - Alarm for VMware NSX edge node not resolving

Products

• VMware NSX

Issue/Introduction

Symptoms:

• You are running VMware NSX 4.1.0.
• There is a Display Name - Mismatch alarm for the NSX-T edge node Configuration Status.

• The NSX-T edge node is auto deployed, that is it is deployed from the NSX-T UI and not via OVF in vCenter.
• The name of the edge node was altered in vCenter.
• When you attempt to resolve the alarm, by selecting the correct value from vSphere/Edge Appliance and Resolve, the alarm is not resolved and the name remains the same in NSX-T.

• Checking the open alarms on the edge node shows the following:

 

Environment

VMware NSX-T Data Center

Cause

The refresh API is unable to resolve the Display Name discrepancy between the NSX values and vSphere/Edge Appliance values.

Resolution

This is a known issue impacting NSX-T data center.

Workaround:
Select NSX as source, not vSphere/Edge Appliance, so the API will use the value for the edge node name which is stored in the NSX-T database.
This means the edge node name will change in vSphere to the name used in NSX-T and the alarm will be resolved.