Question & Answer
Question
MIB Manager : How are the exported rules files used?
Answer
The files exported by MIB Manager include a README.txt that explains how to merge and use the exported rules files.
Here is an example merge of some IBM MIBs for NcKL 4.2:
To create the NcKL rules file for the given MIBs:
- IMPORT MIBS into MIB Manager
Note: Usually it is easiest to remove all the mibs from MIB MANAGER, then import the base mibs, and then import the custom mibs.
- EXPORT MIBS as NcKL 3.0
<date&time>-nckl_3_0
- Zip up the directory for copying to the probe server:
Review the README.txt file:
MIB Manager NCKL Format Rulesfiles
--------------------------------
Instructions For Use:
The rulesfile was designed for use with the NCKL 3.x format rules.
The current IBM recommended and supported rulesfile format
is NCKL. It is highly recommended all users make use of the NCKL
format if at all possible.
To use this NCKL format rulesfile simply place includes for the two
per vendor master files into your snmptrap.rules file.
Those files are named:
<vendor>/<vendor>.m2r.master.include.lookup
<vendor>/<vendor>.m2r.master.include.rules
If there already exists vendor specific NCKL rules for the vendor
then simply include the above two m2r.master files in
<vendor>/<vendor>.master.include.lookup
<vendor>/<vendor>.master.include.rules
and in this case the <vendor>/<vendor>-preclass.snmptrap.lookup
file should be merged into the existing preclass lookup file.
-----------------------------------------------------------------------------
To install on the probe server:
- Unpack the zip file in a temporary directory
unzip <date&time>-nckl_3_0.zip
cd <date&time>-nckl_3_0
ls -R1 ibm
ibm:
ibm-IBM-3200-MIB_eventBrowserLogin.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventBrowserLogin.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventBrowserLogout.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventBrowserLogout.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventDoorOpen.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventDoorOpen.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventDriveError.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventDriveError.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventFaultPosted.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventFaultPosted.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderConfigChange.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderConfigChange.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderOK.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderOK.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderPasswordChange.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderPasswordChange.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderRetriesExcessive.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventLoaderRetriesExcessive.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventMailSlotAccessed.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventMailSlotAccessed.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventRequestDriveClean.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventRequestDriveClean.user.include.snmptrap.rules
ibm-IBM-3200-MIB_eventStatusChange.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_eventStatusChange.user.include.snmptrap.rules
ibm-IBM-3200-MIB_ibm3200Event.adv.include.snmptrap.rules
ibm-IBM-3200-MIB_ibm3200Event.user.include.snmptrap.rules
ibm-IBM-3200-MIB.include.snmptrap.lookup
ibm-IBM-3200-MIB.include.snmptrap.rules
ibm-IBM-3200-MIB.sev.snmptrap.lookup
ibm-IBM-ENETDISPATCHER-MIB.adv.include.snmptrap.rules
ibm-IBM-ENETDISPATCHER-MIB.include.snmptrap.lookup
ibm-IBM-ENETDISPATCHER-MIB.include.snmptrap.rules
ibm-IBM-ENETDISPATCHER-MIB.sev.snmptrap.lookup
ibm-IBM-ENETDISPATCHER-MIB.user.include.snmptrap.rules
ibm-IBM2210-MIB.adv.include.snmptrap.rules
ibm-IBM2210-MIB.include.snmptrap.rules
ibm-IBM2210-MIB.sev.snmptrap.lookup
ibm-IBM2210-MIB.user.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapsels.adv.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapsels.user.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapsfr.adv.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapsfr.user.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapssys.adv.include.snmptrap.rules
ibm-IBMIROC-MIB_ibmIROCtrapssys.user.include.snmptrap.rules
ibm-IBMIROC-MIB.include.snmptrap.rules
ibm-IBMIROC-MIB.sev.snmptrap.lookup
ibm-IBMTCPIPMVS-MIB.adv.include.snmptrap.rules
ibm-IBMTCPIPMVS-MIB.include.snmptrap.rules
ibm-IBMTCPIPMVS-MIB.sev.snmptrap.lookup
ibm-IBMTCPIPMVS-MIB.user.include.snmptrap.rules
ibm-IPSECV1-MIB.adv.include.snmptrap.rules
ibm-IPSECV1-MIB.include.snmptrap.rules
ibm-IPSECV1-MIB.sev.snmptrap.lookup
ibm-IPSECV1-MIB.user.include.snmptrap.rules
ibm-L2TV1-MIB.adv.include.snmptrap.rules
ibm-L2TV1-MIB.include.snmptrap.lookup
ibm-L2TV1-MIB.include.snmptrap.rules
ibm-L2TV1-MIB.sev.snmptrap.lookup
ibm-L2TV1-MIB.user.include.snmptrap.rules
ibm-preclass.include.snmptrap.rules
ibm-preclass.snmptrap.lookup
ibm.m2r.master.include.lookup
ibm.m2r.master.include.rules
- Interactively copy the files to the vendor specific directory
- Check and compare the pre-class files
check differences
diff /opt/NcKL_42/rules/include-snmptrap/ibm/ibm-preclass.include.snmptrap.rules ibm-preclass.include.snmptrap.rules
diff /opt/NcKL_42/rules/include-snmptrap/ibm/ibm-preclass.snmptrap.lookup ibm-preclass.snmptrap.lookup
- Add in the master files
cd /opt/NcKL_42/rules/include-snmptrap/ibm
vim ibm.master.include.lookup
# NcKL lookups
include "$NC_RULES_HOME/include-snmptrap/ibm/ibm.m2r.master.include.lookup"
#EOF
vim ibm.master.include.rules
# NcKL Includes
include "$NC_RULES_HOME/include-snmptrap/ibm/ibm.m2r.master.include.rules"
#EOF
- Check the rules files syntax using nco_p_syntax
$OMNIHOME/probes/nco_p_syntax -rulesfile $NC_RULES_HOME/snmptrap.rules -server NCKL4
- Make any required modifications
vi ibm.m2r.master.include.lookup
#include "$NC_RULES_HOME/include-snmptrap/ibm/ibm-preclass.snmptrap.lookup"
The rules files can then be used with the working mttrapd probe.
Notes:
You should always perform rules file work after making a backup of the rules files, and preferably check the edits on a test system, before deployment.
Once installed, the MIB Manager, loaded with the vendor MIBs can be used to send test traps to the MTTrapd probe to confirm the rules files process the traps as required.
[{"Product":{"code":"SSSHTQ","label":"Tivoli Netcool\/OMNIbus"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Not Applicable","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.4.0;8.1.0","Edition":"Edition Independent","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21700105