OID reference

asDot3OamPortFunctionsSupported

1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.6

Description

The OAM functions supported on this interface. OAM consists of separate functional sets beyond the basic discovery process that 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 OA…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1 (asDot3OamPortEntry)
Node code
6
Node name
asDot3OamPortFunctionsSupported
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
  • {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) asDot3OamPortTable(1) asDot3OamPortEntry(1) asDot3OamPortFunctionsSupported(6)}
OID-IRI notation
  • /1/3/6/1/4/1/119/2/3/69/501/3/46/1/1/6
  • /ISO/Identified-Organization/6/1/4/1/119/2/3/69/501/3/46/1/1/6
  • /ISO/3/6/1/4/1/119/2/3/69/501/3/46/1/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/org/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/org/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/org/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/org/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-identified-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-organization/dod/internet/private/enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-organization/dod/internet/private/enterprises/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-organization/dod/internet/private/ldap-enterprise/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported
  • /iso/iso-organization/dod/internet/private/vendor-objects/nec/nec-mib/necProductDepend/radioEquipment/pasoNeoIpe-common/alarmStatusGroup/asDot3OamGroup/asDot3OamPortTable/asDot3OamPortEntry/asDot3OamPortFunctionsSupported

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

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.119.2.3.69.501.3.46.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.

asDot3OamPortFunctionsSupported 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 interface. OAM consists of
            separate functional sets beyond the basic discovery process that
            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.
            
            Setting unidirectionalSupport(0) indicates that the OA entity
            supports the transmission of OAMPDUs on links that are operating
            in unidirectional mode. Setting loopbackSupport(1) indicates that
            the OAM entity can initiate and respond to loopback commands.
            Setting eventSupport(2) indicates that the OAM entity can send
            and receive Event Notification OAMPDUs. Setting
            variableSupport(3) indicates that the OAM entity can send and
            receive Variable Request and Response OAMPDUs."
        ::= { asDot3OamPortEntry 6 }

Meaning

Descriptions

1 unique

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

The OAM functions supported on this interface. OAM consists of separate functional sets beyond the basic discovery process that 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. Setting unidirectionalSupport(0) indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode. Setting loopbackSupport(1) indicates that the OAM entity can initiate and respond to loopback commands. Setting eventSupport(2) indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting variableSupport(3) indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs.

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

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

Status in source: current.

Names: asDot3OamPortFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "asDot3OamPortFunctionsSupported",
    "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 interface. OAM consists of separate functional sets beyond the basic discovery process that 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. Setting unidirectionalSupport(0) indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode. Setting loopbackSupport(1) indicates that the OAM entity can initiate and respond to loopback commands. Setting eventSupport(2) indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting variableSupport(3) indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs.\"",
    "::=",
    "{",
    "asDot3OamPortEntry",
    "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 interface. OAM consists of separate functional sets beyond the basic discovery process that 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. Setting unidirectionalSupport(0) indicates that the OA entity supports the transmission of OAMPDUs on links that are operating in unidirectional mode. Setting loopbackSupport(1) indicates that the OAM entity can initiate and respond to loopback commands. Setting eventSupport(2) indicates that the OAM entity can send and receive Event Notification OAMPDUs. Setting variableSupport(3) indicates that the OAM entity can send and receive Variable Request and Response OAMPDUs."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.119)

Akiyama Yoshiyuki

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.1 asDot3OamPortIfIndex00
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.2 asDot3OamPortNEAddress00
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.3 asDot3OamPortOperStatus00
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.4 asDot3OamPortMaxOamPduSize00
1.3.6.1.4.1.119.2.3.69.501.3.46.1.1.5 asDot3OamPortConfigRevision00