Reference record for OID 1.3.6.1.2.1.10.7.2.1.17


parent
1.3.6.1.2.1.10.7.2.1 (dot3StatsEntry)
node code
17
node name
dot3StatsEtherChipSet
dot oid
1.3.6.1.2.1.10.7.2.1.17
type
OBJECT-TYPE
asn1 oid
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsEtherChipSet(17)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • ...skipped...
  • /iso/org/dod/internet/mgmt/mib-2/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • /iso/org/dod/internet/mgmt/mib-2/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • /iso/org/dod/internet/mgmt/mib/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • /iso/org/dod/internet/mgmt/mib/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsEtherChipSet
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/10/7/2/1/17

    Description by circitor

    ******** THIS OBJECT IS DEPRECATED ********

    This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are typically built out of
    several different chips. The MIB implementor
    is presented with a decision of which chip
    to identify via this object. The implementor
    should identify the chip which is usually
    called the Medium Access Control chip.
    If no such chip is easily identifiable,
    the implementor should identify the chip
    which actually gathers the transmit
    and receive statistics and error
    indications. This would allow a
    manager station to correlate the
    statistics and the chip generating
    them, giving it the ability to take
    into account any known anomalies
    in the chip.

    This object has been deprecated. Implementation
    feedback indicates that it is of limited use for
    debugging network problems in the field, and
    the administrative overhead involved in
    maintaining a registry of chipset OIDs is not
    justified.

    Parsed from file EtherLike-MIB.mib
    Module: EtherLike-MIB

    Description by cisco_v1

    ******** THIS OBJECT IS DEPRECATED ********

    This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are typically built out of
    several different chips. The MIB implementor
    is presented with a decision of which chip
    to identify via this object. The implementor
    should identify the chip which is usually
    called the Medium Access Control chip.
    If no such chip is easily identifiable,
    the implementor should identify the chip
    which actually gathers the transmit
    and receive statistics and error
    indications. This would allow a
    manager station to correlate the
    statistics and the chip generating
    them, giving it the ability to take
    into account any known anomalies
    in the chip.

    This object has been deprecated. Implementation
    feedback indicates that it is of limited use for
    debugging network problems in the field, and
    the administrative overhead involved in
    maintaining a registry of chipset OIDs is not
    justified.

    Description by oid_info

    dot3StatsEtherChipSet OBJECT-TYPE
    SYNTAX OBJECT IDENTIFIER
    MAX-ACCESS read-only
    STATUS deprecated
    DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
    This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are typically built out of
    several different chips. The MIB implementor
    is presented with a decision of which chip
    to identify via this object. The implementor
    should identify the chip which is usually
    called the Medium Access Control chip.
    If no such chip is easily identifiable,
    the implementor should identify the chip
    which actually gathers the transmit
    and receive statistics and error
    indications. This would allow a
    manager station to correlate the
    statistics and the chip generating
    them, giving it the ability to take
    into account any known anomalies
    in the chip."

    View at oid-info.com

    Description by mibdepot

    This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are typically built out of
    several different chips. The MIB implementor
    is presented with a decision of which chip
    to identify via this object. The implementor
    should identify the chip which is usually
    called the Medium Access Control chip.
    If no such chip is easily identifiable,
    the implementor should identify the chip
    which actually gathers the transmit
    and receive statistics and error
    indications. This would allow a
    manager station to correlate the
    statistics and the chip generating
    them, giving it the ability to take
    into account any known anomalies
    in the chip.

    Parsed from file rfc1643.mib.txt
    Company: None
    Module: EtherLike-MIB

    Description by cisco

    ******** THIS OBJECT IS DEPRECATED ********

    This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are typically built out of
    several different chips. The MIB implementor
    is presented with a decision of which chip
    to identify via this object. The implementor
    should identify the chip which is usually
    called the Medium Access Control chip.
    If no such chip is easily identifiable,
    the implementor should identify the chip
    which actually gathers the transmit
    and receive statistics and error
    indications. This would allow a
    manager station to correlate the
    statistics and the chip generating
    them, giving it the ability to take
    into account any known anomalies
    in the chip.

    This object has been deprecated. Implementation
    feedback indicates that it is of limited use for
    debugging network problems in the field, and
    the administrative overhead involved in
    maintaining a registry of chipset OIDs is not
    justified.

    Information by circitor

    dot3StatsEtherChipSet OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS deprecated DESCRIPTION "******** THIS OBJECT IS DEPRECATED ******** This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip. This object has been deprecated. Implementation feedback indicates that it is of limited use for debugging network problems in the field, and the administrative overhead involved in maintaining a registry of chipset OIDs is not justified." ::= { dot3StatsEntry 17 }

    Information by cisco_v1

    dot3StatsEtherChipSet OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS deprecated DESCRIPTION "******** THIS OBJECT IS DEPRECATED ******** This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip. This object has been deprecated. Implementation feedback indicates that it is of limited use for debugging network problems in the field, and the administrative overhead involved in maintaining a registry of chipset OIDs is not justified." ::= { dot3StatsEntry 17 }

    Information by oid_info

    Automatically extracted from RFC2665

    Information by mibdepot

    dot3StatsEtherChipSet OBJECT-TYPE SYNTAX OBJECT IDENTIFIER ACCESS read-only STATUS mandatory DESCRIPTION "This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip." ::= { dot3StatsEntry 17 }

    Information by cisco

    dot3StatsEtherChipSet OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-only STATUS deprecated DESCRIPTION "******** THIS OBJECT IS DEPRECATED ******** This object contains an OBJECT IDENTIFIER which identifies the chipset used to realize the interface. Ethernet-like interfaces are typically built out of several different chips. The MIB implementor is presented with a decision of which chip to identify via this object. The implementor should identify the chip which is usually called the Medium Access Control chip. If no such chip is easily identifiable, the implementor should identify the chip which actually gathers the transmit and receive statistics and error indications. This would allow a manager station to correlate the statistics and the chip generating them, giving it the ability to take into account any known anomalies in the chip. This object has been deprecated. Implementation feedback indicates that it is of limited use for debugging network problems in the field, and the administrative overhead involved in maintaining a registry of chipset OIDs is not justified." ::= { dot3StatsEntry 17 }

    First Registration Authority (recovered by parent 1.3.6)

    Defense Communication Agency

    Current Registration Authority (recovered by parent 1.3.6.1.2)

    Internet Assigned Numbers Authority

    Children (1)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.10.7.2.1.17.0 dot3StatsEtherChipSet 0 0 None

    Brothers (20)

    OIDNameSub childrenSub Nodes TotalDescription
    1.3.6.1.2.1.10.7.2.1.1 dot3StatsIndex 5 5 An index value that uniquely identifies an
    interface to an ethernet-like medium. The
    interface identified by a particular value …
    1.3.6.1.2.1.10.7.2.1.2 dot3StatsAlignmentErrors 0 0 A count of frames received on a particular
    interface that are not an integral number of
    octets in length and do not pass the FCS …
    1.3.6.1.2.1.10.7.2.1.3 dot3StatsFCSErrors 0 0 A count of frames received on a particular
    interface that are an integral number of octets in
    length but do not pass the FCS chec…
    1.3.6.1.2.1.10.7.2.1.4 dot3StatsSingleCollisionFrames 0 0 A count of successfully transmitted frames on a
    particular interface for which transmission is
    inhibited by exactly one collision…
    1.3.6.1.2.1.10.7.2.1.5 dot3StatsMultipleCollisionFrames 0 0 A count of successfully transmitted frames on a
    particular interface for which transmission is
    inhibited by more than one collisi…
    1.3.6.1.2.1.10.7.2.1.6 dot3StatsSQETestErrors 0 0 A count of times that the SQE TEST ERROR message
    is generated by the PLS sublayer for a particular
    interface. The SQE TEST ERROR …
    1.3.6.1.2.1.10.7.2.1.7 dot3StatsDeferredTransmissions 0 0 A count of frames for which the first
    transmission attempt on a particular interface is
    delayed because the medium is busy.
    The co…
    1.3.6.1.2.1.10.7.2.1.8 dot3StatsLateCollisions 0 0 The number of times that a collision is detected
    on a particular interface later than 512 bit-times
    into the transmission of a pa…
    1.3.6.1.2.1.10.7.2.1.9 dot3StatsExcessiveCollisions 0 0 A count of frames for which transmission on a
    particular interface fails due to excessive
    collisions.
    1.3.6.1.2.1.10.7.2.1.10 dot3StatsInternalMacTransmitErrors 0 0 A count of frames for which transmission on a
    particular interface fails due to an internal MAC
    sublayer transmit error. A frame …
    1.3.6.1.2.1.10.7.2.1.11 dot3StatsCarrierSenseErrors 0 0 The number of times that the carrier sense
    condition was lost or never asserted when
    attempting to transmit a frame on a particul…
    1.3.6.1.2.1.10.7.2.1.12 dot3StatsExcessiveDeferrals, dot3StatsFiller12 0 0 A count of frames for which transmission on a
    particular interface is deferred for an excessive
    period of time.
    1.3.6.1.2.1.10.7.2.1.13 dot3StatsFrameTooLongs 0 0 A count of frames received on a particular
    interface that exceed the maximum permitted frame
    size.

    The count represented by an ins…
    1.3.6.1.2.1.10.7.2.1.14 dot3StatsInRangeLengthErrors, dot3StatsFiller14 0 0 A count of frames received on a particular
    interface with a length field value that falls
    between the minimum unpadded LLC data s…
    1.3.6.1.2.1.10.7.2.1.15 dot3StatsOutOfRangeLengthFields, dot3StatsFiller15 0 0 A count of frames received on a particular
    interface for which the length field value exceeds
    the maximum allowed LLC data size.

    T…
    1.3.6.1.2.1.10.7.2.1.16 dot3StatsInternalMacReceiveErrors 0 0 A count of frames for which reception on a
    particular interface fails due to an internal MAC
    sublayer receive error. A frame is o…
    1.3.6.1.2.1.10.7.2.1.18 dot3StatsSymbolErrors 0 0 For an interface operating at 100 Mb/s, the
    number of times there was an invalid data symbol
    when a valid carrier was present.

    For…
    1.3.6.1.2.1.10.7.2.1.19 dot3StatsDuplexStatus 0 0 The current mode of operation of the MAC
    entity. 'unknown' indicates that the current
    duplex mode could not be determined.

    Manage…
    1.3.6.1.2.1.10.7.2.1.20 dot3StatsRateControlAbility 0 0 'true' for interfaces operating at speeds above
    1000 Mb/s that support Rate Control through
    lowering the average data rate of the…
    1.3.6.1.2.1.10.7.2.1.21 dot3StatsRateControlStatus 0 0 The current Rate Control mode of operation of
    the MAC sublayer of this interface.