In my previous response I didn't mean to imply that there aren't good
reasons to forward traps.  There are.  And many people do this, for one
reason or another.

When I said that few people use the -f option on trapd to forward traps as
EVENTS (to 1661/tcp), I meant that most folks use instead the -m option to
forward them as TRAPS (to 162/udp) so that they arrive at the final
destination exactly like they did when they arrived at the forwarding box.

James Shanks
Tivoli (NetView for UNIX) L3 Support



"Houle, Stephen A" <sh32829 AT IMCNAM.SBI DOT COM> on 09/18/98 03:06:49 PM

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

To:   NV-L AT UCSBVM.UCSB DOT EDU
cc:    (bcc: James Shanks)
Subject:  Re: Forwarding traps/events





If you have two machines, and the first is a trap target, but the second
isn't, you can forward events to the second machine so operators there can
see everything that is happening.  That second machine can also be behind a
firewall, or a development machine (or both).  If you want to migrate from
one machine to another, but can't change all the trap targets in your
network all at once, you can do this.  There must be other good reasons.
I've used it once or twice.

Steve

--
Steve Houle
Enterprise Management
Salomon Smith Barney
ph: (212) 723-3369
mailto:stephen.a.houle AT ssmb DOT com


-----Original Message-----
From: Simon Long [mailto:simon AT nettrack.com DOT au]
Sent: Friday, September 18, 1998 9:06 AM
To: NV-L AT UCSBVM.UCSB DOT EDU
Subject: Forwarding traps/events


Hi,

In configuring trapd there is the option to forward traps as events.
Why would you do this?

Simon Long
Nettrack Technical Solutions Pty Ltd