OID reference

dot3OamFunctionsSupportedR

1.3.6.1.4.1.164.20.7.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.164.20.7.1.1.1 (dot3OamEntryR)
Node code
6
Node name
dot3OamFunctionsSupportedR
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.164.20.7.1.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.164.20.7.1.1.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

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

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

dot3OamFunctionsSupportedR 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 OAM PDUs.

          Setting 'unidirectionalSupport(0)' indicates that the OAM
          entity supports the transmission of OAM PDUs on links that are
          operating in unidirectional mode (traffic flowing in one
          direction only).  Setting 'loopbackSupport(1)' indicates the
          OAM entity can initiate and respond to loopback commands.
          Setting 'eventSupport(2)' indicates the OAM entity can send
          and receive Event Notification OAM PDUs. Setting
          'variableSupport(3)' indicates the OAM entity can send and
          receive Variable Request and Response OAM PDUs.
          "
        REFERENCE   "[802.3ah], 30.3.6.1.6"
        ::= { dot3OamEntryR 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 OAM PDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAM PDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates the OAM entity can send and receive Event Notification OAM PDUs. Setting 'variableSupport(3)' indicates the OAM entity can send and receive Variable Request and Response OAM PDUs.

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

dot3OamFunctionsSupportedR · currentRAD MIB copies (Observium Community)1 source

Status in source: current.

Names: dot3OamFunctionsSupportedR

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dot3OamFunctionsSupportedR",
    "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 OAM PDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAM PDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates the OAM entity can send and receive Event Notification OAM PDUs. Setting 'variableSupport(3)' indicates the OAM entity can send and receive Variable Request and Response OAM PDUs. \"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.6\"",
    "::=",
    "{",
    "dot3OamEntryR",
    "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 OAM PDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAM PDUs on links that are operating in unidirectional mode (traffic flowing in one direction only). Setting 'loopbackSupport(1)' indicates the OAM entity can initiate and respond to loopback commands. Setting 'eventSupport(2)' indicates the OAM entity can send and receive Event Notification OAM PDUs. Setting 'variableSupport(3)' indicates the OAM entity can send and receive Variable Request and Response OAM PDUs."
    ],
    [
      "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.164)

Brighitte Shalom

Current Registration Authority (inferred from ancestor 1.3.6.1.4.1.164)

Smadar Tauber

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.164.20.7.1.1.1.1 dot3OamAdminStateR00
1.3.6.1.4.1.164.20.7.1.1.1.2 dot3OamOperStatusR00
1.3.6.1.4.1.164.20.7.1.1.1.3 dot3OamModeR00
1.3.6.1.4.1.164.20.7.1.1.1.4 dot3OamMaxOamPduSizeR00
1.3.6.1.4.1.164.20.7.1.1.1.5 dot3OamConfigRevisionR00