19.4 Blocking incidents using the trapFilter.conf file
Suppose the number of incidents flowing through your NNMi management server reaches a rate that causes NNMi to block newly arriving incidents. When this happens, NNMi generates a TrapStorm incident, indicating that incidents are being blocked. NNMi might also generate a major health message indicating that the incident rate is high and incidents are being blocked.
You can use one of the methods described below to block incidents so that their number does not reach a certain rate.
- Using the nnmtrapd.conf file:
-
Use the nnmtrapd.conf file to block incidents from entering NNMi in an attempt to reduce the incident traffic. However, when 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. When you use the nnmtrapd.conf file approach, you only stop incidents from being created or stored in the database. For details, see the nnmtrapd.conf Reference Page.
- Using the trapFilter.conf file:
-
This is a better solution to this problem than using the nnmtrapd.conf file. NNMi provides a filtering mechanism that blocks 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. By adding device IP addresses or OIDs to the trapFilter.conf file, you can block these high-volume incidents and avoid incident volume problems. For details, see the trapFilter.conf Reference Page and the nnmtrapconfig.ovpl Reference Page.