License count exceeded in VCF Operations for Networks due to stale data from deleted vCenter

Products

• VCF Operations for Networks

Issue/Introduction

Administrators observe a "License count exceeded" alert in VCF Operations for Networks.

The License and Usage dashboard reports a total core usage count that significantly exceeds the known active environment (e.g., reporting 428 cores against an entitlement of 272).

Upon investigation in Settings > Data Sources, a vCenter data source that was previously deleted (potentially months prior) is still contributing to the aggregated core usage count.

 

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

Environment

VCF Operations for Networks

Cause

This issue is caused by stale records in the backend database (RDB).

When the vCenter data source was deleted, the associated records were not successfully purged from the database.

The licensing logic continues to aggregate core counts from these orphaned records, resulting in an artificially inflated usage count.

Resolution

The resolution requires manual intervention to purge the stale records from the backend database using internal engineering tools.

1. Validate the Issue:

   • Navigate to Settings > Data Sources.

   • Confirm that the sum of cores from active data sources is less than the total reported in the License dashboard.

   • Verify if a deleted data source is still listed or if the math implies a missing (deleted) source is being counted.

2. Open a Support Request:

   • Open a support request with Broadcom Support.

   • Reference this Knowledge Base article.

   • State that a backend database cleanup is required for a deleted data source to reconcile license usage.

3. Post-Resolution Verification:

   • Once Broadcom Support has executed the cleanup, allow a wait time of 1–2 hours.

   • Refresh the License and Usage dashboard to confirm the core count now reflects only the active environment.

Additional Information

Attempting to remove the data source again via the UI will likely fail or have no effect if the entry is already in a stale/hidden state.

The cleanup must be performed at the database level.