Allied Telesis AT-S62 User Manual
Page 382

Chapter 21: SNMPv3
382
Section III: SNMPv3
For a more detailed description of the SNMPv3 Tables, see the following
subsections:
“SNMPv3 User Table” on page 382
“SNMPv3 View Table” on page 382
“SNMPv3 SecurityToGroup Table” on page 383
“SNMPv3 Notify Table” on page 383
“SNMPv3 Target Address Table” on page 383
“SNMPv3 Target Parameters Table” on page 383
“SNMPv3 Community Table” on page 384
SNMPv3 User Table
The Configure SNMPv3 User Table menu allows you to create an
SNMPv3 user and provides the options of configuring authentication and
privacy protocols. With an authentication protocol configured, users are
authenticated when they send and receive messages. In addition, you can
configure a privacy protocol and password so messages a user sends and
receives are encrypted. The DES privacy algorithm uses the privacy
password and the Engine ID to generate a key that is used for encryption.
Lastly, you can configure a storage type for this table entry which allows
you to save this user and its related configuration to flash memory.
SNMPv3 View Table
The Configure SNMPv3 View Table Menu allows you to create a view of
the MIB OID Table. First, you configure a view of a subtree. Then you
have the option of configuring a Subtree Mask that further refines the
subtree view. For example, you can use a Subtree Mask to restrict a
user’s view to one row of the MIB OID Table. In addition, you can chose to
include or exclude a view. As a result, you can let a user see a particular
view or prevent a user from seeing a particular view. Lastly, you can
configure a storage type for this table entry which allows you to save this
view to flash memory.
SNMPv3 Access Table
The Configure SNMPv3 Access Table Menu allows you to configure a
security group. After you create a security group, you assign a set of users
with the same access privileges to this group using the SNMPv3
SecurityToGroup Table. It is useful to consider the types of groups you
want to create and the types of access privileges each group will have. In
this way, it is easy to keep track of your users as belonging to one or two
groups.
For each group, you can assign read, write, and notify views of the MIB
table. The views you assign here have been previously defined in the