Re-join the secondary vRealize Automation appliance vra01svr01b.rainpole.local to the cluster where the vra01svr01b.rainpole.local appliance is primary. As a result, the secondary appliance re-synchronizes with the primary appliance for the latest data and configuration settings after the migration to embedded vRealize Orchestrator.

Procedure

  1. Log in to the appliance management console of the secondary vRealize Automation appliance.
    1. Open a Web browser and go to https://vra01svr01b.rainpole.local:5480.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vra_appB_root_password

  2. Rejoin the secondary appliance to the primary appliance.
    1. On the vRA Settings tab, click Cluster.
    2. Under the Distributed Deployment Information pane, enter the following settings and click Join Cluster.

      Setting

      Value

      Leading Cluster Node

      vra01svr01a.rainpole.local

      Admin User

      root

      Password

      vra_appA_root_password

    3. When prompted, accept the certificate of the primary vRealize Automation appliance.
    4. Allow for the vra01svr01b.rainpole.local to re-synchronize with vra01svr01a.rainpole.local.
  3. Verify on the secondary appliance that all services are registered and license information is valid.
    1. After the synchronization is complete, click the Services tab and verify that all services on vra01svr01b.rainpole.local are registered.
    2. Click the vRA Settings > Licensing tab and verify that the product license licensing information is available and valid.
      Note:

      If the license is removed, enter the license key in the New License Key field and click Submit Key. Verify that the license has been successfully applied. Repeat this step for vra01svr01a.rainpole.local appliance.

  4. Log in to the secondary vRealize Automation appliance using a Secure Shell (SSH) client.
    1. Open an SSH connection to vra01svr01b.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vra_appA_root_password

  5. Restart the Orchestrator server and Control Center services on the appliance and verify if they are running.
    service vco-configurator restart && service vco-server restart
    service vco-configurator status && service vco-server status
  6. Set the Control Center service of the built-in vRealize Orchestrator server on vra01svr01b.rainpole.local to automatically start on restart of the appliance.
    chkconfig vco-configurator on
  7. Verify that the vRealize Orchestrator cluster is synchronized on the primary vRealize Automation appliance.
    1. Open a Web browser and go to https://vra01svr01a.rainpole.local:8283/vco-controlcenter.
    2. Log in using the following credentials.

      Setting

      Value

      Domain

      rainpole.local

      User name

      svc-vra

      Password

      svc-vra_password

    3. On the home page, click Validate Configuration under Manage and verify that the report shows no errors for any component.
    4. On the home page, click Orchestrator Cluster Management, and verify that only the vRealize Automation appliances are present and that the Configuration Synchronization State is a green Synchronized.
  8. If you cannot access the vRealize Orchestrator Control Center on the primary appliance, reset the authentication provider and reconfigure the vRealize Orchestrator registration.
    1. Open an SSH connection to the primary vRealize Orchestrator virtual appliance vra01svr01a.rainpole.local.
    2. Log in using the following credentials.

      Setting

      Value

      User name

      root

      Password

      vra_appA_root_password

    3. Reset the authentication provider for vRealize Orchestrator.
      /var/lib/vco/tools/configuration-cli/bin/vro-configure.sh reset-authentication
    4. Remove the vRealize Orchestrator registration file.
      rm /etc/vco/app-server/vco-registration-id
    5. Reconfigure the vRealize Orchestrator registration.
      vcac-vami vco-service-reconfigure
    6. Restart the Orchestrator server and the Control Center services of the built-in vRealize Orchestrator server.
      service vco-server restart && service vco-configurator restart