SNMP Trap reception - trapd or MLM?
Another question in the saga of Danny and the MLMs:
Is it better to have an MLM on a NetView server receive SNMP traps, or send
them directly to trapd? Currently I am not planning on filtering the SNMP
traps anywhere but at the source of the trap - i.e. if the trap is sent, I
am interested in it. I have read on the NV-L archives of people using MLMs
to filter traps but this doesn't apply to me.
I have been trying to work out how the MLM communicates with the NetView
server but am failing miserably.
Can I use the MLM to do the local subnet discovery and status polling and
have trapd receive the SNMP traps or does the MLM use SNMP to communicate
One configuration I have considered is to have trapd configured to listen
on 162/udp for the normal traps and 165/tcp to receive stuff from the MLM.
I could configure the MLM to listen on port 162/tcp for anything else that
is floating around (not that there should be - but just in case).
Am I complicating stuff terribly. Have I missed something fundamental. I
have been RTFM'ing but am still confused.
(By the way - the MLMs are to get around a firewall NAT issue until I can
Archive operated by Skills 1st Ltd
See also: The NetView Web