How about a little more explanation of what you are trying to do here?

When you send a trap to 162/udp it is a one-way operation.  The trap
receiver just has to listen to the port.  But tcp communication requires
that the parties involved negotiate a session -- tcp is connection-oriented
while udp is conectionless.  So trapd does allow tcp communication --
netmon sends that way, so does MLM, even another NetView's trapd, but they
are designed to do that.

Who is sending the trap to 162/tcp?

James Shanks
Tivoli (NetView for UNIX) L3 Support



Bob Engley <bob.engley AT UALBERTA DOT CA> on 09/29/98 04:24:13 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:  trapd problem





We need to receive BOTH tcp and udp traps on NetView's port 162.
Our tests so far have been unsuccessful. The documentation seems to
indicate
that it is possible, but sending tcp traps to port 162 never seem to get
there
(at least they don't get logged in trapd.log).
Any ideas?

--
/in haste
/Bob