HPE FlexFabric 5930 Series, Справочник команд управления и мониторинга сети

Страница: 143 / 367

134
You can create up to 20 SNMP groups, including SNMPv1, SNMPv2c, and SNMPv3 groups.
All SNMPv3 users in a group share the same security model, but can use different authentication
and privacy key settings. To implement a security model for a user and avoid SNMP communication
failures, make sure the security model configuration for the group and the security key settings for
the user are compliant with
Table 40 and match the settings on the NMS.
Table 40 Basic security setting requirements for different security models
Security model
Security model
keyword for the
group Security key
settings for the
user
Remarks
Authentication with
privacy
privacy
Authentication key,
privacy key
If the authentication key
or the privacy key is not
configured, SNMP
communication will fail.
Authentication without
privacy
authentication Authentication key
If no authentication key is
configured, SNMP
communication will fail.
The privacy key (if any)
for the user does not take
effect.
No authentication, no
privacy Neither authentication
nor privacy
None
The authentication and
privacy keys, if
configured, do not take
effect.
Examples
# Create the SNMPv3 group group1 and assigns the no authentication, no privacy security model to
the group.
<Sysname> system-view
[Sysname] snmp-agent group v3 group1
Related commands
•
display snmp-agent group
•
snmp-agent mib-view
•
snmp-agent usm-user
snmp-agent local-engineid
Use snmp-agent local-engineid to change the SNMP engine ID of the local SNMP agent.
Use undo snmp-agent local-engineid to restore the default local SNMP engine ID.
Syntax
snmp-agent local-engineid engineid
undo snmp-agent local-engineid
Default
The local engine ID is the combination of the company ID and the device ID. Device ID varies by
product and might be an IP address, a MAC address, or any user-defined hexadecimal string.
Views
System view