OID reference

etherHistoryCollisions

1.3.6.1.4.1.5504.10.1.12.1.2.2.1.14

Description

The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. 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 m…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.5504.10.1.12.1.2.2.1 (etherHistoryEntry)
Node code
14
Node name
etherHistoryCollisions
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.14
URN notation
urn:oid:1.3.6.1.4.1.5504.10.1.12.1.2.2.1.14
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 5504 10 1 12 1 2 2 1 14}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zhone(5504) zhoneExperimental(10) ietfDrafts(1) zhoneRmonMibModule(12) zhoneRmon(1) history(2) etherHistoryTable(2) etherHistoryEntry(1) etherHistoryCollisions(14)}
OID-IRI notation
  • /1/3/6/1/4/1/5504/10/1/12/1/2/2/1/14
  • /ISO/Identified-Organization/6/1/4/1/5504/10/1/12/1/2/2/1/14
  • /ISO/3/6/1/4/1/5504/10/1/12/1/2/2/1/14
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/Zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/Zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/Zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/Zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/org/dod/internet/private/enterprise/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/org/dod/internet/private/enterprise/zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/org/dod/internet/private/enterprise/Zhone/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • /iso/org/dod/internet/private/enterprises/5504/zhoneExperimental/ietfDrafts/zhoneRmonMibModule/zhoneRmon/history/etherHistoryTable/etherHistoryEntry/etherHistoryCollisions
  • Additional combinations skipped.

SNMP properties

Value type
Counter32
Units
Collisions
Maximum access defined by MIB
read-only
Status in MIB
current

Interpreting this counter

A counter is cumulative. To estimate a rate, subtract two readings and divide by the elapsed time; use the units stated in the MIB.

Counter values can wrap or reset. A decrease alone does not distinguish a wrap from a reset, and multiple wraps between readings cannot be recovered reliably. Check the device's discontinuity indicators when available.

Published counter width: 32 bits. SMIv2: Counter32 · Counter64

Using this OID with SNMP

At least one MIB declaration places this object in a table row. A value belongs to a row instance; its suffix depends on the row's INDEX or AUGMENTS definition.

In ZHONE-RMON-MIB, the row index consists of these components in order:

  1. etherHistoryIndex (Integer32): one numeric subidentifier for the non-negative value.
  2. etherHistorySampleIndex (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.5504.10.1.12.1.2.2.1.14.<etherHistoryIndex>.<etherHistorySampleIndex>. Use values present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.5504.10.1.12.1.2.2.1.14

Replace the placeholders with your connection and authentication options. Available permissions and device support can differ from the MIB.

Properties come from available MIB definitions. Actual device support and access can differ. See source records below for original files and qualifications.

The displayed source records contain one distinct definition. Compare its source records.

etherHistoryCollisions 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 during this sampling
                interval.
                
                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."
            ::= { etherHistoryEntry 14 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

The best estimate of the total number of collisions on this Ethernet segment during this sampling interval. 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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)

See 1 matching source record

Evidence

Source records

1 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

etherHistoryCollisions · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: etherHistoryCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "etherHistoryCollisions",
    "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 during this sampling interval. 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.\"",
    "::=",
    "{",
    "etherHistoryEntry",
    "14",
    "}"
  ],
  "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 during this sampling interval. 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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.5504)

Goldberg Allen

Siblings (14)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.1 etherHistoryIndex00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.2 etherHistorySampleIndex00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.3 etherHistoryIntervalStart00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.4 etherHistoryDropEvents00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.5 etherHistoryOctets00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.6 etherHistoryPkts00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.7 etherHistoryBroadcastPkts00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.8 etherHistoryMulticastPkts00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.9 etherHistoryCRCAlignErrors00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.10 etherHistoryUndersizePkts00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.11 etherHistoryOversizePkts00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.12 etherHistoryFragments00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.13 etherHistoryJabbers00
1.3.6.1.4.1.5504.10.1.12.1.2.2.1.15 etherHistoryUtilization00