Whoa.  Back up.  What EXACTLY is your TEC guy complaining about?  That one event
or others?  That one currently is the only one generated by nvserverd himself,
though in the next maintenance release there will be a matching one when
nvserverd reconnects (and it will tell you which ruleset it is using) so that
your TEC guy can correlate them if he likes.   Your fellow customers demanded
that we send both of these events.

Since this is a very tiny issue -- one internal event being generated by
nvserverd when he goes down  -- it should not cause anyone heartburn over in TEC
...  unless you are stopping/restarting nvserverd several times a day.  So what
is the real story?   My guess is that your are using something like
forwardall.rs to send all traps to TEC and they only want to see a very small
subset.  In which case, you need a better ruleset.

You don't need a list (and there isn't one).   You need a clear understanding of
the problem.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Kashif Karim <kashif_karim AT YAHOO DOT COM> on 06/21/99 07:00:52 PM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
      <NV-L AT UCSBVM.UCSB DOT EDU>

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks/Tivoli Systems)
Subject:  Netview internal traps





sometime ago James Shank had answered a forum append from me about the
event "Nvserverd is ending" saying that this event is internal to
Nvserverd and hence nothing about this can be changed on Netview side.
That was dated: 05/18/99.

James and others, I need to know what other such events are present and
where to find a listing of these that I can not do anything about on
Netview side because my T/EC administrator has to tell T/EC to throw
all such events away when it sees them, as that seems to be the only
option available.

Kashif
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com