Words and Phrases
Display an SNMP Trap as a Root Cause Incident
SNMP traps normally appear as symptoms rather than as root cause incidents. However, there might be times when you want an SNMP trap to appear as a root cause incident. For example, you might want an HSRP state change (cHsrpStateChange, 1.3.6.1.4.1.9.9.106.2.0.1) trap to be listed as a root cause. This trap might occur when the hot standby has gone down indicating the system is at risk if there is a failover.
Note To reduce "noise" associated with duplicate incidents, NNMi changes the incident Correlation Nature to 
Symptom for any user-defined Root Cause (User Root Cause) incidents that exceed the rate or de-duplication threshold:
-
Root Cause value = determined by NNMi's Causal Engine -
User Root Cause = your NNMi administrator configured NNMi to always treat this Incident as Correlation Nature: Root Cause
To display an SNMP Trap Incident as a Root Cause incident:
Select Root Cause 
in the SNMP Trap Incident Configuration form.
The next time the incident occurs, the Correlation Nature attribute value changes to Root Cause.
To no longer display an SNMP Trap Incident as a Root Cause incident:
Clear Root Cause 
in the SNMP Trap Incident Configuration form.
The next time the incident occurs, the Correlation Nature attribute value changes to Symptom.