OID reference

zxAnEthOamFunctionsSupported

1.3.6.1.4.1.3902.1015.61.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.3902.1015.61.1.1 (zxAnEthOamEntry)
Node code
6
Node name
zxAnEthOamFunctionsSupported
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.1015.61.1.1.6
URN notation
urn:oid:1.3.6.1.4.1.3902.1015.61.1.1.6
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 3902 1015 61 1 1 6}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zte(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zte(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) zxEnterpriseMib(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zte(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) zxEnterpriseMib(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zte(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) zxAn(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) zxEnterpriseMib(3902) msag(1015) zxAnEthOamObjects(61) zxAnEthOamTable(1) zxAnEthOamEntry(1) zxAnEthOamFunctionsSupported(6)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/3902/1015/61/1/1/6
  • /ISO/Identified-Organization/6/1/4/1/3902/1015/61/1/1/6
  • /ISO/3/6/1/4/1/3902/1015/61/1/1/6
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/3902/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/3902/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/zte/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/zte/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprise/zxEnterpriseMib/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/3902/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/3902/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/zte/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/zte/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/enterprises/zxEnterpriseMib/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/3902/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/zxAn/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/zte/msag/zxAnEthOamObjects/zxAnEthOamTable/zxAnEthOamEntry/zxAnEthOamFunctionsSupported
  • 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.3902.1015.61.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.

zxAnEthOamFunctionsSupported 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 
            OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports 
            the transmission of OAMPDUs on links that are operating in undirectional 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 OAMPDUs. Setting 
            'variableSupport(3)' indicates the OAM entity can send and receive Variable Request 
            and Response OAMPDUs. "
        ::= { zxAnEthOamEntry 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 OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAMPDUs on links that are operating in undirectional 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 OAMPDUs. Setting 'variableSupport(3)' indicates the OAM entity can send and receive Variable Request and Response OAMPDUs.

Sources for this description

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

Description 1

zxAnEthOamFunctionsSupported · currentZTE MIB copies (LibreNMS/Observium Community)1 source

Status in source: current.

Names: zxAnEthOamFunctionsSupported

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zxAnEthOamFunctionsSupported",
    "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 OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAMPDUs on links that are operating in undirectional 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 OAMPDUs. Setting 'variableSupport(3)' indicates the OAM entity can send and receive Variable Request and Response OAMPDUs. \"",
    "::=",
    "{",
    "zxAnEthOamEntry",
    "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 OAMPDUs. Setting 'unidirectionalSupport(0)' indicates that the OAM entity supports the transmission of OAMPDUs on links that are operating in undirectional 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 OAMPDUs. Setting 'variableSupport(3)' indicates 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.3902)

Xianlin Luo

Siblings (7)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.3902.1015.61.1.1.1 zxAnEthOamAdminState00
1.3.6.1.4.1.3902.1015.61.1.1.2 zxAnEthOamOperStatus00
1.3.6.1.4.1.3902.1015.61.1.1.3 zxAnEthOamMode00
1.3.6.1.4.1.3902.1015.61.1.1.4 zxAnEthOamMaxOamPduSize00
1.3.6.1.4.1.3902.1015.61.1.1.5 zxAnEthOamConfigRevision00
1.3.6.1.4.1.3902.1015.61.1.1.7 zxAnEthOamHardwareInfo00
1.3.6.1.4.1.3902.1015.61.1.1.8 zxAnEthOamSoftwareInfo00