OID reference

dot3OamPeerFunctionsSupportedR

1.3.6.1.4.1.164.20.7.1.2.1.7

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. If unidirectionalSupport(0) is set, …

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.164.20.7.1.2.1 (dot3OamPeerEntryR)
Node code
7
Node name
dot3OamPeerFunctionsSupportedR
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.164.20.7.1.2.1.7
URN notation
urn:oid:1.3.6.1.4.1.164.20.7.1.2.1.7
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 164 20 7 1 2 1 7}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) rad(164) radExperimental(20) dot3OamMIBR(7) dot3OamObjectsR(1) dot3OamPeerTableR(2) dot3OamPeerEntryR(1) dot3OamPeerFunctionsSupportedR(7)}
OID-IRI notation
  • /1/3/6/1/4/1/164/20/7/1/2/1/7
  • /ISO/Identified-Organization/6/1/4/1/164/20/7/1/2/1/7
  • /ISO/3/6/1/4/1/164/20/7/1/2/1/7
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/identified-organization/dod/internet/private/enterprises/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/identified-organization/dod/internet/private/vendor-objects/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/org/dod/internet/private/enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/org/dod/internet/private/enterprises/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/org/dod/internet/private/ldap-enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/org/dod/internet/private/vendor-objects/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-identified-organization/dod/internet/private/enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-identified-organization/dod/internet/private/enterprises/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-organization/dod/internet/private/enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-organization/dod/internet/private/enterprises/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR
  • /iso/iso-organization/dod/internet/private/vendor-objects/rad/radExperimental/dot3OamMIBR/dot3OamObjectsR/dot3OamPeerTableR/dot3OamPeerEntryR/dot3OamPeerFunctionsSupportedR

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.164.20.7.1.2.1.7

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.

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

dot3OamPeerFunctionsSupportedR 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.

          If unidirectionalSupport(0) is set, then the peer OAM entity
          supports sending OAM frames on Ethernet interfaces when the
          receive path is known to be inoperable.   If
          loopbackSupport(1) is set, then the peer OAM entity can send
          and receive OAM loopback commands.  If eventSupport(2) is set,
          then the peer OAM entity can send and receive event OAM PDUs to
          signal various error conditions. If variableSupport(3) is set,
          then the peer OAM entity can send and receive variable
          requests to monitor attribute value as described in Clause 57
          of [802.3ah].

          The capabilities 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.  All zeros are returned if no Local Information TLV has
          yet been received.
          "
        REFERENCE   "[802.3ah], REFERENCE 30.3.6.1.7."
        ::= { dot3OamPeerEntryR 7 }

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. If unidirectionalSupport(0) is set, then the peer OAM entity supports sending OAM frames on Ethernet interfaces when the receive path is known to be inoperable. If loopbackSupport(1) is set, then the peer OAM entity can send and receive OAM loopback commands. If eventSupport(2) is set, then the peer OAM entity can send and receive event OAM PDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor attribute value as described in Clause 57 of [802.3ah]. The capabilities 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. All zeros are returned if no Local Information TLV has yet been received.

Sources for this description

RAD MIB copies (Observium Community)

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 1RAD MIB copies (Observium Community)1 record · 1 source

Description 1

dot3OamPeerFunctionsSupportedR · currentRAD MIB copies (Observium Community)1 source

Status in source: current.

Names: dot3OamPeerFunctionsSupportedR

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dot3OamPeerFunctionsSupportedR",
    "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. If unidirectionalSupport(0) is set, then the peer OAM entity supports sending OAM frames on Ethernet interfaces when the receive path is known to be inoperable. If loopbackSupport(1) is set, then the peer OAM entity can send and receive OAM loopback commands. If eventSupport(2) is set, then the peer OAM entity can send and receive event OAM PDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor attribute value as described in Clause 57 of [802.3ah]. The capabilities 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. All zeros are returned if no Local Information TLV has yet been received. \"",
    "REFERENCE",
    "\"[802.3ah], REFERENCE 30.3.6.1.7.\"",
    "::=",
    "{",
    "dot3OamPeerEntryR",
    "7",
    "}"
  ],
  "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. If unidirectionalSupport(0) is set, then the peer OAM entity supports sending OAM frames on Ethernet interfaces when the receive path is known to be inoperable. If loopbackSupport(1) is set, then the peer OAM entity can send and receive OAM loopback commands. If eventSupport(2) is set, then the peer OAM entity can send and receive event OAM PDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor attribute value as described in Clause 57 of [802.3ah]. The capabilities 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. All zeros are returned if no Local Information TLV has yet been received."
    ],
    [
      "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.164)

Brighitte Shalom

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.164)

Smadar Tauber

Siblings (6)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.164.20.7.1.2.1.1 dot3OamPeerMacAddressR00
1.3.6.1.4.1.164.20.7.1.2.1.2 dot3OamPeerVendorOuiR00
1.3.6.1.4.1.164.20.7.1.2.1.3 dot3OamPeerVendorInfoR00
1.3.6.1.4.1.164.20.7.1.2.1.4 dot3OamPeerModeR00
1.3.6.1.4.1.164.20.7.1.2.1.5 dot3OamPeerMaxOamPduSizeR00
1.3.6.1.4.1.164.20.7.1.2.1.6 dot3OamPeerConfigRevisionR00