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:
- 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.
- 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.
- Edit the probe's properties file and set values for the following: [insert nested list of properties and the values they need]
- Ensure that $NCHOME/etc/omni.dat includes information on the ObjectServer.
- If you made changes to omni.dat, regenerate the definition file by running $NCHOME/bin/nco_igen.
- Check that the server where you have installed the
probe can contact the ObjectServer using the ping utility.
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:
Replace object-server with the name of the ObjectServer.
- Obtain a listing of the probe's command line options to check the probe is
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
- Start the probe as follows:
$NCHOME/omnibus/probes/nco_p_hp_nnm -propsfile $NCHOME/omnibus/probes/linux2x86/hp_nnm.props -messagelevel debug
- 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.
- Where possible, use a test tool to send events to the probe and so check they are processed
For example, use the
curlutility 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.