Upgrade the Data Collectors

After you upgrade the Data Aggregator, upgrade the Data Collectors.
capm360
After you upgrade the Data Aggregator, upgrade the Data Collectors.
If you are upgrading from 
CA Performance Management
 3.5 or higher as the 
root
 user, you can upgrade the Data Collector easily using the Upgrade button in 
Performance Center
. This button is an extra and easier avenue for upgrading your Data Collectors. If you are upgrading from 
CA Performance Management
 3.6 or higher as a non-root user, you can also use the Upgrade button.
 To use this feature, the Data Collectors must be running as the 
root
 user or a user with the necessary 
sudo
 privileges. If you are upgrading from any 3.5 release as a non-root user, you must upgrade the Data Collectors manually. Also, anyone upgrading from a release before 3.5 must upgrade the Data Collectors manually.
 For a major release, the user interface indicates that an upgrade is required. For a minor incremental upgrade (for example, a monthly update), the user interface does not indicate that an upgrade is required. However, you can still use the Upgrade button to upgrade to the latest release.
The Data Collectors can continue to run during the upgrade and cache polled data to disk. When the Data Aggregator and Data Repository upgrade completes, the Data Collectors load the cached data. All the Data Collectors are upgraded at once through a staged process where up to two Data Collectors upgrade in parallel. This upgrade method allows you to upgrade your Data Collectors with a minimal reporting gap. Also, an upgraded Data Aggregator (at version 3.5 or higher) can continue to communicate with the previous versions of your Data Collectors (at version 3.5 or higher) as they upgrade.
 Before you upgrade the Data Collectors, each Data Collector must have a Tenant and IP Domain assigned. The upgrade process skips any Data Collectors with no Tenant or IP Domain assigned.
 This upgrade method does not support remote upgrade for Data Collectors that are assigned with a Pseudo Tenant Proxy. For more information, see Tenant-Agnostic Data Collectors.
The upgrade for these Data Collectors might hang with an "Upgrade Pending" status. You must manually upgrade these Data Collectors. If this issue occurs, the Data Collectors continue to collect data as normal and other Data Collectors continue to upgrade.
If you have authenticated and encrypted activeMQ communication, you must regenerate the keys before this upgrade. For more information, see Authenticate and Encrypt ActiveMQ Communication.
For the first and last name prompt, you must enter the host name of the system where you are creating the certification.
 
Follow these steps:
 
  1. If you are running the upgrade as a non-root user, complete the following steps:
    1. Locate the following file on the Data Collector host:
      /etc/sudoers
       
    2. Add the following command alias with the following permissions to the file:
      dcuser dchostname
      = (root) NOPASSWD:
      DC_install_directory
      /upgrade/install.bin
      If 
      requiretty
       is enabled, add the following text to disable 
      requiretty
       for the Data Collector installer:
       
      Defaults!
      DC_install_directory
      /upgrade/install.bin !requiretty
       
  2. Log in to 
    Performance Center
     as the global administrator.
  3. Hover over 
    Administration
    , and click
     Monitored Items Management: Data Collectors
    .
  4. Select all the Data Collectors and click 
    Upgrade
    .
    A confirmation message appears.
  5. To proceed with the upgrade, click 
    Yes
    .
    The status of the upgrade appears in the Status column.
 If you are upgrading from any 3.5 release as a non-root user, you must upgrade the Data Collectors manually. Also, anyone upgrading from a release before 3.5 must upgrade the Data Collectors manually.
 
 
2
 
 
Verify the Prerequisites for a Manual Upgrade
Meet the following prerequisites before you upgrade the Data Collector:
  • On the Data Aggregator system, verify that ports 61616, 61618, 61620, and 61622 are open. These ports enable communication between the Data Collector and the Data Aggregator.
  • Before you upgrade, verify the zip and unzip packages are installed. If these packages are not installed, use the following command to install them:
    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:
    rpm -qa | grep ^at
    If the command does not return a result, install the package:
     If you are not the root user, use the sudo prefix.
    yum install at
Upgrade the Data Collector Manually
To upgrade the Data Collector manually, run the installation as the root or sudo user.
 
Follow these steps:
 
  1. Log in to the Data Collector host as the root user or a sudo user.
  2. Change to the /tmp directory:
    cd /tmp
  3. Use 
    wget
    curl
    , or a browser to download the installation package to the /tmp directory:
    wget http://
    data_aggregator
    :
    port
    /dcm/InstData/Linux/VM/install.bin
    curl -o /tmp/install.bin http://
    data_aggregator
    :
    port
    /dcm/InstData/Linux/VM/install.bin
    Default port: 8581
  4. Change permissions for the installation file:
    chmod a+x install.bin
  5. To run the upgrade, do one of the following steps:
    • Run the installation as the root user:
      ./install.bin -i console
    • Run the installation as the sudo user:
      sudo ./install.bin -i console
     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.
    To run the installation in silent mode, use 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.
  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 fault tolerance was configured for the Data Aggregators, 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.
  8. When the upgrade is complete, the console displays a confirmation message.
  9. Verify that Data Collector is running:
    service dcmd status
Verify a Manual Upgrade
After you upgrade the Data Collectors manually, verify the upgrade.
 
Follow these steps:
 
  1. Log in to 
    Performance Center
     as the global administrator.
  2. Navigate to the Data Aggregator data source.
  3. Expand 
    System Status
    , and click 
    Data Collectors
    .
  4. Verify that Data Collector appears in the list.
     The list can take several minutes to refresh and show the new Data Collector installation.