R3721-F3210-F3171-HP High-End Firewalls System Management and Maintenance Command Reference-6PW101

169
The converted key is valid only under the specified engine ID.
In FIPS mode, SHA authentication is available but 3DES encryption is not available.
Related commands: snmp-agent usm-user v3.
Examples
# Use local engine ID to convert the plaintext key authkey to an encrypted key for MD5 authentication.
<Sysname> system-view
[Sysname] snmp-agent calculate-password authkey mode md5 local-engineid
The secret key is: 09659EC5A9AE91BA189E5845E1DDE0CC
snmp-agent community
Syntax
snmp-agent community { read | write } community-name [ acl acl-number | mib-view view-name ] *
undo snmp-agent community { read | write } community-name
View
System view
Default level
3: Manage level
Parameters
read: Assigns the specified community the read only access to MIB objects. A read-only community can
only inquire MIB information.
write: Assigns the specified community the read and write access to MIB objects. A read and write
community can configure MIB information.
community-name: Sets a community name, which is a string of 1 to 32 characters.
acl acl-number: Applies a basic ACL to filter NMSs by source IP address. The acl-number argument
represents a basic ACL number in the range of 2,000 to 2,999.
mib-view view-name: Specifies the MIB view available for the community. The view-name argument
represents a MIB view name, which is a string of 1 to 32 characters. A MIB view represents a set of
accessible MIB objects. If no MIB view is specified, the specified community can access the MIB objects
in the default MIB view ViewDefault. To create a MIB view, use the snmp-agent mib-view command.
Description
Use snmp-agent community to configure an SNMP community.
Use undo snmp-agent community to delete a specified community.
This command is for SNMPv1 and SNMPv2c.
A community comprises NMSs and SNMP agents, and is identified by a community name. When
devices in a community communicate with each other, they use the community name for authentication.
An NMS and an SNMP agent can access each other only when they are configured with the same
community name. Typically, public is used as the read-only community name, and private is used as the
read and write community name. To improve security, assign your SNMP communities a name other than
public and private.