This project has moved. For the latest updates, please go here.

Unicorn Horn and SNMP V2c

Topics: usage (how to ...)
Sep 8, 2008 at 12:15 PM
Hi all,

I am interested in this great project, so I have decided to test some code samples. I read that the SNMP V1 is totally finished and tested, but V2c is waiting for the new revision.

However, in my first experiences I try to use some functions (get and set) with VersionCode.V2 and all works ok. So, what is the real state of developing?

Best regards.

Coordinator
Sep 8, 2008 at 1:53 PM
Edited Sep 8, 2008 at 1:56 PM
Hi, v2c support is almost done (currently REPORT is the only missing part). And that's why you see GET and SET work for v2c already.

-Lex
Marked as answer by lextm on 10/6/2013 at 4:07 AM
Sep 9, 2008 at 11:02 AM
Edited Sep 9, 2008 at 11:22 AM
Thanks for your quick answer.

Meanwhile I have continued testing another functions and I have two notes:

1. The walk subtree mode is not working well as far I know (always in V2c). When I use this function, it only obtains the first OID subtree under the OID given. Example: If I use .1.3.6.1.4.1.23632.2.2, I get only the subtree of .1.3.6.1.4.1.23632.2.2.1 (4 elements in my case) but not the next subtrees like .1.3.6.1.4.1.23632.2.2.2 and so on. Nevertheless normal walk mode is ok.
2. Notify traps from my systems generate exceptions in the library Sharpsnmp ({"unsupported data type: InformRequestPdu"}). The typical structure that I use is a notify OID and several data OID inside.

Only to be sure, are this options implemented at this moment in Unicorn or perhaps in repository source code? It is possible that I have done something wrong, I am a beginner.
Thanks again.
Sep 9, 2008 at 1:08 PM
About note 2 I answer myself.

If I try to send traps with INFORM notification rather than an unacknowledged TRAP I have a exception, so, I guess that your code is not ready for this kind of notification. With standard TRAP I don't have problems.

Follow investigation about note 1 (also I ll be happy with more help)

Regards.
Coordinator
Sep 10, 2008 at 4:46 AM
Edited Sep 10, 2008 at 4:48 AM
Hi, thank you so much for your opinions.

About note 2, you need to check out latest source code from repository or wait a few days til I pull out TwinTower release candidate one (a 1.4 milestone). UnicornHorn does not support INFORM because INFORM support was added a few weeks after its release.

About note 1, I still need to investigate to see if it is a bug.

Regards,

-Lex
Coordinator
Sep 10, 2008 at 5:44 AM
Hi, now I can state that the issue described in note 1 is a new bug. I already add a Work Item for it. Thanks for the report. This is going to be fixed soon.

-Lex
Sep 10, 2008 at 12:34 PM
Thanks for your good job.

Now we are developing with Visual Studio 2005. In a short time we are changing to 2008, so it is possible that we can make changes in your code in the future, that we'll share with you, if you consider them useful.

Best Regards.
Coordinator
Sep 11, 2008 at 4:46 AM
Dear,

:-) Any help (suggestions, bug reports and patches) is appreciated (unless you violate LGPL that covers #SNMP Library).

-Lex
Coordinator
Sep 13, 2008 at 5:43 AM
Hi, this bug is fixed in the repository now.

-Lex
Coordinator
Feb 1, 2013 at 8:55 AM
A quick update is that starting from http://sharpsnmplib.codeplex.com/releases/view/79079, #SNMP is released under MIT/X11 (MIB support is under BSD 3 Clause).

Lex
Marked as answer by lextm on 10/6/2013 at 4:06 AM