Hello again, Giscard;
If you desire to log those events and to display them only for some selected
nodes, you can copy each event to create a
new one (with the same Specific ID as that of its source) and modify them so
that Source can contain just those nodes.
Let the events from these nodes be displayed and logged if desired. The
original events can be then set to Don't log or
display, simply discarded, or anything you want.
Best regards,
Vladimir.
giscard.fuchs@GECITS-EU.COM wrote:
> vladimir, james,
>
> 1. as described: ovevents.log (max. only 2MB) and events-display (max
> only
> 1000).
> the maximum values are not enough for our situation.
>
> 2. via xnmtraps i can only block out totally the specific traps.
> i can't filter for example the server node-down traps (or only a list or
> collection of ip-addresses)
>
> 3. this is exactly what i was trying to do (i even included the rule:
> see
> below). unfortunately it doesn't work :-(
> james, what do you mean by the expression "hand your events windows"?
> we are using the rule block.rs as described below and we can't see a
> difference to forwardall.rs.
>
> 4. please no dynamic filtering: ovevents.log is still clogged! the
> important traps are still purged out! this is only a solution for the
> display.
>
> >To change the ruleset of the primary workspace you have to modify
> /usr/OV/app-defaults/Nvevents
> this is i was looking for - but the rule itself still doesn't work.
>
> Mit freundlichen Gruessen - Yours sincerely
>
> Giscard Fuchs
> CompuNet Berlin
> System Engineering
> Mariendorfer Damm 1-3, 12099 Berlin, Germany
> Phone: +49 30 70785-147, Fax: +49 30 70785-130, Mobile: 0172/8212409
> Internet: giscard.fuchs @ gecits-eu.com
>
>
>
>
--
Vladimir Petr
DATASYS
-----------------------------
|