>>>>> On Tue, 9 Dec 2008 10:59:06 +0000, liao yedda <[EMAIL PROTECTED]> said:
ly> Does anyone explain above issue? Is it the correct behavior of ly> Net-SNMP? If we hope the Net-SNMP to handle the new user ly> automatically for both of configuration files, how do we do? What ly> are the corrected steps to clone a snmpv3 user by SNMP interface ly> without adding any other configuration line? The persistent file is the only one that snmpd will modify. It does not need to modify the regular system file. When you create a new user via SNMP (eg, if you're using the "snmpusm" command), it stores the information for the new user inside the persistent file only. However, creating a new USM user does not provide it access. You said you added a rouser line and that fixed the problem. That line adds access rights. To add access rights for your new user via SNMP instead of editing the snmpd.conf file you need to add new configuration to the SNMP-VACM-MIB. There is a command line utility called snmpvacm that can help you do this if you like. -- Wes Hardaker Sparta, Inc. ------------------------------------------------------------------------------ SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ _______________________________________________ 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
