Plan the Upgrade or Migration

The path that you take for your upgrade or migration depends on various factors.
The path that you take for your upgrade or migration depends on various factors. Use the following sections to plan your upgrade:
For cloud environments, see Rehydrating Data in a Cloud Environment.
Verify ETL Health
Before you upgrade, run the
etlHealth.sh
script. Run this script well in advance of the upgrade and again directly before the upgrade. For
DX NetOps Performance Management
20.2.3 and higher, the script is included with the data repository installation. For earlier releases, contact Support.
Follow these steps:
  1. Log in to one of the data repository nodes as the root user.
  2. Run the validation script by issuing the following command:
    ./etlHealth.sh
    dauser
    dapassword
  3. Do one of the following:
    • If the health check passes, proceed with the upgrade.
    • If the health check fails, follow the instructions in the prompt to collect the irep and the data collected by the
      etlHealth.sh
      script, and submit these details in a Support ticket.
The ETL health is verified.
Plan the
DX NetOps Performance Management
Upgrade
Because the data repository in
DX NetOps Performance Management
20.2 and higher runs Vertica release 9.1, you can upgrade the data repository only from the following
DX NetOps Performance Management
releases to
DX NetOps Performance Management
20.2:
  • DX NetOps Performance Management
    3.6
  • DX NetOps Performance Management
    3.7
If you are upgrading from
DX NetOps Performance Management
3.2 and earlier, you must upgrade to
DX NetOps Performance Management
3.6
before
upgrading the data repository to
DX NetOps Performance Management
20.2.
For other
DX NetOps Performance Management
components, you can upgrade from the following
DX NetOps Performance Management
releases to
DX NetOps Performance Management
20.2:
  • DX NetOps Performance Management
    3.2
  • DX NetOps Performance Management
    3.5
  • DX NetOps Performance Management
    3.6
  • DX NetOps Performance Management
    3.7
The following table describes the best upgrade paths for indirect upgrades to
DX NetOps Performance Management
20.2:
For information about previous releases, see the previous documentation using the
Versions
drop-down. For assistance locating documentation for releases earlier than
DX NetOps Performance Management
3.1, contact your Support representative.
Current Version
Upgrade Path
3.2
3.5 to 3.6 to 20.2 (data repository)
20.2 (other components)
3.5
3.6 to 20.2 (data repository)
20.2 (other components)
Plan the Operating System Upgrade or Install
For more information about the operating systems that are required and Red Hat Enterprise Linux (RHEL) versions that were verified, see Upgrade Requirements and Considerations.
To plan your operating system (OS) upgrade and understand your upgrade scenario, review the following details and answer the following questions:
The following numbered questions correlate to the numbered decision steps in the following flowchart.
  1. If you have not yet, review the Upgrade Requirements and Considerations.
  2. Are you going to perform an OS installation (for example, going from RHEL 6.9 to RHEL 7.5 or SLES 12 SP2)?
    1. Is your current OS RHEL 5.x?
    2. Are you going to move to new hosts?
    3. Is RHEL 7.x, SLES, or OL the desired OS?
  3. Are you going to perform a minor OS upgrade (for example, RHEL 6.5 to RHEL 6.9)?
The following OS upgrade and install scenarios upgrade or install the OS for all components. However, your unique scenario might upgrade or install the OS for a select set of components.
Upgrade Scenarios
Review the following graphic to help identify your upgrade scenario. Then use the procedures that are outlined in the following sections. The following graphic provides a high-level overview of some common upgrade scenarios:
Plan_Upgrade
Plan_Upgrade
Upgrade
DX NetOps Performance Management
without an Operating System Upgrade
If this version of
DX NetOps Performance Management
supports your current OS, you can upgrade each component using its supported upgrade path.
For more information, see Upgrading.
Upgrade
DX NetOps Performance Management
with a Minor OS Upgrade
If you are performing a minor OS upgrade (for example, RHEL 6.5 to RHEL 6.9), do the following tasks:
  1. Upgrade your OS.
  2. Upgrade each component using its supported upgrade path.
    For more information, see Upgrading.
Migrate to New Hosts from a Supported Operating System
Migration involves moving the
DX NetOps Performance Management
components, including configurations, customizations, and data, from one system to another system.
The following situations require migration:
  • You are moving to new hosts for an OS install (for example, RHEL 6.9 to RHEL 7.5 or SLES 12 SP2).
  • The current database hardware no longer meets sizing requirements.
  • You are moving from virtual machines to physical hardware for the database.
If you are moving
DX NetOps Performance Management
components to new systems with new IP addresses and hostnames from a supported OS, use the following process:
  1. Upgrade each component using its supported upgrade path.
    For more information, see Upgrading.
    You must upgrade the existing system to the product version to which you are migrating before migrating.
  2. Depending on the amount of data, migrating the data repository can take a significant amount of time.
    To minimize downtime, perform incremental backups after your initial backup.
  3. This migration procedure copies over
    NetOps Portal
    and does not require you to install
    NetOps Portal
    on the new host.
  4. Update the Data Collector.
    1. For
      DX NetOps Mediation Manager
      , see the CAMM documentation.
    2. For
      DX NetOps Virtual Network Assurance
      , see the CA VNA documentation.
Migrate to New Hosts from an Unsupported OS
RHEL 6.x is required.
If you are moving
DX NetOps Performance Management
components to new systems with new IP addresses and hostnames from an unsupported OS, use the following process:
  1. Upgrade each component using its supported upgrade path until you reach a version from which you can upgrade directly to
    DX NetOps Performance Management
    20.2.
    For more information, see the Upgrading documentation for the version from which you are upgrading.
  2. Back up each component to another server:
    1. Back Up the Data Repository.
      Depending on the amount of data, backing up and restoring the data repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Install the OS on each host.
  4. Install the same product version from your recent upgrade on each host. For more information, see the Installing documentation for the recommended version.
  5. Restore each component:
    For each component, verify that the backup is copied over.
  6. Upgrade each component to this product version. For more information, see Upgrading.
  7. Migrate the Data Repository.
    Depending on the amount of data, migrating the data repository can take a significant amount of time.
    To minimize downtime, perform incremental backups after your initial backup.
  8. Migrate
    NetOps Portal
    .
    Migrating
    NetOps Portal
    copies over
    NetOps Portal
    and does not require you to install
    NetOps Portal
    on the new host.
  9. Update the Data Collector.
    1. For
      DX NetOps Mediation Manager
      , see the
      DX NetOps Mediation Manager
      documentation
      .
    2. For
      DX NetOps Virtual Network Assurance
      , see the
      DX NetOps Virtual Network Assurance
      documentation
      .
Perform an Operating System Installation from a Supported Operating System
If you are performing a major OS upgrade from a supported OS (for example, RHEL 6.9 to RHEL 7.5 or SLES 12 SP2) on the same systems with the same IP addresses and hostnames, use the following procedures:
  1. Upgrade each component using its supported upgrade path.
    For more information, see Upgrading.
    You must upgrade the existing system to the product version to which you are backing up and restoring before backing up and restoring.
  2. Back up each component to another server:
    1. Back Up the Data Repository.
      Depending on the amount of data, backing up and restoring the data repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Update the Data Collector.
    1. For
      DX NetOps Mediation Manager
      , see the
      DX NetOps Mediation Manager
      documentation
      .
    2. For
      DX NetOps Virtual Network Assurance
      , see the
      DX NetOps Virtual Network Assurance
      documentation
      .
  4. Install the OS on each host.
  5. Install this product version on each host. For more information, see Installing.
  6. Restore each component:
    For each component, verify that the backup is copied over.
Perform an OS Installation from an Unsupported OS
If your current OS is RHEL 5.x, you must first move to RHEL 6.x.
If you are performing a major OS upgrade from an unsupported OS (for example, RHEL 5.x to RHEL 6.9) on the same systems with the same IP addresses and hostnames, use the following procedures:
  1. Upgrade each component using its supported upgrade path until you reach a version from which you can upgrade directly to 20.2. For more information, see the Upgrading documentation for the version from which you are upgrading.
  2. Back up each component to another server:
    1. Back Up the Data Repository.
      Depending on the amount of data, backing up and restoring the data repository can take a significant amount of time.
      To minimize downtime, perform incremental backups after your initial backup.
  3. Update the Data Collector.
    1. For
      DX NetOps Mediation Manager
      , see the
      DX NetOps Mediation Manager
      documentation
      .
    2. For
      DX NetOps Virtual Network Assurance
      , see the
      DX NetOps Virtual Network Assurance
      documentation
      .
  4. Install the OS on each host.
  5. Install the same product version from your recent upgrade on each host. For more information, see the Installing documentation for the recommended version.
  6. Restore each component:
    For each component, verify that the backup is copied over.
  7. Upgrade each component to this product version. For more information, see Upgrading.