frame relay dte mib update (finally)

Caralyn Brown <cbrown@baynetworks.com> Thu, 20 July 1995 19:56 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12959; 20 Jul 95 15:56 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12954; 20 Jul 95 15:56 EDT
Received: from ietf.cnri.reston.va.us by CNRI.Reston.VA.US id aa17831; 20 Jul 95 15:56 EDT
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa12897; 20 Jul 95 15:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa12893; 20 Jul 95 15:51 EDT
Received: from lobster.wellfleet.com by CNRI.Reston.VA.US id aa17737; 20 Jul 95 15:51 EDT
Received: from BayNetworks.com (pobox.wellfleet.com) by lobster.wellfleet.com (4.1/SMI-4.1) id AA05950; Thu, 20 Jul 95 15:51:19 EDT
Received: from godiva.engeast by BayNetworks.com (4.1/SMI-4.1) id AA20199; Thu, 20 Jul 95 15:52:34 EDT
Date: Thu, 20 Jul 95 15:52:34 EDT
X-Orig-Sender: iplpdn-request@IETF.CNRI.Reston.VA.US
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Caralyn Brown <cbrown@baynetworks.com>
Message-Id: <9507201952.AA20199@BayNetworks.com>
Received: by godiva.engeast (4.1/SMI-4.1) id AA09065; Thu, 20 Jul 95 15:52:34 EDT
To: iplpdn@CNRI.Reston.VA.US
Subject: frame relay dte mib update (finally)

-- 
Please find attached a new and improved copy of the update to the frame relay
DTE mib.  There have been a few minor changes, but for the most part it is
the same as the last version.  The highlights of the changes are as follows:

1. Update to address the ifIndex issue with the new ifTable/ifIndex.  This 
includes a new value in the frCircuitEntry to address logical interfaces.

2. The order of the DLCMI record has been modified to stay consistent with
the original 1315.  Apparently we inadvertently added a value at the top of
the list which caused problems.  The value was frDlcmiStatus.  It now lives
at the bottom of the DLCMI entry where it belongs.

3. Spelling errors (ok...so I'm not that great at spelling).

Hope you all enjoy this.

Caralyn
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Caralyn Brown             Voice: 508-436-3835
Bay Networks              Internet: cbrown@wellfleet.com
2 Federal Street
Billerica, MA 01821
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++




     Draft                Frame Relay DTE MIB             July 1995


            Management Information Base for Frame Relay DTEs
                   draft-ietf-iplpdn-frmib-dte-05.txt

                      Thu Jul 20 15:47:28 EDT 1995


                             Caralyn Brown

                           Bay Networks, Inc.
                            2 Federal Street
                    Billerica, Massachusetts  01821

                         cbrown@baynetworks.com


                            Charles Carvalho

                             Cisco Systems
                          633 Miramonte Drive
                    Santa Barbara, California 93109

                           carvalho@cisco.com


                               Fred Baker

                             Cisco Systems
                             519 Lado Drive
                    Santa Barbara, California 93111

                             fred@cisco.com






     1.  Status of this Memo

     This draft document will be submitted to the RFC editor as an
     extension to the SNMP MIB.  Please send comments to the
     authors, copying iplpdn@cnri.reston.va.us.  It expires October
     1995.







     Brown, Baker, and Carvalho                            [Page 1]





     Draft                Frame Relay DTE MIB             July 1995


     2.  Abstract

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

     This memo does not specify a standard for the Internet
     community.


     3.  The SNMPv2 Network Management Framework

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

     o    RFC 1441 which defines the SMI, the mechanisms used for
          describing and naming objects for the purpose of
          management.

     o    RFC 1213 defines MIB-II, the core set of managed objects
          for the Internet suite of protocols.

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

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


     3.1.  Object Definitions

     Managed objects are accessed via a virtual information store,
     termed the Management Information Base or MIB.  Objects in the
     MIB are defined using the subset of Abstract Syntax Notation
     One (ASN.1) defined in the SMI.  In particular, each object
     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.





     Brown, Baker, and Carvalho                            [Page 2]





     Draft                Frame Relay DTE MIB             July 1995


     4.  Overview

     4.1.  Frame Relay Operational Model

     For the purposes of understanding this document, Frame Relay
     is viewed as a multi-access media, not as a group of point-
     to-point connections.  This model proposes that Frame Relay is
     a single interface to the network (physical connection) with
     many destinations or neighbors (virtual connections).  This
     view enables a network manager the ability to group all
     virtual connections with their corresponding physical
     connection thereby allowing simpler diagnostics and trouble
     shooting.

     With the extention of the interfaces MIB, it is possible to
     configure frame relay DLCs as individual interfaces and create
     ifTable entries for each.  This is not recommended and is not
     directly supported by this MIB.  Additionally, in the presence
     of demand circuits (SVCs) creation of individual ifEntries for
     each is not possible.

     Should the user wish to group DLCs together to associate them
     with a higher layer, or to associate a DLC with an unnumbered
     point-to-point service, the frame relay DTE MIB provides an
     entry in the frCircuitEntry record.  For example, suppose one
     were to configure a company proprietary protocol to run above
     several of the frame relay VCs.  The basic layering would look
     something like the following:






















     Brown, Baker, and Carvalho                            [Page 3]





     Draft                Frame Relay DTE MIB             July 1995


      IP (ipaddrEntry 1 )  IP (ipaddrEntry 2)  IP (ipaddrEntry 3)
         |                    |                     |
         |                    |                     |
         |                    |              proprietary protocol
         |                    |              layer   (ifIndex 3)
         |                    |                     |
         |                    |                     |
      DLCI 20            DLCI 30            DLCI 40/41/42
      (ifIndex 2)        (ifIndex 2)         (ifIndex 2,
                                              logical ifIndex 3)
         |                    |                     |
         |                    |                     |
         |____________________|_____________________|
                              |
                              |
                      FR  DLMCI (ifIndex.2)
                              |
                              |
                   Physical Interface (ifIndex.1)



     A configuration which specified that DLCI 40, 41,and 42 were
     associated with a proprietary protocol layer, while DLCI 20
     and 30 were to run IP directly can now be expressed using a
     combination of frCircuitIfIndex and frCircuitLogicalIfIndex.
     In this particular case DLCIs 40, 41 and 42 would use
     frCircuitIfIndex equal to the frame relay interface level (2)
     while their frCircuitLogicalIfIndex would indicate the
     propritary protocol (3).  DLCIs 20 and 30 would have both
     instances set to the frame relay interface (2).


     4.2.  Textual Conventions

     One new data type is introduced as a textual convention in
     this MIB document.  This textual conventions enhances the
     readability of the specification and can ease comparison with
     other specifications if appropriate.  It should be noted that
     the introduction of the this textual conventions has no effect
     on either the syntax nor the semantics of any managed objects.
     The use of this is merely an artifact of the explanatory
     method used.  Objects defined in terms of one of these methods
     are always encoded by means of the rules that define the
     primitive type.  Hence, no changes to the SMI or the SNMP are





     Brown, Baker, and Carvalho                            [Page 4]





     Draft                Frame Relay DTE MIB             July 1995


     necessary to accommodate this textual conventions which is
     adopted merely for the convenience of readers and writers in
     pursuit of the elusive goal of clear, concise, and unambiguous
     MIB documents.

     The new data types is DLCI.  DLCI refers to the range
     0..DLCINumber, and is used to refer to the valid Data Link
     Connection Indices.  DLCINumber is, by definition, the largest
     possible DLCI value possible under the configured Q.922
     Address Format.

     4.3.  Structure of MIB

     The MIB is composed of three groups, one defining the Data
     Link Connection Management Interface (DLCMI), one describing
     the Circuits, and a third describing errors.

     During normal operation, Frame Relay virtual circuits will be
     added, deleted and change availability.  The occurrence of
     such changes is of interest to the network manager and
     therefore, one trap is defined, intended to be corollary to
     the SNMP "Link Up" and "Link Down" traps.




























     Brown, Baker, and Carvalho                            [Page 5]





     Draft                Frame Relay DTE MIB             July 1995


     5.  Definitions

     FRAME-RELAY-DTE-MIB DEFINITIONS ::= BEGIN

     IMPORTS
                 MODULE-IDENTITY, OBJECT-TYPE, Counter32,
                 Integer32, TimeTicks, NOTIFICATION-TYPE  FROM SNMPv2-SMI
                 TEXTUAL-CONVENTION, RowStatus            FROM SNMPv2-TC
                 MODULE-COMPLIANCE, OBJECT-GROUP          FROM SNMPv2-CONF
                 transmission                             FROM RFC1213-MIB
                 InterfaceIndex                           FROM RFC1573-MIB;

     --  Frame Relay DTE MIB

     frameRelayDTE MODULE-IDENTITY
         LAST-UPDATED "9501091735Z" -- Thu Jul 20 15:47:28 EDT 1995
         ORGANIZATION "IETF IPLPDN Working Group"
         CONTACT-INFO
            "       Caralyn Brown
            Postal: Bay Networks, Inc.
                    2 Federal Street
                    Billerica, Massachusetts  01821
            Tel:
            E-Mail: cbrown@baynetworks.com

                    Fred Baker
            Postal: Cisco Systems
                    519 Lado Drive
                    Santa Barbara, California 93111
            Tel:    +1 805 681 0115
            E-Mail: fred@cisco.com

                    Charles Carvalho
            Postal: Cisco Systems
                    633 Miramonte Drive
                    Santa Barbara, California 93109
            E-Mail: carvalho@cisco.com"
         DESCRIPTION
            "The MIB module to describe the use of a Frame Relay
            interface by a DTE."
         ::= { transmission 32 }


     --
     --      the range of a Data Link Connection Identifier





     Brown, Baker, and Carvalho                            [Page 6]





     Draft                Frame Relay DTE MIB             July 1995


     --
     DLCI ::= TEXTUAL-CONVENTION
         STATUS      current
         DESCRIPTION
            "The range of DLCI values.  Note that this varies by
            interface configuration; normally, interfaces may use
            0..1023, but may be configured to use ranges as large
            as 0..2^23."
         SYNTAX      Integer32        -- 0..8388607









































     Brown, Baker, and Carvalho                            [Page 7]





     Draft                Frame Relay DTE MIB             July 1995


     --  Data Link Connection Management Interface

     --      The variables that configure the DLC Management Interface.

     frDlcmiTable OBJECT-TYPE
         SYNTAX   SEQUENCE OF FrDlcmiEntry
         MAX-ACCESS   not-accessible
         STATUS   current
         DESCRIPTION
            "The Parameters for the Data Link Connection Management
            Interface for the frame relay service on this
            interface."
         REFERENCE
            "American National Standard T1.617-1991, Annex D"
         ::= { frameRelayDTE 1 }

     frDlcmiEntry OBJECT-TYPE
         SYNTAX   FrDlcmiEntry
         MAX-ACCESS   not-accessible
         STATUS   current
         DESCRIPTION
            "The Parameters for a particular Data Link Connection
            Management Interface."
         INDEX { frDlcmiIfIndex }
         ::= { frDlcmiTable 1 }


     FrDlcmiEntry ::=
         SEQUENCE {
             frDlcmiIfIndex
                 InterfaceIndex,
             frDlcmiState
                 INTEGER,
             frDlcmiAddress
                 INTEGER,
             frDlcmiAddressLen
                 INTEGER,
             frDlcmiPollingInterval
                 INTEGER,
             frDlcmiFullEnquiryInterval
                 INTEGER,
             frDlcmiErrorThreshold
                 INTEGER,
             frDlcmiMonitoredEvents
                 INTEGER,





     Brown, Baker, and Carvalho                            [Page 8]





     Draft                Frame Relay DTE MIB             July 1995


             frDlcmiMaxSupportedVCs
                 Integer32,
             frDlcmiMulticast
                 INTEGER,
             frDlcmiStatus
                 INTEGER,
             frDlcmiRowStatus
                 RowStatus
     }


     frDlcmiIfIndex OBJECT-TYPE
         SYNTAX   InterfaceIndex
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The ifIndex value of the corresponding ifEntry."
         ::= { frDlcmiEntry 1 }


     frDlcmiState OBJECT-TYPE
         SYNTAX INTEGER      {
             noLmiConfigured  (1),
             lmiRev1          (2),
             ansiT1-617D      (3),  -- ANSI T1.617 Annex D
             ansiT1-617B      (4),  -- ANSI T1.617 Annex B
             ituT-933A        (5),  -- CCITT Q933 Annex A
             ansiT1-617-1994D (6)   -- ANSI T1.617a-1994 Annex D
         }
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This variable states which Data Link Connection
            Management scheme is active (and by implication, what
            DLCI it uses) on the Frame Relay interface."
         REFERENCE
            "American National Standard T1.617-1991, American
            National Standard T1.617a-1994, ITU-T Recommendation
            Q.933 (03/93)."

         ::= { frDlcmiEntry 2 }


     frDlcmiAddress OBJECT-TYPE
         SYNTAX      INTEGER {





     Brown, Baker, and Carvalho                            [Page 9]





     Draft                Frame Relay DTE MIB             July 1995


                     q921           (1),  -- 13 bit DLCI
                     q922March90    (2),  -- 11 bit DLCI
                     q922November90 (3),  -- 10 bit DLCI
                     q922           (4)   -- Final Standard
         }
         MAX-ACCESS  read-write
         STATUS  current
         DESCRIPTION
            "This variable states which address format is in use on
            the Frame Relay interface."
         ::= { frDlcmiEntry 3 }


     frDlcmiAddressLen OBJECT-TYPE
         SYNTAX  INTEGER     {
                 twoOctets (2),
                 threeOctets (3),
                 fourOctets (4)
         }
         MAX-ACCESS  read-write
         STATUS  current
         DESCRIPTION
            "This variable states the address length in octets.  In
            the case of Q922 format, the length indicates the
            entire length of the address including the control
            portion."
         ::= { frDlcmiEntry 4 }


     frDlcmiPollingInterval OBJECT-TYPE
         SYNTAX   INTEGER (5..30)
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This is the number of seconds between successive
            status enquiry messages."
         REFERENCE
            "American National Standard T1.617-1991, Section D.7
            Timer T391."
         DEFVAL { 10 }
         ::= { frDlcmiEntry 5 }


     frDlcmiFullEnquiryInterval OBJECT-TYPE
         SYNTAX   INTEGER (1..255)





     Brown, Baker, and Carvalho                           [Page 10]





     Draft                Frame Relay DTE MIB             July 1995


         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "Number of status enquiry intervals that pass before
            issuance of a full status enquiry message."
         REFERENCE
            "American National Standard T1.617-1991, Section D.7
            Counter N391."
         DEFVAL { 6 }
         ::= { frDlcmiEntry 6 }



     frDlcmiErrorThreshold OBJECT-TYPE
         SYNTAX   INTEGER (1..10)
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This is the maximum number of unanswered Status
            Enquiries the equipment shall accept before declaring
            the interface down."
         REFERENCE
            "American National Standard T1.617-1991, Section D.5.1
            Counter N392."
         DEFVAL { 3 }
         ::= { frDlcmiEntry 7 }


     frDlcmiMonitoredEvents OBJECT-TYPE
         SYNTAX   INTEGER (1..10)
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This is the number of status polling intervals over
            which the error threshold is counted.  For example, if
            within 'MonitoredEvents' number of events the station
            receives 'ErrorThreshold' number of errors, the
            interface is marked as down."
         REFERENCE
            "American National Standard T1.617-1991, Section D.5.2
            Counter N393."
         DEFVAL { 4 }
         ::= { frDlcmiEntry 8 }







     Brown, Baker, and Carvalho                           [Page 11]





     Draft                Frame Relay DTE MIB             July 1995


     frDlcmiMaxSupportedVCs OBJECT-TYPE
         SYNTAX   Integer32
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "The maximum number of Virtual Circuits allowed for
            this interface.  Usually dictated by the Frame Relay
            network.

            In response to a SET, if a value less than zero or
            higher than the agent's maximal capability is
            configured, the agent should respond badValue"
         ::= { frDlcmiEntry 9 }


     frDlcmiMulticast OBJECT-TYPE
         SYNTAX   INTEGER    {
                     nonBroadcast (1),
                     broadcast (2)
                     }
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This indicates whether the Frame Relay interface is
            using a multicast service."
         ::= { frDlcmiEntry 10 }



     frDlcmiStatus OBJECT-TYPE
         SYNTAX   INTEGER    {
                     running      (1),    -- init complete, system running
                     fault        (2),    -- error threshold exceeded
                     initializing (3)     -- system start up
                     }
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "This indicates the status of the Frame Relay interface
            as determined by the performance of the dlcmi.  If no
            dlcmi is running, the Frame Relay interface will stay
            in the running state indefinately."
         ::= { frDlcmiEntry 11 }







     Brown, Baker, and Carvalho                           [Page 12]





     Draft                Frame Relay DTE MIB             July 1995


     frDlcmiRowStatus OBJECT-TYPE
         SYNTAX   RowStatus
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "SNMP Version 2 Row Status Variable."
         ::= { frDlcmiEntry 12 }











































     Brown, Baker, and Carvalho                           [Page 13]





     Draft                Frame Relay DTE MIB             July 1995


     -- A Frame Relay service is a multiplexing service.  Data
     -- Link Connection Identifiers enumerate virtual circuits
     -- (permanent or dynamic) which are layered onto the underlying
     -- circuit, represented by ifEntry.  Therefore, each of the entries
     -- in the Standard MIB's Interface Table with an IfType of
     -- Frame Relay represents a Q.922 interface.  Zero or more
     -- virtual circuits are layered onto this interface and provide
     -- interconnection with various remote destinations.
     -- Each such virtual circuit is represented by an entry in the
     -- circuit table.

     --   Circuit Table

     -- The table describing the use of the DLCIs attached to
     -- each Frame Relay Interface.

     frCircuitTable OBJECT-TYPE
         SYNTAX   SEQUENCE OF FrCircuitEntry
         MAX-ACCESS   not-accessible
         STATUS   current
         DESCRIPTION
            "A table containing information about specific Data
            Link Connections (DLC) or virtual circuits."
         ::= { frameRelayDTE 2 }

     frCircuitEntry OBJECT-TYPE
         SYNTAX   FrCircuitEntry
         MAX-ACCESS   not-accessible
         STATUS   current
         DESCRIPTION
            "The information regarding a single Data Link
            Connection."
         INDEX { frCircuitIfIndex, frCircuitDlci }
         ::= { frCircuitTable 1 }


     FrCircuitEntry ::=
         SEQUENCE {
             frCircuitIfIndex
                 InterfaceIndex,
             frCircuitDlci
                 DLCI,
             frCircuitState
                 INTEGER,
             frCircuitReceivedFECNs





     Brown, Baker, and Carvalho                           [Page 14]





     Draft                Frame Relay DTE MIB             July 1995


                 Counter32,
             frCircuitReceivedBECNs
                 Counter32,
             frCircuitSentFrames
                 Counter32,
             frCircuitSentOctets
                 Counter32,
             frCircuitReceivedFrames
                 Counter32,
             frCircuitReceivedOctets
                 Counter32,
             frCircuitCreationTime
                 TimeStamp,
             frCircuitLastTimeChange
                 TimeStamp,
             frCircuitCommittedBurst
                 Integer32,
             frCircuitExcessBurst
                 Integer32,
             frCircuitThroughput
                 Integer32,
             frCircuitMulticast
                 INTEGER,
             frCircuitType
                 INTEGER,
             frCircuitDiscards
                 Counter32,
             frCircuitRowStatus
                 RowStatus,
             frCircuitReceivedDEs
                 Counter32,
             frCircuitLogicalIfIndex
                 InterfaceIndex
     }


     frCircuitIfIndex OBJECT-TYPE
         SYNTAX   InterfaceIndex
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The ifIndex Value of the ifEntry this virtual circuit
            is layered onto."
         ::= { frCircuitEntry 1 }






     Brown, Baker, and Carvalho                           [Page 15]





     Draft                Frame Relay DTE MIB             July 1995


     frCircuitDlci OBJECT-TYPE
         SYNTAX   DLCI
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The Data Link Connection Identifier for this virtual
            circuit."
         REFERENCE
            "American National Standard T1.618-1991, Section 3.3.6"
         ::= { frCircuitEntry 2 }


     frCircuitState OBJECT-TYPE
         SYNTAX   INTEGER    {
                     invalid (1),
                     active (2),
                     inactive (3)
                  }
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "Indicates whether the particular virtual circuit is
            operational.  In the absence of a Data Link Connection
            Management Interface, virtual circuit entries (rows)
            may be created by setting virtual circuit state to
            'active', or deleted by changing Circuit state to
            'invalid'.

            Whether or not the row actually disappears is left to
            the implementation, so this object may actually read as
            'invalid' for some arbitrary length of time.  It is
            also legal to set the state of a virtual circuit to
            'inactive' to temporarily disable a given circuit.

            The use of 'invalid' is deprecated in this SNMP Version
            2 MIB, in favor of frCircuitRowStatus."
         DEFVAL { active }
         ::= { frCircuitEntry 3 }


     frCircuitReceivedFECNs OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION





     Brown, Baker, and Carvalho                           [Page 16]





     Draft                Frame Relay DTE MIB             July 1995


            "Number of frames received from the network indicating
            forward congestion since the virtual circuit was
            created.  This occurs when the remote DTE sets the FECN
            flag, or when a switch in the network enqueues the
            frame to a trunk whose transmission queue is
            congested."
         REFERENCE
            "American National Standard T1.618-1991, Section 3.3.3"
         ::= { frCircuitEntry 4 }


     frCircuitReceivedBECNs OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "Number of frames received from the network indicating
            backward congestion since the virtual circuit was
            created.  This occurs when the remote DTE sets the BECN
            flag, or when a switch in the network receives the
            frame from a trunk whose transmission queue is
            congested."
         REFERENCE
            "American National Standard T1.618-1991, Section 3.3.4"
         ::= { frCircuitEntry 5 }


     frCircuitSentFrames OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The number of frames sent from this virtual circuit
            since it was created."
         ::= { frCircuitEntry 6 }


     frCircuitSentOctets OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The number of octets sent from this virtual circuit
            since it was created."
         ::= { frCircuitEntry 7 }





     Brown, Baker, and Carvalho                           [Page 17]





     Draft                Frame Relay DTE MIB             July 1995


     frCircuitReceivedFrames OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "Number of frames received over this virtual circuit
            since it was created."
         ::= { frCircuitEntry 8 }


     frCircuitReceivedOctets OBJECT-TYPE
         SYNTAX   Counter32
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "Number of octets received over this virtual circuit
            since it was created."
         ::= { frCircuitEntry 9 }


     frCircuitCreationTime OBJECT-TYPE
         SYNTAX   TimeStamp
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The value of sysUpTime when the virtual circuit was
            created, whether by the Data Link Connection Management
            Interface or by a SetRequest."
         ::= { frCircuitEntry 10 }


     frCircuitLastTimeChange OBJECT-TYPE
         SYNTAX   TimeStamp
         MAX-ACCESS   read-only
         STATUS   current
         DESCRIPTION
            "The value of sysUpTime when last there was a change in
            the virtual circuit state"
         ::= { frCircuitEntry 11 }


     frCircuitCommittedBurst OBJECT-TYPE
         SYNTAX   Integer32
         MAX-ACCESS   read-write
         STATUS   current





     Brown, Baker, and Carvalho                           [Page 18]





     Draft                Frame Relay DTE MIB             July 1995


         DESCRIPTION
            "This variable indicates the maximum amount of data, in
            bits, that the network agrees to transfer under normal
            conditions, during the measurement interval."
         REFERENCE
            "American National Standard T1.617-1991, Section
            6.5.19"
         DEFVAL   { 0 }  -- the default indicates no commitment
         ::= { frCircuitEntry 12 }


     frCircuitExcessBurst OBJECT-TYPE
         SYNTAX   Integer32
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This variable indicates the maximum amount of
            uncommitted data bits that the network will attempt to
            deliver over the measurement interval.

            By default, if not configured when creating the entry,
            the Excess Information Burst Size is set to the value
            of ifSpeed."
         REFERENCE
            "American National Standard T1.617-1991, Section
            6.5.19"
                ::= { frCircuitEntry 13 }


            frCircuitThroughput OBJECT-TYPE
                SYNTAX   Integer32
                MAX-ACCESS   read-write
                STATUS   current
                DESCRIPTION
                   "Throughput is the average number of 'Frame
                   Relay Information Field' bits transferred per
                   second across a user network interface in one
                   direction, measured over the measurement
                   interval.

                   If the configured committed burst rate and
                   throughput are both non-zero, the measurement
                   interval
                    T=frCircuitCommittedBurst/frCircuitThroughput.






     Brown, Baker, and Carvalho                           [Page 19]





     Draft                Frame Relay DTE MIB             July 1995


                   If the configured committed burst rate and
                   throughput are both zero, the measurement
                   interval
                           T=frCircuitExcessBurst/ifSpeed."
               REFERENCE
                  "American National Standard T1.617-1991, Section
                  6.5.19"
              DEFVAL {0}  -- the default value of Throughput is
                          -- "no commitment".
              ::= { frCircuitEntry 14 }


          frCircuitMulticast OBJECT-TYPE
              SYNTAX   INTEGER    {
                          unicast   (1),
                          multicast (2)
                          }
              MAX-ACCESS   read-only
              STATUS   current
              DESCRIPTION
                 "This indicates whether this VC is used as a
                 multicast VC or a single destination"
             ::= { frCircuitEntry 15 }


         frCircuitType OBJECT-TYPE
             SYNTAX   INTEGER    {
                         static  (1),
                         dynamic (2)
                      }
             MAX-ACCESS   read-only
             STATUS   current
             DESCRIPTION
                "Indication of whether the VC was manually created
                (static), or dynamically created (dynamic) via the
                data link control managment interface."
            ::= { frCircuitEntry 16 }


        frCircuitDiscards OBJECT-TYPE
            SYNTAX   Counter32
            MAX-ACCESS   read-only
            STATUS   current
            DESCRIPTION
               "The number of inbound frames dropped because of





     Brown, Baker, and Carvalho                           [Page 20]





     Draft                Frame Relay DTE MIB             July 1995


               format errors, or because the VC is inactive."
           ::= { frCircuitEntry 17 }


       frCircuitRowStatus OBJECT-TYPE
           SYNTAX   RowStatus
           MAX-ACCESS   read-write
           STATUS   current
           DESCRIPTION
              " This object is used to create a new row or modify
              or destroy an existing row in the manner described in
              the definition of the RowStatus textual convention."
          ::= { frCircuitEntry 18 }


      frCircuitReceivedDEs OBJECT-TYPE
          SYNTAX   Counter32
          MAX-ACCESS   read-only
          STATUS   current
          DESCRIPTION
             "Number of frames received from the network indicating
             that they were eligible for discard since the virtual
             circuit was created.  This occurs when the remote DTE
             sets the DE flag, or when in remote DTE's switch
             detects that the frame was received as Excess Burst
             data."
         REFERENCE
            "American National Standard T1.618-1991, Section 3.3.4"
         ::= { frCircuitEntry 19 }


     frCircuitLogicalIfIndex OBJECT-TYPE
         SYNTAX  InterfaceIndex
         MAX-ACCESS read-write
         STATUS  current
         DESCRIPTION
            "Normally the same value as frDlcmiIfIndex, but
            different when an implementation associates a virtual
            ifEntry with a DLC or set of DLCs in order to associate
            higher layer objects such as the ipAddrEntry with a
            subset of the virtual circuits on a Frame Relay
            interface. The type of such ifEntries is defined by the
            higher layer object; for example, if PPP/Frame Relay is
            implemented, the ifType of this ifEntry would be PPP.
            If it is not so defined, as would be the case with an





     Brown, Baker, and Carvalho                           [Page 21]





     Draft                Frame Relay DTE MIB             July 1995


            ipAddrEntry, it should be of type Other."
        ::= { frCircuitEntry 20 }.so frErrTable.v2

     -- Frame Relay Trap Control

     frameRelayTrapControl OBJECT IDENTIFIER ::= { frameRelayDTE 4 }
     frameRelayTraps OBJECT IDENTIFIER ::= { frameRelayDTE 5 }

     frTrapState OBJECT-TYPE
         SYNTAX  INTEGER     { enabled(1), disabled(2) }
         MAX-ACCESS   read-write
         STATUS   current
         DESCRIPTION
            "This variable indicates whether the system produces
            the frDLCIStatusChange trap."
         DEFVAL { disabled }
         ::= { frameRelayTrapControl 1 }



     --  Data Link Connection Management Interface Related Traps

     frDLCIStatusChange NOTIFICATION-TYPE
         OBJECTS  { frCircuitState }
         STATUS      current
         DESCRIPTION
            "This trap indicates that the indicated Virtual Circuit
            has changed state.  It has either been created or
            invalidated, or has toggled between the active and
            inactive states."
     ::= { frameRelayTraps 1 }

     -- conformance information

     frConformance OBJECT IDENTIFIER ::= { frameRelayDTE 6 }

     frGroups      OBJECT IDENTIFIER ::= { frConformance 1 }
     frCompliances OBJECT IDENTIFIER ::= { frConformance 2 }

     -- compliance statements

     frCompliance MODULE-COMPLIANCE
         STATUS  current
         DESCRIPTION
            "The compliance statement "





     Brown, Baker, and Carvalho                           [Page 22]





     Draft                Frame Relay DTE MIB             July 1995


         MODULE  -- this module
         MANDATORY-GROUPS { frLmiGroup,
                            frCircuitGroup,
                            frErrorGroup
                          }

         GROUP       frTrapGroup
         DESCRIPTION
            "This group is optional, and is used for the management
            of asynchronous notifications by Frame Relay Systems."
         ::= { frCompliances 1 }

     -- units of conformance

     frLmiGroup    OBJECT-GROUP
         OBJECTS {
                   frDlcmiIfIndex,
                   frDlcmiState,
                   frDlcmiStatus,
                   frDlcmiAddress ,
                   frDlcmiAddressLen,
                   frDlcmiPollingInterval,
                   frDlcmiFullEnquiryInterval,
                   frDlcmiErrorThreshold,
                   frDlcmiMonitoredEvents,
                   frDlcmiMaxSupportedVCs,
                   frDlcmiMulticast,
                   frDlcmiRowStatus  }
         STATUS  current
         DESCRIPTION
            "The objects necessary to control the Link Management
            Interface for a Frame Relay Interface."
         ::= { frGroups 1 }

     frCircuitGroup    OBJECT-GROUP
         OBJECTS {
                   frCircuitIfIndex,
                   frCircuitDlci,
                   frCircuitState,
                   frCircuitReceivedFECNs,
                   frCircuitReceivedBECNs,
                   frCircuitReceivedDEs,
                   frCircuitSentFrames,
                   frCircuitSentOctets,
                   frCircuitReceivedFrames,





     Brown, Baker, and Carvalho                           [Page 23]





     Draft                Frame Relay DTE MIB             July 1995


                   frCircuitReceivedOctets,
                   frCircuitCreationTime,
                   frCircuitLastTimeChange,
                   frCircuitCommittedBurst,
                   frCircuitExcessBurst,
                   frCircuitThroughput,
                   frCircuitMulticast,
                   frCircuitType,
                   frCircuitDiscards,
                   frCircuitRowStatus
                 }
         STATUS  current
         DESCRIPTION
            "The objects necessary to control the Virtual Circuits
            layered onto a Frame Relay Interface."
         ::= { frGroups 2 }

     frErrorGroup    OBJECT-GROUP
         OBJECTS {
                     frErrIfIndex,
                     frErrType,
                     frErrData,
                     frErrTime,
                     frErrDiscards,
                     frErrFaults,
                     frErrFaultTime
                 }
         STATUS  current
         DESCRIPTION
            "The objects necessary to display recent errors on a
            Frame Relay Interface."
         ::= { frGroups 3 }

     frTrapGroup    OBJECT-GROUP
         OBJECTS { frTrapState }
         STATUS  current
         DESCRIPTION
            "The objects necessary to control a Frame Relay
            Interface's notification messages."
         ::= { frGroups 4 }
     END









     Brown, Baker, and Carvalho                           [Page 24]





     Draft                Frame Relay DTE MIB             July 1995


     6.  Acknowledgements

     This document was produced by the IP Over Large Public Data
     Networks (IPLPDN) Working Group.

     The following people provided additional comments and
     suggestions: Art Berggreen of Advanced Computer
     Communications, and Jim Philippou of Xyplex Communications.










































     Brown, Baker, and Carvalho                           [Page 25]





     Draft                Frame Relay DTE MIB             July 1995


     7.  References

     [1]  V. Cerf, IAB Recommendations for the Development of
          Internet Network Management Standards.  Internet Working
          Group Request for Comments 1052.  Network Information
          Center, SRI International, Menlo Park, California, April
          1988.

     [2]  V. Cerf, Report of the Second Ad Hoc Network Management
          Review Group, Internet Working Group Request for Comments
          1109.  Network Information Center, SRI International,
          Menlo Park, California, August 1989.

     [3]  M.T. Rose and K. McCloghrie, Structure and Identification
          of Management Information for TCP/IP-based internets,
          Internet Working Group Request for Comments 1155.
          Network Information Center, SRI International, Menlo
          Park, California, May 1990.

     [4]  K. McCloghrie and M.T. Rose, Management Information Base
          for Network Management of TCP/IP-based internets,
          Internet Working Group Request for Comments 1156.
          Network Information Center, SRI International, Menlo
          Park, California, May 1990.

     [5]  J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
          Simple Network Management Protocol, Internet Working
          Group Request for Comments 1157.  Network Information
          Center, SRI International, Menlo Park, California, May
          1990.

     [6]  M.T. Rose, K.  McCloghrie (editors), "Management
          Information Base for Network Management of TCP/IP-based
          internets", RFC 1213, Performance Systems Internations,
          March 1991

     [7]  Information processing systems - Open Systems
          Interconnection - Specification of Abstract Syntax
          Notation One (ASN.1), International Organization for
          Standardization.  International Standard 8824, December
          1987.

     [8]  Information processing systems - Open Systems
          Interconnection - Specification of Basic Encoding Rules
          for Abstract Notation One (ASN.1), International





     Brown, Baker, and Carvalho                           [Page 26]





     Draft                Frame Relay DTE MIB             July 1995


          Organization for Standardization.  International Standard
          8825, December 1987.

     [9]  M.T. Rose, K. McCloghrie (editors), "Concise MIB
          Definitions", RFC 1212, Performance Systems
          International, Hughes LAN Systems, March 1991

     [10] M.T. Rose (editor), "Convention for Defining Traps for
          use with the SNMP", RFC 1215 Internet Engineering Task
          Force, March 1991.








































     Brown, Baker, and Carvalho                           [Page 27]





     Draft                Frame Relay DTE MIB             July 1995


     Table of Contents


     1 Status of this Memo ...................................    1
     2 Abstract ..............................................    2
     3 The SNMPv2 Network Management Framework ...............    2
     3.1 Object Definitions ..................................    2
     4 Overview ..............................................    3
     4.1 Frame Relay Operational Model .......................    3
     4.2 Textual Conventions .................................    4
     4.3 Structure of MIB ....................................    5
     5 Definitions ...........................................    6
     5.1 Data Link Connection Management Interface ...........    8
     5.2 Circuit Table .......................................   14
     5.4 Trap Management .....................................   22
     6 Acknowledgements ......................................   25
     7 References ............................................   26

































     Brown, Baker, and Carvalho                           [Page 28]