Well, if the mismatch is in a Smartset, I don't worry about it too
much (probably should), I just 'delete the egg' to get it re-evaluated,
or sometimes kill the collmap application and restart it (there is an
option to do this under Administer....Start Application - which should
be a clue to you).
If it is in the regular IP topology, and I have a r/w map open, and it
is not synchronizing, trying to catch up with those changes, then I
do worry a lot. For voodoo I would do an ovotopofix (to udate the
times and force synchronization) and restart the map to try to synch
things up.
Then if the color on the map does not match the status in the object
or topology databases, I would call Support.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
Detroit
William.Stringfellow@bankofamerica.com@tkg.com on 03/19/2001 02:17:49 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
Sent by: owner-nv-l@tkg.com
To: IBM NetView Discussion <nv-l@tkg.com>
cc:
Subject: [NV-L] RE: Netview discovery status
Leslie,
Even when netmon updates the status to "normal" we still see objects
displayed in the GUI as down. Is there any 1 common error that causes
this,
or is it case-by-case specific? i.e., is there a short and easy fix or do
we have to open cases with support as they occur?
Thanks for all of the information that you, James, and the other
folks on the list have provided,
Bill
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|