When adding an NSX-T Datasource and/or enabling latency metric collection for an existing one, the following error "Latency metric collector is already enabled for another collector. It can be enabled for single collector at a time." is observed.

Products

• VCF Operations for Networks

Issue/Introduction

Unable to enable "latency metric collection" for a NSX-T Manager datasource, due to the following error message seen from VCF Operations for Networks GUI as below:

As a result, you may not be able to add the NSX-T Manager Datasource with "latency metric collection" enabled (as seen below):

 

Environment

VCF Operations for Networks 6.13.0
VCF Operations for Networks 6.14.X

Cause

Error message seen is expected as NSXT Latency metric can be enabled for one collector as a given time as per design.

This issue occurs when on older collector node has been deleted/decommissioned without removing the Latency metric option from VCF Operations for Networks GUI.

Resolution

To fix this issue, delete the existing/old NSX_T latency entry using via Postman using NSX-T API commands as follows:

1.  Login credentials should be "Basic Authentication" on Postman, refer to screenshot below:

 

 

2. Verify the existing/old profile present:

 

3. Use "PUT" following contents using below API:

https://<NSX-T IP>/api/v1/global-configs/OperationCollectorGlobalConfig

4. In Body of the API add below using Postman:

{
    "collectors": [],
    "report_interval": 1,
    "resource_type": "OperationCollectorGlobalConfig",
    "_revision": 1
}

5. Refer to below screenshots form Postman:

• Change the API Request seen in 'Step 2' to a "PUT" Request and add the following to the body:

• Click 'Send' on the 'PUT' Request: 

6. Wait for 5 minutes and enable NSXT Latency checkbox in VCF Operations for Networks GUI and Click Submit.

 

7. No error should come this time and datasource gets sucesfully added for latency metric collection.

 

 

Additional Information

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