On 8 November 2011 14:38, Simon Chamlian <
simon.c...@gmail.com> wrote:
> I tried the following:
> # snmpusm -v3 172.27.42.191 create initial wes
> snmpset: No securityName specified
>
> # snmpusm -v3 -l authNoPriv -a MD5 172.27.42.191 create enzo1 simon1
> snmpset: No securityName specified
If you are going to use SNMPv3, then you *must* specify the SNMPv3 user
that is authenticating the request. Not just the new user that you
wish to create,
or the existing user that you are copying from - the user that is
making the request.
> # snmpusm -v3 -u simon -n "" -l authNoPriv -a MD5 -A "hello_world" 172.27.42.191 create enzo simon
> snmpset: Unknown user name
That should work if you have already set up a user "simon" (with
suitable access rights).
But not if the user "simon" doesn't yet exist.
> The agent (snmpd) should be running during these commands
Yes - the agent needs to be running.
"snmpusm" is sending SNMP requests, so there needs to be something to
receive and act on them.
But you still haven't answered my initial question.
Did you put a line of the form
"createUser initial ....."
in one of the snmpd.conf files?
The only configuration setting you've mentioned so far is the "rwuser" entry.
You *also* need to create this user (using "createUser")
It's not possible to start using SNMPv3 without having an initial user,
and this needs to be set up via the config file.
Try that , and make sure you can run simple "snmpget" requests.
There's no point in trying to use "snmpusm" until you've got this working first.