RFC 2037 (rfc2037) - Page 2 of 35

Entity MIB using SMIv2

RFC 2037                 Entity MIB using SMIv2             October 1996


1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for managing
   multiple logical and physical entities managed by a single SNMP
   agent.

2.  The SNMP Network Management Framework

   The SNMP Network Management Framework presently consists of three
   major components.  They are:

   o    the SMI, described in RFC 1902 [1], - the mechanisms used for
        describing and naming objects for the purpose of management.

   o    the MIB-II, STD 17, RFC 1213 [2], - the core set of managed
        objects for the Internet suite of protocols.

   o    the protocol, RFC 1157 [6] and/or RFC 1905 [4], - the protocol
        for accessing managed information.

   Textual conventions are defined in RFC 1903 [3], and conformance
   statements are defined in RFC 1904 [5].

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

   This memo specifies a MIB module that is compliant to the SNMPv2 SMI.
   A semantically identical MIB conforming to the SNMPv1 SMI can be
   produced through the appropriate translation.

2.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI.  In particular, each object type is named by an
   OBJECT IDENTIFIER, an administratively assigned name.  The object
   type together with an object instance serves to uniquely identify a
   specific instantiation of the object.  For human convenience, we
   often use a textual string, termed the descriptor, to refer to the
   object type.








McCloghrie & Bierman        Standards Track