The seedfile is part of the daemon configuration meaning that whenever
the daemon is started it checks its config and loads the proper
settings. So your netmon daemon must have used the seedfile or you
have a bigger problem.
What I am guessing is that you did not limit your seedfile to only the
devices you listed in it. Basically, you should have listed all of
your devices one per line and then at the end of your seedfile place
something like this:
3.3.3.*
This will tell the netmon daemon to stop looking for devices once it
hits this bogus address.
Hope this helps...
______________________________ Reply Separator _________________________________
Subject: [NV-L] Unbridled Netmon
Author: "IBM NetView Discussion" <nv-l@tkg.com> at smtplink
Date: 2/23/01 11:23 AM
Hi All,
I'm hoping someone here can confirm or refute my suspicions regarding the
cause of the following symptom(s) in my AIX 4.3.3, NV6.0.1 environment.
Recently my Netmon took off on an unbridled (sans seedfile) voyage to
discover the world, earning me the new title of "Christopher Columbus",
apparently choking our DNSs and firewall in the process, and discovering way
too much undesirable stuff.
I believe I had stopped Netmon and absentmindedly left it down. A collegue
noticed Netmon wasn't running and restarted it after becoming root with
"su", not "su -". Root's .profile sources the Tivoli environment, as does
this user's .profile. I suspect that "su" didn't get the Tivoli environment
set, thus netmon didn't know to use the seedfile and was able to run wild.
Are my suspicions correct or even on track?
BTW, after reigning in Netmon I cleaned up the mess by restoring a recent
tarball of /usr/OV/databases. Stuff DOES happen.
Thanks in advance.
Mark A. Scherting
State of Montana
Information Services Division
(406) 444-0117
mscherting@state.mt.us
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|