Trap OID when using v2c in SNMP Adaptor

[amyrlinseat]

Hi all,

I use JBoss (3.2.6) SNMP Adaptor to convert a JMX notification to an SNMP trap.
in the file "managers.xml" I define the manager app that receives the traps, and there I can define if the trap is sent as version 1 or as version 2 (v2c):

 <manager>
 <address>localhost</address>
 <port>1162</port>
 <local-address></local-address>
 <local-port></local-port>
 <version>1</version>
 </manager>

I use some other tool to catch the trap when it is sent.
In this tool I see the values of the enterprise oid, generic type and specific type, which should be the same values I defined for that trap in the mapping node in the file "notifications.xml".

When I set the version node to be 1, and send a JMX notification, the adaptor converts it to an SNMP trap of version v1, and in my tool I see the correct values of the enterprise oid, generic type and specific type.

But when I set the version node to be 2, the trap is received by the tool as v2c, but without any values for the enterprise oid, generic type and specific type.

Is this a bug in the SNMP adaptor, an intended behavior, or a problem with my trap viewer tool?
When using v2c traps, how should the SNMP manager application know the trap OID?

TIA
Amyrlin

[dimitris]

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.

[amyrlinseat]

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)
http://www.zvon.org/tmRFC/RFC2089/Output/chapter3.html

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?

Amyrlin

[dimitris]

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?