Re: problem with snmpusm command

"kusuma.bm" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hi,
 thanks a lot Dave, the problem got solved.
Actually the agent was reading the settings from /usr/local 
/share/snmpd.conf and not from /etc/snmp/snmpd.conf.

This command really helped me to solve the problem.

*snmpd -f -Le -Dread_config


thanks
kusuma
*


Dave Shield wrote:
>     [ 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.   ]
>
> 2009/3/4 kusuma. bm <[email protected]>:
>   
>> Hi,
>> In /var/net-snmp/snmpd.conf on 172.10.1.4 , i gave
>> createUser initial MD5 initialpasswd
>>
>> The /etc/snmp/snmpd.conf contains
>> rwuser initial
>> rwuser wes
>>     
>
>
> If that information is in /etc/snmp/snmpd.conf  (as you say here),
> but you can't see anything relevant in the vacm tables (as you say
> elsewhere),  then that would tend to indicate that the agent is not
> reading this config file.
>
>
>   
>> * * *snmpgetnext -v3 -u initial -l authNoPriv -a MD5 -A initialpassword
>> 172.10.1.4 .1
>> SNMPv2-MIB::sysDescr.0 = STRING: Linux kusuma 2.6.21.5-smp #2 SMP Tue Jun 19
>> 14:58:11 CDT 2007 i686  ---> is my output
>>
>> *
>> *Now if i try to give the command from snmptrapd
>>
>> snmpgetnext -v3 -u wes  -l authNoPriv -a MD5 -A initialpasswd 172.10.1.4
>> :161 .1.3.6.1.6.3.15
>> this vil give me
>> Error in packet.
>> Reason: authorizationError (access denied to that object)
>> *
>>     
>
> I.e. the user "wes" doesn't have access to anything.
> That also indicates that the agent isn't picking up the "rwuser wes" line.
>
>
>
>   
>> I am using net-snmp-5.2.1 as snmpd agent and yes i have compiled it myself.
>>     
>
> Try putting the rwuser lines in /usr/local/etc/snmpd.conf
> rather than /etc/snmp/snmpd.conf
>
>
> If that doesn't work, try killing off the agent, and restarting it as
>
>      snmpd -f -Le -Dread_config
>
> That will display debugging information, including a list of where the agent
> is looking for configuration, and what settings it finds.
> That should help you track down where to put the snmpd.conf file.
>
> Dave
>
> ------------------------------------------------------------------------------
> Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
> -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
> -Strategies to boost innovation and cut costs with open source participation
> -Receive a $600 discount off the registration fee with the source code: SFAD
> http://p.sf.net/sfu/XcvMzF8H
> _______________________________________________
> 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
>
>

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.