OID reference

sleEtherStatsCollisions

1.3.6.1.4.1.6296.101.9.4.1.1.1.13

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.6296.101.9.4.1.1.1 (sleEtherStatsEntry)
Node code
13
Node name
sleEtherStatsCollisions
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.6296.101.9.4.1.1.1.13
URN notation
urn:oid:1.3.6.1.4.1.6296.101.9.4.1.1.1.13
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 6296 101 9 4 1 1 1 13}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) dasan(6296) sleMgmt(101) sleRmon(9) sleStatistics(4) sleEtherStats(1) sleEtherStatsTable(1) sleEtherStatsEntry(1) sleEtherStatsCollisions(13)}
OID-IRI notation
  • /1/3/6/1/4/1/6296/101/9/4/1/1/1/13
  • /ISO/Identified-Organization/6/1/4/1/6296/101/9/4/1/1/1/13
  • /ISO/3/6/1/4/1/6296/101/9/4/1/1/1/13
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/enterprise/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/enterprise/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/enterprises/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/enterprises/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/vendor-objects/6296/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • /iso/org/dod/internet/private/vendor-objects/dasan/sleMgmt/sleRmon/sleStatistics/sleEtherStats/sleEtherStatsTable/sleEtherStatsEntry/sleEtherStatsCollisions
  • 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.

In SLE-RMON-MIB, the row index sleEtherStatsIndex is declared as INTEGER. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.6296.101.9.4.1.1.1.13.<sleEtherStatsIndex>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.6296.101.9.4.1.1.1.13

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.

sleEtherStatsCollisions 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.
				"
			::= { sleEtherStatsEntry 13 }

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

DASAN Networks 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 1DASAN Networks MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

sleEtherStatsCollisions · currentDASAN Networks MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: sleEtherStatsCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "sleEtherStatsCollisions",
    "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. \"",
    "::=",
    "{",
    "sleEtherStatsEntry",
    "13",
    "}"
  ],
  "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.6296)

Lee Wonhee

Siblings (21)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.6296.101.9.4.1.1.1.1 sleEtherStatsIndex00
1.3.6.1.4.1.6296.101.9.4.1.1.1.2 sleEtherStatsDataSource00
1.3.6.1.4.1.6296.101.9.4.1.1.1.3 sleEtherStatsDropEvents00
1.3.6.1.4.1.6296.101.9.4.1.1.1.4 sleEtherStatsOctets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.5 sleEtherStatsPkts00
1.3.6.1.4.1.6296.101.9.4.1.1.1.6 sleEtherStatsBroadcastPkts00
1.3.6.1.4.1.6296.101.9.4.1.1.1.7 sleEtherStatsMulticastPkts00
1.3.6.1.4.1.6296.101.9.4.1.1.1.8 sleEtherStatsCRCAlignErrors00
1.3.6.1.4.1.6296.101.9.4.1.1.1.9 sleEtherStatsUndersizePkts00
1.3.6.1.4.1.6296.101.9.4.1.1.1.10 sleEtherStatsOversizePkts00
1.3.6.1.4.1.6296.101.9.4.1.1.1.11 sleEtherStatsFragments00
1.3.6.1.4.1.6296.101.9.4.1.1.1.12 sleEtherStatsJabbers00
1.3.6.1.4.1.6296.101.9.4.1.1.1.14 sleEtherStatsPkts64Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.15 sleEtherStatsPkts65to127Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.16 sleEtherStatsPkts128to255Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.17 sleEtherStatsPkts256to511Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.18 sleEtherStatsPkts512to1023Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.19 sleEtherStatsPkts1024to1518Octets00
1.3.6.1.4.1.6296.101.9.4.1.1.1.20 sleEtherStatsOwner00
1.3.6.1.4.1.6296.101.9.4.1.1.1.21 sleEtherStatsStatus00
1.3.6.1.4.1.6296.101.9.4.1.1.1.22 sleEtherStatsClearedTime00