Specifications

MX-2100/2104 Installation and Operation Manual Appendix C SNMP Management
SNMP Environment C-3
MIBs Supported by the MX-2100 SNMP Agent
The interpretation of the relevant MIBs is a function of the SNMP agent of each
managed entity. The general MX-2100 SNMP agent currently supports RFC 1213
(the standard MIB-II).
In addition, the MX-2100 SNMP agent supports the enterprise-specific MIB
identified as (read the following as a continuous string):
iso(1).org(3).dod(6).internet(1).private(4)
.enterprises(1).rad(164).radWAN(3)
Management Domains Under SNMP
SNMP enables, in principle, each management station that knows the MIBs
supported by a device, to perform all the management operations available on that
device. However, this is not desirable in practical situations, so it is necessary to
provide a means to limit the management domains.
SNMP Communities
To enable the delimitation of management domains, SNMP uses communities.
Each community is identified by a name, which is a case-sensitive alphanumeric
string defined by the user (the MX-2100 SNMP agents support community names
of up to 8 characters).
Any SNMP entity (this term includes both managed entities and management
stations) can be assigned by its user community names.
Access Restriction Using SNMP Communities
In general, SNMP agents support two types of access rights:
• Read-only - The SNMP agent accepts and processes only SNMP getRequest
and getNextRequest commands from management stations which have the
same read-only community name.
• Read-write - The SNMP agent accepts and processes all the SNMP commands
received from a management station with the same write community name.
For each SNMP entity it is possible to define a list of the communities which
are authorized to communicate with it, and the access rights associated with
each community (this is the entity’s SNMP community name table). For
example, the SNMP community name table of the SNMP agent of the
MX-2100 can include three community names.
In accordance with the SNMP protocol, the SNMP community of the originating
entity is sent in each message.
When an SNMP message is received by the addressed entity, first it checks the
originator's community: if the community name of the message originator differs
from the community name specified for that type of message in the agent, the
message it discarded (SNMP agents of managed entities report this event by means
of an authentication failure trap).