Table of ContentsRecent announcements for end of Operating System support
Identifying which Agents require upgrades
Obtaining a detailed list of Agents which require upgrades
Upgrade paths for specific systems
RHEL 7 / CentOS 7
Requesting support consultations
The following Operating Systems were announced as "End of Life" by their respective developers within the last year:
- Red Hat Enterprise Linux / CentOS / Oracle Linux 6x
- Red Hat Enterprise Linux / CentOS / Oracle Linux 7.1 to 7.3
- Ubuntu 14.04
End of Life agents will no longer be able to connect to our platform beginning July 1st, 2019.
ThousandEyes Appliances (both virtual and physical) and Docker agents will receive a supported upgrade path. Linux package installations require that you replace or upgrade your system with a supported Operating System in compliance with your company's standards.
You may identify which of your Agents are running on an unsupported Operating System from the Agent Settings page.To access the Agent Settings page, select Cloud & Enterprise Agents > Agent Settings within the left-hand navigation pane:
1. A red triangle (attention) icon will be located next to the name of each agent which requires attention.
2. Hovering over an agent's attention icon will display a list of items to be addressed. Agent's requiring an upgrade will display the message "Agent OS will soon be unsupported"
When communicating with your team members which agents need to be updated, the following will be useful:
3. Agent Name: This is the name used by the ThousandEyes platform and may not match the hostname of the system running the Enterprise Agent
4. Agent IP Addresses: This includes both public and private IP addresses
5. Agent Operating System: This includes both distribution and version number
6. Agent Installation Type: This may be Linux Package, Docker, Physical Appliance, or Virtual Appliance
7. Target for Tests: This may be either an IP Address or a domain name
8. Proxy Settings: An information icon will appear if your Agent is utilizing a Proxy
ThousandEyes is conducting a customer outreach program between April 1st and July 1st 2019. Organizational Administrators will be contacted, via email, and provided a list of affected agents. Requests for detailed lists should be submitted to email@example.com.
Customers who choose to install the ThousandEyes Enterprise Agent onto their own Linux system are responsible for system maintenance.
ThousandEyes has tested and documented the upgrade process for supported Linux distributions. The following information may be used as a general guideline for customers to reference when planning upgrades.
Red Hat Enterprise Linux 6.x
Red Hat has provided an upgrade path for customers who wish to update their system from RHEL 6 to RHEL 7. Please note that only 64-bit Operating Systems are supported.
ThousandEyes suggests that customers attempt an upgrade on a single RHEL 6 system prior to determining whether they should upgrade or replace their current RHEL 6 Enterprise Agents.
RHEL 7 and CentOS 7 systems may be updated to the latest version (7.6 at the time of writing) using the following command:
sudo yum update
Custom repositories should be made current prior to the upgrade.
Canonical has provided an upgrade path from Ubuntu 14.04 to Ubuntu 18.04. Please note that only 64-bit Operating Systems are supported.
ThousandEyes has provided an automated upgrade path for customers to update their Virtual Appliance. The upgrade process requires SSH access to the appliance.
ThousandEyes has provided an automated upgrade path for customers who wish to update their Physical Appliance. This upgrade process requires SSH access to the appliance.
The current Docker container is built using the base Ubuntu 18.04 container image. When a replacement Enterprise Agent container is deployed using the same volumes as the original Enterprise Agent container, the platform will not distinguish between the original and new containers.
ThousandEyes Enterprise Agents may be replaced using two different methods
Agent Clustering Method
This method consists of deploying a new agent, clustering together the new agent with the old one, and then deleting the old agent from the cluster. The act of clustering transfers test associations and Agent characteristics.
Customers using the metered billing model are not advised to use this method. This method creates a new Agent ID, and units consumed by the original Agent will not be applied to the new Agent's maximum number of billed units.
Complete instructions for replacing Enterprise Agents the Agent clustering method are available here.
Transferring Agent Identity Files
During the installation of a replacement Enterprise Agent, identity files from an existing Enterprise Agent are transferred to the replacement system. The platform will make no distinction between the original Agent and the replacement Agent.
Customers using the metered billing model are advised to use this method. This method does not create a new Agent ID, and the existing monthly unit consumption will be applied to the agent's maximum number of billed units.
Complete instructions for replacing Enterprise Agents using Agent identity files are available here.