Skip to main content

 How to Export a List of Managed, Onboarded, and Discovered VMs from VMware Aria Automation 8.x

https://knowledge.broadcom.com/external/article?articleNumber=345958


Products

VMware Aria Suite

Issue/Introduction

This article will help you generate and export a list of Virtual Machines (VMs) along with their status (managed, onboarded, or discovered) from VMware Aria Automation.

Currently, there is no option to directly export this data from the VMware Aria Automation UI. This guide provides a detailed workaround by querying the VMware Aria Automation database.

Environment

VMware Aria Automation 8.x

Resolution

The list of VMs can be generated by running a SQL query against the VMware Aria Automation database. Carefully follow the steps below to export the list in CSV format.

Prerequisites

  • Take snapshots or backups of all VMware Aria Automation nodes as a precautionary measure before proceeding.
  • You have SSH access enabled.
  • You have root username and password for the appliances.
  • You are familiar with SQL query syntax.
  • You have access to file transfer utilities such as scp or WinSCP. 

Procedure

  1. Prepare the Query File:
    1. Create a SQL query file to retrieve the VM list. Save the file with the .sql extension. For example, name it VMStatusQuery.sql.
    2. The content of the query file should be as follows:
      SELECT name, state, origin FROM dep_resource WHERE type='Cloud.vSphere.Machine';
      • Note: This process may be used to run other different SQL Queries against the target database.
    3. Find the writable PSQL container by directly running this script from one of the appliances you are connected to over SSH:
      for pod in $(kubectl get pods --namespace prelude -l app=postgres -o jsonpath='{.items[?(@.status.phase=="Running")].metadata.name}'); do
      if kubectl exec --namespace prelude -it $pod -- /bin/bash -c "chpst -u postgres -- psql -t -c 'SELECT pg_is_in_recovery();'" | grep -q "f"; then
        echo "Writable master found: $pod"
        break
      fi
      done
    4. Using the output from Step 1.3, SSH to this node then use a file transfer utility like WinSCP to copy this .sql file to the VMware Aria Automation appliance. Place it in the /data directory.
  2. Change File Permissions
    1. SSH to one of the VMware Aria Automation appliances and log in as root.
    2. Change the file ownership and permissions to ensure the database can execute the file:
      chown postgres:postgres /data/VMStatusQuery.sql
      chmod 666 /data/VMStatusQuery.sql
  3. Connect to the VMware Aria Automation Database:
    1. Run the following command to connect to the database using the vracli tool:
      vracli dev psql
    2. You will be prompted to confirm; type yes and press Enter.
  4. Run the Query and Export Data to CSV:
    1. Once connect to the database, change to the catalog-db (or any other database like provisioning-db) and run the query to export the data to a CSV (or a text / log) file:
      \c catalog-db;
      \o /data/VMStatus.csv;
      \i /data/VMStatusQuery.sql;
      \o
    2. This will execute the query and save the output to /data/VMStatus.csv.
  5. Retrieve the CSV file:
    1. Use WinSCP or another file transfer utility to copy the CSV file from the /data directory to your local machine for further analysis.

Additional Information:

  • The resulting CSV file can be opened with spreadsheet software like Microsoft Excel / Google Sheets for sorting, filtering, and other auditing purposes.
    • You may import this data on a regular schedule into another database for more granular auditing purposes or use Aria Automation Orchestrator to automate this procedure in a workflow using the SQL plug-in.
      • Support Services cannot help with that particular process. Please contact Professional Services for additional information.

Comments

Popular posts from this blog

Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware

 🔹 Step-by-Step Explanation of Ballooning, Compression & Swapping in VMware ⸻ 1️⃣ Memory Ballooning (vmmemctl) Ballooning is the first memory reclamation technique used when ESXi detects memory pressure. ➤ Step-by-Step: How Ballooning Works  1. VMware Tools installs the balloon driver (vmmemctl) inside the guest OS.  2. ESXi detects low free memory on the host.  3. ESXi inflates the balloon in selected VMs.  4. Balloon driver occupies guest memory, making the OS think RAM is full.  5. Guest OS frees idle / unused pages (because it believes memory is needed).  6. ESXi reclaims those freed pages and makes them available to other VMs. Why Ballooning Happens?  • Host free memory is very low.  • ESXi wants the VM to release unused pages before resorting to swapping. Example  • Host memory: 64 GB  • VMs used: 62 GB  • Free: 2 GB → ESXi triggers ballooning  • VM1 (8 GB RAM): Balloon inflates to 2 GB → OS frees 2 GB → ESXi re...

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...

ESXi Host Troubleshooting Checklist

  🛠️ ESXi Host Troubleshooting Checklist (With Complete Log Locations) ✅ 1. Host Status & Connectivity Check host state in vCenter (Connected / Not Responding / Disconnected) Review CPU, RAM, and datastore usage Validate HA/DRS recommendations ✅ 2. Hardware Health Monitor hardware sensors (CPU, DIMMs, fans, PSU, RAID) Check RAID controller logs via vendor tools View hardware status in: vCenter → Monitor → Hardware Health DCUI → Hardware Status ✅ 3. Network Validation Verify vSwitches, Port Groups, NIC teaming, VLAN tagging Check vmkernel ports (mgmt, vMotion, iSCSI, vSAN) Test reachability using: Shell vmkping < IP > Show more lines Validate physical NIC status and link speed ✅ 4. Storage & Datastore Checks Confirm datastore accessibility Rescan storage adapters (iSCSI/FC/NFS) Validate multipathing (Round Robin / Fixed / MRU) Check datastore latency with esxtop ✅ **5. Critical Logs & Their Locations (Full List) Here are key ESXi log files that every VMware adm...