VMware NSX Compute Manager Lost Connectivity Alarm is Displayed after Compute Manager vCenter is Deleted

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

• VMware NSX Compute Manager lost connectivity alarm in open state even after the Compute Manager vCenter is deleted from NSX manager.
• Resolving the alarm via UI or API does not work; the alarm is triggered again from the alarm framework memory.

Environment

VMware NSX

 

Cause

The open alarm is not cleaned up while deleting Compute Manager. Hence, it is still in open state.

Resolution

Workaround:

1. Identify which NSX Manager node is actively reporting the alarm. This can be verified by querying the alarms API:
   GET https://<nsx_manager_ip>/api/v1/alarms?status=OPEN
   or
   Through UI: Expand the alarm and look for "Reported by Node"
   
   Note: The proton service only needs to be restarted on the manager node that is currently the "owner" or generator of this specific alarm.
   

2. Connect to the identified NSX Manager appliance via SSH as the root user.

3. Restart the proton service using one of the following commands:
   service proton restart
   or
   /etc/init.d/proton restart
   
   Note: Since the proton service provides management plane services, please refrain from making NSX configuration changes as a precaution during the restart. There is no impact on the data plane of already deployed services.

4. After the proton service has fully initialized, log back into the NSX UI and resolve the alarm one final time. The alarm should no longer regenerate afterward.