Error "NSX-T latency node group is not configured correctly" in VCF Operations for Networks

Products

• VCF Operations for Networks

Issue/Introduction

VCF Operations for Networks GUI under Accounts and Data Sources shows error: "NSX-T latency node group is not configured correctly" for the referenced NSX-T manager

• Collector logs show:

ERROR nsxt.tasks.NSXTLatencyStateWatcher NSXT_###.###.###.###_Config_OpMgr-5 watchTransportNodes:204 Transport node(s) [########-########-########-########, ########-########-########] not configured for end2end latency

 

NOTE:  VCF Operations for Networks was formerly named Aria Operations for Networks (AON), and prior to that was named vRealize Network Insight (vRNI).

Environment

Aria Operations for Networks 6.12.0
Aria Operations for Networks 6.12.1
Aria Operations for Networks 6.13.0
Aria Operations for Networks 6.14.0

Cause

Stale NSX-T Latency Node group entries in the collector database.

Resolution

This issue is resolved in Aria Operations for Networks 6.14.

If you are running 6.14, you may still see this error.  If you do, hover over the error alert and follow the instructions that are revealed, as below:

1. Under "Accounts and Data Sources", select the checkbox to the left of the referenced NSX Manager, and click the three vertical dots to the right of the line, and select Edit.
2. Scroll to "Additional Information" and un-check "Enable latency metric collection" and then click "Submit" at the bottom of the page.
3. Wait for a period of at least 5 minutes, and then repeat step 1, then repeat step 2 but check "Enable latency metric collection" and then click "Submit" at the bottom of the page.

If the error returns after a 25 hour period, please open a support case with the instructions at Creating and managing Broadcom support cases

If you are running a version prior to 6.14 and are unable to upgrade at this time, please open a support case indicating the release you are running.