Important

   

This documentation space contains information about PATROL Agents when deployed in a TrueSight Operations Management environment. If you are a BMC Helix Operations Management user, see PATROL Agent 22.4 for BMC Helix Operations Management. Open link

Upgrading

This section provides instructions to upgrade PATROL Agent.

Before you begin

From PATROL Agent version 22.3.01, the default mode of communication between PATROL Agent and Integration Services is TLS v1.2.

Review the following topics

Security planning. Open link

Changing the security certificate configuration options Open link

Configuring the PATROL Agent to Integration Service communication to enable TLS 1.2 Open link

Configuring TrueSight Infrastructure Management to enable TLS 1.2 Open link

Best practices to upgrade PATROL Agent to version 22.3.01 or later that are connected to non-TLS ISNs.  Open link

  • If ISN is not configured in TLS mode, the PATROL Agent version 22.3.01 or later does not connect to the ISN.
  • The p7_change_security_level* script is deprecated from the 22.3.01 version of PATROL Agent. 

Perform the following steps to upgrade PATROL Agent:

  1. Create a deployable package.

  2. Deploy the package either by using the TrueSight console or downloading the package to the host computer.

  3. (When package does not contain root password in UNIX) Run hostname__install.log_rootscripts

Step 1: Create a deployable package

Create a deployment package with the PATROL Agent version to which you want to upgrade.

When you create a deployable package to upgrade PATROL Agent in UNIX and plan to deploy the package by using TrueSight console, you must enter the root password. If you do not enter the root password, the upgrade does not proceed.
  

If you want to upgrade without providing the root password during the creation of the package, you can upgrade with the silent option.

For instructions to create a deployable package, see  creating a deployable package Open link

Step 2: Deploy the package

To deploy the package by using the TrueSight console

  1. Select Configuration > Managed Devices.
  2. Find the PATROL Agent version that you want to upgrade.

  3. From the PATROL Agent action menu, select Deploy and Install Packages.
  4. Select the package that includes the PATROL Agent to be upgraded and select Deploy and Install.

  5. View the status in the Deploy Status column.


To deploy the package silently

  1. Log in by using PATROL default account to the host computer where you want to upgrade the PATROL Agent.
  2. Copy the package that you downloaded to a temporary directory location.
  3. Extract the package.
    It is extracted to the <PA_EXTRACTED_PACKAGE>\bmc_products  directory.
  4. From the bmc_products directory, run one of the following commands:

    • Windows:  RunSilentInstall.exe

    • UNIX:  ./RunSilentInstall.sh

    • (UNIX without root password)  ./RunSilentInstall.sh -no_backup
  5. Start the PATROL Agent, if you selected to start the PATROL Agent manually during package creation.
    For more information, see Starting and stopping the PATROL Agent . Open link

Step 3: (UNIX only) Post upgrade steps Run hostname__install.log_rootscripts

When deploying the package silently, if you did not enter the root password, you need to run the <hostname>_<port>_install.log_rootscripts script and make some other small modifications. 

  1. Stop the PATROL Agent process if it is running:
    For more information, see Starting and stopping the PATROL Agent . Open link
  2. Navigate to the unpacked installation files directory:
         cd <installation_directory>/log/<date_time_of_install>_install/
         Example: /opt/bmc/log/2021_07_08_05_57_59_install/
  3. Switch to the root user by using the following command and entering the root password:
         su
  4. As root user, rename the <hostname>_<port>_install.log_rootscripts file to <hostname>_<port>_install.log_rootscripts.sh by running the following command:
         mv <hostname>_<port>_install.log_rootscripts <hostname>_<port>_install.log_rootscripts.sh
         Example: mv myhostname_3181_install.log_rootscripts myhostname_3181_install.log_rootscripts.sh
  5. As root user, assign the permissions to run the <hostname>_<port>_install.log_rootscripts.sh file:
          chmod 755 <hostname>_<port>_install.log_rootscripts.sh
          Example: chmod 755 myhostname_3181_install.log_rootscripts.sh
  6. As root user, run <hostname>_<port>_install.log_rootscripts.sh:
         ./<hostname>_<port>_install.log_rootscripts.sh
       
    Example: ./myhostname_3181_install.log_rootscripts.sh
  7. Run patrolrc.sh to load environment variables:
    1. Navigate to Patrol3 directory:
      cd <installation_directory>/Patrol3
      Example: cd /opt/bmc/Patrol3
    2. Run patrolrc.sh:
      . ./patrolrc.sh
  8. Navigate to the Patrol Agent’s bin directory and run migrate_kdb_password.sh:
    1. Navigate to the Patrol bin directory:
      cd $PATROL_HOME/bin
    2.  Run the migrate_kdb_password.sh script:
      ./migrate_kdb_password.sh
  9. Verify the PatrolAgent/snmpmagt binaries are owned by the root account and that the sticky bit is set:
          ls -tl PatrolAgent
    The following output is displayed:
          -rwsr-xr-x 1 root patrol 12641000 Feb 10 10:39 PatrolAgent
     The S indicates the sticky bit is set successfully on the PatrolAgent binary. (Same for the snmpmagt binary, if present.)

    Learn more about the S bit Open link

  10. Ensure the access file is owned by the default account:
      sudo chown <default_account>:<default_account> <install_directory>/common/security/keys/access
     
    Example: sudo chown patrol:patrol /opt/bmc/common/security/keys/access
  11. As the default account, start the PATROL Agent.
     For more information, see Starting and stopping the PATROL Agent . Open link
  

         
       

Was this page helpful? Yes No Submitting... Thank you

Comments