OID reference

h3cDot3OamFunctionsSupported

1.3.6.1.4.1.2011.10.2.42.3.1.1.1.6

Description

The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2011.10.2.42.3.1.1.1 (h3cDot3OamEntry)
Node code
6
Node name
h3cDot3OamFunctionsSupported
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.42.3.1.1.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 42 3 1 1 1 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamFunctionsSupported(6)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/42/3/1/1/1/6
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/42/3/1/1/1/6
  • /ISO/3/6/1/4/1/2011/10/2/42/3/1/1/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamFunctionsSupported
  • Additional combinations skipped.

SNMP properties

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

Bit values

Bit positionName
0unidirectionalSupport
1loopbackSupport
2eventSupport
3variableSupport

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

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.2011.10.2.42.3.1.1.1.6

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.

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cDot3OamFunctionsSupported · current

h3cDot3OamFunctionsSupported OBJECT-TYPE
        SYNTAX      BITS {
                      unidirectionalSupport (0),
                      loopbackSupport(1),
                      eventSupport(2),
                      variableSupport(3)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The OAM functions supported on this Ethernet like interface.
          OAM consists of separate functional sets beyond the basic
          discovery process which is always required.  These functional
          groups can be supported independently by any implementation.
          These values are communicated to the peer via the local
          configuration field of Information OAMPDUs."
        REFERENCE   "[802.3ah], 30.3.6.1.6"
        ::= { h3cDot3OamEntry 6 }

h3cDot3OamFunctionsSupported · current

h3cDot3OamFunctionsSupported OBJECT-TYPE
        SYNTAX      BITS {
                      unidirectionalSupport (0),
                      loopbackSupport(1),
                      eventSupport(2),
                      variableSupport(3)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The OAM functions supported on this Ethernet like interface.
          OAM consists of separate functional sets beyond the basic
          discovery process which is always required.  These functional
          groups can be supported independently by any implementation.
          These values are communicated to the peer via the local
          configuration field of Information OAMPDUs.  "
        REFERENCE   "[802.3ah], 30.3.6.1.6"
        ::= { h3cDot3OamEntry 6 }

Meaning

Descriptions

1 unique

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

The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs.

Sources for this description

H3C and HH3C MIB copies (Observium Community)Netdisco MIB archive copies

See 2 matching source records

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1H3C and HH3C MIB copies (Observium Community), Netdisco MIB archive copies2 records · 2 sources

Description 1

h3cDot3OamFunctionsSupported · currentH3C and HH3C MIB copies (Observium Community)1 source

Status in source: current.

Names: h3cDot3OamFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamFunctionsSupported",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "unidirectionalSupport",
    "(",
    "0",
    ")",
    ",",
    "loopbackSupport",
    "(",
    "1",
    ")",
    ",",
    "eventSupport",
    "(",
    "2",
    ")",
    ",",
    "variableSupport",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs.\"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.6\"",
    "::=",
    "{",
    "h3cDot3OamEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "unidirectionalSupport",
          0
        ],
        [
          "loopbackSupport",
          1
        ],
        [
          "eventSupport",
          2
        ],
        [
          "variableSupport",
          3
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs."
    ],
    [
      "REFERENCE",
      "[802.3ah], 30.3.6.1.6"
    ],
    null,
    null,
    null
  ]
}
h3cDot3OamFunctionsSupported · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: h3cDot3OamFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamFunctionsSupported",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "unidirectionalSupport",
    "(",
    "0",
    ")",
    ",",
    "loopbackSupport",
    "(",
    "1",
    ")",
    ",",
    "eventSupport",
    "(",
    "2",
    ")",
    ",",
    "variableSupport",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs. \"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.6\"",
    "::=",
    "{",
    "h3cDot3OamEntry",
    "6",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "unidirectionalSupport",
          0
        ],
        [
          "loopbackSupport",
          1
        ],
        [
          "eventSupport",
          2
        ],
        [
          "variableSupport",
          3
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The OAM functions supported on this Ethernet like interface. OAM consists of separate functional sets beyond the basic discovery process which is always required. These functional groups can be supported independently by any implementation. These values are communicated to the peer via the local configuration field of Information OAMPDUs."
    ],
    [
      "REFERENCE",
      "[802.3ah], 30.3.6.1.6"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.1 h3cDot3OamAdminState00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.2 h3cDot3OamOperStatus00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.3 h3cDot3OamMode00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.4 h3cDot3OamMaxOamPduSize00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.5 h3cDot3OamConfigRevision00