RFC 2239 (rfc2239) - Page 2 of 43
Definitions of Managed Objects for IEEE 802
Alternative Format: Original Text Document
RFC 2239 Managed Objects for IEEE 802.3 MAUs November 1997
Abstract
This memo defines an portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it defines objects for managing 10 and 100 Mb/second
Medium Attachment Units (MAUs) based on IEEE Std 802.3 Section 30,
"10 & 100 Mb/s Management," October 26, 1995.
1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework presently consists of three
major components. They are:
o the SMI, described in RFC 1902 [6] - the mechanisms used
for describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [5] - the core set of
managed objects for the Internet suite of protocols.
o the protocol, STD 15, RFC 1157 [10] and/or RFC 1905 [9] -
the protocol used for accessing managed information.
Textual conventions are defined in RFC 1903 [7], and conformance
statements are defined in RFC 1904 [8].
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
1.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.
de Graaf, et. al. Standards Track