H3C SR6600 Command Reference Manual page 119

Syntax
snmp-agent community { read | write } [ cipher ] community-name [ mib-view view-name ] [ acl
acl-number | acl ipv6 ipv6-acl-number ] *
undo snmp-agent community { read | write } [ cipher ] community-name
Views
System view
Default command 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.
cipher: Saves the specified community name in cipher text. If this keyword is not specified, the command
saves the community name in plain text.
community-name: Sets a community name. If you specify the cipher keyword, the community name is a
string of 1 to 73 characters. If you do not specify the cipher keyword, the community name is a string of
1 to 32 characters.
mib-view view-name: Specifies the MIB view available for the community. The view-name argument
represents a MIB view name, 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.
acl acl-number: Specifies a basic ACL to filter NMSs by source IP address. The acl-number argument
represents a basic ACL number in the range of 2000 to 2999. In the specified community, only the NMSs
with the IP addresses permitted in the ACL can access the SNMP agent.
acl ipv6 ipv6-acl-number: Specifies a basic ACL to filter NMSs by source IPv6 address. The
ipv6-acl-number argument represents a basic ACL number in the range of 2000 to 2999. In the specified
community, only the NMSs with the IPv6 addresses permitted in the ACL can access the SNMP agent.
Usage guidelines
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.
To make sure the MIB objects are accessible only to a specific NMS, use a basic ACL to identify the
source IP address of the NMS. To set the range of the MIB objects available for the community, use a MIB
view.
This command is supported only in non-FIPS mode.
111