OoO La nuit ayant déjà recouvert d'encre ce jour du vendredi 16 mars 2012, vers 23:03, Charlie Martin <crmar...@sgi.com> disait :
> Okay, so I've implemented a sub-agent using the pass_persist mechanism > in net-SNMP. Testing with snmpget, I can get the values expected. > Testing with snmpgetnext, I get the value of the "next" OID. Here's a > sample, slightly anonymized: > 1004 $ snmpget -On -v 2c -c xxx dev1 1.3.6.1.4.1.59.1.5.3.1.1.1 > .1.3.6.1.4.1.59.1.5.3.1.1.1 = INTEGER: 1 > 1004 $ snmpgetnext -On -v 2c -c xxx dev1 1.3.6.1.4.1.59.1.5.3.1.1.1 > .1.3.6.1.4.1.59.1.5.3.1.1.2 = STRING: "91" > 1005 $ snmpgetnext -On -v 2c -c xxx dev1 1.3.6.1.4.1.59.1.5.3.1.1.2 > .1.3.6.1.4.1.59.1.5.3.1.1.3 = STRING: "42" > As I say, the types and values for those responses appear to be > correct. Now I try an snmpwalk > 1006 $ snmpwalk -On -v 2c -c copan psmdev1 1.3.6.1.4.1.59.1.5.3.1.1.2 > .1.3.6.1.4.1.59.1.5.3.1.1.2 = STRING: "91" > Observe that it gets back only one reply, which is unexpected. At least > to me. Use: snmpwalk -On -v 2c -c copan psmdev1 1.3.6.1.4.1.59.1.5.3.1.1 -- Vincent Bernat ☯ http://vincent.bernat.im printk("Penguin %d is stuck in the bottle.\n", i); 2.0.38 /usr/src/linux/arch/sparc/kernel/smp.c ------------------------------------------------------------------------------ This SF email is sponsosred by: Try Windows Azure free for 90 days Click Here http://p.sf.net/sfu/sfd2d-msazure _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
