Getting started

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

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 items:
   • Server: Set this property to the name of the ObjectServer that the probe sends events to. The default value of this property is NCOMS.
   • Port: Set this property to the port that the probe listens to for SNMP traffic. Make sure that no other SNMP agent is using the port you choose. Note that if you use the default value of 162, you cannot run the port from a non-root user account.
   • Protocol: Set this property to ALL. This setting ensures that the probe listens for V1 and V2c traps on both the UDP and TCP protocols.
   • MessageLevel: Set this property to Debug. This setting provides the maximum amount of information when the probe is running.

   For example, if the ObjectServer is named MY_OBJ and the probe uses port 1162, the properties file would contain the following entries:

   #######################################################################
   #
   # Add your settings here
   #
   #######################################################################
   Server : 'MY_OBJ'
   Port : 1162
   Protocol : 'ALL'
   MessageLevel : 'debug'

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 that the probe is correctly installed. For example:

   $NCHOME/omnibus/probes/linux2x86/nco_p_mttrapd -help

   Check that the output from this command begins as follows:

   
   Usage: opt/netcool/omnibus/probes/linux2x86/nco_p_mttrapdd [options]
   
   where options can be:
   
   -all           Listen for traps via UDP and TCP, using IPv4
   -allip6        Listen for UDP or TCP traps, using IPv6
   -any           Listen for traps via UDP and TCP, using IPv4
   -autosaf       Enable automatic Store and Forward on startup
   -beatinterval  Probe failover heartbeat interval.

8. Run the probe from the command line:

   $NCHOME/omnibus/probes/linux2x86/nco_p_mttrapd \
   -propsfile $NCHOME/omnibus/probes/linux2x86/mttrapd.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 snmptrap utility to send a number of test traps to the probe.

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

For example, you can change the values of the properties used in this example to their production values:

• MessageLevel: Set this property to the level you require, such as Warning.
• Protocol: Set this property to the protocol you require, such as TCP.

In addition, you can set up other facilities of the probe, such as SNMP V3, peer-to-peer failover, and remote management using the probes HTTP/HTTPS interface.