Data collection failed for NSX datasource with the error : "Data collection failed due to an error. Please wait for sometime" due to undetected vusb0 interface on NSX.
search cancel

Data collection failed for NSX datasource with the error : "Data collection failed due to an error. Please wait for sometime" due to undetected vusb0 interface on NSX.

book

Article ID: 414145

calendar_today

Updated On:

Products

VCF Operations for Networks

Issue/Introduction

  • NSX Manager data sources encounter the following error message during data collection:
    "Data collection failed due to an error. Please wait..."



  • The collector logs on the VCF operations for Network show following entries :

    2025-06-24T03:32:39.146Z ERROR dataprovider.utils.HttpUtils NSXT_TransportNode_nsxt.metric.exec.numThreads-2 checkCodeAndThrow:53 Could not get response for /api/v1/transport-nodes/12xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxc1/network/interfaces/vusb0/stats, status 404
    2025-06-24T03:32:39.147Z ERROR dataprovider.utils.HttpUtils NSXT_TransportNode_nsxt.metric.exec.numThreads-2 checkStatusAndThrow:41 API /api/v1/transport-nodes/12xxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxc1/network/interfaces/vusb0/stats error response {
      "httpStatus" : "NOT_FOUND",
      "error_code" : 600,
      "module_name" : "common-services",
      "error_message" : "The requested object : Provided interface id vusb0 in the request is invalid could not be found. Object identifiers are case sensitive."
    }

Environment

Aria Operations for Networks 6.x

VMware NSX 

Cause

Starting with vSphere 8.0, in both Integrated Dell Remote Access Controller (iDRAC) and HP Integrated Lights Out (ILO), when you have a USB interface enabled, vUSB or vNIC respectively, an additional standard switch vSwitchBMC with uplink vusb0 gets created on the ESXi host.

This vusb0 adapter is the one that is not detected by AON as the object identifier is case sensitive.

Please refer : ESXi creates standard switch vSwitchBMC with uplink vusb0 automatically after upgrading to 8.0.3 version

Resolution

Workaround :

  • Verify on the transport node, if the vusb0 adapter exists but is not in use. Move the vusb0 adapter to unclaimed section from the vSwitch. The error should resolve.
  • If the adapter is in use or if the alert shows up even after deletion of the adapter, please open a Support Request with Broadcom.

To remove the vusb0 adapter from the switch, follow the steps mentioned below.

1. Open the vSphere Client

2. Under Configure -> virtual switches -> vSwitchBMC -> Manage physical adapters

3. Move vusb0 to Unclaimed section