IBM Tivoli Monitoring > Version 6.3 Fix Pack 2 > Administrator's Guide > Agent-based services > SNMP alerts > OMNIbus configuration for SNMP

IBM Tivoli Monitoring, Version 6.3 Fix Pack 2

Configure OMNIbus to receive SNMP alerts

Configure the SNMP Probe to accept the SNMP traps and informs of situation events from Tivoli monitoring agents.

Have the IBM Tivoli Monitoring V6.2.2 or later Agents DVD available. Verify that Tivoli Netcool/OMNIbus V7.x is installed and that the SNMP Probe is installed.

Do not configure an enterprise situation for emitting SNMP alerts to the SNMP Probe if the hub monitoring server is also configured to forward events for the same situation to the Netcool/OMNIbus Probe for Tivoli EIF because OMNIbus deduplication will not detect that they are the same event.


Complete these steps to prepare your OMNIbus environment to receive SNMP alerts for situation events from Tivoli monitoring agents.


Procedure

  1. Copy the Tivoli Monitoring rules file and lookup file.

    1. Locate the mibs/sample_rules/omnibus directory on the Tivoli Monitoring V6.2.2 or later Agents installation media.

    2. Copy these management information base files to $OMNIHOME/probes/arch/ on the computer where the SNMP Probe is installed:
      ibm-TIVOLI-CANSYSSG-MIB.include.snmptrap.rules
      ibm-TIVOLI-CANSYSSG-MIB.include.snmptrap.lookup

  2. Reference the files in the rules that the SNMP Probe is using.

    1. Open the default rules file in a text editor. The default rules file is $OMNIHOME/probes/arch/mttrapd.rules unless specified otherwise in the mttrapd properties file (Step 3).

    2. Add the lookup table reference as the first definition: 

        include "<path_to_lookup_file>/
ibm-TIVOLI-CANSYSSG-MIB.include.snmptrap.lookup"

      Table definitions must appear at the start of a rules file, before any processing statements. If you are adding this statement to mttrapd.rules, position it after the comments at the head of the file and before the first processing statement. The fully qualified filename must be enclosed in double quotes. Environment variables like %OMNIHOME% or $OMNIHOME can be used. The Linux and UNIX filename convention, with the / forward slash to delimit the path, is also used by Windows.

    3. Add the rules reference in the order in which it should be processed. 

        include "<path_to_rules_file>/
ibm-TIVOLI-CANSYSSG-MIB.include.snmptrap.rules"

      This statement should be added in the rules file in the location where it should be processed. For example, if adding the include to the default mttrapd.rules file, you would want the default rules to first "Check if an SNMPv2 trap and convert to SNMPv1 style tokens". The next block of code in the default mttrapd.rules handles Generic traps. The include statement for the ibm-TIVOLI-CANSYSSG-MIB.include.snmptrap.rules should go after this, possibly as the last line of mttrap.rules. You will best know where to include the rules if you are familiar with the SNMP Probe and your event space.

  3. Review and edit the SNMP Probe properties file:

    1. Open $OMNIHOME/probes/arch/mttrapd.props in a text editor.

    2. Set the Protocol property to "UDP" or "ALL". Tivoli Monitoring SNMP alerts are sent using UDP.

    3. Set the RulesFile property if the default rules file for the probe is not mttrapd.rules.

    4. Set the MIBDirs property to the path where the mib files will reside.

  4. Make the Tivoli Monitoring mib files available to the SNMP Probe:

    1. Locate the mibs directory on the Tivoli Monitoring installation media.

    2. Copy canbase.mib and cansyssg.mib, to the mib location specified in mttrapd.props by the MIBDirs property.

    3. The canbase.mib and cansyssg.mib include some common SNMP mibs. These mibs must also be available to the SNMP probe:
      RFC1155-SMI
      RFC1213-MIB
      SNMPv2-TC
      RFC-1212
      RFC-1215
      If these mibs are not already present in the location specified in mttrapd.props by the MIBDirs property, they are publicly available and can be downloaded from the Internet.

  5. If you are integrating Tivoli Monitoring, Tivoli Business Service Manager, and Netcool/OMNIbus, the Netcool/OMNIbus SNMP Probe rules should also include an additional rules file, tbsm_snmp_event.rules, that sets the OMNIbus BSM_Identity attribute. The mibs/sample_rules/omnibus/tbsm directory on the Tivoli Monitoring Agent installation media (V6.2.2 and higher) contains the tbsm_snmp_event.rules file and the readme file that describes how to use it with the SNMP Probe and how to use the itm_tbsm_update.sql file to add the BSM_Identity attribute to the Netcool/OMNIbus database schema.


Results

You should now have these files installed on the probe system:


What to do next

To activate the new rules and begin receiving alerts from Tivoli Monitoring agents, recycle the SNMP Probe.


Parent topic:

OMNIbus configuration for SNMP

Related information:

IBM Tivoli Network Management documentation
IBM Tivoli Netcool/OMNIbus: Installing, upgrading, and uninstalling
IBM Tivoli Network Manager Transmission: Integrating with Netcool/OMNIbus
IBM Tivoli Netcool OMNIbus: Setting up probes to use the updated rules files
IBM Tivoli Netcool OMNIbus: Monitoring and managing events

+

Search Tips   |   Advanced Search