If you use clustered external instances of vRealize Orchestrator with vRealize Automation, you must upgrade each vRealize Orchestrator node individually when you upgrade vRealize Automation.

About this task

You do not need to recreate the existing cluster. vRealize Orchestrator nodes remain part of the cluster after the upgrade.

Prerequisites

Procedure

  1. Shut down each vRealize Orchestrator node.
  2. Select one of the vRealize Orchestrator nodes in the cluster to be the primary vRealize Orchestrator node.

    Record the identifying information for this node to use later.

  3. Take a snapshot of each vRealize Orchestrator node and the vRealize Orchestrator database.
  4. On the vRealize Orchestrator node you selected for the primary node, increase the RAM to 6 GB.
  5. Upgrade the primary vRealize Orchestrator node.
    1. Power on the node you selected to be the vRealize Orchestrator primary node.
    2. Log in as root to the vRealize Orchestrator Appliance management console at https://orchestrator_server:5480.
    3. Select Update > Settings.
    4. Choose your download method and click Save Settings.
    5. Click Status.
    6. Click Check Updates.
    7. Click Install Updates.
    8. Accept the VMware End User License Agreement.
    9. When the update finishes, restart the vRealize Orchestrator appliance.
  6. If your clustered vRealize Orchestrator was previously configured with vRealize Automation authentication type, unregister and re-register the node.
    1. On the primary node, log in as root to the vRealize Orchestrator Control Center at https://your_orchestrator_server_IP_or_DNS_name:8283/vco-controlcenter/.
    2. Click the Configure Authentication Provider icon.
    3. Click Unregister.
    4. Click Connect.
    5. Enter your user name and password credentials.
    6. Select the Configure licenses checkbox and select the vco administrators group.
    7. Click Save Changes.
    8. Navigate to Orchestrator Cluster Management at https://vco-controlcenter:8283/vcocontrolcenter/#/control-app/ha and append ?remove-nodes to the URL, for example, https://vco-controlcenter:8283/vcocontrolcenter/#/control-app/ha?remove-nodes.
    9. For each vRealize Orchestrator node in the old cluster, select the Remove checkbox in the table and click Remove and Refresh.
    10. Restart the main vRealize Orchestrator server service and wait for the service to fully initialize.
  7. Verify that the vco service appears as registered in the vRealize Orchestrator Appliance management console.
  8. On the vRealize Orchestrator Control Center, click the Validate Configuration icon and verify that the configuration is valid.
  9. On the vRealize Orchestrator Control Center, upgrade the vRealize Automation default plugins, which include the NSX plugin.
  10. Log in as root to the vRealize Orchestrator Control Center on the primary vRealize Orchestrator node at https://your_orchestrator_server_IP_or_DNS_name:8283/vcocontrolcenter.
  11. Click the Manage Plugins icon.
  12. Select Browse > plug-in name > Install.
  13. Deploy a new vRealize Orchestrator appliance for a new secondary vRealize Orchestrator node in this cluster.
  14. Set up the network configuration of the new secondary vRealize Orchestrator node to match the secondary vRealize Orchestrator node in the old cluster.
  15. Join the new secondary vRealize Orchestrator node to the primary vRealize Orchestrator node.
    1. Open a secure shell connection and log in to the primary vRealize Orchestrator node and change directories to /etc/vco/app-server/plugins.
    2. Copy all the .xml files that are not prepended with an underscore (_) to the same location on the new secondary vRealize Orchestrator node.

      Make sure that all copied files have the same ownership, vco, and permissions.

    3. Log in as root to the vRealize Orchestrator Control Center on the secondary vRealize Orchestrator node at https://your_orchestrator_server_IP_or_DNS_name:8283/vcocontrolcenter.
    4. Click the Orchestrator Cluster Management icon.
    5. Click Join Node To Cluster and enter the primary vRealize Orchestrator node details.
    6. Click Join and wait for the new secondary vRealize Orchestrator node to complete the join cluster operation.
    7. Verify that the new secondary vRealize Orchestrator node pending configuration fingerprint is the same as the primary vRealize Orchestrator node.
    8. Restart the new secondary vRealize Orchestrator server service from Startup Options in the Control Center.
    9. Verify that the new secondary vRealize Orchestrator node Applied Configuration Fingerprint is the same as the primary vRealize Orchestrator node.
  16. Repeat steps 13-15 for each secondary vRealize Orchestrator node in the old cluster.