2003 2009 Ericsson AB. All Rights Reserved.
The contents of this file are subject to the Erlang Public License, Version 1.1, (the "License"); you may not use this file except in compliance with the License. You should have received a copy of the Erlang Public License along with this software. If not, it can be retrieved online at http://www.erlang.org/. Software distributed under the License is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the License for the specific language governing rights and limitations under the License.

Mibs

Ingela Anderton
2003-05-19
A mibs.xml

## Structure

The OTP mibs are stored in the $OTP_ROOT/lib/otp_mibs/mibs/ directory. They are defined in SNMPv2 SMI syntax. An SNMPv1 version of the mib is delivered in the mibs/v1 directory. The compiled MIB is located under priv/mibs, and the generated .hrl file under the include directory. To compile a MIB that IMPORTS a MIB in the OTP_Mibs application, give the option {il, ["otp_mibs/priv/mibs"]} to the MIB compiler.

## OTP-MIB

The OTP-MIB mib represents information about Erlang nodes such as node name, number of running processes, virtual machine version etc. If the MIB should be used in a system, it should be loaded into an SNMP agent by using the API function otp_mib:load/1.

## OTP-REG

The OTP-REG mib defines the unique OTP subtree of object identifiers under the Ericsson subtree. Under the OTP subtree several object identifiers are defined. This module is typically included by OTP applications defining their own mibs, or ASN.1 modules in general, that require unique object identifiers under the OTP subtree.

## OTP-TC

The OTP-TC mib provides the textual convention datatype OwnerString.