Skip to main content

VMware vCenter Server

Integrate VMware vCenter with Cloudaware to inventory ESXi hosts, clusters, virtual machines, datastores, networks, and related vSphere resources in the Cloudaware CMDB.

info
  • Audience: Cloudaware administrators, VMware administrators, virtualization teams, cloud engineers, operation and security teams
  • Outcome: VMware vCenter environments are connected to Cloudaware for vSphere inventory, configuration, and hybrid cloud reporting

Capabilities

The integration supports:

  • Read-only discovery of core vSphere inventory: vCenter management servers, datacenters, clusters, hosts, virtual machines, etc.
  • Relationship mapping between VMware infrastructure, applications, and assets
  • Optional correlation with Breeze Agent data using the vCenter Service Instance UUID
  • Search, reporting, and coverage analysis for VMware resources using CMDB Navigator, CMDB list views, and reports

Prerequisites

Before you begin, make sure you have:

  • Access to a Cloudaware account.
  • A user with access to the Admin Console and permissions to manage cloud accounts, organizations, and integrations (Cloudaware Administrator).
  • A supported VMware vCenter environment.
  • vCenter access details:
    • vCenter Management Server hostname or FQDN
    • Dedicated vCenter username and password
    • Read-only permissions for the objects Cloudaware must inventory
  • For private vCenter environments, a TunHub gateway deployed and configured.
  • Optional: To allow Cloudaware to collect vCenter custom attributes, add the System.View permission using a custom role.
  • Optional: vCenter Service Instance UUID (instanceUuid) for Breeze Agent correlation.

Add a VMware vCenter Server Integration

To connect VMware vCenter Server to Cloudaware:

  1. In Cloudaware, go to Admin (Admin Console).
  2. Select vCenter Management Server.
  3. Click + ADD.
  4. Enter the following values:
    • Name: A display name for the vCenter integration
    • URL: The direct vCenter URL or the TunHub URL for private connectivity
    • Hostname: The vCenter Management Server hostname
    • Username: The vCenter username dedicated to Cloudaware
    • Password: The password for that vCenter user
    • Service Instance UUID: optional; the instanceUuid value used for Breeze Agent
    • Trust Certificate: Enable when required for TunHub or private certificate scenarios
  5. Click SAVE.
  6. Confirm that the integration status indicator is green.
tip

Allow the initial discovery cycle to complete after enabling the integration. In private TunHub scenarios, initial connection and sync may take up to 24-48 hours.

View VMware Data in CMDB

To browse discovered VMware resources:

  1. In Cloudaware, open CMDB Navigator.
  2. In the left pane, select VMWARE.
  3. Open an object list, e.g., vCenter Virtual Machines, to view records.

Use CMDB list views and reports to analyze vSphere inventory, relationships, and coverage.

Supported Objects

Cloudaware ingests the following vCenter objects:

VMware vCenter ObjectCMDB Object API Name
vCenter ClusterCA10V__CaVCenterCluster__c
vCenter Custom Attribute DefinitionCA10V__CaVCenterCustomAttributeDefinition__c
vCenter DatacenterCA10V__CaVCenterDatacenter__c
vCenter DatastoreCA10V__CaVCenterDatastore__c
vCenter FolderCA10V__CaVCenterFolder__c
vCenter HostCA10V__CaVCenterHost__c
vCenter K8s ClusterCA10V__CaVCenterKubernetesCluster__c
vCenter K8s Cluster Config MapCA10V__CaVCenterK8sClusterConfigMap__c
vCenter K8s Cluster Daemon SetCA10V__CaVCenterK8sClusterDaemonSet__c
vCenter K8s Cluster DeploymentCA10V__CaVCenterK8sClusterDeployment__c
vCenter K8s Cluster EndpointCA10V__CaVCenterK8sClusterEndpoint__c
vCenter K8s Cluster HPACA10V__CaVCenterK8sClusterHpa__c
vCenter K8s Cluster IngressCA10V__CaVCenterK8sClusterIngress__c
vCenter K8s Cluster Limit RangeCA10V__CaVCenterK8sClusterLimitRange__c
vCenter K8s Cluster NamespaceCA10V__CaVCenterK8sClusterNamespace__c
vCenter K8s Cluster Network PolicyCA10V__CaVCenterK8sClusterNetworkPolicy__c
vCenter K8s Cluster Network Policy RuleCA10V__CaVCenterK8sClusterNetworkPolicyRule__c
vCenter K8s Cluster NodeCA10V__CaVCenterK8sClusterNode__c
vCenter K8s Cluster Node AddressCA10V__CaVCenterK8sClusterNodeAddress__c
vCenter K8s Cluster PodCA10V__CaVCenterK8sClusterPod__c
vCenter K8s Cluster Pod ContainerCA10V__CaVCenterK8sClusterPodContainer__c
vCenter K8s Cluster Pod Disruption BudgetCA10V__CaVCenterK8sClusterPodDisruptionBudget__c
vCenter K8s Cluster Replica SetCA10V__CaVCenterK8sClusterReplicaSet__c
vCenter K8s Cluster Resource QuotaCA10V__CaVCenterK8sClusterResourceQuota__c
vCenter K8s Cluster RoleCA10V__CaVCenterK8sClusterRole__c
vCenter K8s Cluster Role BindingCA10V__CaVCenterK8sClusterRoleBinding__c
vCenter K8s Cluster SecretCA10V__CaVCenterK8sClusterSecret__c
vCenter K8s Cluster ServiceCA10V__CaVCenterK8sClusterService__c
vCenter K8s Cluster Service Acc SecretCA10V__CaVCenterK8sClusterServiceAccSecret__c
vCenter K8s Cluster Service AccountCA10V__CaVCenterK8sClusterServiceAccount__c
vCenter K8s Cluster Stateful SetCA10V__CaVCenterK8sClusterStatefulSet__c
vCenter K8s Cluster Storage ClassCA10V__CaVCenterK8sClusterStorageClass__c
vCenter Management ServerCA10V__CaVCenterManagementServer__c
vCenter NetworkCA10V__CaVCenterNetwork__c
vCenter Resource PoolCA10V__CaVCenterResourcePool__c
vCenter Supervisor ClusterCA10V__CaVCenterSupervisorCluster__c
vCenter Supervisor Cluster NamespaceCA10V__CaVCenterNamespace__c
vCenter Virtual MachineCA10V__CaVCenterVirtualMachine__c
vCenter Virtual Machine DiskCA10V__CaVCenterVirtualMachineDisk__c
vCenter Virtual Machine Ethernet AdapterCA10V__CaVCenterVirtualMachineEthernetAdapter__c
vCenter Virtual Machine FactCA10V__CaVCenterVirtualMachineFact__c
vCenter Virtual Machine Mount PointCA10V__CaVCenterVirtualMachineMountPoint__c

Troubleshooting

note

Initial data collection may take time to complete.

Authentication or Permission Errors

  • Confirm the vCenter user can sign in to vCenter directly.
  • Verify that the account is not locked or expired.
  • Confirm that the account has read-only access to the required vCenter inventory scope.
  • Re-enter the credentials by editing the integration in Cloudaware.

Connectivity or SSL Errors

  • Verify that Cloudaware can reach the vCenter endpoint directly or through TunHub.
  • Confirm firewall rules allow traffic to the vCenter endpoint.
  • If using TunHub, verify that the route and gateway are healthy.
  • Enable Trust Certificate when required for the certificate presented through the private route.

No VMware Data Appears After Setup

  • Allow the initial discovery cycle to complete.
  • Confirm that the integration status indicator is green.
  • In CMDB Navigator, verify that you are viewing the VMWARE section.
  • Check that the vCenter account has access to the datacenters, clusters, hosts, and virtual machines you expect Cloudaware to collect.

Still stuck? Contact Cloudaware Support at support@cloudaware.com with the integration name and a brief description of the issue.

Reconfigure or Remove the Integration

warning

To rotate credentials, edit the existing integration instead of deleting and re-creating it.

Update Credentials or Connection Settings

  1. Go to Admin.
  2. Select vCenter Management Server.
  3. Select the specific integration.
  4. Open the three-dot menu (), then click Edit.
  5. Update the required fields.
  6. Click Save.

Remove the Integration from Cloudaware

  1. Go to Admin.
  2. Select vCenter Management Server.
  3. Select the specific integration.
  4. Open the three-dot menu (), then click Delete.
  5. Confirm the deletion if prompted.

Security Notes

  • Use a dedicated vCenter account with the minimum required read-only access.
  • Rotate the vCenter password according to your organization's credential-rotation policy.
  • Limit network access to the vCenter endpoint to trusted Cloudaware or TunHub routes.
  • Credentials are stored securely and are only visible to Cloudaware administrators.