Supported Platforms
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Creating SNMPv3 Users
- Minimum SNMPv3 Configuration on a Device Running Junos OS
- ACX, M, MX, PTX, T Series
- Complete SNMPv3 Configuration Statements
- Example: SNMPv3 Community Configuration
Configuring the SNMPv3 Community
The SNMP community defines the relationship between an SNMP server system and the client systems. This statement is optional.
To configure the SNMP community, include the snmp-community statement at the [edit snmp v3] hierarchy level:
community-index is the index for the SNMP community.
To configure the SNMP community properties, include the following statements at the [edit snmp v3 snmp-community community-index] hierarchy level:
This section includes the following topics:
Configuring the Community Name
The community name defines the SNMP community. The SNMP community authorizes SNMPv1 or SNMPv2c clients. The access privileges associated with the configured security name define which MIB objects are available and the operations (read, write, or notify) allowed on those objects.
To configure the SNMP community name, include the community-name statement at the [edit snmp v3 snmp-community community-index] hierarchy level:
community-name is the community string for an SNMPv1 or SNMPv2c community.
If unconfigured, it is the same as the community index.
If the community name contains spaces, enclose it in quotation marks (“ “).
 | Note: Community names must be unique. You cannot configure the same community name at the [edit snmp community] and [edit snmp v3 snmp-community community-index] hierarchy levels. The configured community name at the [edit snmp v3 snmp-community community-index] hierarchy level is encrypted. You cannot view the community name after you have configured it and committed your changes. In the command-line interface (CLI), the community name is concealed. |
Configuring the Context
An SNMP context defines a collection of management information that is accessible to an SNMP entity. Typically, an SNMP entity has access to multiple contexts. A context can be a physical or logical system, a collection of multiple systems, or even a subset of a system. Each context in a management domain has a unique identifier.
To configure an SNMP context, include the context context-name statement at the [edit snmp v3 snmp-community community-index] hierarchy level:
| Note: To query a routing instance or a logical system, |
Configuring the Security Names
To assign a community string to a security name, include the security-name statement at the [edit snmp v3 snmp-community community-index] hierarchy level:
security-name is used when access control is set up. The security-to-group configuration at the [edit snmp v3 vacm] hierarchy level identifies the group.
| Note: This security name must match the security name configured at the [edit snmp v3 target-parameters target-parameters-name parameters] hierarchy level when you configure traps. |
Configuring the Tag
To configure the tag, include the tag statement at the [edit snmp v3 snmp-community community-index] hierarchy level:
tag-name identifies the address of managers that are allowed to use a community string.
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Creating SNMPv3 Users
- Minimum SNMPv3 Configuration on a Device Running Junos OS
- ACX, M, MX, PTX, T Series
- Complete SNMPv3 Configuration Statements
- Example: SNMPv3 Community Configuration
Published: 2012-12-08
Supported Platforms
Related Documentation
- ACX, M, MX, PTX, QFX, T Series
- Creating SNMPv3 Users
- Minimum SNMPv3 Configuration on a Device Running Junos OS
- ACX, M, MX, PTX, T Series
- Complete SNMPv3 Configuration Statements
- Example: SNMPv3 Community Configuration
