RFC 1604 (rfc1604) - Page 2 of 46
Definitions of Managed Objects for Frame Relay Service
Alternative Format: Original Text Document
RFC 1604 Frame Relay Service MIB March 1994
1. The SNMPv2 Network Management Framework
The SNMPv2 Network Management Framework consists of four major
components. They are:
o RFC 1442 which defines the SMI, the mechanisms used for
describing and naming objects for the purpose of
management.
o STD 17, RFC 1213 defines MIB-II, the core set of managed
objects for the Internet suite of protocols.
o RFC 1445 which defines the administrative and other
architectural aspects of the framework.
o RFC 1448 which defines the protocol used for network
access to managed objects.
The Framework permits new objects to be defined for the purpose of
experimentation and evaluation.
2. 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 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.
3. Overview
These objects are used when the particular media being used to manage
is Frame Relay Service. At present, this applies to these values of
the ifType variable in the Internet-standard MIB:
frameRelayService (44)
This section provides an overview and background of how to use this
MIB and other potential MIBs when managing a Frame Relay Service.
Figure 1 shows the MIB stack that could be followed for managing a
Frame Relay Service. This is only an example and not meant to be
inclusive.
Frame Relay Service MIB Working Group