VRNI Alert "NSX-T controller node has lost control cluster connectivity" with a critical severity

Products

• VCF Operations/Automation (formerly VMware Aria Suite)
• VMware NSX

Issue/Introduction

Symptoms:

• VRNI Alert "NSX-T controller node has lost control cluster connectivity" with a critical severity

• The VRNI Alert gets cleared automatically in the next status pull, this is approximately 2 minutes later.
• There is no impact on any NSX T functionality observed, a critical alert is seen on VRNI dashboard momentarily.
• The below entries are seen in the nsxapi log:

2021-02-04T13:40:04.547Z WARN messagingTaskExecutor-1 ClusteringStatusManager - - [nsx@6876 comp="nsx-manager" level="WARNING" subcomp="manager"] readClustersAggregateInfo Couldn't get a clustering status of CCP node with responseTime 1690

Environment

VMware NSX-T Data Center

Cause

The API used by VRNI to trigger this alert "/api/v1/cluster/nodes/node-id/status" creates a function call from MP to CCP.
The call timeout is 1 second and the issue is encountered when the call takes longer than 1 second.
In this case, the response generated for this function is "null", which results in an UNKNOWN response for the API call, though the alert in question here shows that the controller cluster is disconnected.
When the response is UNKNOWN, this means only that the status cannot be fetched due to the function call timeout.
This alert is safe to ignore and is automatically cleared out in the next pull from VRNI.

Resolution

There is currently no NSX fix required.
This will be resolved in a future release of VRNI.