21.9 Blocking incidents using the trapFilter.conf file
Note the following if the number of incidents flowing through your NNMi management server reaches a rate that causes NNMi to block newly arriving incidents:
NNMi will generate 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.
Use either of the following methods to reduce the number of incidents:
Use the nnmtrapd.conf file to block incidents from entering NNMi by reducing the volume of incident traffic.
- Important
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. By using 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.
Use trapFilter.conf to block incidents earlier in the NNMi event pipeline, preventing the blocked incidents from being analyzed for trap rate calculations and from being stored in the NNMi trap binary store.
- Note
Adding device IP addresses or OIDs to the trapFilter.conf file enables you to block high-volume incidents and avoid problems caused by a high volume of incidents.
For details, see the trapFilter.conf Reference Page and the nnmtrapconfig.ovpl Reference Page.