RAD Data comm IPmux-16 operation manual Management Information Base MIB, MIB Structure

Appendix B SNMP Management IPmux-16Installation and Operation Manual

•getNextRequest: Command for retrieving sequentially specific management information from the managed entity. The managed entity responds with a getResponse message.

•setRequest: Command for manipulating specific management information within the managed entity. The managed entity responds with a getResponse message.

•trap: Management message carrying unsolicited information on extraordinary events, which are events that occurred not in response to a management operation reported by the managed entity.

Management Information Base (MIB)

The MIB includes a collection of managed objects. A managed object is defined as a parameter that can be managed, such as a performance statistics value. The MIB includes the definitions of relevant managed objects. Various MIBs can be defined for various management purposes or types of equipment.

An object definition includes the range of values (also called instances) and the following access rights:

•Read-only: Instances of that object can be read, but cannot be set.

•Read-write: Instances of that object can be read or set.

•Write-only: Instances of that object can be set, but cannot be read.

•Not accessible: Instances of that object cannot be read, or set.

MIB Structure

The MIB has an inverted tree-like structure, with each definition of a managed object forming one leaf, located at the end of a branch of that tree.

Each leaf in the MIB is reached by a unique path. Thus, by numbering the branching points starting with the top, each leaf can be uniquely defined by a sequence of numbers.

The formal description of the managed objects and the MIB structure is provided in a special standardized format, called ASN.1 (Abstract Syntax Notation 1). Since the general collection of MIBs can also be organized in a similar structure, under IAB (Internet Activities Board) supervision, any parameter included in a MIB that is recognized by the IAB is uniquely defined.

To provide the flexibility necessary in a global structure, MIBs are classified in various classes (branches). One is the experimental branch and another the group of private (enterprise-specific) branch.

Under the private enterprise-specific branch of MIBs, each enterprise (manufacturer) can be assigned a number, which is its enterprise number. The assigned number designates the top of an enterprise-specific sub-tree of non- standard MIBs. Within this context, RAD has been assigned the enterprise number 164. Therefore, enterprise MIBs published by RAD can be found under 1.3.6.1.4.1.164.

B-2 SNMP Environment