Id like to take a stab at this...
I have witnessed this happen many times. My environment is a nightmare.
All of what I am going to discuss was already in place before I got here.
The design for my NMS is to use the Netview GUI (OVw) to display proprietary
status of objects to the operator on top of Netviews 'IP Status' for that
node. Example, down-trap-1 (our own MIB) comes in and we change the color
of the object of the node to red (Critical), even though that node has
network connectivity. Netviews 'IP Status' has not changed (use nvUtil p to
show this) but the object icon is red. During some development I had a
collection of these objects based on the 'IP Status'. So what I would see
happen was the objects icon red, but is not being displayed in my collection
(rule was 'IP Status' = 'Warning' || 'Major' || 'Critical'). The internals
behind this is Netview (ipmap, OVw, netmon?) knows this objects IP Status to
be healthy, and netmon <i>does not care what the icons color is</i>, since
netmon/ipmap knows its IP Status has not changed, why should it take other
action. To go further, the representation of that symbol/object in OVw
(ovw.h, OVwSymbolInfo, OVwObjectInfo) has a OVwStatusType value representing
the icon color. Netview is not 'defined' to have icon color represent IP
status. netmon/ipmap will set this status when there is a change, just as I
do when I get a trap-down/up evet. This is in no way a flame, just my
observations as a user in an 'unfriendly environment'.
What does this mean to you?
Maybe you have an application setting the icon color and you dont know it?
What are the specific rules on your Smartset? I am using netview 5.1.3 so
my results may differ somewhat to yours, but unless there have been some
serious underlying changes, I would assume this to be the case.
Never-the-less, take my info with a grain of salt and see if you can apply
it to your situation.
FWIW, I am still in the process of selling to my higher-uppers that the
current implementation is horribly incorrect, from many standpoints. Dont
get me started on our switchover design ;). It is my opinion the proper
solution for this environment is to decouple the proprietary aspect of the
node into its own symbol/object and have our specific traps change the color
of that symbol instead of stepping on OVw's (ipmap, netmon, etc) toes.
Hope this helps,
Jason
-----Original Message-----
From: Jim Corrigan [mailto:corrigan@KiNETWORKS.com]
Sent: Tuesday, October 09, 2001 1:13 PM
To: nv-l@tkg.com
Subject: Re: [NV-L] Re: IP status
Offer 5 % if they pay by 15 November.
Jc
>
>
>
>Allie,
> Please call it in. We are having the same problem and have an open
PMR
>on it. Bottom line, support needs data from affected systems to figure out
>what is going on and how to fix it.
>
> Bill
>
>
>Date: Thu, 27 Sep 2001 13:14:29 -0500
>From: "Allie M Tate" <allie@lsu.edu>
>Subject: IP status
>
>AIX 4.3.3 NetView 6.0.2
>
>This question was asked some time ago - but no final result was given. The
>IP status is not updating according to what is really going on. All
>interfaces are green and the actual device is green, but the IP status is
>still showing marginal or critical and therefore remaining in my Smartset
>collections looking for down devices. Unmanaging and managing fixes this,
>but I'm not interested in this as a long term solution. Is there a patch
>for this or do I need to call this is?
>
>Thanks.
>
>
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
Jim Corrigan
President/CEO
voice: +919 319 1152 x 22
fax: +919 468 5797
mobile: +919 349-8767
URL: http://www.KiNETWORKS.com
email: Jim.Corrigan@KiNETWORKS.com
SnailMail:
Ki NETWORKS, Inc
102 New Edition Court
Cary, NC 27511
------------------------------------
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient or have received this e-mail
in error, notify the sender immediately and destroy this e-mail.
Any unauthorized duplication, disclosure or distribution of the
material in this e-mail is forbidden.
|