OID reference

h3cDot3OamPeerFunctionsSupported

1.3.6.1.4.1.2011.10.2.42.3.1.2.1.8

Description

The OAM functions supported on this Ethernet like interface. OAM consists of separate functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeer…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.2011.10.2.42.3.1.2.1 (h3cDot3OamPeerEntry)
Node code
8
Node name
h3cDot3OamPeerFunctionsSupported
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.8
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.42.3.1.2.1.8
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • {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) h3cDot3OamPeerTable(2) h3cDot3OamPeerEntry(1) h3cDot3OamPeerFunctionsSupported(8)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/42/3/1/2/1/8
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/42/3/1/2/1/8
  • /ISO/3/6/1/4/1/2011/10/2/42/3/1/2/1/8
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamPeerTable/h3cDot3OamPeerEntry/h3cDot3OamPeerFunctionsSupported
  • 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.2.1.8

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

h3cDot3OamPeerFunctionsSupported · current

h3cDot3OamPeerFunctionsSupported 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 functionality sets above the basic
          discovery process.  This value indicates the capabilities of
          the peer OAM entity with respect to these functions.  This
          value is initialized so all bits are clear, and is invalid if
          the h3cDot3OamPeerStatus is inactive.

          The capbilities of the OAM peer can be determined from the
          configuration field of the Local Information TLV of the most
          recently received Information OAMPDU with a Local Information
          TLV.

          An Information OAMPDU is indicated by a valid frame with (1)
          destination MAC address equal to that of the reserved MAC
          address for Slow Protocols (See 43B of [802.3ah]), (2) a
          lengthOrType field equal to the reserved type for Slow
          Protocols, (3) a Slow Protocols subtype equal to that of the
          subtype reserved for OAM, and (4) a OAM code that equals the
          code reserved for Information OAMPDUs.  "
        REFERENCE   "[802.3ah], REFERENCE 30.3.6.1.7."
        ::= { h3cDot3OamPeerEntry 8 }

h3cDot3OamPeerFunctionsSupported · current

h3cDot3OamPeerFunctionsSupported 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 functionality sets above the basic
          discovery process.  This value indicates the capabilities of
          the peer OAM entity with respect to these functions.  This
          value is initialized so all bits are clear, and is invalid if
          the h3cDot3OamPeerStatus is inactive.

          The capbilities of the OAM peer can be determined from the
          configuration field of the Local Information TLV of the most
          recently received Information OAMPDU with a Local Information
          TLV.

          An Information OAMPDU is indicated by a valid frame with (1)
          destination MAC address equal to that of the reserved MAC
          address for Slow Protocols (See 43B of [802.3ah]), (2) a
          lengthOrType field equal to the reserved type for Slow
          Protocols, (3) a Slow Protocols subtype equal to that of the
          subtype reserved for OAM, and (4) a OAM code that equals the
          code reserved for Information OAMPDUs."
        REFERENCE   "[802.3ah], REFERENCE 30.3.6.1.7."
        ::= { h3cDot3OamPeerEntry 8 }

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 functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeerStatus is inactive. The capbilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. An Information OAMPDU is indicated by a valid frame with (1) destination MAC address equal to that of the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a lengthOrType field equal to the reserved type for Slow Protocols, (3) a Slow Protocols subtype equal to that of the subtype reserved for OAM, and (4) a OAM code that equals the code reserved for 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

h3cDot3OamPeerFunctionsSupported · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: h3cDot3OamPeerFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamPeerFunctionsSupported",
    "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 functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeerStatus is inactive. The capbilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. An Information OAMPDU is indicated by a valid frame with (1) destination MAC address equal to that of the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a lengthOrType field equal to the reserved type for Slow Protocols, (3) a Slow Protocols subtype equal to that of the subtype reserved for OAM, and (4) a OAM code that equals the code reserved for Information OAMPDUs. \"",
    "REFERENCE",
    "\"[802.3ah], REFERENCE 30.3.6.1.7.\"",
    "::=",
    "{",
    "h3cDot3OamPeerEntry",
    "8",
    "}"
  ],
  "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 functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeerStatus is inactive. The capbilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. An Information OAMPDU is indicated by a valid frame with (1) destination MAC address equal to that of the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a lengthOrType field equal to the reserved type for Slow Protocols, (3) a Slow Protocols subtype equal to that of the subtype reserved for OAM, and (4) a OAM code that equals the code reserved for Information OAMPDUs."
    ],
    [
      "REFERENCE",
      "[802.3ah], REFERENCE 30.3.6.1.7."
    ],
    null,
    null,
    null
  ]
}
h3cDot3OamPeerFunctionsSupported · currentH3C and HH3C MIB copies (Observium Community)1 source

Status in source: current.

Names: h3cDot3OamPeerFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamPeerFunctionsSupported",
    "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 functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeerStatus is inactive. The capbilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. An Information OAMPDU is indicated by a valid frame with (1) destination MAC address equal to that of the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a lengthOrType field equal to the reserved type for Slow Protocols, (3) a Slow Protocols subtype equal to that of the subtype reserved for OAM, and (4) a OAM code that equals the code reserved for Information OAMPDUs.\"",
    "REFERENCE",
    "\"[802.3ah], REFERENCE 30.3.6.1.7.\"",
    "::=",
    "{",
    "h3cDot3OamPeerEntry",
    "8",
    "}"
  ],
  "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 functionality sets above the basic discovery process. This value indicates the capabilities of the peer OAM entity with respect to these functions. This value is initialized so all bits are clear, and is invalid if the h3cDot3OamPeerStatus is inactive. The capbilities of the OAM peer can be determined from the configuration field of the Local Information TLV of the most recently received Information OAMPDU with a Local Information TLV. An Information OAMPDU is indicated by a valid frame with (1) destination MAC address equal to that of the reserved MAC address for Slow Protocols (See 43B of [802.3ah]), (2) a lengthOrType field equal to the reserved type for Slow Protocols, (3) a Slow Protocols subtype equal to that of the subtype reserved for OAM, and (4) a OAM code that equals the code reserved for Information OAMPDUs."
    ],
    [
      "REFERENCE",
      "[802.3ah], REFERENCE 30.3.6.1.7."
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.2011)

Lwu Zhao

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.1 h3cDot3OamPeerStatus00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.2 h3cDot3OamPeerMacAddress00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.3 h3cDot3OamPeerVendorOui00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.4 h3cDot3OamPeerVendorInfo00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.5 h3cDot3OamPeerMode00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.6 h3cDot3OamPeerMaxOamPduSize00
1.3.6.1.4.1.2011.10.2.42.3.1.2.1.7 h3cDot3OamPeerConfigRevision00