OID reference

statisticsStatsCollisions

1.3.6.1.4.1.171.11.166.1000.99.1.1.24

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…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.171.11.166.1000.99.1.1 (statisticsEntry)
Node code
24
Node name
statisticsStatsCollisions
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.171.11.166.1000.99.1.1.24
URN notation
urn:oid:1.3.6.1.4.1.171.11.166.1000.99.1.1.24
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 171 11 166 1000 99 1 1 24}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dlink(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) d-link(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) company(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) my(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dlink(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) d-link(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) company(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) my(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nms(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dlink(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) d-link(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) company(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) my(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nms(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dlink(171) dlink-mgmt(11) dlink-DGS1210SeriesProj(166) dgs-1210-Common(1000) companyStatistics(99) sysStatisticsTable(1) statisticsEntry(1) statisticsStatsCollisions(24)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/171/11/166/1000/99/1/1/24
  • /ISO/Identified-Organization/6/1/4/1/171/11/166/1000/99/1/1/24
  • /ISO/3/6/1/4/1/171/11/166/1000/99/1/1/24
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/dlink/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/d-link/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/company/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/my/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/dlink/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/d-link/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/company/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/my/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/nms/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/dlink/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/d-link/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/company/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/my/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nms/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/dlink/dlink-mgmt/dlink-DGS1210SeriesProj/dgs-1210-Common/companyStatistics/sysStatisticsTable/statisticsEntry/statisticsStatsCollisions
  • Additional combinations skipped.

SNMP properties

Value type
Counter32
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. The index encoding is not inferred here.

Published row index: statisticsIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.171.11.166.1000.99.1.1.24

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.

statisticsStatsCollisions OBJECT-TYPE
     SYNTAX     Counter32
     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."
     ::= { statisticsEntry 24 }

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. 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

D-Link official switch MIBs

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 1D-Link official switch MIBs1 record · 2 sources

Description 1

statisticsStatsCollisions · currentD-Link official switch MIBs2 sources

Status in source: current.

Names: statisticsStatsCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "statisticsStatsCollisions",
    "OBJECT-TYPE",
    "SYNTAX",
    "Counter32",
    "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.\"",
    "::=",
    "{",
    "statisticsEntry",
    "24",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Counter32"
    ],
    null,
    [
      "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
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.171)

Henry P. Nagai

Siblings (29)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.171.11.166.1000.99.1.1.1 statisticsIndex00
1.3.6.1.4.1.171.11.166.1000.99.1.1.2 statisticsInOctets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.3 statisticsInUcastPkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.4 statisticsInMcastPkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.5 statisticsInNUcastPkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.6 statisticsInDiscards00
1.3.6.1.4.1.171.11.166.1000.99.1.1.7 statisticsInErrors00
1.3.6.1.4.1.171.11.166.1000.99.1.1.8 statisticsOutOctets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.9 statisticsOutUcastPkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.10 statisticsOutNUcastPkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.11 statisticsOutErrors00
1.3.6.1.4.1.171.11.166.1000.99.1.1.12 statisticsOutDiscards00
1.3.6.1.4.1.171.11.166.1000.99.1.1.13 statisticsLateCollisions00
1.3.6.1.4.1.171.11.166.1000.99.1.1.14 statisticsExcessiveCollisions00
1.3.6.1.4.1.171.11.166.1000.99.1.1.15 statisticsFCSErrors00
1.3.6.1.4.1.171.11.166.1000.99.1.1.16 statisticsFrameTooLongs00
1.3.6.1.4.1.171.11.166.1000.99.1.1.17 statisticsEtherUndersizePkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.18 statisticsEtherOversizePkts00
1.3.6.1.4.1.171.11.166.1000.99.1.1.19 statisticsEtherFragments00
1.3.6.1.4.1.171.11.166.1000.99.1.1.20 statisticsEtherJabbers00
1.3.6.1.4.1.171.11.166.1000.99.1.1.21 statisticsEtherDropEvents00
1.3.6.1.4.1.171.11.166.1000.99.1.1.22 statisticsDeferredTransmissions00
1.3.6.1.4.1.171.11.166.1000.99.1.1.23 statisticsSingleCollisionFrames00
1.3.6.1.4.1.171.11.166.1000.99.1.1.25 statisticsPkts64Octets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.26 statisticsPkts65to127Octets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.27 statisticsPkts128to255Octets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.28 statisticsPkts256to511Octets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.29 statisticsPkts512to1023Octets00
1.3.6.1.4.1.171.11.166.1000.99.1.1.30 statisticsPkts1024to1518Octets00