Verify that you can continue to operate the vRealize Automation stack even as individual stack components become unavailable.

About this task

Performing system login and provisioning blueprints while some of the stack components are unavailable validates that the vRealize Automation stack is built for resiliency and eliminates single points of failure.

Expected Outcome

You can successfully perform all the login and provisioning operations without any disruptions.

Procedure

  1. Log in to vCenter Server by using the vSphere Web Client.
    1. Open a Web browser and go to https://sfo01m01vc01.sfo01.rainpole.local/vsphere-client.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      administrator@vsphere.local

      Password

      vsphere_admin_password

  2. Shut down the secondary node of vRealize Automation.
    1. From the Home menu, select VMs and Templates.
    2. In the Navigator pane, expand the sfo01m01vc01.sfo01.rainpole.local > sfo01-m01dc > sfo01-m01fd-vra tree.
    3. Right-click the vra01svr01b virtual machine, select Power > Shut Down Guest OS and click Yes in the confirmation box that appears.
  3. Log in to the vRealize Automation Rainpole portal.
    1. Open a Web browser and go to https://vra01svr01.rainpole.local/vcac/org/rainpole.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      vra-admin-rainpole

      Password

      vra-admin-rainpole_password

      Domain

      rainpole.local

  4. Request a single-machine blueprint item from the service catalog of vRealize Automation.
    1. In the Infrastructure Service Portal, click the Catalog tab.
    2. Locate the Windows Server 2012 R2 - SFO Prod single-machine blueprint and click Request.
    3. On the New Request page, click Submit to request a virtual machine provisioning.
  5. Click the Requests tab and verify that the Status column for the Windows Server 2012 R2 - SFO Prod single-machine blueprint provisioning is Successful.
  6. Repeat the procedure and validate for the other nodes of vRealize Automation by shutting down either primary or secondary node.

What to do next

If you encounter issues while performing this procedure, use the following troubleshooting tips:

Troubleshooting Tips

  • Ensure that automatic failover of Manager Service is enabled.

    Note:

    This feature is available in vRA 7.3.

  • Ensure that the load balancer is operational and the application profiles, pools, service monitoring, and virtual servers pertaining to vRealize Automation are configured correctly.

  • Ensure that vRealize Automation appliance clustering is configured correctly.

  • Ensure that at least one component in each layer of the stack is up and running.

  • Ensure that all the service monitoring URLs are functional.