For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol
when a valid carrier was present.
For an interface operating in half-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than slotTime, and
during which there was at least one occurrence
of an event that causes the PHY to indicate
'Data reception error' or 'carrier extend error'
on the GMII.
For an interface operating in full-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than minFrameSize,
and during which there was at least one
occurrence of an event that causes the PHY to
indicate 'Data reception error' on the GMII.
For an interface operating at 10 Gb/s, the
number of times the receiving media is non-idle
(a carrier event) for a period of time equal to
or greater than minFrameSize, and during which
there was at least one occurrence of an event
that causes the PHY to indicate 'Receive Error'
on the XGMII.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event. This count does
not increment if a collision is present.
This counter does not increment when the
interface is operating at 10 Mb/s.
For interfaces operating at 10 Gb/s, this
counter can roll over in less than 5 minutes if
it is incrementing at its maximum rate. Since
that amount of time could be less than a
management station's poll cycle time, in order
to avoid a loss of information, a management
station is advised to poll the
dot3HCStatsSymbolErrors object for 10 Gb/s
or faster interfaces.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime.
Parsed from file EtherLike-MIB.mib
Module: EtherLike-MIB
For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol
when a valid carrier was present.
For an interface operating in half-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than slotTime, and
during which there was at least one occurrence
of an event that causes the PHY to indicate
'Data reception error' or 'carrier extend error'
on the GMII.
For an interface operating in full-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than minFrameSize,
and during which there was at least one
occurrence of an event that causes the PHY to
indicate 'Data reception error' on the GMII.
For an interface operating at 10 Gb/s, the
number of times the receiving media is non-idle
(a carrier event) for a period of time equal to
or greater than minFrameSize, and during which
there was at least one occurrence of an event
that causes the PHY to indicate 'Receive Error'
on the XGMII.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event. This count does
not increment if a collision is present.
This counter does not increment when the
interface is operating at 10 Mb/s.
For interfaces operating at 10 Gb/s, this
counter can roll over in less than 5 minutes if
it is incrementing at its maximum rate. Since
that amount of time could be less than a
management station's poll cycle time, in order
to avoid a loss of information, a management
station is advised to poll the
dot3HCStatsSymbolErrors object for 10 Gb/s
or faster interfaces.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime.
dot3StatsSymbolErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION "For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol
when a valid carrier was present.
For an interface operating in half-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than slotTime, and
during which there was at least one occurrence
of an event that causes the PHY to indicate
Data reception error or carrier extend error
on the GMII.
For an interface operating in full-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle a carrier event) for a period
of time equal to or greater than minFrameSize,
and during which there was at least one
occurrence of an event that causes the PHY to
indicate Data reception error on the GMII.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event. This count does
not increment if a collision is present.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime."
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5,
aSymbolErrorDuringCarrier."
View at oid-info.com
For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol
when a valid carrier was present.
For an interface operating in half-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than slotTime, and
during which there was at least one occurrence
of an event that causes the PHY to indicate
'Data reception error' or 'carrier extend error'
on the GMII.
For an interface operating in full-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle a carrier event) for a period
of time equal to or greater than minFrameSize,
and during which there was at least one
occurrence of an event that causes the PHY to
indicate 'Data reception error' on the GMII.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event. This count does
not increment if a collision is present.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime.
Parsed from file rfc1643.mib.txt
Company: None
Module: EtherLike-MIB
For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol
when a valid carrier was present.
For an interface operating in half-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than slotTime, and
during which there was at least one occurrence
of an event that causes the PHY to indicate
'Data reception error' or 'carrier extend error'
on the GMII.
For an interface operating in full-duplex mode
at 1000 Mb/s, the number of times the receiving
media is non-idle (a carrier event) for a period
of time equal to or greater than minFrameSize,
and during which there was at least one
occurrence of an event that causes the PHY to
indicate 'Data reception error' on the GMII.
For an interface operating at 10 Gb/s, the
number of times the receiving media is non-idle
(a carrier event) for a period of time equal to
or greater than minFrameSize, and during which
there was at least one occurrence of an event
that causes the PHY to indicate 'Receive Error'
on the XGMII.
The count represented by an instance of this
object is incremented at most once per carrier
event, even if multiple symbol errors occur
during the carrier event. This count does
not increment if a collision is present.
This counter does not increment when the
interface is operating at 10 Mb/s.
For interfaces operating at 10 Gb/s, this
counter can roll over in less than 5 minutes if
it is incrementing at its maximum rate. Since
that amount of time could be less than a
management station's poll cycle time, in order
to avoid a loss of information, a management
station is advised to poll the
dot3HCStatsSymbolErrors object for 10 Gb/s
or faster interfaces.
Discontinuities in the value of this counter can
occur at re-initialization of the management
system, and at other times as indicated by the
value of ifCounterDiscontinuityTime.
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. This counter does not increment when the interface is operating at 10 Mb/s. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsSymbolErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, aSymbolErrorDuringCarrier." ::= { dot3StatsEntry 18 }
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter ACCESS read-only STATUS mandatory DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. This counter does not increment when the interface is operating at 10 Mb/s. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsSymbolErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, aSymbolErrorDuringCarrier." ::= { dot3StatsEntry 18 }
Automatically extracted from RFC2665
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, aSymbolErrorDuringCarrier." ::= { dot3StatsEntry 18 }
dot3StatsSymbolErrors OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "For an interface operating at 100 Mb/s, the number of times there was an invalid data symbol when a valid carrier was present. For an interface operating in half-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than slotTime, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' or 'carrier extend error' on the GMII. For an interface operating in full-duplex mode at 1000 Mb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Data reception error' on the GMII. For an interface operating at 10 Gb/s, the number of times the receiving media is non-idle (a carrier event) for a period of time equal to or greater than minFrameSize, and during which there was at least one occurrence of an event that causes the PHY to indicate 'Receive Error' on the XGMII. The count represented by an instance of this object is incremented at most once per carrier event, even if multiple symbol errors occur during the carrier event. This count does not increment if a collision is present. This counter does not increment when the interface is operating at 10 Mb/s. For interfaces operating at 10 Gb/s, this counter can roll over in less than 5 minutes if it is incrementing at its maximum rate. Since that amount of time could be less than a management station's poll cycle time, in order to avoid a loss of information, a management station is advised to poll the dot3HCStatsSymbolErrors object for 10 Gb/s or faster interfaces. Discontinuities in the value of this counter can occur at re-initialization of the management system, and at other times as indicated by the value of ifCounterDiscontinuityTime." REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, aSymbolErrorDuringCarrier." ::= { dot3StatsEntry 18 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.10.7.2.1.1 | dot3StatsIndex | 5 | 5 | An index value that uniquely identifies an interface to an ethernet-like medium. The interface identified by a particular value … |
1.3.6.1.2.1.10.7.2.1.2 | dot3StatsAlignmentErrors | 0 | 0 | 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 … |
1.3.6.1.2.1.10.7.2.1.3 | dot3StatsFCSErrors | 0 | 0 | A count of frames received on a particular interface that are an integral number of octets in length but do not pass the FCS chec… |
1.3.6.1.2.1.10.7.2.1.4 | dot3StatsSingleCollisionFrames | 0 | 0 | A count of successfully transmitted frames on a particular interface for which transmission is inhibited by exactly one collision… |
1.3.6.1.2.1.10.7.2.1.5 | dot3StatsMultipleCollisionFrames | 0 | 0 | A count of successfully transmitted frames on a particular interface for which transmission is inhibited by more than one collisi… |
1.3.6.1.2.1.10.7.2.1.6 | dot3StatsSQETestErrors | 0 | 0 | A count of times that the SQE TEST ERROR message is generated by the PLS sublayer for a particular interface. The SQE TEST ERROR … |
1.3.6.1.2.1.10.7.2.1.7 | dot3StatsDeferredTransmissions | 0 | 0 | A count of frames for which the first transmission attempt on a particular interface is delayed because the medium is busy. The co… |
1.3.6.1.2.1.10.7.2.1.8 | dot3StatsLateCollisions | 0 | 0 | The number of times that a collision is detected on a particular interface later than 512 bit-times into the transmission of a pa… |
1.3.6.1.2.1.10.7.2.1.9 | dot3StatsExcessiveCollisions | 0 | 0 | A count of frames for which transmission on a particular interface fails due to excessive collisions. |
1.3.6.1.2.1.10.7.2.1.10 | dot3StatsInternalMacTransmitErrors | 0 | 0 | A count of frames for which transmission on a particular interface fails due to an internal MAC sublayer transmit error. A frame … |
1.3.6.1.2.1.10.7.2.1.11 | dot3StatsCarrierSenseErrors | 0 | 0 | The number of times that the carrier sense condition was lost or never asserted when attempting to transmit a frame on a particul… |
1.3.6.1.2.1.10.7.2.1.12 | dot3StatsExcessiveDeferrals, dot3StatsFiller12 | 0 | 0 | A count of frames for which transmission on a particular interface is deferred for an excessive period of time. |
1.3.6.1.2.1.10.7.2.1.13 | dot3StatsFrameTooLongs | 0 | 0 | A count of frames received on a particular interface that exceed the maximum permitted frame size. The count represented by an ins… |
1.3.6.1.2.1.10.7.2.1.14 | dot3StatsInRangeLengthErrors, dot3StatsFiller14 | 0 | 0 | A count of frames received on a particular interface with a length field value that falls between the minimum unpadded LLC data s… |
1.3.6.1.2.1.10.7.2.1.15 | dot3StatsOutOfRangeLengthFields, dot3StatsFiller15 | 0 | 0 | A count of frames received on a particular interface for which the length field value exceeds the maximum allowed LLC data size. T… |
1.3.6.1.2.1.10.7.2.1.16 | dot3StatsInternalMacReceiveErrors | 0 | 0 | A count of frames for which reception on a particular interface fails due to an internal MAC sublayer receive error. A frame is o… |
1.3.6.1.2.1.10.7.2.1.17 | dot3StatsEtherChipSet | 1 | 1 | This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are… |
1.3.6.1.2.1.10.7.2.1.19 | dot3StatsDuplexStatus | 0 | 0 | The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Manage… |
1.3.6.1.2.1.10.7.2.1.20 | dot3StatsRateControlAbility | 0 | 0 | 'true' for interfaces operating at speeds above 1000 Mb/s that support Rate Control through lowering the average data rate of the… |
1.3.6.1.2.1.10.7.2.1.21 | dot3StatsRateControlStatus | 0 | 0 | The current Rate Control mode of operation of the MAC sublayer of this interface. |