21.8.3 Configuring timeframes within which the Causal Engine stops accepting traps

When large areas of a network are unavailable at regular and predictable times, NNMi enables you to moderate the Causal Engine analysis load by inhibiting delivery of traps to the Causal Engine. To inhibit delivery of traps, you configure as an NNMi administrator the timeframes within which the NNMi Causal Engine is to stop accepting traps from the event system.

Important

This feature does not interfere with traps delivered to the NNMi console.

Traps that are delivered to the Causal Engine are used to trigger the State Poller to poll a node sooner than the schedule set by the State Poller polling policy. When you inhibit delivery of traps, NNMi must wait until the scheduled polling interval before obtaining updated information from the State Poller. In all cases, the NNMi Causal Engine reaches the same conclusion with or without traps by using status flows from the NNMi State Poller.

To configure times during which the Causal Engine is to stop accepting traps:

1. Create the following file:

   • Windows: %NNM_PROPS%\nms-apa.properties

   • Linux: $NNM_PROPS/nms-apa.properties

2. Add the following content to the created file:

   PROPERTY NAME: com.hp.ov.nms.apa.trapGateSchedule

   Use the following examples as guidelines:

   In the following example, traps flow at midnight, are inhibited at 8:30 a.m., resume flowing at 10:00 a.m., and then are inhibited again at 4:30 p.m.:

   com.hp.ov.nms.apa.trapGateSchedule = ENABLE_APA_TRAPS 08:30 10:00 16:30

   In the following example, traps are inhibited at midnight, begin flowing at 8:30 a.m., are inhibited at 10:00 a.m., and then flow again at 4:30 p.m.:

   com.hp.ov.nms.apa.trapGateSchedule = DISABLE_APA_TRAPS 08:30 10:00 16:30

3. Save your changes.

4. Restart NNMi by running the following commands:

   ovstop
   ovstart

To Page Top