datatracker.ietf.org
Sign in
Version 5.7.1.p2, 2014-10-29
Report a bug

OSPF Version 2 Management Information Base
RFC 1253

Document type: RFC - Proposed Standard (August 1991; No errata)
Obsoleted by RFC 1850
Obsoletes RFC 1252
Document stream: Legacy
Last updated: 2013-03-02
Other versions: plain text, pdf, html

Legacy State: (None)
Document shepherd: No shepherd assigned

IESG State: RFC 1253 (Proposed Standard)
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                          F. Baker
Request for Comments: 1253                                          ACC
Obsoletes: RFC 1252                                           R. Coltun
                                                Computer Science Center
                                                            August 1991

               OSPF Version 2 Management Information Base

Status of this Memo

   This RFC specifies an IAB standards track protocol for the Internet
   community, and requests discussion and suggestions for improvements.
   Please refer to the current edition of the "IAB Official Protocol
   Standards" for the standardization state and status of this protocol.
   This memo replaces RFC 1252 which contained an error in the
   "standard-mib" number assignment in Section 5.  Distribution of this
   memo is unlimited.

Table of Contents

   1. Abstract .............................................    2
   2. The Network Management Framework......................    2
   3. Objects ..............................................    2
   3.1 Format of Definitions ...............................    3
   4. Overview .............................................    3
   4.1 Textual Conventions .................................    3
   4.2 Structure of MIB ....................................    3
   4.2.1 General Variables .................................    4
   4.2.2 Area Data Structure and Area Stub Metric Table ....    4
   4.2.3 Link State Database ...............................    4
   4.2.4 Address Table and Host Tables .....................    4
   4.2.5 Interface and Interface Metric Tables .............    4
   4.2.6 Virtual Interface Table ...........................    4
   4.2.7 Neighbor and Virtual Neighbor Tables ..............    4
   4.3 Conceptual Row Creation .............................    5
   4.4 Default Configuration ...............................    5
   5. Definitions ..........................................    7
   5.1 OSPF General Variables ..............................    8
   5.2 OSPF Area Data Structure ............................   11
   5.3 OSPF Area Default Metric Table ......................   14
   5.4 OSPF Link State Database ............................   16
   5.5 OSPF Address Range Table ............................   19
   5.6 OSPF Host Table .....................................   21
   5.7 OSPF Interface Table ................................   23
   5.8 OSPF Interface Metric Table .........................   28
   5.9 OSPF Virtual Interface Table ........................   31
   5.10 OSPF Neighbor Table ................................   34

Baker & Coltun                                                  [Page 1]
RFC 1253                   OSPF Version 2 MIB                August 1991

   5.11 OSPF Virtual Neighbor Table ........................   38
   6. Acknowledgements .....................................   40
   7. References ...........................................   40
   8. Security Considerations...............................   41
   9. Authors' Addresses....................................   42

1.  Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in TCP/IP-based internets.
   In particular, it defines objects for managing OSPF Version 2.

2.  The Network Management Framework

   The Internet-standard Network Management Framework consists of three
   components.  They are:

      RFC 1155 which defines the SMI, the mechanisms used for describing
      and naming objects for the purpose of management.  RFC 1212
      defines a more concise description mechanism, which is wholly
      consistent with the SMI.

      RFC 1156 which defines MIB-I, the core set of managed objects for
      the Internet suite of protocols.  RFC 1213, defines MIB-II, an
      evolution of MIB-I based on implementation experience and new
      operational requirements.

      RFC 1157 which defines the SNMP, the protocol used for network
      access to managed objects.

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

3.  Objects

   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) [7]
   defined in the SMI.  In particular, each object has a name, a syntax,
   and an encoding.  The name is an object identifier, an
   administratively assigned name, which specifies an object type.  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 OBJECT

[include full document text]