Blocking Incidents using the nnmtrapd.conf and trapFilter.conf Files

If the number of incidents flowing through your NNMi management server reaches a rate that causes NNMi to block newly arriving incidents, note the following:

• NNMi generates a TrapStorm incident, indicating that incidents are blocked.
• NNMi might also generate a major health message indicating that the incident rate is high and incidents are being blocked.

To reduce the number of incidents, use either of the following methods:

• Use the nnmtrapd.conf file to block incidents from entering NNMi in an attempt to reduce the incident traffic.

  Note If you use the nnmtrapd.conf file approach, NNMi still uses these incidents to calculate the trap rate and to write to the trap binary store. By using the nnmtrapd.conf file approach, you only stop incidents from being created or stored in the database.

  See the nnmtrapd.conf reference page, or the Linux manpage for more information.

• Use trapFilter.conf to block incidents earlier in the NNMi event pipeline, preventing these incidents from being analyzed for trap rate calculations or from being stored in the NNMi trap binary store.

  Tip By adding device IP addresses or OIDs to the trapFilter.conf file, you can block these high-volume incidents and avoid incident volume problems.

  See the trapFilter.conf reference page, or the Linux manpage for more information.