Upgrading IBM Spectrum LSF RTM to 10.2

The IBM Spectrum LSF RTM 10.2 packages upgrade your RTM system from version 10.1.0 or later to version 10.2.

1. Log in to the RTM host as root.
2. Create a directory to store the installation packages.
   For example:

   mkdir -p /mnt/rtm

   Attention: If /mnt/rtm already contains previous installation packages, move them to a different folder. Make sure that /mnt/rtm contains only the current installation packages.
3. Download the following RTM installation packages compatible with your operating system and store them in the directory you created:
   • rtm-poller-10.2.0-rhel7-<arch>.tar.gz
   • rtm-server-10.2.0-rhel7-<arch>.tar.gz
4. Remove any non-RTM provided legacy Cacti plugins from RTM_TOP/cacti/plugins.
   Note: RTM may run with but exceptions if your customized Cacti plugins are not compatible with Cacti 1.2.x.
5. Go to the directory with the upgrade installation packages and uncompress the rtm-server-10.2.0-rhel7-<arch>.tar.gz file.
   For example:

   #cd /mnt/rtm
   #tar -zxvf rtm-server-10.2.0-rhel7-x64.tar.gz

6. Back up the RTM basic database before proceeding.

   In your existing RTM, go to Console > Utilities > Grid Utilities > Force Cacti Backup.

   The backup process may take a long time for large deployments.

   Note: If you are using a remote database or remote pollers, you must reconfigure the remote database/poller settings during or after the upgrade. Be sure to back up your remote database/poller settings before you configure them.
7. If RTM is using a remote database, edit the /etc/rtm_install.conf file to configure the remote database connection information:

   remote_db='Y'
   
   # Enter the username to be used to connect to database during installation 
   # to perform database changes
   # This user needs to have sufficient privileges to create/delete/modify database/tables.
   db_username='root'
   
   # Enter the password to be used to connect to the database during installation 
   # to perform database changes
   db_password=''
   
   # Specify the database hostname
   db_host=''
   
   # Specify the database port number
   db_port=''

8. Edit the upgrade.config file at /mnt/rtm and configure all the required parameters.
   To configure any optional parameters, uncomment the line and specify the appropriate value.
9. Add a new mysql option myisam-recover=FORCE,BACKUP to the [mysqld] section in the MySQL config file my.cnf. This ensures any crashed myisam tables are repaired automatically.
   Important: The update in my.cnf should happen before running the rtm_upgrade.sh script since the database is restarted in the upgrade script and any update will be valid immediately after the RTM upgrade procedure finishes.
10. Run the rtm_upgrade.sh script to upgrade RTM to version 10.2.
    You can refer to/var/log/rtm.upgrade.log for details or errors that were encountered during the upgrade. For example:

    #cd /mnt/rtm
    #sh rtm_upgrade.sh -f upgrade.config

    Note: If you encounter one or more of the following messages during the upgrade:

    Warning:<config file path> created as <config file path>.rpmnew

    this means that the configuration file was modified since the last installation. Merge the modifications into the <config file path>.rpmnew file and replace all the files. For example:

    # diff <config file path> <config file path>.rpmnew
    # cp <config file path> <config file path>.bak
    # vi <config file path>.rpmnew
    # mv <config file path>.rpmnew <config file path>  

    Note: The upgrade script creates a background process to upgrade the jobs table. This process will continue even after you complete the upgrade steps. During this period, the job search is limited.

    Note: If your database table is too big, you can plan to partition the database before you upgrade.

    1. Go to Console > Configuration > RTM Settings > Maint. Under Large System Settings select Enable Record Partition and set the Partition Size.
    2. Click Save.
    3. Log on to the RTM host as root and go to <RTM_TOP>/cacti/plugins/grid and run this command:

       #php -q poller_grid.php -fr -fm

11. If RTM is using remote pollers, refer to Setting up remote license, LSF pollers, or DiskU client pollers to configure remote pollers.
    • For remote pollers, you can find the rtm-pollers-VERSION.ARCH.rpm RPM in /mnt/rtm:
      Copy the RPM to the remote poller host and install them on the remote host:

      # rpm -Uvh rtm-*.rpm

      Note: lmstat will be deleted by the rpm upgrade. Therefore, when upgrading remote license pollers, back up lmstat first then do the upgrade. After upgrading, copy the lmstat back to RTM_TOP/flexlm/bin. Also, the authority of the lmstat should be at least 755. If necessary, use chmod 755 lmstat to change the authority.
    • For remote IBM Spectrum LSF pollers, you can find the rtm-poller-VERSION.ARCH.rpm RPM in /mnt/rtm:
      Copy the RPM to the remote poller host and install them on the remote host:

      # rpm -Uvh rtm-*.rpm

    Run the RTM upgrade command to upgrade the pollers, database, and templates.

12. Restart the RTM services:

    # systemctl restart lsfpollerd
    # systemctl restart licpollerd
    # systemctl restart advocate
    # systemctl restart crond
     # systemctl restart rtmclientd (if installed)

13. If you no longer need them, you can remove the upgrade files.
    For example:

    # rm -rf /mnt/rtm