Reference record for OID 1.3.6.1.2.1.10.7.2.1.19


parent
1.3.6.1.2.1.10.7.2.1 (dot3StatsEntry)
node code
19
node name
dot3StatsDuplexStatus
dot oid
1.3.6.1.2.1.10.7.2.1.19
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) dot3StatsDuplexStatus(19)}
  • {iso(1) identified-organization(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • ...skipped...
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib-2(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • {iso(1) org(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • ...skipped...
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) ieee8023(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) mgmt(2) mib(1) transmission(10) dot3(7) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(19)}
  • iri oid
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/identified-organization/dod/internet/mgmt/mib-2/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • ...skipped...
  • /iso/org/dod/internet/mgmt/mib-2/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/org/dod/internet/mgmt/mib-2/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/org/dod/internet/mgmt/mib/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/org/dod/internet/mgmt/mib/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • ...skipped...
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/ieee8023/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/iso-identified-organization/dod/internet/mgmt/mib/transmission/dot3/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • iri by oid_info
    /ISO/Identified-Organization/6/1/2/1/10/7/2/1/19

    Description by circitor

    The current mode of operation of the MAC
    entity. 'unknown' indicates that the current
    duplex mode could not be determined.

    Management control of the duplex mode is
    accomplished through the MAU MIB. When
    an interface does not support autonegotiation,
    or when autonegotiation is not enabled, the
    duplex mode is controlled using
    ifMauDefaultType. When autonegotiation is
    supported and enabled, duplex mode is controlled
    using ifMauAutoNegAdvertisedBits. In either
    case, the currently operating duplex mode is
    reflected both in this object and in ifMauType.

    Note that this object provides redundant
    information with ifMauType. Normally, redundant
    objects are discouraged. However, in this
    instance, it allows a management application to
    determine the duplex status of an interface
    without having to know every possible value of
    ifMauType. This was felt to be sufficiently
    valuable to justify the redundancy.

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

    Description by cisco_v1

    The current mode of operation of the MAC
    entity. 'unknown' indicates that the current
    duplex mode could not be determined.

    Management control of the duplex mode is
    accomplished through the MAU MIB. When
    an interface does not support autonegotiation,
    or when autonegotiation is not enabled, the
    duplex mode is controlled using
    ifMauDefaultType. When autonegotiation is
    supported and enabled, duplex mode is controlled
    using ifMauAutoNegAdvertisedBits. In either
    case, the currently operating duplex mode is
    reflected both in this object and in ifMauType.

    Note that this object provides redundant
    information with ifMauType. Normally, redundant
    objects are discouraged. However, in this
    instance, it allows a management application to
    determine the duplex status of an interface
    without having to know every possible value of
    ifMauType. This was felt to be sufficiently
    valuable to justify the redundancy.

    Description by oid_info

    dot3StatsDuplexStatus OBJECT-TYPE
    SYNTAX INTEGER {
    unknown(1),
    halfDuplex(2),
    fullDuplex(3)
    }
    MAX-ACCESS read-only
    STATUS current
    DESCRIPTION "The current mode of operation of the MAC
    entity. unknown indicates that the current
    duplex mode could not be determined.
    Management control of the duplex mode is
    accomplished through the MAU MIB. When
    an interface does not support autonegotiation,
    or when autonegotiation is not enabled, the
    duplex mode is controlled using
    ifMauDefaultType. When autonegotiation is
    supported and enabled, duplex mode is controlled
    using ifMauAutoNegAdvertisedBits. In either
    case, the currently operating duplex mode is
    reflected both in this object and in ifMauType.
    Note that this object provides redundant
    information with ifMauType. Normally, redundant
    objects are discouraged. However, in this
    instance, it allows a management application to
    determine the duplex status of an interface
    without having to know every possible value of
    ifMauType. This was felt to be sufficiently
    valuable to justify the redundancy."
    REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32,
    aDuplexStatus."

    View at oid-info.com

    Description by mibdepot

    The current mode of operation of the MAC
    entity. 'unknown' indicates that the current
    duplex mode could not be determined.


    Management control of the duplex mode is
    accomplished through the MAU MIB. When
    an interface does not support autonegotiation,
    or when autonegotiation is not enabled, the
    duplex mode is controlled using
    ifMauDefaultType. When autonegotiation is
    supported and enabled, duplex mode is controlled
    using ifMauAutoNegAdvertisedBits. In either
    case, the currently operating duplex mode is
    reflected both in this object and in ifMauType.

    Note that this object provides redundant
    information with ifMauType. Normally, redundant
    objects are discouraged. However, in this
    instance, it allows a management application to
    determine the duplex status of an interface
    without having to know every possible value of
    ifMauType. This was felt to be sufficiently
    valuable to justify the redundancy.

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

    Description by cisco

    The current mode of operation of the MAC
    entity. 'unknown' indicates that the current
    duplex mode could not be determined.

    Management control of the duplex mode is
    accomplished through the MAU MIB. When
    an interface does not support autonegotiation,
    or when autonegotiation is not enabled, the
    duplex mode is controlled using
    ifMauDefaultType. When autonegotiation is
    supported and enabled, duplex mode is controlled
    using ifMauAutoNegAdvertisedBits. In either
    case, the currently operating duplex mode is
    reflected both in this object and in ifMauType.

    Note that this object provides redundant
    information with ifMauType. Normally, redundant
    objects are discouraged. However, in this
    instance, it allows a management application to
    determine the duplex status of an interface
    without having to know every possible value of
    ifMauType. This was felt to be sufficiently
    valuable to justify the redundancy.

    Information by circitor

    dot3StatsDuplexStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), halfDuplex(2), fullDuplex(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, aDuplexStatus." ::= { dot3StatsEntry 19 }

    Information by cisco_v1

    dot3StatsDuplexStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), halfDuplex(2), fullDuplex(3) } ACCESS read-only STATUS mandatory DESCRIPTION "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, aDuplexStatus." ::= { dot3StatsEntry 19 }

    Information by oid_info

    Automatically extracted from RFC2665

    Information by mibdepot

    dot3StatsDuplexStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), halfDuplex(2), fullDuplex(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, aDuplexStatus." ::= { dot3StatsEntry 19 }

    Information by cisco

    dot3StatsDuplexStatus OBJECT-TYPE SYNTAX INTEGER { unknown(1), halfDuplex(2), fullDuplex(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current mode of operation of the MAC entity. 'unknown' indicates that the current duplex mode could not be determined. Management control of the duplex mode is accomplished through the MAU MIB. When an interface does not support autonegotiation, or when autonegotiation is not enabled, the duplex mode is controlled using ifMauDefaultType. When autonegotiation is supported and enabled, duplex mode is controlled using ifMauAutoNegAdvertisedBits. In either case, the currently operating duplex mode is reflected both in this object and in ifMauType. Note that this object provides redundant information with ifMauType. Normally, redundant objects are discouraged. However, in this instance, it allows a management application to determine the duplex status of an interface without having to know every possible value of ifMauType. This was felt to be sufficiently valuable to justify the redundancy." REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, aDuplexStatus." ::= { dot3StatsEntry 19 }

    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

    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.17 dot3StatsEtherChipSet 1 1 This object contains an OBJECT IDENTIFIER
    which identifies the chipset used to
    realize the interface. Ethernet-like
    interfaces are…
    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.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.