In VMware Aria Operations, duplicate vCenter Server objects associated with an Azure VMware Solution (AVS) SDDC appear in the Overview

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

• Two distinct vCenter Server objects for the same AVS SDDC appear in the Home > Dashboard view.
• Duplicate alerts or metrics for the same resources are seen.

Environment

VMware Aria Operations 8.18.5
Azure VMware Solution (AVS)

Cause

The AVS vCenter is being monitored by two distinct integrations simultaneously, the native Azure VMware Solution integration (which automatically discovers and monitors the SDDC vCenter) and a manually configured vCenter (vSphere Adapter) instance targeting the same IP/FQDN. Aria Operations treats these as separate data sources, leading to duplicate objects and collection.

Resolution

To resolve this issue, remove the redundant manually configured vSphere Adapter instance. 

WARNING: Deleting an adapter instance permanently deletes all historical data (metrics, alerts, and reports) collected by that specific instance. Create a snapshot of the Aria Operations cluster before proceeding. Ensure the deletion of only the manual vSphere Adapter instance, not the AVS Integration instance.

1. Log in to the VMware Aria Operations 8.18.5 user interface.
2. Navigate to Administration > Integrations.
3. Expand the "vCenter (vSphere Adapter) integration type" to view the list of configured instances.
4. Identify the manually configured adapter instance corresponding to the AVS vCenter IP or FQDN.
5. Note: Do not select the instance listed under the "Azure VMware Solution" integration type.
6. Select the manual instance (click the vertical ellipsis or the selection checkbox).
7. Select Delete.
8. Confirm the deletion in the dialog prompt.
9. Verify the duplicate object disappears from the inventory after the next collection cycle (approximately 5-10 minutes).

 

Additional Information

The Azure VMware Solution integration is the recommended method for monitoring AVS environments as it handles specific cloud-context relationships not effectively captured by the standard vSphere adapter.