IBM E027SLL-H Troubleshooting Guide - Page 258

Table 21. Monitoring events in Netcool/OMNIbus do not have expected values (continued) Cause Other EIF probe rules files are modifying OMNIbus attributes for monitoring events Resolution 1. Check if the itm_event.rules file is including the itm_custom_override.rules file and if the customizations in that file are causing OMNIbus attributes to be set inappropriately. 2. Check the other rules files included by the EIF probe's master rules file (tivoli_eif.rules). If the tivoli_eif_virtualization_pt2.rules or predictive_event.rules files are uncommented in tivoli_eif.rules: v verify that you are using a version of tivoli_eif.rules that includes these two files after the itm_event.rules file v verify that you are using the versions of tivoli_eif_virtualization_pt2.rules or predictive_event.rules from Netcool/OMNIbus 7.3.1 Fixpack 2 or later fixpack or Netcool/OMNIbus 7.3.0 Fixpack 6 or later fixpack. EIF slot customizations are changing the values of EIF slots that are mapped to OMNIbus attributes Note: If you change the probe rules files, you must restart the EIF probe. Use the Tivoli Enterprise Portal Situation Editor to check if EIF slot customization has been configured for a situation and is setting slots to invalid values. The Netcool/OMNIbus ObjectServer default duplication trigger is processing monitoring events and setting the Summary attribute to the situation name when events are acknowledged or deacknowledged. For information on which EIF slots should not be customized, see the topic "Default mapping of situation events to OMNIbus events" in the IBM Tivoli Monitoring Installation and Setup Guide. Verify that the default duplication trigger has been configured to ignore events from IBM Tivoli Monitoring. See the topic "Changing the default deduplication trigger" in the IBM Tivoli Monitoring Installation and Setup Guide for more details. 240 IBM Tivoli Monitoring: Troubleshooting Guide