A common problem with Netview and TEC is the fact that many unnecessary Events are sent to TEC, e.g. Node Down and Node Up events from devices, that are only down for a very short amount of time.
One way to minimize these unnecessary events is to play with netmon parameters. But this can be done only in a very limited way and care should be taken. Since netmon is not multithreaded it could have difficulties processing all objects in time when the polling parameters are set wrong.
So with standard polling times and retries, it is quite common that TEC gets lots of Node Down events, which are resolved after the next netmon polling cycle because the Node came up again. This can be especially annoying when you have a TTS system connected to TEC and all these Node Down events trigger Incidents.
This example rule delays Node_Down events by 6 minutes with a Reset On Match. So if within 6 minutes the Node_Up is received the Node_Down is discarded.
It also insures, that only Node_Up events are sent to TEC in case the corresponding Node_Down event was sent to TEC.
--
WolfgangBergbauer - 22 Oct 2004
- Netview_Rule.gif:
Netview_Rule.gif 