First, make sure netmon is running, and hasn't died. Then check to see
if it has fallen far behind. You can do this with 'netmon -a 3' (for
pinging list)
and 'netmon -a 4' (for configuration polling list) on unix. It puts a
report in
/usr/OV/log/netmon.trace that shows what it is doing. If it is too busy to
answer,
that's a clue too. A wild guess is that it is being slowed down by poor
name resolution. An ovotopofix removed all of the hints and partial nodes,
but now those are back and netmon is trying to look up the names of those
hints, and going very slowly. You can see this if you turn on tracing at
startup
of netmon.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
Sebastian.Szumczyk@natned.com.pl@tkg.com on 11/13/2000 07:33:42 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: nv-l@tkg.com
cc:
Subject: [NV-L] netview doesn't change status of active/non-active
devices!
one more thing,
netview reported that one device is not reachable so it changed color for
that device (from green to red). after node is connecting to network
properly (test ping works) netview can't change status of that device
(still
non-active!). when i would like to poll it manually i can't (netview
doesn't
respond for that:-( ). i wrote that problem with manual polling is solved,
but unfortunately it isn't:-(.
do you mind if i ask you for help?
bast3k
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|