That's two questions, not one.

I assume from your previous appends you are talking about UNIX.

Trap forwarding in UNIX is an option on trapd, either -m or -M, see the
trapd man page for details.  If you use little -m, then you identify each
trap to be forwarded in trapd.conf  by clicking the button to forward it in
Event Configuration.

The second question is not easily answered.  The traps you send are subject
to the trapd.conf in the receiving NetView.  You could make them all Log
Only and then they would not be displayed.  But the problem comes when you
also want to see the same trap if it is generated locally, like Node Down.
Then you are out of luck.  Either they all get shown or none of them do.  A
forwarded trap is not flagged as "forwarded"  so there is no way to
differentiate them when they arrive.  All traps will be handled the same
way.

James Shanks
Tivoli (NetView for UNIX) L3 Support



Lucy Premus <lpremus AT METLIFE DOT COM> on 06/15/99 10:13:33 AM

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:  Forwarding events/traps from one NetView to another





Is it possible to forward events/traps from one NetView to another?  We
don't
want them to be displayed on the second NetView.  We just want it sent
there,
logged and forwarded from there to a TEC console.