RAD Data comm ASMI-450 - Manual (Page 108)

SNMP Management
B-4 ASMi-450 Installation and Operation Manual
In addition, the ASMi-450 SNMP agent supports the RAD-private (enterprise-
specific) MIB.
•
For ASMi-450/1152, the RAD-private MIB is identified as (read the
following as a continuous string):
iso(1).org(3).dod(6).internet(1).private(4).enterprise
s(1).rad(164).radGen(6).systems(1).radSysWAN(3).radASM
i450R1152Sa
•
For ASMi-450/768, the RAD-private MIB is identified as:
iso(1).org(3).dod(6).internet(1).private(4).enterprise
s(1).rad(164).radGen(6).systems(1).radSysWAN(3).radASM
i450R768Sa
Enterprise-specific MIBs supported by RAD equipment, including those for the
ASMi-450, are available in ASN.1 format from the RAD Technical Support
Department.
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 delimit management domains.
SNMP Communities
To enable the delimitation of management domains, SNMP uses
“communities”. Each community is identified by a name, which is an
alphanumeric string of up to 32 characters defined by the user.
Any SNMP entity (this term includes both managed entities and management
stations) is assigned by its user a community name.
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 read-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 SNMP community names table of the entity). For
example, the SNMP community names table of the ASMi-450 can include three
community names.
In accordance with the SNMP protocol, the SNMP community of the
originating entity is sent in each message.