2009/5/27 Filka Michal <[email protected]>:
>> > trapcommunity public
>> > trapsink <ip>
>> > trap2sink <ip>
>>
>> OK - so that explains why you are getting two copies of each trap.
> ... the <ip> Is supposed as target for SNMPv1 traps even SNMPv2
> notifications. However I currently generate just one SNMPv2 notification
> only.


No - you are generating one notification.
The SNMP version(s) and destination(s) of that notification
are not the responsibility of the "monitor" directive.
That is handled by the trap*sink directives.

Because you have two such trap*sink directives, you will always
get two copies of every trap.




> I know, I've read that ... but I generate 1 SNMPv2 notification (testTr)
> and catch 4 traps ... 2 SNMPv1 (traps, mib-2 - see bellow) and 2 SNMPv2
> (mib-2.88.2.0.1, testTr - see bellow) that was subject of the question

Well, the second and third traps come from your "testNotification" event
(with two copies, because you've got two trap*sink directives).

The first and fourth traps are the standard DisMan Event MIB trap
"mteTriggerFired"  (again with two copies, becuase you've got two
trap*sink directives).


Now I'm not sure why you are getting *both* of these.
I'd expect to get one or the other pair.

What version of the agent are you using?

Dave

------------------------------------------------------------------------------
Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
is a gathering of tech-side developers & brand creativity professionals. Meet
the minds behind Google Creative Lab, Visual Complexity, Processing, & 
iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to