Net Insight Nimbra 300 Series, Руководство пользователя

Страница: 69 / 100

Element Manager User’s Manual Nimbra OneSerie Control Network
•
67
©2006 Net Insight AB, All rights reserved
vacmGroupName (group)
vacmGroupName (name)
vacmAccessReadViewName… (read/write/notify)
vacmViewTreeFamilyViewName (name)
vacmSecurityName (principal)
usmUserName (name)
user
usmUserEntry
group
vacmAccessEntry
MIB view
vacmViewTreeFamilyEntry
user group
vacmSecurityToGroupEntry
community name
snmpCommunityEntry
snmpCommunitySecurityName (name)
vacmSecurityName (principal)
- or -
Figure 63. MIB views, groups and users or community names
Defining SNMPv3 Users
At least one SNMPv3 user must be configured for the SNMP agent to send and
receive SNMP messages using the SNMPv3 protocol. (SNMPv1 and SNMPv2c
do not have users. Instead they have community names, see section Defining
Community.) The preferred way to define a user is to use the SNMP page.
A user is defined in the User-based Security Model, USM.
Note that an USM user is not the same as the element manager users used for
the CLI or web access of the Nimbra network element. Hence, the users defined
for the element manager is not known by the SNMP agent, and the element
manger does not know about the USM users.
A user entry is represented by the tag usmUserEntry . The format of the
entry is:
usmUserEntry engineID name authProtocol privProtocol storage target
authKey