OID reference

cienaCesOamOperStatus

1.3.6.1.4.1.1271.2.3.5.1.1.4.1.3

Description

At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OAM sub layer. This value is always disabled(1) if OAM is disabled on this inter…

Full description and source information

Identification

Identifier and names

Parent
1.3.6.1.4.1.1271.2.3.5.1.1.4.1 (cienaCesOamEntry)
Node code
3
Node name
cienaCesOamOperStatus
Category
SNMP management object
Numeric OID
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.3
URN notation
urn:oid:1.3.6.1.4.1.1271.2.3.5.1.1.4.1.3
ASN.1, OID-IRI and named path variants
ASN.1 notation

{1 3 6 1 4 1 1271 2 3 5 1 1 4 1 3}

  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) enterprises(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) org(3) dod(6) internet(1) private(4) vendor-objects(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) enterprises(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-identified-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) enterprises(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) ldap-enterprise(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
  • {iso(1) iso-organization(3) dod(6) internet(1) private(4) vendor-objects(1) ciena(1271) cienaCes(2) cienaCesStatistics(3) cienaCesOamMibModule(5) cienaCesOamMIB(1) cienaCesOamStatistics(1) cienaCesOamTable(4) cienaCesOamEntry(1) cienaCesOamOperStatus(3)}
OID-IRI notation
  • /1/3/6/1/4/1/1271/2/3/5/1/1/4/1/3
  • /ISO/Identified-Organization/6/1/4/1/1271/2/3/5/1/1/4/1/3
  • /ISO/3/6/1/4/1/1271/2/3/5/1/1/4/1/3
Named path variants
  • /iso/identified-organization/dod/internet/private/enterprise/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/enterprise/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/enterprises/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/enterprises/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/ldap-enterprise/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/identified-organization/dod/internet/private/vendor-objects/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/enterprise/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/enterprise/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/enterprises/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/enterprises/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/ldap-enterprise/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/ldap-enterprise/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/vendor-objects/1271/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • /iso/org/dod/internet/private/vendor-objects/ciena/cienaCes/cienaCesStatistics/cienaCesOamMibModule/cienaCesOamMIB/cienaCesOamStatistics/cienaCesOamTable/cienaCesOamEntry/cienaCesOamOperStatus
  • Additional combinations skipped.

SNMP properties

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

Enumerated values

ValueName
1disabled
2linkfault
3passiveWait
4activeSendLocal
5sendLocalAndRemote
6sendLocalAndRemoteOk
7oamPeeringLocallyRejected
8oamPeeringRemotelyRejected
9operational

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.

In CIENA-CES-OAM-MIB, the row index cienaCesOamPort is declared as Integer32. A non-negative index value is encoded as one numeric subidentifier. An instance has the form .1.3.6.1.4.1.1271.2.3.5.1.1.4.1.3.<cienaCesOamPort>. Use an index value actually present on the device and permitted by its MIB. Other definitions can differ.

snmpwalk [connection options] DEVICE .1.3.6.1.4.1.1271.2.3.5.1.1.4.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.

cienaCesOamOperStatus OBJECT-TYPE
                        SYNTAX INTEGER
                                {
                                disabled(1),
                                linkfault(2),
                                passiveWait(3),
                                activeSendLocal(4),
                                sendLocalAndRemote(5),
                                sendLocalAndRemoteOk(6),
                                oamPeeringLocallyRejected(7),
                                oamPeeringRemotelyRejected(8),
                                operational(9)
                                }
                        MAX-ACCESS read-only
                        STATUS current
                        DESCRIPTION
                                "At initialization and failure conditions, two OAM entities on
                                         the same full-duplex Ethernet link begin a discovery phase to
                                         determine what OAM capabilities may be used on that link.  The
                                         progress of this initialization is controlled by the OAM
                                         sub layer.  
                                                    
                                         This value is always disabled(1) if OAM is disabled on this
                                         interface via the cienaCesOamAdminState.  
                                  
                                         If the link has detected a fault and is transmitting OAMPDUs
                                         with a link fault indication, the value is linkFault(2). 
                                                          
                                         The passiveWait(3) state is returned only by OAM entities in
                                         passive mode (cienaCesOamMode) and reflects the state in which the
                                         OAM entity is waiting to see if the peer device is OAM
                                         capable.  The activeSendLocal(4) is used by active mode
                                         devices (cienaCesOamMode) and reflects the OAM entity actively
                                         trying to discover whether the peer has OAM capability but has
                                         not yet made that determination.
                                                          
                                         The state sendLocalAndRemote(5) indicates that the local OAM
                                         entity has discovered the peer but has not yet accepted or
                                         rejected the configuration of the peer.  The local device can,
                                         for whatever reason, decide that the peer device is
                                         unacceptable and decline OAM peering.  If the local OAM entity
                                         rejects the peer OAM entity, the state becomes
                                         oamPeeringLocallyRejected(7).  If the OAM peering is allowed
                                         by the local device, the state moves to
                                         sendLocalAndRemoteOk(6).  Note that both the
                                         sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states
                                         fall within the state SEND_LOCAL_REMOTE of the Discovery state
                                         diagram [802.3ah, Figure 57-5], with the difference being
                                         whether the local OAM client has actively rejected the peering
                                         or has just not indicated any decision yet.  Whether a peering
                                         decision has been made is indicated via the local flags field
                                         in the OAMPDU (reflected in the aOAMLocalFlagsField of
                                         30.3.6.1.10).  
                                  
                                         If the remote OAM entity rejects the peering, the state
                                         becomes oamPeeringRemotelyRejected(8).  Note that both the
                                         sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8)
                                         states fall within the state SEND_LOCAL_REMOTE_OK of the
                                         Discovery state diagram [802.3ah, Figure 57-5], with the
                                         difference being whether the remote OAM client has rejected
                                         the peering or has just not yet decided.  This is indicated
                                         via the remote flags field in the OAM PDU (reflected in the
                                         aOAMRemoteFlagsField of 30.3.6.1.11).  
                                                          
                                         When the local OAM entity learns that both it and the remote
                                         OAM entity have accepted the peering, the state moves to
                                         operational(9) corresponding to the SEND_ANY state of the
                                         Discovery state diagram [802.3ah, Figure 57-5]."
                        ::= { cienaCesOamEntry 3 }

Meaning

Descriptions

1 unique

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

At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OAM sub layer. This value is always disabled(1) if OAM is disabled on this interface via the cienaCesOamAdminState. If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault(2). The passiveWait(3) state is returned only by OAM entities in passive mode (cienaCesOamMode) and reflects the state in which the OAM entity is waiting to see if the peer device is OAM capable. The activeSendLocal(4) is used by active mode devices (cienaCesOamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination. The state sendLocalAndRemote(5) indicates that the local OAM entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowed by the local device, the state moves to sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected(8). Note that both the sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAM PDU (reflected in the aOAMRemoteFlagsField of 30.3.6.1.11). When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5].

Sources for this description

Multiple manufacturers; see the original MIB 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 1Multiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)1 record · 2 sources

Description 1

cienaCesOamOperStatus · currentMultiple manufacturers; see the original MIB MIB copies (LibreNMS/Observium Community)2 sources

Status in source: current.

Names: cienaCesOamOperStatus

Technical details
{
  "smi_kind": "OBJECT-TYPE",
  "definition": [
    "cienaCesOamOperStatus",
    "OBJECT-TYPE",
    "SYNTAX",
    "INTEGER",
    "{",
    "disabled",
    "(",
    "1",
    ")",
    ",",
    "linkfault",
    "(",
    "2",
    ")",
    ",",
    "passiveWait",
    "(",
    "3",
    ")",
    ",",
    "activeSendLocal",
    "(",
    "4",
    ")",
    ",",
    "sendLocalAndRemote",
    "(",
    "5",
    ")",
    ",",
    "sendLocalAndRemoteOk",
    "(",
    "6",
    ")",
    ",",
    "oamPeeringLocallyRejected",
    "(",
    "7",
    ")",
    ",",
    "oamPeeringRemotelyRejected",
    "(",
    "8",
    ")",
    ",",
    "operational",
    "(",
    "9",
    ")",
    "}",
    "MAX-ACCESS",
    "read-only",
    "STATUS",
    "current",
    "DESCRIPTION",
    "\"At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OAM sub layer. This value is always disabled(1) if OAM is disabled on this interface via the cienaCesOamAdminState. If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault(2). The passiveWait(3) state is returned only by OAM entities in passive mode (cienaCesOamMode) and reflects the state in which the OAM entity is waiting to see if the peer device is OAM capable. The activeSendLocal(4) is used by active mode devices (cienaCesOamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination. The state sendLocalAndRemote(5) indicates that the local OAM entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowed by the local device, the state moves to sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected(8). Note that both the sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAM PDU (reflected in the aOAMRemoteFlagsField of 30.3.6.1.11). When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5].\"",
    "::=",
    "{",
    "cienaCesOamEntry",
    "3",
    "}"
  ],
  "syntax_tree": [
    [
      "SimpleSyntax",
      "INTEGER",
      [
        "enumSpec",
        [
          [
            "disabled",
            1
          ],
          [
            "linkfault",
            2
          ],
          [
            "passiveWait",
            3
          ],
          [
            "activeSendLocal",
            4
          ],
          [
            "sendLocalAndRemote",
            5
          ],
          [
            "sendLocalAndRemoteOk",
            6
          ],
          [
            "oamPeeringLocallyRejected",
            7
          ],
          [
            "oamPeeringRemotelyRejected",
            8
          ],
          [
            "operational",
            9
          ]
        ]
      ]
    ],
    null,
    [
      "MaxAccessPart",
      "read-only"
    ],
    [
      "Status",
      "current"
    ],
    [
      "DESCRIPTION",
      "At initialization and failure conditions, two OAM entities on the same full-duplex Ethernet link begin a discovery phase to determine what OAM capabilities may be used on that link. The progress of this initialization is controlled by the OAM sub layer. This value is always disabled(1) if OAM is disabled on this interface via the cienaCesOamAdminState. If the link has detected a fault and is transmitting OAMPDUs with a link fault indication, the value is linkFault(2). The passiveWait(3) state is returned only by OAM entities in passive mode (cienaCesOamMode) and reflects the state in which the OAM entity is waiting to see if the peer device is OAM capable. The activeSendLocal(4) is used by active mode devices (cienaCesOamMode) and reflects the OAM entity actively trying to discover whether the peer has OAM capability but has not yet made that determination. The state sendLocalAndRemote(5) indicates that the local OAM entity has discovered the peer but has not yet accepted or rejected the configuration of the peer. The local device can, for whatever reason, decide that the peer device is unacceptable and decline OAM peering. If the local OAM entity rejects the peer OAM entity, the state becomes oamPeeringLocallyRejected(7). If the OAM peering is allowed by the local device, the state moves to sendLocalAndRemoteOk(6). Note that both the sendLocalAndRemote(5) and oamPeeringLocallyRejected(7) states fall within the state SEND_LOCAL_REMOTE of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the local OAM client has actively rejected the peering or has just not indicated any decision yet. Whether a peering decision has been made is indicated via the local flags field in the OAMPDU (reflected in the aOAMLocalFlagsField of 30.3.6.1.10). If the remote OAM entity rejects the peering, the state becomes oamPeeringRemotelyRejected(8). Note that both the sendLocalAndRemoteOk(6) and oamPeeringRemotelyRejected(8) states fall within the state SEND_LOCAL_REMOTE_OK of the Discovery state diagram [802.3ah, Figure 57-5], with the difference being whether the remote OAM client has rejected the peering or has just not yet decided. This is indicated via the remote flags field in the OAM PDU (reflected in the aOAMRemoteFlagsField of 30.3.6.1.11). When the local OAM entity learns that both it and the remote OAM entity have accepted the peering, the state moves to operational(9) corresponding to the SEND_ANY state of the Discovery state diagram [802.3ah, Figure 57-5]."
    ],
    null,
    null,
    null,
    null
  ]
}

Registration

Registration authorities

First Registration Authority (inferred from ancestor 1.3.6.1.4.1.1271)

Jones Wes

Siblings (8)

OIDNameDirect childrenDescendantsDescription
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.1 cienaCesOamPort00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.2 cienaCesOamAdminState00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.4 cienaCesOamMode00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.5 cienaCesMaxOamPduSize00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.6 cienaCesOamConfigRevision00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.7 cienaCesOamFunctionsSupported00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.8 cienaCesOamPduTimer00
1.3.6.1.4.1.1271.2.3.5.1.1.4.1.9 cienaCesOamLinkLostTimer00