Back to ITRS Internal Only FAQ

Internal documentation only

This page has been marked as draft.

Step-by-step guide to upgrade OP5 Monitor 7.5.x to 9.x

Assumptions Copied

Upgrade Path Copied

There are two paths to migrating from OP5 7.x on EL6 to OP5 9.x on EL8:

  1. Option 1
    1. Upgrade OP5 7.5.x on EL6 to OP5 7.5.13 and take a migration backup.
    2. Procure an EL7 server and install OP5 7.5.13 then restore the migration backup.
    3. Upgrade OP5 7.5.13 on EL7 to 8.x. Upgrade to 8.3.8 (or higher) then take a migration backup.
    4. Procure an EL8 server and install OP5 9.x then restore the migration backup.
  2. Option 2
    1. Upgrade OP5 7.5.x on EL6 to OP5 7.5.13.
    2. Upgrade OP5 7.5.13 on EL6 to OP5 8.1.0 on EL6 then take a migration backup.
    3. Procure an EL7 server and install OP5 8.1.0 then restore the migration backup.
    4. Upgrade the OP5 8.1.0 on EL7 to 8.3.8 (or higher) then take a migration backup.
    5. Procure an EL8 server and install OP5 9.x then restore the migration backup.

The examples in this guide show the steps for Option 2.

Upgrading OP5 version 7.5.x on EL6 to version 7.5.13 on EL6 Copied

Check current version of OP5 Copied

The current version of OP5 is 7.5.1 running on CentOS 6.10.

[root@op5-el6 ~]# cat /etc/*release*
CentOS release 6.10 (Final)
VERSION=7.5.1
VERSION=2018.g.2-op5.1.20180711120010.el6
CentOS release 6.10 (Final)
CentOS release 6.10 (Final)
cpe:/o:centos:linux:6:GA

The last release for the 7.5.x branch is version 7.5.13.

Check repositories Copied

Check that the OP5 repositories on your environment are valid. Refer to this article for changes to the OP5 repositories.

Verify that you have an available CentOS 6 repository. An alternate repository can be used if no local mirror is available. Refer to details on this article but do so at your own risk.

Disable any op5-epel repositories as these are no longer maintained. There is no real reason to use this anymore as most of the EPEL packages are managed and maintained through the official epel repository.

Disable the op5-epel repository by editing the /etc/yum.repos.d/op5-release.repo file and verify that it has been disabled:

[root@op5-el6 ~]# grep "op5-epel" -A3 /etc/yum.repos.d/op5-release.repo
[op5-epel]
name=op5 EPEL
baseurl=http://repos.op5.com/epel/6/$basearch
enabled=0

Install the official epel-release:

[root@op5-el6 yum.repos.d]# yum install epel-release
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror, security
Setting up Install Process
[...] 1/1
Installed:
epel-release.noarch 0:6-8

Complete!

Verify that the official epel is enabled through yum repolist:

[root@op5-el6 ~]# yum repolist epel
Loaded plugins: fastestmirror, security
Loading mirror speeds from cached hostfile
- epel: d2lzkl7pfhq30w.cloudfront.net
repo id                   repo name                                                  status
epel                      Extra Packages for Enterprise Linux 6 - x86_64             12581

Run the update Copied

[root@op5-el6 yum.repos.d]# yum update
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
- epel: ftp.iij.ad.jp
Resolving Dependencies
--> Running transaction check
[...]
vim-filesystem.x86_64 2:7.4.629-5.el6_10.2
vim-minimal.x86_64 2:7.4.629-5.el6_10.2

Complete!

To run the update and ensure that op5-epel will not be used, an alternate command can be run instead: yum --disablerepo="op5-epel" update.

Verify that 7.5.13 is installed Copied

[root@op5-el6 yum.repos.d]# cat /etc/*release*
CentOS release 6.10 (Final)
VERSION=7.5.13
CentOS release 6.10 (Final)
CentOS release 6.10 (Final)
cpe:/o:centos:linux:6:GA

OP5 Monitor 7.5.13 is now running on EL6.

Upgrading OP5 version 7.5.13 on EL6 to version 8.1.0 on EL6 Copied

Check current version of OP5 Copied

The current version of OP5 is 7.5.13 running on CentOS 6.10.

[root@op5-el6 yum.repos.d]# cat /etc/*release*
CentOS release 6.10 (Final)
VERSION=7.5.13
CentOS release 6.10 (Final)
CentOS release 6.10 (Final)
cpe:/o:centos:linux:6:GA

Check repositories Copied

The op5-epel repository may have been enabled again after upgrading OP5 to 7.5.13. Check that it is disabled and disable it if it is enabled.

[root@op5-el6 yum.repos.d]# grep "op5-epel" -A3 /etc/yum.repos.d/op5-release.repo
[op5-epel]
name=op5 EPEL
baseurl=http://repos.op5.com/epel/6/$basearch
enabled=0

Install 7-to-8 update Copied

[root@op5-el6 ~]# yum install op5-release-up-7-to-8
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror, security
Setting up Install Process
Loading mirror speeds from cached hostfile
- epel: archivefedora.mirror.angkasa.id
[...]
Installing : op5-release-up-7-to-8-2018.y.2-op5.1.20200506230519.el6.noarch 1/1
Verifying : op5-release-up-7-to-8-2018.y.2-op5.1.20200506230519.el6.noarch 1/1

Installed:
op5-release-up-7-to-8.noarch 0:2018.y.2-op5.1.20200506230519.el6

Complete!

Run the update to version 8 Copied

[root@op5-el6 ~]# yum --enablerepo='*7-to-8*' update
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror, security
Setting up Update Process
Loading mirror speeds from cached hostfile
- epel: archivefedora.mirror.angkasa.id
op5-monitor-up-7-to-8-updates                                   |                    3.6 kB 00:00
[...]
portal.noarch 0:2019.j.1-op5.1.20191101165758.el6
smsacknowledge.noarch 0:2018.e.1-op5.1.20200203030253.el6
smspassivecheck.noarch 0:2015.g.1-op5.1.20200203025812.el6
smsreceiver.noarch 0:2019.h.1-op5.1.20200203030750.el6

Replaced:
op5-release-up-7-to-8.noarch 0:2018.y.2-op5.1.20200506230519.el6

Complete!

This will have updated OP5 to the latest 8.x version available on EL6, which is 8.1.0.

Verify that 8.1.0 is installed Copied

[root@op5-el6 ~]# cat /etc/*release*
CentOS release 6.10 (Final)
VERSION=8.1.0
VERSION=2019.a.2-op5.1.20190130130201.el6
CentOS release 6.10 (Final)
CentOS release 6.10 (Final)
cpe:/o:centos:linux:6:GA

OP5 Monitor 8.1.0 is now running on EL6.

Migrating OP5 version 8.1.0 on EL6 to version 8.1.0 on EL7 Copied

At this point, the EL7 server must have already been prepared and ready for use and already have OP5 Monitor version 8.1.0 installed. If the installer for this is needed, please contact ITRS Support.

On the EL6 server Copied

Run the migration backup Copied

[root@op5-el6 ~]# op5-backup -g
2023-02-02 10:05:48 INFO - Backup job started
2023-02-02 10:05:48 INFO - Found CentOS 6.10 operating system
2023-02-02 10:05:48 INFO - Migrating in default mode
2023-02-02 10:05:48 INFO - Preparing the working directory /var/lib/op5-backup/20230202-100548
2023-02-02 10:05:48 INFO - Starting detecting modules
2023-02-02 10:05:48 INFO - Detected the following modules: dokuwiki migrate nagios-plugins op5-geomap op5-logger-2020.a.2-op5.1.20200203015731.el6.x86_64 op5-logger op5-monitor op5-notify op5-synergy op5-system op5-trapper ssh
2023-02-02 10:05:48 INFO - Executing the backup job
[...]
2023-02-02 10:05:52 INFO - Moving the backup file to /root/
2023-02-02 10:05:52 INFO - Backup file moved to /root/
2023-02-02 10:05:52 INFO - Removing workdir: /var/lib/op5-backup/20230202-100548
2023-02-02 10:05:52 INFO - Backup was successfully created
[root@op5-el6 ~]# ls -l /root/migration_backup*
-rw-r----- 1 root root 3031040 Feb 2 10:05 /root/migration_backup.op5-el6.2023-02-02.backup

Verify that there are no errors from running the backup and that the backup is not empty

[root@op5-el6 ~]# grep -i error /var/log/op5-backup/*
[root@op5-el6 ~]# tar tvf migration_backup.op5-el6.2023-02-02.backup
-rw-r----- root/root 231883 2023-02-02 10:05 dokuwiki.tar.gz
-rw-r----- root/root 554373 2023-02-02 10:05 migrate.tar.gz
-rw-r----- root/root 310594 2023-02-02 10:05 nagios-plugins.tar.gz
-rw-r----- root/root 682 2023-02-02 10:05 op5-geomap.tar.gz
-rw-r----- root/root 3252 2023-02-02 10:05 op5-logger.tar.gz
-rw-r----- root/root 1669864 2023-02-02 10:05 op5-monitor.tar.gz
-rw-r----- root/root 142 2023-02-02 10:05 op5-notify.tar.gz
-rw-r----- root/root 892 2023-02-02 10:05 op5-synergy.tar.gz
-rw-r----- root/root 216367 2023-02-02 10:05 op5-system.tar.gz
-rw-r----- root/root 2584 2023-02-02 10:05 op5-trapper.tar.gz
-rw-r----- root/root 138 2023-02-02 10:05 ssh.tar.gz
-rw-r--r-- root/root 4 2023-02-02 10:05 version
-rw-r--r-- root/root 16 2023-02-02 10:05 timestamp
-rw-r--r-- root/root 7 2023-02-02 10:05 architecture
-rw-r--r-- root/root 6 2023-02-02 10:05 monitor_version
-rw-r--r-- root/root 8 2023-02-02 10:05 mode
-rw-r--r-- root/root 7 2023-02-02 10:05 archive
drw-r----- root/root 0 2023-02-02 10:05 modules/
-rw-r--r-- root/root 141 2023-02-02 10:05 modules/op5-notify
-rw-r--r-- root/root 234 2023-02-02 10:05 modules/nagios-plugins
-rw-r--r-- root/root 6152 2023-02-02 10:05 modules/migrate
-rw-r--r-- root/root 399 2023-02-02 10:05 modules/op5-trapper
-rw-r--r-- root/root 4097 2023-02-02 10:05 modules/op5-monitor
-rw-r--r-- root/root 193 2023-02-02 10:05 modules/op5-synergy
-rw-r--r-- root/root 641 2023-02-02 10:05 modules/dokuwiki
-rw-r--r-- root/root 116 2023-02-02 10:05 modules/ssh
-rw-r--r-- root/root 147 2023-02-02 10:05 modules/op5-geomap
-rw-r--r-- root/root 793 2023-02-02 10:05 modules/op5-system
-rw-r--r-- root/root 1024 2023-02-02 10:05 modules/op5-logger
-rw-r--r-- root/root 20 2023-02-02 10:05 backup_workdir

Transfer the migration backup from EL6 to EL7 server Copied

This can be done through various methods (WinSCP, FileZilla, etc). In this example, rsync was used.

[root@op5-el6 ~]# rsync -a /root/migration_backup.op5-el6.2023-02-02.backup 192.168.36.224:/root/migration_backup.op5-el6.2023-02-02.backup

On the EL7 server Copied

Verify that OP5 version 8.1.0 has been installed Copied

[root@op5-el7 ~]# cat /etc/*release*
CentOS Linux release 7.5.1804 (Core)
Derived from Red Hat Enterprise Linux 7.5 (Source)
VERSION=8.1.0
VERSION=2019.a.2-op5.1.20190130130201.el7
NAME="CentOS Linux"
VERSION="7 (Core)"
ID="centos"
ID_LIKE="rhel fedora"
VERSION_ID="7"
PRETTY_NAME="CentOS Linux 7 (Core)"
ANSI_COLOR="0;31"
CPE_NAME="cpe:/o:centos:centos:7"
HOME_URL="https://www.centos.org/"
BUG_REPORT_URL="https://bugs.centos.org/"

CENTOS_MANTISBT_PROJECT="CentOS-7"
CENTOS_MANTISBT_PROJECT_VERSION="7"
REDHAT_SUPPORT_PRODUCT="centos"
REDHAT_SUPPORT_PRODUCT_VERSION="7"

CentOS Linux release 7.5.1804 (Core)
CentOS Linux release 7.5.1804 (Core)
cpe:/o:centos:centos:7

Check repositories Copied

The op5-epel repository may have been enabled again after upgrading OP5 to 7.5.13. Check that it is disabled and disable it if it is enabled.

[root@op5-el6 yum.repos.d]# grep "op5-epel" -A3 /etc/yum.repos.d/op5-release.repo
[op5-epel]
name=op5 EPEL
baseurl=http://repos.op5.com/epel/6/$basearch
enabled=0

Restore the migration backup file Copied

An interactive session may appear asking about network settings and running in the background.

[root@op5-el7 ~]# op5-restore -b migration_backup.op5-el6.2023-02-02.backup
2023-02-02 10:17:57 INFO - Starting the restore job
2023-02-02 10:17:57 INFO - The following 11 modules has been detected: dokuwiki migrate nagios-plugins op5-geomap op5-logger op5-monitor op5-notify op5-synergy op5-system op5-trapper ssh
2023-02-02 10:17:57 INFO - Creating temporary modules directory: /var/lib/op5-backup/modules
[...]
2023-02-02 10:18:58 INFO - restored files for these packages:
2023-02-02 10:18:59 INFO - Restore successfully completed
2023-02-02 10:18:59 INFO - Removing temporary workdir: /var/lib/op5-backup/20230202-100548

Backup log file can be found here: /var/log/op5-backup/restore-20230202-100548.log

Remember to reboot the server

Verify that there were no errors in the restore log

[root@op5-el7 ~]# grep error /var/log/op5-backup/restore-20230202-100548.log
[root@op5-el7 ~]#

Reboot the server.

OP5 Monitor 8.1.0 is now running on EL7

Upgrading OP5 version 8.1.0 on EL7 to version 8.4.x on EL7 Copied

Migrating version 8.4.x on EL7 to version 9.x on EL8 Copied

Your Answer here Copied

  1. Make sure title does not finish with a question mark (if you come across any FAQ that doesn’t meet the guideline correct it)
  2. Please include pictures and attach xml setup if possible.
  3. If you are linking to a documentation link, make sure you replace the version with “current” i.e.: https://docs.itrsgroup.com/docs/geneos/5.10.0/index.html , replace 5.10.0 with “current”. This will make sure the url is linked to latest documentation.
  4. On the right side panel, make sure you select the correct visibility to the intended audience (Agents and Managers if ITRS and Everyone if is to be client facing).
  5. On the right side panel, make sure you create the article for the appropriate section of Product and Sub-Category (Please, remember to place FAQ’s that are ONLY for CS in the ‘ITRS internal only’).
  6. On the right side panel, make sure you leave the ‘open for comments’ ticked.
  7. On the right side panel, make sure you set yourself as ‘owner’ of the article.
  8. Make sure you enter keywords labels as the words the client might use to search and find the article
  9. Make sure you get a peer review before publishing it.
  10. For each new FAQ created (ALL PRODUCTS) create TCP > Documentation issue in JIRA.
    • for the new FAQ, use the TCP > Documentation project type.
    • Select FAQ on the Documentation Type menu.
    • Assign it to the Tech Comms Team group.
    • use the FAQ title as the JIRA and provide a link to the FAQ in the comment of the JIRA
["Geneos"] ["FAQ"]

Was this topic helpful?