Reference record for OID 1.3.6.1.4.1.278.108.1.23.1.1.17

Parent
1.3.6.1.4.1.278.108.1.23.1.1 (statisticsChartEntry)
Node code
17
Node name
statisEtherCollisions
Numeric OID
1.3.6.1.4.1.278.108.1.23.1.1.17
URN notation
urn:oid:1.3.6.1.4.1.278.108.1.23.1.1.17
ASN.1 notation

{1 3 6 1 4 1 278 108 1 23 1 1 17}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) hitachi-cable(278) aplgs-series(108) aplgs(1) sysStatistics(23) statisticsChartTable(1) statisticsChartEntry(1) statisEtherCollisions(17)}
OID-IRI notation
  • /1/3/6/1/4/1/278/108/1/23/1/1/17
  • /ISO/Identified-Organization/6/1/4/1/278/108/1/23/1/1/17
  • /ISO/3/6/1/4/1/278/108/1/23/1/1/17
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/enterprise/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/enterprise/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/enterprises/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/enterprises/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/vendor-objects/278/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • /iso/org/dod/internet/private/vendor-objects/hitachi-cable/aplgs-series/aplgs/sysStatistics/statisticsChartTable/statisticsChartEntry/statisEtherCollisions
  • Additional combinations skipped.

Descriptions

statisEtherCollisions — APRESIA official small-business switch MIB packages

The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.

Source records

statisEtherCollisions

Status in source: current.

Names: statisEtherCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "statisEtherCollisions",
    "OBJECT-TYPE",
    "SYNTAX",
    "Counter32",
    "UNITS",
    [
      "literal",
      "22436f6c6c6973696f6e7322"
    ],
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected.\"",
    "::=",
    "{",
    "statisticsChartEntry",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Counter32"
    ],
    [
      "UNITS",
      "Collisions"
    ],
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the location of the RMON probe. Section 8.2.1.3 (10BASE-5) and section 10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a station must detect a collision, in the receive mode, if three or more stations are transmitting simultaneously. A repeater port must detect a collision when two or more stations are transmitting simultaneously. Thus a probe placed on a repeater port could record more collisions than a probe connected to a station on the same segment would. Probe location plays a much smaller role when considering 10BASE-T. 14.2.1.4 (10BASE-T) of IEEE standard 802.3 defines a collision as the simultaneous presence of signals on the DO and RD circuits (transmitting and receiving at the same time). A 10BASE-T station can only detect collisions when it is transmitting. Thus probes placed on a station and a repeater, should report the same number of collisions. Note also that an RMON probe inside a repeater should ideally report collisions between the repeater and one or more other hosts (transmit collisions as defined by IEEE 802.3k) plus receiver collisions observed on any coax segments to which the repeater is connected."
    ],
    null,
    null,
    null,
    null
  ]
}
  • APRESIA official small-business switch MIB packages · Publisher's source file: Source package: ApresiaLightGS-mibs_13.zip

    Module: ApresiaLightGS-Series

    Published definition
    statisEtherCollisions OBJECT-TYPE
         SYNTAX     Counter32
         UNITS      "Collisions"
         MAX-ACCESS read-only
         STATUS     current
         DESCRIPTION
             "The best estimate of the total number of collisions
             on this Ethernet segment.
    
             The value returned will depend on the location of the
             RMON probe. Section 8.2.1.3 (10BASE-5) and section
             10.3.1.3 (10BASE-2) of IEEE standard 802.3 states that a
             station must detect a collision, in the receive mode, if
             three or more stations are transmitting simultaneously.  A
             repeater port must detect a collision when two or more
    
             stations are transmitting simultaneously.  Thus a probe
             placed on a repeater port could record more collisions
             than a probe connected to a station on the same segment
             would.
    
             Probe location plays a much smaller role when considering
             10BASE-T.  14.2.1.4 (10BASE-T) of IEEE standard 802.3
             defines a collision as the simultaneous presence of signals
             on the DO and RD circuits (transmitting and receiving
             at the same time).  A 10BASE-T station can only detect
             collisions when it is transmitting.  Thus probes placed on
             a station and a repeater, should report the same number of
             collisions.
    
             Note also that an RMON probe inside a repeater should
             ideally report collisions between the repeater and one or
             more other hosts (transmit collisions as defined by IEEE
             802.3k) plus receiver collisions observed on any coax
             segments to which the repeater is connected."
         ::= { statisticsChartEntry 17 }
    Module imports
    {'IF-MIB': ['InterfaceIndex', 'InterfaceIndexOrZero'], 'SNMPv2-TC': ['RowStatus', 'TruthValue', 'DisplayString', 'TEXTUAL-CONVENTION', 'MacAddress', 'TimeStamp', 'DateAndTime', 'TimeInterval'], 'BRIDGE-MIB': ['dot1dBridge', 'dot1dBasePortEntry', 'dot1dBasePort'], 'SNMPv2-SMI': ['MODULE-IDENTITY', 'OBJECT-TYPE', 'NOTIFICATION-TYPE', 'Gauge32', 'enterprises', 'IpAddress', 'Integer32', 'Unsigned32', 'TimeTicks', 'Counter32'], 'INET-ADDRESS-MIB': ['InetAddressType', 'InetAddress', 'InetAddressPrefixLength', 'InetScopeType'], 'SNMP-FRAMEWORK-MIB': ['SnmpAdminString', 'SnmpEngineID', 'SnmpSecurityLevel']}
    · Download APRESIA official MIB — ApresiaLightGS-mibs_13.zip / ApresiaLightGS-mibs.mib

    Related source files and packages:


    Source location: ApresiaLightGS-Series::statisEtherCollisions.
    Source version and references

    Downloaded: 2026-11-03T01:07:37.136046+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.278)

Asai Takahiro

Siblings (24)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.278.108.1.23.1.1.1 statisIndex00
1.3.6.1.4.1.278.108.1.23.1.1.2 statisInOctets00
1.3.6.1.4.1.278.108.1.23.1.1.3 statisInUcastPkts00
1.3.6.1.4.1.278.108.1.23.1.1.4 statisInNUcastPkts00
1.3.6.1.4.1.278.108.1.23.1.1.5 statisInDiscards00
1.3.6.1.4.1.278.108.1.23.1.1.6 statisInErrors00
1.3.6.1.4.1.278.108.1.23.1.1.7 statisOutOctets00
1.3.6.1.4.1.278.108.1.23.1.1.8 statisOutUcastPkts00
1.3.6.1.4.1.278.108.1.23.1.1.9 statisOutNUcastPkts00
1.3.6.1.4.1.278.108.1.23.1.1.10 statisOutDiscards00
1.3.6.1.4.1.278.108.1.23.1.1.11 statisOutErrors00
1.3.6.1.4.1.278.108.1.23.1.1.12 statisEtherDropEvents00
1.3.6.1.4.1.278.108.1.23.1.1.13 statisEtherCRCAlignErrors00
1.3.6.1.4.1.278.108.1.23.1.1.14 statisEtherUndersizePkts00
1.3.6.1.4.1.278.108.1.23.1.1.15 statisEtherOversizePkts00
1.3.6.1.4.1.278.108.1.23.1.1.16 statisEtherFragments00
1.3.6.1.4.1.278.108.1.23.1.1.18 statisInErrorsRate00
1.3.6.1.4.1.278.108.1.23.1.1.19 statisOutErrorsRate00
1.3.6.1.4.1.278.108.1.23.1.1.20 statisEtherDropEventsRate00
1.3.6.1.4.1.278.108.1.23.1.1.21 statisEtherCRCAlignErrorsRate00
1.3.6.1.4.1.278.108.1.23.1.1.22 statisEtherUndersizePktsRate00
1.3.6.1.4.1.278.108.1.23.1.1.23 statisEtherOversizePktsRate00
1.3.6.1.4.1.278.108.1.23.1.1.24 statisEtherFragmentsRate00
1.3.6.1.4.1.278.108.1.23.1.1.25 statisEtherCollisionsRate00