Thanks, Dave, I had missed that option.

I now have:

> snmpgetnext -v 3 -n "" -u user1 -l authPriv -a MD5 -A sessame1 -x DES

-X sessame1 localhost sysUpTime
Snmpgetnxt: Unsupported security level (Sub-id not found: (top) ->

The user2 with -l authNoPriv is working fine for sysUpTime, so do I need
to somehow configure security levels for the data (as well as for the

I should say I am using the windows precompiled executables from

snmpd.conf is:

createUser user1 MD5 sessame1 DES sessame1
createUser user2 SHA sessame2
rwuser user1 priv
rwuser user2 auth
rwcommunity public

Thanks again


-----Original Message-----
From: [] On
Behalf Of Dave Shield
Sent: 16 April 2008 19:22
To: Williams, Gareth (FN) @ TRL
Subject: Re: SNMPv3 privacy: what am I doing wrong?

On 16/04/2008, wrote:
> * I have this snmpd.conf file:
> createUser user1 MD5 sessame1 DES sessame1
> rwuser user1 priv

> > snmpgetnext -v 3 -n -c public -u user1 -a MD5 -A sessame1

> -x DES -X sessame1 localhost sysUpTime

You haven't specified a security level, so the request will
default to 'authNoPriv'. But your snmpd.conf settings only
allow user1 to access the agent using encrypted requests.

Try adding '-l authPriv' to the command.

(And you don't need '-c public' - that's not relevant for SNMPv3)


This email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.;
Net-snmp-users mailing list
Please see the following page to unsubscribe or change other options: