Object IDentifier. A number that identifies an object's position in a global object registration tree. An example is 1.3.6.1.4.1.45.1.3.2, that corresponds to ios.org.dod.internet.private.enterprise.synoptics.1.3.2, and identifies a Synoptics3000 concentrator. There may also be a MIB name for the object identifier (for example, cisco for a Cisco router). [S] In CMIP, one half of the Relative Distinguished Name (RDN) pair, that identifies an object's position in an MIT. See Name. [C] An Object IDentifier uses a system for describing an object's class by reference to a standard tree structure of descriptions. Each node of the tree is assigned a number, so that an object's identifier is a sequence of numbers. In Internet usage, the identifiers are shown as a string of numbers delimited by dots (for example, 0.128.45.12); in the OSI context (and in Solstice EM) the numbers are delimited by blanks and the entire sequence is surrounded by braces (for example, { 0 128 45 12 }).

The range of OIDs implied by a subtree. For instance, the subtree 1.2.3 carries an implied range of 1.2.3 up to but not including 1.2.4.

Open Network Computing/Remote Procedure Call.

Open Systems Foundation. UNIX consortium including Hewlett-Packard, IBM, and DEC, founded 1988. Sponsors of DME.

Open Systems Interconnection. General name for the set of network management conventions adopted by the International Standards Organization. An international effort (via ISO) to facilitate communications among computers of varying manufacturers and technology.

OSI Network Management Forum. An OSI group formed to develop and promulgate definitions and standards for the SNMP, PING, and CMIP protocols.

An attempt by one subagent to register a subtree that is contained within or contains a subtree already registered by another subagent.

An instance of the class containing a (child) object. [C]

A periodic request for MIB or MIT object-class status information sent to a managed object. Configurable in some cases by the network administrator via Solstice EM Request Designer. SNMP tends to be poll-oriented, while CMIP tends to be event-oriented.

A proprietary group is a group of attributes that is specific to a particular product vendor and has not been proposed or standardized by the DMTF special interest group. Proprietary groups allow vendors to differentiate their product and demonstrate competitive advantages.

A set of rules used by computers to communicate with each other. A protocol is also the private language and procedures of an OSI layer.

The act of a subagent informing the Master Agent that the subagent will provide management of a MIB subtree.

A required group is a group of attributes that are required to be included in a MIF file in order to be DMI-compliant. Currently, the only required group is the ComponentID group, that must be group 1 in any MIF file.

Request for Comment. The series of documents that formalize protocols within the Internet (TCP/IP-based) community are referred to as RFC, the last phase in the formal standardization process before the document is made official. RFCs are published by the Internet Engineering Task Force (IETF).

The term routing refers to the process of selecting a path to send packets over, and router is any computer able to make such a selection. Although both hosts and gateways do routing, the term router is commonly used for a device that interconnects two networks (See gateway).

Service Access Point.The notional point where a service user and a layer entity meet so that services may be offered by the layer entity to the particular user.

A bit-mask so that multiple event severities may be selected for a filter entry.

An object that shares a common parent class with the object in question. [C]

Structure of Management Information.

SunNet Manager. To export your subagent to Site/SunNet/Domain Manager (SNM), you need an SNM schema file.

Simple Network Management Protocol. Protocol for exchanging information between network managers and "agents', processes within various managed objects that are able to report their status on request. The protocol was introduced as a simple interim solution, but is at present widely used in the Internet environment. It is a connection-less protocol, with the view of continuing to receive information from managed objects even when network performance is degraded and a connection-based reliable transport may fail.

Simple Network Management Protocol Daemon.

An MIF group that has been proposed to and accepted by the DMTF special interest group and that describes attributes applicable to all, or most all, products of a similar type, such as all printers or all network interface cards. Currently, standard groups are approved for PC Systems, have been proposed for Network Information Cards, and are in development for Printers, Servers, Software and Modems.

A description of a managed object in a point in time with respect to a request. At any given moment, a request, reflecting the target managed object, is in some state defined in that request or is undergoing a transition between states. You may think of a state as a receptacle that holds transitions to other states. While in a state, a request repeatedly, at intervals determined by the state's poll rate, tests the conditions associated with each transition leading from that state.

In addition to a poll rate, each state has a severity associated with it. It also has a name and a description. Between any two states, there is a single transition (one-way or two-way) with, potentially, multiple conditions associated with each transition.

There is one required state, the ground (or init) state. The only requirement for this state is that it have a severity of "normal". Other states are of your choosing.