RAD Data comm Management Domains Under Snmp, MIBs Supported by the LRS-24 Snmp Agent

LRS-24Installation and Operation Manual Appendix C SNMP Management

MIBs Supported by the LRS-24 SNMP Agent

The interpretation of the relevant MIBs is a function of the SNMP agent of each managed entity. CM-2 SNMP agent supports the standard MIB-II (RFC 1158).

In addition, LRS-24 SNMP agent supports the RAD-private (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(6).

TBD

Enterprise-specific MIBs supported by RAD equipment, including the LRS-24, are available in ASN.1 format from the RAD Technical Support Department.

Management Domains Under SNMP

In principle, SNMP enables 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 a case-sensitive alphanumeric string defined by the user (LRS-24 SNMP agents support community names of up to 20 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-onlySNMP agent accepts and processes only SNMP getRequest and getNextRequest commands from management stations that have the same read-only community name.

Read-writeSNMP 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 name table of the entity). For example, the SNMP community name table of the SNMP agent of LRS-24 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, it first checks the originator's community first. If the community name of the message originator differs from the community name specified for that type of message in the SNMP community names table of the recipient, the message is discarded (SNMP agents of managed entities usually report this event by means of an authentication failure trap).

SNMP Environment C-3

Order from: Cutter Networks Ph:727-398-5252/Fax:727-397-9610 www.bestdatasource.com