All unsolicited traps go to 162/udp per the RFCs which define SNMP. So the
answer to question 1 is that whomever owns 162/udp gets all traps and thereby
has the chance to filter or determine what others see. So you must set MLM to
forward what traps you want trapd to see to the port that trapd is now on.
There is no reason to set trapd to 165/tcp but I don't know that this will hurt
anything
Status traps from MLM go to trapd but they are defined as Log only (unless you
change them) and when netmon gets these from trapd he issues the normal NetView
status traps, just as if he had done the status polling himself, and you do see
those.
Every time MLM is re-started he sends all new status traps on the devices he
monitors but netmon re-issues only those which represent a change, as he usually
does.
James Shanks
Tivoli (NetView for UNIX) L3 Support
Gregory Adams <gadams@US.IBM.COM> on 01/21/2000 06:56:38 AM
Please respond to Discussion of IBM NetView and POLYCENTER Manager on NetView
<NV-L@UCSBVM.UCSB.EDU>
To: NV-L@UCSBVM.UCSB.EDU
cc: (bcc: James Shanks/Tivoli Systems)
Subject: MLM and TRAPD
Hello, I am running NV6000 5.1.2 on AIX 4.3.2 along with MLM v
05.00.0002.0000
I have configured the mlm trap reception table to use port 162 TCP and
UDP. I have configured TRAPD to listen on port 165 TCP and UDP. I have a
couple of questions about this configuration.
1. Do both TRAPD and MLM receive unsolicited traps ? Or does the mlm trap
destination table and filter tables control what TRAPD sees ?
2. When netmon is configured to allow mlm to do status polling what is the
flow of status traps ?
Thankyou,
Greg Adams
|