Configure Data Aggregator to use added memory [DX NetOps Performance Management]
search cancel

Configure Data Aggregator to use added memory [DX NetOps Performance Management]

book

Article ID: 46810

calendar_today

Updated On:

Products

CA Performance Management Network Observability

Issue/Introduction

When installing DX Netops Performance Management  (CA Performance Management/CAPM) components, memory usage is set by a combination of questions and automatic evaluation of the system resources.

When increasing memory on a Data Aggregator host, manual configuration changes are required to ensure the Data Aggregator (DA) and ActiveMQ services leverage the additional resources.

This article outlines the necessary file updates to synchronize memory allocation settings.

 

Data Aggregator, Repository performance issues

Environment

  • DX NetOps Performance Management (All Supported Versions)
  • Note: The configuration process and file locations changed significantly in release 25.4.4.

Cause

Increased memory resources on Data Aggregator (DA). Need to configure it to use the increased resources available.

Configuration drift between the runtime environment files and the persistent DA.cfg file, or failure to update configuration files after a host resource upgrade.

NOTE :: The process and files change for release 25.4.4+

Resolution

Memory Allocation Formula To determine the correct memory settings:

  1. Reserve 2 GB for the Operating System.
  2. Allocate 80% of the remaining memory to the Data Aggregator (DA).
  3. Allocate 20% of the remaining memory to ActiveMQ (AMQ).

Resolution

For versions prior to 25.4.4:

  1. Stop the dadaemon and activemq services.
  2. Edit the DA runtime values in /opt/IMDataAggregator/apache-karaf/bin/setenv:
    • Update export IM_MAX_MEM=[Value]M
  3. Edit the persistent DA configuration in /etc/DA.cfg:
    • Update da.memory=[Value]M
  4. Edit the ActiveMQ runtime values in /opt/IMDataAggregator/scripts/activemq:
    • Update ACTIVEMQ_OPTS_MEMORY (Set -Xmx to the allocated AMQ memory and -Xms to half of that value).
  5. Edit the persistent ActiveMQ configuration in /etc/DA.cfg:
    • Update da.activemq.memory=[Value]M
  6. Restart the dadaemon and activemq services.

For versions 25.4.4 and later:

  1. Stop the dadaemon and activemq services.
  2. Edit the consolidated configuration in /etc/DA.cfg:
    • Update da.memory for Data Aggregator memory settings.
    • Update da.activemq.memory for ActiveMQ memory settings.
  3. Restart the dadaemon and activemq services.

Additional Information

How to add more memory and/or CPU to vertica hosts:

https://knowledge.broadcom.com/external/article/213360/

 

How to configure my Data Collector (DC) to make use of new resources.

https://knowledge.broadcom.com/external/article/46765/

 

How to configure NetOps Portal to make use of new resources.

https://knowledge.broadcom.com/external/article/46563/