RMON2-MIB DEFINITIONS ::= BEGIN

IMPORTS

    MODULE-IDENTITY, OBJECT-TYPE, Counter32, Integer32,

    Gauge32, IpAddress, TimeTicks, mib-2         FROM SNMPv2-SMI

    TEXTUAL-CONVENTION, RowStatus, DisplayString, TimeStamp

                                                 FROM SNMPv2-TC

    MODULE-COMPLIANCE, OBJECT-GROUP              FROM SNMPv2-CONF

    ifIndex                                      FROM IF-MIB

    OwnerString, statistics, history, hosts,

    matrix, filter, etherStatsEntry, historyControlEntry,

    hostControlEntry, matrixControlEntry, filterEntry,

    channelEntry                    FROM RMON-MIB

    tokenRing, tokenRingMLStatsEntry, tokenRingPStatsEntry,

    ringStationControlEntry, sourceRoutingStatsEntry

                                    FROM TOKEN-RING-RMON-MIB;

--  Remote Network Monitoring MIB

rmon MODULE-IDENTITY

    LAST-UPDATED "200605020000Z"    -- May 2, 2006

    ORGANIZATION "IETF RMON MIB Working Group"

    CONTACT-INFO

        "Author:

                     Steve Waldbusser

             Phone:  +1-650-948-6500

             Fax :   +1-650-745-0671

             Email:  waldbusser@nextbeacon.com

         Working Group Chair:

                     Andy Bierman

             E-mail: ietf@andybierman.com

         Working Group Mailing List: <rmonmib@ietf.org>

         To subscribe send email to: <rmonmib-request@ietf.org>    "

    DESCRIPTION

        "The MIB module for managing remote monitoring

         device implementations.  This MIB module

         extends the architecture introduced in the original

         RMON MIB as specified in RFC 2819.

         Copyright (C) The Internet Society (2006).  This version of

         this MIB module is part of RFC 4502;  see the RFC itself for

         full legal notices."

    REVISION "200605020000Z"    -- May 2, 2006

    DESCRIPTION

        "This version updates the proposed-standard version of the

        RMON2 MIB (published as RFC 2021) by adding 2 new

        enumerations to the nlMatrixTopNControlRateBase object and

        4 new enumerations to the alMatrixTopNControlRateBase object.

        These new enumerations support the creation of high-capacity

        topN reports in the High Capacity RMON MIB [RFC3273].

        Additionally, the following objects have been deprecated, as

        they have not had enough independent implementations to

        demonstrate interoperability to meet the requirements of a

        Draft Standard:

        probeDownloadFile

        probeDownloadTFTPServer

        probeDownloadAction

        probeDownloadStatus

        serialMode

        serialProtocol

        serialTimeout

        serialModemInitString

        serialModemHangUpString

        serialModemConnectResp

        serialModemNoConnectResp

        serialDialoutTimeout

        serialStatus

        serialConnectDestIpAddress

        serialConnectType

        serialConnectDialString

        serialConnectSwitchConnectSeq

        serialConnectSwitchDisconnectSeq

        serialConnectSwitchResetSeq

        serialConnectOwner

        serialConnectStatus

        netConfigIPAddress

        netConfigSubnetMask

        netConfigStatus

        netDefaultGateway

        tokenRingMLStats2DroppedFrames

        tokenRingMLStats2CreateTime

        tokenRingPStats2DroppedFrames

        tokenRingPStats2CreateTime

        ringStationControl2DroppedFrames

        ringStationControl2CreateTime

        sourceRoutingStats2DroppedFrames

        sourceRoutingStats2CreateTime

        trapDestIndex

        trapDestCommunity

        trapDestProtocol

        trapDestAddress

        trapDestOwner

        trapDestStatus

        In addition, two corrections were made.  The LastCreateTime

        Textual Convention had been defined with a base type of

        another textual convention, which isn't allowed in SMIv2.  The

        definition has been modified to use TimeTicks as the base

        type.

        Further, the SerialConfigEntry SEQUENCE definition included

        sub-typing information that is not allowed in SMIv2.  This

        information has been deleted.  Ranges were added to a number of

        objects and textual-conventions to constrain their maximum

        (and sometimes minimum) sizes.  The addition of these ranges

        documents existing practice for these objects.  These objects

        are:

            ControlString

            protocolDirID

            protocolDirParameters

            addressMapNetworkAddress

            nlHostAddress

            nlMatrixSDSourceAddress

            nlMatrixSDDestAddress

            nlMatrixDSSourceAddress

            nlMatrixDSDestAddress

            nlMatrixTopNSourceAddress

            nlMatrixTopNDestAddress

            alHostEntry

            alMatrixSDEntry

            alMatrixDSEntry

            alMatrixTopNSourceAddress

            alMatrixTopNDestAddress

        Finally, the TimeFilter TC has been updated to encourage agent

        implementations that allow a MIB walk to behave well even when

        performed by an application that is not aware of the special

        TimeFilter semantics."

    REVISION "200207080000Z"        -- 08 July, 2002

    DESCRIPTION

        "Added new enumerations to support the High-Capacity RMON

        MIB as defined in RFC 3273.  Also fixed some typos and

        added clarifications."

    REVISION "199605270000Z"    -- 27 May, 1996

    DESCRIPTION

        "Original version.  Published as RFC 2021."

    ::= { mib-2 16 }

-- { rmon 1 } through { rmon 10 } are defined in RMON and

-- the Token Ring RMON MIB [RFC1513]

    protocolDir     OBJECT IDENTIFIER ::= { rmon 11 }

    protocolDist    OBJECT IDENTIFIER ::= { rmon 12 }

    addressMap      OBJECT IDENTIFIER ::= { rmon 13 }

    nlHost          OBJECT IDENTIFIER ::= { rmon 14 }

    nlMatrix        OBJECT IDENTIFIER ::= { rmon 15 }

    alHost          OBJECT IDENTIFIER ::= { rmon 16 }

    alMatrix        OBJECT IDENTIFIER ::= { rmon 17 }

    usrHistory      OBJECT IDENTIFIER ::= { rmon 18 }

    probeConfig     OBJECT IDENTIFIER ::= { rmon 19 }

    rmonConformance OBJECT IDENTIFIER ::= { rmon 20 }

-- Textual Conventions

ZeroBasedCounter32 ::= TEXTUAL-CONVENTION

    STATUS current

    DESCRIPTION

        "This TC describes an object that counts events with the

        following semantics: objects of this type will be set to

        zero(0) on creation and will thereafter count appropriate

        events, wrapping back to zero(0) when the value 2^32 is

        reached.

        Provided that an application discovers the new object within

        the minimum time to wrap, it can use the initial value as a

        delta since it last polled the table of which this object is

        part.  It is important for a management station to be aware of

        this minimum time and the actual time between polls, and to

        discard data if the actual time is too long or there is no

        defined minimum time.

        Typically, this TC is used in tables where the INDEX space is

        constantly changing and/or the TimeFilter mechanism is in use."

    SYNTAX Gauge32

LastCreateTime ::= TEXTUAL-CONVENTION

    STATUS current

    DESCRIPTION

        "This TC describes an object that stores the value of the

        sysUpTime object at the last time its entry was created.

        This can be used for polling applications to determine that an

        entry has been deleted and re-created between polls, causing

        an otherwise undetectable discontinuity in the data.

        If sysUpTime is reset to zero as a result of a re-

        initialization of the network management (sub)system, then

        the values of all LastCreateTime objects are also reset.

        However, after approximately 497 days without a re-

        initialization, the sysUpTime object will reach 2^^32-1 and

        then increment to zero; in this case, existing values

        of TimeStamp objects do not change.  This can lead to

        ambiguities in the value of TimeStamp objects."

    SYNTAX TimeTicks

TimeFilter ::= TEXTUAL-CONVENTION

  STATUS        current

  DESCRIPTION

      "To be used for the index to a table.  Allows an application

      to download only those rows changed since a particular time.

      Note that this is not a history mechanism.  Only current values

      of underlying objects are returned; saved instance values

      associated with particular values of sysUpTime are not.

      An entry is considered changed if the value of any object in the

      entry changes, if the row is created, or if any object in the

      entry is created or deleted.  Note that deleted entries cannot

      be detected or downloaded.

      A time-filtered conceptual table is created by inserting a

      single object of SYNTAX TimeFilter as the first INDEX component

      in a copy of an existing basic conceptual table (i.e., any

      SEQUENCE without a TimeFilter INDEX component).  Thus, for

      each conceptual entry 'I' in the basic table, there exists N

      conceptual entries in the time-filtered version, indexed N.I,

      where 'N' is equal to the value of sysUpTime.

      When an application retrieves conceptual instances from a

      time-filtered table, and an INDEX value is provided for the

      TimeFilter INDEX component 'N', the agent will only consider

      returning basic conceptual entries (e.g., 'fooColumn.N.I') if

      any column within the basic conceptual entry has changed since

      sysUpTime 'N'.  If not, the basic conceptual entry will

      be ignored for the particular retrieval operation.

      When sysUpTime is equal to zero, this table shall be empty.

      One conceptual entry exists for each past value of sysUpTime,

      except that the whole table is purged should sysUpTime wrap.

      As an entry in a time-filtered table is updated (i.e., one of

      the columns in the basic conceptual table is changed), new

      conceptual entries are also created in the time-filtered version

      (which still shares the now updated object values with all other

      instances).  The number of unique time-filtered instances that

      are created is determined by the value of sysUpTime at which the

      basic entry was last updated.  One unique instance will exist

      for each value of sysUpTime at the last update time for the row.

      However, a new TimeFilter index instance is created for each new

      sysUpTime value.  The TimeFilter index values not associated

      with entry updates are called duplicate time-filtered instances.

      After some deployment experience, it has been determined that

      a time-filtered table is more efficient if the agent

      stops a MIB walk operation by skipping over rows with a

      TimeFilter index value higher than the value in the received

      GetNext/GetBulk request.  That is, instead of incrementing a

      TimeFilter index value, the agent will continue to the next

      object or table.  As a consequence, GetNext or GetBulk

      operations will provide only one pass through a time-filtered

      table.

      It is suggested that an agent implement a time-filtered table

      in this manner to improve performance and avoid a MIB walk

      getting stuck in time-filtered tables.  It is, however, still

      acceptable for an agent to implement a time-filtered table in

      the traditional manner (i.e., every conceptual time-filtered

      instance is returned in GetNext and GetBulk PDU responses), and

      management applications must be able to deal with such

      traditional implementations.

      See the appendix for further discussion of this textual

      convention.

      The following example is provided to demonstrate TimeFilter

      behavior:

      Consider the following basic conceptual table, basicFooTable.

      (Note that the basic version of a time-filtered table may not

      actually be defined.)

          basicFooTable:

          basicFooTable ...

          INDEX { fooIndex }

          BasicFooEntry {

             fooIndex     Integer32,

             fooCounts    Counter32

          }

      For this example, the basicFooTable contains two static

      conceptual entries (fooIndex equals '1' and '2'), created at

      time zero.  It also contains one dynamic conceptual entry

      (fooIndex equals '3'), which is created at time '3' and deleted

      at time '7'.

      The time-filtered version of the basicFooTable could be defined

      as follows:

          FooTable:

          fooTable ...

          INDEX { fooTimeMark, fooIndex }

          FooEntry {

             fooTimeMark  TimeFilter,

             fooIndex     Integer32,

             fooCounts    Counter32

          }

      Note that entries exist in the time-filtered conceptual table

      only if they actually exist in the underlying (basic) table.

      For this example, the fooTable will have three underlying

      basic entries (fooIndex == 1, 2, and 3), with the following

      activity (for sysUpTime equal 0 to 9):

         - fooEntry.N.1 is created at time '0' and most recently

           updated at time '6' to the value '5'.

         - fooEntry.N.2 is created at time '0' and most recently

           updated at time '8' to the value '9'.

         - fooEntry.N.3 is created at time '3', updated at time '5'

           to the value '17', and deleted at time '7'.

     The following tables show the values that would be returned for

     MIB walk operations with various TimeFilter values, done at

     different times.  An application issues a retrieval request at

     time 'T', with a TimeFilter value, 'N' (typically set to a lower

     value, such as the value of sysUpTime at the last polling cycle).

     The following values would be returned in a MIB walk of

     fooCounts.N if T equals '0' and N equals '0':

           fooCounts.N.I    Value

           ==========================

           fooCounts.0.1    0

           fooCounts.0.2    0

       Note that nothing is returned for fooCounts.0.3, since that

       entry does not exist at sysUpTime equals '0'.

     The following values would be returned in a full (traditional) MIB

     walk of fooCounts.N if T equals '3' and N equals '0':

           fooCounts.N.I    Value

           =======================

           fooCounts.0.1    0

           fooCounts.0.2    0

           fooCounts.0.3    0

           fooCounts.1.3    0

           fooCounts.2.3    0

           fooCounts.3.3    0

       Note that there are no instances for T equals 1 or 2 for the

       first two values of N, as these entries did not change

       since they were created at time '0'.

       Note that the current value for 'fooCounts.N.3' is returned

       here, even for values of N less than '3' (when the entry was

       created).  The agent only considers the current existence of an

       entry in the TimeFilter algorithm, not the time when the entry

       was created.

       Note that the instances 'fooCounts.0.3', 'fooCounts.1.3',

       and 'fooCounts.2.3' are duplicates and can be suppressed by the

       agent in a MIB walk.

     The following values would be returned in a full (traditional)

     MIB walk of fooCounts.N if T equals '6' and N equals '3':

           fooCounts.N.I    Value

           =======================

           fooCounts.3.1    5

           fooCounts.3.3    17

           fooCounts.4.1    5

           fooCounts.4.3    17

           fooCounts.5.1    5

           fooCounts.5.3    17

           fooCounts.6.1    5

        Note that no instances for entry 'fooCounts.N.2' are returned,

        since it has not changed since time '3'.

        Note that all instances except 'fooCounts.5.3' and

        'fooCounts.6.1' are duplicates and can be suppressed by the

        agent in a MIB walk.

     The following values would be returned in a full (traditional)

     MIB walk of fooCounts.N if T equals '9' and N equals '6':

           fooCounts.N.I    Value

           =======================

           fooCounts.6.1    5

           fooCounts.6.2    9

           fooCounts.7.2    9

           fooCounts.8.2    9

        Note that no instances for entry 'fooCounts.N.3' are returned,

        since it was deleted at time '7'.

        Note that instances 'fooCounts.6.2' and 'fooCounts.7.2'

        are duplicates and can be suppressed by the agent in a MIB

        walk."

  SYNTAX    TimeTicks

DataSource ::= TEXTUAL-CONVENTION

    STATUS        current

    DESCRIPTION

        "Identifies the source of the data that the associated

        function is configured to analyze.  This source can be any

        interface on this device.

        In order to identify a particular interface, this

        object shall identify the instance of the ifIndex

        object, defined in [RFC2863], for the desired interface.

        For example, if an entry were to receive data from

        interface #1, this object would be set to ifIndex.1."

    SYNTAX      OBJECT IDENTIFIER

--

-- Protocol Directory Group

--

-- Lists the inventory of protocols the probe has the capability of

-- monitoring and allows the addition, deletion, and configuration of

-- entries in this list.

protocolDirLastChange OBJECT-TYPE

    SYNTAX      TimeStamp

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION

        "The value of sysUpTime at the time the protocol directory

        was last modified, either through insertions or deletions,

        or through modifications of the

        protocolDirAddressMapConfig, protocolDirHostConfig, or

        protocolDirMatrixConfig."

    ::= { protocolDir 1 }

protocolDirTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF ProtocolDirEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "This table lists the protocols that this agent has the

        capability to decode and count.  There is one entry in this

        table for each such protocol.  These protocols represent

        different network-layer, transport-layer, and higher-layer

        protocols.  The agent should boot up with this table

        preconfigured with those protocols that it knows about and

        wishes to monitor.  Implementations are strongly encouraged to

        support protocols higher than the network layer (at least for

        the protocol distribution group), even for implementations

        that don't support the application-layer groups."

    ::= { protocolDir 2 }

protocolDirEntry OBJECT-TYPE

    SYNTAX      ProtocolDirEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A conceptual row in the protocolDirTable.

         An example of the indexing of this entry is

         protocolDirLocalIndex.8.0.0.0.1.0.0.8.0.2.0.0, which is the

         encoding of a length of 8, followed by 8 subids encoding the

         protocolDirID of 1.2048, followed by a length of 2 and the

         2 subids encoding zero-valued parameters.

         Note that some combinations of index values may result in an

         index that exceeds 128 sub-identifiers in length, which exceeds

         the maximum for the SNMP protocol.  Implementations should take

         care to avoid such combinations."

    INDEX { protocolDirID, protocolDirParameters }

    ::= { protocolDirTable  1 }

ProtocolDirEntry ::= SEQUENCE {

    protocolDirID                   OCTET STRING,

    protocolDirParameters           OCTET STRING,

    protocolDirLocalIndex           Integer32,

    protocolDirDescr                DisplayString,

    protocolDirType                 BITS,

    protocolDirAddressMapConfig     INTEGER,

    protocolDirHostConfig           INTEGER,

    protocolDirMatrixConfig         INTEGER,

    protocolDirOwner                OwnerString,

    protocolDirStatus               RowStatus

}

protocolDirID OBJECT-TYPE

    SYNTAX      OCTET STRING  (SIZE (4..128))

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A unique identifier for a particular protocol.  Standard

        identifiers will be defined in such a manner that they

        can often be used as specifications for new protocols - i.e.,

        a tree-structured assignment mechanism that matches the

        protocol encapsulation 'tree' and that has algorithmic

        assignment mechanisms for certain subtrees.  See RFC 2074 for

        more details.

        Despite the algorithmic mechanism, the probe will only place

        entries in here for those protocols it chooses to collect.  In

        other words, it need not populate this table with all

        possible ethernet protocol types, nor need it create them on

        the fly when it sees them.  Whether it does these

        things is a matter of product definition (cost/benefit,

        usability) and is up to the designer of the product.

        If an entry is written to this table with a protocolDirID that

        the agent doesn't understand, either directly or

        algorithmically, the SET request will be rejected with an

        inconsistentName or badValue (for SNMPv1) error."

    ::= { protocolDirEntry 1 }

protocolDirParameters OBJECT-TYPE

    SYNTAX      OCTET STRING (SIZE (1..32))

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A set of parameters for the associated protocolDirID.

        See the associated RMON2 Protocol Identifiers document

        for a description of the possible parameters.  There

        will be one octet in this string for each sub-identifier in

        the protocolDirID, and the parameters will appear here in the

        same order as the associated sub-identifiers appear in the

        protocolDirID.

        Every node in the protocolDirID tree has a different, optional

        set of parameters defined (that is, the definition of

        parameters for a node is optional).  The proper parameter

        value for each node is included in this string.  Note that the

        inclusion of a parameter value in this string for each node is

        not optional.  What is optional is that a node may have no

        parameters defined, in which case the parameter field for that

        node will be zero."

    ::= { protocolDirEntry 2 }

protocolDirLocalIndex OBJECT-TYPE

    SYNTAX      Integer32 (1..2147483647)

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION

        "The locally arbitrary but unique identifier associated

        with this protocolDir entry.

        The value for each supported protocol must remain constant at

        least from one re-initialization of the entity's network

        management system to the next re-initialization, except that

        if a protocol is deleted and re-created, it must be re-created

        with a new value that has not been used since the last

        re-initialization.

        The specific value is meaningful only within a given SNMP

        entity.  A protocolDirLocalIndex must not be re-used until the

        next agent restart in the event that the protocol directory

        entry is deleted."

    ::= { protocolDirEntry 3 }

protocolDirDescr OBJECT-TYPE

    SYNTAX      DisplayString (SIZE (1..64))

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "A textual description of the protocol encapsulation.

        A probe may choose to describe only a subset of the

        entire encapsulation (e.g., only the highest layer).

        This object is intended for human consumption only.

        This object may not be modified if the associated

        protocolDirStatus object is equal to active(1)."

    ::= { protocolDirEntry 4 }

protocolDirType OBJECT-TYPE

    SYNTAX      BITS {

                    extensible(0),

                    addressRecognitionCapable(1)

                }

    MAX-ACCESS  read-only

    STATUS      current

    DESCRIPTION

        "This object describes 2 attributes of this protocol

         directory entry.

         The presence or absence of the 'extensible' bit describes

         whether this protocol directory entry can be extended

         by the user by creating protocol directory entries that are

         children of this protocol.

         An example of an entry that will often allow extensibility is

         'ip.udp'.  The probe may automatically populate some children

         of this node, such as 'ip.udp.snmp' and 'ip.udp.dns'.

         A probe administrator or user may also populate additional

         children via remote SNMP requests that create entries in this

         table.  When a child node is added for a protocol for which the

         probe has no built-in support extending a parent node (for

         which the probe does have built-in support),

         that child node is not extendable.  This is termed 'limited

         extensibility'.

         When a child node is added through this extensibility

         mechanism, the values of protocolDirLocalIndex and

         protocolDirType shall be assigned by the agent.

         The other objects in the entry will be assigned by the

         manager who is creating the new entry.

         This object also describes whether this agent can

         recognize addresses for this protocol, should it be a

         network-level protocol.  That is, while a probe may be able

         to recognize packets of a particular network-layer protocol

         and count them, it takes additional logic to be able to

         recognize the addresses in this protocol and to populate

         network-layer or application-layer tables with the addresses

         in this protocol.  If this bit is set, the agent will

         recognize network-layer addresses for this protocol and

         populate the network- and application-layer host and matrix

         tables with these protocols.

         Note that when an entry is created, the agent will supply

         values for the bits that match the capabilities of the agent

         with respect to this protocol.  Note that since row creations

         usually exercise the limited extensibility feature, these

         bits will usually be set to zero."

    ::= { protocolDirEntry 5 }

protocolDirAddressMapConfig OBJECT-TYPE

    SYNTAX      INTEGER {

                    notSupported(1),

                    supportedOff(2),

                    supportedOn(3)

                }

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "This object describes and configures the probe's support for

        address mapping for this protocol.  When the probe creates

        entries in this table for all protocols that it understands,

        it will set the entry to notSupported(1) if it doesn't have

        the capability to perform address mapping for the protocol or

        if this protocol is not a network-layer protocol.  When

        an entry is created in this table by a management operation as

        part of the limited extensibility feature, the probe must set

        this value to notSupported(1), because limited extensibility

        of the protocolDirTable does not extend to interpreting

        addresses of the extended protocols.

        If the value of this object is notSupported(1), the probe

        will not perform address mapping for this protocol and

        shall not allow this object to be changed to any other value.

        If the value of this object is supportedOn(3), the probe

        supports address mapping for this protocol and is configured

        to perform address mapping for this protocol for all

        addressMappingControlEntries and all interfaces.

        If the value of this object is supportedOff(2), the probe

        supports address mapping for this protocol but is configured

        to not perform address mapping for this protocol for any

        addressMappingControlEntries and all interfaces.

        Whenever this value changes from supportedOn(3) to

        supportedOff(2), the probe shall delete all related entries in

        the addressMappingTable."

    ::= { protocolDirEntry 6 }

protocolDirHostConfig OBJECT-TYPE

    SYNTAX      INTEGER {

                    notSupported(1),

                    supportedOff(2),

                    supportedOn(3)

                }

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "This object describes and configures the probe's support for

        the network-layer and application-layer host tables for this

        protocol.  When the probe creates entries in this table for

        all protocols that it understands, it will set the entry to

        notSupported(1) if it doesn't have the capability to track the

        nlHostTable for this protocol or if the alHostTable is

        implemented but doesn't have the capability to track this

        protocol.  Note that if the alHostTable is implemented, the

        probe may only support a protocol if it is supported in both

        the nlHostTable and the alHostTable.

        If the associated protocolDirType object has the

        addressRecognitionCapable bit set, then this is a network-

        layer protocol for which the probe recognizes addresses, and

        thus the probe will populate the nlHostTable and alHostTable

        with addresses it discovers for this protocol.

        If the value of this object is notSupported(1), the probe

        will not track the nlHostTable or alHostTable for this

        protocol and shall not allow this object to be changed to any

        other value.  If the value of this object is supportedOn(3),

        the probe supports tracking of the nlHostTable and alHostTable

        for this protocol and is configured to track both tables

        for this protocol for all control entries and all interfaces.

        If the value of this object is supportedOff(2), the probe

        supports tracking of the nlHostTable and alHostTable for this

        protocol but is configured to not track these tables

        for any control entries or interfaces.

        Whenever this value changes from supportedOn(3) to

        supportedOff(2), the probe shall delete all related entries in

        the nlHostTable and alHostTable.

        Note that since each alHostEntry references 2 protocol

        directory entries, one for the network address and one for the

        type of the highest protocol recognized, an entry will

        only be created in that table if this value is supportedOn(3)

        for both protocols."

    ::= { protocolDirEntry 7 }

protocolDirMatrixConfig OBJECT-TYPE

    SYNTAX      INTEGER {

                    notSupported(1),

                    supportedOff(2),

                    supportedOn(3)

                }

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "This object describes and configures the probe's support for

        the network-layer and application-layer matrix tables for this

        protocol.  When the probe creates entries in this table for

        all protocols that it understands, it will set the entry to

        notSupported(1) if it doesn't have the capability to track the

        nlMatrixTables for this protocol or if the alMatrixTables are

        implemented but don't have the capability to track this

        protocol.  Note that if the alMatrix tables are implemented,

        the probe may only support a protocol if it is supported in

        both of the nlMatrixTables and both of the

        alMatrixTables.

        If the associated protocolDirType object has the

        addressRecognitionCapable bit set, then this is a network-

        layer protocol for which the probe recognizes addresses, and

        thus the probe will populate both of the nlMatrixTables and

        both of the alMatrixTables with addresses it discovers for

        this protocol.

        If the value of this object is notSupported(1), the probe

        will not track either of the nlMatrixTables or the

        alMatrixTables for this protocol and shall not allow this

        object to be changed to any other value.  If the value of this

        object is supportedOn(3), the probe supports tracking of both

        of the nlMatrixTables and (if implemented) both of the

        alMatrixTables for this protocol and is configured to track

        these tables for this protocol for all control entries and all

        interfaces.  If the value of this object is supportedOff(2),

        the probe supports tracking of both of the nlMatrixTables and

        (if implemented) both of the alMatrixTables for this protocol

        but is configured to not track these tables for this

        protocol for any control entries or interfaces.

        Whenever this value changes from supportedOn(3) to

        supportedOff(2), the probe shall delete all related entries in

        the nlMatrixTables and the alMatrixTables.

        Note that since each alMatrixEntry references 2 protocol

        directory entries, one for the network address and one for the

        type of the highest protocol recognized, an entry will

        only be created in that table if this value is supportedOn(3)

        for both protocols."

    ::= { protocolDirEntry 8 }

protocolDirOwner OBJECT-TYPE

    SYNTAX      OwnerString

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The entity that configured this entry and is

        therefore using the resources assigned to it."

    ::= { protocolDirEntry 9 }

protocolDirStatus OBJECT-TYPE

    SYNTAX      RowStatus

    MAX-ACCESS  read-create

    STATUS      current

    DESCRIPTION

        "The status of this protocol directory entry.

        An entry may not exist in the active state unless all

        objects in the entry have an appropriate value.

        If this object is not equal to active(1), all associated

        entries in the nlHostTable, nlMatrixSDTable, nlMatrixDSTable,

        alHostTable, alMatrixSDTable, and alMatrixDSTable shall be

        deleted."

    ::= { protocolDirEntry 10 }

--

-- Protocol Distribution Group  (protocolDist)

--

-- Collects the relative amounts of octets and packets for the

-- different protocols detected on a network segment.

--    protocolDistControlTable,

--    protocolDistStatsTable

protocolDistControlTable OBJECT-TYPE

    SYNTAX      SEQUENCE OF ProtocolDistControlEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "Controls the setup of protocol type distribution statistics

        tables.

        Implementations are encouraged to add an entry per monitored

        interface upon initialization so that a default collection

        of protocol statistics is available.

        Rationale:

        This table controls collection of very basic statistics

        for any or all of the protocols detected on a given interface.

        An NMS can use this table to quickly determine bandwidth

        allocation utilized by different protocols.

        A media-specific statistics collection could also

        be configured (e.g., etherStats, trPStats) to easily obtain

        total frame, octet, and droppedEvents for the same

        interface."

    ::= { protocolDist 1 }

protocolDistControlEntry OBJECT-TYPE

    SYNTAX      ProtocolDistControlEntry

    MAX-ACCESS  not-accessible

    STATUS      current

    DESCRIPTION

        "A conceptual row in the protocolDistControlTable.

         An example of the indexing of this entry is

         protocolDistControlDroppedFrames.7"

    INDEX { protocolDistControlIndex }