If I remember, when using v2 the properties of the trap, have to be defined in its var-bind list instead.
See for example http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a0080094aa5.shtml#topic1
It would be good to come out with a working example to post it on the wiki.
Yes, I understand it now. Thanks Dimitris for the quick reply.
Also see these URLs:
http://www.zvon.org/tmRFC/RFC3584/Output/index.html (section 3)
But, this means that my mapping nodes in notifications.xml depend on my choice of a version in manages.xml - because if I choose v2c I should put 2 additional values in the var-bind (payload) part. Also it means that I can't define in managers.xml several managers, and have some of them use v1 and some of them use v2c. Am I correct in this?
It seems a better implementation would do the translation from v1 to v2c automatically (as the rules for doing that are quite simple, see the URLs I gave). Am I correct in this? Do you plan doing it in the future?
You are right. The simplest solution would be to just instantiate twice the snmp-adapter with one instance configured with the managers using v1 and the other v2.
I think what's more important now is to get on the wiki some real use-cases, so if you get to configure it correctly for v2 traps, would you like to write a page about that?