After upgrading the vRealize Log Insight cluster in Region A, upgrade the vRealize Log Insight agents on the Windows Server virtual machines in the environment. You download the latest agents from the vRealize Log Insight cluster and upgrade the agent that runs on the vRealize Automation IaaS servers, Microsoft SQL Server, and Site Recovery Manager Server in Region A.

Procedure

  1. Log in to the vRealize Log Insight user interface.
    1. Open a Web browser and go to https://sfo01vrli01.sfo01.rainpole.local.
    2. Log in by using the following credentials.
      Setting Value
      User name admin
      Password vrli_admin_password
  2. Click the configuration drop-down menu icon and select Administration.
  3. Under Management, click Agents.
  4. Click the Download Log Insight Agent Version 4.7.0 link from the bottom of the page.
  5. In the Download Log Insight Agent Version 4.7.0 dialog box, download the following vRealize Log Insight Agent files on the Windows host that you use to access the environment.

    Setting

    Value

    Download location

    https://sfo01vrli01.sfo01.rainpole.local

    Agent version

    Windows MSI (32-bit/64-bit)

    Save As

    VMware-Log-Insight-Agent-4.7.0-build_number_Region_A_vRealize_Log_Insight_VIP_address.msi

  6. Upgrade the vRealize Log Insight Agents for Windows virtual machines.
    1. Open a Remote Desktop Protocol (RDP) connection to each of the following Windows virtual machines.

      SDDC Layer

      Role

      Fully Qualified Domain Name

      Cloud Management

      vRealize Automation IaaS Web Server

      vra01iws01a.rainpole.local

      vra01iws01b.rainpole.local

      vRealize Automation IaaS Manager Service and DEM Orchestrator

      vra01ims01a.rainpole.local

      vra01ims01b.rainpole.local

      vRealize Automation IaaS DEM Worker

      vra01dem01a.rainpole.local

      vra01dem01b.rainpole.local

      vRealize Automation IaaS Proxy Agent

      sfo01ias01a.sfo01.rainpole.local

      sfo01ias01b.sfo01.rainpole.local

      Microsoft SQL Server

      vra01mssql01.rainpole.local

      Business Continuity

      Site Recovery Manager

      sfo01m01srm01.sfo01.rainpole.local

    2. Log in to the vRealize Automation windows virtual machine using the following credentials.

      Setting

      Value

      User name

      rainpole\svc-vra

      Password

      svc-vra_user_password

    3. Copy the VMware-Log-Insight-Agent-4.7.0-build_number_Region_A_vRealize_Log_Insight_VIP_address.msi file from the Windows host to the vRealize Automation Windows Server virtual machine.
    4. Open an administrative command prompt window, and navigate to the directory where the .msi file is saved.
    5. Run the following command to install the vRealize Log Insight agent with custom values.
      VMware-Log-Insight-Agent-4.7.0-build_number_192.168.31.10.msi SERVERPORT=9000 AUTOUPDATE=yes LIAGENT_SSL=no
    6. In the VMware vRealize Log Insight Agent Setup wizard, accept the license agreement and click Next.
    7. With the Log Insight host name sfo01vrli01.sfo01.rainpole.local shown in the Host text box, click Install.
    8. When the installation is complete, click Finish.
    9. Repeat this step on the remaining vRealize Automation IaaS virtual machines including Microsoft SQL Server.
    10. After the vRealize Log Insight agent has been upgraded on the vRealize Automation IaaS virtual machines, repeat this step on the Site Recovery Manager virtual machine using the following credentials to log in.
      Settings Value
      User name Windows administrator user
      Password windows_administrator_password
  7. After you upgrade the vRealize Log Insight agents for Region A, verify the agent version in the vRealize Log Insight cluster.
    1. Open a Web browser and go to https://sfo01vrli01.sfo01.rainpole.local.
    2. Log in by using the following credentials.
      Setting Value
      User name admin
      Password vrli_admin_password
    3. Click the configuration drop-down menu icon and select Administration.
    4. Under Management, click Agents.
    5. On the Agents page, verify that the Version column shows 4.7.0.xxxxxxx for all the windows server virtual machines.