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

Comments

Popular posts from this blog

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...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...