Red Hat Enterprise Linux 7 (RHEL 7) is the first major release of RHEL to allow in-place upgrades from the previous major RHEL release (RHEL 6). An in-place upgrade offers a way of upgrading a system to a new major release of RHEL by replacing the existing operating system. The following guide will lead you through the process of upgrading package-based Enterprise Agent's underlying RHEL 6 operating system to RHEL version 7.
This guide is based on Red Hat's How do I upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7? guide. Before proceeding any further, make sure that you have read the aforementioned guide.
ThousandEyes followed the above Red Hat guide and successfully performed the Enterprise Agent upgrade. At the time of the upgrade, a ThousandEyes Enterprise Agent installed on RHEL 6.10 x86_64 Server Edition Virtual Machine (VMware) was upgraded to RHEL 7.6 x86_64 Server Edition.
Depending on your Enterprise Agent's hardware performance, the whole process could take more or less than an hour; plan your maintenance window accordingly. Your Enterprise Agent won't perform any tests during the upgrade.
Depending on your Enterprise Agent's software custom configurations, additional steps may be required to restore those custom configurations. Carefully analyze the generated preupgrade report. The following guide assumes that no custom configurations took place on your Enterprise Agent's Operating System.
Upgrading from RHEL 6 Server Edition to RHEL 7 Server Edition is supported for x86_64 architecture (64 bit), but not for x86 architecture (32 bit). The support is assured by your contract with Redhat, not by ThousandEyes. If your Enterprise Agent is running RHEL 6 x86 architecture, you should consider replacing it with a clean installation of RHEL 7 Server Edition x86_64 architecture.
Red Hat states that only KVM and VMWare virtualization platforms are supported for in-place upgrades. Hyper-V is an example of an unsupported platform.
All the commands below should be run as root. To reduce the content repetition, all "sudo" command prefixes have been removed and the whole guide assumes that you are running each command in a root shell.
To reach the root shell, use the following command:
$ sudo -s
If you have the possibility of creating a backup snapshot of your virtual machine, we encourage you to do so. This will enable you to revert to the known-good state in case the upgrade does not go as smoothly as anticipated.
# subscription-manager register --username <username> --auto-attach# subscription-manager repos --enable rhel-6-server-extras-rpms# subscription-manager repos --enable rhel-6-server-optional-rpms
# yum update -y# reboot
# yum -y install preupgrade-assistant preupgrade-assistant-ui preupgrade-assistant-el6toel7 redhat-upgrade-tool
This report will point out possible upgrade contention points. Evaluate whether it is safe to continue with the upgrade process.
# semodule -r sandbox
The following step assumes a (virtual) CD/DVD Media rhel-server-7.6-x86_64-dvd.iso is inserted into the VM's virtual CD/DVD drive from hypervisor's VM Settings.
Other installation sources are supported as well - the following command line options are applicable in the next step:
"--device [DEV]"- Device or mount point. default: check mounted devices
"--iso [FILE.iso]"- Installation image file
"--network VERSION"- Online repos matching VERSION. Example: --network 7.6 --instrepo=https://myinternalwebserver.com/rhel7repo/ --cleanup-post
# redhat-upgrade-tool --device /dev/sr0 --cleanup-post# reboot
You may connect to the VM console and observe the output of the upgrade process - wait for its completion.
A few additional tasks need to be taken care of in order to ensure smooth agent operation.
# subscription-manager repos --enable rhel-7-server-optional-rpms
If the BrowserBot component was previously not installed or is not needed, don't use the "-b" switch in the following command.
Use the same account group token as found in the /etc/te-agent.cfg file.
# curl -Os https://downloads.thousandeyes.com/agent/install_thousandeyes.sh# bash install_thousandeyes.sh -b <ACCOUNT_GROUP_TOKEN># yum reinstall te-agent -y# systemctl start te-agent
If the "-b" switch was used to install the BrowserBot component in the step above, enable the te-browserbot service. The upgrade process does not handle this task transparently.
# systemctl enable te-browserbot
If you skip this step, the BrowserBot service will not start automatically on the next reboot.
If you had previously installed the ntpd service, make sure the service is enabled and started. If you didn't have the ntpd service installed before the upgrade, we recommend you install it by running the following command:
yum install ntp.
# systemctl enable ntpd# systemctl start ntpd
The major version upgrade may not have upgraded your operating system to the latest point release. It is recommended to follow Red Hat's point releases.
# yum update -y# reboot
If the report generated by the pre-upgrade tool identified any potential issues, now is a good time to resolve them.
When the upgrade does not seem to be going as planned, the following suggestions outline basic troubleshooting activities. If you cannot figure out what is causing the issue, reach out to firstname.lastname@example.org and we'll help you out.
The first thing to do if the agent software installation fails is the inspection of the installation logs. Use the following command to do so:
# cat /tmp/install_thousandeyes*.log
Inspect the agent logs with the following command:
# tail -f /var/log/te-agent.log
Are you subscribed to Red Hat? Is your subscription valid?
Check your subscription with the following command:
# subscription-manager list
The following resources provide related information:
Enterprise Agent support lifecycle policy Knowledge Base article explains when to expect end-of-support events for each supported operating system.