Skip to main content

 

Starting and stopping VMware Aria Automation


Observe the proper procedures when starting or shutting down VMware Aria Automation.

The recommended procedure to shut down and start VMware Aria Automation components is to use the Power OFF and ON functionality provided in Lifecycle Operations > Environments section of VMware Aria Suite Lifecycle. The following procedures outline manual methods to shut down and start VMware Aria Automation components in case VMware Aria Suite Lifecycle is not available for some reason.

Shut down VMware Aria Automation

To preserve data integrity, shut down the VMware Aria Automation services before powering off the virtual appliances. Using SSH or VMRC, you can shut down or start all nodes from any individual appliance.

Note:Avoid using vracli reset vidm commands if at all possible. This command resets all configurations of Workspace ONE Access and breaks the association between users and provisioned resources.
  1. Log in to the console of any VMware Aria Automation appliance using either SSH or VMRC.
  2. To shut down the VMware Aria Automation services on all cluster nodes, run the following set of commands.
    Note:If you copy any of these commands to run and they fail, paste them into notepad first, and then copy them again before running them. This procedure strips out any hidden characters and other artifacts that might exist in the documentation source.
    /opt/scripts/deploy.sh --shutdown
  3. Shut down the VMware Aria Automation appliances.

Your VMware Aria Automation deployment is now shut down.

Start VMware Aria Automation

Following an unplanned shutdown, a controlled shutdown, or a recovery procedure, you must restart VMware Aria Automation components in a specific order. VMware Aria Suite Lifecycle is a non-critical component, so you can start it at any time. Workspace ONE Access components must be started before you start VMware Aria Automation.

Note:Verify that applicable load balancers are running before starting VMware Aria Automation components.
  1. Power on all VMware Aria Automation appliances and wait for them to start.
  2. Log into the console for any appliance using SSH or VMRC and run the following command to restore the services on all nodes.
    /opt/scripts/deploy.sh
  3. Verify that all services are up and running with the following command.
    kubectl get pods --all-namespaces
    Note:You should see three instances of every service, with a status of either Running or Completed.

    When all services are listed as Running or Completed, VMware Aria Automation is ready to use.

Restart VMware Aria Automation

You can restart all VMware Aria Automation services centrally from any of the appliances in your cluster. Follow the preceding instructions to shut down VMware Aria Automation, and then use the instructions to start VMware Aria Automation. Before restarting VMware Aria Automation, verify that all applicable load balancer and Workspace ONE Access components are running.

When all services are listed as Running or Completed, then VMware Aria Automation is ready to use.

Run the following command to verify that all services are running:

kubectl -n prelude get pods
Labels:

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