Rajagopal> The main motto of our project is that the SNMPv3 agent Rajagopal> should act as proxy for the SNMPV2 agent when somebody Rajagopal> tries to query the version 2 snmpd.
Um, why wouldn't you have one agent that handled both requests? Or is the v2 agent only listening locally and the v3 agent is proxying to the same agent locally which can't accept v2 requests from outside (which is smart). But if you're using our software for both, I'm a bit confused as ours can handle both at once. Rajagopal> We created a v3 user name with the command Rajagopal> net-snmp-config --create-snmpv3-usr -a "my_password" myuser Rajagopal> and its output is Rajagopal> "adding the following linet to /var/net-snmp/snmpd.conf: Rajagopal> createUser myuser MD5 "my_password" DES Rajagopal> adding the following line to /usr/share/snmp/snmpd.conf: Rajagopal> rwuser myuser " Ok, notice the two .conf paths that have been modified... now: Rajagopal> Then I started my snmpd with the following command Rajagopal> "/usr/sbin/snmpd -L -f -c /usr/share/snmp/snmpd.conf" You're only loading one of them. The right way to do this is actually to tell the agent to look in both places: setenv SNMPCONFPATH /usr/share/snmp:/var/net-snmp /usr/sbin/snmpd -L -f /usr/share/snmp/snmpd.conf -- Wes Hardaker Sparta, Inc. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
