Getting started

This section shows how to start the probe with the minimum required configuration. The procedure assumes that you have a version of Netcool/OMNIbus installed and running.

Use the following procedure to start the probe with a minimal configuration:

Note: The commands shown in this example are for a Linux system. Adapt these commands as necessary for the operating system that your probe server runs.
  1. Download the probe's installation package following the instructions in http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_download_intro.html.
  2. Install the probe following the instructions in http://www-01.ibm.com/support/knowledgecenter/SSSHTQ/omnibus/probes/all_probes/wip/reference/install_install_intro.html.
  3. Edit the probe's properties file and set values for the following: [insert nested list of properties and the values they need]
  4. Ensure that $NCHOME/etc/omni.dat includes information on the ObjectServer.
  5. If you made changes to omni.dat, regenerate the definition file by running $NCHOME/bin/nco_igen.
  6. Check that the server where you have installed the probe can contact the ObjectServer using the ping utility. For example:
    ping -c 10 server-name

    Replace server-name with the name of the server where the ObjectServer is running.

    Alternatively, if you have installed the Netcool/OMNIbus desktop feature, you can use the nco_ping utility to check connectivity to the ObjectServer. For example:

    nco_ping object-server

    Replace object-server with the name of the ObjectServer.

  7. Obtain a listing of the probe's command line options to check the probe is installed correctly:

    $NCHOME/omnibus/probes/nco_p_hp_nnm -help

    Check that the output from this command begins as follows:

    Using IBM Java
Version 1.8.0
Usage: "nco_p_hp_nnm" [options]
where options can be:
 -autosaf                     Enable automatic Store and Forward on startup
 -beatinterval                Probe failover heartbeat interval
 -beatthreshold               Probe failover heartbeat threshold time
 -buffer                      Turn on alert buffering
 -bufferflushinterval         The interval (in seconds) before flushing the alert buffer
  8. Start the probe as follows:
    $NCHOME/omnibus/probes/nco_p_hp_nnm -propsfile $NCHOME/omnibus/probes/linux2x86/hp_nnm.props -messagelevel debug
  9. Check the probe's log file to ensure the probe started correctly and is ready to receive, process, and dispatch events.

    The probe's MessageLog property provides the name and location of the probe's log file.

  10. Where possible, use a test tool to send events to the probe and so check they are processed correctly.

    For example, use the curl utility to send an event to the probe.

The probe is now successfully installed and operational. You can now configure the probe to suit your operating environment.