1. Network Management Specification
8000-A2-GB30-30
June 2004
93
As indicated before this table will have a default user whose name and password are the
same as the default userID and password of the entire device. This initial password is run
through an algorithm based on the HMAC-MD5-96 (default algorithm for authentication)
and converted in what is called a
localized key
. This procedure is stardarized in RFC
3414_std62.
Remote SNMP entities must define the same userName/Password and run it through a sim-
ilar procedure to obtain the
same
value of the
localized key
to start with.
The following is the default user in the usmUserTable:
*
The usmUserSecurityName will be set to the same usmUserName.
8.4.5
View-based Access Control (VACM) RFC 3415_std62
RFC 3415_std62 discusses the “View-based Access Control Model” for SNMPv3. The
SNMP agent will create default entries in the neccesary tables to be commonly used
among the different model processing supported (e.g, SNMPv1/v2c/v3 config access)..
Table 1-113. Default SNMPv3 user with Auth and Privacy Enabled
usmUserEntry
Default
usmUserEngineID
localSnmpID
usmUserName
“SUPERUSER”
usmUserSecurityName
“SUPERUSER”
*
usmUserCloneFrom
.0.0
usmUserAuthProtocol
usmHMACMD5AuthProtocol
usmUserAuthKeyChange
********
usmUserOwnAuthKeyChange
““
usmUserPrivProtocol
usmDESPrivProtocol
usmUserPrivKeyChange
********
usmUserOwnPrivKeyChange
““
usmUserPublic
““
Table 1-114. SNMP-VACM-MIB mib objects (1 of 2)
Object
Supported
Comments
vacmContextTable
not supported
It defines the locally available
contexts. For this product, this table
contains only the default context ““
and it is not required to be
accessible.
vacmSecurityToGroupTable
read-only
It maps a securityModel and
securityName to a groupName.
Some default entries are provided.
