OID reference

h3cEponUniOutStatsCollisions

1.3.6.1.4.1.2011.10.2.42.5.1.2.1.17

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.2011.10.2.42.5.1.2.1 (h3cEponUniCountEntry)
Node code
17
Node name
h3cEponUniOutStatsCollisions
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.17
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.42.5.1.2.1.17
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 42 5 1 2 1 17}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEponUni(5) h3cEponUniSysMan(1) h3cEponUniCountTable(2) h3cEponUniCountEntry(1) h3cEponUniOutStatsCollisions(17)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/42/5/1/2/1/17
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/42/5/1/2/1/17
  • /ISO/3/6/1/4/1/2011/10/2/42/5/1/2/1/17
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEponUni/h3cEponUniSysMan/h3cEponUniCountTable/h3cEponUniCountEntry/h3cEponUniOutStatsCollisions
  • Additional combinations skipped.

SNMP properties

Value type
Unsigned32
Maximum access defined by MIB
read-only
Status in MIB
current

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: ifIndex, h3cEponUniIndex.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2011.10.2.42.5.1.2.1.17

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cEponUniOutStatsCollisions · current

h3cEponUniOutStatsCollisions OBJECT-TYPE
    SYNTAX      Unsigned32
    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
        could.  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."
    ::= { h3cEponUniCountEntry 17 }

h3cEponUniOutStatsCollisions · current

h3cEponUniOutStatsCollisions OBJECT-TYPE
    SYNTAX      Unsigned32
    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
        could.  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."
    ::= { h3cEponUniCountEntry 17 }

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

H3C and HH3C MIB copies (Observium Community)Netdisco MIB archive copies

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 1H3C and HH3C MIB copies (Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cEponUniOutStatsCollisions · currentH3C and HH3C MIB copies (Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cEponUniOutStatsCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cEponUniOutStatsCollisions",
    "OBJECT-TYPE",
    "SYNTAX",
    "Unsigned32",
    "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 could. 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.\"",
    "::=",
    "{",
    "h3cEponUniCountEntry",
    "17",
    "}"
  ],
  "syntax_tree": [
    [
      "ApplicationSyntax",
      "Unsigned32"
    ],
    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 could. 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.2011)

Lwu Zhao

Siblings (19)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.1 h3cEponUniInStatsPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.2 h3cEponUniInStatsUnicastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.3 h3cEponUniInStatsBroadcastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.4 h3cEponUniInStatsMulticastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.5 h3cEponUniInPausePkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.6 h3cEponUniInTotalErrors00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.7 h3cEponUniInStatsCRCAlignErrors00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.8 h3cEponUniInStatsUndersizePkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.9 h3cEponUniInStatsOversizePkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.10 h3cEponUniInErrorbyOther00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.11 h3cEponUniOutStatsPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.12 h3cEponUniOutStatsUnicastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.13 h3cEponUniOutStatsBroadcastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.14 h3cEponUniOutStatsMulticastPkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.15 h3cEponUniOutStatsPausePkts00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.16 h3cEponUniOutTotalErrors00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.18 h3cEponUniOutDelayExceededDiscards00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.19 h3cEponUniOutErrorbyOther00
1.3.6.1.4.1.2011.10.2.42.5.1.2.1.20 h3cEponUniOutDroppedFrames00