Definitions of Managed Objects for Frame Relay Service
RFC 2954

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 12

Network Working Group                                        K. Rehbehn
Request for Comments: 2954                              Megisto Systems
Obsoletes: 1604                                               D. Fowler
Category: Standards Track                              Syndesis Limited
                                                           October 2000

                     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.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   This memo defines an extension to the Management Information Base
   (MIB) for use with network management protocols in Transmission
   Control Protocol/Internet Protocol-based (TCP/IP) internets.  In
   particular, it defines objects for managing the frame relay service.

   This document obsoletes RFC 1604.

Table of Contents

   1 The SNMP Management Framework ................................   2
   2 Overview .....................................................   3
   2.1 Scope of MIB ...............................................   3
   2.2 Transiting Multiple Frame Relay Networks ...................   5
   2.3 Access Control .............................................   5
   2.4 Frame Relay Service MIB Terminology ........................   6
   2.5 Relation to Other MIBs .....................................   8
   2.5.1 System Group .............................................   8
   2.5.2 Interfaces Table (ifTable, ifXtable) .....................   8
   2.5.3 Stack Table for DS1/E1 Environment .......................  12
   2.5.4 Stack Table for V.35 Environments ........................  14
   2.5.5 The Frame Relay/ATM PVC Service Interworking MIB .........  14
   2.6 Textual Convention Change ..................................  15
   3 Object Definitions ...........................................  15
   3.1 The Frame Relay Service Logical Port .......................  17

Rehbehn & Fowler            Standards Track                     [Page 1]
RFC 2954                Frame Relay Service MIB             October 2000

   3.2 Frame Relay Management VC Signaling ........................  22
   3.3 Frame Relay PVC End-Points .................................  32
   3.4 Frame Relay PVC Connections ................................  45
   3.5 Frame Relay Accounting .....................................  53
   3.6 Frame Relay Network Service Notifications ..................  56
   3.7 Conformance Information ....................................  57
   4 Acknowledgments ..............................................  67
   5 References ...................................................  67
   6 Security Considerations ......................................  69
   7 Authors' Addresses ...........................................  70
   APPENDIX A Update Information ..................................  71
   Intellectual Property Rights ...................................  75
   Full Copyright Statement .......................................  76

1.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o  An overall architecture, described in RFC 2571 [1].

   o  Mechanisms for describing and naming objects and events for the
      purpose of management.  The first version of this Structure of
      Management Information (SMI) is called SMIv1 and described in STD
      16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4].  The
      second version, called SMIv2, is described in STD 58, RFC 2578
      [5], STD 58, RFC 2579 [6] and STD 58, RFC 2580 [7].

   o  Message protocols for transferring management information.  The
      first version of the SNMP message protocol is called SNMPv1 and
      described in STD 15, RFC 1157 [8].  A second version of the SNMP
      message protocol, which is not an Internet standards track
      protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
      1906 [10].  The third version of the message protocol is called
      SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
      [12].

   o  Protocol operations for accessing management information.  The
      first set of protocol operations and associated PDU formats is
      described in STD 15, RFC 1157 [8].  A second set of protocol
      operations and associated PDU formats is described in RFC 1905
      [13].

   o  A set of fundamental applications described in RFC 2573 [14] and
      the view-based access control mechanism described in RFC 2575
      [15].

Rehbehn & Fowler            Standards Track                     [Page 2]