>> MIB - Management Information Base

>> Table: dot3StatsTable - (.1.3.6.1.2.1.10.7.2.1)

Description: Statistics for a particular interface to an ethernet-like medium.

dot3StatsTable
OIDNameTypeAccess
.1IndexINTEGERR
.2AlignmentErrorsCounterR
.3FCSErrorsCounterR
.4SingleCollisionFramesCounterR
.5MultipleCollisionFramesCounterR
.6SQETestErrorsCounterR
.7DeferredTransmissionsCounterR
.8LateCollisionsCounterR
.9ExcessiveCollisionsCounterR
.10InternalMacTransmitErrorsCounterR
.11CarrierSenseErrorsCounterR
.13FrameTooLongsCounterR
.16InternalMacReceiveErrorsCounterR
.17EtherChipSetOBJECT IDENTIFIERR

Index
An index value that uniquely identifies an
interface to an ethernet-like medium.  The
interface identified by a particular value of
this index is the same interface as identified
by the same value of ifIndex.
AlignmentErrors
A count of frames received on a particular
interface that are not an integral number of
octets in length and do not pass the FCS check.
The count represented by an instance of this
object is incremented when the alignmentError
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC.
FCSErrors
A count of frames received on a particular
interface that are an integral number of octets
in length but do not pass the FCS check.
The count represented by an instance of this
object is incremented when the frameCheckError
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC.
SingleCollisionFrames
A count of successfully transmitted frames on
a particular interface for which transmission
is inhibited by exactly one collision.
A frame that is counted by an instance of this
object is also counted by the corresponding
instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsMultipleCollisionFrames
object.
MultipleCollisionFrames
A count of successfully transmitted frames on
a particular interface for which transmission
is inhibited by more than one collision.
A frame that is counted by an instance of this
object is also counted by the corresponding
instance of either the ifOutUcastPkts,
ifOutMulticastPkts, or ifOutBroadcastPkts,
and is not counted by the corresponding
instance of the dot3StatsSingleCollisionFrames
object.
SQETestErrors
A count of times that the SQE TEST ERROR
message is generated by the PLS sublayer for a
particular interface. The SQE TEST ERROR
message is defined in section 7.2.2.2.4 of
ANSI/IEEE 802.3-1985 and its generation is
described in section 7.2.4.6 of the same
document.
DeferredTransmissions
A count of frames for which the first
transmission attempt on a particular interface
is delayed because the medium is busy.
The count represented by an instance of this
object does not include frames involved in
collisions.
LateCollisions
The number of times that a collision is
detected on a particular interface later than
512 bit-times into the transmission of a
packet.
Five hundred and twelve bit-times corresponds
to 51.2 microseconds on a 10 Mbit/s system. A
(late) collision included in a count
represented by an instance of this object is
also considered as a (generic) collision for
purposes of other collision-related
statistics.
ExcessiveCollisions
A count of frames for which transmission on a
particular interface fails due to excessive
collisions.
InternalMacTransmitErrors
A count of frames for which transmission on a
particular interface fails due to an internal
MAC sublayer transmit error. A frame is only
counted by an instance of this object if it is
not counted by the corresponding instance of
either the dot3StatsLateCollisions object, the
dot3StatsExcessiveCollisions object, or the
dot3StatsCarrierSenseErrors object.
The precise meaning of the count represented by
an instance of this object is implementation-
specific.  In particular, an instance of this
object may represent a count of transmission
errors on a particular interface that are not
otherwise counted.
CarrierSenseErrors
The number of times that the carrier sense
condition was lost or never asserted when
attempting to transmit a frame on a particular
interface.
The count represented by an instance of this
object is incremented at most once per
transmission attempt, even if the carrier sense
condition fluctuates during a transmission
attempt.
FrameTooLongs
A count of frames received on a particular
interface that exceed the maximum permitted
frame size.
The count represented by an instance of this
object is incremented when the frameTooLong
status is returned by the MAC service to the
LLC (or other MAC user). Received frames for
which multiple error conditions obtain are,
according to the conventions of IEEE 802.3
Layer Management, counted exclusively according
to the error status presented to the LLC.
InternalMacReceiveErrors
A count of frames for which reception on a
particular interface fails due to an internal
MAC sublayer receive error. A frame is only
counted by an instance of this object if it is
not counted by the corresponding instance of
either the dot3StatsFrameTooLongs object, the
dot3StatsAlignmentErrors object, or the
dot3StatsFCSErrors object.
The precise meaning of the count represented by
an instance of this object is implementation-
specific.  In particular, an instance of this
object may represent a count of receive errors
on a particular interface that are not
otherwise counted.
EtherChipSet
This object contains an OBJECT IDENTIFIER
which identifies the chipset used to
realize the interface. Ethernet-like
interfaces are typically built out of
several different chips. The MIB implementor
is presented with a decision of which chip
to identify via this object. The implementor
should identify the chip which is usually
called the Medium Access Control chip.
If no such chip is easily identifiable,
the implementor should identify the chip
which actually gathers the transmit
and receive statistics and error
indications. This would allow a
manager station to correlate the
statistics and the chip generating
them, giving it the ability to take
into account any known anomalies
in the chip.


Copyright ©2003 by BinTec Access Networks GmbH
This page was last modified on: 11.03.2003 by Projectmanager Maintenance