OID reference

dot3StatsDuplexStatus

1.3.111.2.802.3.1.10.1.2.1.18

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…

Full description and source information

Identification

Identifier and names

Parent
1.3.111.2.802.3.1.10.1.2.1 (dot3StatsEntry)
Node code
18
Node name
dot3StatsDuplexStatus
Category
SNMP management object
Numeric OID
1.3.111.2.802.3.1.10.1.2.1.18
URN notation
urn:oid:1.3.111.2.802.3.1.10.1.2.1.18
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 111 2 802 3 1 10 1 2 1 18}

  • {iso(1) identified-organization(3) ieee(111) standards-association-numbered-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) identified-organization(3) ieee(111) standards-association-numbers-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) org(3) ieee(111) standards-association-numbered-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) org(3) ieee(111) standards-association-numbers-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) iso-identified-organization(3) ieee(111) standards-association-numbered-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) iso-identified-organization(3) ieee(111) standards-association-numbers-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) iso-organization(3) ieee(111) standards-association-numbered-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
  • {iso(1) iso-organization(3) ieee(111) standards-association-numbers-series-standards(2) lan-man-stds(802) ieee802dot3(3) ieee802dot3dot1mibs(1) ieee8023etherMIB(10) ieee8023etherMIBObjects(1) dot3StatsTable(2) dot3StatsEntry(1) dot3StatsDuplexStatus(18)}
OID-IRI notation
  • /1/3/111/2/802/3/1/10/1/2/1/18
  • /ISO/Identified-Organization/111/2/802/3/1/10/1/2/1/18
  • /ISO/3/111/2/802/3/1/10/1/2/1/18
Named path variants
  • /iso/identified-organization/ieee/standards-association-numbered-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/identified-organization/ieee/standards-association-numbers-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/org/ieee/standards-association-numbered-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/org/ieee/standards-association-numbers-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/iso-identified-organization/ieee/standards-association-numbered-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/iso-identified-organization/ieee/standards-association-numbers-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/iso-organization/ieee/standards-association-numbered-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus
  • /iso/iso-organization/ieee/standards-association-numbers-series-standards/lan-man-stds/ieee802dot3/ieee802dot3dot1mibs/ieee8023etherMIB/ieee8023etherMIBObjects/dot3StatsTable/dot3StatsEntry/dot3StatsDuplexStatus

SNMP properties

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

Enumerated values

ValueName
1unknown
2halfDuplex
3fullDuplex

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: dot3StatsIndex.

snmpwalk [connection options] DEVICE .1.3.111.2.802.3.1.10.1.2.1.18

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.

Product context

Documented MIB packages

The NETGEAR catalogue lists MIB files containing this definition with these product and release labels:

These are catalogue release labels, not necessarily MIB revisions. A MIB definition does not establish that a device implements it or permits access.

The displayed source records contain one distinct definition. Compare its source records.

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 Std 802.3, 30.3.1.1.32,
                       aDuplexStatus."
           ::= { dot3StatsEntry 18 }

Meaning

Descriptions

1 unique

Identical descriptions are grouped. Different wording and device-specific notes are retained.

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.

Sources for this description

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)HPE Instant On official MIBsNETGEAR official product and EOL MIB downloads

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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), HPE Instant On official MIBs, and others1 record · 3 sources

Description 1

dot3StatsDuplexStatus · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community), HPE Instant On official MIBs, and others3 sources

Status in source: current.

Names: dot3StatsDuplexStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "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 Std 802.3, 30.3.1.1.32, aDuplexStatus.\"",
    "::=",
    "{",
    "dot3StatsEntry",
    "18",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "unknown",
            1
          ],
          [
            "halfDuplex",
            2
          ],
          [
            "fullDuplex",
            3
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "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 Std 802.3, 30.3.1.1.32, aDuplexStatus."
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

Current Registration Authority (inferred from ancestor 1.3)

Frank Farance

Siblings (17)

OIDNameDirect childrenDescendantsDescription
1.3.111.2.802.3.1.10.1.2.1.1 dot3StatsIndex00
1.3.111.2.802.3.1.10.1.2.1.2 dot3StatsAlignmentErrors00
1.3.111.2.802.3.1.10.1.2.1.3 dot3StatsFCSErrors00
1.3.111.2.802.3.1.10.1.2.1.4 dot3StatsSingleCollisionFrames00
1.3.111.2.802.3.1.10.1.2.1.5 dot3StatsMultipleCollisionFrames00
1.3.111.2.802.3.1.10.1.2.1.6 dot3StatsSQETestErrors00
1.3.111.2.802.3.1.10.1.2.1.7 dot3StatsDeferredTransmissions00
1.3.111.2.802.3.1.10.1.2.1.8 dot3StatsLateCollisions00
1.3.111.2.802.3.1.10.1.2.1.9 dot3StatsExcessiveCollisions00
1.3.111.2.802.3.1.10.1.2.1.10 dot3StatsInternalMacTransmitErrors00
1.3.111.2.802.3.1.10.1.2.1.11 dot3StatsCarrierSenseErrors00
1.3.111.2.802.3.1.10.1.2.1.13 dot3StatsFrameTooLongs00
1.3.111.2.802.3.1.10.1.2.1.16 dot3StatsInternalMacReceiveErrors00
1.3.111.2.802.3.1.10.1.2.1.17 dot3StatsSymbolErrors00
1.3.111.2.802.3.1.10.1.2.1.19 dot3StatsRateControlAbility00
1.3.111.2.802.3.1.10.1.2.1.20 dot3StatsRateControlStatus00
1.3.111.2.802.3.1.10.1.2.1.21 dot3StatsMaxFrameLength00