"Data Collection failed due to an error. Please wait for some time." for NSXT Datasource adding in GUI due to stale entry for Latency Node Group TN profile

Products

• VCF Operations for Networks

Issue/Introduction

• GUI shows error under account and datasource page for added NSXT Manager. Error seen is Data Collector failed due to an error. Please wait for some time.
  
  See screenshot below:
  

  

•  

  Collector support bundle logs at location /var/log/arkin/collector/ shows health as healthy but datasource Operations fails for Latency Node Group TN profile.

2025-11-20T17:03:39.238Z INFO impl.dataprovider.AbstractDPOperationsManager DataProviderManager::healthCheck getHealthStatus:514 DPHealthStatus: dpId {
  dataProviderIdentifier: "NSXT_###.###.#.##"
  customerId: 11417
}
healthReport {
  health: HEALTHY
       taskId='com.vnera.dataproviders.core.impl.vmware.nsxt.tasks.NSXTLatencyStateWatcher'
        collectedDataType=CONFIG
        taskExecType=SCHEDULED
        isSuccess=false
        timestamp=1763656715868
        errorCode='FAILED_DATASOURCE_OPERATION'
     errorMessage='com.vnera.dataproviders.core.common.impl.dataprovider.utils.exceptions.HttpException: Could not get response for /policy/api/v1/infra/domains/default/groups/vRNI-Node_Group_Profile_TN_####-6dac-###-9a89-###3a18###, status 400

Further in the collector logs we see below error/exception for latency profiles for Node Group

2025-11-20T16:08:29.507Z ERROR dataprovider.utils.HttpUtils NSXT_##.###.#.##_Config_OpMgr-3 checkCodeAndThrow:53 Could not get response for /policy/api/v1/infra/domains/default/groups/vRNI-Node_Group_Profile_TN_####-6dac-###-9a89-###3a18###, status 400
2025-11-20T16:08:29.507Z ERROR dataprovider.utils.HttpUtils NSXT_##.###.#.##_Config_OpMgr-3 checkStatusAndThrow:41 API /policy/api/v1/infra/domains/default/groups/vRNI-Node_Group_Profile_TN_####-6dac-###-9a89-###3a18### error response {
  "httpStatus" : "BAD_REQUEST",
  "error_code" : 500012,
  "module_name" : "Policy",
  "error_message" : "The path=[/infra/sites/default/enforcement-points/default/host-transport-nodes/#####-#####-####1-#####-d771acc5-###-497f-ae5d-6f68d#######host-####] is invalid"
}

 

Environment

• Aria Operations for Networks 6.13.0
• Aria Operations for Networks 6.14.0
• Aria Operations for Networks 6.14.1
• VCF Operations for Networks 9.0.x

Cause

This is a known issue which usually occurs when there is a discrepancy in  NSX-T Latency Node Group TN profile causing stale entry, which usually happens due to one of below or a combination of below activities:

• During movement or migrations of NSX datasources between collector VMs.
• The respective NSX datasource has been enabled and disabled using GUI toggle.
• Latency metric has been unchecked and check multiple times from the GUI.

Resolution

Issue is with NSX-T Latency Node Group TN profile stale entries which needs to be cleaned up using script(s) available with support team.

If you believe you have have encountered this issue then to investigate this further 

1. Open a support case with Broadcom Support mentioning this KB number to review your VCF Operations for Networks deployment. For more information, see Creating and managing Broadcom support cases. 
2. Generate support bundle for Aria Operations for Networks collector from GUI, see steps mentioned in KB