On 9 September 2010 07:37, Vinod Nanjaiah <vinod_nanja...@mindtree.com> wrote:
> Another problem is that without completing the perl snmp installation,
> snmpconf is not available; without which snmpd throws up some warnings
> as shown below.
>
>
>
>> snmpd
> No log handling enabled - turning on stderr logging
> iquerySecName has not been configured - internal queries will fail
> Warning: no access control information configured.
> (Config search path:
> c:/usr/etc/snmp;c:/usr/share/snmp;c:/usr/lib)
>
> It's unlikely this agent can serve any useful purpose in this state.
>
> Run "snmpconf -g basic_setup" to help you configure the snmpd.conf
> file for this agent.
It's not complaining about "snmpconf".
It's complaining about the file 'snmpd.conf'
(which may well not exist in any of the specified locations)
Without a valid snmpd.conf file (including suitable access control settings)
the agent will not provide any information at all.
This snmpd.conf file is simply a text file - you can create it using your
favourite text editor. One possibility is to use "snmpconf", as suggested
in this error message. But this is not strictly necessary.
The simplest approach is just to create a text file containing
rocommunity public
(or your preferred community string), and this would be sufficient to
get the agent working again.
I'll leave the windows/perl issues to someone with more knowledge
and time.
Dave
------------------------------------------------------------------------------
This SF.net Dev2Dev email is sponsored by:
Show off your parallel programming skills.
Enter the Intel(R) Threading Challenge 2010.
http://p.sf.net/sfu/intel-thread-sfd
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
