[ Sorry for the delay in responding to this ]
> I receive twice trap per notification.
> Here is the list of snmpd.conf trap & access statements:
> "...
> rocommunity public 192.9.200.0/24
> rwcommunity private 192.9.200.67
> trap2sink 192.9.200.67 private 162
> authtrapenable 1
> ..."
Are those the *only* trap command-related entries in your snmpd.conf
file? I'd check very carefully to make sure there isn't another
trapsink (or similar) line somewhere there.
The other possibility is that this file might be being read in twice.
Try running the agent using
snmpd -f -Le -Dread-config
and pay close attention to which files are read in.
> I receive 2 instances of every trap in my NNM alarm Browser.
> I also receive 2 instances when trap receiver is MG-Soft Mib Browser.
Are these duplicated traps always the same version (i.e. both SNMPv2
traps)? What if you change that 'trap2sink' to be 'trapsink'
(or 'informsink')? Does that affect both copies of the trap
(which would tend to indicate the file being read in twice)
or only one (which would indicate there's another config entry somewhere).
Dave
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
