Definitions of Managed Objects for Frame Relay Service
RFC 1604

Document Type RFC - Proposed Standard (March 1994; No errata)
Obsoleted by RFC 2954
Obsoletes RFC 1596
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 1604 (Proposed Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                   T. Brown, Editor
Request for Comments: 1604                  Bell Communications Research
Obsoletes: 1596                                               March 1994
Category: Standards Track

                     Definitions of Managed Objects
                        for Frame Relay Service

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Abstract

   This memo defines an extension to the Management Information Base
   (MIB) for use with network management protocols in TCP/IP-based
   internets.  In particular, it defines objects for managing the Frame
   Relay Service.

Table of Contents

   1. The SNMPv2 Network Management Framework ...............    2
   2. Object Definitions ....................................    2
   3. Overview ..............................................    2
   3.1 Scope of MIB .........................................    3
   3.2 Frame Relay Service MIB Terminology ..................    5
   3.3 Apply MIB II to a Frame Relay Service ................    7
   4. Object Definitions ....................................   12
   4.1 The Frame Relay Service Logical Port Group ...........   12
   4.2 The Frame Relay Management VC Signaling Group ........   15
   4.3 The PVC End-Point Group ..............................   22
   4.4 Frame Relay PVC Connection Group .....................   30
   4.5 Frame Relay Accounting Groups ........................   37
   5. Frame Relay Network Service TRAPS .....................   40
   6. Conformance Information ...............................   43
   7. Acknowledgments .......................................   45
   8. References ............................................   45
   9. Security Considerations ...............................   46
   10. Author's Address .....................................   46

Frame Relay Service MIB Working Group                           [Page 1]
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                           [Page 2]
RFC 1604                Frame Relay Service MIB               March 1994

                ____________________________________________________
                |              |              |       |            |
                |              |              | SIP   |  RFC1490   |
                |              | X.25 MIB     | Relay | (no applic.|
                |              | for IW/Encap.| MIB   |  MIB)      |
                |              |              |       |            |
                |    MIB II    |-----------------------------------|
                |              |                                   |
                |   ifTable    |      Frame Relay Service MIB      |
Show full document text