>From what I can see in the logic, if you are using the GUI to build the
collection, I think it should be
'IP Status' = Critical
and
'isNode' = TRUE
or
'IP Status' = Marginal
and
'isNode' = TRUE
To me that would fix it.
Regards,
Philip
"Hill, Channing" <CHill@BBandT.com> on 04/12/2000 10:20:55 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: "'IBM NetView Discussion'" <nv-l@tkg.com>
cc: (bcc: Philip Guerra/Tivoli Systems)
Subject: RE: [NV-L] Collections Problem
We use the same collection and have the same problem. I've noticed that if I
unmanage and then manage a device with these symptoms that it will leave the
collection.
Channing Hill
EMS Analyst I
chill@bbandt.com
> BB&T
Wilson, NC 27893
> -----Original Message-----
> From: Jewan, P. (Pritesh) [SMTP:PriteshJ@nedcor.com]
> Sent: Wednesday, April 12, 2000 10:42 AM
> To: 'nv-l@tkg.com'
> Subject: [NV-L] Collections Problem
>
> Hello People,
>
> We have built a collection called 'Marginal Devices' for the support desk.
> The rules of the collection states that if a device becomes marginal or
> critical then that device must be part of the collection. The rules are as
> follows:
>
> 'IP Status' = Critical
> or
> 'IP Status' = Marginal
> and
> 'isNode' = TRUE
>
> The collection seems to work fine however sometimes there are devices that
> are part of the collection but are green is colour. If we try pinging all
> the interfaces and demand polling the device, according to netmon,
> everything is up. However if we display the devices object properties, the
> 'IP Status' field is marginal even though all the interfaces are up. My
> understanding for the device still been in the collection is that nvcold
> reads the object properties of which the IP Status is marginal and
> therefore places it in the collection according to the collection rules.
> If netmon has demand polled the device and knows that all the interfaces
> are up why has the object database still got the device as Marginal and
> this condition stays this way for upto 2 days sometimes. Does anyone have
> any ideas on where the problem might be and how can I trouble shoot where
> exactly in the process the ovw database should be getting updated and why
> it isn't ?
>
> Any help/suggestions would be greatly appreciated
>
> Regards
> Pritesh Jewan
> ESM - Technology & Operations Division
> Nedcor Bank Limited (South Africa)
>
> Tel : +27 - 011 - 320 5417
> Cell: +27 - 82 570 5046
> Fax : +27 - 011 - 8814743
> e-mail : priteshj@nedcor.com
>
_________________________________________________________________________
NV-L List information (unsubscribing, policies, posting, digest version,
searchable archives): http://www.tkg.com/nv-l
|