OID reference

h3cDot3OamMode

1.3.6.1.4.1.2011.10.2.42.3.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.2011.10.2.42.3.1.1.1 (h3cDot3OamEntry)
Node code
3
Node name
h3cDot3OamMode
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.3
URN notation
urn:oid:1.3.6.1.4.1.2011.10.2.42.3.1.1.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 2011 10 2 42 3 1 1 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) huawei(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) iMAP(2011) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamTable(1) h3cDot3OamEntry(1) h3cDot3OamMode(3)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/2011/10/2/42/3/1/1/1/3
  • /ISO/Identified-Organization/6/1/4/1/2011/10/2/42/3/1/1/1/3
  • /ISO/3/6/1/4/1/2011/10/2/42/3/1/1/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/identified-organization/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/enterprises/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/enterprises/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/ldap-enterprise/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/ldap-enterprise/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/vendor-objects/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • /iso/org/dod/internet/private/vendor-objects/iMAP/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamTable/h3cDot3OamEntry/h3cDot3OamMode
  • Additional combinations skipped.

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

Available source records contain 2 distinct definitions; some records may not include a definition.

Show 2 published definitions

h3cDot3OamMode · current

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

          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
          h3cDot3OamOperStatus was already operational(9).  "
        REFERENCE   "[802.3ah], 30.3.6.1.3"
        ::= { h3cDot3OamEntry 3 }

h3cDot3OamMode · current

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

          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
          h3cDot3OamOperStatus was already operational(9)."
        REFERENCE   "[802.3ah], 30.3.6.1.3"
        ::= { h3cDot3OamEntry 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. 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 h3cDot3OamOperStatus was already operational(9).

Sources for this description

H3C and HH3C MIB copies (Observium Community)Netdisco MIB archive copies

See 2 matching source records

Evidence

Source records

2 records

Matching descriptions are grouped; open a group to compare definitions and supporting files.

Records for description 1H3C and HH3C MIB copies (Observium Community), Netdisco MIB archive copies2 records · 2 sources

Description 1

h3cDot3OamMode · currentNetdisco MIB archive copies1 source

Status in source: current.

Names: h3cDot3OamMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamMode",
    "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. 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 h3cDot3OamOperStatus was already operational(9). \"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.3\"",
    "::=",
    "{",
    "h3cDot3OamEntry",
    "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. 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 h3cDot3OamOperStatus was already operational(9)."
    ],
    [
      "REFERENCE",
      "[802.3ah], 30.3.6.1.3"
    ],
    null,
    null,
    null
  ]
}
h3cDot3OamMode · currentH3C and HH3C MIB copies (Observium Community)1 source

Status in source: current.

Names: h3cDot3OamMode

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamMode",
    "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. 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 h3cDot3OamOperStatus was already operational(9).\"",
    "REFERENCE",
    "\"[802.3ah], 30.3.6.1.3\"",
    "::=",
    "{",
    "h3cDot3OamEntry",
    "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. 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 h3cDot3OamOperStatus 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.2011)

Lwu Zhao

Siblings (5)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.1 h3cDot3OamAdminState00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.2 h3cDot3OamOperStatus00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.4 h3cDot3OamMaxOamPduSize00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.5 h3cDot3OamConfigRevision00
1.3.6.1.4.1.2011.10.2.42.3.1.1.1.6 h3cDot3OamFunctionsSupported00