[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: 00 01 02 03 RFC 3020

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


                     Definitions of Managed Objects
                   for Monitoring and Controlling the
                 UNI/NNI Multilink Frame Relay Function

                           September 6, 2000


                     draft-ietf-frnetmib-mfrmib-03

                              Prayson Pate
                            Overture Networks
                    prayson.pate@overturenetworks.com

                               Bob Lynch
                          Larscom Incorporated
                           blynch@larscom.com

                            Kenneth Rehbehn
                         Megisto Systems, Inc.
                          krehbehn@megisto.com

Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC 2026.  Internet-Drafts are
   working documents of the Internet Engineering Task Force (IETF), its
   areas, and its working groups.  Note that other groups may also
   distribute working documents as Internet-Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as ``work in progress.''

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.












Expires March 2001                                              [Page 1]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


Abstract


   This memo defines a Management Information Base (MIB) for monitoring
   and controlling a UNI/NNI Multilink Frame Relay Function as defined
   in Frame Relay Forum FRF.16.  This MIB also include conformance and
   notification information.

Copyright Notice


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







































Expires March 2001                                              [Page 2]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   Table of Contents


   1 The SNMP Management Framework ................................    4
   2 Overview .....................................................    5
   2.1 Multilink Frame Relay Background ...........................    5
   2.1.1 Terminology ..............................................    5
   2.1.2 Reference Model ..........................................    6
   2.2 Structure of the MIB .......................................    7
   2.2.1 bundleMaxNumBundles ......................................    7
   2.2.2 bundleNextIndex ..........................................    7
   2.2.3 bundleTable ..............................................    7
   2.2.4 Bundle-to-ifIndex Mapping Table ..........................    7
   2.2.5 bundleLinkTable ..........................................    8
   2.3 Relationship With Other MIBS and Tables ....................    8
   2.3.1 Relationship With Interface Table ........................    8
   2.3.1.1 Bundle Links ...........................................    8
   2.3.1.2 Bundles ................................................    8
   2.3.1.3 Mapping Between ifIndex and bundleIndex ................    9
   2.3.1.4 ifTable Objects ........................................    9
   2.3.2 Relationship With Interface Stack Table ..................   10
   2.3.3 Relationship With Frame Relay DTE MIB ....................   10
   2.3.4 Relationship With Frame Relay Service MIB ................   10
   2.3.5 Example ..................................................   10
   2.4 Creation Of Bundles and Bundle Links .......................   12
   2.4.1 Creation Of Bundles ......................................   12
   2.4.2 Creation Of Bundle Links .................................   12
   2.5 Notifications ..............................................   12
   2.5.1 Bundle ...................................................   12
   2.5.1.1 linkUp .................................................   12
   2.5.1.2 linkDown ...............................................   13
   2.5.2 Bundle Link ..............................................   13
   2.5.2.1 linkUp .................................................   13
   2.5.2.2 linkDown ...............................................   13
   2.5.2.3 mfrMibTrapBundleLinkMismatch ...........................   13
   3 Object Definitions ...........................................   14
   4 Acknowledgments ..............................................   34
   5 References ...................................................   35
   6 Security Considerations ......................................   38
   7 Authors' Addresses ...........................................   39
   8 Full Copyright Section .......................................   39










Expires March 2001                                              [Page 3]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


1.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

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

    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 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
        1215 [RFC1215].  The second version, called SMIv2, is described
        in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580
        [RFC2580].

    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 [RFC1157]. A second version of the
        SNMP message protocol, which is not an Internet standards track
        protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
        and RFC 1906 [RFC1906]. The third version of the message
        protocol is called SNMPv3 and described in RFC 1906 [RFC1906],
        RFC 2572 [RFC2572] and RFC 2574 [RFC2574].

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

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

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [RFC2570].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in
   SMIv1 during the translation process. However, this loss of machine
   readable information is not considered to change the semantics of the


Expires March 2001                                              [Page 4]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   MIB.


2.  Overview

   This document defines a Management Information Base (MIB) for
   monitoring and controlling the UNI/NNI Multilink Frame Relay
   function.  The agreement on which this MIB is based was defined and
   documented by the Frame Relay Forum in the Frame Relay Forum Document
   FRF.16 [FRF.16].

2.1.  Multilink Frame Relay Background

   Multilink Frame Relay (MFR) for the User-to-Network Interface (UNI)
   and the Network-to-Network Interface (NNI) provides physical
   interface emulation for frame relay devices.  The emulated physical
   interface consists of one or more physical links, called "bundle
   links", aggregated together into a single "bundle" of bandwidth.
   This service provides a frame-based inverse multiplexing function,
   sometimes referred to as an "IMUX".

   The bundle provides the same order-preserving service as a physical
   layer for frames sent on a data link connection.  In addition, the
   bundle provides support for all Frame Relay services based on UNI and
   NNI standards.


2.1.1.  Terminology

Physical Link --    A single physical interface that interconnects two
                    devices in a frame relay network (e.g. DS1, DS0,
                    Bearer channel, refer to FRF.14).

Bundle --           A grouping of one or more physical links using the
                    formats and procedures of multilink frame relay.
                    The bundle operates as a logical interface function
                    that emulates a single physical interface to the
                    Q.922 data link layer.

Bundle Link --      A MFR sub-component that controls operation of one
                    of the bundle's physical links.










Expires March 2001                                              [Page 5]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


2.1.2.  Reference Model

  +--------------------------+                 +--------------------------+
  |   Switching Layer -OR-   |                 |   Switching Layer -OR-   |
  | Higher-Level Applications|                 | Higher-Level Applications|
  +--------------------------+                 +--------------------------+
  |          |C-Plane - Q.933|                 |          |C-Plane - Q.933|
  | U-Plane  |    (Note 1)   |                 | U-Plane  |    (Note 1)   |
  | (Note 3) |---------------|                 | (Note 3) |---------------|
  |          |Q.922 (Note 2) |                 |          |Q.922 (Note 2) |
  +--------------------------+                 +--------------------------+
  | Data Link Layer (Q.922)  |                 | Data Link Layer (Q.922)  |
  +--------------------------+                 +--------------------------+
  |       Bundle (B)         |                 |       Bundle (B)         |
  +--------------------------+                 +--------------------------+
  | Bundle | Bundle | Bundle |                 | Bundle | Bundle | Bundle |
  |  Link  |  Link  |  Link  |                 |  Link  |  Link  |  Link  |
  |  (BL)  |  (BL)  |  (BL)  |                 |  (BL)  |  (BL)  |  (BL)  |
  +--------+--------+--------+                 +--------+--------+--------+
  |Physical|Physical|Physical|                 |Physical|Physical|Physical|
  |  (PH)  |  (PH)  |  (PH)  |   ___________   |  (PH)  |  (PH)  |  (PH)  |
  +----+---+----+---+----+---+  /\          \  +----+---+----+---+----+---+
       |        |        |     /  \          \      |        |        |
       |        |        +---------\          \-----+        |        |
       |        |            /      \          \             |        |
       |        +--------------------\          \------------+        |
       |            _________\_______/  Bundle  /_                    |
       |           /\               /          /  \                   |
       +-------------| Bundle Link /          /    |------------------+
                   \/_____________/          /____/
                                \/__________/

                    Figure 1: MFR Reference Diagram


   Note 1: C-Plane operation as described in Q.933 [Q.933] and FRF.4
   [FRF.4]

   Note 2: Multiple frame acknowledged information fransfer mode as
   described in Q.922 [Q.922]

   Note 3: Core aspects for use with frame relay bearer service as
   described in Q.922, Annex A [Q.922]








Expires March 2001                                              [Page 6]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


2.2.  Structure of the MIB

   The UNI/NNI MFR managed objects consist of two scalar objects and
   three tables.

2.2.1.  bundleMaxNumBundles

   This scalar is used to inform the manager of the maximum number of
   bundles supported by this device.

2.2.2.  bundleNextIndex

   This scalar is used to assist the manager in selecting a value for
   bundleIndex during row creation.  It can also be used to avoid race
   conditions with multiple managers trying to create rows in the table
   (see RFC 2494 [RFC2494] for one such alogrithm).

2.2.3.  bundleTable

   This table provides a means to configure and monitor bundles.  It is
   indexed by bundleIndex and contains these columns:

       - bundleIndex                    Integer32
       - bundleIfIndex                  InterfaceIndex
       - bundleRowStatus                RowStatus
       - bundleNearEndName              SnmpAdminString
       - bundleFragmentation            INTEGER
       - bundleMaxFragSize              Integer32
       - bundleTimerHello               INTEGER
       - bundleTimerAck                 INTEGER
       - bundleCountMaxRetry            INTEGER
       - bundleActivationClass          INTEGER
       - bundleThreshold                Integer32
       - bundleMaxDiffDelay             Integer32
       - bundleSeqNumSize               INTEGER
       - bundleLinksConfigured          Integer32
       - bundleLinksActive              Integer32
       - bundleBandwidth                Integer32
       - bundleFarEndName               SnmpAdminString
       - bundleResequencingErrors       Counter32

2.2.4.  Bundle-to-ifIndex Mapping Table

   This table provides a means to take an ifIndex and find the
   corresponding bundleIndex.  It is indexed by ifIndex and contains
   these columns:

       - bundleIfIndexMapping                 Integer32



Expires March 2001                                              [Page 7]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


2.2.5.  bundleLinkTable

   This table provides a means to configure and monitor bundle links.
   It is indexed by ifIndex and contains these columns:

       - bundleLinkRowStatus            RowStatus
       - bundleLinkConfigBundleIndex    Integer32
       - bundleLinkNearEndName          SnmpAdminString
       - bundleLinkState                BundleLinkState
       - bundleLinkFarEndName           SnmpAdminString
       - bundleLinkFarEndBundleName     SnmpAdminString
       - bundleLinkDelay                Integer32
       - bundleLinkFramesControlTx      Counter32
       - bundleLinkFramesControlRx      Counter32
       - bundleLinkFramesControlInvalid Counter32
       - bundleLinkTimerExpiredCount    Counter32
       - bundleLinkLoopbackSuspected    Counter32
       - bundleLinkUnexpectedSequence   Counter32
       - bundleLinkMismatch             Counter32


2.3.  Relationship With Other MIBS and Tables

2.3.1.  Relationship With Interface Table

2.3.1.1.  Bundle Links

   Each bundle link will appear as an interface in the ifTable.  The
   ifIndex that appears in the ifTable is used for indexing the bundle
   link tables in the UNI-NNI MFR MIB.

2.3.1.2.  Bundles

   Each bundle will appear as an interface in the ifTable.  There will
   be corresponding bundleIndex which may be different than the ifIndex
   of the bundle.

   The reason is best summarized in RFC 2494 [RFC2494], which describes
   frame relay bundle of DS0.  It says:

        This table is not indexed by ifIndex because the manager has to
        choose the index in a createable row and the agent must be
        allowed to select ifIndex values.

   The rows in the ifEntry table are not creatable as they do not have
   row status.  RFC 2233 [RFC2233] suggests that the ifIndex should be
   chosen by the agent.  Here is its statement regarding row creation
   and deletion:



Expires March 2001                                              [Page 8]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


        While some interfaces, for example, most physical interfaces,
        cannot be created via network management, other interfaces such
        as logical interfaces sometimes can be.  The ifTable contains
        only generic information about an interface.  Almost all
        'create-able' interfaces have other, media-specific, information
        through which configuration parameters may be supplied prior to
        creating such an interface.  Thus, the ifTable does not itself
        support the creation or deletion of an interface (specifically,
        it has no RowStatus column).  Rather, if a particular interface
        type supports the dynamic creation and/or deletion of an
        interface of that type, then that media-specific MIB should
        include an appropriate RowStatus object (see the ATM LAN-
        Emulation Client MIB [ATMLANE] for an example of a MIB which
        does this).  Typically, when such a RowStatus object is
        created/deleted, then the conceptual row in the ifTable
        appears/disappears as a by-product, and an ifIndex value (chosen
        by the agent) is stored in an appropriate object in the media-
        specific MIB.

   The ATM LAN-Emulation Client MIB [ATMLANE] uses different indices and
   so does the IMA MIB [ATMIMA].  Looking at the examples we have, and
   the statements from RFC, it seems better to have two indices.  This
   gives the SNMP agent implementor the freedom to manage their ifIndex
   in the way they like.

2.3.1.3.  Mapping Between ifIndex and bundleIndex

   The bundleIfIndexMappingTable is indexed by ifIndex and provides the
   means to map a given ifIndex into the corresponding bundleIndex.  The
   bundleIfIndexMapping object in the bundleTable (indexed by
   bundleIndex) provides the reverse mapping of a bundleIndex to the
   corresponding ifIndex in the ifTable.

2.3.1.4.  ifTable Objects

   The bundle configuration and status table. There is a one-to-one
   correspondence between a bundle and an interface represented in the
   ifTable.

   The following objects of the ifTable have specific meaning for an MFR
   bundle:

       ifAdminStatus  - the bundle admin status
       ifOperStatus   - the bundle operational status
       ifSpeed        - the current bandwidth of the bundle
       ifInUcastPkts  - the number of frames received on the bundle
       ifOutUcastPkts - the number of frames transmitted on the bundle
       ifInErrors     - frame (not fragment) errors
       ifOutErrors    - frame (not fragment) errors


Expires March 2001                                              [Page 9]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   The following objects of the ifTable have specific meaning for an MFR
   bundle link:

       ifAdminStatus  - the bundle link admin status
       ifOperStatus   - the bundle link operational status
       ifSpeed        - the bandwidth of the bundle link interface
       ifInUcastPkts  - the number of frames received on the bundle link
       ifOutUcastPkts - the number of frames transmitted on the bundle link
       ifInErrors     - frame and fragment errors
       ifOutErrors    - frame and fragment errors


2.3.2.  Relationship With Interface Stack Table

   The bundles and bundle links will appear in the ifStackTable defined
   in RFC 2233 [RFC2233].  Each bundle link will appear a lower layer to
   its owner bundle.  The bundle will appear as a higher layer to the
   bundle links and as a lower layer to a frame relay service or UNI.

2.3.3.  Relationship With Frame Relay DTE MIB

   The bundle will have a one-to-one correspondence with a DLCMI or UNI
   that appear in the DTE MIB tables [RFC2115].

2.3.4.  Relationship With Frame Relay Service MIB

   There is a one-to-one relationship between the MFR bundle and the
   frame relay service logical port defined in RFC1604 [RFC1604].

2.3.5.  Example

   Figure two shows an example of how the various tables are related.
   This example shows two bundles composed of 2 T1s each.  The bundles
   have a bundleIndex of 10 and 20 respectively.

              +-------------------------+
              |   Frame Relay Service   |
              +-----+-------------+-----+
                    |             |
              +-----+------+------+-----+
              | MFR Bundle | MFR Bundle |
              |    10      |     20     |
              +--+-----+---+---+-----+--+
                 |     |       |     |
               +-+-+ +-+-+   +-+-+ +-+-+
               |T1 | |T1 |   |T1 | |T1 |
               +---+ +---+   +-+-+ +---+

           Figure 2: Frame Relay Service Being Carried on 4 T1s


Expires March 2001                                             [Page 10]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   The assignment of the ifTable index values could for example be:

              ifIndex |  Description               | ifType
              --------+----------------------------+----------------------
                 1    |  FrameRelayService         | frameRelayService(44)
                 2    |  MFR Bundle #10            | frf16MfrBundle(163)
                 3    |  MFR Bundle #20            | frf16MfrBundle(163)
                 4    |  ds1 #1/MFR Bundle Link #1 | ds1(18)
                 5    |  ds1 #2/MFR Bundle Link #2 | ds1(18)
                 6    |  ds1 #3/MFR Bundle Link #3 | ds1(18)
                 7    |  ds1 #4/MFR Bundle Link #4 | ds1(18)

   The ifStackTable is then used to show the relationships between the
   various interfaces.

              HigherLayer | LowerLayer
              ------------+-----------
                  0       |     1
                  1       |     2
                  1       |     3
                  2       |     4
                  2       |     5
                  3       |     6
                  3       |     7
                  4       |     0
                  5       |     0
                  6       |     0
                  7       |     0


   The bundleIfIndexMappingTable shows the relationship between the
   ifTable ifIndex and the bundleIndex:

              ifIndex | bundleIfIndexMappingIndex
              --------+--------------------------
                 2    |            10
                 3    |            20


   The bundleTable shows the relationship between the bundleIndex and
   the ifIndex:

              bundleIndex | bundleIfIndex
             -------------+--------------
                   10     |      2
                   20     |      3





Expires March 2001                                             [Page 11]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   The bundleLinkTable shows the relationship between the bundles and
   bundle links:

              bundleIndex | bundleLinkIfIndex
              ------------+------------------
                  10      |        4
                  10      |        5
                  20      |        6
                  20      |        7


2.4.  Creation Of Bundles and Bundle Links

2.4.1.  Creation Of Bundles

   A new bundle is created by setting a createAndGo(4) value in the
   bundleRowStatus RowStatus object.  Optionally, an agent could also
   support setting a value of createAndWait(5) followed by a set to the
   value active(1).

   When a bundle is created, the agent must create a new interface in
   the ifTable.  The ifIndex for this new interface is used for the
   value of bundleIfIndex.

2.4.2.  Creation Of Bundle Links

   A new bundle link is created by setting a createAndGo(4) value in the
   bundleLinkRowStatus RowStatus object.

   The bundle link is associated with a specific physical interface and
   uses the ifIndex of the physical interface. The bundleLinkEntry row
   objects may be created after or during creation of the physical
   interface's ifEntry row objects.

   The bundle identified in the object bundleIndex must exist at time of
   bundle link creation.

2.5.  Notifications

   The linkUp and linkDown traps are defined in RFC 1573 [RFC1573].

2.5.1.  Bundle

   The following SNMP traps are defined for MFR bundles.

2.5.1.1.  linkUp

   This trap is sent when the ifOperStatus of a bundle transitions from
   down to up.  This occurs when a sufficient number of links


Expires March 2001                                             [Page 12]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   (determined by bundleActivationClass and bundleThreshold) are in the
   operationally up state.

2.5.1.2.  linkDown

   This trap is sent when the ifOperStatus of a bundle transitions from
   up to down.  This occurs when a insufficient number of links
   (determined by bundleActivationClass and bundleThreshold) are in the
   operationally up state.

2.5.2.  Bundle Link

   The following SNMP traps are defined for MFR bundle links.

2.5.2.1.  linkUp

   This trap is sent when a bundleLinkState object transitions to the
   value bundleLinkStateUp.

2.5.2.2.  linkDown

   This trap is sent when a bundleLinkState object transitions from the
   value bundleLinkStateUp.

2.5.2.3.  mfrMibTrapBundleLinkMismatch

   This trap indicates that a bundle link mismatch has been detected.
   The following objects are reported:

      - bundleNearEndName:          configured name of near end bundle
      - bundleFarEndName:           previously reported name of far
                                    end bundle
      - bundleLinkNearEndName:      configured name of near end bundle
      - bundleLinkFarEndName:       reported name of far end bundle
      - bundleLinkFarEndBundleName: currently reported name of far
                                    end bundle

   Note that the configured items may have been configured
   automatically.  Note also that the bundleLinkMismatch counter is
   incremented when the trap is sent.











Expires March 2001                                             [Page 13]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


3.  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.

 FRF16-MFR-MIB-EXP DEFINITIONS ::= BEGIN

    IMPORTS
       MODULE-IDENTITY, OBJECT-TYPE, Integer32, Counter32,
          NOTIFICATION-TYPE, experimental
          FROM SNMPv2-SMI
       TEXTUAL-CONVENTION, TestAndIncr, RowStatus
          FROM SNMPv2-TC
       MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
          FROM SNMPv2-CONF
       SnmpAdminString
          FROM SNMP-FRAMEWORK-MIB
       InterfaceIndex, ifIndex
          FROM IF-MIB;

    mfrMib MODULE-IDENTITY
       LAST-UPDATED "0009050000Z"
       ORGANIZATION "IETF Frame Relay Service MIB (frnetmib) Working Group"
       CONTACT-INFO
         "WG Charter:    http://www.ietf.org/html.charters/frnetmib-charter.html
          WG-email:      frnetmib@sunroof.eng.sun.com
          Subscribe:     frnetmib-request@sunroof.eng.sun.com
          Email Archive: ftp://ftp.ietf.org/ietf-mail-archive/frnetmib

          Chair:      Andy Malis
                      Lucent Technologies
          Email:      Andy.Malis@vivacenetworks.com

          WG editor:  Prayson Pate
                      Overture Networks
          Email:      prayson.pate@overturenetworks.com

          Co-author:  Bob Lynch
                      Larscom Incorporated
          EMail:      blynch@larscom.com

          Co-author:  Kenneth Rehbehn


Expires March 2001                                             [Page 14]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


                      Megisto Systems, Inc.
          EMail:      krehbehn@megisto.com"

       DESCRIPTION
          "This is the MIB used to control and monitor the multilink frame
           relay (MFR) function described in FRF.16.   This was originally
           submitted to the Frame Relay Forum as contribution FRFTC 99-151
           and then updated as FRFTC 99-193."

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Revision History
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

       REVISION "0009050000Z"
       DESCRIPTION
           "Initial version of the FRF.16 UNI/NNI Multilink
            Frame Relay MIB.  Published as RFC [RFC-EDITOR: Enter RFC # here]."

       REVISION "0009050000Z"
       DESCRIPTION
           "[RFC-EDITOR:  Remove this and all following REVISION
           statements prior to publication as an RFC]

           Changes after review by Dan Romascanu.
           "

       REVISION "0004040000Z"
       DESCRIPTION
           "Changes from draft-ietf-frnetmib-mfrmib-01.txt from IETF-47:
            o  Fixed display of sample ifStackTable
            o  Changed bundleIfIndexMappingIndex from InterfaceIndex
               to Integer32
           "


       REVISION "0003090000Z"
       DESCRIPTION
           "Changes from draft-ietf-frnetmib-mfrmib-00.txt
            o  changed experimental number to IANA-approved 105.
            o  changed interface type for frf16MfrBundle to IANA-approved 163.
           "

       REVISION "9912061700Z"
       DESCRIPTION
           "Updates:
            o  changed name to draft-ietf-frnetmib-mfrmib-00
            o  updated text to match last MIB revisions


Expires March 2001                                             [Page 15]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


            o  corrected description of bundleIfIndexMappingTable
            o  added objects to show configured and current bundle links.
           "

       REVISION "9910212020Z"
       DESCRIPTION
           "Updated after comments from Michael Allen and Ken Rehben.
            o  corrected options for sequence number length
            o  changed frf16Mfr prefix to mfr
            o  created a sub-group for scalars
            o  created an entry in the bundleTable for maximum links per bundle
            o  changed indices to not-accessible
            o  changed DisplayString to SnmpAdminString
            o  updated some of the object descriptions
            o  added a -EXP to the name of the MIB
            o  added some DEFVAL and REFERENCE clauses"

       REVISION "9910151300Z"
       DESCRIPTION
           "Updated after review at the October meeting in Huntsville:
            o  removed log table
            o  removed several columns from each table
            o  combined configuration, status and error tables into
               one table each for bundles and bundle links
            o  added new objects for
               - maximum number of bundles
               - maximum fragment size
               - size of sequence number
            o  added notifications
            o  added conformance information"

       REVISION "9910011440Z"
       DESCRIPTION
           "The initial version of this MIB was originally submitted
            to the Frame Relay Forum October 1999 meeting in Huntsville
            as FRFTC/99-151."

       ::= { experimental 105 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Textual Conventions
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    BundleLinkState ::= TEXTUAL-CONVENTION
       STATUS      current
       DESCRIPTION
          "The possible states for a bundle link, as defined in


Expires March 2001                                             [Page 16]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


           Annex A of FRF.16."
       REFERENCE "FRF.16 Annex A"
       SYNTAX  INTEGER {
          bundleLinkStateAddSent       (1),
          bundleLinkStateAddRx         (2),
          bundleLinkStateAddAckRx      (3),
          bundleLinkStateUp            (4),
          bundleLinkStateIdlePending   (5),
          bundleLinkStateIdle          (6),
          bundleLinkStateDown          (7),
          bundleLinkStateDownIdle      (8)
          }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Object Identifers
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    mfrMibObjects           OBJECT IDENTIFIER ::= { mfrMib 1 }
    mfrMibTraps             OBJECT IDENTIFIER ::= { mfrMib 2 }
    mfrMibConformance       OBJECT IDENTIFIER ::= { mfrMib 3 }

    mfrMibScalarObjects     OBJECT IDENTIFIER ::= { mfrMibObjects 1 }
    mfrMibBundleObjects     OBJECT IDENTIFIER ::= { mfrMibObjects 2 }
    mfrMibBundleLinkObjects OBJECT IDENTIFIER ::= { mfrMibObjects 3 }

    mfrMibTrapsPrefix       OBJECT IDENTIFIER ::= { mfrMibTraps 0 }

    mfrMibGroups            OBJECT IDENTIFIER ::= { mfrMibConformance 1 }
    mfrMibCompliances       OBJECT IDENTIFIER ::= { mfrMibConformance 2 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Scalars
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    bundleMaxNumBundles OBJECT-TYPE
       SYNTAX  Integer32
       MAX-ACCESS read-only
       STATUS  current
       DESCRIPTION
          "This object is used to inform the manager of the
           maximum number of bundles supported by this device."
       ::= { mfrMibScalarObjects 1 }

    bundleNextIndex OBJECT-TYPE
       SYNTAX  TestAndIncr


Expires March 2001                                             [Page 17]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


       MAX-ACCESS read-write
       STATUS  current
       DESCRIPTION
          "This object is used to assist the manager in
           selecting a value for bundleIndex during row creation
           in the bundleTable. It can also be used to avoid race
           conditions with multiple managers trying to create
           rows in the table (see RFC 2494 [RFC2494] for one such
           alogrithm)."
       REFERENCE "RFC 2494"
       ::= { mfrMibScalarObjects 2 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Bundle Table
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    bundleTable OBJECT-TYPE
       SYNTAX  SEQUENCE OF BundleEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "The bundle configuration and status table.  There
           is a one-to-one correspondence between a bundle
           and an interface represented in the ifTable.

           The following objects of the ifTable have specific
           meaning for an MFR bundle:
              ifAdminStatus  - the bundle admin status
              ifOperStatus   - the bundle operational status
              ifSpeed        - the current bandwidth of the bundle
              ifInUcastPkts  - the number of frames received
                               on the bundle
              ifOutUcastPkts - the number of frames transmitted
                               on the bundle
              ifInErrors     - frame (not fragment) errors
              ifOutErrors    - frame (not fragment) errors
              "
       ::= { mfrMibBundleObjects 3 }

    bundleEntry OBJECT-TYPE
       SYNTAX  BundleEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "An entry in the bundle table."
       INDEX   { bundleIndex }
       ::= { bundleTable 1 }


Expires March 2001                                             [Page 18]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


    BundleEntry ::=
       SEQUENCE {
          bundleIndex
             Integer32,
          bundleIfIndex
             InterfaceIndex,
          bundleRowStatus
             RowStatus,
          bundleNearEndName
             SnmpAdminString,
          bundleFragmentation
             INTEGER,
          bundleMaxFragSize
             Integer32,
          bundleTimerHello
             INTEGER,
          bundleTimerAck
             INTEGER,
          bundleCountMaxRetry
             INTEGER,
          bundleActivationClass
             INTEGER,
          bundleThreshold
             Integer32,
          bundleMaxDiffDelay
             Integer32,
          bundleSeqNumSize
             INTEGER,
          bundleMaxBundleLinks
             Integer32,
          bundleLinksConfigured
             Integer32,
          bundleLinksActive
             Integer32,
          bundleBandwidth
             Integer32,
          bundleFarEndName
             SnmpAdminString,
          bundleResequencingErrors
             Counter32
          }

    bundleIndex OBJECT-TYPE
       SYNTAX  Integer32 (1..2147483647)
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "The index into the table.  While this corresponds
           to an entry in the ifTable, the value of bundleIndex


Expires March 2001                                             [Page 19]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


           need not match that of the ifIndex in the ifTable.
           A manager can use bundleNextIndex to select a unique
           bundleIndex for creating a new row."
       ::= { bundleEntry 1 }

    bundleIfIndex OBJECT-TYPE
       SYNTAX  InterfaceIndex
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The value must match an entry in the interface
           table whose ifType must be set to frf16MfrBundle(163).

           For example: if the value of bundleIfIndex is 10,
           then a corresponding entry should be present in
           the ifTable with an index of 10 and an ifType of 163."
       ::= { bundleEntry 2 }

    bundleRowStatus OBJECT-TYPE
       SYNTAX  RowStatus
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
           "The bundleRowStatus object allows create, change,
            and delete operations on bundle entries."
       REFERENCE "RFC 1903"
       ::= { bundleEntry 3 }

    bundleNearEndName OBJECT-TYPE
       SYNTAX  SnmpAdminString
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The configured name of the bundle."
       REFERENCE "FRF.16 section 3.4.1"
       ::= { bundleEntry 4 }

    bundleFragmentation OBJECT-TYPE
       SYNTAX  INTEGER {
          enable  (1),
          disable (2)
          }
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "Controls whether the bundle performs/accepts
           fragmentation and re-assembly.  The possible
           values are:



Expires March 2001                                             [Page 20]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


           enable(1) - Bundle links will fragment frames

           disable(2) - Bundle links will not fragment
                       frames."
       DEFVAL { disable }
       ::= { bundleEntry 5 }

    bundleMaxFragSize OBJECT-TYPE
       SYNTAX  Integer32 (-1..8184)
       UNITS "Octets"
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The maximum fragment size supported.  Note that this
           is only valid if bundleFragmentation is set to enable(1).

           Zero is not a valid fragment size.

           A bundle that does not support fragmentation must be
           set to -1."
       DEFVAL { -1 }
       ::= { bundleEntry 6 }

    bundleTimerHello OBJECT-TYPE
       SYNTAX  INTEGER (1..180)
       UNITS "Seconds"
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The configured MFR Hello Timer value."
       REFERENCE "FRF.16 section 4.3.8.1"
       DEFVAL { 10 }
       ::= { bundleEntry 7 }

    bundleTimerAck OBJECT-TYPE
       SYNTAX  INTEGER (1..10)
       UNITS "Seconds"
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The configured MFR T_ACK value."
       REFERENCE "FRF.16 section 4.3.8.2"
       DEFVAL { 4 }
       ::= { bundleEntry 8 }

    bundleCountMaxRetry OBJECT-TYPE
       SYNTAX  INTEGER (1..5)
       MAX-ACCESS  read-create
       STATUS  current


Expires March 2001                                             [Page 21]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


       DESCRIPTION
          "The MFR N_MAX_RETRY value."
       REFERENCE "FRF.16 section 4.3.8.3"
       DEFVAL { 2 }
       ::= { bundleEntry 9 }

    bundleActivationClass OBJECT-TYPE
       SYNTAX  INTEGER {
          bundleActivationClassA (1),
          bundleActivationClassB (2),
          bundleActivationClassC (3),
          bundleActivationClassD (4)
          }
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "Controls the conditions under which the bundle is activated.
           The following settings are available:

              bundleActivationClassA(1) - at least one must link up
              bundleActivationClassB(2) - all links must be up
              bundleActivationClassC(3) - a certain number must be up.
                                          Refer to bundleThreshold for
                                          the required number.
              bundleActivationClassD(4) - custom (implementation
                                          specific)."
       REFERENCE "FRF.16 section 4.2.2.1"
       DEFVAL { bundleActivationClassA }
       ::= { bundleEntry 10 }

    bundleThreshold OBJECT-TYPE
       SYNTAX  Integer32
       UNITS "Bundle Links"
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "Specifies the number of links that must be in operational
           'up' state before the bundle will transition to an
           operational up/active state.  If the number of
           operational 'up' links falls below this value,
           then the bundle will transition to an inactive
           state.

           Note - this is only valid when bundleActivationClass
           is set to bundleActivationClassC or, depending upon the
           implementation, to bundleActivationClassD."
       REFERENCE "FRF.16 section 4.2.2.1"
       DEFVAL { -1 }
       ::= { bundleEntry 11 }


Expires March 2001                                             [Page 22]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


    bundleMaxDiffDelay OBJECT-TYPE
       SYNTAX  Integer32
       UNITS "Milliseconds"
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The maximum delay difference between the bundle
           links."
       DEFVAL { -1 }
       ::= { bundleEntry 12 }

    bundleSeqNumSize OBJECT-TYPE
       SYNTAX  INTEGER {
           seqNumSize12bit (1),
           seqNumSize24bit (2)
           }
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "Controls whether the standard FRF.12 12-bit
           sequence number is used or the optional 24-bit
           sequence number."
       REFERENCE "FRFTC/99-194"
       DEFVAL { seqNumSize12bit }
       ::= { bundleEntry 13 }

    bundleMaxBundleLinks OBJECT-TYPE
       SYNTAX  Integer32
       UNITS "Bundle Links"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The maximum number of bundle links supported for this bundle."
       ::= { bundleEntry 14 }

    bundleLinksConfigured OBJECT-TYPE
        SYNTAX  Integer32
        UNITS "Bundle Links"
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
           "The number of links configured for the bundle."
        ::= {  bundleEntry 15 }

    bundleLinksActive OBJECT-TYPE
        SYNTAX  Integer32
        UNITS "Bundle Links"
        MAX-ACCESS  read-only
        STATUS  current


Expires March 2001                                             [Page 23]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


        DESCRIPTION
           "The number of links that are active."
        ::= {  bundleEntry 16 }

    bundleBandwidth OBJECT-TYPE
        SYNTAX  Integer32
        UNITS "Bits/Sec"
        MAX-ACCESS  read-only
        STATUS  current
        DESCRIPTION
           "The amount of available bandwidth on the bundle"
        ::= {  bundleEntry 17 }

    bundleFarEndName OBJECT-TYPE
       SYNTAX  SnmpAdminString
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Name of the bundle received from the far end."
       REFERENCE "FRF.16 section 3.4.1"
       ::= { bundleEntry 18 }

    bundleResequencingErrors OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Error Events"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "A count of the number of resequncing errors. Each event
           may correspond to multiple lost frames.  Example:
           Say sequence number 56, 59 and 60 is received for DLCI 100.
           It is decided by some means that sequence 57 and 58 is lost.
           This counter should then be incremented by ONE, even though
           two frames were lost."
       ::= { bundleEntry 19 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- ifIndex Mapping to Bundle Index Table
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    bundleIfIndexMappingTable OBJECT-TYPE
       SYNTAX  SEQUENCE OF BundleIfIndexMappingEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
           "A table mapping the values of ifIndex to the
            bundleIndex. This is required in order to find


Expires March 2001                                             [Page 24]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


            the bundleIndex given an ifIndex.  The mapping of
            bundleIndex to ifIndex is provided by the bundleIfIndex
            entry in the bundleTable."
       ::= { mfrMibBundleObjects 4 }

    bundleIfIndexMappingEntry OBJECT-TYPE
       SYNTAX  BundleIfIndexMappingEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
            "Each row describes one ifIndex to bundleIndex mapping."
     INDEX   { ifIndex }
     ::= { bundleIfIndexMappingTable 1 }

    BundleIfIndexMappingEntry ::=
       SEQUENCE {
         bundleIfIndexMappingIndex
            Integer32
         }

    bundleIfIndexMappingIndex OBJECT-TYPE
       SYNTAX  Integer32
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
            "The bundleIndex of the given ifIndex."
     ::= { bundleIfIndexMappingEntry 2 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Bundle Link Table
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    bundleLinkTable OBJECT-TYPE
       SYNTAX  SEQUENCE OF BundleLinkEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "The bundle link configuration and status table.  There
           is a one-to-one correspondence between a bundle link
           and a physical interface represented in the ifTable.  The
           ifIndex of the physical interface is used to index the
           bundle link table, and to create rows.

           The following objects of the ifTable have specific
           meaning for an MFR bundle link:

              ifAdminStatus  - the bundle link admin status


Expires March 2001                                             [Page 25]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


              ifOperStatus   - the bundle link operational
                               status
              ifSpeed        - the bandwidth of the bundle
                               link interface
              ifInUcastPkts  - the number of frames received
                               on the bundle link
              ifOutUcastPkts - the number of frames transmitted
                               on the bundle link
              ifInErrors     - frame and fragment errors
              ifOutErrors    - frame and fragment errors"
       ::= { mfrMibBundleLinkObjects 1 }

    bundleLinkEntry OBJECT-TYPE
       SYNTAX  BundleLinkEntry
       MAX-ACCESS  not-accessible
       STATUS  current
       DESCRIPTION
          "An entry in the bundle link table."
       INDEX   { ifIndex }
       ::= { bundleLinkTable 1 }

    BundleLinkEntry ::=
       SEQUENCE {
          bundleLinkRowStatus
             RowStatus,
          bundleLinkConfigBundleIndex
             Integer32,
          bundleLinkNearEndName
             SnmpAdminString,
          bundleLinkState
             BundleLinkState,
          bundleLinkFarEndName
             SnmpAdminString,
          bundleLinkFarEndBundleName
             SnmpAdminString,
          bundleLinkDelay
             Integer32,
          bundleLinkFramesControlTx
             Counter32,
          bundleLinkFramesControlRx
             Counter32,
          bundleLinkFramesControlInvalid
             Counter32,
          bundleLinkTimerExpiredCount
             Counter32,
          bundleLinkLoopbackSuspected
             Counter32,
          bundleLinkUnexpectedSequence
             Counter32,


Expires March 2001                                             [Page 26]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


          bundleLinkMismatch
             Counter32
          }

    bundleLinkRowStatus OBJECT-TYPE
       SYNTAX  RowStatus
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The bundleLinkRowStatus object allows create, change,
           and delete operations on bundleLink entries.

           The create operation must fail if no physical interface
           is associated with the bundle link."
       ::= { bundleLinkEntry 1 }

    bundleLinkConfigBundleIndex OBJECT-TYPE
       SYNTAX  Integer32
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The bundleLinkConfigBundleIndex object allows
           the manager to control the bundle to which the bundle
           link is assigned. If no value were in this field, then
           the bundle would remain in NOT_READY rowStatus and be
           unable to go to active.  With an appropriate bundleIndex
           in this field, then we could put the bundleLink row in
           NOT_IN_SERVICE or ACTIVE rowStatus."
       ::= { bundleLinkEntry 2 }

    bundleLinkNearEndName OBJECT-TYPE
       SYNTAX  SnmpAdminString
       MAX-ACCESS  read-create
       STATUS  current
       DESCRIPTION
          "The configured bundle link name that is sent to the far end."
       ::= { bundleLinkEntry 3 }

    bundleLinkState OBJECT-TYPE
       SYNTAX  BundleLinkState
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Current bundle link state as defined by the MFR protocol
           described in Annex A of FRF.16."
       REFERENCE "FRF.16 Annex A"
       ::= { bundleLinkEntry 4 }

    bundleLinkFarEndName OBJECT-TYPE


Expires March 2001                                             [Page 27]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


       SYNTAX  SnmpAdminString
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Name of bundle link received from far end."
       REFERENCE "FRF.16 section 3.4.2"
       ::= { bundleLinkEntry 5 }

    bundleLinkFarEndBundleName OBJECT-TYPE
       SYNTAX  SnmpAdminString
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Name of far end bundle for this link received from far end."
       REFERENCE "FRF.16 section 3.4.1"
       ::= { bundleLinkEntry 6 }

    bundleLinkDelay OBJECT-TYPE
       SYNTAX  Integer32
       UNITS "Milliseconds"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Current round-trip delay for this bundle link.  The value -1
           is returned when an implementation does not support measurement
           of the bundle link delay."
       REFERENCE "FRF.16 section 3.4.4"
       ::= { bundleLinkEntry 7 }

    bundleLinkFramesControlTx OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Frames"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Number of MFR control frames sent."
       REFERENCE "FRF.16 section 3.2"
       ::= { bundleLinkEntry 8 }

    bundleLinkFramesControlRx OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Frames"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Number of valid MFR control frames received."
       REFERENCE "FRF.16 section 3.2"
       ::= { bundleLinkEntry 9 }



Expires March 2001                                             [Page 28]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


    bundleLinkFramesControlInvalid OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Frames"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The number of invalid MFR control frames received."
       REFERENCE "FRF.16 section 3.2"
       ::= { bundleLinkEntry 10 }

    bundleLinkTimerExpiredCount OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Timer Expiration Events"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "Number of times the T_HELLO or T_ACK timers expired."
       REFERENCE "FRF.16 section 4.3.8.1 and 4.3.8.2"
       ::= { bundleLinkEntry 11 }

    bundleLinkLoopbackSuspected OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Loopback Suspected Events"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The number of times a loopback has been suspected
           (based upon the use of magic numbers)."
       REFERENCE "FRF.16 section 4.3.7"
       ::= { bundleLinkEntry 12 }

    bundleLinkUnexpectedSequence OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Frames"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The number of data MFR frames discarded because the sequence
           number of the frame for a DLCI was less than (delayed frame)
           or equal to (duplicate frame) the one expected for that DLCI.

           Example:
           Say frames with sequence numbers 56, 58, 59 is received for
           DLCI 100. While waiting for sequence number 57 another frame
           with sequence number 58 arrives. Frame 58 is discarded and
           the counter is incremented."
       REFERENCE "FRF.16 section 4.2.3.2"
       ::= { bundleLinkEntry 13 }



Expires March 2001                                             [Page 29]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


    bundleLinkMismatch OBJECT-TYPE
       SYNTAX  Counter32
       UNITS "Bundle Name Mismatch Events"
       MAX-ACCESS  read-only
       STATUS  current
       DESCRIPTION
          "The number of times that the unit has been notified by the
           remote peer that the bundle name is inconsistent with other
           bundle links attached to the far-end bundle."
       REFERENCE "FRF.16 section 4.3.2.4"
       ::= { bundleLinkEntry 14 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Notifications/Traps
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    mfrMibTrapBundleLinkMismatch NOTIFICATION-TYPE
       OBJECTS {
          bundleNearEndName,
          bundleFarEndName,
          bundleLinkNearEndName,
          bundleLinkFarEndName,
          bundleLinkFarEndBundleName
          }
       STATUS  current
       DESCRIPTION
          "This trap indicates that a bundle link mismatch has
           been detected.  The following objects are reported:

           bundleNearEndName:    configured name of near end bundle

           bundleFarEndName:     previously reported name of
                                 far end bundle

           bundleLinkNearEndName: configured name of near end bundle

           bundleLinkFarEndName: reported name of far end bundle

           bundleLinkFarEndBundleName: currently reported name of
                                 far end bundle

           Note: that the configured items may have been configured
                 automatically.

           Note: The bundleLinkMismatch counter is incremented when
                 the trap is sent."
       REFERENCE "FRF.16 section 4.3.2.4"


Expires March 2001                                             [Page 30]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


        ::= { mfrMibTrapsPrefix 1 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Conformance/Compliance
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    mfrMibCompliance MODULE-COMPLIANCE
       STATUS      current
       DESCRIPTION
          "The compliance statement for equipment that implements
           the FRF16 MIB.  All of the current groups are mandatory,
           but a number of objects may be read-only if the
           implementation does not allow configuration."
       MODULE -- this module
       MANDATORY-GROUPS {
          mfrMibBundleGroup,
          mfrMibBundleLinkGroup,
          mfrMibTrapGroup
          }

       OBJECT     bundleFragmentation
       MIN-ACCESS read-only
       DESCRIPTION
           "Write access is not required, but the value used must be reported."

       OBJECT     bundleMaxFragSize
       MIN-ACCESS read-only
       DESCRIPTION
           "Write access is not required, but the value used must be reported.
            A value of -1 indicates that the value is not applicable."

       OBJECT     bundleThreshold
       MIN-ACCESS read-only
       DESCRIPTION
           "Write access is not required, but the value used must be reported.
            A value of -1 indicates that the value is not applicable."

       OBJECT     bundleMaxDiffDelay
       MIN-ACCESS read-only
       DESCRIPTION
           "Write access is not required, but the value used must be reported."

       OBJECT     bundleSeqNumSize
       MIN-ACCESS read-only
       DESCRIPTION
           "Write access is not required, but the value used must be reported.
            A value of -1 indicates that the value is not applicable."


Expires March 2001                                             [Page 31]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


       ::= { mfrMibCompliances 1 }

    -- ---------------------------------------------------------
    -- ---------------------------------------------------------
    -- Units of Conformance
    -- ---------------------------------------------------------
    -- ---------------------------------------------------------

    mfrMibBundleGroup OBJECT-GROUP
       OBJECTS {
          bundleMaxNumBundles,
          bundleNextIndex,
          bundleIfIndex,
          bundleRowStatus,
          bundleNearEndName,
          bundleFragmentation,
          bundleMaxFragSize,
          bundleTimerHello,
          bundleTimerAck,
          bundleCountMaxRetry,
          bundleActivationClass,
          bundleThreshold,
          bundleMaxDiffDelay,
          bundleMaxBundleLinks,
          bundleLinksConfigured,
          bundleLinksActive,
          bundleBandwidth,
          bundleSeqNumSize,
          bundleFarEndName,
          bundleResequencingErrors,
          bundleIfIndexMappingIndex
          }
       STATUS current
       DESCRIPTION
           "Group of objects describing bundles."
       ::= { mfrMibGroups 1 }

    mfrMibBundleLinkGroup   OBJECT-GROUP
       OBJECTS {
          bundleLinkRowStatus,
          bundleLinkConfigBundleIndex,
          bundleLinkNearEndName,
          bundleLinkState,
          bundleLinkFarEndName,
          bundleLinkFarEndBundleName,
          bundleLinkDelay,
          bundleLinkFramesControlTx,
          bundleLinkFramesControlRx,
          bundleLinkFramesControlInvalid,


Expires March 2001                                             [Page 32]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


          bundleLinkTimerExpiredCount,
          bundleLinkLoopbackSuspected,
          bundleLinkUnexpectedSequence,
          bundleLinkMismatch
          }
       STATUS current
       DESCRIPTION
           "Group of objects describing bundle links."
       ::= { mfrMibGroups 2 }

    mfrMibTrapGroup NOTIFICATION-GROUP
       NOTIFICATIONS {
          mfrMibTrapBundleLinkMismatch
          }
       STATUS current
       DESCRIPTION
           "Group of objects describing notifications (traps)."
       ::= { mfrMibGroups 3 }

 END































Expires March 2001                                             [Page 33]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


4.  Acknowledgments

   This document was produced by the Frame Relay MFR MIB Working Group.
















































Expires March 2001                                             [Page 34]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


5.  References

[RFC2571]   Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
            for Describing SNMP Management Frameworks", RFC 2571, April
            1999

[RFC1155]   Rose, M., and K. McCloghrie, "Structure and Identification
            of Management Information for TCP/IP-based Internets", STD
            16, RFC 1155, May 1990

[RFC1212]   Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
            16, RFC 1212, March 1991

[RFC1215]   M. Rose, "A Convention for Defining Traps for use with the
            SNMP", RFC 1215, March 1991

[RFC2578]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Structure of Management
            Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999

[RFC2579]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Textual Conventions for
            SMIv2", STD 58, RFC 2579, April 1999

[RFC2580]   McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
            Rose, M., and S. Waldbusser, "Conformance Statements for
            SMIv2", STD 58, RFC 2580, April 1999

[RFC1157]   Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
            Network Management Protocol", STD 15, RFC 1157, May 1990.

[RFC1901]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Introduction to Community-based SNMPv2", RFC 1901, January
            1996.

[RFC1906]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Transport Mappings for Version 2 of the Simple Network
            Management Protocol (SNMPv2)", RFC 1906, January 1996.

[RFC2572]   Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
            Processing and Dispatching for the Simple Network Management
            Protocol (SNMP)", RFC 2572, April 1999

[RFC2574]   Blumenthal, U., and B. Wijnen, "User-based Security Model
            (USM) for version 3 of the Simple Network Management
            Protocol (SNMPv3)", RFC 2574, April 1999

[RFC1905]   Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
            "Protocol Operations for Version 2 of the Simple Network


Expires March 2001                                             [Page 35]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


            Management Protocol (SNMPv2)", RFC 1905, January 1996.

[RFC2573]   Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
            RFC 2573, April 1999

[RFC2575]   Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
            Access Control Model (VACM) for the Simple Network
            Management Protocol (SNMP)", RFC 2575, April 1999

[RFC2570]   Case, J., Mundy, R., Partain, D., and B. Stewart,
            "Introduction to Version 3 of the Internet-standard Network
            Management Framework", RFC 2570, April 1999

[Q.922]     ITU-T, Recommendation Q.922:  "ISDN Data Link Layer
            Specification For Frame Mode Bearer Services"

[Q.933]     ITU-T, Recommendation Q.933:  "Signalling Specification For
            Frame Mode Basic Call Control"

[FRF.4]     R. Cherukuri (ed), FRF.4:  "Frame Relay User-to-Network SVC
            Implementation Agreement" January 5, 1994.

[FRF.16]    M. Sheehan (ed), FRF.16:  "UNI/NNI Multilink Frame Relay
            Interworking Implementation Agreement" August 20, 1999.

[RFC1604]   T. Brown, "Definitions of Managed Objects for Frame Relay
            Service" RFC 1604, Bell Communications Research, March 1994.
            [RFC-EDITOR:  Update to current RFC that replaces RFC1604]

[RFC2494]   D. Fowler, "Definitions of Managed Objects for the DS0 and
            DS0 Bundle Interface Type" RFC 2494, Newbridge Networks,
            November 1997.

[RFC2233]   K. McCloghrie, F. Kastenholz, "The Interfaces Group MIB
            using SMIv2" RFC 2233, Cisco Systems, FTP Software, November
            1997.

[ATMLANE]   T. Newton, ed., "LAN Emulation Client Management
            Specification Version 2.0" AF-LANE-0093.000, ATM Forum,
            October, 1998

[ATMIMA]    R. Vallee, ed., "Inverse Multiplexing for ATM Specification
            Version 1.1" (Appendix A) AF-PHY-0086.001, ATM Forum, March,
            1999

[RFC2115]   C. Brown, F. Baker, "Management Information Base for Frame
            Relay DTEs Using SMIv2" RFC 2115, Cadia Networks, Cisco
            Systems, September 1997.



Expires March 2001                                             [Page 36]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


[RFC1573]   K. McCloghrie, F. Kastenholz, "Evolution of the Interfaces
            Group of MIB-II" RFC 1573, Hughes LAN Systems, FTP Software,
            January 1994.
















































Expires March 2001                                             [Page 37]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


6.  Security Considerations

   There are a number of management objects defined in this MIB that
   have a MAX-ACCESS clause of read-write and/or read-create.  Such
   objects may be considered sensitive or vulnerable in some network
   environments.  The support for SET operations in a non-secure
   environment without proper protection can have a negative effect on
   network operations.

   No managed objects in this MIB contain sensitive information.

   SNMPv1 by itself is not a secure environment.  Even if the network
   itself is secure (for example by using IPSec), even then, there is no
   control as to who on the secure network is allowed to access and
   GET/SET (read/change/create/delete) the objects in this MIB.

   It is recommended that the implementers consider the security
   features as provided by the SNMPv3 framework.  Specifically, the use
   of the User-based Security Model RFC 2574 [RFC2574] and the View-
   based Access Control Model RFC 2575 [RFC2575] is recommended.

   It is then a customer/user responsibility to ensure that the SNMP
   entity giving access to an instance of this MIB, is properly
   configured to give access to the objects only to those principals
   (users) that have legitimate rights to indeed GET or SET
   (change/create/delete) them.

























Expires March 2001                                             [Page 38]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


7.  Authors' Addresses

  Prayson Pate
  Overture Networks
  P. O. Box 14864
  RTP, NC, USA 27709

  Phone: +1 919 302 5145

  EMail: prayson.pate@overturenetworks.com


  Bob Lynch
  Larscom Incorporated
  P. O. Box 14993
  RTP, NC, USA 27560

  Phone: +1 919 991-9062

  EMail: blynch@larscom.com


  Kenneth Rehbehn
  Megisto Systems, Inc.
  20251 Century Boulevard
  Germantown, MD, USA 20874

  Phone: +1 301 529-4427

  EMail: krehbehn@megisto.com

8.  Full Copyright Section

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

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the  purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.



Expires March 2001                                             [Page 39]

Internet Draft         MIB For FRF.16 UNI/NNI MFR         September 2000


   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.










































Expires March 2001                                             [Page 40]


Html markup produced by rfcmarkup 1.111, available from https://tools.ietf.org/tools/rfcmarkup/