#2402 snmpTargetSpinLock returns invalid error

open
nobody
agent (1105)
5
2012-11-08
2012-09-02
No

net-snmp-5-7-2-rc2:

SNMP-TARGET-MIB::snmpTargetSpinLock (1.3.6.1.6.3.12.1.1.0) is returning wrong error (inconsistentValue) writing to an invalid instance. Error notWritable / noCreation was expected.

correct:
snmpset -v2c -cprivate 192.168.0.39 1.3.6.1.6.3.12.1.1.0 i 1
iso.3.6.1.6.3.12.1.1.0 = INTEGER: 1

incorrect:
snmpset -v2c -cprivate 192.168.0.39 1.3.6.1.6.3.12.1.1 i 1
Error in packet.
Reason: inconsistentValue (The set value is illegal or unsupported in some way)
Failed object: iso.3.6.1.6.3.12.1.1

dito for
1.3.6.1.6.3.12.1.1.0.0
1.3.6.1.6.3.12.1.1.1 ...

Discussion

  • Finzel Stefan

    Finzel Stefan - 2012-09-03

    the behaviour should also be consistent to other locks like ipAddressSpinLock, usmUserSpinLock, vacmViewSpinLock

     
  • Finzel Stefan

    Finzel Stefan - 2012-10-19

    it looks like REGISTER_MIB was not made to handle scalars like snmpTargetSpinLock therefore a query to an invalid oid (1.3.6.1.6.3.12.1.1.0.0 or 1.3.6.1.6.3.12.1.1.1) is not recognized

    this could be fixed by checks around functions var_targetSpinLock or write_targetSpinLock

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks