Stale alarms are present for hosts that have NSX uninstalled.

Products

• VMware NSX

Issue/Introduction

• Stale alarms are present for hosts that have NSX uninstalled.
• These alarms are only visible using API GET /api/v1/alarms.
• The stale alarm will be present only if the TN's TransportNodeMsg's key entry does not end with UUID string.
• You see messages noting an invalid UUID string in /var/log/phonehome-coordinator/phonehome-coordinator.log

Environment

VMware NSX-T Data Center 3.x
VMware NSX 4.x

Cause

Stale alarms are present for ESXi hosts that have NSX uninstalled.

For example:

"The DFW vMotion for DFW filter <nic> on destination host <hostname> has failed and the port for the entity has been disconnected."

The above example is for a DFW vMotion alarm, but the stale alarm can be seen for other event types also.

NSX was uninstalled from host but the alarm is still present.

Resolution

This issue is resolved in:

• VMware NSX-T Data Center 3.2.4 and higher
• VMware NSX 4.1.2 and higher
• VMware NSX 4.2.0 and higher

 

You can download up to date product versions from Broadcom Downloads.

If you are having difficulty finding and downloading software, please review the Download Broadcom products and software KB.

Workaround:

• Clear alarm using following API,
• POST https://<nsx-manager>/api/v1/alarms/<alarm-id>?action=set_status&new_status=RESOLVED
• Alarm will not appear again if the host does not have NSX configured.

Additional Information

Impact/Risks:
The host does not have NSX installed, so the alarm is a stale entry.

VMware NSX REST API guide:

• GET /api/v1/alarms/{alarm-id}
• POST /api/v1/alarms/{alarm-id}?action=set_status