OID reference

reportsL2IfaceStatsCollisions

1.3.6.1.4.1.738.1.5.100.3.1.1.1.33

Description

The best estimate of the total number of collisions on this Ethernet segment. The value returned will depend on the RMON probe's location. Sections 8.2.1.3 (10BASE-5) and 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 transmitt…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.738.1.5.100.3.1.1.1 (reportsL2IfaceEntry)
Node code
33
Node name
reportsL2IfaceStatsCollisions
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.738.1.5.100.3.1.1.1.33
URN notation
urn:oid:1.3.6.1.4.1.738.1.5.100.3.1.1.1.33
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 738 1 5 100 3 1 1 1 33}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) privateVendorOID(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) prvtVendorDefMIB(738) prvt-products(1) switch(5) prvtSwitchMib(100) reports(3) reportsL2(1) reportsL2IfaceTable(1) reportsL2IfaceEntry(1) reportsL2IfaceStatsCollisions(33)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/738/1/5/100/3/1/1/1/33
  • /ISO/Identified-Organization/6/1/4/1/738/1/5/100/3/1/1/1/33
  • /ISO/3/6/1/4/1/738/1/5/100/3/1/1/1/33
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/privateVendorOID/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/privateVendorOID/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/prvtVendorDefMIB/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/privateVendorOID/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/prvtVendorDefMIB/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/privateVendorOID/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/prvtVendorDefMIB/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/org/dod/internet/private/enterprise/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/org/dod/internet/private/enterprise/privateVendorOID/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/org/dod/internet/private/enterprise/prvtVendorDefMIB/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • /iso/org/dod/internet/private/enterprises/738/prvt-products/switch/prvtSwitchMib/reports/reportsL2/reportsL2IfaceTable/reportsL2IfaceEntry/reportsL2IfaceStatsCollisions
  • 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 PRVT-SWITCH-MIB, the row index consists of these components in order:

  1. reportsL2IfaceUnit (Integer32): one numeric subidentifier for the non-negative value.
  2. reportsL2IfaceSlot (Integer32): one numeric subidentifier for the non-negative value.
  3. reportsL2IfacePort (Integer32): one numeric subidentifier for the non-negative value.

An instance has the form .1.3.6.1.4.1.738.1.5.100.3.1.1.1.33.<reportsL2IfaceUnit>.<reportsL2IfaceSlot>.<reportsL2IfacePort>. 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.738.1.5.100.3.1.1.1.33

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.

reportsL2IfaceStatsCollisions 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 RMON probe's location.
Sections 8.2.1.3 (10BASE-5) and 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. Section 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 coaxial segments to which
the repeater is connected."
::= { reportsL2IfaceEntry 33 }

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 RMON probe's location. Sections 8.2.1.3 (10BASE-5) and 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. Section 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 coaxial 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

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

Status in source: current.

Names: reportsL2IfaceStatsCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "reportsL2IfaceStatsCollisions",
    "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 RMON probe's location. Sections 8.2.1.3 (10BASE-5) and 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. Section 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 coaxial segments to which the repeater is connected.\"",
    "::=",
    "{",
    "reportsL2IfaceEntry",
    "33",
    "}"
  ],
  "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 RMON probe's location. Sections 8.2.1.3 (10BASE-5) and 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. Section 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 coaxial 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.738)

Killim Nahum

Siblings (41)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.738.1.5.100.3.1.1.1.1 reportsL2IfaceUnit00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.2 reportsL2IfaceSlot00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.3 reportsL2IfacePort00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.4 reportsL2IfaceBridgeIndex00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.5 reportsL2IfaceType00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.6 reportsL2IfaceLink00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.7 reportsL2IfaceDuplexSpeedGet00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.8 reportsL2IfaceTXOctetsNoErr00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.9 reportsL2IfaceTXPacketsNoErr00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.10 reportsL2IfaceRXOctetsNoErr00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.11 reportsL2IfaceRXPacketsNoErr00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.12 reportsL2IfaceIfInOctets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.13 reportsL2IfaceIfInUcastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.14 reportsL2IfaceIfInNUcastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.15 reportsL2IfaceIfInDiscards00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.16 reportsL2IfaceIfInErrors00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.17 reportsL2IfaceIfInUnknownProtos00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.18 reportsL2IfaceIfOutOctets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.19 reportsL2IfaceIfOutUcastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.20 reportsL2IfaceIfOutNUcastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.21 reportsL2IfaceIfOutDiscards00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.22 reportsL2IfaceIfOutErrors00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.23 reportsL2IfaceStatsDropEvents00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.24 reportsL2IfaceStatsOctets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.25 reportsL2IfaceStatsPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.26 reportsL2IfaceStatsBroadcastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.27 reportsL2IfaceStatsMulticastPkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.28 reportsL2IfaceStatsCRCAlignErrors00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.29 reportsL2IfaceStatsUndersizePkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.30 reportsL2IfaceStatsOversizePkts00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.31 reportsL2IfaceStatsFragments00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.32 reportsL2IfaceStatsJabbers00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.34 reportsL2IfaceStatsPkts64Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.35 reportsL2IfaceStatsPkts65to127Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.36 reportsL2IfaceStatsPkts128to255Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.37 reportsL2IfaceStatsPkts256to511Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.38 reportsL2IfaceStatsPkts512to1023Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.39 reportsL2IfaceStatsPkts1024to1518Octets00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.40 reportsL2IfaceFlow00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.41 reportsL2IfaceHWType00
1.3.6.1.4.1.738.1.5.100.3.1.1.1.42 reportsL2IfaceActiveJackIndex00