Upgrade the Data Collectors

Upgrade the data collectors after you have upgraded the data aggregator.
Upgrade the data collectors after you have upgraded the data aggregator. Upgrading the data collectors upgrades them to the version of the data aggregator. The data collectors continue to run during upgrades and cache polled data to disk. When the data repository and data aggregator upgrade completes, the data collectors load the cached data. The upgrade process upgrades the data collectors at once through a staged process where up to two data collectors upgrade in parallel.
NetOps Portal
indicates that an upgrade is required only for major releases. For a minor incremental upgrade (for example, a monthly update), you can choose to upgrade to the latest release.
If you have installed a low-scale system, the configuration of installing this system does not persist through upgrades. Upgrade and configure the data collector according to the procedures described in Install the Data Collector on the Same Host as the Data Aggregator.
The method that you use to upgrade the data collectors depends on how you plan to run the upgrade:
  • As a non-root user (using
    NetOps Portal
    )
    .
    Use this method to upgrade the data collectors with a minimal reporting gap. During this upgrade process, the data collector service is down until the upgrade completes. The upgraded data aggregator (
    DX NetOps Performance Management
    3.5 or higher) continues to communicate with the previous versions of your data collectors (
    DX NetOps Performance Management
    3.5 or higher) as they upgrade.
  • As a root user or as a user with the necessary sudo privileges (manual method).
    Use this method to upgrade in the following cases:
    • You are upgrading from
      DX NetOps Performance Management
      3.5 as a non-root user.
    • You are upgrading from
      DX NetOps Performance Management
      3.2 or lower.
    • A pseudo tenant proxy is assigned to the data collectors. This method prevents the data collectors from hanging with an "Upgrade Pending" status, prevents them from continuing to collect data as normal, and prevents the other data collectors from continuing to upgrade.
      For more information, see Tenant-Agnostic Data Collectors.
Run the Upgrade as a Non-Root User
Upgrade the data collectors as a non-root user using the following process:
Verify the Prerequisites for an Upgrade as a Non-Root User
Before you upgrade the data collectors using this method, ensure that you have completed the following prerequisite steps:
  • You have assigned a Tenant and IP Domain to each data collector that you want to upgrade.
  • If you have authenticated and encrypted ActiveMQ communication, you have regenerated the keys and established trust.
    For more information, see Authenticate and Encrypt ActiveMQ Communication.
Upgrade as a Non-Root User
Follow these steps:
  1. Locate the
    /etc/sudoers
    file on the data collector host.
  2. Add the following command alias with the following permissions to the file by issuing the following command:
    dcuser dchostname
    = (root) NOPASSWD:
    <DC_installation_directory>
    /upgrade/install.bin
    If the
    requiretty
    parameter is enabled, disable it for the data collector installer by adding the following text:
    Defaults!<
    DC_installation_directory>
    /upgrade/install.bin !requiretty
  3. Log in to
    NetOps Portal
    as the global administrator.
  4. Hover over
    Administration
    ,
    Monitored Items Management
    , and then click
    Data Collectors
    .
    The
    Data Collectors
    page appears.
  5. Select the data collectors that you want to upgrade, and then click
    Upgrade
    .
    The
    Upgrade Data Collectors
    dialog opens.
  6. To proceed with the upgrade, click
    Yes
    .
    You can view the status of the upgrade in the
    Overall Status
    column.
The data collector is upgraded.
Run the Upgrade as a Root or Sudo User
Upgrade the data collectors manually as a root user or as a user with the necessary sudo privileges using the following process:
Verify the Prerequisites for an Upgrade as a Root or Sudo User
Before you upgrade the data collectors using this method, ensure that you have completed the following prerequisite steps:
  • On the data aggregator server, you have verified that the ports that enable communication between the data collector and the data aggregator (ports 61616, 61618, 61620, and 61622) are open.
    For more information about the data aggregator server ports that are required to be open, see Installation Requirements and Considerations.
  • You have installed the zip and unzip packages. If you have not installed these packages, install them by issuing the following command:
    yum -y install zip unzip
  • The data collector uses the "at" package to schedule the restart of the application when assigning a Tenant or IP Domain. Verify whether the "at" package is installed on each data collector host by issuing the following command:
    rpm -qa | grep ^at
    If the command does not return a result, install the package by issuing the following command:
    If you are not the root user, use the sudo prefix.
    yum install at
Upgrade as a Root or Sudo User
Follow these steps:
  1. Log in to the data collector host as a root user or as a user with the necessary sudo privileges.
  2. Change to the
    /tmp
    directory by issuing the following command:
    cd /tmp
  3. Download the installation package to the
    /tmp
    directory based on your configuration:
    • (If
      wget
      is available) Issue the following command:
      • (HTTP data aggregator)
        wget http://
        <da_host>
        :
        <port>
        /dcm/InstData/Linux/VM/install.bin
        • da_host
          Specifies the data aggregator host name.
        • port
          Specifies the data aggregator required port number.
          Default:
          8581
      • (HTTPS-enabled data aggregator) Issue the command with the
        --no-check-certificate
        option:
        wget -P /tmp --no-check-certificate https://
        <da_host>
        :
        <port>
        /dcm/InstData/Linux/VM/install.bin
        • da_host
          Specifies the data aggregator host name.
        • port
          Specifies the data aggregator required port number.
          Default:
          8582
    • (If
      wget
      is unavailable) Issue the following command:
      • (HTTP data aggregator)
        curl -o /tmp/install.bin http://
        <da_host>
        :
        <port>
        /dcm/InstData/Linux/VM/install.bin
        • da_host
          Specifies the data aggregator host name.
        • port
          Specifies the data aggregator required port number.
          Default:
          8581
      • (HTTPS-enabled data aggregator) Issue the command with the
        -k
        option:
        curl -k -o /tmp/install.bin https://
        <da_host>
        :
        <port>
        /dcm/InstData/Linux/VM/install.bin
        • da_host
          Specifies the data aggregator host name.
        • port
          Specifies the data aggregator required port number.
          Default:
          8581
    • Use a browser.
  4. Change permissions for the
    install.bin
    installation file by issuing the following command:
    chmod a+x install.bin
  5. Do
    one
    of the following steps:
    • Run the installation as the root user by issuing the following command:
      ./install.bin -i console
    • Run the installation as a user with the necessary sudo privileges by issuing the following command:
      sudo ./install.bin -i console
    • Run the installation in silent mode by issuing the following command:
      ./installDA.bin -i silent -f
      response_file
      response_file
      is the directory path and file name of the previously generated response file.
      To generate a response file for silent installation, add the following argument:
      -r
      response_file
      response_file
      specifies the directory the directory path and file name for the response file.
      Example:
      /temp/installer.properties
      Follow the prompts until you get to the summary, type
      quit
      , and press
      Enter
      .
  6. Follow the instructions in the console.
  7. (Optional) When prompted, specify the following parameters for fault tolerance:
    For more information, see Fault Tolerance.
    • Is the Data Aggregator configured with fault tolerance?
      If you have configured a fault-tolerant environment, specify
      2
      for Yes.
      Default:
      1
    • Inactive Data Aggregator Host/IP Address
      Specify the host name/IP address of the inactive data aggregator responsible for this data collector.
      For more information about how to view this information, see View the Health of the System.
The data collector is upgraded. The console displays a confirmation message.
Verify the Upgrade as a Root or Sudo User
After you have upgraded the data collectors manually, verify the upgrade.
Follow these steps:
  1. Verify that the data collector is running on the data collector host by issuing the following command:
    service dcmd status
  2. Verify that the data collector connection is successful. Complete the following steps:
    1. Log in to
      NetOps Portal
      as the global administrator.
    2. Hover over
      Administration
      ,
      Data Source
      , and then click the data aggregator data source.
      The
      Monitored Devices
      page appears.
    3. From the
      System Status
      menu, click
      Data Collectors
      .
      The
      Data Collectors
      page appears.
    4. Verify that the data collector appears in the list.
The upgrade is verified.
The data collector is upgraded.