nv-l

AW: Icon Status Color Changes

1999-04-06 03:02:00
Subject: AW: Icon Status Color Changes
From: Schiffinger Ralph 2100 <Ralph.Schiffinger AT ERSTEBANK DOT AT>
To: nv-l AT lists.tivoli DOT com
Date: Tue, 6 Apr 1999 09:02:00 +0200
Hi, group!
Exactly what i've experienced and i don't think it's a browser issue.
Color changes work fine on r/w AND r/o maps with every kind of collection NOT 
checking IP Status.
Try to create an additional egg with other rules for these nodes (vendor, 
sysObjectId, ...) and you'll see what i mean.
Regards, Ralph.

 -----Ursprüngliche Nachricht-----
Von:    Owens, Blaine C [SMTP:bowens AT EASTMAN DOT COM]
Gesendet am:    Freitag, 02. April 1999 20:10
An:     NV-L AT UCSBVM.ucsb DOT edu; Schiffinger Ralph 2100
Betreff:        Re: Icon Status Color Changes


Thanks, Leslie. Maybe that is not my real problem. Yes, my subsequent
testing indeed will straighten things out but the operations staff sees the
color changes and sometimes waste time investigating false indications of
trouble. In particular - I have created a collection they monitor holding
objects which are critical or marginal using the web interface. While it
seems the IP map always reflects current status they must "refresh" the
collection submap before these false "red or yellow icons" go away. It may
be a browser issue (??). The read-write submap is always correct - only the
collection submap on the web browser must be refreshed.

Blaine Owens
Eastman Chemical Company
Email - bowens AT eastman DOT com
Phone - (423)229-3579
Fax     - (423)229-1188

> -----Original Message-----
> From: Leslie Clark [SMTP:lclark AT us.ibm DOT com]
> Sent: Friday, April 02, 1999 11:32 AM
> To:   NV-L AT UCSBVM.ucsb DOT edu
> Subject:      Re: Icon Status Color Changes
>
> If in the course of investigation of a 'down' node you ping the thing,
> Netview will hear it and
> correct the status for you. Better that than altering the guts of the
> product. Unless of course
> you are itching to write your own network management product....
>
> Cordially,
>
> Leslie A. Clark
> IBM Global Services - Systems Mgmt & Networking
>
>
>
> I automatically generate Remedy Trouble Tickets for "Node Down" events but
> not directly from the netmon node down trap, which is not always true.
> Instead I run a script from automatic action and do more extensive testing
> to make sure the node really is down before generating my own trap which
> triggers the Remedy Ticket. I would prefer that the icon for the node NOT
> change to red/down from the netmon 58916865 trap but rather from my trap.
> Using the gui the "STATUS" for trap 58916865 (and 58916865) is greyed out.
> Is there a way to modify this behavior? Would it be safe to manually
> insert
> the status field in the trapd.conf file? Thanks.
>
> Blaine Owens
> Eastman Chemical Company
> Email - bowens AT eastman DOT com
> Phone - (423)229-3579
> Fax     - (423)229-1188

<Prev in Thread] Current Thread [Next in Thread>
  • AW: Icon Status Color Changes, Schiffinger Ralph 2100 <=