Re: Filters / Rulesets
Usually the best way to handle this is to:
- only discover things that you want managed (put in a discovery filter so
that only SNMP devices are discovered, assuimng your end user PCs are not
SNMP capable, or filter discovery by the SNMP OID if they are)
- or discover PCs as unmanaged (based on lack of SNMP support or OID).
Then they will not be polled by Netview, and it will not generate events
Saves you lots in Netview CPU, memory, etc.
John Mayeur wrote:
> AIX 4.3.2
> Netview 5.1
> Framework 3.6.1
> I am replacing a Netview 3.x server with a new one ases described above.
> My company basically uses the product for up/down status notification
> only. It monitors routers, RS/6000's, AS/400's, file/print servers,
> hubs and switches. None of these hosts are configured to send traps to
> the new installation. I have all the components installed and working
> and I have a map built with all the submaps needed.
> My questions are concerning filters and rulesets. When Netview is
> started the Events app is running in the Control Desk. It is constantly
> scrolling messages for Node Up/Down, Interface Up/Down for hosts I don't
> need to monitor (end user PCs). Since there are no hosts configured
> (yet) to send traps, I assume these are being generated by the polling
> process? My goal is to show only events/traps for the nodes needed. I
> have noticed that the Events app starts with the forwardall.rs ruleset.
> Should I modify this ruleset or create a new one? How do you start the
> Events app with a different ruleset by default? Can you have multiple
> rulesets active for the Events app (ESE.automation)? Or should a filter
> block all of the unwanted events first. Which comes first the filter or
> the ruleset? I would like to start by filtering (exclude) all events
> that come from hosts that have an IP address issued from DHCP if
> possible (because I know the ranges). Would there be a better selection
> criteria? I have read the docs on this but it is still unclear to me.
> Could someone please explain the "flow" of events and traps as well as
> tips to efficiently handle them.
> John Mayeur
> Network Engineer