Upgrade to Aternity on-premise 10.x

Update your Aternity on-premise from 9.x to 10 for a significant step forward in new features and resolved issues.

Always check the sizing before updating. Version 10 uses different database sizes, dashboard requirements and new servers.

Upgrade the Aternity components in the prescribed order in this procedure.

Upgrade to Aternity 10 in the correct order

Before you begin

Before upgrading Aternity on-premise:

  • You must start with a fully functioning deployment of Aternity on-premise version 9.x. If you have an older version, first upgrade to version 9.x, then continue to Aternity 10.

  • Before starting the upgrade, all devices MUST already report using a compatible version of the Aternity Agent. Learn more about deploying the Agent.

    Important

    Aternity on-premise 10 requires that devices ONLY run Aternity Agent 9.0.x, 9.1.7 or 9.2.5.

    Product Supported Aternity Agent
    Aternity 10.x

    Aternity Agent 9.0.x, 9.1.7 or 9.2.5 ONLY.

    Aternity 9.x

    Aternity Agent 9.0.x ONLY.

  • Check the correct sizing for your deployment before updating any of your Aternity servers.

  • After the upgrading to Aternity 10, all dashboards only display data from the past seven days, and two dashboards start with empty data: Application Commonalities Analysis and Validate Configuration Change.

  • If you are deploying Aternity in an air-gapped network, download the following files and packages before beginning the setup procedures.

    File Name Description Link for download

    Aternity_OnPremise_<version>_GA.zip

    Download the package that includes the setup of the following Aternity servers: Management Server, Aggregation Server, Data Warehouse Server. Vertica Database Server, Dashboard Gateway, ETL Server, Aternity REST API Server, Aternity Data Source for Portal, (For Aternity 10.0.1 only) TableauServer-9-3-22-Aternity-64bit.exe for the Aternity Dashboard Server

    Download the latest Aternity on-premise's main setup package from the Riverbed support site by selecting Software (size).

    Oracle_11.2.0.4.part1.exe, Oracle_11.2.0.4.part2.exe or Winx64_12102_database_1of2.zip, Winx64_12102_database_2of2.zip

    Download the pair of setup files for one of the supported versions of Aternity Oracle Database Server.

    Only these exact versions of Oracle to work with this version of Aternity.

    Related Links section of the Riverbed support site

    Oracle 11.2.0.4 part 1, Oracle 11.2.0.4 part 2

    (Aternity 10.0.1) Oracle 12.1.0.2 part 1, Oracle 12.1.0.2 part 2,

    OracleSilentInstall_12.1.0.2.zip, OracleSilentInstall_11.2.0.4.zip

    Download the script to use the express setup of the Aternity Oracle Database, which requires the complete Oracle setup packages.

    Related Links section of the Riverbed support site

    Silent Install 11.2.0.4, Silent Install 12.1.0.2

    (For Aternity 10.0) TableauServer-9-3-3-Aternity-64bit.exe

    The Aternity Dashboard Server uses Tableau, a third party product, as its main engine. Only this exact version of Tableau works with Aternity 10.

    Tip

    Air-gapped networks make offline Tableau setup very lengthy. You must upload and download several files in sequence as a challenge response. Tableau does not allow this in one action. We do not control their setup procedures.

    Related Links section of the Riverbed support site

    Win64OpenSSL_Light-1_0_2n.exe

    Download this patch to address an HTTPS (SSL) vulnerability required to access Aternity. Run this during a Dashboard Server fresh setup or update.

    Download from this third party site.

    Tableau's Apache server update files: vc_redist_x86.exe, httpd-2.4.27-Win32-VC15.zip, and mod_log_rotate-1.00a-win32-VC15.zip

    Download this patch to address an Apache server security issue for the Dashboard Server.

    Download from this third party site.

    .NET

    Ensure this server has Microsoft .NET 3.5 (exactly) required for the database drivers, and .NET 4.5 or later, required for driver setup (both in parallel). To add .NET to a Windows Server, learn more.

    Search for these versions on the Microsoft Download Center.

    Chrony

    Synchronizes time and time zones between the Aternity components.

    If not included in your version of CentOS, search for Chrony, and download the version for your Linux OS.

    Database template (DBT)

    (Optional) When a DBA manually deploys the Aternity Oracle Database Server, you can use a template to set default values in the setup assistant (DBCA), depending on the size of your deployment.

    Contained in the express setup of the Aternity Oracle Database (see above).

Procedure

  1. Step 1 Plan the strategy of your Aternity on-premise upgrade
    Considerations when planning your upgrade of Aternity on-premise
    • Decide on the size of your deployment, based on the number of devices to monitor. This directly determines the number of servers you need, and their hardware specifications.

      For example, if the updated requirements for your sizing state you must have a new standalone Aggregation Server, you must use the custom update to remove the legacy embedded Aggregation Server from within the Management Server, then run the setup again on a standalone server to a fresh setup of a new Aggregation Server there.

      Remove an embedded component during upgrade, then run setup on a standalone server
    • Aternity 10 requires several new servers: Vertica Database Server, Aternity ETL Server, and optionally Aternity REST API Server and Aternity Data Source for Portal.

      It also features a smaller Oracle Database Server and only one Aternity Dashboard Server.

    • Ensure you have an existing fully functional Aternity 9.x before starting your upgrade.

      All devices MUST be reporting to Aternity using Agent 9.x.

  2. Step 2 Download the latest Aternity on-premise's main setup package from the Riverbed support site by selecting Software (size).

    The setup package is for all Aternity servers.

    Download Aternity on-premise from the website

    There are also entries in the Useful Links section which are required for database setup.

  3. Step 3 (One week before upgrading Aternity) Prepare the Aternity Oracle Database Server for Aternity 10 by verifying its schema.

    Learn more.

    Aternity 10's requirements for the version of Oracle are the same as Aternity 9. Therefore it is not necessary to change the Oracle version for this upgrade. For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4.

    Important

    Always check the sizing before updating. Version 10 uses different database sizes, dashboard requirements and new servers.

    Use the Aternity Database Verification Utility to prepare for Aternity 10

    You must run the Aternity Database Verification Utility several times before and after updating the database (learn more):

    1. A week before updating, run the Aternity Database Verification Utility from the Aternity Management Server to find any issues with the existing database.

      Tip

      We strongly advise you to submit this report to Customer Services to confirm your database is ready for the update.

      Fix all the flagged items listed in the reports by updating the settings in your legacy Aternity or by asking a DBA to change the database directly.

    2. Run the utility a second time before updating, to check there are no more actionable changes.

    3. (Optional, only if you change Oracle versions) Ask your DBA to update Oracle. For Aternity 10.x, use Oracle 12.1.0.2 or 11.2.0.4

      You can download either version of Oracle from the Related Links of the Riverbed support site.

    4. (Optional, only if you change Oracle versions) Run the utility again to check if there are issues with the updated database.

      Implement the required fixes. To resolve an issue from within Aternity's settings, you must first complete all the server updates, then implement those fixes.

    Learn more.

  4. Step 4 (Updating to Aternity 10.0) Set up a single new Aternity Vertica Database Server or a cluster of Vertica Database Servers.

    (Updating from Aternity 10.0 to 10.0.1) You must update to Vertica 8.1.1. Learn more.

    The Aternity Vertica Database Server stores the performance data from the past 31 days in the Vertica format, which is most efficient for displaying in Aternity dashboards. It receives its data from the Aternity ETL Server, which translates performance data from the Aternity Oracle Database Server to this server.

  5. Step 5 Update the Dashboard Server by removing the previous version of Tableau and then running the setup of the new version.

    The Dashboard Server displays Aternity's intuitive dashboards using Tableau as its engine.

    Update the Dashboard Server component (Tableau Server)
  6. Step 6 On the Dashboard Server, update the Dashboard Gateway component.

    The Dashboard Gateway acts as the interface between the Dashboard Server and the Aternity Management Server, performing background tasks like preprocessing the data for display in the dashboards, and maintaining logs, audits and cleanup. It must be on the same computer as the Dashboard Server. While it has no user interface of its own, it is crucial to the proper functioning of Aternity.

    Update the Dashboard Gateway on the same computer as the Dashboard Server
  7. Step 7 Update the Aternity Management Server by running its express setup or custom setup over the previous version.

    To setup the Aternity Management Server, you must register with Aternity's online activation form. Enter your contact details and serial number to send an activation key to your email (learn more).

    If you previously had several Aternity components on this server, recheck the sizing, as you may need to create new standalone servers and remove legacy embedded components in this server.

    • If you keep the same topology or security, choose the express update, which keeps your legacy settings in the updated servers.

    • If you are changing your topology or security, choose the custom update.

    Remove an embedded component during upgrade, then run setup on a standalone server

    For example, if the updated requirements for your sizing state you must have a new standalone Aggregation Server, you must use the custom update to remove the legacy embedded Aggregation Server from within the Management Server, then run the setup again on a standalone server to a fresh setup of a new Aggregation Server there.

    Use the updated sizing to determine whether a component is embedded or standalone
  8. Step 8 Update the Aternity dashboard layouts from the Management Server.

    The Aternity dashboard layouts contain the names, calculations and layouts of the system's dashboards for this Aternity version.

    Important

    Add the dashboard layouts ONLY from the Management Server.

    Add the layouts from the Management Server into the Dashboard Server via Dashboard Gateway
  9. Step 9 Access Aternity 10 to add your new serial number and purchased licenses.
    Enter your new serial number and license volume

    Select the Gear Icon > License Provisioning > Edit Licenses.

    If it displays an existing serial number, select it. Otherwise select Add License. Enter your new number and license volume.

  10. Step 10 (For deployments above 20,000 devices only) Run the express update or the custom update of a standalone Data Warehouse Server on its own computer, or create a new one.

    The Data Warehouse Server stores the raw data gathered from the Aggregation Servers, and aggregates (summarizes) it for the Oracle Database Server.

  11. Step 11 (For deployments above 5,000 devices only) Run the express update or the custom update of a standalone Aggregation Server on its own computer, or create a new one.

    As your deployment grows in size, add more identical Aggregation Servers (see deployment sizing for details). If your sizing requires that you deploy more than one dedicated Aternity Aggregation Server, you must deploy a third party load balancer (LB). Then configure the Aternity Agent of all devices to point to the LB's virtual IP address (learn more). Configure the LB with persistent (sticky) sessions to ensure the Agent maintains its connection with the same server. Aternity also supports sticky sessions also when the LB implements stickiness via cookies.

    Aggregation Server collects and consolidates data from monitored devices
  12. Step 12 On a separate computer, set up a new Aternity ETL Server.

    The Aternity ETL Server is a component of Aternity on-premise, which aggregates and converts performance data from the Aternity Oracle Database Server to the Vertica database format, and sends it to the Vertica Database Server.

  13. Step 13 (Optional) To retrieve Aternity data via REST API, set up a new Aternity REST API Server.

    The Aternity REST API Server is a component in Aternity on-premise which allows authorized users to send REST API queries to directly extract and analyze Aternity's data without accessing Aternity's dashboards. You can combine the data with other data sources if needed, or transform it as required, then view it in Microsoft Excel, Power BI, or your own data application.

  14. Step 14 (Optional) To view Aternity data in SteelCentral Portalâ„¢, set up a new Aternity Data Source for Portal.

    The Aternity Data Source for Portal provides Aternity data to the SteelCentral Portalâ„¢, so you can view end-user experience data in its dashboards. You can configure the Portal to connect to your Aternity Data Source.

    Once it is set up, you can connect the Aternity Data Source to Portal

  15. Step 15 Check that the system's monitor tree is valid for Aternity 10, by selecting the Gear Icon > Monitors Compatibility Tester.

    It creates a report listing the issues it found, organized like the Monitors Settings window, by application name. For details, see Validate Changes to the Monitors Settings (Monitor Tree Compatibility Tester).

    Validate the monitors in the system
  16. Step 16 Browse the Aternity dashboards.
    Tip

    Immediately after an upgrade, the dashboards initially appear empty and take time to fill with data, initially from the past seven days, and then increasingly updated as new data flows in from devices.