Reference record for OID 1.3.6.1.4.1.52642.2.83.4.2.1.18

Parent
1.3.6.1.4.1.52642.2.83.4.2.1 (fsEOCComUniCountEntry)
Node code
18
Node name
fsEOCUniOutCollisions
Numeric OID
1.3.6.1.4.1.52642.2.83.4.2.1.18
URN notation
urn:oid:1.3.6.1.4.1.52642.2.83.4.2.1.18
ASN.1 notation

{1 3 6 1 4 1 52642 2 83 4 2 1 18}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsnetworks(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) nmslocal(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsProtocol(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) fsCommon(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fs(52642) transmission(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsnetworks(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) nmslocal(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsProtocol(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) fsCommon(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nms(52642) transmission(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsnetworks(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) nmslocal(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsProtocol(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) fsCommon(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) fiberstore(52642) transmission(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) vtss(52642) fsnetworks(2) fsEOCCommon(83) fsEOCComUniMan(4) fsEOCComUniCountTable(2) fsEOCComUniCountEntry(1) fsEOCUniOutCollisions(18)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/52642/2/83/4/2/1/18
  • /ISO/Identified-Organization/6/1/4/1/52642/2/83/4/2/1/18
  • /ISO/3/6/1/4/1/52642/2/83/4/2/1/18
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsnetworks/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fs/nmslocal/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsProtocol/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fs/fsCommon/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fs/transmission/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsnetworks/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/nmslocal/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsProtocol/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/fsCommon/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/nms/transmission/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsnetworks/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/nmslocal/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsProtocol/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/fsCommon/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/fiberstore/transmission/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/FS/fsnetworks/fsEOCCommon/fsEOCComUniMan/fsEOCComUniCountTable/fsEOCComUniCountEntry/fsEOCUniOutCollisions
  • Additional combinations skipped.

Descriptions

fsEOCUniOutCollisions — FS.COM official Documentation Hub native MIB packages

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.

Source records

fsEOCUniOutCollisions

Status in source: current.

Names: fsEOCUniOutCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "fsEOCUniOutCollisions",
    "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.\"",
    "::=",
    "{",
    "fsEOCComUniCountEntry",
    "18",
    "}"
  ],
  "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
  ]
}
  • FS.COM official Documentation Hub native MIB packages · Publisher's source file: Source package: ies3220-8t4f-switch-snmp-mib-files.zip

    Module: FS-EOC-COMMON-MIB

    Published definition
    fsEOCUniOutCollisions  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."
        ::= { fsEOCComUniCountEntry 18 }
    Module imports
    {'IF-MIB': ['ifIndex', 'ifDescr'], 'SNMPv2-TC': ['MacAddress', 'RowStatus', 'DisplayString', 'TruthValue'], 'FS-OID-MIB': ['fsCommon'], 'SNMPv2-SMI': ['Integer32', 'Unsigned32', 'TimeTicks', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE', 'Gauge32'], 'FS-HPEOC-MIB': ['fsHPEOCDownLoadCNUFWResult'], 'IANAifType-MIB': ['IANAifType']}

    Related source files and packages:

    • IES5120-28TF Switch SNMP MIB FilesIES5120-28TF Switch SNMP MIB Files; Models: IES5120-28TF; Catalog updated: 2026-02-27 15:56:52; File: mall/resource/ies5120-28tf-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:14:36 GMT; 2.6 MiB
    • IES3220-8T4F Switch SNMP MIB FilesIES3220-8T4F Switch SNMP MIB Files; Models: IES3220-8T4F; Catalog updated: 2025-12-03 14:28:43; File: mall/resource/ies3220-8t4f-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:08:16 GMT; 2.6 MiB
    • IES5120-48T4S Switch SNMP MIB FilesIES5120-48T4S Switch SNMP MIB Files; Models: IES5120-48T4S; Catalog updated: 2026-02-27 16:10:26; File: mall/resource/ies5120-48t4s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:16:11 GMT; 2.6 MiB
    Show all 10 related files and packages
    • TSN3220-10S Switch SNMP MIB FilesTSN3220-10S Switch SNMP MIB Files; Models: TSN3220-10S; Catalog updated: 2026-01-08 09:53:00; File: mall/resource/tsn3220-10s-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:10:41 GMT; 2.6 MiB
    • IES5120-28TS-P Switch SNMP MIB FilesIES5120-28TS-P Switch SNMP MIB Files; Models: IES5120-28TS-P; Catalog updated: 2026-02-27 16:09:52; File: mall/resource/ies5120-28ts-p-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:40 GMT; 2.6 MiB
    • IES5220-30TS-3ES Switch SNMP MIB FilesIES5220-30TS-3ES Switch SNMP MIB Files; Models: IES5220-30TS-3ES; Catalog updated: 2025-08-19 16:17:18; File: mall/resource/ies5220-30ts-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:17:18 GMT; 2.6 MiB
    • IES5220-6S-3ES Switch SNMP MIB FilesIES5220-6S-3ES Switch SNMP MIB Files; Models: IES5220-6S-3ES; Catalog updated: 2026-02-27 16:11:15; File: mall/resource/ies5220-6s-3es-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:32:47 GMT; 2.6 MiB
    • IES3220-8T4F-U Switch SNMP MIB FilesIES3220-8T4F-U Switch SNMP MIB Files; Models: IES3220-8T4F-U; Catalog updated: 2025-12-03 14:47:49; File: mall/resource/ies3220-8t4f-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:09:07 GMT; 2.6 MiB
    • IES5120-28TS Switch SNMP MIB FilesIES5120-28TS Switch SNMP MIB Files; Models: IES5120-28TS; Catalog updated: 2026-02-27 15:57:39; File: mall/resource/ies5120-28ts-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:15:08 GMT; 2.6 MiB
    • TSN3220-10S-U Switch SNMP MIB FilesTSN3220-10S-U Switch SNMP MIB Files; Models: TSN3220-10S-U; Catalog updated: 2025-12-16 18:11:48; File: mall/resource/tsn3220-10s-u-switch-snmp-mib-files.zip; Publisher Last-Modified: Tue, 19 Aug 2025 08:13:57 GMT; 2.6 MiB

    Source location: FS-EOC-COMMON-MIB::fsEOCUniOutCollisions.
    Source version and references

    Same file in tsn3220-10s-u-switch-snmp-mib-files.zip.

    Same file in tsn3220-10s-switch-snmp-mib-files.zip.

    Same file in ies5220-6s-3es-switch-snmp-mib-files.zip.

    Same file in ies5220-30ts-3es-switch-snmp-mib-files.zip.

    Downloaded: 2026-10-24T13:35:15.398925+00:00.

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.52642)

FS.COM INC

Siblings (21)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.52642.2.83.4.2.1.1 fsEOCUniInPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.2 fsEOCUniInUPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.3 fsEOCUniInBPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.4 fsEOCUniInMPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.5 fsEOCUniInPausePkts00
1.3.6.1.4.1.52642.2.83.4.2.1.6 fsEOCUniInTotalErrors00
1.3.6.1.4.1.52642.2.83.4.2.1.7 fsEOCUniInCRCErrs00
1.3.6.1.4.1.52642.2.83.4.2.1.8 fsEOCUniInUndersizePkts00
1.3.6.1.4.1.52642.2.83.4.2.1.9 fsEOCUniInOversizePkts00
1.3.6.1.4.1.52642.2.83.4.2.1.10 fsEOCUniInErrorbyOther00
1.3.6.1.4.1.52642.2.83.4.2.1.11 fsEOCUniInOctets00
1.3.6.1.4.1.52642.2.83.4.2.1.12 fsEOCUniOutPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.13 fsEOCUniOutUPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.14 fsEOCUniOutBPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.15 fsEOCUniOutMPkts00
1.3.6.1.4.1.52642.2.83.4.2.1.16 fsEOCUniOutPausePkts00
1.3.6.1.4.1.52642.2.83.4.2.1.17 fsEOCUniOutTotalErrors00
1.3.6.1.4.1.52642.2.83.4.2.1.19 fsEOCUniOutDelayExceedDsds00
1.3.6.1.4.1.52642.2.83.4.2.1.20 fsEOCUniOutErrorbyOther00
1.3.6.1.4.1.52642.2.83.4.2.1.21 fsEOCUniOutDroppedFrames00
1.3.6.1.4.1.52642.2.83.4.2.1.22 fsEOCUniOutOctets00