OID reference

zxAnEthOamMode

1.3.6.1.4.1.3902.1015.61.1.1.3

Description

This object configures the mode of OAM operation for this Ethernet like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode gene…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.3902.1015.61.1.1 (zxAnEthOamEntry)
Node code
3
Node name
zxAnEthOamMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.3902.1015.61.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.3902.1015.61.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

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

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

SNMP properties

Value type
INTEGER
Maximum access defined by MIB
read-write
Status in MIB
current

Enumerated values

ValueName
1passive
2active

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

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.

zxAnEthOamMode OBJECT-TYPE 
        SYNTAX       INTEGER{ 
                     passive(1), 
                     active(2)
                     }                           
        MAX-ACCESS   read-write
        STATUS       current 
        DESCRIPTION
            "This object configures the mode of OAM operation for this Ethernet like interface. 
             OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes 
             differ in that active mode provides additional capabilities to initiate monitoring 
             activities with the remote OAM peer entity, while passive mode generally waits for 
             the peer to initiate OAM actions with it. As an example, an active OAM entity can 
             put the remote OAM entity in a loopback state, where a passive OAM entity cannot. 
             The default value of OamMode is dependent on the type of system on which this 
             Ethernet like interface resides. The default value should be 'active(2)' unless it 
             is known that this system should take on a subservient role to the other device 
             connected over this interface. Changing this value results in incrementing the 
             configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and 
             potentially re-doing the OAM discovery process if the OamOperStatus was already 
             operational(9)."
        ::= { zxAnEthOamEntry 3 }

Meaning

Descriptions

1 unique

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

This object configures the mode of OAM operation for this Ethernet like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OAM actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OAM entity cannot. The default value of OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the OamOperStatus was already operational(9).

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

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

Status in source: current.

Names: zxAnEthOamMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "zxAnEthOamMode",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "passive",
    "(",
    "1",
    ")",
    ",",
    "active",
    "(",
    "2",
    ")",
    "}",
    "MAX-ACCESS",
    "read-write",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"This object configures the mode of OAM operation for this Ethernet like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OAM actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OAM entity cannot. The default value of OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the OamOperStatus was already operational(9).\"",
    "::=",
    "{",
    "zxAnEthOamEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "passive",
            1
          ],
          [
            "active",
            2
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-write"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "This object configures the mode of OAM operation for this Ethernet like interface. OAM on Ethernet interfaces may be in 'active' mode or 'passive' mode. These two modes differ in that active mode provides additional capabilities to initiate monitoring activities with the remote OAM peer entity, while passive mode generally waits for the peer to initiate OAM actions with it. As an example, an active OAM entity can put the remote OAM entity in a loopback state, where a passive OAM entity cannot. The default value of OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(2)' unless it is known that this system should take on a subservient role to the other device connected over this interface. Changing this value results in incrementing the configuration revision field of locally generated OAMPDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the OamOperStatus was already operational(9)."
    ],
    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.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.6 zxAnEthOamFunctionsSupported00
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