Upgrade the Data Aggregator

To upgrade the Data Aggregator, complete the following steps:
capm360
To upgrade the Data Aggregator, complete the following steps:
2
If you enabled FIPS-compliant encryption, and you upgrade
CA Performance Center
before the Data Aggregator, temporary FIPS compatibility synchronization errors occur. These errors occur until the Data Aggregator is upgraded. To avoid this temporary condition, upgrade the Data Aggregator before upgrading
CA Performance Center
.
Verify the Prerequisites
Meet the following prerequisites before you upgrade the Data Aggregator:
  • Verify that ports 8581, 61616, 61618, 61620, and 61622 are open for communication between your Data Collectors and your Data Aggregators.
    For the detailed port list, Review Installation Requirements and Considerations.
  • 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
  • For the Data Aggregator and the Data Collectors, the default maximum memory is 80% of the total system memory. AMQ uses 20% of total memory on both components. Both components reserve 2 GB of memory for the operating system. These maximum values can be modified, however the modifications are not preserved during an upgrade. For more information, see Modify Maximum Memory Usage for Data Aggregator and Data Collector Components.
Verify the Limit on the Number of Open Files on Data Aggregator
Verify that the user that is installing Data Aggregator has a limit of at least 65536 on the number of open files. Set this value permanently.
Follow these steps:
  1. As the root user or a sudo user, log in to the Data Aggregator host. 
  2. Change the ulimit for the open files limit to at least 65536:
    ulimit -n
    ulimit_number
    For example:
    ulimit -n 65536
  3. Open the following file:
    /etc/security/limits.conf
  4. Add the following lines:
    # Added by Data Aggregator
    * soft nofile 65536
    # Added by Data Aggregator
    * hard nofile 65536
    Restart Data Aggregator for these changes to take effect. If you are upgrading, the upgrade process automatically restarts Data Aggregator.
  5. Verify that the number of open files is set properly:
    ulimit -n
    The command returns the limit that you specified earlier.
Verify That the Data Repository Is Running
The Data Aggregator Upgrade requires that the Data Repository is running.
Follow these steps:
  1. Log in to the Data Repository host.
  2. Verify that the Data Repository is running:
    /opt/vertica/bin/vsql -U
    dauser
    -w
    dapass
    -c 'select version()'
    The expected return shows the version of the Data Repository:
    version
    ------------------------------------
    Vertica Analytic Database vx.x.x-x
(Optional) Temporarily Connect to Older Versions of Data Collectors
You can reduce data loss during an upgrade by temporarily connecting existing Data Collectors (version 3.0, 3.1, or 3.2) to an upgraded Data Aggregator. Consider this upgrade option if you have many Data Collectors to upgrade.
Important! Connecting 3.x versions of Data Collectors to upgraded Data Aggregators is only supported on a temporary basis.
New features in
CA Performance Management
3.5 may not be compatible with older Data Collectors. Before using new features or making configuration changes, upgrade all Data Collectors to the same version as the Data Aggregator.
Follow these steps before upgrading the Data Aggregator:
  1. Create a file called com.ca.im.dm.core.collector.controller.cfg in the following location:
    /opt/IMDataAggregator/apache-karaf-2.4.3/etc/
  2. Add the following single line to the file:
    allowed-mismatch-dc-version=3.0.0.0
  3. Save the file.
  4. Proceed with upgrading the Data Aggregator.
Verify ETL Health
Before you upgrade, run the
etlHealth.sh
script. For releases 3.7.16 and higher, the script is included with the Data Repository installation. For earlier releases, contact Support. We recommend you run this script well in advance of the upgrade and again directly before the upgrade.
Follow these steps:
  1. Log in to one of the Data Repository nodes as the root user.
  2. Run the validation script:
    ./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.
Upgrade the Data Aggregator
To upgrade the Data Aggregator, run the installation as the root or sudo user.
Follow these steps:
  1. Log in to the Data Aggregator host as the root user or a sudo user.
  2. Copy the installDA.bin file to the /tmp directory.
  3. Change to the /tmp directory:
    cd /tmp
  4. Change permissions for the installation file:
    chmod a+x installDA.bin
  5. To run the upgrade, do one of the following steps:
    • Run the installation as the root user:
      ./installDA.bin -i console
    • Run the installation as the sudo user:
      sudo ./installDA.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.
    If the Data Repository was migrated, follow the Data Aggregator upgrade instructions in the console. Answer NO when prompted to drop the schema and the upgrade continues. If you answer YES, you lose your migrated data.
    When you are prompted for the data directory, use the default directory. Do not use
    DA_Install_Directory
    /apache-karaf-
    version
    /data
    .
  7. (Optional) When prompted, specify the following parameters to configure fault tolerance. For more information, see Fault Tolerance.
    If you are upgrading an existing fault tolerant environment, see Upgrade Fault Tolerant Data Aggregators.
    • Configure Data Aggregator For Fault Tolerance
      Specify 2 to configure fault tolerance.
      Default:
      1
      The default is for a non-fault tolerant environment.
    • Data Aggregator Proxy Host
    • Specify the host name/IP address of the proxy server.
    • Consul HTTP port:
      Specify the port for communication with Consul.
      Default:
      8500
    • Choose host IP address for Consul
      This prompt appears only when multiple public IP addresses are configured.
      Specify the bind address that the Consul agents use to communicate with each other. The Consul agents include the proxy host and both Data Aggregators in the cluster. If prompted for an address, specify an address that the other two hosts in the Consul cluster can reach.
    Data Aggregator is upgraded. The console displays a confirmation message.
    The installer restarts Data Aggregator automatically when the upgrade is complete.
    Wait for Data Aggregator to synchronize automatically with CA
    CA Performance Center
    . This process can take 30 minutes or longer.
  8. Verify that Data Aggregator is running:
    service dadaemon status
  9. Verify access to the Data Aggregator REST endpoints. Open a Web browser on a computer with HTTP access to Data Aggregator. Navigate to the following address:
    http://
    data_aggregator
    :port/rest
    data_aggregator:port
    specifies the Data Aggregator host name and the required port number.
    The return is a list of hyperlinks for available web services. When you click a link, the XML content describing the selection displays.
    Table segmentation is required for systems where the original installation was a release earlier than 2.3.3. Segmentation is a one-time task that improves database performance and reduces the required disk space. If you received a message during the upgrade that the database tables require segmentation, complete table segmentation after the upgrade. For more information, see Segment Database Tables.
    The Karaf log in the Data Aggregator includes the following error after upgrading the installation:
    ERROR | tenderThread-178 | 2013-01-24 13:36:40,431 | ndorCertificationPriorityManager | nager.core.cert-mgr.impl |
    | Failed to load the MetricFamilyVendorPriority for bundle: BundleURLEntry [bundle=198, resourceURL=file:/opt/IMDataAggregator/apache-karaf-<
    vers
    >/data/cache/resources/198--xml-vendorpriorities-ReachabilityVendorPriorities.xml
    This error for Reachability is expected and harmless. Other occurrences of this error are not expected.