Background: Know: MAX-ACCESS, Recognize: sysObjectID
| Up | ||
| Previous | Next | |
|
Down |
Communities restrict access[]
SNMP communities can access the elements of communities differently (see SNMP Communities). SMI defines MAX-ACCESS for each object("MIB view"). For any network element, a subset of objects in the MIB that pertain to that element is called a SNMP MIB view. MAX-ACCESS is defines whether it makes “protocol sense” to read, write and/or create an instance of the object, or to include its value in a notification. This is the maximal level of access for the object. There are five kinds of access value here:
1. “read-write”: indicates that read and write access make “protocol sense”, but create does not;
2. “read-create”: indicates that read, write and create access make “protocol sense”;
3. “not-accessible”: indicates an auxiliary object;
4. “accessible-for-notify”: indicates an object which accessible only via a notification (e.g. , snmpTrapOID);
5. "read-only": indicates that read access make "protocol sense".
These values are ordered, from least to greatest: “not-accessible”, “accessible-for-notify”, “read-only”, “read-write”, “read-create”.
In addition, an element of the set {READ-ONLY, READ-WRITE} is called an SNPM ACCESS MODE. For each commuynity, each element defines an "access mode" for each object. The access level permitted is determined by access mode and max-access. please see MAX-ACCESS+Access Mode
References[]
RFC 1157 A Simple Network Management Protocol (SNMP)