IEEE 802.5 Station Source Routing MIB using SMIv2

Network Working Group                                      K. McCloghrie
Request for Comments: 1749                                      F. Baker
Updates: <a href="./rfc1748">1748</a>                                                  E. Decker
Category: Standards Track                            cisco Systems, Inc.
                                                           December 1994


           <span class="h1">IEEE 802.5 Station Source Routing MIB using SMIv2</span>

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

   <a href="#section-1">1</a>. Introduction .............................................    <a href="#page-1">1</a>
   <a href="#section-2">2</a>. The SNMPv2 Network Management Framework ..................    <a href="#page-2">2</a>
   <a href="#section-2.1">2.1</a> Object Definitions ......................................    <a href="#page-2">2</a>
   <a href="#section-3">3</a>. Overview .................................................    <a href="#page-2">2</a>
   <a href="#section-3.1">3.1</a> Source Routing ..........................................    <a href="#page-2">2</a>
   <a href="#section-3.2">3.2</a> Relationship to <a href="./rfc1748">RFC 1748</a> ................................    <a href="#page-3">3</a>
   <a href="#section-3.3">3.3</a> Relationship to <a href="./rfc1525">RFC 1525</a> ................................    <a href="#page-3">3</a>
   <a href="#section-3.4">3.4</a> Static Source Routes ....................................    <a href="#page-4">4</a>
   <a href="#section-3.5">3.5</a> Destinations on the Local Ring ..........................    <a href="#page-4">4</a>
   <a href="#section-4">4</a>. Definitions ..............................................    <a href="#page-4">4</a>
   <a href="#section-5">5</a>. Acknowledgements .........................................    <a href="#page-8">8</a>
   <a href="#section-6">6</a>. References ...............................................    <a href="#page-8">8</a>
   <a href="#section-7">7</a>. Security Considerations ..................................    <a href="#page-9">9</a>
   <a href="#section-8">8</a>. Authors' Addresses .......................................   <a href="#page-10">10</a>

<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   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 by IEEE 802.5 end-
   stations for managing source routes on a Token Ring network where
   IEEE source-routing is in use.  IEEE source-routing is described in
   802.5 Token Ring Access Method and Physical Layer Specifications [<a href="#ref-8" title=""Token Ring Access Method and Physical Layer Specifications"">8</a>]
   and related ISO publications [<a href="#ref-9" title=""Information technology - Local and metropolitan area networks - Part 5: Token ring access method and physical layer specifications"">9</a>, <a href="#ref-10" title=""Information technology - Telecommunications and information exchange between systems - Local area networks - Media access control (MAC) bridges"">10</a>, <a href="#ref-11" title=""Source Routing Operation by End Systems"">11</a>].

   This memo is an incremental update to <a href="./rfc1748">RFC 1748</a> [<a href="#ref-6" title=""IEEE 802.5 Token Ring MIB using SMIv2"">6</a>].  It is documented
   separately from the <a href="./rfc1748">RFC 1748</a> solely due to the latter's maturity
   within the Internet standardization process.




<span class="grey">McCloghrie, Baker & Decker                                      [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  The SNMPv2 Network Management Framework</span>

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

      o    <a href="./rfc1442">RFC 1442</a> [<a href="#ref-1" title=""Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)"">1</a>] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

      o    STD 17, <a href="./rfc1213">RFC 1213</a> [<a href="#ref-2" title=""Management Information Base for Network Management of TCP/IP-based internets: MIB- II"">2</a>] defines MIB-II, the core set of managed
           objects for the Internet suite of protocols.

      o    <a href="./rfc1445">RFC 1445</a> [<a href="#ref-3" title=""Administrative Model for version 2 of the Simple Network Management Protocol (SNMPv2)"">3</a>] which defines the administrative and other
           architectural aspects of the framework.

      o    <a href="./rfc1448">RFC 1448</a> [<a href="#ref-4" title=""Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)"">4</a>] 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.

<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>.  Object Definitions</span>

   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.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Overview</span>

   This memo defines a single table: the 802.5 Station Source Routing
   Table, which contains the source routes known by a end-station on an
   IEEE 802.5 Token Ring network in which IEEE source-routing is in use.

<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>.  Source Routing</span>

   Source routing extends the 802.5 protocol [<a href="#ref-8" title=""Token Ring Access Method and Physical Layer Specifications"">8</a>] by assigning a unique
   ring number to each ring within the extended LAN, and a bridge number
   to each source routing bridge's connection to a ring.  A Routing
   Information Field (RIF) must be included in frames which need to
   traverse multiple rings.  The format of the RIF is:






<span class="grey">McCloghrie, Baker & Decker                                      [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


              octets octets octets         octets
               1&2    3&4    5&6            17&18
             +------+------+------+-------+------+
             |  RC  |  RD  |  RD  | ...   |  RD  |
             +------+------+------+-------+------+
                     <---- 0 to 8 RD fields ---->

   The format of the Routing Control (RC) field is:

                            octet 1         octet 2
                       +---------------+---------------+
                       |b b b l l l l l|d f f f 0 0 0 0|
                       +---------------+---------------+
                          ^       ^     ^   ^
                          |       |     |   |
     Explorer indicator --+       |     |   +-- Max frame length*
            Length of RIF field --+     +-- Direction to use RDs

     * Note that the length of the Maximum frame length subfield
       has recently been extended to 6 bits.

   The format of each Routing Descriptor (RD) field is:

                     octet 1         octet 2
                 +---------------+---------------+
                 |r r r r r r r r r r r r i i i i|
                 +---------------+---------------+
                  <---- ring number ----> <----->
                                             ^
                                             |
                             bridge number --+

<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>.  Relationship to <a href="./rfc1748">RFC 1748</a></span>

   <a href="./rfc1748">RFC 1748</a> [<a href="#ref-6" title=""IEEE 802.5 Token Ring MIB using SMIv2"">6</a>], the IEEE 802.5 MIB, defines managed objects used for
   interfaces to IEEE 802.5 Token Ring subnetworks.  This memo is an
   incremental update to <a href="./rfc1748">RFC 1748</a>, and is documented independently
   solely due to the maturity of the definitions contained within <a href="./rfc1748">RFC</a>
   <a href="./rfc1748">1748</a>.

<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>.  Relationship to <a href="./rfc1525">RFC 1525</a></span>

   <a href="./rfc1525">RFC 1525</a> [<a href="#ref-7" title=""Definitions of Managed Objects for Source Routing Bridges"">7</a>] defines the MIB objects specific to source-routing for
   source-routing and SRT bridges.  This memo defines the MIB objects
   specific to source-routing for source-routing end-stations.






<span class="grey">McCloghrie, Baker & Decker                                      [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


<span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a>.  Static Source Routes</span>

   It is unclear how many, if any, existing systems allow the creation
   or deletion of "static" 802.5 source routes by network management.
   However, SNMPv2 SMI defines that the MAX-ACCESS clause as specifying
   the maximal level of access which makes "protocol sense".  Thus, this
   memo provides support for static source routes through the
   dot5SrRouteStatus object, but the conformance statements allow for
   stations which do not support static source routes, by requiring that
   compliant agents only need provide read-access to dot5SrRouteStatus.

<span class="h3"><a class="selflink" id="section-3.5" href="#section-3.5">3.5</a>.  Destinations on the Local Ring</span>

   Entries should be included in the dot5SrRouteTable for destination
   MAC addresses which are on the same ring as the instrumented 802.5
   interface.  For such entries, dot5SrRouteDescr has the value of the
   zero-length string, and dot5SrRouteControl has the corresponding
   value.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Definitions</span>

TOKENRING-STATION-SR-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE
                                         FROM SNMPv2-SMI
    TEXTUAL-CONVENTION, RowStatus, MacAddress
                                         FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP      FROM SNMPv2-CONF
    mib-2, ifIndex                       FROM <a href="./rfc1213">RFC1213</a>-MIB;

dot5SrMIB MODULE-IDENTITY
    LAST-UPDATED "9412161000Z"
    ORGANIZATION "IETF Interfaces MIB Working Group"
    CONTACT-INFO
            "       Keith McCloghrie
            Postal: Cisco Systems, Inc.
                    170 West Tasman Drive
                    San Jose, CA  95134-1706
                    US

             Phone: +1 408 526 5260
             Email: [email protected]"
    DESCRIPTION
            "The MIB module for managing source routes in
            end-stations on IEEE 802.5 Token Ring networks."
    ::= { mib-2 42 }




<span class="grey">McCloghrie, Baker & Decker                                      [Page 4]</span>

<span id="page-5" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


dot5SrMIBObjects OBJECT IDENTIFIER ::= { dot5SrMIB 1 }

SourceRoute ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "1x:"
    STATUS       current
    DESCRIPTION
                 "Represents a Source Route, containing an
                 embedded sequence of bridge and ring ID's,
                 as used by 802.5 Source Routing."
    REFERENCE    "Annex C of ISO/IEC 10038: 1993,
                 [ANSI/IEEE Std 802.1D, 1993]"
    SYNTAX       OCTET STRING (SIZE(0..30))


--           The 802.5 Station Source Route Table
--

dot5SrRouteTable   OBJECT-TYPE
    SYNTAX      SEQUENCE OF Dot5SrRouteEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
               "The table of source-routing routes.
               This represents the 802.5 RIF database."
    ::= { dot5SrMIBObjects 1 }

dot5SrRouteEntry  OBJECT-TYPE
    SYNTAX      Dot5SrRouteEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
                "Information on a specific route.

                An entry is created whenever a 'Single Path
                Explorer' or an 'All Paths Explorer' discovers
                a route to a neighbor not currently in the table,
                or whenever an 'All Paths Explorer' discovers a
                better (e.g., shorter) route than the route currently
                stored in the table.  This is done on behalf of
                any network layer client.

                The ifIndex value in the INDEX clause refers to
                the value of MIB-II's ifIndex object for the
                interface on which the route is in effect."
    INDEX  { ifIndex, dot5SrRouteDestination }
    ::= { dot5SrRouteTable 1 }

Dot5SrRouteEntry ::= SEQUENCE {



<span class="grey">McCloghrie, Baker & Decker                                      [Page 5]</span>

<span id="page-6" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


    dot5SrRouteDestination   MacAddress,
    dot5SrRouteControl       OCTET STRING,
    dot5SrRouteDescr         SourceRoute,
    dot5SrRouteStatus        RowStatus
}

dot5SrRouteDestination  OBJECT-TYPE
    SYNTAX      MacAddress
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
               "The destination of this route."
    ::= { dot5SrRouteEntry 2 }

dot5SrRouteControl  OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE(2))
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
               "The value of Routing Control field for this
               route."
    REFERENCE  "Annex C of ISO/IEC 10038: 1993,
               [ANSI/IEEE Std 802.1D, 1993]"
    ::= { dot5SrRouteEntry 3 }

dot5SrRouteDescr  OBJECT-TYPE
    SYNTAX      SourceRoute
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
               "The embedded sequence of bridge and ring ID's
               for this route.  For destinations on the
               local ring, the value of this object is
               the zero-length string."
    REFERENCE  "Annex C of ISO/IEC 10038: 1993,
               [ANSI/IEEE Std 802.1D, 1993]"
    ::= { dot5SrRouteEntry 4 }

dot5SrRouteStatus  OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
             "The status of this row.  Values of the instances
             of dot5SrRouteControl and dot5SrRouteDescr can be
             modified while the row's status is 'active."
    ::= { dot5SrRouteEntry 5 }




<span class="grey">McCloghrie, Baker & Decker                                      [Page 6]</span>

<span id="page-7" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


-- conformance information

dot5SrConformance OBJECT IDENTIFIER ::= { dot5SrMIB 2 }

dot5SrGroups      OBJECT IDENTIFIER ::= { dot5SrConformance 1 }
dot5SrCompliances OBJECT IDENTIFIER ::= { dot5SrConformance 2 }


-- compliance statements

dot5SrCompliance MODULE-COMPLIANCE
    STATUS  current
    DESCRIPTION
        "The compliance statement for SNMPv2 entities
        which implement the IEEE 802.5 Station Source Route
        MIB."

    MODULE  -- this module
        MANDATORY-GROUPS { dot5SrRouteGroup }

        OBJECT      dot5SrRouteStatus
        SYNTAX      INTEGER { active(1) }   -- subset of values
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is not required, and only the 'active'
            value need be supported."

        OBJECT      dot5SrRouteControl
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is not required."

        OBJECT      dot5SrRouteDescr
        MIN-ACCESS  read-only
        DESCRIPTION
            "Write access is not required."

    ::= { dot5SrCompliances 1 }


-- units of conformance

dot5SrRouteGroup  OBJECT-GROUP
    OBJECTS   { dot5SrRouteControl,
                dot5SrRouteDescr,
                dot5SrRouteStatus
              }
    STATUS    current



<span class="grey">McCloghrie, Baker & Decker                                      [Page 7]</span>

<span id="page-8" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


    DESCRIPTION
        "A collection of objects providing for the management of
        source routes in stations on IEEE 802.5 source-routing
        networks."
    ::= { dot5SrGroups 1 }

END

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Acknowledgements</span>

   The need for this MIB module was agreed upon by the members of the
   IETF Interfaces Working Group, and the definitions were derived from
   experience with enterprise-specific MIBs presented to the Working
   Group.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  References</span>

   [<a id="ref-1">1</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
       of Management Information for version 2 of the Simple Network
       Management Protocol (SNMPv2)", <a href="./rfc1442">RFC 1442</a>, SNMP Research,Inc.,
       Hughes LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon
       University, April 1993.

   [<a id="ref-2">2</a>] McCloghrie, K., and M. Rose, Editors, "Management Information
       Base for Network Management of TCP/IP-based internets: MIB- II",
       STD 17, <a href="./rfc1213">RFC 1213</a>, Hughes LAN Systems, Performance Systems
       International, March 1991.

   [<a id="ref-3">3</a>] Galvin, J., and K. McCloghrie, "Administrative Model for version
       2 of the Simple Network Management Protocol (SNMPv2)", <a href="./rfc1445">RFC 1445</a>,
       Trusted Information Systems, Hughes LAN Systems, April 1993.

   [<a id="ref-4">4</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
       Operations for version 2 of the Simple Network Management
       Protocol (SNMPv2)", <a href="./rfc1448">RFC 1448</a>, SNMP Research,Inc., Hughes LAN
       Systems, Dover Beach Consulting, Inc., Carnegie Mellon
       University, April 1993.

   [<a id="ref-5">5</a>] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
       Conventions for version 2 of the Simple Network Management
       Protocol (SNMPv2)", <a href="./rfc1443">RFC 1443</a>, SNMP Research Inc., Hughes LAN
       Systems, Dover Beach Consulting, Inc., Carnegie Mellon
       University, April 1993.

   [<a id="ref-6">6</a>] McCloghrie, K., and E. Decker, "IEEE 802.5 Token Ring MIB using
       SMIv2", <a href="./rfc1748">RFC 1748</a> cisco Systems, Inc., December 1994.





<span class="grey">McCloghrie, Baker & Decker                                      [Page 8]</span>

<span id="page-9" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


   [<a id="ref-7">7</a>] McCloghrie, K., Decker, E., Langville, P., and A.  Rijsinghani,
       "Definitions of Managed Objects for Source Routing Bridges", <a href="./rfc1525">RFC</a>
       <a href="./rfc1525">1525</a>, Hughes LAN Systems, cisco Systems, Inc., Digital Equipment
       Corporation, September 1993.

   [<a id="ref-8">8</a>] "Token Ring Access Method and Physical Layer Specifications",
       IEEE Standard 802.5-1989, 1989.

   [<a id="ref-9">9</a>] "Information technology - Local and metropolitan area networks -
       Part 5: Token ring access method and physical layer
       specifications", ISO/IEC 8802-5, 1992.

  [<a id="ref-10">10</a>] "Information technology - Telecommunications and information
       exchange between systems - Local area networks - Media access
       control (MAC) bridges", ISO/IEC 10038, 1993 [ANSI/IEEE Std
       802.1D, 1993 Edition].

  [<a id="ref-11">11</a>] "Source Routing Operation by End Systems", ISO/IEC 8802-2 PDAM5.3
       (6N7721).

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Security Considerations</span>

   Security issues are not discussed in this memo.




























<span class="grey">McCloghrie, Baker & Decker                                      [Page 9]</span>

<span id="page-10" ></span>
<span class="grey"><a href="./rfc1749">RFC 1749</a>      802.5 Station Source Routing MIB using SMIv2 December 1994</span>


<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>.  Authors' Addresses</span>

   Keith McCloghrie
   cisco Systems, Inc.
   170 West Tasman Drive,
   San Jose CA 95134-1706.

   Phone: (408) 526-5260
   EMail: [email protected]


   Fred Baker
   cisco Systems, Inc.
   519 Lado Drive
   Santa Barbara, CA 93111

   Phone: (805) 681-0115
   EMail: [email protected]


   Eric B. Decker
   cisco Systems, Inc.
   1525 O'Brien Dr.
   Menlo Park, California 94025

   Phone: (415) 688-8241
   EMail: [email protected]
























McCloghrie, Baker & Decker                                     [Page 10]