Skip to main content

 Troubleshooting Aria Automation reconciliation of vMotion migrated VM's

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

Products

VMware Aria Suite

Issue/Introduction

Starting in Aria Automation 8.18.1, reconciliation of managed VM's that are vMotioned is possible preventing the VM's from reporting a 'missing' status: https://techdocs.broadcom.com/us/en/vmware-cis/aria/aria-automation/all/Chunk340324046.html

In some situations, a vMotion of a VM can still result in the machine going missing from Aria Automation inventory rendering the VM unavailable for management.

Environment

Aria Automation 8.18.1 and later

Cause

This can be caused by incorrect configuration of config mappings, failures leading to update status in Aria Automation database, and migration status not being reported correctly by vCenter.  See below for various checks to identify where this workflow may be failing.

Resolution

Validate vCenter Events and Automation Logging

vCenter must post the event so that the Aria Automation service account has permission to read them:

  1. Check that the service account assigned to the Cloud Account can access vCenter and see the events.  Look for events in vCenter related to "VmRelocatedEvent" and "VmBeingRelocatedEvent".In Automation logs, check in the Provisioining-service-app logs for responses to these migrations that include "VmEmigratingEvent".

Checking that the event broker config maps contain the correct event types

The Event Broker service in Aria Automation must be properly patched and it's config maps must be updated.  If something failed during upgrade or the service has not been patched, we can see it by performing the following: 

  1. SSH into Aria Automation.
  2. Execute the following command:
    1. kubectl get configmaps -n prelude ebc-events-config -o json

Review the output for the "ebs.connect.enabled-vcenter-event-types" to ensure that we're collecting proper vCenter events. An example of this output:

"ebs.connect.enabled-vcenter-event-types": "VmMigratedEvent,VmEmigratingEvent,VmBeingRelocatedEvent,VmRelocatedEvent,VmRelocateFailedEvent,com.vmware.vc.vm.DstVmMigratedEvent,com.vmware.vc.vm.SrcVmMigratedEvent,com.vmware.vc.vm.SrcVmMigrateFailedEvent,VmFailedMigrateEvent"

 

  1. Wait for data to sync and validate that the migration shows successful.

Validate the migration state is being populated in the Aria Automation database:

When migration is detected and a reconcile attempt is made, the resource metadata is updated with results under custom properties.  Check in the UI under the deployment/resource/custom properties for the properties called "migrationMessage" and "migrationStatus" and if there are errors they should show up in the migrationMessage.  Example of a successful reconcile will include the following status:

Alternatively you can query the metadata details of the resource in the database:

  1. SSH into the Aria Automation appliance and execute the following commands:
    1. vracli dev psql provisioning-db
    2. \x
    3. select * from compute_state where name = 'COMPUTERNAME'

In the output, look for all instances of the custom properties related to 'migration' for information.

Comments

Post a Comment

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...
Post a Comment
Read more

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...
Post a Comment
Read more
  vCenter Troubleshooting Tips, Common Issues & Log Locations 🚀 1. General Troubleshooting Approach A. Check service health first For vCenter Server Appliance (VCSA): Shell https : / / < vcenter - FQDN > : 5480 Show more lines Go to Services → Health to verify: vCenter Server ESXi hosts vSphere Client DNS, NTP, DB connections vpxd, vpxd-svcs, vsphere-ui B. DNS & NTP checks vCenter is highly dependent on correct DNS & time sync. Check: Shell nslookup < vcenter - fqdn > nslookup < esxi - host - fqdn > Show more lines Time drift > 5 minutes causes: Login failures vpxd crashes PSC authentication issues C. Check storage/database health Slow DB/storage = UI slow, tasks hung. For VCSA: Shell df - h du - sh / storage / log / * / var / log Show more lines Free up space if partitions hit >80%. D. Restart critical services safely On VCSA: Shell service - control - - status service - control - - stop - - all service - control - - start - - all ...
Post a Comment
Read more