Net Insight Nimbra 300 Series, User Manual

Page: 73 / 100

Element Manager User’s Manual Nimbra OneSerie Control Network
•
71
©2006 Net Insight AB, All rights reserved
The example defines a group named "FullAccessUser" that requires the user to
have at least the security level "authNoPriv" (authenticated, but not encrypted).
The group permits access to the MIB view "All" for read (responding to snmp-
get operations), write (accept snmp-set operationrs) and for notifications.
Assigning Users
A user must be associated with a group, where the group defines the access
rights for the user. For SNMPv1 and SNMPv2c, which do not have the user
concept, the community name is used instead.
An entry maps a security model and its user or community name to a group. An
entry is represented by the tag
vacmSecurityToGroupEntry
.
vacmSecurityToGroupEntry model principal group storage
model defines if the security model for the entry. The model is
snmpv1
,
snmpv2c
or
usm
.
principal is the user name for the security model USM (see Defining SNMPv3
Users), or the security name that represents the community name for
SNMPv1/v2c. A default security name is public. The community name for the
public security name is modified from the web page Status | SNMP config.
group is the name of the group (see Defining Groups and Access Rights) to
which the user or community name shall be associated.
storage describes how the entry is stored. This is always
nonVolatile
.
Example 1
The example associates the USM user "root" with the group "FullAccessUser".
vacmSecurityToGroupEntry usm root FullAccessUser nonVolatile
Example 2
The example associates the community name "public" for SNMPv2 access to
the group "ReadOnlyUser".
vacmSecurityToGroupEntry snmpv2c public ReadOnlyUser nonvolatile