Upgrading

This section provides instructions to upgrade PATROL Agent.

Before you begin

The default mode of communication between PATROL Agent and Integration Services is now TLS v1.2.

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

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.

   Important

   If the word PATROLAgent (case insensitive) is present in the service name (on Windows), the service is also upgraded.

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 .

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

When deploying the package silently, if you did not enter root password, you need to run the hostname__install.log_rootscripts script file. 

1. Stop the PATROL Agent process if it is running.
   For more information, see Starting and stopping the PATROL Agent .

2. Navigate to the following directory.
   cd <Installation_directory>/log/<date_time>_install/ directoryExample : /opt/bmc/log/2021_07_08_05_57_59_install/xyz
3. For the root user:
   1. Switch to the root user by using the following command and entering the root password:
          su
   2. 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
   3. 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
   4. As root user, run <hostname>_<port>_install.log_rootscripts.sh:
          ./<hostname>_<port>_install.log_rootscripts.sh
         Example: ./myhostname_3181_install.log_rootscripts.sh
4. For the sudo user:
   1. Log in using the sudo user credentials.
   2. Ensure that one of the entries below is added by the root user to the /etc/sudoers file, depending on the use case:
      1. Specifying a group name:
         %<groupname> ALL=/tmp/install_script.sh
      2. Specifying a user name:
         <sudousername> ALL=/tmp/install_script.sh

      3. Specifying a specific hostname:
         {{code language="none"}}
         <sudouser> <hostname>=/tmp/install_script.sh
         
         {{/code}}If you are using Solaris, add the below entry to the /etc/sudoers file for sudo users:

         ALL=/tmp/install_script.sh, /bin/cp, /usr/bin/cp, /bin/ln
   3. As the sudo user, run the script /tmp/install_script.sh using the sudo command. Enter the sudo password when prompted, as illustrated in the example below:
      Example: 
      $ sudo /tmp/install_script.sh
      [sudo] password for patdev1:
5. Verify if the PatrolAgent/snmpmagt binaries are owned by the root account and set the S bit.
6. To verify:
   1. Navigate using cd $BMC_BASE/Patrol3.
   2. Run the . ./patrolrc.sh.
   3. Then run cd $PATROL_HOME/bin.

   4. Run the command ls -tl PatrolAgent
      -rwsr-xr-x 1 root patrol 12641000 Jan 10 10:39 PatrolAgent

      The s indicates S bit is set successfully on the PatrolAgent binary.

7. Start the PATROL Agent.
   For more information, see Starting and stopping the PATROL Agent .