[ First - *please* don't mail me privately, without copying
any responses to the mailing list. I don't have the time
or inclination to offer private, unpaid, SNMP consultancy.
Keep discussions to the list, where others can both learn
and offer advice. Thanks. ]
On 31 July 2012 04:39, Rajeesh R <[email protected]> wrote:
> Hi,
>
> In my snmpd.conf file rocommunity: a SNMPv1/SNMPv2c read-only access
> community name is commented one
[snip]
> # rocommunity: a SNMPv1/SNMPv2c read-only access community name
> # arguments: community [default|hostname|network/bits] [oid]
>
> #rocommunity public
>
> # rwcommunity: a SNMPv1/SNMPv2c read-write access community name
> # arguments: community [default|hostname|network/bits] [oid]
>
> rwcommunity public
> rwcommunity private 192.168.3.163
OK - yes, that should allow write access.
> Please see my snmpd file below which is in /usr/local/share/snmp
So the config file is under /usr/local.
Is this an agent that you have compiled yourself?
Or are you using the vendor supplied one?
> While creating a table entry using the command
> snmpset -v2c -c public 192.168.3.163 .1.3.111.2.802.1.1.8.1.5.2.1.8 i 4
That OID isn't part of one of the standard MIBs.
(In fact, it looks extremely strange
I have no idea who looks after .iso.org.111 !)
Is this a MIB module that you have developed yourself?
Or from somewhere else?
Where did this MIB come from?
Dave
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
