Reference record for OID 1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.17

Parent
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1 (hpnicfEponUniCountEntry)
Node code
17
Node name
hpnicfEponUniOutStatsCollisions
Numeric OID
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.17
URN notation
urn:oid:1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.17
ASN.1 notation

{1 3 6 1 4 1 11 2 14 11 15 2 42 5 1 2 1 17}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) hpPrintServer(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hp(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) nm(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) hP(11) wireless(2) icf(14) hpicfObjects(11) hpnicf(15) hpnicfCommon(2) hpnicfEpon(42) hpnicfEponUni(5) hpnicfEponUniSysMan(1) hpnicfEponUniCountTable(2) hpnicfEponUniCountEntry(1) hpnicfEponUniOutStatsCollisions(17)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/11/2/14/11/15/2/42/5/1/2/1/17
  • /ISO/Identified-Organization/6/1/4/1/11/2/14/11/15/2/42/5/1/2/1/17
  • /ISO/3/6/1/4/1/11/2/14/11/15/2/42/5/1/2/1/17
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprise/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hp/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hp/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/IMPORTS/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hP/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hP/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/nm/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • /iso/identified-organization/dod/internet/private/enterprises/hpPrintServer/wireless/icf/hpicfObjects/hpnicf/hpnicfCommon/hpnicfEpon/hpnicfEponUni/hpnicfEponUniSysMan/hpnicfEponUniCountTable/hpnicfEponUniCountEntry/hpnicfEponUniOutStatsCollisions
  • Additional combinations skipped.

Descriptions

hpnicfEponUniOutStatsCollisions — HPE networking MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies

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

hpnicfEponUniOutStatsCollisions

Status in source: current.

Names: hpnicfEponUniOutStatsCollisions

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "hpnicfEponUniOutStatsCollisions",
    "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.\"",
    "::=",
    "{",
    "hpnicfEponUniCountEntry",
    "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
  ]
}
  • HPE networking MIB copies (LibreNMS/Observium Community) · Publisher's source file: Source package: observium-community-latest.tar.gz

    Vendor MIB copy from the Observium Community archive. HPE networking support.

    Module: HPN-ICF-EPON-UNI-MIB

    Published definition
    hpnicfEponUniOutStatsCollisions 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."
        ::= { hpnicfEponUniCountEntry 17 }
    Module imports
    {'IF-MIB': ['ifIndex', 'ifDescr'], 'SNMPv2-TC': ['MacAddress', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['Integer32', 'Unsigned32', 'IpAddress', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfEpon']}

    Related source files and packages:


    Source location: HPN-ICF-EPON-UNI-MIB::hpnicfEponUniOutStatsCollisions.
    Source version and references

    Downloaded: 2026-10-23T19:25:41.049282+00:00.

  • Netdisco MIB archive copies · Publisher's source file: hpnicfEponUni.mib

    Vendor MIB copy from the Netdisco archive.

    Module: HPN-ICF-EPON-UNI-MIB

    Published definition
    hpnicfEponUniOutStatsCollisions 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."
        ::= { hpnicfEponUniCountEntry 17 }
    Module imports
    {'IF-MIB': ['ifIndex', 'ifDescr'], 'SNMPv2-TC': ['MacAddress', 'TruthValue', 'RowStatus'], 'SNMPv2-SMI': ['Integer32', 'Unsigned32', 'IpAddress', 'OBJECT-TYPE', 'MODULE-IDENTITY', 'NOTIFICATION-TYPE'], 'HPN-ICF-OID-MIB': ['hpnicfEpon']}
    · Archived source file

    Related source files and packages:


    Source location: HPN-ICF-EPON-UNI-MIB::hpnicfEponUniOutStatsCollisions.
    Source version and references

    Downloaded: 2026-10-24T15:28:10.515993+00:00.

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.11)

Peterson Tyler

Siblings (19)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.1 hpnicfEponUniInStatsPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.2 hpnicfEponUniInStatsUnicastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.3 hpnicfEponUniInStatsBroadcastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.4 hpnicfEponUniInStatsMulticastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.5 hpnicfEponUniInPausePkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.6 hpnicfEponUniInTotalErrors00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.7 hpnicfEponUniInStatsCRCAlignErrors00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.8 hpnicfEponUniInStatsUndersizePkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.9 hpnicfEponUniInStatsOversizePkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.10 hpnicfEponUniInErrorbyOther00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.11 hpnicfEponUniOutStatsPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.12 hpnicfEponUniOutStatsUnicastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.13 hpnicfEponUniOutStatsBroadcastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.14 hpnicfEponUniOutStatsMulticastPkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.15 hpnicfEponUniOutStatsPausePkts00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.16 hpnicfEponUniOutTotalErrors00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.18 hpnicfEponUniOutDelayExceededDiscards00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.19 hpnicfEponUniOutErrorbyOther00
1.3.6.1.4.1.11.2.14.11.15.2.42.5.1.2.1.20 hpnicfEponUniOutDroppedFrames00