In VMware Aria Operations for Networks (vRNI), network flows for a specific vCenter Server (VC) register as zero, showing no active traffic or flow data in the dashboard.
The vCenter Server is simultaneously registered as a data source in two separate, independent instances of vRNI.
vRNI architecture requires a strict 1:1 relationship between a vCenter Server and a vRNI instance. Registering a single vCenter to multiple vRNI instances is an unsupported configuration that disrupts flow collection and leads to unexpected behaviors, including flows dropping to zero.
Log into the original/incorrect vRNI instance, navigate to your data sources, and delete/remove the affected vCenter Server.
Log into the intended vRNI instance and remove the vCenter Server data source to clear any corrupted state.
Add the vCenter Server back as a data source in the intended vRNI instance.
Verify flow collection. Monitor the data source status in the intended vRNI instance to confirm that the flow count updates to a non-zero value and active traffic is observed. Please allow 15-30 minutes for a new polling cycle to occur.