Install snmpcollector

This article contains recommendations and considerations for installing the snmpcollector probe software.
uimpga-ga
This article contains recommendations and considerations for installing the snmpcollector probe software.
Contents
Installation Considerations
Consider the following information before you install the probe, on the secondary hub CA Unified Infrastructure Management server:
You might require updates to ci_defn_pack, mps_language_pack and wasp_language_pack
The minimum software packages that are required to run snmpcollector to generate only QoS data are: 
  • Install the following
    minimum
    probe packages on the secondary hub, where snmpcollector is deployed:
    • snmpcollector
    • ppm (automatically installs the required probes prediction_engine and baseline_engine)
      Imporant!
      In snmpcollector Raw Configure, update the
      “discovery_address”
      key to point to primary hub discovery server.
  • If you want to enable alarms, install on a remote (not primary) hub:
    • prediction_engine
    • baseline_engine
    • NAS (to install the alarm_enrichment package)
    Warning!
    These packages are required to enable alarm functionality in the snmpcollector probe. Do not uninstall prediction_engine and baseline_engine once installation is complete.
    The threshold alarm options only appear in the probe configuration GUI if you install these probes.
    We recommend that you do install these probes.
    These probes provide useful features such as Time to Threshold and Time Over Threshold alarms.
  • On Linux/Unix systems, the /etc/hosts file should contain an entry with the FQDN for the installation system.
Performance and Scalability Considerations
The snmpcollector probe uses a large amount of memory and disk resources. For the best performance and scalability:
  • Install the snmpcollector probe on a secondary hub. Installing the probe on the primary hub, or on a robot alone is not supported. The hub that you use for SNMP data monitoring can have a significant impact on the performance and scalability of the probe. 
  • Allocate sufficient memory and disk space to support your data collection requirements. The monitoring capabilities of the snmpcollector probe are limited if you install the probe on a small scale system with a limited amount of resources. For more information about the
    minimum
    hardware requirements, see snmpcollector Hardware Requirements.
  • Only install snmpcollector with other monitoring probes if the other probes do not consume a large amount of system resources.
    For example, you can install the cdm and ntservices probes if the hub has sufficient resources. We do not recommend installing snmpcollector on a hub with other probes that can also consume a large amount of system resources. Some examples of these probes are vmware, icmp, and ibmvm.
  • Use filters as much as possible rather than creating multiple templates. Filters let you control how the probe applies monitors based on attributes of the target device. Every template that you create is read separately by the probe. The probe uses a large amount of system resources to read each template.
Install snmpcollector
Follow these steps:
  1. Review the installation considerations and performance and scalability considerations.
    These sections contain important information about where and how to deploy the snmpcollector probe and information about alternative installation options.
  2. Verify that the local archive has the packages for all the minimum probe versions. For specific information about your snmpcollector version, see snmpcollector Software Requirements.
  3. Verify that you installed any required:
    • mps_language_packs where service_host is running
    • ci_defn_packs where nis_server is running
    • wasp_language packs on the UMP server where wasp is running
  4. Restart nis_server and wasp.
  5. Choose one of the following options:
    • (
      Versions 2.1-2.26
      ) Deploy the probe meta-package on the appropriate hub. Use the meta-package to install the current version for snmpcollector probe packages that exist in the local archive. The meta-package installs the snmpcollector probe with
      all
      the software packages required to enable
      all
      the snmpcollector probe features. Do not use the meta-package to install individual software components. The meta-package installation fails if all the packages are not present in the local archive.
      Warning!
      We recommend that you use a remote (not primary) hub. 
    • Install the packages individually on the appropriate hub.
  6. Configure the queues on any remote hubs to post data to the primary hub. The remote hub requires a queue for
     QOS_MESSAGE, QOS_DEFINITION, QOS_BASELINE, and
      a queue for 
    probe_discovery
     to export messages.
  7. Configure the hub name service on the primary hub for any remote (not primary) hubs.
  8. On a remote hub with snmpcollector and NAS, set NAS forwarding as "All alarm events in both directions". The destination is the primary hub.
  9. Verify that NAS and alarm_enrichment are running on the hub. If necessary, start NAS and alarm_enrichment.
  10. Configure the
    “discovery_address”
    key to point to primary hub discovery server.
Adjust Probe Memory Settings
The memory and disk requirements for the snmpcollector and pollagent probes can vary. The number of processors, devices, device components, and metrics can affect your requirements. You might need to adjust the Xmx memory to improve performance. For more information, see snmpcollector Memory and Disk Requirements.
pollagent Memory
(snmpcollector 2.x and earlier)
Follow these steps:
  1. In Infrastructure Manager, select and right-click on pollagent.
  2. Select
    Edit
    from the menu.
  3. In the
    Arguments
    box, change the number in
    -Xmx
    1536
    m. 
    The number following
    Xmx
    is the maximum amount of memory in megabytes consumed by the probe.
  4. Click
    OK
    .
snmpcollector Memory
Follow these steps:
  1. Enter the Raw Configure menu for the snmpcollector probe.
  2. Select the
    startup
    node.
  3. Select
    options
    .
  4. Change the number in
    -Xmx
    1024
    m
    . The number following
    Xmx
    is the maximum amount of memory in megabytes consumed by the probe.
  5. Click Apply.
Hub Configuration
You set up queues on the hub to transfer snmpcollector data as part of the
CA Unified Infrastructure Management
configuration process. The snmpcollector probe can send a large amount of data through these queues.
If the size of a get or post queue never shrinks to zero or if it always has many messages, increase the
Bulk Size
on the queue. The bulk size setting allows the hub to transfer multiple messages in one packet. For more information about hub configuration, see the appropriate guide for your hub version.
(v2.x and later)
We recommend that you install snmpcollector and NAS on a remote (not primary) hub. In addition, verify that you have:
  • Set up queues on the remote hub to post data to the primary hub. The remote hub requires a queue for
     QOS_MESSAGE, QOS_DEFINITION, QOS_BASELINE
    , and a queue for 
    probe_discovery
     to export messages.
  • Configure NAS forwarding as "All alarm events in both directions" on the remote hub. The destination is the primary hub.
    Note
    : If you have a multi-tenant environment and want users to see only their respective data, use "All events to destination (one direction)."