R0106-HP MSR Router Series Network Management and Monitoring Command Reference(V7)

189
priv-password: Specifies a case-sensitive plaintext or encrypted privacy key. In non-FIPS mode, a
plaintext key is a string of 1 to 64 characters. In FIPS mode, a plaintext key is a string of 15 to 64 visible
characters, which must contain numbers, uppercase letters, lowercase letters, and special characters. If
the cipher keyword is specified, the encrypted privacy key length requirements differ by authentication
algorithm and key string format, as shown in Table 45.
Table 45 Encrypted privacy key length requirements
Authentication
al
g
orithm
Encryption
al
g
orithm
Hexadecimal string Non-hexadecimal string
MD5
AES128 or
DES-56
32 characters 53 characters
SHA
AES128 or
DES-56
40 characters 53 characters
acl acl-number: Specifies a basic IPv4 ACL to filter NMSs by source IPv4 address. The acl-number
argument represents an ACL number in the range of 2000 to 2999. Only NMSs with an IPv4 address
permitted in the ACL can use the specified username to access the SNMP agent. If no ACL is specified,
the specified ACL does not exist, or the specified ACL does not have any rules, any NMS can use the
specified username to access the SNMP agent.
acl ipv6 ipv6-acl-number: Specifies a basic IPv6 ACL to filter NMSs by source IPv6 address. The
ipv6-acl-number argument represents an ACL number in the range of 2000 to 2999. Only NMSs with an
IPv6 address permitted in the IPv6 ACL can use the specified username to access the SNMP agent. If no
ACL is specified, the specified ACL does not exist, or the specified ACL does not have any rules, any NMS
can use the specified username to access the SNMP agent.
local: Specifies the local SNMP engine.
engineid engineid-string: Specifies an SNMP engine. The engineid-string argument represents the
engine ID and must contain an even number of hexadecimal characters, in the range of 10 to 64. All-zero
and all-F strings are invalid.
Usage guidelines
To send SNMPv3 informs to an NMS, perform the following tasks:
• Specify the IPv4 or IPv6 address of the NMS in the snmp-agent usm-user v3 command.
• Map the IPv4 or IPv6 address to the SNMP engine ID of the NMS by using the snmp-agent remote
command.
You must create an SNMPv3 group before you assign an SNMPv3 user to the group. Otherwise, the user
cannot take effect after it is created. An SNMP group contains one or multiple users and specifies the MIB
views and security model for the group of users. The authentication and encryption algorithms for each
user are specified when they are created.
SNMPv3 users are valid only on the SNMP engine that creates them. By default, SNMPv3 users are
created on the local SNMP engine. When you create an SNMPv3 user for sending SNMP inform
messages, you must associate it with the remote SNMP engine.
If you configure an SNMPv3 user multiple times, the most recent configuration takes effect.
For security purposes, all keys, including keys configured in plain text, are saved in cipher text.
Make sure you remember the username and the plain text of the keys. When you access the device from
an NMS, you must provide this information.