Re: Send event when node is down at startup???

1999-06-07 19:58:02
Subject: Re: Send event when node is down at startup???
From: James Shanks <James_Shanks AT TIVOLI DOT COM>
To: nv-l AT lists.tivoli DOT com
Date: Mon, 7 Jun 1999 19:58:02 -0400
NetView for UNIX does not keep such a list per se, though you could build
one by querying the databases (creatively using ovobjprint and awk for
example) or by building a collection of nodes with a Status of Down, and
let nvcold do it for you.   Lots of folks do that.

But events are strictly current events.  The only ones you will see in the
window are those which have arrived since nvcorrd was last started.  Old
events are not part of the event display.  You can look at recently past
events using Event History but that is a separate facility.  Once the
daemons are restarted, the event stream is considered anew.

Saving your environment just allows your filter to work on the next events
which come in, though you could also bring up Event History and apply it
there too.  But after the ovevent.log reaches its max (about 2 Meg I think)
then the old ones are gone from there too.  So there is no reliable way to
look at all currently valid node down events unless you search the old
copies of trapd.log or build a mechanism of your own to save them as they
occur. Trapd has an option to automatically roll over to new log files if
you like to save them, but there is no GUI for looking at them.

James Shanks
Tivoli (NetView for UNIX) L3 Support

Jeff Fitzwater <jfitz AT PRINCETON DOT EDU> on 06/07/99 04:27:12 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on

cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Send event when node is down at startup???

        I am running Netview 5.1.1on Solaris 2.6, and am trying to have
show a list of events indicating all nodes currently down.
        If I create a dynamic event list and filter only node down events,
I do
not get all the nodes that are down in the map, only nodes that were up
and then went down after netview was started.   I decided to save the
"event environment" so when I started netview the event filter would be
available at startup to receive the full event stream.   But no luck,
none of the nodes that are down at startup show up in the filtered event
stream or in the full unfiltered event stream.

As far as startup, I exited the Netview GUI and restarted it and also
tried stopping all netview processes and restarting them but same

In summary, if the node is down at startup no "event down" is
generated.   So it appears.

Any ideas on this.


Jeff Fitzwater
Princeton University

<Prev in Thread] Current Thread [Next in Thread>