rfc1231.txt

来自「著名的RFC文档,其中有一些文档是已经翻译成中文的的.」· 文本 代码 · 共 1,291 行 · 第 1/4 页

Network Working Group                                      K. McCloghrie
Request for Comments: 1231                      Hughes LAN Systems, Inc.
                                                                  R. Fox
                                                         Synoptics, Inc.
                                                               E. Decker
                                                     cisco Systems, Inc.
                                                                May 1991


                       IEEE 802.5 Token Ring MIB

Status of this Memo

   This memo defines a MIB for 805.5 networks for use with the SNMP
   protocol.  This memo is a product of the Transmission Working Group
   of the Internet Engineering Task Force (IETF).  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.  Distribution of
   this memo is unlimited.

Table of Contents

   1. Abstract ..............................................    1
   2. The Network Management Framework.......................    2
   3. Objects ...............................................    2
   3.1 Format of Definitions ...............................     3
   4. Overview ..............................................    3
   4.1 Scope of Definitions ................................     3
   4.2 Textual Conventions .................................     3
   5. Definitions ...........................................    4
   6. Acknowledgements ......................................   21
   7. References ............................................   22
   8. Security Considerations................................   23
   9. Authors' Addresses.....................................   23

1.  Abstract

   This memo defines an experimental portion of the Management
   Information Base (MIB) for use with network management protocols in
   TCP/IP-based internets.  In particular, this memo defines 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.






Transmission Working Group                                      [Page 1]

RFC 1231                     IEEE 802.5 MIB                     May 1991


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
   DESCRIPTOR, to also refer to the object type.

   The syntax of an object type defines the abstract data structure
   corresponding to that object type.  The ASN.1 language is used for
   this purpose.  However, the SMI [3] purposely restricts the ASN.1
   constructs which may be used.  These restrictions are explicitly made
   for simplicity.

   The encoding of an object type is simply how that object type is
   represented using the object type's syntax.  Implicitly tied to the
   notion of an object type's syntax and encoding is how the object type
   is represented when being transmitted on the network.

   The SMI specifies the use of the basic encoding rules of ASN.1 [8],
   subject to the additional requirements imposed by the SNMP.




Transmission Working Group                                      [Page 2]

RFC 1231                     IEEE 802.5 MIB                     May 1991


3.1.  Format of Definitions

   Section 5 contains contains the specification of all object types
   contained in this MIB module.  The object types are defined using the
   conventions defined in the SMI, as amended by the extensions
   specified in [9,10].

4.  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.  Implementation of the 802.5
   Timer Table is optional.

   This memo also defines OBJECT IDENTIFIERs, some to identify 802.5
   tests, for use with the ifExtnsTestTable defined in [11], and some to
   identify Token Ring interface Chip Sets, for use with the
   ifExtnsChipSet object defined in [11].

4.1.  Scope of Definitions

   All objects defined in this memo are registered in a single subtree
   within the experimental namespace [3], and are for use with every
   interface which conforms to the IEEE 802.5 Token Ring Access Method
   and Physical Layer Specifications [10].  At present, this applies to
   interfaces for which the ifType variable in the Internet-standard MIB
   [4,6] has the value:

              iso88025-tokenRing(9)

   For these interfaces, the value of the ifSpecific variable in the
   MIB-II [6] has the OBJECT IDENTIFIER value:

               dot5    OBJECT IDENTIFIER ::= { experimental 4 }

   as defined below.

4.2.  Textual Conventions

   A new datatype, MacAddress, is introduced as a textual convention in
   this document.  This textual convention has NO effect on either the
   syntax nor the semantics of any managed object. Objects defined using
   this convention are always encoded by means of the rules that define
   their primitive type.  Hence, no changes to the SMI or the SNMP are



Transmission Working Group                                      [Page 3]

RFC 1231                     IEEE 802.5 MIB                     May 1991


   necessary to accommodate this textual convention which is adopted
   merely for the convenience of readers.

5.  Definitions


          RFC1231-MIB DEFINITIONS ::= BEGIN

          --                 IEEE 802.5 Token Ring MIB

          IMPORTS
                  experimental
                          FROM RFC1155-SMI
                  OBJECT-TYPE
                          FROM RFC-1212;

          --  This MIB Module uses the extended OBJECT-TYPE macro as
          --  defined in [9].



          dot5    OBJECT IDENTIFIER ::= { experimental 4 }

          -- All representations of MAC addresses in this MIB Module
          -- use, as a textual convention (i.e. this convention does
          -- not affect their encoding), the data type:

          MacAddress ::= OCTET STRING (SIZE (6))    -- a 6 octet
                                                    -- address in the
                                                    -- "canonical" order
          -- defined by IEEE 802.1a, i.e., as if it were transmitted
          -- least significant bit first, even though 802.5 (in
          -- contrast to other 802.x protocols) requires MAC addresses
          -- to be transmitted most significant bit first.
          --
          -- 16-bit addresses, if needed, are represented by setting
          -- their upper 4 octets to all 0's, i.e., AAFF would be
          -- represented as 00000000AAFF.



          -- The Interface Table

          -- This table contains state and parameter information which
          -- is specific to 802.5 interfaces.  It is mandatory that
          -- systems having 802.5 interfaces implement this table in
          -- addition to the generic interfaces table [4,6] and its
          -- generic extensions [11].



Transmission Working Group                                      [Page 4]

RFC 1231                     IEEE 802.5 MIB                     May 1991


          dot5Table  OBJECT-TYPE
                     SYNTAX  SEQUENCE OF Dot5Entry
                     ACCESS  not-accessible
                     STATUS  mandatory
                     DESCRIPTION
                             "This table contains Token Ring interface
                             parameters and state variables, one entry
                             per 802.5 interface."
                     ::= { dot5 1 }

          dot5Entry  OBJECT-TYPE
                     SYNTAX  Dot5Entry
                     ACCESS  not-accessible
                     STATUS  mandatory
                     DESCRIPTION
                             "A list of Token Ring status and parameter
                              values for an 802.5 interface."
                     INDEX   { dot5IfIndex }
                     ::= { dot5Table 1 }

          Dot5Entry
              ::= SEQUENCE {
                      dot5IfIndex
                          INTEGER,
                      dot5Commands
                          INTEGER,
                      dot5RingStatus
                          INTEGER,
                      dot5RingState
                          INTEGER,
                      dot5RingOpenStatus
                          INTEGER,
                      dot5RingSpeed
                          INTEGER,
                      dot5UpStream
                          MacAddress,
                      dot5ActMonParticipate
                          INTEGER,
                      dot5Functional
                          MacAddress
                  }

          dot5IfIndex  OBJECT-TYPE
                     SYNTAX  INTEGER
                     ACCESS  read-only
                     STATUS  mandatory
                     DESCRIPTION
                             "The value of this object identifies the



Transmission Working Group                                      [Page 5]

RFC 1231                     IEEE 802.5 MIB                     May 1991


                              802.5 interface for which this entry
                              contains management information.  The
                              value of this object for a particular
                              interface has the same value as the
                              ifIndex object, defined in [4,6],
                              for the same interface."
                     ::= { dot5Entry 1 }

          dot5Commands  OBJECT-TYPE
                     SYNTAX  INTEGER {
                                   no-op(1),
                                   open(2),
                                   reset(3),
                                   close(4)
                             }
                     ACCESS  read-write
                     STATUS  mandatory
                     DESCRIPTION
                             "When this object is set to the value of
                              open(2), the station should go into the
                              open state.  The progress and success of
                              the open is given by the values of the
                              objects dot5RingState and
                              dot5RingOpenStatus.
                                  When this object is set to the value
                              of reset(3), then the station should do
                              a reset.  On a reset, all MIB counters
                              should retain their values, if possible.
                              Other side affects are dependent on the
                              hardware chip set.
                                  When this object is set to the value
                              of close(4), the station should go into
                              the stopped state by removing itself
                              from the ring.
                                  Setting this object to a value of
                              no-op(1) has no effect.
                                  When read, this object always has a