User-Based Security Model Community Strings; Views; Access Groups - Alcatel-Lucent 7210 SAS E OS System Management Manual

User-Based Security Model Community Strings

User-based security model (USM) community strings associates a community string with an
SNMPv3 access group and its view. The access granted with a community string is restricted
to the scope of the configured group.

Views

Views control the access to a managed object. The total MIB of a router can be viewed as a
hierarchical tree. When a view is created, either the entire tree or a portion of the tree can be
specified and made available to a user to manage the objects contained in the subtree. Object
identifiers (OIDs) uniquely identify managed objects. A view defines the type of operations
for the view such as read, write, or notify.
OIDs are organized in a hierarchical tree with specific values assigned to different
organizations. A view defines a subset of the agent's managed objects controlled by the access
rules associated with that view.
Pre-defined views are available that are particularly useful when configuring SNMPv1 and
SNMPv2c.
The Alcatel-Lucent SNMP agent associates SNMPv1 and SNMPv2c community strings with
a SNMPv3 view.

Access Groups

Access groups associate a user group and a security model to the views the group can access.
An access group is defined by a unique combination of a group name, security model
(SNMPv1, SNMPv2c, or SNMPv3), and security level (no-authorization-no privacy,
authorization-no-privacy, or privacy).
An access group, in essence, is a template which defines a combination of access privileges
and views. A group can be associated to one or more network users to control their access
privileges and views.
Additional access parameters must be explicitly configured if the preconfigured access groups
and views for SNMPv1 and SNMPv2c do not meet your security requirements.
7210 SAS-E OS System Management Guide
SNMP
Page 151