IEEE 802.5 MIB using SMIv2
RFC 1743

 
Document Type RFC - Draft Standard (December 1994; No errata)
Obsoleted by RFC 1748
Obsoletes RFC 1231
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 1743 (Draft Standard)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                      K. McCloghrie
Request for Comments: 1743                                     E. Decker
Obsoletes: 1231                                      cisco Systems, Inc.
Category: Standards Track                                  December 1994

                       IEEE 802.5 MIB using SMIv2

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.

Table of Contents

   1. Introduction .............................................    1
   2. The SNMPv2 Network Management Framework ..................    2
   2.1 Object Definitions ......................................    2
   3. Overview .................................................    2
   3.1 MAC Addresses ...........................................    3
   3.2 Relationship to RFC 1213 ................................    3
   3.3 Relationship to RFC 1573 ................................    3
   3.3.1 Layering Model ........................................    3
   3.3.2 Virtual Circuits ......................................    3
   3.3.3 ifTestTable ...........................................    3
   3.3.4 ifRcvAddressTable .....................................    4
   3.3.5 ifPhysAddress .........................................    4
   3.3.6 ifType ................................................    4
   4. Definitions ..............................................    4
   5. Acknowledgements .........................................   23
   6. References ...............................................   23
   Appendix A. Changes from RFC 1231 ...........................   24
   Security Considerations .....................................   24
   Authors' Addresses ..........................................   25

1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes managed objects used for managing
   subnetworks which use the IEEE 802.5 Token Ring technology described
   in 802.5 Token Ring Access Method and Physical Layer Specifications,
   IEEE Standard 802.5-1989 [7].  This memo is a replacement for RFC
   1231.

McCloghrie & Decker                                             [Page 1]
RFC 1743               IEEE 802.5 MIB using SMIv2          December 1994

2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      o    RFC 1442 [1] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

      o    STD 17, RFC 1213 [2] defines MIB-II, the core set of managed
           objects for the Internet suite of protocols.

      o    RFC 1445 [3] which defines the administrative and other
           architectural aspects of the framework.

      o    RFC 1448 [4] 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.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.

3.  Overview

   This memo defines three tables: the 802.5 Interface Table, which
   contains state and parameter information which is specific to 802.5
   interfaces, the 802.5 Statistics Table, which contains 802.5
   interface statistics, and the 802.5 Timer Table, which contains the
   values of 802.5-defined timers. A managed system will have one entry
   in the 802.5 Interface Table and one entry in the 802.5 Statistics
   Table for each of its 802.5 interfaces.  The 802.5 Timer Table is
   obsolete, but its definition has been retained in this memo for
   backward compatibility.

   This memo also defines OBJECT IDENTIFIERs, some to identify interface
   tests for use with the ifTestTable [6], and some to identify Token
   Ring interface Chip Sets.

McCloghrie & Decker                                             [Page 2]
Show full document text