I must still be confused, or perhaps I don't understand your setup.
The question I have is "suppress them from where?". The event display?
Technically speaking NetView cannot suppress traps, only prevent them from being
displayed or logged. They will still be processed. Any traps sent to NetView
will still be pulled in by trapd (he has no choice) and then sent to all
connected applications, including netmon, snmpCollect, ipmap, and so on. You
cannot do anything about that. And they will still all be in trapd.log. By
default MLM status traps are all "Log Only" anyway, or so I thought, so they do
not normally go to the event display. Did you change that? If so, then you
could use a ruleset or a filter to suppress them, but as these are the same
traps that will be sent later, you would have to apply the filter/ruleset only
when you knew the MLMs were going to be rebooted, else they would always be
filtered.
So unless I miss my guess, you should just make them "Log Only" again if they
are not. netmon gets them from trapd and "re-issues" them as netmon traps if
required, and those are what you should see in the event display.
Or am I still missing something?
James Shanks
Tivoli (NetView for UNIX and NT) L3 Support
Peter Cho <chop AT tdbank DOT ca> on 05/05/2000 04:33:23 PM
Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
To: IBM NetView Discussion <nv-l AT tkg DOT com>
cc: (bcc: James Shanks/Tivoli Systems)
Subject: Re: [NV-L] MLM floods NetView with interface up traps
MLMs are not booted at the same time.
The problem with MLM is that it sends interface up traps for everything
it has in it's collection the first time it comes up. This is the part I was
asking about. I wanted a way to suppress the flood of traps, just for
the MLM startup.
James_Shanks AT tivoli DOT com wrote:
> As far as I know, what you are describing is normal behavior. When an MLM is
> rebooted, it starts from ground zero and sends status traps on all the nodes
it
> monitors to NetView. That's what it is supposed to do. It doesn't have a
> topology database like netmon does to store this information in, so it sends a
> level-set to netmon. It has no idea what happened to the nodes it monitor
when
> it is down, whether netmon was able to take over the polling successfully or
> not, so it has to start somewhere. Are you rebooting all your MLMs at once or
> something? If not, then the question becomes, why have MLMs monitor status in
> the first place if you don't want them to send the traps?
>
> James Shanks
> Tivoli (NetView for UNIX and NT) L3 Support
>
> Peter Cho <chop AT tdbank DOT ca> on 05/05/2000 02:03:12 PM
>
> Please respond to IBM NetView Discussion <nv-l AT tkg DOT com>
>
> To: IBM NetView Discussion <nv-l AT tkg DOT com>
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: [NV-L] MLM floods NetView with interface up traps
>
> Hello,
>
> Using NT MLMs with AIX NetView 5.12. When our MLM's are
> rebooted, it floods NetView with hundreds of interface up traps.
>
> Don't want to filter the trap as our network people want to see it.
> Does anyone have a work around? Is there a ruleset to handle this?
>
> Thanks,
>
> Peter
>
> _________________________________________________________________________
>
> NV-L List information (unsubscribing, policies, posting, digest version,
> searchable archives): http://www.tkg.com/nv-l
>
> _________________________________________________________________________
>
> NV-L List information (unsubscribing, policies, posting, digest version,
> searchable archives): http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|
