From: Dave S. <D.T...@cs...> - 2004-08-09 11:09:04
|
> a) But I still am not able to set engineID using snmpset command. First thing. *Why* are you trying to set the engineID. Normally you can just leave SNMPv3 to discover this automatically. > I am giving the command: > > snmpset -v 3 -u tina -l authNoPriv -a MD5 -A tina12345 10.254.24.227 > -e 800000020109840310 > It gives me error: > -e : Bad object type: 8 > > Please tell me where I am wrong.. You're mixing up command line options, and "positional" parameters. All the options (i.e. "-something") must come *before* the positional parameters (such as the destination host) Try snmpset -v 3 -u tina -l authNoPriv -a MD5 -A tina12345 -e 800000020109840310 10.254.24.277 > b) Also, please help me differentiate between user and group. A group consists of one or more users, who all have the same level of access. It means that you only need one "access" entry, rather than one per user. So you might have something like: createUser dave ..... createUser wes ..... createUser robert ..... group theYanks wes robert group theBrits dave access theYanks ..... access theBrits ..... and the first "access" line will cover both "wes" and "robert" while the second access line will only cover "dave" If you've only got one user in a group ("theBrits"), then this simply adds an extra (unnecessary) level of indirection. But if you've got two or more users ("theYanks"), then it can simplify the overall setup. > I created > "rwuser tina" in snmpd.conf and added manually "rwuser sample". Don't try to understand groups/users from the "rwuser" and "rouser" settings. These are intended as a somewhat simpler configuration mechanism. In fact they are just wrappers round the full VACM setup, and create an (anonymous) group for each user. Have a look at the FAQ entry: I don't understand the new access control stuff - what does it mean? which goes into this in more detail. > c) How can I create view in snmpv3. Is the method same as snmpv2?? Yes. See the FAQ entry mentioned above. Dave |