SNMP Management
In addition, the
∙For
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
Management
Domains Under
SNMP
SNMP Communities
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.
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:
∙
∙
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
In accordance with the SNMP protocol, the SNMP community of the originating entity is sent in each message.