OID reference

asDot3OamPeerFunctionsSupported

1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.9

Description

The OAM functions supported on the 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, the the peer OA…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1 (asDot3OamPeerEntry)
Node code
9
Node name
asDot3OamPeerFunctionsSupported
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.9
URN notation
urn:oid:1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.9
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 119 2 3 69 501 3 46 2 1 9}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) nec(119) nec-mib(2) necProductDepend(3) radioEquipment(69) pasoNeoIpe-common(501) alarmStatusGroup(3) asDot3OamGroup(46) asDot3OamPeerTable(2) asDot3OamPeerEntry(1) asDot3OamPeerFunctionsSupported(9)}
OID-IRI notation
  • /1/3/6/1/4/1/119/2/3/69/501/3/46/2/1/9
  • /ISO/Identified-Organization/6/1/4/1/119/2/3/69/501/3/46/2/1/9
  • /ISO/3/6/1/4/1/119/2/3/69/501/3/46/2/1/9
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported
  • /iso/iso-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPeerTable/asDot3OamPeerEntry/asDot3OamPeerFunctionsSupported

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

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.9

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.

asDot3OamPeerFunctionsSupported OBJECT-TYPE
        SYNTAX       BITS {
                         unidirectionalSupport(0),
                         loopbackSupport(1),
                         eventSupport(2),
                         variableSupport(3)
                     }
        MAX-ACCESS   read-only
        STATUS       current
        DESCRIPTION  
            "The OAM functions supported on the 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, the the peer OAM entity
            supports sending OAM frames on the 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 OAMPDUs to signal various error
            conditions. If variableSupport(3) is set, then the peer OAM
            entity can send and receive variable requests to monitor the
            attribute value.
            
            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."
        ::= { asDot3OamPeerEntry 9 }

Meaning

Descriptions

1 unique

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

The OAM functions supported on the 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, the the peer OAM entity supports sending OAM frames on the 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 OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value. 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

Multiple manufacturers; see the original MIB MIB copies (LibreNMS/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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 1 source

Description 1

asDot3OamPeerFunctionsSupported · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: asDot3OamPeerFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "asDot3OamPeerFunctionsSupported",
    "OBJECT-TYPE",
    "SYNTAX",
    "BITS",
    "{",
    "unidirectionalSupport",
    "(",
    "0",
    ")",
    ",",
    "loopbackSupport",
    "(",
    "1",
    ")",
    ",",
    "eventSupport",
    "(",
    "2",
    ")",
    ",",
    "variableSupport",
    "(",
    "3",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The OAM functions supported on the 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, the the peer OAM entity supports sending OAM frames on the 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 OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value. 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.\"",
    "::=",
    "{",
    "asDot3OamPeerEntry",
    "9",
    "}"
  ],
  "syntax_tree": [
    [
      "BITS",
      [
        [
          "unidirectionalSupport",
          0
        ],
        [
          "loopbackSupport",
          1
        ],
        [
          "eventSupport",
          2
        ],
        [
          "variableSupport",
          3
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The OAM functions supported on the 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, the the peer OAM entity supports sending OAM frames on the 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 OAMPDUs to signal various error conditions. If variableSupport(3) is set, then the peer OAM entity can send and receive variable requests to monitor the attribute value. 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."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.119)

Akiyama Yoshiyuki

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.1 asDot3OamPeerIfIndex00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.2 asDot3OamPeerNEAddress00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.3 asDot3OamPeerMacAddress00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.4 asDot3OamPeerVendorOui00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.5 asDot3OamPeerVendorInfo00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.6 asDot3OamPeerMode00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.7 asDot3OamPeerMaxOamPduSize00
1.3.6.1.4.1.119.2.3.69.501.3.46.2.1.8 asDot3OamPeerConfigRevision00