26.5.3 Setting up blocking, ignoring, or disabling of traps

NNM is equipped to perform various levels of event processing, such as the following:

• Blocks traps when they come into ovtrapd.

• Processes traps or events labeled IGNORE, but does not save or display them.

• Saves and processes (correlates) events labeled LOGONLY, but does not display them.

• Saves events in categories, processes and displays them.

• Displays traps arriving without settings as No format in trapd.conf for ... in the alarm browser, and saves them in the database.

NNMi has a much simpler method. It does not save, process, or display disabled events or traps. NNMi fully saves, processes, and displays enabled events or traps. Events that are not set in NNMi are blocked.

1. Determine whether customization that ignores traps or customization that sets traps in LOGONLY is used.

2. Check whether NNM uses a trap-filtering mechanism (ovtrapd.conf, which was new in NNM 08-00).

   

3. In the NNMi console, from the Configuration workspace, choose Incident Configuration.

   Find events you do not want to receive or display, and clear the Enabled check box for these events.

4. To block traps from certain IP addresses, edit the following file and update NNMi by using the trap-filtering information from NNM:

   • Windows: %NnmDataDir%shared\nnm\conf\nnmtrapd.conf

   • Linux: $NnmDataDir/shared/nnm/conf/nnmtrapd.conf

5. Enable trap blocking by running the nnmtrapconfig.ovpl command with a trap-blocking rate and a threshold value specified.

   For details about how to use this command, see the nnmtrapconfig.ovpl Reference Page.

To Page Top