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?
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
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?
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l