Re: [snmpsim-users] v3 GETs failing to select proper controller

[Ilya E. <il...@gl...>]

Hi Andrew,

Right, according to the log different .snmprec files were selected for v2c and v3 queries. That can be because you are not passing v3 contextName (which is e5d93d7d01f1414254094c14fa19bd92 for MYMIB.snmprec) along with v3 request. With Net-SNMP tools that would take the -n command-line switch to snmpwalk. Could you check that?

BTW, the --v3-priv-proto=NONE --v3-priv-key=ThePassword options combination is meaningless but harmless. ;)

-ilya

On Sep 28, 2013, at 2:04 AM, Forman, Andrew wrote:

> Hi, I’m at a complete loss as to what I’ve screwed up.
>  
> Previously, I had no trouble accessing the data in my .snmprec files over v2c or v3.
> But today, I found that while my v2c GETs still work fine, my v3s are all failing.
>  
> When I make a v2 call, I get the data and see logging entries like this:
>  
> 2013-09-27 16:32:50.957 snmpsimd[3164]: Using ./data\MYMIB.snmprec controller selected by contextName "e5d93d7d01f1414254094c14fa19bd92", transport ID 1.3.6.1.6.1.1.0, source address 127.0.0.1
> 2013-09-27 16:32:50.957 snmpsimd[3164]: SNMP EngineID 0x80004fb8050c5c96c0, securityModel 2, securityName e5d93d7d01f1414254094c14fa19bd92, securityLevel 1
> 2013-09-27 16:32:50.796 snmpsimd[3164]: Request var-binds: 1.3.6.1.4.1.73.50.1.1000.4.0=<>, flags: NEXT, GET
> 2013-09-27 16:32:50.796 snmpsimd[3164]: Response var-binds: 1.3.6.1.4.1.73.50.1.1000.5.0=<0>
>  
> When I make a v3 call to the same OID as the v2, I get this:
>  
> 2013-09-27 14:52:06.388 snmpsimd[16605]: Using /usr/lib/python2.4/site-packages/snmpsim-0.2.3-py2.4.egg/snmpsim/data/1.3.6.1.6.1.1.0/127.0.0.1.snmprec controller selected by candidate 1.3.6.1.6.1.1.0/127.0.0.1; transport ID 1.3.6.1.6.1.1.0, source address 127.0.0.1, context name "b00e7c4780fffc4ca0a74e262dd116bc"
> 2013-09-27 14:52:06.388 snmpsimd[16605]: Request var-binds: 1.3.6.1.4.1.73.50.1.1000=<>, flags: EXACT, GET
> 2013-09-27 14:52:06.389 snmpsimd[16605]: Response var-binds: 1.3.6.1.4.1.73.50.1.1000=<No Such Instance currently exists at this OID>
>  
> My command line looks like:
>  
> snmpsimd.py --data-dir=./data --variation-module-options=writecache:file:./data/sets.db --agent-udpv4-endpoint=localhost:1611 --v3-user=user --v3-auth-proto=NONE --v3-auth-key=ThePassword --v3-priv-proto=NONE --v3-priv-key=ThePassword --logging-method=file:./snmpsim.tmp
>  
> I’ve tried both the latest RC and the last formal release, but see no difference in behavior.
> Any chance you can tell what I’ve messed up?
>  
> Thanks!
> Andrew
> ------------------------------------------------------------------------------
> October Webinars: Code for Performance
> Free Intel webinars can help you accelerate application performance.
> Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
> the latest Intel processors and coprocessors. See abstracts and register >
> http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk_______________________________________________
> snmpsim-users mailing list
> snm...@li...
> https://lists.sourceforge.net/lists/listinfo/snmpsim-users