Pardon me, but I think you have a terminological problem in describing just
netmon not initializing is not the same thing as netmon failing. Neither
is netmon not noticing something proof of failure. It might be simply
misconfiguration, either in the seed file, the SNMP polling parameters, or
netmon not initializing would mean that you never see the message in
serversetup that it has initialized. If you do, then it is up and fully
netmon failing would mean that the daemon, or one its threads, is not
running. This is evidenced by a failure message in the nv.log or the
failure shown in the drwatson32.log. You might also see a trap in the Event
Browser that netmon has gone away unexpectedly, or you might also get a
popup that the daemon failed while the NetView GUI is up. But if none of
these occurred and your refresh the status with serversetup, and netmon
still shows up, then it's up.
But netmon not noticing something is different than both these cases, and
depending on what it did not notice, might mean that your configuration
needs attention. Even if it's not a configurational issue, it might still
require a netmon.trace to figure out. But the netmon trace is difficult
to read unless you have some experience.
For any of these cases, I think you should contact Support so they can help
you determine just what went wrong. That's why they are there.
Level 3 Support for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group
Sent by: <firstname.lastname@example.org>
[nv-l] netmon not Initializing
Please respond to
I am running netview 7.1.4 for windows with fp3 recently I found out that
Netmon is failing occasionally ,some serious problems was left unnoticed by
netview ,in the ovstatus it shows running ,when I restarted the server it
is fine ,but after some time the problem is still there ,could any one
help me out to overcome this ?