SNMP Command Reference
Page 180 7705 SAR OS System Management Guide
usm-community
Syntax usm-community community-string [hash | hash2] group group-name
no usm-community community-string
Context config>system>security>snmp
Description This command is used to associate a community string with an SNMPv3 access group and its view.
The access granted with a community string is restricted to the scope of the configured group.
The 7705 SAR OS implementation of SNMP uses SNMPv3. In order to implement SNMPv1 and
SNMPv2c configurations, several access groups are predefined. In order to implement SNMP with
security features (version 3), security models, security levels, and USM communities must be
explicitly configured. Optionally, additional views that specify more specific OIDs (MIB objects in
the subtree) can be configured.
The no form of this command removes a community string.
Default none
Parameters community-string — configures the SNMPv1/SNMPv2c community string to determine the SNMPv3
access permissions to be used
group — specifies the group that governs the access rights of this community string. This group must
be configured first in the config>system>security>snmp>access group context.
hash1 | hash2 — configures hashing scheme for the community-string
view
Syntax view view-name subtree oid-value
no view view-name [subtree oid-value]
Context config>system>security>snmp
Description This command configures a view. Views control the accessibility of a MIB object within the
configured MIB view and subtree. Object identifiers (OIDs) uniquely identify MIB objects in the
subtree. OIDs are organized hierarchically with specific values assigned by different organizations.
Once the subtree (OID) is identified, a mask can be created to select the portions of the subtree to be
included or excluded for access using this particular view. See the
mask command. The view(s)
configured with this command can subsequently be used in read, write, and notify commands that are
used to assign specific access group permissions to created views and assigned to particular access
groups.
Multiple subtrees can be added or removed from a view name to tailor a view to the requirements of
the user access group.
The no view view-name command removes a view and all subtrees.
The no view view-name subtree oid-value command removes a sub-tree from the view name.