snmpset gives different error reasons for v1 and v2c

Hello All,

I have a community "benu123" configured as read-only. I could do
snmpget with both -v1 and -v2c.
While I am trying snmpset with -v1 and -v2c, I am getting different
reasons for errors. I believe the error reason should be noAccess as
in the -v2 case.

Why am I getting noSuchName for -v1? Please refer the following
commands and outputs.

[root@localhost sbin]# snmpget -v1 -c benu123 localhost sysName.0
SNMPv2-MIB::sysName.0 = STRING: BENU

[root@localhost sbin]# snmpget -v2c -c benu123 localhost sysName.0
SNMPv2-MIB::sysName.0 = STRING: BENU
[root@localhost sbin]#

[root@localhost sbin]# snmpset -v1 -c benu123 localhost sysName.0 s BENU123
Error in packet.
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: SNMPv2-MIB::sysName.0

[root@localhost sbin]# snmpset -v2c -c benu123 localhost sysName.0 s BENU123
Error in packet.
Reason: noAccess
Failed object: SNMPv2-MIB::sysName.0

Regards,
Ashok

------------------------------------------------------------------------------
The demand for IT networking professionals continues to grow, and the
demand for specialized networking skills is growing even more rapidly.
Take a complimentary Learning@Cisco Self-Assessment and learn 
about Cisco certifications, training, and career opportunities. 
http://p.sf.net/sfu/cisco-dev2dev
_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users