Install a Low-Scale System

In a standard large-scale deployment, the data aggregator and data collector components require dedicated nodes. For some smaller deployments of 150,000 polled items or less, you can run these components on a shared single node.
capm360
HID_DA_DC_shared_host
In a standard large-scale deployment, the data aggregator and data collector components require dedicated nodes. For some smaller deployments of 150,000 polled items or less, you can run these components on a shared single node.
In high-scale environments, install the data aggregator and the data collector on
separate
dedicated nodes.
Limitations
When
DX NetOps Performance Management
is deployed with the data aggregator and the data collector on a single node, the following options are not supported:
  • Calculated metrics beyond 150,000 metrics per second
  • Fast (1 minute) polling
  • Integration with
    DX NetOps Mediation Manager
    or
    DX NetOps Virtual Network Assurance
  • Multiple DCs
  • Multiple IP domains
  • Multiple tenants
  • Polling beyond 150,000 items
The configuration of deploying on a single node does not persist through upgrades. After you upgrade the data aggregator, upgrade and configure the data collector according to the procedures described in this article.
How to Install a Low-Scale System
Use the following process to deploy
DX NetOps Performance Management
with the data aggregator and data collector on a single node:
  1. Install
    NetOps Portal
    .
    For more information, see Install Performance Center.
  2. Install the Data Repository.
    Because the Data Repository in a low-scale system is deployed on a single node, skip the steps that refer to cluster installation.
    For more information, see Install the Data Repository.
  3. Install the data aggregator.
    For more information, see Install the Data Aggregator.
  4. Install and configure the data collector on the same host as the data aggregator using the following procedures:
    3
Install the Data Collector
Install the data collector on the same host as the data aggregator.
Follow these steps:
  1. Log in to the shared host.
  2. Verify that the data aggregator service is running by issuing the following command:
    service dadaemon status
    For RHEL 7.x or OL,
    service
    invokes
    systemctl
    . You can use
    systemctl
    instead.
  3. If the service is not running, do one of the following steps:
    • Start the data aggregator service by issuing the following command:
      service dadaemon start
    • (Fault tolerant environment) Issue one the following commands to enable the fault tolerant data aggregator so that it can start when necessary:
      • RHEL 6.x:
        service dadaemon activate
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory
        /scripts/dadaemon activate
  4. Verify that the ActiveMQ broker is running by issuing the following command:
    service activemq status
    If the service is not running, start the ActiveMQ service by issuing the following command:
    service activemq start
  5. Download the data collector installer:
    wget -nv http://
    da_host
    :8581/dcm/InstData/Linux/VM/install.bin
  6. Make the install file executable by issuing the following command:
    chmod a+x install.bin
  7. Do one of the following steps:
    • Stop the data aggregator and ActiveMQ services by issuing the following commands:
      service dadaemon stop
      service activemq stop
    • (Fault tolerant environment) If the local data aggregator is running, issue one the following commands to shut it down and prevent it from restarting until maintenance is complete:
      • RHEL 6.x:
        service dadaemon maintenance
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory/scripts/dadaemon maintenance
  8. Install the data collector by issuing the following command:
    ./install.bin -i console
  9. Follow the instructions in the console.
    The installer prompts you for the hostname or IP address of the data aggregator host. Supply the hostname of the shared host. The data collector is installed and the data collector and ActiveMQ services start. After a short time, the data collector service fails because the data aggregator service is not running.
  10. Uninstall the Data Aggregator ActiveMQ service by issuing the following command:
    /opt/IMDataAggregator/scripts/activemq uninstall
  11. Install the data collector ActiveMQ service by issuing the following command:
    /opt/IMDataCollector/scripts/activemq install
Reconfigure the Data Collector
After you have installed the data collector on the shared host, reconfigure the data collector to use the shared host. On a shared host, the data aggregator and data collector use a single ActiveMQ broker.
This procedure includes the following variables:
  • <DA_Install_Directory>
    The installation directory for the data aggregator.
    Default:
    /opt/IMDataAggregator
  • <DC_Install_Directory>
    The installation directory for the data collector.
    Default:
    /opt/IMDataCollector
Follow these steps:
  1. Stop the data collector and ActiveMQ services by issuing the following commands:
    service dcmd stop
    service activemq stop
  2. Modify the data aggregator startup script:
    1. Edit the
      DA_Install_Directory
      /scripts/dadaemon
      file.
    2. Modify the ACTIVEMQ_HOME variable to point to the data collector ActiveMQ broker by issuing the following command:
      ACTIVEMQ_HOME="
      <DC_Install_Directory>
      /broker/apache-activemq-
      version
      " export ACTIVEMQ_HOME
      • version
        Specify the ActiveMQ version. To find the correct version, go to the
        <DC_Install_Directory>
        /broker
        directory.
  3. Disable the data aggregator ActiveMQ broker heartbeat:
    1. Create the
      <
      DA_Install_Directory
      >/apache-karaf-2.4.3/etc/com.ca.im.dm.core.amq.cfg
      file.
      Create this file as the user running the data aggregator to ensure the correct permissions are set on the new file.
    2. Edit the file and insert the following property configuration:
      jmsbroker-heartbeat-disabled=true
    3. To disable log messages that are related to the data aggregator heartbeat manager, edit the
      <
      DA_Install_Directory
      >/apache-karaf-2.4.3/etc/org.ops4j.pax.logging.cfg
      file.
    4. Insert the following property configuration:
      # Disable ActiveMQ Health Monitoring log messages in shared DA/data collector mode
      log4j.logger.com.ca.im.core.jms.heartbeat.JmsHeartbeatManager=OFF
  4. Modify the Apache Karaf JMX management properties:
    1. Edit the
      <DC_Install_Directory>
      /apache-karaf-2.4.3/etc/org.apache.karaf.management.cfg
      file.
    2. Set the following properties:
      rmiRegistryPort = 1199
      rmiServerPort = 44445
  5. (Optional) To support the ability to debug the data aggregator and data collector components simultaneously, modify the Karaf debug port:
    1. Edit the
      <
      DC_Install_Direcotry
      >/apache-karaf-2.4.3/bin/karaf
      file.
    2. Set the following property:
      DEFAULT_JAVA_DEBUG_PORT=5006
  6. Do one of the following steps:
    • Start the data aggregator service by issuing the following command:
      service dadaemon start
    • (Fault tolerant environment) Issue one the following commands to enable the fault tolerant data aggregator so that it can start when necessary:
      • RHEL 6.x:
        service dadaemon activate
      • RHEL 7.x, SLES, or OL:
        DA_Install_Directory
        /scripts/dadaemon activate
  7. Start the data collector service by issuing the following command:
    service dcmd start
  8. The data aggregator and data collector services start on the single host. Complete post installation configuration for your deployment.
Validate the Deployment
Validate the deployment by verifying that the required services are functioning as expected.
Follow these steps:
  1. Validate that the data aggregator service is running by issuing the following command:
    service dadaemon status
  2. Validate that the data collector service is running by issuing the following command:
    service dcmd status
  3. Validate that the ActiveMQ Broker is running by issuing the following command:
    service activemq status
  4. Validate that the ActiveMQ Broker being run is the data collector broker by issuing the following command:
    service activemq status
    The returned message must include the following information:
    Status for ActiveMQ: INFO: Loading '
    <
    DC_Install_Directory
    >
    /broker/apache-activemq-
    version
    /bin/env
    '
    If the message does not show the data collector installation directory, repeat the step in the previous procedure to modify the data aggregator startup script.