OID reference

dot3OamModeR

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

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

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

SNMP properties

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

Enumerated values

ValueName
1active
2passive

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

dot3OamModeR OBJECT-TYPE
        SYNTAX      INTEGER {
                      active(1),
                      passive(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 dot3OamMode is dependent on the type of
          system on which this Ethernet like interface resides.  The
          default value should be 'active(1)' 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 OAM PDUs (30.3.6.1.12) and
          potentially re-doing the OAM discovery process if the
          dot3OamOperStatus was already operational(9).
          "
        REFERENCE   "[802.3ah], 30.3.6.1.3"
        ::= { dot3OamEntryR 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 dot3OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(1)' 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 OAM PDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9).

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

dot3OamModeR · currentRAD MIB copies (Observium Community)1 source

Status in source: current.

Names: dot3OamModeR

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "dot3OamModeR",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "active",
    "(",
    "1",
    ")",
    ",",
    "passive",
    "(",
    "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 dot3OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(1)' 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 OAM PDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9). \"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.3\"",
    "::=",
    "{",
    "dot3OamEntryR",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "active",
            1
          ],
          [
            "passive",
            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 dot3OamMode is dependent on the type of system on which this Ethernet like interface resides. The default value should be 'active(1)' 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 OAM PDUs (30.3.6.1.12) and potentially re-doing the OAM discovery process if the dot3OamOperStatus was already operational(9)."
    ],
    [
      "REFERENCE",
      "[802.3ah], 30.3.6.1.3"
    ],
    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.4 dot3OamMaxOamPduSizeR00
1.3.6.1.4.1.164.20.7.1.1.1.5 dot3OamConfigRevisionR00
1.3.6.1.4.1.164.20.7.1.1.1.6 dot3OamFunctionsSupportedR00