6.1.7 Incident suppression, enrichment, and dampening

NNMi provides a rich feature set for deriving the most value from incidents. For each incident type, you can use the following incident configuration options to define specifically whether an incident is of interest:

• Suppression

  An incident that matches the suppression configuration does not appear in the NNMi console incident views. Incident suppression is useful for incidents (such as SNMPLinkDown traps) that are important for some nodes (routers and switches, for example) but not for others.

• Enrichment

  When an incident matches the enrichment configuration, NNMi changes one or more incident values (for example, severity or message) according to the contents of the incident. Incident enrichment is useful for processing traps (for example, RMONFallingAlarm) that carry the distinguishing information in the trap varbinds (payload).

• Dampening

  When an incident matches the dampening configuration, NNMi delays activity (such as refreshing the display of the incident view or execution of an action) for that incident for the duration of the dampening interval. Incident dampening provides time for the NNMi Causal Engine to perform root cause analysis on the incident, which is useful for providing fewer, more meaningful incidents on the NNMi console.

For each incident type, NNMi provides the following levels of configuration for suppression, enrichment, and dampening:

• Interface group settings

  Specify incident behavior when the source object is a member of an NNMi interface group. You can specify different behavior for each interface group.

• Node group settings

  Specify incident behavior when the source object is a member of an NNMi node group. You can specify different behavior for each node group.

• Default settings

  Specify default incident behavior.

The following is the procedure for determining the behavior of a specific incident for any incident configuration area (suppression, enrichment, or dampening):

1. Check the interface group settings:

   • If the source object matches any interface group settings, carry out the behavior defined in the match with the lowest ordering number and stop looking for a match.

   • If the source object does not match any interface group settings, go to step 2.

2. Check the node group settings:

   • If the source object matches any node group settings, carry out the behavior defined in the match with the lowest ordering number and stop looking for a match.

   • If the source object does not match any node group settings, go to step 3.

3. Perform the actions defined in the default settings, if any.

To Page Top