OID reference

h3cDot3OamLoopbackStatus

1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1.2

Description

The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). If the O…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1 (h3cDot3OamLoopbackEntry)
Node code
2
Node name
h3cDot3OamLoopbackStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1.2
URN notation
urn:oid:1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1.2
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 43 45 1 10 2 42 3 1 3 1 2}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3Com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) a3com(43) jv-mib(45) huawei(1) h3c(10) h3cCommon(2) h3cEpon(42) h3cEfmOamMIB(3) h3cDot3OamMIB(1) h3cDot3OamLoopbackTable(3) h3cDot3OamLoopbackEntry(1) h3cDot3OamLoopbackStatus(2)}
  • Additional combinations skipped.
OID-IRI notation
  • /1/3/6/1/4/1/43/45/1/10/2/42/3/1/3/1/2
  • /ISO/Identified-Organization/6/1/4/1/43/45/1/10/2/42/3/1/3/1/2
  • /ISO/3/6/1/4/1/43/45/1/10/2/42/3/1/3/1/2
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/enterprises/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/enterprises/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/ldap-enterprise/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/ldap-enterprise/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/vendor-objects/a3Com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • /iso/org/dod/internet/private/vendor-objects/a3com/jv-mib/huawei/h3c/h3cCommon/h3cEpon/h3cEfmOamMIB/h3cDot3OamMIB/h3cDot3OamLoopbackTable/h3cDot3OamLoopbackEntry/h3cDot3OamLoopbackStatus
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1noLoopback
2initiatingLoopback
3remoteLoopback
4terminatingLoopback
5localLoopback
6unknown

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

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

h3cDot3OamLoopbackStatus · current

h3cDot3OamLoopbackStatus OBJECT-TYPE
        SYNTAX      INTEGER {
                      noLoopback (1),
                      initiatingLoopback (2),
                      remoteLoopback (3),
                      terminatingLoopback (4),
                      localLoopback (5),
                      unknown (6)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The loopback status of the OAM entity.  This status is
          determined by a combination of the local parser and
          multiplexer states, the remote parser and multiplexer states,
          as well as by the actions of the local OAM client.  When
          operating in normal mode with no loopback in progress, the
          status reads noLoopback(1).

          If the OAM client has sent an Loopback OAMPDU and is waiting
          for a response, where the local parser and multiplexer states
          are DISCARD (see [802.3ah, 57.2.11.1]), the status is
          'initiatingLoopback'.  In this case, the local OAM entity has
          yet to receive any acknowledgement that the remote OAM entity
          has received its loopback command request.

          If the local OAM client knows that the remote OAM entity is in
          loopback mode (via the remote state information as described
          in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
          remoteLoopback(3).  If the local OAM client is in the process
          of terminating the remote loopback [802.3ah, 57.2.11.3,
          30.3.6.1.14], with its local multiplexer and parser states in
          DISCARD, the status is terminatingLoopback(4).  If the remote
          OAM client has put the local OAM entity in loopback mode as
          indicated by its local parser state, the status is
          localLoopback(5).

          The unknown(6) status indicates the parser and multiplexer
          combination is unexpected.  This status may be returned if the
          OAM loopback is in a transition state but should not persist.

          The values of this attribute correspond to the following
          values of the local and remote parser and multiplexer states.

            value            LclPrsr   LclMux    RmtPrsr   RmtMux
            noLoopback         FWD       FWD       FWD       FWD
            initLoopback     DISCARD   DISCARD     FWD       FWD
            rmtLoopback      DISCARD     FWD      LPBK    DISCARD
            tmtngLoopback    DISCARD   DISCARD    LPBK    DISCARD
            lclLoopback        LPBK    DISCARD   DISCARD     FWD
            unknown            ***   any other combination   ***
          "
        REFERENCE   "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
          30.3.6.1.15"
        ::= { h3cDot3OamLoopbackEntry 2 }

h3cDot3OamLoopbackStatus · current

h3cDot3OamLoopbackStatus OBJECT-TYPE
        SYNTAX      INTEGER {
                      noLoopback (1),
                      initiatingLoopback (2),
                      remoteLoopback (3),
                      terminatingLoopback (4),
                      localLoopback (5),
                      unknown (6)
                    }
        MAX-ACCESS  read-only
        STATUS      current
        DESCRIPTION
          "The loopback status of the OAM entity.  This status is
          determined by a combination of the local parser and
          multiplexer states, the remote parser and multiplexer states,
          as well as by the actions of the local OAM client.  When
          operating in normal mode with no loopback in progress, the
          status reads noLoopback(1).

          If the OAM client has sent an Loopback OAMPDU and is waiting
          for a response, where the local parser and multiplexer states
          are DISCARD (see [802.3ah, 57.2.11.1]), the status is
          'initiatingLoopback'.  In this case, the local OAM entity has
          yet to receive any acknowledgement that the remote OAM entity
          has received its loopback command request.

          If the local OAM client knows that the remote OAM entity is in
          loopback mode (via the remote state information as described
          in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is
          remoteLoopback(3).  If the local OAM client is in the process
          of terminating the remote loopback [802.3ah, 57.2.11.3,
          30.3.6.1.14], with its local multiplexer and parser states in
          DISCARD, the status is terminatingLoopback(4).  If the remote
          OAM client has put the local OAM entity in loopback mode as
          indicated by its local parser state, the status is
          localLoopback(5).

          The unknown(6) status indicates the parser and multiplexer
          combination is unexpected.  This status may be returned if the
          OAM loopback is in a transition state but should not persist.

          The values of this attribute correspond to the following
          values of the local and remote parser and multiplexer states.

            value            LclPrsr   LclMux    RmtPrsr   RmtMux
            noLoopback         FWD       FWD       FWD       FWD
            initLoopback     DISCARD   DISCARD     FWD       FWD
            rmtLoopback      DISCARD     FWD      LPBK    DISCARD
            tmtngLoopback    DISCARD   DISCARD    LPBK    DISCARD
            lclLoopback        LPBK    DISCARD   DISCARD     FWD
            unknown            ***   any other combination   ***
          "
        REFERENCE   "[802.3ah], REFERENCE 57.2.11, 30.3.61.14,
          30.3.6.1.15"
        ::= { h3cDot3OamLoopbackEntry 2 }

Meaning

Descriptions

1 unique

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

The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). If the OAM client has sent an Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgement that the remote OAM entity has received its loopback command request. If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14], with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5). The unknown(6) status indicates the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist. The values of this attribute correspond to the following values of the local and remote parser and multiplexer states. value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination ***

Sources for this description

3Com MIB copies (LibreNMS/Observium Community)Netdisco MIB archive copies

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 13Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies1 record · 2 sources

Description 1

h3cDot3OamLoopbackStatus · current3Com MIB copies (LibreNMS/Observium Community), Netdisco MIB archive copies2 sources

Status in source: current.

Names: h3cDot3OamLoopbackStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "h3cDot3OamLoopbackStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "noLoopback",
    "(",
    "1",
    ")",
    ",",
    "initiatingLoopback",
    "(",
    "2",
    ")",
    ",",
    "remoteLoopback",
    "(",
    "3",
    ")",
    ",",
    "terminatingLoopback",
    "(",
    "4",
    ")",
    ",",
    "localLoopback",
    "(",
    "5",
    ")",
    ",",
    "unknown",
    "(",
    "6",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). If the OAM client has sent an Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgement that the remote OAM entity has received its loopback command request. If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14], with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5). The unknown(6) status indicates the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist. The values of this attribute correspond to the following values of the local and remote parser and multiplexer states. value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination *** \"",
    "REFERENCE",
    "\"[802.3ah], REFERENCE 57.2.11, 30.3.61.14, 30.3.6.1.15\"",
    "::=",
    "{",
    "h3cDot3OamLoopbackEntry",
    "2",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "noLoopback",
            1
          ],
          [
            "initiatingLoopback",
            2
          ],
          [
            "remoteLoopback",
            3
          ],
          [
            "terminatingLoopback",
            4
          ],
          [
            "localLoopback",
            5
          ],
          [
            "unknown",
            6
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "The loopback status of the OAM entity. This status is determined by a combination of the local parser and multiplexer states, the remote parser and multiplexer states, as well as by the actions of the local OAM client. When operating in normal mode with no loopback in progress, the status reads noLoopback(1). If the OAM client has sent an Loopback OAMPDU and is waiting for a response, where the local parser and multiplexer states are DISCARD (see [802.3ah, 57.2.11.1]), the status is 'initiatingLoopback'. In this case, the local OAM entity has yet to receive any acknowledgement that the remote OAM entity has received its loopback command request. If the local OAM client knows that the remote OAM entity is in loopback mode (via the remote state information as described in [802.3ah, 57.2.11.1, 30.3.6.1.15]), the status is remoteLoopback(3). If the local OAM client is in the process of terminating the remote loopback [802.3ah, 57.2.11.3, 30.3.6.1.14], with its local multiplexer and parser states in DISCARD, the status is terminatingLoopback(4). If the remote OAM client has put the local OAM entity in loopback mode as indicated by its local parser state, the status is localLoopback(5). The unknown(6) status indicates the parser and multiplexer combination is unexpected. This status may be returned if the OAM loopback is in a transition state but should not persist. The values of this attribute correspond to the following values of the local and remote parser and multiplexer states. value LclPrsr LclMux RmtPrsr RmtMux noLoopback FWD FWD FWD FWD initLoopback DISCARD DISCARD FWD FWD rmtLoopback DISCARD FWD LPBK DISCARD tmtngLoopback DISCARD DISCARD LPBK DISCARD lclLoopback LPBK DISCARD DISCARD FWD unknown *** any other combination ***"
    ],
    [
      "REFERENCE",
      "[802.3ah], REFERENCE 57.2.11, 30.3.61.14, 30.3.6.1.15"
    ],
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.43)

Jeremy Siegel

Siblings (2)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1.1 h3cDot3OamLoopbackCommand00
1.3.6.1.4.1.43.45.1.10.2.42.3.1.3.1.3 h3cDot3OamLoopbackIgnoreRx00