Whenever I see odd behavior in a collection based on status, I check the
object info (Tools..
Display Object Info) for the node, looking at the fields on which the
collection is based. That
usually clarifies what is going on. Keep in mind that there are a couple of
problems with
status in collections that we all hope are fixed in the 5.1.1 patch. Other
times it is due to
a less-than-optimal collection definition.
When you say bright green, do you mean the Acknowledge color?
Also, is it possible that the map just has not caught up with object status
yet, like is the system
constrained? Sometimes it can take a few seconds in that case.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
(248) 552-4968 Voicemail, Fax, Pager
---------------------- Forwarded by Leslie Clark/Southfield/IBM on 02-15-99
08:41 PM ---------------------------
Peter Hadamovsky <Peter.Hadamovsky@DEBIS.COM> on 02-15-99 03:23:32 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on
NetView <NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: Leslie Clark/Southfield/IBM)
Subject: collection problem
Hi folks,
We ran into a problem which seems really awkward:
We built a collection group that contains router which aren't alive
anymore. It is based on the information that the device isRouter and
isCritical.
The failed nodes get collected and presented in the colour red - that's
ok, but when they reach the operational status normal again they change
to green - then the awkward thing happens:
some disappear (which is correct) and some still remain in the bright
colour green in the collection group which makes a lot of confusion!
Does anybody have any idea?
Best regards
Peter Hadamovsky
--
---------------------------------------------------------------------------
mailto:Peter.Hadamovsky@debis.com
GSS GmbH
Office: Fasanenweg 9 70771 Leinfelden-Echterdingen
Phone/Fax: +49 711 972 -3525 / -1930
Mobile: +49 171 6943 156
---------------------------------------------------------------------------
-
|