A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes.            The approximate minimum time for rollover of this            counter is 81 hours in a 10Mb/s repeater."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.12, aLateEvents."    ::= { rptrMonitorPortEntry 11 }rptrMonitorPortVeryLongEvents OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "For a clause 9 repeater port, this counter            is incremented by one for each CarrierEvent            whose ActivityDuration is greater than the            MAU Jabber Lockup Protection timer TW3            (Ref: 9.6.1 & 9.6.5, IEEE 802.3 Std).            For a clause 27 repeater port, this counter            is incremented by one on entry to the            Rx Jabber state of the receiver timer state            diagram (fig 27-7).  Other counters may            be incremented as appropriate.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.13, aVeryLongEvents."    ::= { rptrMonitorPortEntry 12 }rptrMonitorPortDataRateMismatches OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This counter is incremented by one for each            frame received by this port that meets all            of the conditions required by only one of the            following two measurement methods:            Measurement method A:  1) The CollisionEvent            signal is not asserted (10Mb/s operation) or            the Collision Count Increment state of the            partition state diagram (fig 27-8 of            [IEEE 802.3 Std]) has not been entered            (100Mb/s operation).  2) The ActivityDuration            is greater than ValidPacketMinTime.  3) The            frequency (data rate) is detectably mismatched            from the local transmit frequency.            Measurement method B:  1) The CollisionEvent            signal is not asserted (10Mb/s operation)            or the Collision Count Increment state of the            partition state diagram (fig 27-8 of            [IEEE 802.3 Std]) has not been entered            (100Mb/s operation).  2) The OctetCount is            greater than 63.  3) The frequency (data            rate) is detectably mismatched from the local            transmit frequency.  The exact degree of            mismatch is vendor specific and is to be            defined by the vendor for conformance testing.            When this event occurs, other counters whose            increment conditions were satisfied may or may not            also be incremented, at the implementor's            discretion.  Whether or not the repeater was able            to maintain data integrity is beyond the scope of            this standard.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.14, aDataRateMismatches."    ::= { rptrMonitorPortEntry 13 }rptrMonitorPortAutoPartitions OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This counter is incremented by one for            each time the repeater has automatically            partitioned this port.            The conditions that cause a clause 9            repeater port to partition are specified in            the partition state diagram in clause 9 of            [IEEE 802.3 Std].  They are not differentiated            here.  A clause 27 repeater port partitions            on entry to the Partition Wait state of the            partition state diagram (fig 27-8 in            [IEEE 802.3 Std]).            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.15, aAutoPartitions."    ::= { rptrMonitorPortEntry 14 }rptrMonitorPortTotalErrors OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The total number of errors which have occurred on            this port.  This counter is the summation of the            values of other error counters (for the same            port), namely:                rptrMonitorPortFCSErrors,                rptrMonitorPortAlignmentErrors,                rptrMonitorPortFrameTooLongs,                rptrMonitorPortShortEvents,                rptrMonitorPortLateEvents,                rptrMonitorPortVeryLongEvents,                rptrMonitorPortDataRateMismatches, and                rptrMonitorPortSymbolErrors.            This counter is redundant in the sense that it is            the summation of information already available            through other objects.  However, it is included            specifically because the regular retrieval of this            object as a means of tracking the health of a port            provides a considerable optimization of network            management traffic over the otherwise necessary            retrieval of the summed counters.            Note that rptrMonitorPortRunts is not included            in this total; this is because runts usually            indicate collision fragments, a normal network            event.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    ::= { rptrMonitorPortEntry 15 }rptrMonitorPortLastChange OBJECT-TYPE    SYNTAX      TimeStamp    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "The value of sysUpTime when the last of            the following occurred:              1) the agent cold- or warm-started;              2) the row for the port was created                 (such as when a device or module was added                  to the system); or              3) any condition that would cause one of                 the counters for the row to experience                 a discontinuity."    ::= { rptrMonitorPortEntry 16 }rptrMonitor100PortTable OBJECT-TYPE    SYNTAX      SEQUENCE OF RptrMonitor100PortEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "Table of additional performance and error            statistics for 100Mb/s ports, above and            beyond those parameters that apply to both            10 and 100Mbps ports.  Entries exist only for            ports attached to 100Mbps repeaters.            The columnar object rptrMonitorPortLastChange            is used to indicate possible discontinuities            of counter type columnar objects in this table."    ::= { rptrMonitorPortInfo 2 }rptrMonitor100PortEntry OBJECT-TYPE    SYNTAX      RptrMonitor100PortEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "An entry in the table, containing performance            and error statistics for a single 100Mb/s port."    INDEX    { rptrMonitorPortGroupIndex, rptrMonitorPortIndex }    ::= { rptrMonitor100PortTable 1 }RptrMonitor100PortEntry ::=    SEQUENCE {        rptrMonitorPortIsolates            Counter32,        rptrMonitorPortSymbolErrors            Counter32,        rptrMonitorPortUpper32Octets            Counter32,        rptrMonitorPortHCReadableOctets            Counter64    }rptrMonitorPortIsolates OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This counter is incremented by one each time that            the repeater port automatically isolates as a            consequence of false carrier events.  The conditions            which cause a port to automatically isolate are            defined by the transition from the False Carrier            state to the Link Unstable state of the carrier            integrity state diagram (figure 27-9)            [IEEE 802.3 Standard].            Note:  Isolates do not affect the value of            the PortOperStatus object.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.16, aIsolates."    ::= { rptrMonitor100PortEntry 1 }rptrMonitorPortSymbolErrors OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This counter is incremented by one each time when            valid length packet was received at the port and            there was at least one occurrence of an invalid            data symbol. This can increment only once per valid            carrier event. A collision presence at any port of            the repeater containing port N, will not cause this            attribute to increment.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes.            The approximate minimum time for rollover of this            counter is 7.4 hours at 100Mb/s."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.17,            aSymbolErrorDuringPacket."    ::= { rptrMonitor100PortEntry 2 }rptrMonitorPortUpper32Octets OBJECT-TYPE    SYNTAX      Counter32    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This object is the number of octets contained in            valid frames that have been received on this port,            modulo 2**32.  That is, it contains the upper 32            bits of a 64-bit octets counter, of which the            lower 32 bits are contained in the            rptrMonitorPortReadableOctets object.            This two-counter mechanism is provided for those            network management protocols that do not support            64-bit counters (e.g. SNMP V1) and are used to            manage a repeater type of 100Mb/s.            Conformance clauses for this MIB are defined such            that implementation of this object is not required            in a system which does not support 100Mb/s.            However, systems with mixed 10 and 100Mb/s ports            may implement this object across all ports,            including 10Mb/s.  If this object is implemented,            it must be according to the definition in the first            paragraph of this description; that is, the value            of this object MUST be a valid count.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    ::= { rptrMonitor100PortEntry 3 }rptrMonitorPortHCReadableOctets OBJECT-TYPE    SYNTAX      Counter64    MAX-ACCESS  read-only    STATUS      current    DESCRIPTION            "This object is the number of octets contained in            valid frames that have been received on this port.            This counter is incremented by OctetCount for each            frame received on this port which has been            determined to be a readable frame (i.e., including            FCS octets but excluding framing bits and dribble            bits).            This statistic provides an indicator of the total            data transferred.            This counter is a 64-bit version of rptrMonitor-            PortReadableOctets. It should be used by network            management protocols which suppport 64-bit counters            (e.g. SNMPv2).            Conformance clauses for this MIB are defined such            that implementation of this object is not required            in a system which does not support 100Mb/s.            However, systems with mixed 10 and 100Mb/s ports            may implement this object across all ports,            including 10Mb/s.  If this object is implemented,            it must be according to the definition in the first            paragraph of this description; that is, the value            of this object MUST be a valid count.            A discontinuity may occur in the value            when the value of object            rptrMonitorPortLastChange changes."    REFERENCE            "[IEEE 802.3 Mgt], 30.4.3.1.5, aReadableOctets."    ::= { rptrMonitor100PortEntry 4 }-- New version of statistics at the repeater level.---- Statistics objects for each managed repeater-- in the system.rptrMonTable OBJECT-TYPE    SYNTAX      SEQUENCE OF RptrMonEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "A table of information about each            non-trivial repeater.  The number of entries            in this table is the same as the number of            entries in the rptrInfoTable.            The columnar object rptrInfoLastChange is            used to indicate possible discontinuities of            counter type columnar objects in this table."    ::= { rptrMonitorAllRptrInfo 1 }rptrMonEntry OBJECT-TYPE    SYNTAX      RptrMonEntry    MAX-ACCESS  not-accessible    STATUS      current    DESCRIPTION            "An entry in the table, containing information            about a single non-trivial repeater."    INDEX    { rptrInfoId }    ::= { rptrMonTable 1 }RptrMonEntry ::=    SEQUENCE {        rptrMonTxCollisions            Counter32,